Administrator Guide

● Bei einer Extentmigration von Thin zu Thick (ohne unterstützte virtuelle Volumes) zeigt die VPlexcli eine Warnung an, die besagt, dass
die Quelle nach der Migration ihre Thin-Fähigkeit verliert.
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:/>
● Für mehrere Thin-zu-Thick-Migrationen werden in der VPlexcli die Migrationsprobleme mit mehreren Warnungen gemeldet. Das
folgende Beispiel zeigt zwei Thin-to-Thick-Migrationen, bei denen eine Migration keine virtuellen Volumes hat.
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.
● Bei einer gleichzeitigen Gerätemigration von Thin zu Thick und Thick zu Thin ist das virtuelle Volume nach dem Aktivieren der
Batchmigration weder „thin-capable“ noch „thin-enabled“.
Tabelle 7. Gleichzeitige Thin-zu-Thick- und Thick-to-Thin-Migration
Migration Quelle Ziel -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:/>
48
Datenmigration