- 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
Offload copy overhead with XCOPY
To minimize I/O overhead and maximize performance on copy operations, data movement should occur as close to the physical storage layer as possible, rather than at the server layer (as in host-based data copies).
Utilizing VMWare’s XCOPY feature, metro node manages data allocation and placement using virtual machines, copying data with minimal performance impact on the host. When XCOPY is enabled, on-disk data copy and move operations occur on the storage-array, not on the host.
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: <>()\