CLI Guide

● The snapshots are named basename_nnnn, where nnnn starts at 0000 and increments for each
subsequent snapshot. If primary-volume snapshots are enabled, snapshots with the same name
will exist on the primary and secondary systems. The snapshot number is incremented each time
that a replication is requested, whether the replication completes. For example, if the replication
was queued and removed later from the queue.
● You can set the number of snapshots to retain, referred to as the snapshot count. This setting
applies to management of snapshots for both the primary and secondary volume. When the
snapshot count is exceeded, the oldest unmapped snapshot will be discarded automatically. If you
reduce the snapshot count setting (by using the set replication-set command) to a value less than
the current number of snapshots, the command will be rejected. Thus, you must manually delete
the excess snapshots before reducing the snapshot count setting
●
If the replication set is deleted, any existing snapshots that are automatically created by snapshot
history rules are not deleted. You can manage those snapshots like any other snapshots.
● Manually creating a snapshot does not increase the snapshot count that is associated with the
snapshot history. Manually created snapshots are not managed by the snapshot history feature. If
a volume already exists with the name of the snapshot that is intended to be taken, the snapshot
will not occur, and the snapshot number is incremented.
● A snapshot that is 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.
● A mapped snapshot-history snapshot will not be deleted until after it is unmapped.
● The snapshot-basename and snapshot-count settings only take effect when snapshot-history is
set to secondary or both, although these settings can be changed at any time.
Minimum role
manage
Syntax
create replication-set
peer-connection peer-connection-ID
primary-address ip= IPs|wwnn= WWNNs]
primary-volume volume-ID | volume-group-ID
[queue-policy discard|queue-latest]
[secondary-pool A|B]
[secondary-volume-name name]
[snapshot-basename basename]
[snapshot-count #]
[snapshot-history disabled|off|secondary|both]
[snapshot-retention-priority never-delete|high|medium|low]
name
Parameters
peer-connection peer-connection-ID
Specifies the name or serial number of the peer connection on which to create the replication set
primary-address ip=IPs|wwnn=WWNNs|wwpn=WWPNs
Optional. Specifies host ports in the local system by IP address, World Wide Node Name,
or World Wide Port Name. An IP address value can include a port number. For example,
10.134.2.1:3260. Multiple values must be separated by commas and no spaces. For example:
ip=10.134.2.1,10.134.2.2.
primary-volume volume-ID|volume-group-ID
Specifies the name or serial number of a volume or volume group on the local system. Volume-groups
must be specified with the name and .* notation used in mapping.
queue-policy discard|queue-latest
Optional. Specifies the action to take when a replication is running and a new replication is requested.
Alphabetical list of commands 51