Administrator Guide

○ low. Snapshots can be deleted. This parameter is unrelated to snapshot history, and because the default is never delete, snapshot
history snapshots will normally not be affected in a low virtual memory situation.
When this option is disabled, snapshot history will not be kept. If this option is disabled after a replication set has been established, any
existing snapshots will be kept, but not updated.
Create a replication set from the Replications 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 Peer Connections table, select the peer connection to use for the replication set.
2. Select Action > Create Replication Set. The Create Replication Set panel appears.
3. Enter a 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 characters: " , < \
4. Select whether you want to use a single volume or a volume group, which will filter the entries in the adjacent table.
5. In the table, select the volume or volume group to replicate. This will be the primary volume or volume group.
6. Optional: If Single Volume is selected, enter a name for the secondary volume. The default name is the name of the primary volume.
The name is case sensitive and can have a maximum of 32 bytes. It cannot already exist on the secondary system or include the
following: " , < \
7. Optional: Select a pool on the secondary system. By default, the pool that corresponds with the pool in which the primary volume
resides is selected. The selected pool must exist on the remote system.
8. Optional: Specify the Queue Policy action to take when a replication is running and a new replication is requested.
9. 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 specify the number of snapshots to retain.
• 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: Check Primary Volume Snapshot History 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
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.
Working in the Replications topic
123