profile ‑add

Creates a custom Storage Profile.

SYNOPSIS

profile ‑add 
   ‑name profile‑name
   ‑priority {premium | high | medium | low | archive}
   [‑raidLevel {raid5 | raid10 | raid6 | default}]
   [‑readAhead {default | normal | aggressive | conservative}]
   [‑stripeWidth stripe‑width]
   [‑writeCache {writeThrough | writeBack | default}]
   [‑storageClass {capDisk | perfDisk | perfSsd | capSsd}
                     [,{capDisk | perfDisk | perfSsd | capSsd}]... ]

   [{‑sessionKey | ‑u admin‑user ‑oracleFS oracle‑fs‑system}]
   [{‑outputformat | ‑o} { text | xml }]
   [{‑timeout timeout‑in‑seconds | ‑verify | ‑usage | ‑example | ‑help}]

DESCRIPTION

Storage Profiles can be used when creating a logical volume. Instead of selecting QoS properties individually, you can associate a Storage Profile that defines the properties that you want with the volume.

Note: Only administrators with primary administrator or admin1 roles are authorized to run the profile ‑add command.

OPTIONS

‑name

Specifies the name of the Quality of Service (QoS) profile that you are creating. The system uses this name to create the fully qualified name (FQN) of the Storage Profile. Use double quotation marks around names containing dashes.

‑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.

‑raidLevel

Specifies the level of RAID data protection to use for the logical volume. Valid values:

raid5: 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.
raid6: 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.
raid10: 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.
default: Indicates that the level of RAID protection is determined by the Storage Class. For large form factor (capacity) hard disk drives, RAID 6 is the default level of protection. For the other Storage Classes, RAID 5 is the default level of protection.

‑readAhead

Identifies the read‑ahead policy to use for the logical volume for sequential read operations. The policy determines the amount of additional data, if any, that the system places into the Controller cache. Valid policies:

default and 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.

‑storageClass

Identifies the type of physical media on which the data is stored. Valid media types (sorted from the highest performance priority to the lowest performance priority):

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

When creating a logical volume using a storage profile, the Oracle FS System uses the Storage Class with the highest performance that has enough capacity for the volume.

The ‑storageClass option is required if the system contains two or more Storage Classes.

‑stripeWidth

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

Valid values are 1 through 64, or all. A value of all specifies the maximum possible stripe width.

‑writeCache

Identifies the write‑caching rules to use for the profile. Valid options:

writeThrough: 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.
writeBack: 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.
default: Indicates that the Oracle FS System selects the appropriate write‑caching rule based on the selected QoS settings.

EXAMPLE

Task

Creates a custom Storage Profile with a specified priority and storage class.

Parameters

The name of the Quality of Service (QoS) profile: profile_1
The priority of the (QoS) profile: medium
The storage class of the (QoS) profile: perfDisk

$ fscli profile ‑add ‑name profile_1 ‑priority medium ‑storageClass perfDisk