Unsolved
This post is more than 5 years old
4 Posts
0
2929
Resetting BCV Information
Does anyone know if there is a way to reset a BCV so that it will not show the STD device name it was paired with after breaking the relationship using a symmir cancel command?
A way to refresh the BCV so it displays N/A for the STD device information in the "BCV Pair Information" section, like a newly created BCV does, would be ideal. If that is not possible, any way to remove/replace the STD device information with something else would be helpful.
Here is an example for clarification. The STD device was 0AA6, and the BCV device was 059D. The symmir cancel was ran to break this relationship and the STD device no longer shows the BCV information.
When I run a symdev show on the BCV it shows this.
BCV Pair Information
{
Standard (STD) Device Symmetrix Name : 0AA6
Standard (STD) Device Serial ID : Not Visible
Standard (STD) Device Group Name : Not/Grouped
Standard (STD) Composite Group Name : Not/Grouped
I would like it to show something more like this.
BCV Pair Information
{
Standard (STD) Device Symmetrix Name : N/A
Standard (STD) Device Serial ID : N/A
Standard (STD) Device Group Name : N/A
Standard (STD) Composite Group Name : N/A
A way to refresh the BCV so it displays N/A for the STD device information in the "BCV Pair Information" section, like a newly created BCV does, would be ideal. If that is not possible, any way to remove/replace the STD device information with something else would be helpful.
Here is an example for clarification. The STD device was 0AA6, and the BCV device was 059D. The symmir cancel was ran to break this relationship and the STD device no longer shows the BCV information.
When I run a symdev show on the BCV it shows this.
BCV Pair Information
{
Standard (STD) Device Symmetrix Name : 0AA6
Standard (STD) Device Serial ID : Not Visible
Standard (STD) Device Group Name : Not/Grouped
Standard (STD) Composite Group Name : Not/Grouped
I would like it to show something more like this.
BCV Pair Information
{
Standard (STD) Device Symmetrix Name : N/A
Standard (STD) Device Serial ID : N/A
Standard (STD) Device Group Name : N/A
Standard (STD) Composite Group Name : N/A
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
October 5th, 2007 13:00
xe2sdc
2 Intern
2 Intern
•
2.8K Posts
0
October 6th, 2007 12:00
Sorry Dynamox .. I don't know any strange exotic symwhatever that handles this
Kiran3
410 Posts
0
October 8th, 2007 07:00
Kiran3
410 Posts
0
October 8th, 2007 07:00
cancel
Cancels the existing internal DeltaMark session between the specified standard and BCV
device(s). Once the DeltaMark session is cancelled, the corresponding BCV device goes
into the SplitNoInc state, and the BCV pair can no longer be incrementally established or
restored. Cancel can also be used to remove any one of the multi-BCV devices from a
multi-BCV set.
detach
Detaches a BCV device from the standard device and disassociates (unmarks) this pair as
the preferred pair when full establish and restore operations occur.
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
October 8th, 2007 07:00
xe2sdc
2 Intern
2 Intern
•
2.8K Posts
0
October 8th, 2007 09:00
VTOCing the device will fill the device (the BCV) with zeroes .. but I'm not sure that this will clear the relationship between the BCV and its last STD. As many of you -maybe- already know, when EMC changes a broken disk, all the BCVs on the broken disk will need a FULL establish. The main reason for the full establish is that you need to copy data from STD to BCV. But you also need to refresh the relationship between the STD and its BCV since the "hidden" data is lost and gone
Maybe MRTs2Symm or MLee may help further ...
xe2sdc
2 Intern
2 Intern
•
2.8K Posts
0
October 8th, 2007 09:00
wdora
4 Posts
0
October 8th, 2007 09:00
Thank you very much for all the helpful responses.
xe2sdc
2 Intern
2 Intern
•
2.8K Posts
0
October 8th, 2007 11:00
xe2sdc
2 Intern
2 Intern
•
2.8K Posts
0
October 8th, 2007 11:00
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
October 8th, 2007 11:00
MrTS2Symm
113 Posts
0
October 9th, 2007 11:00
Coming in on the flip side...sorry.
There is an internal way to do this in the Symmetrix, but most hesitate to do it unless there is an issue. In your case, you WANT this relationship discarded, etc. Right? There is a table for the relationship that can be cleared, but it is performed via the EMC Support Centre via your local CE or RTS.
What code family are you running? i.e.-5670, 5772?
Do you want or require all relationships discarded or specific? Continuous or scattered?
Michael
xe2sdc
2 Intern
2 Intern
•
2.8K Posts
0
October 16th, 2007 00:00
symwhatever that handles this
While running some tests I wondered myself if -maybe- removing and giving back the BCV attribute to a volume may clear the STD/BCV relationship.
So I picked up a BCV, run a full establish with a STD volume and split them.
While in split state I took the BCV and converted to unprotected. Symdev, at this point, didn't show the std-bcv relation. But when I added again the BCV flag to the volume, with another symconfigure run, the relation was back again !!
So even removing and adding back BCV flag will not clear the relation between a STD and a BCV
-s-
Message was edited by:
Stefano Del Corno
mlee2
108 Posts
0
October 16th, 2007 01:00
Sorry, I am afraid I cannot help.....
As per MrTS2Symm our internal "Global Dynamic Assignment Table" tracks these STD => BCV, BCV => STD and Dynamic RDF relationships. Converting from BCV to STD to BCV would not clear this associated entry in the table since the volume still exists.
Your next "test" should be to perform an online deletion (this should remove the deleted Symm Vol # from the GDAT) and volume re-addition but that IS getting a little drastic....
IF this is more than a display issue or a display issue causing concern (without a workaround) then I suggest that the local friendly EMC Support person or the EMC Support Centre should submit an enhancement request
Regards,
Michael.
xe2sdc
2 Intern
2 Intern
•
2.8K Posts
0
October 16th, 2007 01:00