This topic guides you through creating your first Storage Gateway file system.
Think of a file system as a namespace containing a dataset that’s accessible through Storage Gateway. A Storage Gateway file system in this context represents a mapping between a directory on your on-premises host and a bucket in Oracle Cloud Infrastructure Object Storage. When you create a Storage Gateway file system, you define the connection credentials that Storage Gateway uses to connect to your Oracle Cloud Infrastructure tenancy.
When you log in to the management console or the first time, a wizard prompts you to create the administrator credentials and your first file system.
- Log in to the management console.
- Click File Systems in the upper-right side 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: Cannot contain a slash (/) character because this character delimits bucket and object names in Oracle Cloud Infrastructure Object Storage.)
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.
Select the Object Storage tier in which you want to store your dataImportant
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 pre-defined schedule. See Using Object Lifecycle Management for details.
- Standard: The Standard tier is the primary default Object Storage tier for storing data that is accessed frequently and requires fast and immediate access. See Overview of 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. You must restore archived data before it’s accessible (see Restoring Files/Objects from Archive Storage).
Object Storage endpoint: Required. The Object Storage API endpoint for your service instance. To find out the object storage API endpoint for your Oracle Cloud Infrastructure Object Storage tenancy, see the API documentation for Oracle Cloud Infrastructure Object Storage.
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. Oracle Cloud Infrastructure Object Storage Public Key's Finger Print.
- Private Key: Required. Oracle Cloud Infrastructure Object Storage Private Key.
- Private Key Passphrase: Required if a passphrase was specified during key creation. Oracle Cloud Infrastructure Object Storage Private Key Passphrase.
The values you entered must match your Oracle Cloud Infrastructure tenancy 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 following 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.
NFS Export Options: The NFS export options.
Don’t specify the
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.
Allowed range: From 1 through 30
- 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 the other transactions are handled asynchronously.
Cloud Read-ahead: The number of blocks to be downloaded and used to read ahead when reading files for improved performance.
Default value: 50
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.
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.
Default value: Depends on how you provisioned local storage prior to 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 read cache is approximately 300 GB.
The file system is created and displayed in the File Systems listing.
Connect the file system to a directory on Storage Gateway host. For more information, see Connecting a File System.
You can also do the following tasks in the management console: