Administrator Guide
Table Of Contents
- Dell EMC Storage Systems Administrator Guide for PowerStore and Unity XT metro node feature
- CLI Workspace and User Accounts
- Meta Volumes
- System Management
- Thin support in metro node
- Provisioning Storage
- Volume expansion
- Data migration
- About data migrations
- Migrating thin-capable storage
- About rebuilds
- One-time data migrations
- Batch migrations
- Prerequisites
- Creating a batch migration plan
- Checking a batch migration plan
- Modifying a batch migration file
- Starting a batch migration
- Pausing/resuming a batch migration (optional)
- Canceling a batch migration (optional)
- Monitoring a batch migration’s progress
- Viewing a batch migration’s status
- Committing a batch migration
- Cleaning a batch migration
- Removing batch migration records
- Configure the WAN Network
- Consistency Groups
- Performance and Monitoring
- Metro node with active-passive storage arrays
- Index
Contexts:
advanced recoverpoint
You might notice rebuilding-across-clusters in operational status while devices are rebuilding.
Setting the read-only attribute
SRDF R2 devices (replicas) are an example of an array-managed Business Continuance Volume (BCV). For consistency groups
that contain these volumes, you can use the set command to set the consistency group to read-only.
About this task
If the read-only attribute is true, the system prevents write operations to virtual volumes in the consistency group. Virtual
volumes in a read-only consistency group must be local, and you must map each virtual volume one-to-one to a single storage
volume (for example, local RAID 0 with no slicing).
You cannot add virtual volumes with an invalid topology to a read-only consistency group. The consistency-group add-
virtual-volumes command fails. If you set a consistency group to read-only and that consistency group already contains
virtual volumes with an invalid topology, the set read-only true command fails.
A consistency group cannot be read-only and recoverpoint-enabled at the same time, since the two properties are
incompatible.
Steps
Use the set command to set the consistency group to read-only.
VPlexcli:/> cd/clusters/cluster-1/consistency-groups/test
VPlexcli:/clusters/cluster-1/consistency-groups/test>set read-only true
VPlexcli:/clusters/cluster-1/consistency-groups>ll
Name Operational Active Passive Detach Rule Cache Mode Read
------ Status Clusters Clusters ---------- --------- Only
------- ----------- ------- -------- ---------- --------- ----
DB2_app (Hopkinton,{ winner Hopkinton after 5s synchronous true
summary:: ok,
details:: []
}),
Providence, {
summary:: ok,
details:: []
})
80
Consistency Groups