IBM XIV STORAGE SYSTEM, Руководство пользователя

Страница: 91 / 652

– If the Consistency Group is mirrored, the mirroring definition of the removed
volume is retained. The mirroring definition is based on the same settings as
the Consistency Group.
v
The peer volume is also removed from the peer Consistency Group
v
The removed mirrored volume is set the RPO of the mirrored Consistency
Group from which it was removed
v
Event is generated
This command succeeds even if the volume is not included in any Consistency
Group.
Requirements for a successful command completion:
v
The command can be issued only on the master
v
The link must be up
v
The Consistency Group cannot have ongoing sync jobs
In case of acknowledgment time-out:
v
Whenever the command is issued on a mirrored CG Master - and the Master
does not receive an acknowledgment from the Slave (until the command timed
out or due to any unexpected failure), a completion code is returned
(MIRROR_POSSIBLE_CONS_GROUP_MEMBERSHIP_MISMATCH).
If applied on a volume that is part of an IBM Hyper-Scale Mobility relation:
v
The command is applicable only to a destination volume
v
This destination volume must be in Proxy state
Otherwise, a completion code is returned.
Example:
cg_remove_vol vol=DBLog
Output:
Command completed successfully
Access Control:
User Category Permission
Storage administrator Allowed
Storage integration administrator Allowed
Application administrator Disallowed
Security administrator Disallowed
Read-only users Disallowed
Technicians Disallowed
Warnings:
v
ARE_YOU_SURE_YOU_WANT_TO_REMOVE_VOLUME_FROM_
CONS_GROUP
Are you sure you want to remove volume '
Volume ' from its Consistency Group?
Chapter 6. Consistency Group Management
85