Administrator Guide

● Modify the Snapshot Basename to change the snapshot name. The name is case sensitive and can have a maximum of
26 bytes. It cannot already exist in the system or include the following characters: " , < \
● Set the Retention Priority to specify the snapshot retention priority.
● Optional: Select the Primary Volume Snapshot History check box to keep a snapshot history for the primary volume
on the primary system
10. Optional: Select the Scheduled check box to schedule recurring replications.
11. Click OK.
12. In the success dialog box:
● If you selected the Scheduled check box, click OK. The Schedule Replications panel opens and you can set the options
to create a schedule for replications. For more information on scheduling replications, see Initiating or scheduling a
replication from the Volumes topic.
● Otherwise, you have the option to perform the first replication. Click Yes to begin the first replication, or click No to
initiate the first replication later.
Initiating or scheduling a replication from the Volumes
topic
After you have created a replication set, you can copy the selected volume or volume group on the primary system to the
secondary system by initiating replication. The first time that you initiate replication, a full copy of the allocated pages for the
volume or volume group is made to the secondary system. Thereafter, the primary system only sends the contents that have
changed since the last replication.
You can manually initiate replication or create a scheduled task to initiate it automatically from both the Replications and
Volumes topics. You can initiate replications only from a replication set's primary system. For information on modifying or
deleting a replication schedule, see Managing replication schedules from the Volumes topic.
NOTE:
If you change the time zone of the secondary system in a replication set whose primary and secondary systems
are in different time zones, you must restart the system to enable management interfaces to show proper time values for
replication operations.
If a replication fails, the system suspends the replication set. The replication operation will attempt to resume if it has been
more than 10 minutes since the replication set was suspended. If the operation has not succeeded after six attempts using the
10-minute interval, it will switch to trying to resume if it has been over an hour and the peer connection is healthy.
NOTE:
Host port evaluation is done at the start or resumption of each replication operation. At most, two ports will be
used. Ports with optimized paths will be used first. Ports with unoptimized paths will be used if no optimized path exists. If
only one port has an optimized path, then only that port will be used. The replication will not use another available port until
all currently used ports become unavailable.
NOTE: If a single host port loses connectivity, event 112 will be logged. Because a peer connection is likely to be associated
with multiple host ports, the loss of a single host port may degrade performance but usually will not cause the peer
connection to be inaccessible.
Manually initiate replication from the Volumes topic
NOTE:
If CHAP is enabled on one system within a peer connection, be sure that CHAP is configured properly on the
corresponding peer system before initiating this operation. For more information about configuring CHAP, see CHAP and
replication.
1. In the Volumes topic, select a replication set in the Replication Sets table.
2. Select Action > Replicate.
The Replicate panel opens.
3. Click OK.
● If a replication is not in progress, the local system begins replicating the contents of the replication set volume to the
remote system and the status of the replication set changes to Running.
● If a replication is already in progress, then the outcome of this replication request depends upon the Queue Policy setting
specified in the Create Replication Set panel. For more information on setting the queue policy, see Queuing replications.
Working in the Volumes topic
109