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
Table 1. Metavolume display fields
Field Description
active
Indicates whether this volume is the currently active metadata volume. The system has
only one active metadata volume at a time.
application-consistent
Whether this storage-volume is application-consistent.
block-count
The number of blocks in the volume.
capacity
The size of the metavolume.
component-count
The number of mirrors in the RAID 1 metadata volume.
free-slots
The number of free slots for storage-volume headers in this metavolume.
geometry
Indicates the geometry or redundancy of the device. Always RAID 1.
health-indications
If health-state is not ok, additional information.
health-state
● ok - The storage volume is functioning normally.
● degraded - The storage volume may be out-of-date compared to its mirror. (This
state applies only to a storage volume that is part of a RAID 1 metadata volume.)
● unknown - Metro node cannot determine the health state of the storage volume, or
the state is invalid.
● non-recoverable error - The storage volume may be out-of-date compared to
its mirror (applies only to a storage volume that is part of a RAID 1 metadata volume),
and/or metro node cannot determine the health state.
● critical failure - Metro node has marked the storage volume as hardware-dead.
locality
Locality of the supporting device.
● local - The volume is local to the enclosing cluster.
● remote - The volume is made available for a different cluster than the enclosing
cluster, and is accessed remotely.
● distributed - The virtual volume either has legs, or is capable of having legs at
more than one cluster.
operational status
● ok - The storage volume is functioning normally.
● degraded - The storage volume may be out-of-date compared to its mirror. (This
state applies only to a storage volume that is part of a RAID 1 metadata volume.)
● unknown - Metro node cannot determine the health state of the storage volume, or
the state is invalid.
● error - Metro node has marked the storage volume as hardware-dead.
● starting - The storage volume is not yet ready.
● lost-communication - The storage volume is unreachable.
ready
Indicates whether this metadata volume is ready or not.
rebuild-allowed
Whether the device is allowed to rebuild.
rebuild-eta
If a rebuild is in progress, the estimated time remaining for the current rebuild to complete.
rebuild-progress
If a rebuild is in progress, the percentage of the device that has been rebuilt.
rebuild-status
The rebuild status of the device. done - Rebuild is complete.
rebuild-type
The rebuild type.
● full - A full copy of all the blocks. A metavolume rebuild is always full.
● incremental - An incremental copy uses a checksum differencing algorithm to
transfer only those blocks that are different.
● comparison - A comparison copy.
● resync - A resync rewrites blocks affected by a director failure, guaranteeing that the
mirror legs are identical.
slots
The total number of slots for storage-volume headers in the metavolume.
stripe-depth
The depth of a stripe in bytes when geometry is RAID-0.
Meta Volumes 13