This weekend I will be performing DR testing on our DMX environment. Once we failed over, users will work on R2 LUNs for 4 hours and we need to retain the modified R2 data by copying it to R1. I have read the SRDF guide and understood that failover/failback would be the correct method to retain the modified R2 data and drafted the below specified steps. Please add your points if I miss something.

Note: Both Prod & DR are in Microcode Version 5772.

###########

FAILOVER:-#

###########

APP DBA Shutdown the application & SA umount the FS.

#symrdf -g DGNAME query ==> Check the R1 (Rw), R2 (WD) & Link (RW) status.

#symrdf -g DGNAME failover

#symrdf -g DGNAME query ==> Check the R1 (WD), R2 (RW) & Link (NR) status.

#symrdf -g DGNAME verify -failedover

###########

FAILBACK:-#

###########

APP DBA Shutdown the application & SA umount the FS at DR.

#symrdf -g DGNAME query ==> Check the invalid tracks count.

#symrdf -g DGNAME failback

#symrdf -g DGNAME query ==> Check the R1 (Rw), R2 (WD) & Link (RW) status.

#symrdf -g DGNAME verify -synchronized

#symrdf -g DGNAME query -i 10

###########

ROLLBACK:-#

###########

If they want to cancel the DR testing (for any said reasons) after I failedover, I am planning to use the below steps to roll back without copying the R2 data.

#symrdf -g DGNAME rw_enable R1

#symrdf -g DGNAME establish

#symrdf -g DGNAME query

Thanks much for your time