Software Manual

C.81
Synchronous Long Distance Remote Copy Disaster Recovery Example
InForm OS Version 2.3.1 Remote Copy User’s Guide
1 Initiate disaster recovery to the asynchronous periodic backup server, InServC, by issuing
the
setrcopygroup failover command on InServC.
By issuing
setrcopygroup failover as shown in the example above:
◆ The disaster recovery operation is run against all groups that were secondary groups to
InServA.
◆ All tasks required for each group to be processed are displayed as is the status of each
task. This can take several minutes to complete.
◆ By default, the setrcopygroup failover command attempts to pull any newer
data from the synchronous backup server (InServB). In doing so, InServB temporarily
assumes the role of the primary storage server. Issuing the
-discard option bypasses
# setrcopygroup failover -f -t -discard InServA
failover started with tasks: 6740
root@xnodeeca5:~/bin# waittask -v 6740
Id Type Name Status Phase Step -------StartTime----
--- -FinishTime-
6740 remote_copy_failover multi.1.r96 active 1/3 0/1 2009-06-29 14:43:44
PDT -
Detailed status:
2009-06-29 14:43:44 PDT Created task.
2009-06-29 14:43:44 PDT Begin Failover operation on group multi.1.r96
started.
2009-06-29 14:43:47 PDT Pushing Pushing newer data from target InServB
to group multi.1.r96.
2009-06-29 14:43:47 PDT Waiting Waiting for synchronization of group
multi.1.r96 to target InServB to complete.
2009-06-29 14:44:04 PDT Pushed Completed push of newer data from target
InServB to group multi.1.r96.
2009-06-29 14:44:05 PDT Switched Group multi.1.r96 was switched from
secondary to primary.
2009-06-29 14:44:05 PDT Starting Starting group multi.1.r96 to target
InServB.
2009-06-29 14:44:09 PDT Started Remote copy was started for group
multi.1.r96 and target InServB.
2009-06-29 14:44:09 PDT Completed Group multi.1.r96 failover completed.
NOTE: Because failover of individual groups can still fail, these tasks should be
checked for successful completion.