v Whenever the command is issued on a mirrored CG Master - and the Master
does not receive an acknowledgment from the Slave (until the command timed
out or due to any unexpected failure), a completion code is returned
(MIRROR_POSSIBLE_CONS_GROUP_MEMBERSHIP_MISMATCH).
If the command CG_ADD_VOLUME is issued on a mirrored CG Master - and the
Master does not receive an acknowledgment from the Slave (until the command
timed out or due to any unexpected failure), a new completion code will be
returned (MIRROR_POSSIBLE_CONS_GROUP_MEMBERSHIP_MISMATCH -
meaning that the member lists of the mirror Consistency Group peers might not be
the same).
If applied on a volume that is part of an IBM Hyper-Scale Mobility relation:
v The command is applicable only to a destination volume
v This destination volume has to be in Proxy state
Otherwise, a completion code is returned (see below).
Example:
cg_add_vol cg=DBGroup vol=DBLog
Output:
Command completed successfully.
Access Control:
User Category Permission
Storage administrator Allowed
Storage integration administrator Allowed
Application administrator Disallowed
Security administrator Disallowed
Read-only users Disallowed
Technicians Disallowed
Warnings:
v CONS_GROUP_MIRROR_DESIGNATION_MISMATCH
Volume Mirror has different designation than Consistency Group Mirror. Are
you sure you want to add that Volume to that CG?
Completion Codes:
v VOLUME_BAD_NAME
Volume name does not exist
v CONS_GROUP_BAD_NAME
Consistency Group name does not exist.
v CONS_GROUP_IS_SLAVE
Consistency Group is mirroring slave.
v MAX_VOLUMES_IN_CONS_GROUP_REACHED
The maximum permitted number of volumes per Consistency Group is reached.
Chapter 6. Consistency Group Management 79
To Next Page
Loading...
Need help?
General
