All Products
Search
Document Center

Create a share

Last Updated: Aug 01, 2019

Columns and descriptions:

• Share Name: The name of an NFS or SMB share. It is also the virtual path of NFS (NFSv4). If the gateway version is earlier than 1.0.35, you must use the NFSv3 protocol. Otherwise, the share name becomes invalid. You need to run the showmount –e command to obtain the path for mounting the share to the target client. Version 1.0.35 and later support the same mount point for both NFSv3 and NFSv4.

• Protocol: Select NFS or SMB as needed.

• Cache: The minimum cache capacity is 40 GB and the maximum is 8 TB. If the cache capacity is smaller than 500 GB, 20% of the cache capacity is used to store metadata. If the cache capacity is larger than 500 GB, 100 GB is used to store metadata. For example, if you select a cache capacity of 40 GB, then the cache capacity displayed is 32 GB.

• Read-only Client IPs: Specify the IP addresses of clients that are only allowed to read data from the share. NFS supports CIDR blocks.

• Read/Write Client IPs: Specify the IP addresses of clients that are allowed to read data from and write data to the share. NFS supports CIDR blocks.

• Discoverable: This parameter indicates whether the SMB share name can be discovered by other clients in the network.

• User Mapping: You can select none, root_squash, all_squas, or all_anomnymous as needed.

• Replication Mode: This mode creates two backups of all data. One is stored in the local cache disk and the other one is stored in the OSS bucket. It is much faster to read data from the local cache disk than reading data from the OSS bucket.

• Cache Mode: In this mode, the backup stored in the local cache disk only contains the metadata and frequently accessed user data. The backup stored in the OSS bucket contains all data.

• Enable Remote Sync: synchronizes metadata stored in the OSS bucket to the local cache disk. This feature can be applied to disaster recovery, data restoration, and data sharing scenarios.

• Ignore Delete: During the data synchronization process, the OSS buckets ignores all data deletion operations. This ensures that the data stored in the OSS bucket is complete and avoids the risk of deleting data by mistake.

• Sync Delay: Fragments may be generated if you frequently open the large files that are being uploaded to the OSS bucket. You can set a sync delay for the system to wait a short period of time before uploading the files to the OSS bucket. During this period, you can still make changes to the files without generating fragments. The default value is 5 seconds and the maximum is 120 seconds.

• Fragment Optimization: For applications that need to read and write small amounts of data frequently, you can set this parameter to Yes to improve the read and write performance. Before you enable this feature, make sure that it suits your business scenario.

• Direct_IO: Files are directly uploaded to the local cache disk, bypassing the ECS instance.

• If the Enable Remote Sync parameter is set to Yes, you can specify a remote sync interval from 15 seconds to 36000 seconds for the gateway. The default value is 36000 seconds.

1.To create a share, click Create in the upper-right corner and the following dialog box appears:

1.Configure the bucket settings, as shown in the following figure:

1

2.Enter the basic information about the share, as shown in the following figure:

2

3.Click the Advanced Settings check box to configure the advanced settings, as shown in the following figures:

3

4.Click OK to create the share. The following example creates an NFS share with a cache capacity of 40 GB:

4

5.After the share is created, the progress of the task is displayed at the bottom of the page, as shown in the following figure:

5

6.On the Cache page, you can view cache disks that you have added, as shown in the following figure:

6