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
● In a thin to thick extent migration (with no supported virtual-volumes), the metro node CLI displays a warning stating that
the source loses its thin-capability after migration.
VPlexcli:/> batch-migrate create-plan --file migration.txt --sources extent_thin_1,
extent_thin_2
--targets extent_thick_1, extent_thick_2
Extents matching source pattern: extent_thin_1, extent_thin_2
Extents matching target pattern: extent_thick_2, extent_thick_1
Creating file /var/log/VPlex/cli/migration.txt as migration plan file.
Wrote file /var/log/VPlex/cli/migration.txt. Please review and edit this file, and
run this command
in the check-plan phase afterward.
VPlexcli:/> batch-migrate check-plan --file /var/log/VPlex/cli/migration.txt
Checking migration plan file /var/log/VPlex/cli/migration.txt.
WARNING: The source 'device_thin_1' is thin-capable but the target 'device_thick_1'
is not thin-capable.
Thin-capability will be lost after migration.
WARNING: The source 'device_thin_2' is thin-capable but the target 'device_thick_2'
is not thin-capable.
Thin-capability will be lost after migration.
Plan-check passed with 2 warnings.
VPlexcli:/>
● For multiple thin-to-thick migrations, the metro node CLI reports the migration problems with multiple warnings. The
following example shows two thin-to-thick migrations, where one migration does not have virtual volumes.
VPlexcli:/> batch-migrate check-plan --file /var/log/VPlex/cli/migration.txt
Checking migration plan file /var/log/VPlex/cli/migration.txt.
WARNING: The source 'device_thin_1' is thin-capable but the target 'device_thick_1'
is not thin-capable.
The virtual-volume 'thin_1' will not be thin-enabled or thin-capable after migration.
PROBLEM: Source device '/clusters/cluster-1/devices/device_thin_2' does not have a
volume.
WARNING: The source 'device_thin_2' is thin-capable but the target 'device_thick_2'
is not thin-capable.
Thin-capability will be lost after migration.
Plan-check failed with 1 problem and 2 warnings.
● In a simultaneous thin to thick and thick to thin device migration, the virtual volume is not thin-capable or thin-enabled after
the batch migration is committed.
Table 6. Simultaneous thin to thick and thick to thin migration
Migration Source Target Volume
BR0_0 device_thick_4 device_thin_4 source_thick
BR0_1 device_thin_5 device_thick_3 source_thin
VPlexcli:/> batch-migrate commit --file /var/log/VPlex/cli/migrate.txt
The virtual-volume 'source_thin' is no longer thin-capable and will not be thin-
enabled after
migration 'BR0_1' is committed.
Committed 2 of 2 migrations
VPlexcli:/>
Data migration
41