This topic describes how to manage cloud resources in the on-premises file gateway console, including binding and unbinding cloud resources, and speed testing.
Prerequisites
-
You have deployed an on-premises file gateway client. For more information, see Deploy an on-premises file gateway console.
An OSS bucket is created. For more information, see Get started by using the OSS console.
ImportantFile gateways support the following storage classes of OSS buckets: Standard, Infrequent Access (IA), and Archive. File gateways do not support OSS buckets for which back-to-origin routing is configured.
We recommend that you do not associate a gateway with an Archive bucket. If files that are written from a file gateway to OSS are infrequently modified, we recommend that you store the files in a Standard or IA bucket first and configure a lifecycle rule that changes the storage class of the files to Archive or Cold Archive. This reduces unnecessary restoration operations and optimizes storage costs and efficiency.
When a client writes a file to a file gateway, the gateway records at least two actions: writing the file and setting the file modification time. The gateway merges the two actions where possible. However, the gateway may still initiate multiple operations on the object to the bucket where the object is stored. The CopyObject operation is called to store the file modification time as a piece of metadata of the object in the bucket. If the object is an Archive or Cold Archive object, this operation requires object restoration, which takes some time to complete. This increases the time required for object uploads and even causes upload failures if not enough time is left to upload data in the cache.
Bind a cloud resource
Binding a cloud resource links your file gateway to an OSS bucket, which serves as the backend storage for a share. Each share corresponds to a single OSS bucket.
By default, data written to a Cloud Storage Gateway by a client is uploaded in real time to an OSS bucket. You can also configure a synchronization delay when you create a share. The maximum delay is 120 seconds.
Based on your business needs, you can use the custom or non-custom method to bind a cloud resource.
Standard method
On the on-premises file gateway console, go to the Cloud Resource Settings page and click Bind.
In the Bind Cloud Resource dialog box, configure the following parameters.
Parameter
Description
Resource Name
Enter a name for the cloud resource.
Cross-region Binding
Configure cross-region binding.
Select Yes to access an OSS bucket that is in a different region from the file gateway.
Select No to access only a bucket that is in the same region as the file gateway.
NoteTo ensure the accuracy of data synchronization, logging, and operations between the file gateway and the OSS bucket, their time zones must be identical.
Region
Select the region where the bucket is located.
Bucket Name
Select the bucket that you want to bind.
Use SSL
Select Yes to use SSL to access the OSS bucket.
Click OK to bind the cloud resource.
Custom method
On the on-premises file gateway console, go to the Cloud Resource Settings page and click Bind.
In the Bind Cloud Resource dialog box, configure the following parameters.
Parameter
Description
Resource Name
Enter a name for the cloud resource.
Use Custom Region
Select the Use Custom Region checkbox.
Endpoint
The endpoint of the OSS bucket. Example: oss-cn-hangzhou.aliyuncs.com
Bucket Name
Enter the name of the OSS bucket that you want to bind.
AccessKey ID
Enter your AccessKey ID.
AccessKey Secret
Enter your AccessKey secret.
Use SSL
Select Yes to use SSL to access the OSS bucket.
Click OK to bind the cloud resource.
Related operations
On the Cloud Resources page, you can also perform the following operations.
|
Actions |
Description |
|
Unbind |
Find the target cloud resource and click Unbind. After you unbind the cloud resource, its data remains. You can then access and delete the data in the Object Storage Service (OSS) console. |
|
Speed test |
Find the target cloud resource and click Speed Test to test its upload and download speeds. |