v The volume that was previously the slave becomes the master
Before this command switches roles, the system stops accepting new writes to the
local volume. With synchronous mirrors the system will perform all pending
writes, and only after all pending writes have been committed, the roles are
switched.
After the command is executed, the coupling is deactivated and the user has to
activate it in order to restart synchronization. It is advised to create a snapshot
before deactivating the coupling in order to enable recovery from logical errors due
to incorrect server configurations.
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 MIRROR_IS_NOT_SYNCHRONIZED
Mirror is not synchronized
v VOLUME_HAS_DATA_MIGRATION
Data Migration is defined for this volume
v REMOTE_TARGET_NOT_CONNECTED
There is currently no connection from the target system
v VOLUME_BELONGS_TO_MIRRORED_CONS_GROUP
Volume mirror is part of Consistency Group mirror.
v MIRROR_HAS_SYNC_JOB
Operation is not permitted on a mirror with active sync jobs
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_MASTER_DIFFERS_FROM_SLAVE
228 IBM XIV Storage System User Manual
To Next Page
Loading...
Need help?
General
