Administrator Guide

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 Replications topic
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 Replications 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.
Schedule a replication from the Replications topic
1. In the Replications topic, select a replication set from the Replication Sets table.
2. Select Action > Replicate.
The Replicate panel opens.
3. Select the Schedule check box.
4. Type a name for the replication schedule task. The name is case sensitive and can have a maximum of 32 bytes. It cannot already exist
in the system or include the following: " , < \
5. If you want to create a replication of the last snapshot of the primary volume, select the Last Snapshot check box.
At the time of the replication, the snapshot must exist. This snapshot may have been created either manually or by scheduling the
snapshot. If no snapshot exists for the volume when the scheduled replication begins, event 362 is logged and the replication fails.
NOTE: This option is unavailable when replicating volume groups.
6. Specify a date and a time in the future to be the first instance when the scheduled task will run, and to be the starting point for any
specified recurrence.
• To set the Date value, enter the current date in the format YYYY-MM-DD.
• To set the Time value, enter two-digit values for the hour and minutes and select either AM, PM, or 24H (24-hour clock). The
minimum interval is one hour.
7. If you want the task to run more than once, select the Repeat check box.
• Specify how often the task should repeat. Enter a number and select the appropriate time unit. Replications can recur no less than
30 minutes apart.
• Either make sure the End check box is cleared, which allows the schedule to run indefinitely, or select the check box to specify
when the schedule ends. To then specify an end date and time, select the On option, and specify when the schedule should stop
running. Or, select the After option, and specify the number of replications that can occur before the schedule stops running.
Working in the Replications topic
125