Use appliance storage object migration to move storage resources to another appliance or multiple appliances in the cluster. This feature is applicable if you want to evacuate space from an appliance, power off an appliance, or remove an appliance from a cluster.
About this task
Volumes, volume groups, and vVols are eligible for migration. When you migrate a storage object, all associated snapshots and thin clones are also migrated.
The following storage objects are not eligible for migration:
Table 1. Storage objects ineligible for migrationStorage objects that are not eligible for migration
Ineligible object
How to make the object eligible
File objects
File objects cannot be migrated.
Volumes or volume groups in an active import session
Wait for the import session to end.
Volumes, volume groups, or vVols in an active internal migration
If the system is migrating objects from the appliance, wait for the migration to end. If the system is migrating objects to the appliance, consider canceling the migration.
Offline volumes
The volume is offline due to metadata inconsistencies. Contact your service provider to bring it online.
vVols with bound snapshots
Interrupt the VMware operation that created the bound snapshot or wait for the process to complete.
vVol bound fast clones
Power off the linked clones of the VM that the vVol belongs to.
You cannot migrate storage objects from an appliance that is out of space and has entered read-only mode. If an appliance is out of space, you must add more storage capacity or delete storage objects until the appliance has at least 16 GB of free space.
To migrate storage objects to another appliance in the cluster:
Steps
Under
Hardware, select the appliance from which you want to migrate storage objects.
Under
More Actions, select
Migrate.
Follow the prompts in the
Migration wizard to migrate storage objects to another appliance.
NOTE:The maximum number of storage objects that you can select for a single migration action is 4000.
Results
The LUN ID of a volume changes automatically when a volume is migrated from one
PowerStore appliance to another appliance in the same cluster.
Follow these guidelines when migrating a boot volume:
Power off the connected host before migrating the boot volume. Then, change the LUN ID for the boot volume after the migration is performed and power on the host.
The recommend Host LUN ID for a boot LUN is 0.
After migrating a boot from SAN volume, the LUN ID can be changed back to 0.
NOTE:For instructions on changing the LUN, see the
PowerStore Host Configuration Guide.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\