I wish to set the establish to adaptive copy disk mode for this new device pair as I dont want to affect the production device performance while synching.
Can I do this for just the pair of devices ?. Also the first step returns an error saying
Cannot add a non R1 device to a device group of RDF R1 devices..
To do this seamlessly you need 5773 microcode on your DMX3, and a resent version of Solutions Enabler. These things give you access to the MOVEPAIR / Consistency Exempt functionality. The MOVEPAIR allows an existing SRDF device to be moved from one RDF group to another. The Consistency Exempt feature allows a device NOT to be in step with all other devices in an existing SRDF/A group.
Here is what you do: - SRDF/A remains active at all times.
- Create an RDF group for the purposes of initial synch up.
- Do the create pair to the synch-up RDF group.
- Synch the device in Adaptive copy mode.
- suspend the device with the -cons_exempt option
- perform a symrdf MOVEPAIR to move the new device into the SRDF/A group
- on the new device (not sure if this step is required from memory)
- symrdf resume the device
- The consistency exempt flag will go away automatically once the device is in srdf/a mode with no invalid tracks (in lock step with all other devices)
- now you can add the device into the device group.
'Cannot add a non R1 device to a device group of RDF R1 devices.."
..the devs are
Dynamic RDF Capability : RDF1_OR_RDF2_Capable
Check to be sure your new device is DYNAMIC RDF device before adding it to the RDF Group.
REMINDER:
If you find any of the replies to your question as helpful, please be so kind as to mark replies as being "helpful" or "answered". This helps us track our success with the Forum.
Looks good to me. However you can skip a step of disabling consisteny by using the cons_exempt option while running the createpair command. This option will exempt the newly created device from consistency and allow this non consistent pair to be added to the consistent group. After two cycles, your newly added devicepair will become consistent..
on step 8, its not 30,000K , it is 30,000 tracks; considerring each track 64KB(128 blocks of 512 bytes) then when you are close to 2GB left to sycn you may put in async mode.
Do you see any document metioned cons_exempt being enabled from a particular code level?. I searched in couple of RN i have and did not get a hit at all.
PedalHarder
4 Apprentice
•
465 Posts
2449
1
Posted November 16th, 2010 23:00
To do this seamlessly you need 5773 microcode on your DMX3, and a resent version of Solutions Enabler. These things give you access to the MOVEPAIR / Consistency Exempt functionality. The MOVEPAIR allows an existing SRDF device to be moved from one RDF group to another. The Consistency Exempt feature allows a device NOT to be in step with all other devices in an existing SRDF/A group.
Here is what you do:
- SRDF/A remains active at all times.
- Create an RDF group for the purposes of initial synch up.
- Do the create pair to the synch-up RDF group.
- Synch the device in Adaptive copy mode.
- suspend the device with the -cons_exempt option
- perform a symrdf MOVEPAIR to move the new device into the SRDF/A group
- on the new device (not sure if this step is required from memory)
- symrdf resume the device
- The consistency exempt flag will go away automatically once the device is in srdf/a mode with no invalid tracks (in lock step with all other devices)
- now you can add the device into the device group.