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
NOTE: You must use the --force option to commit a migration.
For example:
● Commit a device migration:
VPlexcli:/data-migrations/device-migrations> dm migration commit --force --migrations
migrate_012
Committed 1 data migration(s) out of 1 requested migration(s).
Cleaning a migration
For device migrations, cleaning dismantles the source device down to its storage volumes. The storage volumes that are no
longer in use are unclaimed.
For device migrations only, use the --rename-target argument to rename the target device after the source device. If the
target device is renamed, the virtual volume on top of it is also renamed if the virtual volume has a system-assigned default
name.
Without renaming, the target devices retain their target names, which can make the relationship between volume and device
less evident.
Use the dm migration clean --force --migrations migration-name command to clean 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 clean --force --migrations
migrate_012
Cleaned 1 data migration(s) out of 1 requested migration(s).
Removing migration records
About this task
NOTE: Migrations must be canceled or committed before they can be removed.
Use the dm migration remove --force --migrations migration-name command to remove the records of the
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 remove --force --migrations
migrate_012
Removed 1 data migration(s) out of 1 requested migration(s).
Batch migrations
Batch migrations are run as batch jobs from reusable batch migration plan files. Migration plan files are created using the
create-plan command.
A single batch migration plan can be for devices.
NOTE: Migrations consume cache resources. Running multiple migrations concurrently may impact host I/O.
Use batch migrations to:
● Retire storage arrays (off-lease arrays) and bring new ones online.
● Migrate devices to a different class of storage array.
46
Data migration