Table of Contents
Advertisement
The force_on_slave parameter:
v The parameter force_on_slave can be issued by a user only if mirroring is in
Access Control:
Warnings:
v ARE_YOU_SURE_YOU_WANT_TO_DELETE_CG_MIRRORING
Completion Codes:
v VOLUME_BAD_NAME
v VOLUME_NO_MIRROR
v CONS_GROUP_BAD_NAME
v CONS_GROUP_NO_MIRROR
v LOCAL_PEER_IS_NOT_MASTER
v MIRROR_IS_ACTIVE
v FORCE_DELETE_NOT_ALLOWED_ON_MASTER
v VOLUME_BELONGS_TO_MIRRORED_CONS_GROUP
v MIRROR_RETRY_OPERATION
v MIRROR_IS_NOT_INITIALIZING
222
IBM XIV Storage System User Manual
– Run the mirror_change_role command to turn the Slave into the Master
– Run mirror_delete
initialization (in any other mode the role can be changed to Master and the peer
mirror can be deleted.).
User Category
Storage administrator
Storage integration administrator
Application administrator
Security administrator
Read-only users
Technicians
Are you sure you want to delete the mirroring relationships of the CG and of all
volumes in the CG?
Volume name does not exist
Local volume does not have remote mirroring definitions
Consistency Group name does not exist.
Local Consistency Group does not have remote mirroring definitions
Local peer is not the master
Remote mirroring is currently active
Only slave mirrors need to be forced to be deleted
Volume mirror is part of Consistency Group mirror.
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
Operation is permitted only during the Initialization phase.
Permission
Allowed
Allowed
Disallowed
Disallowed
Disallowed
Disallowed
Hide quick links:
Advertisement
Chapters
Table of Contents
