Unsolved
This post is more than 5 years old
1 Message
0
711
Changing BCV sig's/labels and bringing up a DB after a Symmir est from R2's
Hello, looking for advice on how to go about bringing up a DB on BCV's after a nightly Symmir est from R2's. We have a process in place now, however we need to increase space. They are basic disks, so we need to create new disks and migrate current to new. We have a DR system at another location and use SRDF. That DR system is also used for reporting and query by doing a nightly Symmir est to BCV's from the R2's and then bringing up the query DB on those BCV's. I was not the original author and in looking at the scripts, after the est and then split the BCV's are set to not_ready using Symdev. Then a Symld relabel occurs on those BCV's (no other parameters other than the bcv's) and then they are made ready before bringing the query DB up. I would imagine that the relabel is reading information from somewhere to change the label/sig to something other than the original R1-R2-BCV. What is that Symld relabel reading and then changing on the BCV's after an est? It's on a Windows 2003 IA64 running SQL 2000.
Regards
Bob MacD
Regards
Bob MacD
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
June 1st, 2007 11:00
To get the label information into the symapi_db.bin file in the first place, you use the "symlabel define" command.
Check the man page on symlabel for a description. In order to relabel, the device must be not_ready, which is why your script will issue the symmir split -not_ready.