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
Steps
1. Use the batch-migrate summary command to verify that the migration has completed with no errors.
2. Use the batch-migrate commit --file command to commit the migration.
WARNING: Commit permanently removes the volumes from the source devices.
For example:
VPlexcli:/> batch-migrate commit --file migrate.txt
Cleaning a batch 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.
About this task
For device migrations only, use the optional --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 batch-migrate clean --file command to clean the specified batch migration.
CAUTION:
This command must be run before the batch-migration has been removed. The command will not
clean migrations that have no record in the VPlexcli context tree.
In the following example, source devices are torn down to their storage volumes and the target devices and volumes are
renamed after the source device names
VPlexcli:/> batch-migrate clean --rename-targets --file migrate.txt
Using migration plan file /temp/migration_plans/migrate.txt for cleanup phase.
0: Deleted source extent /clusters/cluster-1/devices/R20061115_Symm2264_010, unclaimed
its disks Symm2264_010
1: Deleted source extent /clusters/cluster-1/extents/R20061115_Symm2264_011, unclaimed
its disks Symm2264_011
2: Deleted source extent /clusters/cluster-1/extents/R20061115_Symm2264_012, unclaimed
its disks Symm2264_012
3: Deleted source extent /clusters/cluster-1/extents/R20061115_Symm2264_013, unclaimed
its disks Symm2264_013
Removing batch migration records
Remove the migration record only if the migration has been committed or canceled.
About this task
Migration records are in the /data-migrations/device-migrations context.
Use the batch-migrate remove --file command to remove records for the specified migration.
For example:
VPlexcli:/data-migrations/device-migrations> batch-migrate remove --file migrate.txt
or:
VPlexcli:> batch-migrate remove /data-migrations/device-migrations --file migrate.txt.
Data migration
51