This command fails if one or more of the volumes in the Consistency Group is a
slave of a synchronous mirroring, and it is currently inconsistent due to either a
re-synchronization or an initialization process.
Mirroring limitations:
v This command fails if the volume is a slave of an asynchronous mirroring
coupling (either synchronous or asynchronous).
v This command fails if the volume is a slave of an inconsistent synchronous
coupling.
Example:
cg_snapshots_create cg=DBgroup snap_group=DBbackupdaily
Output:
Command completed successfully.
Access Control:
User Category Permission Condition
Storage administrator Allowed N/A
Storage integration administrator Allowed N/A
Application administrator Conditionally Allowed At least one of the volumes in
the group is mapped to a host or
cluster associated with the user.
If a Snapshot Group overwrite is
used, then the target Snapshot
Group must be one created by a
server administrator.
Security administrator Disallowed N/A
Read-only users Disallowed N/A
Technicians Disallowed N/A
Completion Codes:
v MAX_VOLUMES_REACHED
Maximum number of volumes already defined
v CONS_GROUP_BAD_NAME
Consistency Group name does not exist.
v SNAPSHOT_GROUP_BAD_NAME
Snapshot Group name does not exist.
v SNAPSHOT_GROUP_BAD_PREFIX
Snapshot Group name has a reserved prefix.
v SNAPSHOT_GROUP_NAME_EXISTS
Snapshot Group name already exists.
v CONS_GROUP_EMPTY
Operation is not allowed on an empty Consistency Group.
v CONS_GROUP_MISMATCH
Snapshot Group does not match Consistency Group volumes.
v OVERWRITE_SNAPSHOT_GROUP_DOES_NOT_BELONG_TO_GIVEN_GROUP
Chapter 7. Snapshot Set Management 103
To Next Page
Loading...
Need help?
General
