HP 3PAR Remote Copy Software - Manual (Page 264)

C.46 Synchronous Long Distance Remote Copy Disaster Recovery Example
Remote Copy User’s Guide InForm OS Version 2.3.1
1 Initiate disaster recovery to the synchronous backup server, InServB, by issuing the
setrcopygroup failover command on InServB.
By issuing setrcopygroup 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.
◆ Groups are started on InServC and InServB assumes the role of the primary storage
server and begins mirroring to InServC. All groups are started and synchronized in this
direction. Any newer data that was sent to InServB since the last synchronization
between InServA and InServB (prior to InServA failing) is copied to InServC.
# setrcopygroup failover -f -t InServA
failover started with tasks: 5745
root@xnodee594:~/bin# waittask -v 5745
Id Type Name Status Phase Step -------StartTime----
--- ------FinishTime-------
5745 remote_copy_failover multi.1.r96 done --- --- 2009-06-29 12:16:31
PDT 2009-06-29 12:16:39 PDT
Detailed status:
2009-06-29 12:16:31 PDT Created task.
2009-06-29 12:16:31 PDT Begin Failover operation on group multi.1.r96
started.
2009-06-29 12:16:32 PDT Switched Group multi.1.r96 was switched from
secondary to primary.
2009-06-29 12:16:34 PDT Starting Starting group multi.1.r96 to target
InServC.
2009-06-29 12:16:39 PDT Started Remote copy was started for group
multi.1.r96 and target InServC.
2009-06-29 12:16:39 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.