migratetoimage
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
Parameters
- -vdisk source_vdisk_id | name
- (Required) Specifies the name or ID of the source volume to be migrated.
- -copy id
- (Required if the specified volume has more than one copy) Specifies the volume copy to migrate from.
- -threads number_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.
- -mdisk unmanaged_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.
- -mdiskgrp managed_disk_group_id | name
- (Required) Specifies the storage pool into which the MDisk must be placed, after the migration has completed.
- -tier tier0_flash | tier1_flash | tier_enterprise | tier_nearline | tier_scm
- (Optional) Specifies the tier of the MDisk being added.
- tier0_flash
- Specifies a
tier0_flash
hard disk drive or an external MDisk for the newly discovered or external volume. - tier1_flash
- Specifies an
tier1_flash
(or flash drive) hard disk drive or an external MDisk for the newly discovered or external volume. - tier_enterprise
- Specifies a
tier_enterprise
hard disk drive or an external MDisk for the newly discovered or external volume. - tier_nearline
- Specifies a
tier_nearline
hard disk drive or an external MDisk for the newly discovered or external volume. - tier_scm
- Specifies a
tier_scm
hard disk drive or an external MDisk for the newly discovered or external volume.
Description
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 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.
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.
You cannot specify migratetoimage if the target or source volume is offline. Correct the offline condition before you migrate the volume.
You cannot specify migratetoimage to migrate a thin or compressed volume in a data reduction storage pool to an image mode volume. You must replicate the volume to a standard-provisioned, thin, or compressed volume copy in a standard storage pool before you migrate a thin or compressed volume that is in a data reduction pool from one clustered system to another clustered system.
The new image mode volume copy which is created by the 'migratetoimage' command contains the same capacity savings as the source volume copy. A thin or compressed image mode copy can only be used for importing the volume into another Storage Virtualize system.
To use the new image mode volume copy directly with a host, you must remove any capacity savings from the volume prior to perform the migrate to image mode process.
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 tier_nearline
The resulting output:
No feedback