v SNAPSHOT_IS_PART_OF_SNAPSHOT_GROUP
Snapshot is part of a Snapshot Group
v SYNCHED_SNAPSHOTS_NOT_SUPPORTED_IN_TARGET
Synchronized Snapshot capability is not supported by the Mirror's Target.
v VOLUME_BAD_PREFIX
Volume name has a reserved prefix
v VOLUME_BELONGS_TO_MIRRORED_CONS_GROUP
Volume mirror is part of Consistency Group mirror.
v VOLUME_DATA_MIGRATION_UNSYNCHRONIZED
Data Migration has not completed to this volume
v VOLUME_EXISTS
Volume name already exists
v VOLUME_BAD_NAME
Volume name does not exist
v VOLUME_NO_MIRROR
Local volume does not have remote mirroring definitions
v VOLUME_IS_NOT_CONSISTENT_SLAVE
Operation not allowed on slave volume that is not consistent.
v VOLUME_IS_SNAPSHOT
Operation is not permitted on snapshots
v VOLUME_IS_OLVM_PROXY
The volume is in an IBM Hyper-Scale Mobility Proxy phase.
Activating Mirroring
Activates mirroring for a defined mirror coupling.
mirror_activate < vol=VolName | cg=cgName >
Parameters:
Name Type Description Mandatory
vol Object name Master volume. N
cg Object name Master CG name or a
list of master CGs
N
This command activates the coupling - either volumes or Consistency Groups -
and switches it to Active state.
Requirements for a successful command completion:
v The specified target must exist
v The specified target must be mirrored
v The specified target is a volume that does not belong to a Consistency Group, or
a Consistency Group
v The specified target is not a Master
v A Standby state was explicitly set by issuing the mirror_deactivate command on
the same peer
Chapter 11. Remote Mirroring 203
To Next Page
Loading...
Need help?
General
