Create Storage Profile Dialog

Navigation: System > Global Settings > Storage Profiles > Actions > Create Storage Profile

Adds a new Storage Profile with custom QoS. The Storage Profile can then be selected when managing a logical volume.

Name

Identifies the name of the Storage Profile. The name includes, in some instances, the name of the application that is associated with the profile.

Storage Profile names can consist of up to 128 UTF-8 characters.

Enter Basic QoS Settings

Opens the Enter Basic QoS Settings dialog where you can enter the following basic QoS parameters. The system converts the basic setting selections to the following advanced QoS settings:

RAID Level
Read Ahead

Typical Access

Identifies the most common method of data access. Valid biases:

Sequential: 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.
Random: Indicates that the read requests and the write requests operate on the data mostly by accessing the records in an arbitrary order.
Mixed: Indicates that the read requests and the write requests operate on the data sometimes in sequential order and sometimes in random order.

I/O Bias

Identifies the typical read‑write ratio. Valid I/O biases:

Read: Indicates that most of the access requests are for read operations.
Write: Indicates that most of the access requests are for write operations.
Mixed: Indicates that the number of access requests are similar for read operations and for write operations.

Redundancy

Identifies the number of copies of the parity bits that the Oracle FS System creates for the volume.

Valid redundancy levels:

Single: 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.
Double: 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.

RAID Level

Identifies the storage mechanism that is used to enhance the ability of the system to recover data from the loss of one or more drives.

Possible RAID levels:

Single parity: 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.
Double parity: 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.
Mirrored: 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.

Read Ahead

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:

Normal: 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.
Aggressive: 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.
Conservative: Indicates that the input requests and the output requests are mostly sequential and that the workload is biased toward write operations.

Priority

Identifies the priority that the system gives to various operational aspects of a logical volume, such as the Controller processing queue. The processing-queue priority defines the percentage of the Controller CPU cycles that are dedicated to the volume. Identifies as well where the data is striped on rotating drives. Valid priority levels:

Premium: Indicates the highest priority for responding to requests in the processing queue.
High: Indicates the next highest priority for responding to requests in the processing queue.
Medium: Indicates an intermediate priority for responding to requests in the processing queue.
Low: Indicates the next to lowest priority for responding to requests in the processing queue.
Archive: Indicates the lowest priority for responding to requests in the processing queue.

Advanced

Provides access to the QoS properties that might affect system performance.

Note: This option is recommended for expert administrators who understand the full range of QoS properties.

Writes

Identifies the write‑caching rules to use for the profile.

Valid options:

Write-through: Writes data to the Controller cache and to the storage arrays before the write request completes. This rule ensures that the data is safely written to the storage before the write request returns to the application. Write-through caching performs more slowly than does write-back caching because the data is being written to the storage arrays as well as to the cache.
Write-back caching: Writes data to the Controller cache, and the write request returns immediately without waiting for the write‑to‑disk to complete. During idle cycles, the system writes the data from the cache to the storage arrays. Write-back caching performs faster than does write‑through because the data only needs to be written to the cache before the write request returns.
Important! If the system goes down unexpectedly, the data in the cache that has not been written to the storage arrays could be lost.

During the shutdown process, the system writes all cached data to the storage arrays.
Default: Indicates that the Oracle FS System selects the appropriate write‑caching rule based on the selected QoS settings.

Stripe Width

Identifies the number of drive groups over which the data is written.

For custom Storage Profiles, you can select a stripe width from the list of predefined values. You can also enter a value from 1 to 64.

Predefined stripe widths values:

1

Indicates a stripe width of 1 drive group.

2

Indicates a stripe width of 2 drive groups.

3

Indicates a stripe width of 3 drive groups.

4

Indicates a stripe width of 4 drive groups.

6

Indicates a stripe width of 6 drive groups.

8

Indicates a stripe width of 8 drive groups.

64

Indicates a stripe width of 64 drive groups.

All

Indicates that the logical volume is striped across all of the available drive groups.

auto‑select

Indicates that the Oracle FS System determines the stripe width based on the Priority option that you selected.

Note: We recommend that you use the auto‑select option.

When you choose auto‑select the system uses the following stripe widths for the Priority that you selected. However, the GUI displays auto‑select not the actual stripe width that the system determines.

Archive priority: The system uses a stripe width of 2 drive groups.
Low priority: The system uses a stripe width of 2 drive groups.
Medium priority: The system uses a stripe width of 3 drive groups.
High priority: The system uses a stripe width of 4 drive groups.
Premium priority: The system uses a stripe width of 4 drive groups.

Preferred Storage Classes

Allows you to specify the Storage Class media on which the logical volume resides and the preferred order that the Oracle FS System uses the media.

Preferred Order

Indicates the preferred order in which the Oracle FS System uses the available Storage Classes.

For example, if you are creating a profile for archiving database records, choose a Storage Class with large capacity as your first choice. For profiles that manage large data volumes, select a Storage Class that is optimized for read and write operations.

Storage Class

Specifies the category of physical media on which the logical volume resides.

Valid media types:

Performance SSD: Specifies that the data is stored on solid state drives (SSDs) that are optimized for the performance of balanced read and write operations.
Capacity SSD: 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.
Performance Disk: 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.
Capacity Disk: 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.