These two last_replicated snapshots are different and denoted" master" and "slave"
accordingly.
The outcome for the synchronous mirroring:
v The Master blocks host I/O for the duration of creating the snapshots
v The Master completes synchronizing pending writes
v A snapshot of the Master and Slave is taken
v The Master no longer blocks host I/O
v An event is generated
Access Control:
User Category Permission Condition
Storage administrator Allowed N/A
Storage integration administrator Allowed N/A
Application administrator Conditionally Allowed The volume is mapped to a host
or a cluster associated with the
user. If a snapshot overwrite is
used, the target snapshot must
be one created by a server
administrator.
Security administrator Disallowed N/A
Read-only users Disallowed N/A
Technicians Disallowed N/A
Completion Codes:
v CONS_GROUP_MISMATCH
Snapshot Group does not match Consistency Group volumes.
v CONS_GROUP_EMPTY
Operation is not allowed on an empty Consistency Group.
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 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_NON_OPERATIONAL
Mirror is non-operational
v MAX_VOLUMES_REACHED
Maximum number of volumes already defined
v OPERATION_NOT_ALLOWED_ON_LOOPBACK
Requested operation is not allowed on loopback target
Chapter 11. Remote Mirroring 201