Maximum capacity for mirrored volumes already defined on remote machine
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 MIRRORING_INCOMPATIBLE_TARGET_VERSION
Mirroring is not supported between the system versions of the specified peers.
v NO_OFFLINE_INIT_TYPE_WITH_SLAVE_CREATION
New Volume will be created as slave. Offline init meaningless.
v ASYNC_WITH_OFFLINE_INIT_NOT_SUPPORTED_IN_TARGET
Asynchronous Mirror with offline initialization option is not supported by the
specified Target.
v VOLUME_SIZE_ABOVE_LIMIT
Volume size specified is above limit
v REMOTE_VOLUME_SIZE_ABOVE_LIMIT
Volume size specified is above limit of remote machine
v INVALID_SLICE_OFFSET
Slice number out of range
v VOLUME_IS_OLVM_PROXY
The volume is in an IBM Hyper-Scale Mobility Proxy phase.
v ENCRYPTION_IN_PROGRESS
System is in the process of changing encryption activation state
Deactivating Mirroring
Deactivates mirroring for a defined mirror coupling.
mirror_deactivate < vol=<VolName [ ,VolName...]>|
cg=cgName >
Parameters:
Name Type Description Mandatory
vol Object name Master volume name or
a list of master volumes.
N
cg Object name Master CG name or a
list of master CGs
N
This command deactivates a coupling and switches it to an Inactive state. While in
the Inactive state, only the master volume is updated. This is in contrast to the
Active state, where the slave volume is updated together with the master volume.
If the mirroring is already inactive, this command has no effect and a success code
is returned.
If more than one volume is specified, mirroring on all the volumes is deactivated.
Furthermore, the deactivation of all the volumes is performed as an atomic
operation, so that the slave volumes remain consistent with each other.
Deactivating a Consistency Group:
Chapter 11. Remote Mirroring 219
To Next Page
Loading...
Need help?
General
