v Deactivating a Consistency Group affects all of its volumes
Note:
v The command can't be issued on the Slave.
The command fails under the following conditions:
v The specified target does not exist
v The specified target is non-mirrored
v The specified target is a volume that belongs to a Consistency Group (in such a
case, you have to deactivate the entire Consistency Group)
v Some of the specified targets are masters and some are slaves
– The command can be applied at each time to either master[s] or slave[s], but
not both
v The target is slave, yet the link is up.
v If multiple volumes are specified in the command and some are already part of
an inactive mirror, the command will fail for all mirrors, including those that
were active. The relevant completion code is: SYNC_ALREADY_INACTIVE.
Access Control:
User Category Permission
Storage administrator Allowed
Storage integration administrator Allowed
Application administrator Disallowed
Security administrator Disallowed
Read-only users Disallowed
Technicians Disallowed
Completion Codes:
v VOLUME_BAD_NAME
Volume name does not exist
v VOLUME_NO_MIRROR
Local volume does not have remote mirroring definitions
v CONS_GROUP_BAD_NAME
Consistency Group name does not exist.
v CONS_GROUP_NO_MIRROR
Local Consistency Group does not have remote mirroring definitions
v LOCAL_PEER_IS_NOT_MASTER
Local peer is not the master
v SYNC_ALREADY_INACTIVE
Synchronization is already inactive
v VOLUME_BELONGS_TO_MIRRORED_CONS_GROUP
Volume mirror is part of Consistency Group mirror.
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
220 IBM XIV Storage System User Manual
To Next Page
Loading...
Need help?
General
