parent_mdisk_grp_name Pool1 encrypt yes deduplicated_copy no used_capacity_before_reduction 0.00MB IBM_Storwize:ITSO:superuser>chvdisk -name VOL_WITH_MIRROR VOL_NO_MIRROR IBM_Storwize:ITSO:superuser> IBM_Storwize:ITSO:superuser>lsvdisk UNCOMPRESSED_VOL id 9 name UNCOMPRESSED_VOL IO_group_id 0 IO_group_name io_grp0 status online ... copy_id 0 status online sync yes auto_delete no primary yes ... compressed_copy no ... IBM_Storwize:ITSO:superuser>addvdiskcopy -autodelete -rsize 2 -mdiskgrp 0 -compressed  UNCOMPRESSED_VOL Vdisk [9] copy [1] successfully created When you add a volume copy, you can define it with parameters that differ from the original  volume copy. For example, you can create a thin-provisioned copy of a fully allocated volume  to migrate a thick-provisioned volume to a thin-provisioned volume. The migration can be also  done in the opposite direction. Volume copy mirror parameters:  To change the parameters of a volume copy, you must  delete the volume copy and redefine it with the new values. If your volume naming convention demands it, you can change the name of the volume. In  Example 7-11 volume name is changed from  VOL_NO_MIRROR  to  VOL_WITH_MIRROR . This section shows the use of  addvdiskcopy  with the  -autodelete  flag set. The  -autodelete flag causes the primary copy to be deleted after the secondary copy is synchronized. Example 7-12 shows a shortened  lsvdisk  output for an uncompressed volume with a single  volume copy. Example 7-13 adds a compressed copy with the  -autodelete  flag set. Example 7-14 on page 323 shows the  lsvdisk  output with an additional compressed volume  (copy 1) and volume copy 0 being set to  auto_delete yes . 322  Implementing the IBM System Storage SAN Volume Controller with IBM Spectrum Virtualize V8.2.1 Example 7-11 Volume name changes Example 7-12 An uncompressed volume Example 7-13 Compressed copy Using the -autodelete flag to migrate a volume