CLI Guide

● 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. This is the default.
NOTE: If the queue policy is queue-latest and a replication is running and another is queued,
you cannot change the queue policy to discard. The queued replication must be manually
removed before you can change the policy.
secondary-pool A|B
Optional. Specifies an existing virtual pool on the remote peer. If this is not specified, the system uses
the corresponding pool on the remote system. For example, if pool A is used on the local system, pool
A is used on the remote system. If this is not specified and the corresponding pool on the remote side
does not exist, this command fails.
secondary-volume-name name
Optional. Specifies a name for the secondary volume. If this is not specified, the name from the
primary volume is used. For volume-group targets, all contained volume names must be unique. Input
rules:
● The value is case-sensitive.
● The value can have a maximum of 32 bytes.
● The value can include spaces and printable UTF-8 characters except: " , < \
● A value that includes a space must be enclosed in double quotes.
There is no default.
snapshot-count #
Optional if snapshot-history is set to disabled or off. Required if snapshot-history is
set to secondary or both.
Specifies the number of snapshots that are taken of the replication volume to retain, from 1 to 16.
When a new snapshot exceeds this limit, the oldest snapshot in the snapshot history is deleted.
The snapshot-count setting can be changed at any time. Its value must be greater than the number
of existing snapshots in the replication set, regardless of whether snapshot-history is enabled.
snapshot-history disabled|off|secondary|both
Optional. Specifies whether to maintain a replication snapshot history for the replication set, as
previously described.
● disabled or off: A snapshot history is not 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 is kept on the secondary system for the secondary volume,
using snapshot-count and snapshot-basename settings.
● both: A snapshot history is kept for the primary volume on the primary system and for the
secondary volume on the secondary system. Both snapshot histories use the same snapshot-
count and snapshot-basename settings
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 of snapshots based on
retention priority is unrelated to deleting the oldest snapshots to maintain a snapshot count.
● never-delete: Snapshots are never automatically deleted to make space. The oldest snapshot
in the snapshot history is 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.
name
Specifies a name for the replication set. Input rules:
52
Alphabetical list of commands