IBM XIV User Manual

v MIRROR_CAN_NOT_BE_ACTIVATED
Mirroring cannot be activated because state cannot be established
Troubleshooting: Delete and recreate mirror
v MIRROR_CONS_GROUP_MEMBERSHIP_MISMATCH
Mirrored CG contains different volumes on Master and Slave. This problem
occurs whenever the cg_add_vol or cg_remove_vol commands were previously
issued and the Master did not receive an acknowledgment from the Slave until
the command timed out, or any other unexpected failure.
v MIRROR_SIZE_MISMATCH
Slave volume and Master Volume sizes are different
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
Changing the RPO for Local/Remote System
Changing Local/Remote RPO for a mirror relation
mirror_change_rpo <vol=VolName | cg=cgName> [ rpo=rpo ] [ remote_rpo=rpo ]
Parameters:
Name Type Description Mandatory Default
vol Object name Local volume
name.
Must be specified
if the command
concerns a volume.
N N/A
cg Object name CG name on the
local system
N N/A
remote_rpo Integer RPO on remote
system
N [Unchanged]
rpo Integer RPO on local
system
N [Unchanged]
This command changes the Local/Remote RPO for a mirror.
v The command must be run on the Master.
v The RPO must be greater than the interval.
v The link has to be up.
Example:
mirror_change_rpo vol=volname rpo=100
Access Control:
User Category Permission
Storage administrator Allowed
Storage integration administrator Allowed
Chapter 11. Remote Mirroring
205

IBM XIV Specifications

General

Power Supply	Redundant power supplies
Drive Type	SATA
Redundancy	Fully redundant components
Connectivity	Fibre Channel, iSCSI
Form Factor	Rack-mounted
Cache	Distributed cache across modules
Data Protection	Snapshots, remote mirroring
Performance	High throughput and low latency
Scalability	Modular, scale-out architecture
Cooling	Redundant cooling
Architecture	Grid-based, distributed architecture