You can use the command-line interface (CLI) to manage volumes that you created on
the system. To work with volumes in the management GUI, select
Volumes.
Enabling volume protection
To prevent active volumes or host mappings from being deleted inadvertently, the system supports a global setting that prevents these objects from being deleted if the system detects that they had recent I/O activity.
Adding a copy to a volume
You can use the management GUI or command-line interface (CLI) to add a mirrored copy to a volume. Each volume can have a maximum of two copies.
Deleting a copy from a volume
You can use the management GUI or command-line interface (CLI) to delete a copy from a volume.
Expanding volumes using the CLI
You can use the command-line interface (CLI) to expand a volume on Windows, AIX, or Linux systems.
Migrating volumes to an encrypted pool
For systems with encryption enabled, you can migrate existing volumes from non-encrypted pools to encrypted pools. Both the management GUI and the command line interface can be used to migrate volumes to encrypted pools.
Shrinking a volume using the CLI
You can reduce the size of a compressed or uncompressed volume by using the command-line interface (CLI).
Deleting a volume
You can use the command-line interface (CLI) or the management GUI to delete a volume.
Image mode volumes An image mode volume provides a direct block-for-block translation from the managed disk (MDisk) to the volume with no virtualization.
Thin-provisioned volumes When you create a volume, you can designate that it is thin-provisioned to save capacity for the volume. A thin-provisioned volume has different virtual capacity and a real capacity.
Determining the host that a volume maps
You can determine the host that a volume maps by using the command-line interface (CLI). To view the host mapping for a volume in the management GUI, select Volumes > Volumes by Hosts.
Moving a volume between I/O groups using the CLI
To move volumes between I/O groups non-disruptively, ensure that hosts are mapped to the volume, support non-disruptive volume move. The cached data that is held within the system must first be written to the system disk before the allocation of the volume can be changed.
Managing VMware vSphere Virtual Volumes The system supports VMware vSphere Virtual Volumes, sometimes referred to as VVols, which allow VMware vCenter to automate the management of system objects like volumes and pools.
Managing throttles for volumes
You can create, modify, and remove throttles for volumes by using the management GUI or the command-line interface.