IBM XIV - Changing a Mirroring Schedule for Local Peers

User Category Permission
Application administrator Disallowed
Security administrator Disallowed
Read-only users Disallowed
Technicians Disallowed
Completion Codes:
v VOLUME_BAD_NAME
Volume name does not exist
v CONS_GROUP_NO_MIRROR
Local Consistency Group does not have remote mirroring definitions
v ASYNC_MIRROR_REMOTE_RPO_TOO_SHORT
Specified Remote RPO is too short.
v ASYNC_MIRROR_RPO_TOO_LONG
Specified RPO is too long.
v TARGET_NOT_CONNECTED
There is currently no connection to the target system
v VOLUME_NO_MIRROR
Local volume does not have remote mirroring definitions
v CONS_GROUP_BAD_NAME
Consistency Group name does not exist.
v ASYNC_MIRROR_RPO_TOO_SHORT
Specified RPO is too short.
v VOLUME_BELONGS_TO_MIRRORED_CONS_GROUP
Volume mirror is part of Consistency Group mirror.
v INTERVAL_SHOULD_BE_SHORTER_THAN_RPO
Schedule interval must me shorter that RPO.
The newly defined schedule has to be shorther than the RPO.
v ASYNC_MIRROR_REMOTE_RPO_TOO_LONG
Specified Remote RPO is too long.
v LOCAL_IS_SLAVE
Local mirror peer is not the master
v SYNC_MIRROR_HAS_NO_RPO
Synchronous Mirror does not have an RPO.
Changing a the Mirroring Peers' Designation
Changes the designation of mirroring peers - from Primary to Secondary, and from
Secondary to Primary.
mirror_change_designation < vol=VolName | cg=cgName >
[ new_designation=<Primary|Secondary|None> ]
206 IBM XIV Storage System User Manual