Completion Codes:
v VOLUME_BAD_NAME
Volume name does not exist
v VOLUME_NOT_IN_CONS_GROUP
Volume does not belong to a Consistency Group
v TARGET_NOT_CONNECTED
There is no connection to the target system
v VOLUME_IS_SNAPSHOT
Operation is not permitted on snapshots
v CONS_GROUP_IS_SLAVE
Consistency Group is mirroring slave.
v MIRROR_RETRY_OPERATION
There is an operation in progress on this mirror , please retry your request in a
few seconds
Troubleshooting: Please retry the command in a few seconds
v MIRROR_HAS_SYNC_JOB
Operation is not permitted on a mirror with active sync jobs
v MIRROR_POSSIBLE_CONS_GROUP_MEMBERSHIP_MISMATCH
Mirrored CG may contain different volumes on Master and Slave. This problem
occurs whenever the cg_add_vol command results with the Master not receiving
an acknowledgment from the Slave until the command timed out, or any other
unexpected failure.
v VOLUME_IS_NOT_CONSISTENT_SLAVE
Operation not allowed on slave volume that is not consistent.
v SNAPSHOT_HAS_ACTIVE_SYNC_JOB
Snapshot is currently a target of an active sync job
Troubleshooting: Please wait for sync job to complete
v VOLUME_HAS_OLVM
IBM Hyper-Scale Mobility relation is defined for this volume
Renaming Consistency Groups
Renames Consistency Groups.
cg_rename cg=cgName new_name=Name
Parameters:
Name Type Description Mandatory
cg Object name The name of the
Consistency Group to
be renamed.
Y
new_name Object name The new name of the
Consistency Group.
Y
This command renames a Consistency Group.
The new name of the Consistency Group must be unique in the system.
86 IBM XIV Storage System User Manual
To Next Page
Loading...
Need help?
General
