- Notes, cautions, and warnings
- Preface
- CLI Workspace and User Accounts
- Meta Volumes
- System Management
- About call-home notifications
- Additional documentation
- SupportAssist MFT feature
- Event log locations
- System Configuration log location
- Hardware acceleration with VAAI
- Offload copy overhead with XCOPY
- Renaming a metro node cluster
- LCD Front Panel settings
- 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
Dell EMC Metro node 7.0.1 Administrator Guide
Limitations with storage-volume expansion
The following limitations apply to the storage volume expansion method:
- For virtual volumes built on RAID 1 or distributed RAID 1 devices, a maximum of 1000 initialization processes can run concurrently per cluster. If this limit is reached on a cluster, then no new expansions can be started on virtual volumes with these geometries until some of the previously started initialization processes finish on that cluster.
Virtual volumes that do not contain RAID 1 or distributed RAID 1 devices are not affected by this limitation.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\