It is only represented as an  image-type volume  after it reaches the state where it is a  straight-through mapping. An image-type volume cannot be expanded. Image-type  disks are used to migrate existing data to an IBM FlashSystem 9100 and to  migrate data out of virtualization. In general, the reason for migrating a volume to an image  type volume is to move the data on the disk to a non virtualized environment. If the migration is interrupted by a cluster recovery, the migration resumes after the recovery  completes. The  migratetoimage  command migrates the data of a user-specified volume by consolidating  its extents (which might be 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. Remember:  This command cannot be used if the source volume copy is in a child pool or  if the target MDisk group that is specified is a child pool. This command does not work if  the volume is fast formatting. The  migratetoimage  command fails if the target or source volume is offline. Correct the offline  condition before attempting to migrate the volume. 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 a volume or volume image between storage pools if cloud  snapshot is enabled on the volume. 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 before  configuring storage pool. The  migratetoimage  command is useful when you want to use your system as a  data mover .  To better understand all requirements and specifications for that command, see IBM  Knowledge Center. If you want to migrate volumes to DRP, you can move them with volume mirroring between  standard pool and DRP. Hosts I/O operations are not disrupted during migration. It is not  supported to change from standard pool to DRP without disruption. Figure 5-14 on page 127  shows volume mirroring migration to change pool types and volume types. 5.8.3 Migration from Standard Pool to Data Reduction Pool 126  IBM FlashSystem 9200 and 9100 Best Practices and Performance Guidelines