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
Pausing/resuming a migration (optional)
Active migrations (a migration that has been started) can be paused and then resumed at a later time.
About this task
Pause an active migration to release bandwidth for host I/O during periods of peak traffic.
Use the dm migration pause --migrations command to pause a migration.
Specify the migration-name by name if that name is unique in the global namespace. Otherwise, specify a full pathname.
For example:
● Pause a device migration:
VPlexcli:/data-migrations/device-migrations> dm migration pause --migrations
migrate_012
Use the dm migration resume --migrations command to resume a paused migration.
Specify the migration-name by name if that name is unique in the global namespace. Otherwise, specify a full pathname.
For example:
● Resume a paused device migration:
VPlexcli:/data-migrations/device-migrations> dm migration resume --migrations
migrate_012
Canceling a migration (optional)
Migrations can be canceled in the following circumstances:
About this task
● The migration is in progress or paused. The migration is stopped, and any resources it was using are freed.
● The migration has not been committed. The source and target devices are returned to their pre-migration state.
Use the dm migration cancel --force --migrations command to cancel a migration.
Specify the migration-name by name if that name is unique in the global namespace. Otherwise, specify a full pathname.
For example:
VPlexcli:/data-migrations/device-migrations> dm migration cancel --force --migrations
migrate_012
Committing a completed migration
The migration process inserts a temporary RAID 1 structure above the source device with the target as an out-of-date leg of the
RAID 1. The migration can be understood as the synchronization of the out-of-date leg (the target).
About this task
After the migration is complete, the commit step detaches the source leg of the RAID 1, and removes the RAID 1.
The virtual volume, or device is identical to the one before the migration except that the source device is replaced with the
target device.
A migration must be committed to be cleaned.
CAUTION: Verify that the migration has completed successfully before committing the migration.
Use the dm migrations commit --force --migrations migration-name command to commit a migration.
Data migration
45