- Notes, cautions, and warnings
- Additional Resources
- Volumes
- Volume groups overview
- Hosts and host group configurations
- Data mobility for volumes and volume groups
- Thin clones
- Quality of Service (QoS) policies
- Performance policies
Obtain the following information:
This information includes the address of the host or WWN, operating system, storage protocol (iSCSI, NVMe/FC, and NVMe/TCP), and initiator to use.
When you create volumes, they may get automatically placed in different appliances within the cluster. A volume group requires all member volumes to reside in the same appliance. If you and then want to add existing volumes to a volume group, you must first migrate them to the same appliance.
If you want to enable Metro protection for a volume, you must first create the volume and then enable that volume for a Metro cluster. Metro clusters provide enhanced availability and disaster avoidance, resource balancing across data centers, and storage migration.
You can select Other if the categories in the drop-down menu do not match the type of application that you are using. After you select Other, type the application name in the Application field.
If you do not see the application that you want in the drop-down menu, you can type it into the Application field. You can manually enter the name of an application whether you choose one of the selections under Category or select Other, from the drop-down menu. The maximum number of characters is 32.
Select a Performance Policy consistent with the I/O priority (High, Medium, or Low).
When you connect the volume to the hosts or host groups, you can specify a Logical Unit Number. The Logical Unit Number panel appears only if you select SCSI for the host. If a Logical Unit Number is not specified, the system assigns one by default. You can add hosts or host groups after creating the volume.