– Run the mirror_change_role command to turn the Slave into the Master
– Run mirror_delete
The force_on_slave parameter:
v The parameter force_on_slave can be issued by a user only if mirroring is in
initialization (in any other mode the role can be changed to Master and the peer
mirror can be deleted.).
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 ARE_YOU_SURE_YOU_WANT_TO_DELETE_CG_MIRRORING
Are you sure you want to delete the mirroring relationships of the CG and of all
volumes in the CG?
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 MIRROR_IS_ACTIVE
Remote mirroring is currently active
v FORCE_DELETE_NOT_ALLOWED_ON_MASTER
Only slave mirrors need to be forced to be deleted
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
v MIRROR_IS_NOT_INITIALIZING
Operation is permitted only during the Initialization phase.
222 IBM XIV Storage System User Manual
To Next Page
Loading...
Need help?
General
