6.2.6.3 mkvault

Create a vault.

Purpose

The mkvault command creates an Exascale vault.

Syntax

mkvault [@]vault [ --attributes attribute=value[,attribute=value]... ]

Command Options

The options for the mkvault command are:

  • vault: Specifies the name of the vault.

  • --attributes: Optionally specifies attributes to set.

    Use the describe mkvault command to see details about the vault attributes you can set. See also Describing Resources and Attributes.

Usage Notes

Note the following information when using this command:

  • Starting with Oracle Exadata System Software release 26.1.0, you can create multiple storage pools for each media type within a single Exascale cluster and you can provision a vault with a specific set of storage resources from each storage pool.

    To use this capability, do not specify any resource provisioning using the mkvault command. Rather, create the vault using the mkvault command, and then complete provisioning by using a separate chvault command for each storage pool that you want to associate with the vault.

    See also Provision a Vault Using Multiple Storage Pools For Each Media Type.

  • If your Exascale cluster is configured with Oracle Exadata System Software before release 26.1.0, you can specify one set of resource provisioning attributes, covering all media types, that is linked directly to the vault.

    The following list describes these attributes, which may be set using the --attributes option. See also Provision a Vault Using Only One Storage Pool For Each Media Type.

    • spaceProvEF, spaceProvHC, spaceProvXT: Provisions the vault with the specified amount of extreme flash (EF), high capacity (HC), or extended (XT) storage space.

    • iopsProvEF, iopsProvHC, iopsProvXT: Provisions the vault with the specified number of IOPS from extreme flash (EF), high capacity (HC), or extended (XT) storage.

    • flashCacheProv: Provisions the vault with the specified amount of flash cache space.

    • flashLogProv: Boolean value (true or false) indicating whether the vault is provisioned with access to Exadata Smart Flash Log.

    • xrmemCacheProv: Provisions the vault with the specified amount of Exadata RDMA Memory Cache (XRMEM cache) space.

      Use this attribute only on systems with HC or EF storage, but not both. For systems with HC and EF storage, use the following media-specific XRMEM cache provisioning attributes.

    • xrmemCacheProvEF: Provisions the vault with the specified amount of XRMEM cache space associated with EF media.

    • xrmemCacheProvHC: Provisions the vault with the specified amount of XRMEM cache space associated with HC media.

    The following notes also apply when specifying resource provisioning attributes using the --attributes option:

    • The default value for all resource provisioning attributes is effectively unlimited. Consequently, a vault that is created without any resource provisioning attribute settings has access to all of the resources in the Exascale cluster.

    • If you specify a value for any provisioning attributes, then the vault is limited to use the provisioned resources from the corresponding storage pools and the other storage pools are effectively disabled.

      If you specify a space provisioning attribute (spaceProvEF, spaceProvHC, or spaceProvXT) without a corresponding IOPS provisioning attribute (iopsProvEF, iopsProvHC, or iopsProvXT), then the vault can consume the specified space and use unlimited IOPS in the associated storage pool.

      If you specify an IOPS provisioning attribute without a corresponding space provisioning attribute, then the vault can consume unlimited space in the associated storage pool but the I/O bandwidth is limited by the IOPS provisioning attribute.

    • Prior to consumption, all provisioned resources are logically provisioned. For example, the spaceProvHC attribute specifies the maximum amount of HC storage space that the vault can consume. However, physical space is only consumed when data is written to files in the vault.

    • To specify an amount of space, you can:

      • Use an integer value representing the number of bytes. The maximum value is 4503599626321920.

      • Specify a space value using suffixes K, KB, M, MB, G, GB, T, TB. The suffix is not case-sensitive.

      • Use unlimited to specify an unlimited amount of space.

    • To specify a number of IOPS, you can:

      • Use an integer value. The maximum value is 4294967295.

      • Use unlimited to specify an unlimited number of IOPS.

    • Specifying 0 (zero) as the value for a cache provisioning attribute (flashCacheProv, xrmemCacheProv, xrmemCacheProvEF, or xrmemCacheProvHC) disables use of the corresponding cache for the vault.

Examples

Example 6-70 Create a Vault with Unlimited Storage

The following example shows creating a vault named my-data that has unlimited access to all of the resources in the Exascale cluster. 

@> mkvault @my-data

Parent topic: Vault Management