I am using srdf (adaptive copy) and have an old srdf pair that has no dg. I need to dissolve both devices within this pairing. I have already unmapped them and set them to the not ready state.
I am unsure of the next steps or requirements -
I have run a symrdf deletepair command with the -force switch and it comes back with: The device is not in a valid RDF state for this operation
I have also tried to dissolve the devices individually - but receive the error: META devices can not be created with RDF devices, nor be altered if later converted to RDF META devices
The R1 - R2 pairing still shows synchronized - i'm guessing that maybe I have to suspend or split them? Can that be done without a device group?
Do the individual devices need the dynamic rdf attribute set to none first?
I'm sure I'm missing a step but not sure what it is.
Also, is there a way to undo both sides of the pair wihout converting the device types? I want to leave them as they are, just dissolve the meta to make them available for later.
I tried running the deletepair command afterwards and received: The device is not in a valid Ready status. Operation cannot proceed
I did set the devices to not ready using the symld -g dgname -bcv not_ready and the device status shows not ready. Is it looking to a different status?
If you have the right licenses and time to spend, you can even convert static relationship to dynamic via (as usual) symconfigure ... "convert rdf xxx to dynamic;" .. and later use "symrdf deletepair" to delete the relationship .. longer than using simply "symconfigure" as zonie suggested ... but if you want a different way of doing the same things
Thanks for the new command - it gives great added srdf information about the device...
I apologize as I may be missing something or I didn't provide the correct information...
When running either symdev show ### or the command you mentioned: symdev -sid ### list -range symdevstart:symdevend -v on either device in the pair, the attribute for Dynamic RDF Capability states RDF1_OR_RDF2_Capable.
Does this mean that these are not a dynamic srdf pair?
Where is it getting the status of the device from when it states The device is not in a valid Ready status. Operation cannot proceed? From device status (mine is not ready) or possibly device rdf status (mine shows ready) and remote device rdf state (shows not ready)? Does device rdf status need to be in the not ready state?
When running either symdev show ### or the command you mentioned: symdev -sid ### list -range symdevstart:symdevend -v on either device in the pair, the attribute for Dynamic RDF Capability states RDF1_OR_RDF2_Capable.
Does this mean that these are not a dynamic srdf pair?
This means simply that the devices CAN be used as either R1 or R2 in a dynamic RDF relation.
If you want to have a list of dynamic pairs you can use "symrdf list" with the "-dynamic" modifier.
This command will show you ONLY dynamic pairs, whichever group they belong. In the above output you'll see three pairs, two belonging to rdf group 21 and another one belonging to rdf group 24.
Where is it getting the status of the device from when it states The device is not in a valid Ready status. Operation cannot proceed? From device status (mine is not ready) or possibly device rdf status (mine shows ready) and remote device rdf state (shows not ready)? Does device rdf status need to be in the not ready state?
Could you please show the failing command and its output??
This last time I ran the deletepair command without the -force switch - it DID state what you mentioned. Fortunately, I don't need the data so the -force switch worked great.
It's important to understand that the warning is too scary then needed. You will loose any data if you use your head before hitting return on the keyboard ..
The message is a warning and at the time you issue the deletepair, it's too soon to say "You will loose data" since when you delete the pairs you are simply going to remove the RDF relationship ... But on the other side, it's impossible to know, when you create new pairs, if the volumes you are using was paired in a RDF relation before .. and maybe had invalid tracks before the deletepair. So the engineer choose to give an early (and maybe too scary) warning instead of loosing data. That's why you are forced to use the -force flag
The first time I ran the deletepair command, with or without the -force switch it came up with: The device is not in a valid RDF state for this operation
That was the most interesting part of the problem .. Unfortunatly we didn't help in the right direction .. but it's great that you had your problem solved anyway
zonie1
41 Posts
1104
0
Posted October 11th, 2007 12:00
Split the pair then run symconfigure based on the base device type.
Device type RDF#+Mir use symconfigure with convert.txt
"convert dev ### to 2-way-mir"
Device type RDF#--BCV+R-5 use symconfigure with convert.txt
"convert dev ### to BCV+R5"
The symconfigure command will undo both sides of the SRDF setup.