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 or spaces.

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

GLOBAL OPTIONS FOR SUBCOMMANDS

The following global options can be used for fscli command-subcommand pairs that do not include other command-line options:

‑help: Returns the context-sensitive help for the specified subcommand.
‑usage: Returns the subcommand syntax for the given command, including all of the options that are available for the command-subcommand pair.

GLOBAL OPTIONS FOR COMMANDS

The following global options can be used for fully formed fscli commands:

‑example

Returns sample output from the specified command.

Note: To see the output in XML format, include the ‑o xml option.

‑timeout timeout-in-seconds

Specifies the length of time (timeout-in-seconds) that the command line interface waits before another command is allowed to run. If the command takes longer to run than the specified time limit, the system continues processing the command, but the command prompt is made available so that you can issue another command. If the -timeout option is omitted, the command line interface blocks until the one of the following conditions is met:

The command completes successfully.
The command returns with an error.
The session times out.

Note: Be sure to check the state of the system after initiating a long running command with the ‑timeout option. Many fscli commands run a series of underlying commands in sequence. When the timeout value is reached before all of the underlying commands have completed, the fscli command does not complete with the outstanding tasks reporting a failure status.

‑outputformat | ‑o { text | xml }: Controls the type of the output the system returns from a command. If the ‑outputformat option is not included, the format of the output defaults to simple text. If xml is provided, the output is a collection of XML elements.
Note: For XML output, if internal errors occur during command execution, each error is included in a separate <ErrorList> tag.

‑verify: Inspects the validity of the command syntax, not the semantics. Used to test the structure of a command without running the command. Does not determine whether errors would be produced if you issue a structurally correct command with the input provided.
‑sessionkey: Directs the CLI to prompt you to supply a session key when you issue the command. The CLI displays Sessionkey: as the prompt. To obtain a session key, log in with the ‑returnKey option specified. After the session is established, the session key is displayed in STDOUT. If you request a session key, the ‑sessionkey option is required syntax for all commands that are issued in a given session. In environments with more than one Oracle FS System, the session key is used to determine to which Oracle FS System to direct the command for validation. Session keys are also used to establish two or more CLI sessions when using a shared administrator account.
‑u admin-user ‑oracleFS oracle‑fs-system: Routes the command to a particular Oracle FS System for execution. This option passes the name of the administrator account to use when opening the session on the specified system. Identify a specific Oracle FS System by its IP address or by the name that is recorded in the domain name system (DNS). When logging in to the Oracle FS System using the ‑u option and the ‑oracleFS option, the fscli application prompts you for a password on the command line interface for access. The Oracle FS System and the account login information are used to authenticate the current session. Establishing a login session by specifying an Oracle FS System and an account does not change the credentials that are associated with the active sessions that are running on other clients.
Caution
Oracle recommends that you not use the Cygwin command line interface to run the fscli application on Windows platforms. If you are running the Cygwin interface and include the ‑u option as a part of the ‑list subcommand, the password for the specified account is included in the results. Exposing the password can cause a breach in security.

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