Navigation:
Displays the storage capacity of the selected storage class and Storage Domain that is available for the logical volume. The graph uses colored bars of different thicknesses to indicate the capacity status of the logical volume you are creating as well as the overall system capacity.
Specifies that the data is stored on solid state drives (SSDs) that are optimized for the performance of balanced read and write operations.
Specifies that the data is stored on SSDs that are optimized for the performance of capacity and for read operations. The write performance for this Storage Class is sacrificed somewhat to achieve the optimizations for read performance and for capacity.
Specifies that the data is stored on high-speed hard disk drives (HDDs). This Storage Class sacrifices some capacity to reduce the access time and the latency of the read operations and of the write operations.
Specifies that the data is stored on high-capacity, rotating HDDs. This Storage Class optimizes capacity at some sacrifice of speed. For a storage system that does not include tape storage as an option, this Storage Class always provides the lowest cost for each GB of capacity.
Specifies whether to enable the Capacity for Clones options. Selecting this option also enables the Specify Clone QoS options.
Specifies the percentage of storage space to allocate for Clone LUNs.
Identifies the maximum capacity to which the logical volume can grow. For a clone, this field identifies how much addressable space is available. Capacity must be greater than or equal to the allocated logical capacity.
Identifies the amount of current storage capacity allocated for clones of this LUN.
Specifies the estimated storage space to allocate for Clone LUNs. The value of this field changes as the Maximum Capacity percentage changes and as the Capacity value changes that you provided in the Quality of Service tab.
Identifies the estimated available capacity for Clone LUNs. The value of this field changes as the Maximum Capacity percentage changes and as the Capacity value changes that you provided in the Quality of Service tab.
Identifies the number of clones that have been created for this LUN and its clones.
Specifies whether to apply the clone storage QoS properties using a Data Protection schedule, or manually applied by the administrator.
Specifies the enhanced QoS settings to apply to the clone storage that are created by the data protection schedule, or manually created by the administrator.
Specifies the name of the storage domain associated with the LUN.
Specifies the category of physical media on which the logical volume resides.
Specifies that the data is stored on solid state drives (SSDs) that are optimized for the performance of balanced read and write operations.
Specifies that the data is stored on SSDs that are optimized for the performance of capacity and for read operations. The write performance for this Storage Class is sacrificed somewhat to achieve the optimizations for read performance and for capacity.
Specifies that the data is stored on high-speed hard disk drives (HDDs). This Storage Class sacrifices some capacity to reduce the access time and the latency of the read operations and of the write operations.
Specifies that the data is stored on high-capacity, rotating HDDs. This Storage Class optimizes capacity at some sacrifice of speed. For a storage system that does not include tape storage as an option, this Storage Class always provides the lowest cost for each GB of capacity.
Indicates that the read requests and the write requests operate on the data mostly by accessing the records one after the other in a physical order.
Indicates that the read requests and the write requests operate on the data mostly by accessing the records in an arbitrary order.
Indicates that the read requests and the write requests operate on the data sometimes in sequential order and sometimes in random order.
Indicates that most of the access requests are for read operations.
Indicates that most of the access requests are for write operations.
Indicates that the number of access requests are similar for read operations and for write operations.
Identifies the RAID level associated with the Storage Profile.
Stores the original user data plus one set of parity bits to help in the recovery of lost data. Access to the data is preserved even after the failure of one drive. Single parity is implemented using RAID 5 technology and is the default redundancy level for the Storage Classes that specify the performance-type media.
Stores the original user data plus two sets of parity bits to help in the recovery of lost data. Access to the data is preserved even after the simultaneous failure of two drives. Double parity is implemented using RAID 6 technology and is the default redundancy level for the Storage Classes that specify the capacity-type media.
Identifies the RAID level associated with the Storage Profile.
Indicates that, in addition to the actual data, one set of parity bits exists for the logical volume. This parity level protects against the loss of one drive. Single parity is implemented as a variant of the RAID 5 storage technology.
Indicates that, in addition to the actual data, two sets of parity bits exist for the logical volume. This parity level protects against the loss of one or two drives with a slight cost to write performance. Double parity is implemented as a variant of the RAID 6 storage technology.
Indicates that no parity bits exist for the volume. Instead, the system writes the data in two different locations. This RAID level protects against the loss of at least one drive and possibly more drives with an improvement of the performance of random write operations. Mirrored RAID is implemented as a variant of the RAID 10 storage technology.
Indicates the highest priority for responding to requests in the processing queue. For auto-tiered LUNs, busy LUN extents receive the highest priority when the system migrates the data to the higher-performing storage tiers.
Indicates the next highest priority for responding to requests in the processing queue. For auto-tiered LUNs, busy LUN extents receive the next highest priority when the system migrates the data to the higher-performing storage tiers.
Indicates an intermediate priority for responding to requests in the processing queue. For auto-tiered LUNs, busy LUN extents receive an intermediate priority when the system migrates the data to the higher-performing storage tiers.
Indicates the next to lowest priority for responding to requests in the processing queue. For auto-tiered LUNs, busy LUN extents receive the next to lowest priority when the system migrates the data to the higher-performing storage tiers.
Indicates the lowest priority for responding to requests in the processing queue. For auto-tiered LUNs, busy LUN extents receive the lowest priority when the system migrates the data to the higher-performing storage tiers.
Lists the data protection schedules that are associated with the logical volume.
Identifies the name of the schedule.
Identifies the date and time that the schedule begins.
Indicates that the scheduled operation performs at the specified time.
Indicates that the operation is not performed as scheduled. Disable the schedule, for example, when the source volume (LUN or Clone LUN) has not been made available to users.
Displays a dialog to create a scheduled operation.
Displays a dialog to modify an existing schedule.
Removes an existing schedule.