Creating Your First Storage Gateway File System

Log in to the management console.

Click File Systems on the upper-right area of the management console.

Click Create File System.

Enter the required information in Create a File System:

• File System Name: A unique, friendly name for the file system. Avoid entering confidential information. Use the following guidelines when naming a file system:

  • Use from 1 to 256 characters.

  • Valid characters are letters (upper or lower case), numbers, hyphens, underscores, and periods.

  Important
  
  

  The name cannot contain the following:

  • A slash (/) character because this character delimits bucket and object names in Oracle Cloud Infrastructure Object Storage.

  • The strings "pub" or "priv."

  If an Object Storage bucket by this file system name doesn’t exist in your tenancy, the bucket is created.

  If a corresponding Object Storage bucket by this file system name exists in your tenancy and there is data in the bucket, Storage Gateway works asynchronously to sync the bucket and file system contents.

  For claiming ownership of an existing bucket that another Storage Gateway appliance is using, see Importing an Existing Storage Gateway File System.

• Select the Object Storage tier in which you want to store your data

  Important
  
  

  Once set, you cannot change the storage tier in which a bucket resides.

  You can use the Oracle Cloud Infrastructure Object Storage object lifecycle policies feature to manage the archiving and deletion of objects in a bucket according to a predefined schedule. See Using Object Lifecycle Management for details.

  • Standard: The Standard tier is the primary default Object Storage tier for storing data that requires frequent and fast access. See Object Storage for more information.

  • Archive: The Archive tier is a special tier for storing data that is accessed infrequently and requires long retention periods. See Overview of Archive Storage for more information. Access to data in the Archive tier is not immediate since you must restore archived data before it’s accessible (see Restoring Storage Gateway Files and Objects from Archive Storage).

• Object Storage endpoint: Required. The Object Storage API endpoint for your service instance. To find the object storage API endpoint for your Oracle Cloud Infrastructure Object Storage tenancy, see the API documentation for Oracle Cloud Infrastructure Object Storage.

  Important
  
  

  The following information is required to connect your Storage Gateway file systems to Oracle Cloud Infrastructure. See Required Keys and OCIDs for detailed information on how to generate the required keys and where to obtain these OCIDs.

• Compartment OCID: Required. Unique identifier of your Oracle Cloud Infrastructure Object Storage compartment.

• Tenant OCID: Required. Unique identifier of your Oracle Cloud Infrastructure Object Storage tenancy.

• User OCID: Required. Unique identifier of your Oracle Cloud Infrastructure Object Storage user.

• Public Key's Finger Print: Required. Your Oracle Cloud Infrastructure Object Storage public key fingerprint.

• Private Key: Required. Your Oracle Cloud Infrastructure Object Storage private key.

• Private Key Passphrase: Required if a passphrase was specified during key creation. Your Oracle Cloud Infrastructure Object Storage private key passphrase.

  Note
  
  

  Your private key and passphrase are securely stored in the Storage Gateway docker. The Storage Gateway installation generates a pair of public and private keys. The system uses the public key to encrypt sensitive data.

Click Save.

The values you entered must match your Oracle Cloud Infrastructure credentials. If you get an error message, verify your entries, update any incorrect values, and click Save again.

Click Show Advanced File System Configuration.

Enter the required configuration information or click Use Default to accept the default values:

• NFS Allowed Hosts: A comma-separated list of hosts allowed to connect to the NFS export. You can also specify * to allow all hosts to connect.

  For example: 2001:db8:9:e54::/64, 192.0.2.0/24

• NFS Export Options: The NFS export options.

  Example: rw, sync, insecure, no_subtree_check, no_root_squash

  Important
  
  Do not specify the fsid option.

• Concurrent Uploads: The number of concurrent uploads to Oracle Cloud Infrastructure.

  This field indicates the maximum number of files that can be concurrently uploaded in Storage Gateway. If the value is 15, the concurrent file uploads can be between 1-15.

  The allowed range is 70.

• Sync Policy: The metadata operations are flushed to the disk based on the sync policy, but do not affect on-disk consistency. Currently, only Posix Standard is supported. Only the synchronous transactions (like fsync, ODSYNC, and OSYNC) are committed to the disk. All other transactions are handled asynchronously.

• Maximum Read Cache Size in GiB: The maximum read cache.

  When the read cache is full or reaches the configured limit, Storage Gateway removes files from the cache based on a least recently used (LRU) algorithm. Files pending upload to your tenancy are not removed from cache. You can also preserve files that you do not want removed from cache.

  Note
  
  

  The number of files in cache is limited to 20,000, regardless of the specified cache size in bytes.

  See Configuring the Cache for File Systems for details.

  The default value depends on how you provisioned local storage before installing Storage Gateway. The recommended local storage disk size is 600 GB (500 GB for file system cache, 80 GB for metadata, 20 GB for log). If you followed the documented recommendations, the default value for the read cache is approximately 300 GB.

Click Save.

The file system is created and appears in the File Systems listing.