CLI Guide

● 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
set schedule
Description
Changes parameters for a specified schedule. If you want to change the schedule name, create a new
schedule to replace the existing one. You must specify at least one of the optional parameters for the
command to succeed.
You can schedule a replication task on the primary system only.
Virtual replication tasks are not queued: if a replication task is running and the time comes for
that replication task to start again, that task will be skipped, though it will be counted against the
schedule’s count constraint (if set).
Minimum role manage
Syntax
set schedule
[schedule-specification "specification"]
[task-name task-name]
schedule-name
Parameters
[schedule-specification "specification"]
Optional. Defines when the task will first run, and optionally when it will recur and expire. You can use
a comma to separate optional conditions. Dates cannot be in the past. For times, if neither AM nor
PM is specified, a 24-hour clock is used.
● start yyyy-mm-dd hh:mm [AM|PM]
148 Alphabetical list of commands