HP Storage Mirroring Software - Manual (Page 507)

Failback and restore Page 506 of 677
Failing back then restoring
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. Locate the file connect.sts on the source where you installed Storage Mirroring
Recover and rename it to connect.sts.old. This will keep the original connection
from reconnecting when you bring the source online.
2. 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.
3. Schedule a time for this process. Select a time that will have minimal disruption on
your users.
4. When you are ready, begin the failback process.
a. Open the Failover Control Center and 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.
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.
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.
5. 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.
6. 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.