Operating System Software User Manual

4. To verify that the volume groups are started, issue the following command on the recovered
system (SystemA):
# showrcopy groups <group_name>
where <group_name> represents the volume group that should be started (multi.1).
SolutionProblem
The volume groups are not
started.
1. On the recovered system, issue either of the following commands:
startrcopygroup <group_name>
or:
startrcopygroup -pat <pattern>
where -pat <pattern> represents the pattern of volume group names
(multi*).
2. Wait for the synchronizations to complete before continuing.
CAUTION: The volume groups must be started before you continue to the next step and issue
the setrcopygroup restore command.
5. To restore the natural direction of data flow to the remote-copy system, issue the following
command on the failover system (SystemC):
# setrcopygroup restore -f -t <target_name>
where <target_name> represents the name of the target (recovered) system (SystemA).
The setrcopygroup restore command:
• Starts tasks for each group that was recovered.
• Starts a final synchronization from the asynchronous periodic backup system (SystemC)
to both the synchronous backup system (SystemB) and the primary system (SystemA) to
ensure that the systems have the most recent data.
• Stops the volume groups.
• Switches the secondary volume groups on the primary system (SystemA) to primary volume
groups.
• Switches the primary volume groups on the asynchronous periodic backup system
(SystemC) to secondary volume groups.
• Returns the primary system (SystemA) to the role of primary system.
• Starts remote copy on the primary system (SystemA).
The following example shows the list of tasks on the synchronous backup system (SystemC):
# setrcopygroup restore -f -t SystemA
~/bin# waittask -v 6754
Id Type Name Status Phase Step -------StartTime------- -FinishTime-
6754 remote_copy_restore multi.1.r96 active 2/4 1/2 2009-06-29 14:56:49 PDT -
Detailed status:
2009-06-29 14:56:49 PDT Created task.
2009-06-29 14:56:49 PDT Begin Restore operation on group multi.1.r96 started.
2009-06-29 14:56:53 PDT Syncing Synchronization started for group multi.1.r96 to target
SystemA.
Failing Over to the Asynchronous Periodic Backup System (No Data Transfer) 243