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

18 - 3
f. The Restore To and Restore From paths will automatically be populated when the
replication set is selected. The restore to path is the directory that is the common parent
directory for all of the directories in the replication set. If the replication set crosses
volumes, then there will be a separate path for each volume. The restore from path is the
path on the target server where the replicated files are located.
g. Select the Use Backup Replication Set check box to use the target’s copy of the replication
set database for the restoration. If this check box is not marked, you will be accessing the
replication set information from the source.
h. Select the Restore Replication Set check box to restore the target’s copy of the replication
set database to the source during the restoration process.
i. Select the restoration conditionals that you want to use.

Overwrite existing files during restore — This option restores all existing files by
overwriting them. Any files that do not exist on the source are written also. If this option
is disabled, only files that do not exist on the source will be restored.

Only if backup copy is more recent—This option restores only those files that are
newer on the target than on the source. The entire file is overwritten with this option.

Use block checksum comparison/delta block transfer—Specify if you want the
restoration process to use a block checksum comparison to determine which blocks are
different. If this option is enabled, only those blocks (not the entire files) that are
different will be restored to the source.
j. If you want to configure orphan files, click the Orphans tab. The same orphan options are
available for a restoration connection as a standard connection. See Configuring and
removing orphan files on page 11-7 for more details.
k. If your source was archiving files, select the Archive tab. Select how you want to restore
those files that have been archived. See the tab Archive Restoration Criteria on page 16-2
for details on how the restoration and archive criteria work together.
l. If you selected the link restore, specify where you want the archive data to be located.
Specify One Per Volume to use one archive bin on each volume of the target. Specify
Centralized To Volume and specify a volume to store all archive data in the same location.
m. 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.
n. 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. 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.
NOTE: Restoring across a NAT router requires the ports to be the same as the original
connection. If the ports have been modified (manually or reinstalled), you must
set the port numbers to the same values as the last valid source/target
connection.
NOTE: If you are using a database application, do not use the newer option unless
you know for certain you need it. With database applications, it is critical that
all files, not just some of them that might be newer, get mirrored.
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.