HP Storage Mirroring V5.1 Software - Manual (Page 134)

18 - 5
Failback then restoration
Failback before restoration can be a simpler process, but it may require additional downtime. The
amount of downtime will depend on the amount of data to be restored. Users must be kept off of the
source and target during this entire process.
1. Resolve the problem(s) on the source that caused it to fail. Make sure in resolving the problems,
that you do not bring the source on the network at this time because the target currently has the
source’s identity because of failover.
2. Schedule a time for this process. Select a time that will have minimal disruption on your users.
3. When you are ready, begin the failback process.
a. From the Failover Control Center, select the target that is currently standing in for the failed
source.
b. Select the failed source and click Failback. The user downtime starts now. If you have a
pre-failback script configured, it will be started.
c. When failback is complete, the post-failback script, if configured, will be started. When the
script is complete, you will be prompted to determine if you want to continue monitoring the
source, do not select either option. Leave the prompt dialog box open as is.
4. Bring your source onto the network at this time, but make sure that the users are not accessing
it. The target must be able to access the source, but users cannot access the source because the
data on the source is out-of-date.
5. Once your source is on the network, select Continue or Stop in the Failover Control Center to
indicate if you want to continue monitoring the source. After you have selected whether or not to
continue monitoring the source machine, the source post-failback script, if configured, will be
started.
6. Stop any applications that may be running on your source. The files must be closed on the
source so that updated files from the target will overwrite the files on the source.
NOTE: If the target is a cluster, you will need to determine the active node and failback
from that node. Then you will need to failback from each of the other nodes to
synchronize all of the nodes of the cluster.
NOTE: The source must be online and Storage Mirroring must be running to ensure that the
source post-failback script can be started. If the source has not completed its boot
process, the command to start the script may be lost and the script will not be
initiated.