This post is more than 5 years old
3 Posts
0
760
August 6th, 2010 10:00
Fail Back from R2 -> R1
Hi,
We have application using Symatrix SRDF replication, I am going test failover this week.
After my aplication failover testing, I want to bring the changes from R2 side to R1. I will be using symrdf comand from Unix host.
Does it matter from which host I run 'symrdf -g restor e' command?
R1 side host? or R2 side host?
Thanks
Sundaram. R
No Events found!
sundaram2
3 Posts
0
August 6th, 2010 12:00
You mean R1 side host?
sundaram2
3 Posts
0
August 6th, 2010 13:00
Thanks for pointing this link: document says source side, thats why I wanted to double check.
◆ The following symrdf restore command is issued from the local host on the
source side. Because the –full option is omitted from the command line, the
system performs an incremental restore, copying tracks that changed on the R2
device to the R1 device. In the process, any tracks on the R1 side that changed
while the SRDF pairs were split are overwritten with data from corresponding
tracks on the R2 side. When the restore is complete, the R1 device will contain
the same data as the R2 device:
symrdf -g Rdf1Grp -noprompt restore
Thanks Agin.
SR
beetgj
16 Posts
0
August 10th, 2010 06:00
Any SYMRDF command can be executed from source or target side....depending where you created your DG, on tge R1 side you will have a DG with type RDF1 and on the R2 side the type of DG will be RDF 2 ...If you are using the "split " command the way to recover synching from R2 to R1 is by using the "restore", you can also use the "failover" to start your DR test but then your host on the R1 side must be down while performing DR test, failover will write disable R1 devs on the front end of source box. When the DR is complete you use the "failback" command which will automatically sync the updates from R2 to R1....