FAQs
Frequently asked questions...
- Why aren't these volumes associated with a workload?
Volumes are not associated with a workload if they have been created using the command line interface (CLI) or if they have been migrated (imported/exported) from a different storage array. - How does my selected workload impact volume creation?
During volume creation, you are prompted for information about a workload’s use. The system uses this information to create an optimal volume configuration for you, which can be edited as needed. Optionally, you can skip this step in the volume creation sequence. - Why don’t I see all my volumes, hosts, or host clusters?
Snapshot volumes with a DA-enabled base volume are not eligible to be assigned to a host that is not Data Assurance (DA) capable. You must disable DA on the base volume before a snapshot volume can be assigned to a host that is not DA capable. - Why can’t I delete the selected workload?
This workload consists of a group of volumes that were created using the command line interface (CLI) or migrated (imported/exported) from a different storage array. As a result, the volumes in this workload are not associated with an application-specific workload, so the workload cannot be deleted. - How do application-specific workloads help me manage my storage array?
The volume characteristics of your application-specific workload dictate how the workload interacts with the components of your storage array and helps determine the performance of your environment under a given configuration. - What do I need to do to recognize the expanded capacity?
If you increase the capacity for a volume, the host might not immediately recognize the increase in volume capacity. - When would I want to use the assign host later selection?
If you want to speed the process for creating volumes, you can skip the host assignment step so that newly created volumes are initialized offline.
Give documentation feedback