Use the migratevdisk command to migrate an entire volume from one
storage pool to another storage pool.
Syntax
migratevdisk -mdiskgrp { mdisk_group_id | mdisk_group_name } [ -threads number_of_threads ] [ -copy id ] -vdisk { vdisk_id | vdisk_name }
Parameters
- -mdiskgrpmdisk_group_id | mdisk_group_name
- (Required) Specifies the new storage pool ID or name.
- -threadsnumber_of_threads
- (Optional) Specifies the number of threads to use during the migration of these
extents. You can specify 1 - 4 threads. The default number of threads is 4.
- -copyid
- (Required if the specified volume has more than one copy) Specifies the volume copy to
migrate.
- -vdiskvdisk_id | vdisk_name
- (Required) Specifies the volume ID or name to migrate in to a new storage pool.
Note: The command cannot be used with image-mode
volumes.
Description
The
migratevdisk command migrates the specified volume into a new storage pool;
all the extents that make up the volume are migrated onto free extents in the new storage
pool.
You can reassign a volume from a:
- Child pool to its parent pool
- Parent pool to one of its child pools
- Between the child pools in the same parent pool
- Between two parent pools
Note: You cannot migrate a volume between storage pools
if cloud snapshot is enabled on the volume.
You can issue the
lsmigrate command to view the progress of the migration.
The process
can be prioritized by specifying the number of threads to use during the migration. Using only
one thread puts the least background load on the system.
The
migratevdisk command fails if there are insufficient free extents on the
targeted storage pool for the duration of the command. To avoid this problem, do not issue new
commands that use extents until the volume migration is completed.
The migratevdisk command fails if the target volume or source volume is
offline. Correct the offline condition before you attempt to migrate the volume.
Remember: You cannot specify this command:
- For volumes that are owned by a file system.
- If the source MDisk is an SAS MDisk (which works in image mode only).
- If the volume that is being migrated is thin-provisioned or
compressed and in a data reduction pool.
- If the target pool is a data reduction pool and the volume that
is being migrated is either thin-provisioned or compressed.
For these volume types, you must create a volume copy in the destination pool by using
volume mirroring to perform the migration. For more information, see the
addvdiskcopy or addvolumecopy command.
If the volume (or volume copy) is a
target of a FlashCopy mapping with a source volume
in an active-active, relationship the new storage pool must be in the same site
as the source volume. If the volume is in an active-active relationship, the
new storage pool must be located in the same site as the source volume.
When the volume is being migrated
from a parent pool to another parent pool, the information is moved (unchanged), whether or not
one or other is encrypted. The parent pool and the child pool cannot have an encryption key (or
else the child pool would have failed during creation).
- A parent pool to parent pool migration is allowed in all cases.
- A parent pool to child pool migration is not allowed if child has encryption key.
- A child pool to parent pool or child pool is not allowed if either child pool has an
encryption key.
An invocation
example
migratevdisk -vdisk 4 -mdiskgrp Group0 -threads 2
The
resulting output:
No feedback