CLI Guide

Table Of Contents
consistency-group resume-at-loser
If I/O is suspended due to a data change, resumes I/O at the specified cluster and consistency group.
Contexts
All contexts (at the losing cluster).
In /clusters/cluster-n/consistency-groups/group-name context, command is resume-at-loser.
Syntax
consistency-group resume-at-loser
[-c|--cluster] cluster
[-s|--consistency-group]consistency-group
[-f|--force]
Arguments
Required arguments
[-c|--cluster] cluster * The cluster on which to roll back and resume I/O.
[-g|--consistency-
group] consistency-group
* The consistency group on which to resynchronize and resume I/O.
Optional arguments
[-f|--force]
Do not prompt for confirmation. Without this argument, the command asks for confirmation
to proceed. This protects against accidental use while applications are still running at the
losing cluster which could cause applications to misbehave. Allows the command to be
executed from a non-interactive script.
* - argument is positional.
Description
During an inter-cluster link failure, you can permit I/O to resume at one of the two clusters: the winning cluster.
I/O remains suspended on the losing cluster.
When the inter-cluster link heals, the winning and losing clusters re-connect, and the losing cluster discovers that the winning
cluster has resumed I/O without it.
Unless explicitly configured otherwise (using the auto-resume-at-loser property), I/O remains suspended on the losing
cluster. This prevents applications at the losing cluster from experiencing a spontaneous data change.
The delay allows the administrator to shut down applications.
After stopping the applications, you can use this command to:
Resynchronize the data image on the losing cluster with the data image on the winning cluster,
Resume servicing I/O operations.
You can then safely restart the applications at the losing cluster.
Without the --force option, this command asks for confirmation before proceding, since its accidental use while applications
are still running at the losing cluster could cause applications to misbehave.
102
Commands