Administrator Guide

● 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 Replications 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.
Modifying a replication set
You can change a replication set's name, queue policy, and snapshot history settings. Volume membership of a replication
cannot change for the life of the replication set.
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.
Modify a replication set
1. In the Replications topic, select the replication set in the Replications Sets table that you want to modify.
2. Select Action > Modify Replication Set. The Modify Replication Set panel opens.
3. Enter a new name for the replication set. The name is case sensitive and can have a maximum of 32 bytes. It cannot already
exist in the system, include leading or trailing spaces, or include the following: " , < \
4. Specify the Queue Policy action to take when a replication is running and a new replication is requested.
● Discard. Discard the new replication request.
● Queue Latest. Take a snapshot of the primary volume and queue the new replication request. If the queue contained
an older replication request, discard that older request. A maximum of one replication can be queued. If the queue policy
is set to Queue Latest and a replication is running and another is queued, you cannot change the queue policy to
Discard. You must manually remove the queued replication before you can change the policy.
5. Optional: Select the Secondary Volume Snapshot History check box to keep a snapshot history on the secondary system
for the secondary volume.
● Set the Retention Count to modify the number of snapshots to retain. Its value must be greater than the number of
existing snapshots in the replication set, regardless of whether snapshot history is enabled.
NOTE:
If you reduce the snapshot count setting to a value less than the current number of snapshots, the operation
will fail. Thus, you must manually delete the excess snapshots before reducing the snapshot count setting. If you
change this parameter while a replication is running, for the current replication it will affect only the secondary
system. In this case the value can only be increased, so you might have one less expected snapshot on the primary
system than on the secondary system.
● Set the Snapshot Basename to modify 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: " , < \
NOTE:
If you change the Snapshot Basename while a replication is running, for the current replication it will affect
the name of the snapshot on the secondary system. For that replication only, the names of the snapshots on the
primary and secondary systems will differ.
● Set the Retention Priority to specify the snapshot retention priority.
● Optional: Check Primary Volume Snapshot History to keep a snapshot history for the primary volume on the primary
system.
6. Click OK. The name of the replication set is updated in the Replications Sets table.
Deleting a replication set
You can delete a replication set. When you delete a replication set, all infrastructure created by the system (internal snapshots
required to support replications) is also deleted. The primary and secondary volumes and volume groups no longer have
restrictions and function like all other base volumes, volume groups, and snapshots.
If you want to delete a replication set that has a replication in progress, you must first suspend and then stop the replication
for that replication set. For more information, see Stopping a replication or Suspending a replication. When a replication set
is deleted, the snapshots created from the snapshot history feature will not be deleted. You will be able to manage those
130
Working in the Replications topic