Administrator Guide

cause: Operation was halted by the user
VPlexcli:/clusters/cluster-1/storage-elements/extents>
● In a thin to thick extent migration (no supported virtual volume), if the source is thin-capable and the target is not
thin-capable, the source loses its thin-capability after migration.
VPlexcli:/clusters/cluster-1/storage-elements/extents> dm migration start --paused --
name my_migration
--from thin_extent_2 --to thick_extent_1
The source 'thin_extent_2' is thin-capable but the target 'thick_extent_1' is not
thin-capable.
Thin-capability will be lost after migration. Do you wish to proceed? (Yes/No) no
dm migration start: Evaluation of <<dm migration start --paused --name my_migration
--from extent_21
--to extent_31>> failed.
cause: Failed to create a new data-migration.
cause: Operation was halted by the user
VPlexcli:/clusters/cluster-1/storage-elements/extents>
Consider the following when committing one time migrations:
● In a thin to thick device migration, the metro node CLI displays a message stating that the virtual volume's thin-properties
are disabled.
VPlexcli:/data-migrations/extent-migrations> dm migration commit my_migration --force
The virtual-volume 'my_vol' is no longer thin-capable and will not be thin-enabled
after
migration 'my_migration' is committed.
Committed 1 data migration(s) out of 1 requested migration(s).
VPlexcli:/data-migrations/extent-migrations>
● In a thin to thin extent or device migration (with supported virtual-volume), if the thin-enabled value is set to false, there is
no change after the migration is committed.
VPlexcli:/data-migrations/extent-migrations> dm migration commit my_migration2 --force
Committed 1 data migration(s) out of 1 requested migration(s).
VPlexcli:/data-migrations/extent-migrations>
● In a thin to thin device migration (with supported virtual volume), if the thin-enabled value is set to true, the virtual volume
remains thin-enabled after the migration is committed.
Consider the following when running and committing batch migrations:
● In a thin to thick device or extent migration, during the check-plan phase, the metro node CLI displays a warning stating that
the virtual volumes are not thin-capable or thin-enabled after migration.
VPlexcli:/> batch-migrate create-plan --file migration.txt --sources device_thin_1,
device_thin_2
--targets device_thick_1, device_thick_2
Extents matching source pattern: device_thin_1, device_thin_2
Extents matching target pattern: device_thick_2, device_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.
The virtual-volume 'thin_1' will not be thin-enabled or thin-capable after migration.
WARNING: The source 'device_thin_2' is thin-capable but the target 'device_thick_2'
is not thin-capable.
The virtual-volume 'thin_2' will not be thin-enabled or thin-capable after migration.
Plan-check passed with 2 warnings.
VPlexcli:/>
40
Data migration