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 the name of the storage domain associated with the LUN.
Displays a dialog that lists the available Storage Domains.
Must be unique across the Oracle FS System
Must be 82 or fewer UTF characters
Must be 255 or fewer ASCII characters
Allows you to assign the LUN to a volume group.
Opens the Manage Volume Groups dialog, which allows you to create a volume group.
Specifies whether the logical volume uses a custom set of QoS properties.
Opens the View Storage Profiles dialog, which allows you to review the profile details.
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 number of copies of the parity bits that the Oracle FS System creates for the volume.
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.
Identifies the read‑ahead policy that the system uses for sequential read operations. The policy determines the amount of additional data, if any, that the system places into the Controller cache. Valid policies:
Indicates that the input requests and the output requests are accessing the data mostly in a random manner or in a mixed sequential and random manner.
Indicates that the input requests and the output requests are accessing the data mostly in a sequential manner and that the workload is biased toward read operations.
Indicates that the input requests and the output requests are mostly sequential and that the workload is biased toward write operations.
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.
Balances the background copy with the incoming client I/O. This option is the default.
Restricts the amount of work performed on a loaded system. This option is intended to have a minimal impact on client I/O throughput at the expense of longer copy times.
Prioritizes the background copy at the expense of client I/O throughput.
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 capacity that is reserved for the logical volume. The reserve capacity must be less than or equal to the maximum capacity.
Indicates that a portion of the internal data integrity checks is disabled for the LUN. If set, the Use as a Boot LUN option has no effect.
Indicates the status returned from the LUN is modified for unwritten data blocks. Setting this option affects the host or application retry timing.