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
The steps to perform a batch migration are generally the same as those described in the General procedure to perform data
migration.
There are two additional steps to prepare for a batch migration:
1. Create a batch migration plan file (using the batch-migrate create-plan command)
2. Test the batch migration plan file (using the batch-migrate check-plan command)
Prerequisites
The following prerequisites are required for batch migrations:
● The source and targets are both devices.
● Local devices must be configured (device migrations) on the target array.
● The structure of the target is the same as the structure of the source.
Creating a batch migration plan
The batch-migrate create-plan command creates a migration plan using the specified sources and targets.
About this task
In the following example, the batch-migrate create-plan command creates a batch migration named ‘MigDev-test.txt’
to:
● Migrate two devices at cluster-1 to two devices at cluster-2.
● Overwrite an existing plan with the same name.
VPlexcli:/> batch-migrate create-plan --file MigDev-test.txt --sources
/clusters/cluster-1/devices/base0,/clusters/cluster-1/devices/base1 --targets /
clusters/cluster-2/devices/dev1723_618, /clusters/cluster-2/devices/dev1723_61C --
force
Extents matching source pattern: base0, base1
Extents matching target pattern: dev1723_61C, dev1723_618
Creating file /var/log/VPlex/cli/MigDev-test.txt as migration plan file.
Wrote file /var/log/VPlex/cli/MigDev-test.txt. Please review and edit this file, and
run this command in the check-plan phase afterward.
In the following example, the batch-migrate create-plan command creates a batch migration to migrate all devices at
cluster-1 to cluster-2.
VPlexcli:/> batch-migrate create-plan migrate.txt --sources /clusters/cluster-1/
devices/* --targets /clusters/cluster-2/devices/*
Checking a batch migration plan
The batch-migrate check-plan command checks the specified batch migration plan for the following:
About this task
● Device migrations:
○ Target device has no volumes on it
○ Source device has volumes on it
If the migration plan contains errors, a description of the errors is displayed, and the plan check fails. For example:
VPlexcli:/> batch-migrate check-plan --file MigDev-test.txt
Checking migration plan file /var/log/VPlex/cli/MigDev-test.txt.
Target device '/clusters/cluster-2/devices/dev1723_61C' has a volume.
Target device '/clusters/cluster-2/devices/dev1723_618' has a volume.
Plan-check failed, 2 problems.
Use the steps described in Modifying a batch migration file to correct the plan.
Data migration
47