UNSOLVED
SRDF Failover state
SRDF Failover state
1. Assume right now SRDF status for R1-R2 pair is "Failed Over".## R1- Write_Disabled and R2- RW-Enabled
2. Production/Tesing is running on R2. So there will be some R2 invalid tracks with respect to R1.
3. After testing if i dont want R2 modified tracks to be updated onto R1 and i want to establish connection between R1-R2 , which is the best method.
1. Assume right now SRDF status for R1-R2 pair is "Failed Over".## R1- Write_Disabled and R2- RW-Enabled
2. Production/Tesing is running on R2. So there will be some R2 invalid tracks with respect to R1.
3. After testing if i dont want R2 modified tracks to be updated onto R1 and i want to establish connection between R1-R2 , which is the best method.
876
0
Posted July 30th, 2009 02:00
In this situation I'd simply write disable R2 devices and issue an establish (to push changed tracks from R1 to R2 devices, overwriting changes made during tests).876
0
Posted July 30th, 2009 02:00
Also can some one please explain the difference between Update and Restore. In which scenarios we have to use Update/Restore.876
0
Posted July 30th, 2009 18:00
But as per the support matrix given in S.E. Document, we cannot do establish in "Failed Over" RDF state.876
0
Posted July 30th, 2009 18:00
Referring SE 6.5.2 CD "Solutions Enabler Symmetrix SRDF Family CLI Product Guide" page 86.876
0
Posted July 30th, 2009 23:00
As long as your R2 are RW enabled, R1 are WD and link is suspended, you are in "failed over" state. But as soon as you write disable also R2 devices you should have a different status. And possibly establish again your devices
xe2sdc
6 Operator
•
2831 Posts
876
0
Posted July 30th, 2009 02:00
restore
Resumes remote mirroring and initiates an incremental
data copy from the target (R2) device to the source (R1)
device.
update
Updates the source (R1) side with the changes from the
target (R2) side while the target (R2) side is still
operational to its local hosts.