Use the migratetoimage command
to migrate data from a volume (image mode or managed mode) onto a
new image mode volume copy. The target disk does not have to be in
the same storage pool as the source disk.
Syntax
migratetoimage [ -copyid ] -vdisk { source_vdisk_id | source_vdisk_name } [ -threadsnumber_of_threads ] -mdisk { unmanaged_target_mdisk_id | unmanaged_target_mdisk_name } [ -tier { ssd | enterprise | nearline } ] -mdiskgrp { managed_disk_group_id | managed_disk_group_name }
Parameters
- -vdisksource_vdisk_id |
name
- (Required) Specifies the name or ID of the source volume to be
migrated.
- -copyid
- (Required if the specified volume has more than one copy)
Specifies the volume copy to migrate from.
- -threadsnumber_of_threads
- (Optional) Specifies the number of threads to use during the
migration of extents. You can specify 1 - 4 threads. The default
number of threads is 4.
- -mdiskunmanaged_target_mdisk_id
| name
- (Required) Specifies the name of the MDisk to which the data must
be migrated. This disk must be unmanaged and large enough to contain
the data of the disk that is being migrated.
- -mdiskgrpmanaged_disk_group_id
| name
- (Required) Specifies the storage pool into which the MDisk must
be placed, after the migration has completed.
- -tierssd | enterprise
| nearline
- (Optional) Specifies the tier of the MDisk being added.
- ssd
- Specifies an SSD (or flash drive) hard disk drive or an external MDisk for the newly discovered
or external volume.
- nearline
- Specifies an nearline hard disk drive or an external MDisk for the newly discovered or external
volume.
- enterprise
- Specifies an enterprise hard disk drive or an external MDisk for the newly discovered or
external volume.
Description
The
migratetoimage command migrates
the data of a user-specified volume by consolidating its extents (which
might reside on one or more MDisks) onto the extents of the target
MDisk that you specify. After migration is complete, the volume is
classified as an image type volume, and the corresponding mdisk is
classified as an image mode MDisk.
Remember: This command cannot
be used to if the source volume copy is in a child pool or if the
MDisk group that is specified is a child pool.
This command does not work if the
volume is fast formatting.
The managed disk that is specified
as the target must be in an unmanaged state at the time that the command
is run. Running this command results in the inclusion of the MDisk
into the user-specified storage pool.
The migratetoimage command
fails if the target or source volume is offline. Correct the offline
condition before attempting to migrate the volume.
Remember: This command cannot be used on a volume owned by a
filesystem or if the source MDisk is an SAS MDisk (which works in
image mode only)..
If the volume (or
volume copy) is a target of a FlashCopy mapping
with a source volume in an active-active relationship
the new managed disk group must be in the same site as the source
volume. If the volume is in an active-active relationship
the new managed disk group must be located in the same site as the
source volume. Additionally, the site information for the MDisk being
added must be well-defined and match the site information for other
MDisks in the storage pool.
Note: You cannot migrate date from
a volume if the target volume's formatting attribute value is yes.
An
encryption key cannot be used when migrating an image mode MDisk.
To use encryption (when the MDisk has an encryption key), the MDisk
must be self-encrypting.
An
invocation example
The
following example specifies
that the user wants to migrate the data from
vdisk0 onto
mdisk5 and
that
the MDisk must be put into the storage pool
mdgrp2.
migratetoimage -vdisk vdisk0 -mdisk mdisk5 -mdiskgrp mdgrp2 -tier nearline
The
resulting output:
No feedback