Administrator Guide
Table Of Contents
- Dell EMC Storage Systems Administrator Guide for the metro node appliance
- Contents
- Preface
- 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
- Cluster Witness
- Consistency Groups
- Performance and Monitoring
- Metro node with active-passive storage arrays
Attributes:
Name Value
------------------- ----------------------------------------------------------
active-clusters [cluster-1, cluster-2]
cache-mode synchronous
detach-rule no-automatic-winner
operational-status [(cluster-1,{ summary:: ok, details:: [] }),
(cluster-2,{ summary:: ok, details:: [] })]
passive-clusters []
recoverpoint-enabled false
storage-at-clusters [cluster-1, cluster-2]
virtual-volumes [dd1_vol, dd2_vol]
visibility [cluster-1, cluster-2]
Contexts:
advanced recoverpoint
Table 12. Consistency group field descriptions
Property Description
Standard properties
cache mode
synchronous (default) - Writes are done synchronously. Writes are not
acknowledged to a host unless they have been sent to back-end storage at all
clusters.
detach-rule
Policy for automatically picking a winning cluster when there is an inter-cluster
link outage. A winning cluster is intended to resume I/O operations when the link
fails.
● no-automatic-winner - The consistency group does not select a winning
cluster.
● winner - The cluster specified by cluster-name will be declared the winner if
an inter-cluster link outage lasts more than the number of seconds specified
by delay.
storage-at-clusters
The cluster where the physical storage associated with a consistency group is
located.
● Modifiable using the set command. If cluster names are cluster-1 and
cluster-2 valid values are:
○ cluster-1 - Storage associated with this consistency group is located
only at cluster-1.
○ cluster-2 - Storage associated with this consistency group is located
only at cluster-2.
○ cluster-1,cluster-2 - Storage associated with this consistency
group is located at both cluster-1 and cluster-2.
● When modified, the new value cannot be incompatible with the volumes that
are already in the consistency group. Change storage-at-clusters only
when the consistency group has no member volumes.
visibility
Lists the clusters at which this consistency group is visible.
● Modifiable using the set command. If cluster names are cluster-1 and
cluster-2 valid values are:
○ cluster-1 - This consistency group is visible only at cluster-1.
○ cluster-2 - This consistency group is visible only at cluster-2.
○ cluster-1,cluster-2 - This consistency group is visible at both
cluster-1 and cluster-2.
● Changing this property changes where the consistency group is visible, and
may cause contexts to appear or disappear in the context tree.
virtual-volume
Lists the virtual volumes that are members of the consistency group. Modifiable
using the following commands:
● consistency-group add-virtual-volumes - Add one or more virtual
volumes to a consistency group.
● consistency-group remove-virtual-volumes - Remove one or
more virtual volumes from a consistency group.
Consistency Groups 79