CLI Guide

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.
[snapshot-history disabled|off|secondary|both]
Optional. Specifies whether to maintain a replication snapshot history for the replication set, as described
above.
disabled or off: A snapshot history will not be kept. If this parameter is disabled after a replication set
has been established, any existing snapshots will be kept, but not updated. This option is the default
secondary: A snapshot history set will be kept on the secondary system for the secondary volume,
using snapshot-count and snapshot-basename settings.
both: A snapshot history will be kept for the primary volume on the primary system and for the
secondary volume on the secondary system. Both snapshot histories will use the same snapshot-
count and snapshot-basename settings.
If you change this parameter while a replication is running, for the current replication it will affect only the
snapping of the secondary volume.
[snapshot-retention-priority never-delete|high|medium|low]
Optional. For virtual storage, this specifies the retention priority for history snapshots, which is used when
automatic deletion of snapshots is enabled by using the set snapshot-space command. In a snapshot tree,
only leaf snapshots can be deleted automatically. Deletion based on retention priority is unrelated to deleting
the oldest snapshots to maintain a snapshot count.
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 value 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.
If you change this parameter while a replication is running, for the current replication it will affect just the
secondary snapshot. An optional primary snapshot will already be created before the change takes affect.
current-replication-set-ID
Specifies the current name or serial number of the replication set for which to change the name.
Examples
Rename the replication set Rep1 to RepSet1.
# set replication-set name RepSet1 Rep1
Change replication set RepSet1’s queue policy to discard a new replication request when a replication is
running.
# set replication-set queue-policy discard RepSet1
For replication set RepSet1 with primary volume Data, enable snapshot history for the secondary volume
only, allowing up to 10 replication snapshots with the basename repsnapData to be retained for that
volume.
# set replication-set snapshot-history secondary snapshot-basename
repsnapData snapshot-count 10 RepSet1
See also
create replication-set
delete replication-set
resume replication-set
show replication-sets
suspend replication-set
Alphabetical list of commands 143