Administrator Guide

The snapshot number is incremented each time a replication is requested, whether or not the replication completes — for
example, if the replication was queued and subsequently removed from the queue.
● If the replication set is deleted, any existing snapshots automatically created by snapshot history rules will not be deleted.
You will be able to manage those snapshots like any other snapshots.
● Manually creating a snapshot will not increase the snapshot count associated with the snapshot history. Manually created
snapshots are not managed by the snapshot history feature. The snapshot history feature generates a new name for the
snapshot that it intends to create. If a volume of that name already exists, the snapshot history feature will not overwrite
that existing volume. Snapshot numbering will continue to increment, so the next time the snapshot history feature runs, the
new snapshot name will not conflict with that existing volume name.
● The snapshot basename and snapshot retention count settings only take effect when snapshot history is set to secondary or
both, although these settings can be changed at any time.
● A mapped snapshot history snapshot will not be deleted until after it is unmapped.
● A snapshot created by this feature is counted against the system-wide maximum snapshots limit, with the following result:
○ If the snapshot count is reached before the system limit then the snapshot history is unchanged.
○ If the system limit is reached before the snapshot count then the snapshot history stops adding or updating snapshots.
● You can set the retention priority for snapshots to the following. In a snapshot tree, only leaf snapshots can be deleted
automatically.
○ never-delete. Snapshots will never be deleted automatically to make space. The oldest snapshot in the snapshot history
will be deleted once the snapshot count has been exceeded. This is the default.
○ high. Snapshots can be deleted after all eligible medium-priority snapshots have been deleted.
○ medium. Snapshots can be deleted after all eligible low-priority snapshots have been deleted.
○ 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:
Working in the Replications topic
129