HP StorageWorks Storage Mirroring Recover User's Guide (T5437-96008, November 2009)

540 of 739
k. If your original source was using Replicate NT Security by Name, you must
enable that option on the target before you start the restoration. The option is
available on the target’s Server Properties on the Source tab.
l. Click Restore to begin the restoration. You can identify a restoration
connection because it is enclosed in parenthesis ( ) and it has _Restore
appended to the end of the replication set name. The initial restoration is
complete when the Mirror Status is Idle. After the Mirror Status is Idle, the
connection will continue replicating any on-going data changes from the
target to the source.
11. After the Mirror Status is Idle, schedule a time for failback. User downtime will
begin once failback is started, so select a time that will have minimal disruption on
your users.
12. When you are ready, begin the failback process.
a. Open the Failover Control Center.
b. Select the target that is currently standing in for the failed source.
c. 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.
d. 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.
13. Back in the Replication Console, watch the restoration connection until activity has
ended and replication is in a Ready state. This will happen as the final data in
queue, if any, is applied on the source. The replication Ready state indicates
replication is waiting for new incoming data changes. There will not be any
additional data changes because failback has released the source identity, so
users are no longer accessing their data.
14. Once replication is in a Ready state, disconnect the restoration connection from
the target. This is the connection enclosed in parenthesis () and it has _Restore
appended to the end of the replication set name.
Note:
If your target is a cluster, take the Double-Take Source Connection
resource offline to disconnect the connection.
During the restoration, only the data is restored back to the source. Shares
are not created on the source during the restoration. Shares that were