Overview
Scalable File Service (SFS) provides scalable, high-performance (NAS) file storage. With SFS, you can enjoy shared file access spanning multiple Elastic Cloud Servers (ECSs), Bare Metal Servers (BMSs), and containers created on Cloud Container Engine (CCE). See Figure 1.
- - - -
- File sharing
Servers in multiple availability zones (AZs) of a same region can access the same file system concurrently and share files.
- - Elastic scaling
Storage can be scaled up or down on demand to dynamically adapt to service changes without interrupting applications. You can complete resizing with a few clicks.
- - Superior performance
SFS enables file system performance to increase as capacity grows, and it delivers a high data durability to support rapid service growth.
-The backend storage system supports both HDD and SSD storage media. It adopts a distributed architecture and uses full redundant design for modules, which eliminate single-node faults.
- - Seamless integration
SFS supports Network File System (NFS). With this standard protocol, a broad range of mainstream applications can read and write data in the file system.
- - Easy operation
In an intuitive graphical user interface (GUI), you can create and manage file systems with ease.
+-Overview
Scalable File Service (SFS) provides scalable, high-performance (NAS) file storage. With SFS, you can enjoy shared file access spanning multiple Elastic Cloud Servers (ECSs), Bare Metal Servers (BMSs), and containers created on Cloud Container Engine (CCE). See Figure 1.
+ + + +Compared with traditional file sharing storage, SFS has the following advantages:- File sharing
Servers in multiple availability zones (AZs) of a same region can access the same file system concurrently and share files.
+ - Elastic scaling
Storage can be scaled up or down on demand to dynamically adapt to service changes without interrupting applications. You can complete resizing with a few clicks.
+ - Superior performance
SFS enables file system performance to increase as capacity grows, and it delivers a high data durability to support rapid service growth.
+The backend storage system supports both HDD and SSD storage media. It adopts a distributed architecture and uses full redundant design for modules, which eliminate single-node faults.
+ - Seamless integration
SFS supports Network File System (NFS). With this standard protocol, a broad range of mainstream applications can read and write data in the file system.
+ - Easy operation
In an intuitive graphical user interface (GUI), you can create and manage file systems with ease.
Accessing SFS
You can access SFS on the management console or via APIs by sending HTTPS requests.
-- APIs
Use APIs if you need to integrate SFS into a third-party system for secondary development. For detailed operations, see Scalable File Service API Reference.
- - Management console
Use the console if you prefer a web-based UI to perform operations.
+Accessing SFS
You can access SFS on the management console or via APIs by sending HTTPS requests.
+- APIs
Use APIs if you need to integrate SFS into a third-party system for secondary development. For detailed operations, see Scalable File Service API Reference.
+ - Management console
Use the console if you prefer a web-based UI to perform operations.
- APIs
diff --git a/docs/sfs/umn/en-us_topic_0034428727.html b/docs/sfs/umn/en-us_topic_0034428727.html index 3e76c5088..b363605a4 100644 --- a/docs/sfs/umn/en-us_topic_0034428727.html +++ b/docs/sfs/umn/en-us_topic_0034428727.html @@ -1,313 +1,313 @@ - +-Parent topic: Introduction+Parent topic: IntroductionCreate a File System
-You can create a file system and mount it to multiple servers. Then the servers can share this file system. You can create three types of file systems: SFS Capacity-Oriented, SFS Turbo, and General Purpose File System.
-Prerequisites
- Before creating an SFS Turbo, SFS Capacity Oriented, or a general purpose file system, ensure that a VPC is available.
If no VPC is available, create one by referring to section "Creating a VPC" in the Virtual Private Cloud User Guide.
- - Before creating an SFS Turbo, SFS Capacity Oriented, or a general purpose file system, ensure that ECSs are available and are in the created VPC.
If no ECS is available, create an ECS by referring to "Creating an ECS" in the Elastic Cloud Server User Guide.
+You can create a file system and mount it to multiple servers. Then the servers can share this file system. You can create three types of file systems: SFS Capacity-Oriented, SFS Turbo, and General Purpose File System.
+-Prerequisites
- Before creating an SFS Turbo, SFS Capacity Oriented, or a general purpose file system, ensure that a VPC is available.
If no VPC is available, create one by referring to section "Creating a VPC" in the Virtual Private Cloud User Guide.
+ - Before creating an SFS Turbo, SFS Capacity Oriented, or a general purpose file system, ensure that ECSs are available and are in the created VPC.
If no ECS is available, create an ECS by referring to "Creating an ECS" in the Elastic Cloud Server User Guide.
Creating an SFS Capacity-Oriented File System
- Log in to the management console using a cloud account.
- Log in to the management console and select a region and a project.
- Choose Storage > Scalable File Service.
- In the upper right corner of the page, click Create File System.
- Set the parameters as described in Table 1 as shown in Figure 1.
+-
Creating an SFS Capacity-Oriented File System
- Log in to the management console using a cloud account.
- Log in to the management console and select a region and a project.
- Choose Storage > Scalable File Service.
- In the upper right corner of the page, click Create File System.
- Set the parameters as described in Table 1 as shown in Figure 1.
-
Table 1 File system parameters Parameter
+-Table 1 File system parameters Parameter
Description
+Description
Remarks
+Remarks
File System Type
+File System Type
Select SFS Capacity-Oriented or SFS Turbo.
+Select SFS Capacity-Oriented or SFS Turbo.
Select SFS Capacity-Oriented.
+Select SFS Capacity-Oriented.
Region
+Region
Mandatory
-Region of the tenant. Select the region from the drop-down list in the upper left corner of the page.
+Mandatory
+Region of the tenant. Select the region from the drop-down list in the upper left corner of the page.
You are advised to select the same region as that of the ECSs.
+You are advised to select the same region as that of the ECSs.
AZ
+AZ
A geographical area with an independent network and an independent power supply.
+A geographical area with an independent network and an independent power supply.
You are advised to select the same AZ as that of the ECSs.
+You are advised to select the AZ where the servers reside.
Protocol Type
+Protocol Type
SFS supports NFS (only the NFSv3 protocol currently) for file system access.
+SFS supports NFS (only the NFSv3 protocol currently) for file system access.
-
+-
VPC
+VPC
An ECS cannot access file systems in a different VPC. Select the VPC to which the ECS belongs.
-NOTE:- By default, all ECSs in a VPC have the same rights. You can modify the VPC in the future.
- Upon creation, only one VPC can be added for each file system. After a file system is created, you can configure multiple VPCs by referring to Configuring Multi-VPC Access for the SFS file system.
An ECS cannot access file systems in a different VPC. Select the VPC to which the ECS belongs.
+NOTE:- By default, all ECSs in a VPC have the same permissions. You can modify the VPC in the future.
- Upon creation, only one VPC can be added for each file system. After a file system is created, you can configure multiple VPCs by referring to Configuring Multi-VPC Access for the SFS file system.
Click View VPC to view existing VPCs or create a new one.
+Click View VPC to view existing VPCs or create a new one.
Maximum Capacity
+Maximum Capacity
Maximum capacity allowed for a single file system. When the used capacity of a file system reaches this value, no more data can be written to the file system. You need to expand the file system capacity.
+Maximum capacity allowed for a single file system. When the used capacity of a file system reaches this value, no more data can be written to the file system. You need to expand the file system capacity.
The value ranges from 1 GB to 512,000 GB.
+The value ranges from 1 GB to 512,000 GB.
Encryption
+Encryption
Optional
-Specifies whether a file system is encrypted. You can create a file system that is encrypted or not, but you cannot change the encryption attribute of an existing file system. If Encryption is selected, the following parameters will be displayed:
-- Create Agency
If the KMS access rights are not granted to SFS Capacity-Oriented, this button will be displayed. Otherwise, this button will not be displayed.
-Click Create Agency to grant SFS Capacity-Oriented the permissions to access KMS. The system automatically creates an agency and names it SFSAccessKMS. When SFSAccessKMS is displayed for Agency Name, the KMS access rights have been granted to SFS Capacity-Oriented, and SFS Capacity-Oriented can obtain KMS keys for encrypting or decrypting the file system. After the rights are granted, follow-up operations do not need granting rights again.
+Optional
+Specifies whether a file system is encrypted. You can create a file system that is encrypted or not, but you cannot change the encryption attribute of an existing file system. If Encryption is selected, the following parameters will be displayed:
+- Create Agency
If the KMS access rights are not granted to SFS Capacity-Oriented, this button will be displayed. Otherwise, this button will not be displayed.
+Click Create Agency to grant SFS Capacity-Oriented the permissions to access KMS. The system automatically creates an agency and names it SFSAccessKMS. When SFSAccessKMS is displayed for Agency Name, the KMS access rights have been granted to SFS Capacity-Oriented, and SFS Capacity-Oriented can obtain KMS keys for encrypting or decrypting the file system. After the rights are granted, follow-up operations do not need granting rights again.
- Agency Name
- Agency: An agency is a trust relationship between two tenants or services. A tenant can create an agency to grant resource access rights to another tenant or service.
- SFSAccessKMS: If Agency Name is SFSAccessKMS, SFS Capacity-Oriented is granted the KMS access rights to use custom keys to encrypt or decrypt file systems.
- KMS key nameNOTE:
KMS key name is displayed only after the agency named SFSAccessKMS has been created. For details, see Create Agency above.
+- Agency Name
- Agency: An agency is a trust relationship between two tenants or services. A tenant can create an agency to grant resource access rights to another tenant or service.
- SFSAccessKMS: If Agency Name is SFSAccessKMS, SFS Capacity-Oriented is granted the KMS access rights to use custom keys to encrypt or decrypt file systems.
- KMS key nameNOTE:-
KMS key name is displayed only after the agency named SFSAccessKMS has been created. For details, see Create Agency above.
KMS key name is the identifier of the key, and you can use KMS key name to specify the KMS key that is to be used for encryption. You can select one of the following keys:
-- Default key: After the KMS access rights have been granted to SFS Capacity-Oriented, the system automatically creates a default key and names it sfs/default.
- Custom key: Existing or newly created custom keys. For details, see "Creating a Custom Key" in the Key Management Service User Guide.
NOTE:Before you use the encryption function, the KMS access rights must be granted to SFS Capacity-Oriented. If you have the right to grant the permission, grant SFS the permissions to access KMS directly. Otherwise, you need to contact the system administrator to obtain the "Security Administrator" rights first. For details, see File System Encryption.
+KMS key name is the identifier of the key, and you can use KMS key name to specify the KMS key that is to be used for encryption. You can select one of the following keys:
+- Default key: After the KMS access rights have been granted to SFS Capacity-Oriented, the system automatically creates a default key and names it sfs/default.
- Custom key: Existing or newly created custom keys. For details, see "Creating a Custom Key" in the Key Management Service User Guide.
NOTE:Before you use the encryption function, the KMS access rights must be granted to SFS Capacity-Oriented. If you have the right to grant the permission, grant SFS the permissions to access KMS directly. Otherwise, you need to contact the system administrator to obtain the "Security Administrator" rights first. For details, see File System Encryption.
- Agency Name
-
+-
- Create Agency
Name
+Name
User-defined name of the file system. If you create more than one file system, a name suffix is added to each file system name automatically. For example, if you set the name to sfs-name for two new file systems, the two file system names will be sfs-name-001 and sfs-name-002.
+User-defined name of the file system. If you create more than one file system, a name suffix is added to each file system name automatically. For example, if you set the name to sfs-name for two new file systems, the two file system names will be sfs-name-001 and sfs-name-002.
The name can contain only letters, digits, underscores (_), and hyphens (-). When creating one file system, enter a maximum of 255 characters. When creating multiple file systems, enter 1 to 251 characters.
+The name can contain only letters, digits, underscores (_), and hyphens (-). When creating one file system, enter a maximum of 255 characters. When creating multiple file systems, enter 1 to 251 characters.
Quantity
+Quantity
Number of file systems to be created
+Number of file systems to be created
Each cloud account can have a total of 512,000 GB for its file systems. Each cloud account can create a maximum of 10 file systems, one by one or in a batch.
-If the quantity or total capacity of the file systems you are creating exceeds the upper limit, contact customer service to apply for a higher quota. For details, see How Do I Apply for a Higher Quota?
+Each cloud account can have a total of 512,000 GB for its file systems. Each cloud account can create a maximum of 10 file systems, one by one or in a batch.
+If the quantity or total capacity of the file systems you are creating exceeds the upper limit, contact customer service to apply for a higher quota. For details, see How Do I Apply for a Higher Quota?
Tag
+Tag
Optional
-You can add tags when creating file systems. Tags can help you to identify, classify, and search for your file systems.
-Tags are composed of key-value pairs.- Key: Mandatory if the file system is going to be tagged.
A tag key can contain a maximum of 36 characters. It can only contain letters, digits, hyphens (-), and underscores (_).
- - Value: Optional if the file system is going to be tagged. It can be an empty character string. A tag value can contain a maximum of 43 characters. It can only contain letters, digits, hyphens (-), and underscores (_).NOTE:
- You can add a maximum of 10 tags to a file system.
- Tag keys of the same file system must be unique.
- Except for tagging the file system during file system creation, you can also add, modify, or delete tags for existing file systems.
Optional
+You can add tags when creating file systems. Tags can help you to identify, classify, and search for your file systems.
+Tags are composed of key-value pairs.- Key: Mandatory if the file system is going to be tagged.
A tag key can contain a maximum of 36 characters. It can only contain letters, digits, hyphens (-), and underscores (_).
+ - Value: Optional if the file system is going to be tagged. It can be an empty character string. A tag value can contain a maximum of 43 characters. It can only contain letters, digits, hyphens (-), and underscores (_).NOTE:
- You can add a maximum of 10 tags to a file system.
- Tag keys of the same file system must be unique.
- Except for tagging the file system during file system creation, you can also add, modify, or delete tags for existing file systems.
-
+-
- Click Create Now.
- Confirm the file system information and click Submit.
- Go back to the file system list.
If the status of the created file system is Available, the file system is created successfully. If the status is Creation failed, contact the administrator.
+- Click Create Now.
- Confirm the file system information and click Submit.
- Go back to the file system list.
-If the status of the created file system is Available, the file system is created successfully. If the status is Creation failed, contact the administrator.
Creating a General Purpose File System
- Log in to the management console using a cloud account.
- Log in to the management console and select a region and a project.
- Choose Storage > Scalable File Service.
- In the navigation pane, choose General Purpose File System. In the upper right corner of the page, click Create File System.
- Set the file system parameters, as shown in Figure 2. Table 2 describes the parameters.
+-
Creating a General Purpose File System
- Log in to the management console using a cloud account.
- Log in to the management console and select a region and a project.
- Choose Storage > Scalable File Service.
- In the navigation pane, choose General Purpose File System. In the upper right corner of the page, click Create File System.
- Set the file system parameters, as shown in Figure 2. Table 2 describes the parameters.
-
Table 2 File system parameters Parameter
+-Table 2 File system parameters Parameter
Description
+Description
Remarks
+Remarks
Region
+Region
Mandatory
-Region of the tenant. Select the region from the drop-down list in the upper left corner of the page.
+Mandatory
+Region of the tenant. Select the region from the drop-down list in the upper left corner of the page.
Select the region where the ECSs and VPC endpoint reside.
+Select the region where the ECSs and VPC endpoint reside.
Data Redundancy Policy
+Data Redundancy Policy
Multi-AZ: Data is stored in multiple AZs to achieve higher reliability.
+Multi-AZ: Data is stored in multiple AZs to achieve higher reliability.
NOTE:SFS uses the Erasure Code (EC) algorithm, instead of multiple copies, to ensure data redundancy.
-EC delivers a higher storage space utilization than the multi-copy redundancy while maintaining the same reliability level.
-If Multi-AZ is set for Data Redundancy Policy, the file system not only ensures redundancy for data among nodes in one AZ, but across multiple AZs.
- +NOTE:SFS uses the Erasure Code (EC) algorithm, instead of multiple copies, to ensure data redundancy.
+EC delivers a higher storage space utilization than the multi-copy redundancy while maintaining the same reliability level.
+If Multi-AZ is set for Data Redundancy Policy, the file system not only ensures redundancy for data among nodes in one AZ, but across multiple AZs.
+Name
+Name
User-defined name of the file system.
-It cannot be the same as that of an existing general purpose file system, including one created by the current user or any other user. And it cannot be changed after the file system is created.
-If a general purpose file system is deleted, you can create a new file system with the same name as the deleted one 30 minutes after that file system has been deleted.
+User-defined name of the file system.
+It cannot be the same as that of an existing general purpose file system, including one created by the current user or any other user. And it cannot be changed after the file system is created.
+If a general purpose file system is deleted, you can create a new file system with the same name as the deleted one 30 minutes after that file system has been deleted.
The name can contain only letters, digits, underscores (_), and hyphens (-). When creating one file system, enter a maximum of 255 characters. When creating multiple file systems, enter 1 to 251 characters.
+The name can contain only letters, digits, underscores (_), and hyphens (-). When creating one file system, enter a maximum of 255 characters. When creating multiple file systems, enter 1 to 251 characters.
Protocol Type
+Protocol Type
General purpose file systems support NFSv3 only.
+General purpose file systems support NFSv3 only.
-
+-
VPC
+VPC
Select the IAM project to which the target VPC belongs and then select the target VPC.
-Select the VPC where the ECSs and VPC endpoint reside.
-An ECS cannot access a file system belonged to a different VPC. Select the VPC where your ECSs reside. You can add VPCs later on the file system details page.
+Select the IAM project to which the target VPC belongs and then select the target VPC.
+Select the VPC where the ECSs and VPC endpoint reside.
+An ECS cannot access a file system belonged to a different VPC. Select the VPC where your ECSs reside. You can add VPCs later on the file system details page.
-
+-
- Click Create Now.
- Confirm the file system information and click Submit.
- Go back to the file system list.
If the file system is displayed in the list, it is successfully created. If it fails to be created, contact the website administrator.
+- Click Create Now.
- Confirm the file system information and click Submit.
- Go back to the file system list.
-If the file system is displayed in the list, it is successfully created. If it fails to be created, contact the website administrator.
Creating an SFS Turbo File System
- Log in to the management console using a cloud account.
- Log in to the management console and select a region and a project.
- Choose Storage > Scalable File Service.
- In the navigation pane on the left, choose SFS Turbo > File Systems. In the upper right corner of the page, click Create File System.
- Configure the parameters, as shown in Figure 3. Table 3 describes the parameters.
-
-
+-
Creating an SFS Turbo File System
- Log in to the management console using a cloud account.
- Log in to the management console and select a region and a project.
- Choose Storage > Scalable File Service.
- In the navigation pane on the left, choose SFS Turbo > File Systems. In the upper right corner of the page, click Create File System.
- Configure the parameters, as shown in Figure 3. Table 3 describes the parameters.
+
+
-
Table 3 File system parameters Parameter
+-Table 3 File system parameters Parameter
Description
+Description
Remarks
+Remarks
Region
+Region
Mandatory
-Region of the tenant. Select the region from the drop-down list in the upper left corner of the page.
+Mandatory
+Region of the tenant. Select the region from the drop-down list in the upper left corner of the page.
You are advised to select the region where the servers reside.
+You are advised to select the region where the servers reside.
AZ
+AZ
Mandatory
-A geographical area with an independent network and an independent power supply.
+Mandatory
+A geographical area with an independent network and an independent power supply.
You are advised to select the AZ where the servers reside.
+You are advised to select the AZ where the servers reside.
File System Type
+File System Type
Mandatory
-The following types are supported: Standard, Standard - Enhanced, Performance, Performance-Enhanced, 20 MB/s/TiB, 40 MB/s/TiB, 125 MB/s/TiB, and 250 MB/s/TiB.
-For more information, see File System Types.
+Mandatory
+The following types are supported: Standard, Standard - Enhanced, Performance, Performance-Enhanced, 20 MB/s/TiB, 40 MB/s/TiB, 125 MB/s/TiB, and 250 MB/s/TiB.
+For more information, see File System Types.
After a file system is created, its type cannot be changed. To change the file system type, you need to create another file system. Plan the file system type in advance.
+After a file system is created, its type cannot be changed. To change the file system type, you need to create another file system. Plan the file system type in advance.
Capacity
+Capacity
Maximum capacity allowed for a single file system. When the used capacity of a file system reaches this value, no more data can be written to the file system. You need to expand the file system capacity. The capacity of an SFS Turbo file system cannot be reduced. Set an appropriate file system capacity based on your service needs.
+Maximum capacity allowed for a single file system. When the used capacity of a file system reaches this value, no more data can be written to the file system. You need to expand the file system capacity. The capacity of an SFS Turbo file system cannot be reduced. Set an appropriate file system capacity based on your service needs.
Supported ranges:
-- 20 MB/s/TiB: 3.6 TB to 1 PB
- 40 MB/s/TiB: 1.2 TB to 1 PB
- 125 MB/s/TiB: 1.2 TB to 1 PB
- 250 MB/s/TiB: 1.2 TB to 1 PB
- Standard: 500 GB to 32 TB
- Performance: 500 GB to 32 TB
- Standard - Enhanced: 10 TB to 320 TB
- Performance - Enhanced: 10 TB to 320 TB
Supported ranges:
+- 20 MB/s/TiB: 3.6 TB to 1 PB
- 40 MB/s/TiB: 1.2 TB to 1 PB
- 125 MB/s/TiB: 1.2 TB to 1 PB
- 250 MB/s/TiB: 1.2 TB to 1 PB
- Standard: 500 GB to 32 TB
- Performance: 500 GB to 32 TB
- Standard-Enhanced: 10 TB to 320 TB
- Performance-Enhanced: 10 TB to 320 TB
Bandwidth (GB/s)
+Bandwidth (GB/s)
Defines the cache bandwidth, which is recommended for workloads with heavy reads and infrequent writes. The higher the bandwidth, the larger the capacity required.
+Defines the cache bandwidth, which is recommended for workloads with heavy reads and infrequent writes. The higher the bandwidth, the larger the capacity required.
- If you select the 20 MB/s/TiB, 40 MB/s/TiB, 125 MB/s/TiB, or 250 MB/s/TiB file system type, this parameter and its value will show up. Bandwidth size = Capacity x Bandwidth density (type value). The minimum bandwidth is 150 MB/s. If the calculated bandwidth is less than 150, 150 MB/s will be used.
- If you select the Standard, Standard-Enhanced, Performance-Enhanced, or Performance-Enhanced file system type, this parameter will not show up.
- If you select the 20 MB/s/TiB, 40 MB/s/TiB, 125 MB/s/TiB, or 250 MB/s/TiB file system type, this parameter and its value will show up. Bandwidth size = Capacity x Bandwidth density (type value). The minimum bandwidth is 150 MB/s. If the calculated bandwidth is less than 150, 150 MB/s will be used.
- If you select the Standard, Standard-Enhanced, Performance, or Performance-Enhanced file system type, this parameter will not show up.
Protocol Type
+Protocol Type
Mandatory
-SFS Turbo supports NFS for file system access.
+Mandatory
+SFS Turbo supports NFS for file system access.
The default value is NFS.
+The default value is NFS.
VPC
+VPC
Mandatory
-Select a VPC and a subnet.
-- VPC: A server cannot access file systems in a different VPC. Select the VPC to which the server belongs.
- Subnet: A subnet is an IP address range in a VPC. In a VPC, a subnet segment must be unique. A subnet provides dedicated network resources that are logically isolated from other networks, improving network security.
NOTE:Upon creation, only one VPC can be added for each file system. Multi-VPC file sharing can be implemented through VPC peering connection.
-For details about VPC peering connection, see section "VPC Peering Connection" in Virtual Private Cloud User Guide.
+Mandatory
+Select a VPC and a subnet.
+- VPC: A server cannot access file systems in a different VPC. Select the VPC to which the server belongs.
- Subnet: A subnet is an IP address range in a VPC. In a VPC, a subnet segment must be unique. A subnet provides dedicated network resources that are logically isolated from other networks, improving network security.
NOTE:Upon creation, only one VPC can be added for each file system. Multi-VPC file sharing can be implemented through VPC peering connection.
+For details about VPC peering connection, see section "VPC Peering Connection" in Virtual Private Cloud User Guide.
-
+-
Cloud Backup and Recovery
+Cloud Backup and Recovery
Cloud Backup and Recovery (CBR) provides backup protection for SFS Turbo and allows you to use backup data to create SFS Turbo file systems. After you configure backup, the system will associate the SFS Turbo file system with the backup vault and apply the selected policy to the vault to periodically back up the file system.
-The following options are available, among which Not required is preselected:
-- Not required: Backup is not configured. If you need backup protection after a file system has been created, log in to the CBR console, locate the desired vault, and associate the file system with the vault.
- Use existing vault
- Select an existing cloud backup vault from the drop-down list.
- Select a backup policy from the drop-down list, or go to the CBR console and configure a desired one.
- Auto assign
- Enter a vault name, which can contain a maximum of 64 characters, including letters, digits, underscores (_), and hyphens (-), for example, vault-f61e. The default naming rule is vault_xxxx.
- Enter a vault capacity, which is required for backing up SFS Turbo file systems. The vault capacity cannot be less than the size of file systems, so enter a value ranging from the total size of the associated file systems to 10,485,760, in the unit of GB.
- Select a backup policy from the drop-down list, or go to the CBR console and configure a desired one.
Cloud Backup and Recovery (CBR) provides backup protection for SFS Turbo and allows you to use backup data to create SFS Turbo file systems. After you configure backup, the system will associate the SFS Turbo file system with the backup vault and apply the selected policy to the vault to periodically back up the file system.
+The following options are available, among which Not required is preselected:
+- Not required: Backup is not configured. If you need backup protection after a file system has been created, log in to the CBR console, locate the desired vault, and associate the file system with the vault.
- Use existing vault
- Select an existing cloud backup vault from the drop-down list.
- Select a backup policy from the drop-down list, or go to the CBR console and configure a desired one.
- Auto assign
- Enter a vault name, which can contain a maximum of 64 characters, including letters, digits, underscores (_), and hyphens (-), for example, vault-f61e. The default naming rule is vault_xxxx.
- Enter a vault capacity, which is required for backing up SFS Turbo file systems. The vault capacity cannot be less than the size of file systems, so enter a value ranging from the total size of the associated file systems to 10,485,760, in the unit of GB.
- Select a backup policy from the drop-down list, or go to the CBR console and configure a desired one.
-
+-
Encryption
+Encryption
Optional
-Specifies whether a file system is encrypted. You can create a file system that is encrypted or not, but you cannot change the encryption attribute of an existing file system. If Encryption is selected, the following parameters will be displayed:
-- KMS key name
KMS key name is the identifier of the key, and you can use KMS key name to specify the KMS key that is to be used for encryption. Select an existing key from the drop-down list, or click View KMS List to create a new key. For details, see "Creating a CMK" in the Key Management Service User Guide.
- - KMS key ID
After you select a key name, the system automatically shows the key ID.
- - Key Encryption Algorithm
After you select a key name, the system automatically shows the encryption algorithm of the key.
+Optional
+Specifies whether a file system is encrypted. You can create a file system that is encrypted or not, but you cannot change the encryption attribute of an existing file system. If Encryption is selected, the following parameters will be displayed:
+- KMS key name
KMS key name is the identifier of the key, and you can use KMS key name to specify the KMS key that is to be used for encryption. Select an existing key from the drop-down list, or click View KMS List to create a new key. For details, see "Creating a CMK" in the Key Management Service User Guide.
+ - KMS key ID
After you select a key name, the system automatically shows the key ID.
+ - Key Encryption Algorithm
After you select a key name, the system automatically shows the encryption algorithm of the key.
-
+-
- KMS key name
Security Group
+Security Group
Mandatory
-A security group is a virtual firewall that provides network access control policies for file systems. You can define different access rules for a security group to protect the file systems that are added to this security group.
-When creating an SFS Turbo file system, you can select only one security group.
-You are advised to use an independent security group for an SFS Turbo file system to isolate it from service nodes.
-The security group rule configuration affects the normal access and use of SFS Turbo. For details about how to configure a security group rule, see section "Adding a Security Group Rule" in the Virtual Private Cloud User Guide. Security Group button allows you to choose Security Group. Additionally you can choose whether the system automatically enables the security group port required by the NFS protocol in the SFS Turbo file system. This ensures that the SFS Turbo file system can be accessed by your ECS and prevents file system mounting failures.
+Mandatory
+A security group is a virtual firewall that provides network access control policies for file systems. You can define different access rules for a security group to protect the file systems that are added to this security group.
+When creating an SFS Turbo file system, you can select only one security group.
+You are advised to use an independent security group for an SFS Turbo file system to isolate it from service nodes.
+The security group rule configuration affects the normal access and use of SFS Turbo. For details about how to configure a security group rule, see section "Adding a Security Group Rule" in the Virtual Private Cloud User Guide. Security Group button allows you to choose Security Group. Additionally you can choose whether the system automatically enables the security group port required by the NFS protocol in the SFS Turbo file system. This ensures that the SFS Turbo file system can be accessed by your ECS and prevents file system mounting failures.
-
+-
Tag
+Tag
Optional
-You can add tags when creating file systems. Tags can help you to identify, classify, and search for your file systems.
-A tag is composed of a key-value pair.- Key: Mandatory if the file system is going to be tagged
A tag key can contain a maximum of 36 characters, including letters, digits, hyphens (-), underscores (_), and at signs (@).
- - Value: Optional if the file system is going to be tagged. It can be an empty character string. A tag value can contain a maximum of 43 characters, including letters, digits, hyphens (-), underscores (_), and at signs (@).
Optional
+You can add tags when creating file systems. Tags can help you to identify, classify, and search for your file systems.
+A tag is composed of a key-value pair.- Key: Mandatory if the file system is going to be tagged
A tag key can contain a maximum of 36 characters, including letters, digits, hyphens (-), underscores (_), and at signs (@).
+ - Value: Optional if the file system is going to be tagged. It can be an empty character string. A tag value can contain a maximum of 43 characters, including letters, digits, hyphens (-), underscores (_), and at signs (@).
- You can add a maximum of 20 tags to a file system.
- Tag keys of the same file system must be unique.
- Except for tagging the file system during file system creation, you can also add, modify, or delete tags for existing file systems.
- You can add a maximum of 20 tags to a file system.
- Tag keys of the same file system must be unique.
- Except for tagging the file system during file system creation, you can also add, modify, or delete tags for existing file systems.
Name
+Name
Mandatory
-User-defined file system name.
+Mandatory
+User-defined file system name.
The name must start with a letter and can contain only letters, digits, and hyphens (-). It must contain more than four characters but no more than 64 characters.
+The name must start with a letter and can contain only letters, digits, and hyphens (-). It must contain more than four characters but no more than 64 characters.
- Click Create Now.
- Confirm the file system information and click Submit.
- Complete the creation and go back to the file system list.
If the status of the created file system is Available, the file system is created successfully. If the status is Creation failed, contact the administrator.
+- Click Create Now.
- Confirm the file system information and click Submit.
- Complete the creation and go back to the file system list.
diff --git a/docs/sfs/umn/en-us_topic_0037925065.html b/docs/sfs/umn/en-us_topic_0037925065.html deleted file mode 100644 index d9fd9f62d..000000000 --- a/docs/sfs/umn/en-us_topic_0037925065.html +++ /dev/null @@ -1,25 +0,0 @@ - - -If the status of the created file system is Available, the file system is created successfully. If the status is Creation failed, contact the administrator.
Overview
--This section describes how to use SFS.
-After creating a file system, you cannot directly access the file system. Instead, you need to mount the file system to ECSs.
-Figure 1 shows the process for creating and mounting an SFS Turbo file system.
-Figure 2 shows the process for creating and mounting an SFS Capacity-Oriented file system.
-Figure 3 shows the process for creating and mounting a general purpose file system.
- - - --- - - \ No newline at end of file diff --git a/docs/sfs/umn/en-us_topic_0037934210.html b/docs/sfs/umn/en-us_topic_0037934210.html deleted file mode 100644 index 43856dc36..000000000 --- a/docs/sfs/umn/en-us_topic_0037934210.html +++ /dev/null @@ -1,44 +0,0 @@ - - ---Parent topic: Getting Started-Mounting a File System Times Out
---Symptom
When a file system is mounted to servers using the mount command, message timed out is displayed.
--Possible Causes
- Cause 1: The network status is not stable.
- Cause 2: The network connection is abnormal.
- Cause 3: The DNS configuration of the server is incorrect. As a result, the domain name of the file system cannot be resolved, and the mounting fails. This issue will not occur on SFS Turbo file systems.
- Cause 4: The server that mounts the file system runs Ubuntu18 or later.
-Fault Diagnosis
After the network fault is excluded, run the mount command again.
--Solution
- Cause 1 and Cause 2: The network status is not stable or the network connection is abnormal.
Re-mount the file system after the network issue is addressed.
-- If the patch is uninstalled successfully, no further action is required.
- If the problem persists, see the solution for cause 3.
- Cause 3: The DNS configuration of the server is incorrect. As a result, the domain name of the file system cannot be resolved, and the mounting fails.
- Check the DNS configuration of the tenant and run the cat /etc/resolv.conf command.
- If the DNS has not been configured, configure it. For details about how to configure the DNS, see Configuring DNS.
- If the DNS has been configured, run the following command to check whether the DNS is correct:
nslookup File system domain name
-If the resolved IP address is in network segment 100, the DNS configuration is correct. If the IP address is in another network segment, the DNS configuration is incorrect. In this case, go to 2.
-
- Modify the /etc/resolv.conf configuration file, configure the correct tenant DNS, and run vi /etc/resolv.conf to edit the /etc/resolv.conf file. Add the DNS server IP address above the existing nameserver information. The DNS server IP address is 100.125.4.25.Figure 1 Configuring DNS-
The format is as follows:- -nameserver 100.125.4.25
- - Press Esc, input :wq, and press Enter to save the changes and exit the vi editor.
- The default DNS of the ECS applied by the user is inherited from the VPC to which the ECS belongs. Therefore, when the ECS restarts, the ECS changes synchronously. For this reason, changing configurations of the ECS does not settle the issue completely. You need to modify configurations in the VPC. Set a correct tenant DNS for the subnet of the VPC to which the ECS belongs. See Figure 3 and Figure 4. - - -
- (Optional) Restart the server.
- Run the mount command again.
- If the problem is solved, no further action is required.
- If the problem persists, see the solution for cause 4.
- Check the DNS configuration of the tenant and run the cat /etc/resolv.conf command.
- Cause 4: The server that mounts the file system runs Ubuntu18 or later.
- Reconfigure DNS by referring to Configuring DNS.
- Check whether the target server running Ubuntu18 or later uses a private image. -
- Convert the public image server to a private image server.
- To create a private image based on an existing ECS, see section "Creating an Image" in the Elastic Cloud Server User Guide.
- Use the private image created in 3.a to create an ECS or change the ECS OS. For details, see section "Changing the OS" in the Elastic Cloud Server User Guide.
- Log in to the server and mount the file system again.
-- - - \ No newline at end of file diff --git a/docs/sfs/umn/sfs_01_0002.html b/docs/sfs/umn/sfs_01_0002.html index 872168eda..f2229fd8a 100644 --- a/docs/sfs/umn/sfs_01_0002.html +++ b/docs/sfs/umn/sfs_01_0002.html @@ -4,7 +4,7 @@--Parent topic: Troubleshooting-Concept
A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.
- A region is a physical data center, which is completely isolated to improve fault tolerance and stability. The region that is selected during resource creation cannot be changed after the resource is created.
- An AZ is a physical location where resources use independent power supplies and networks. A region contains one or more AZs that are physically isolated but interconnected through internal networks. Because AZs are isolated from each other, any fault that occurs in one AZ will not affect others.
Figure 1 shows the relationship between regions and AZs.
- +diff --git a/docs/sfs/umn/sfs_01_0004.html b/docs/sfs/umn/sfs_01_0004.html index 21e31203a..1ce060865 100644 --- a/docs/sfs/umn/sfs_01_0004.html +++ b/docs/sfs/umn/sfs_01_0004.html @@ -20,7 +20,7 @@Selecting a Region
Select a region closest to your target users for lower network latency and quick access.
diff --git a/docs/sfs/umn/sfs_01_0005.html b/docs/sfs/umn/sfs_01_0005.html index 828b4b122..c5ae64761 100644 --- a/docs/sfs/umn/sfs_01_0005.html +++ b/docs/sfs/umn/sfs_01_0005.html @@ -266,7 +266,7 @@-Parent topic: Introduction+Parent topic: Introductiondiff --git a/docs/sfs/umn/sfs_01_0006.html b/docs/sfs/umn/sfs_01_0006.html index c993508ee..e60b2c09c 100644 --- a/docs/sfs/umn/sfs_01_0006.html +++ b/docs/sfs/umn/sfs_01_0006.html @@ -18,7 +18,7 @@-Parent topic: Introduction+Parent topic: Introductiondiff --git a/docs/sfs/umn/sfs_01_0007.html b/docs/sfs/umn/sfs_01_0007.html index 452e128a2..bfc91baf6 100644 --- a/docs/sfs/umn/sfs_01_0007.html +++ b/docs/sfs/umn/sfs_01_0007.html @@ -69,7 +69,7 @@-Parent topic: Introduction+Parent topic: Introductiondiff --git a/docs/sfs/umn/sfs_01_0008.html b/docs/sfs/umn/sfs_01_0008.html index ff59b596f..5a9710219 100644 --- a/docs/sfs/umn/sfs_01_0008.html +++ b/docs/sfs/umn/sfs_01_0008.html @@ -11,7 +11,7 @@-Parent topic: Introduction+Parent topic: Introduction-diff --git a/docs/sfs/umn/sfs_01_0011.html b/docs/sfs/umn/sfs_01_0011.html index 8684e1a3d..ebbaec4da 100644 --- a/docs/sfs/umn/sfs_01_0011.html +++ b/docs/sfs/umn/sfs_01_0011.html @@ -16,7 +16,7 @@Parent topic: Introduction+Parent topic: Introductiondiff --git a/docs/sfs/umn/sfs_01_0013.html b/docs/sfs/umn/sfs_01_0013.html index 20d6de6aa..a02ee326d 100644 --- a/docs/sfs/umn/sfs_01_0013.html +++ b/docs/sfs/umn/sfs_01_0013.html @@ -79,7 +79,7 @@-Parent topic: Introduction+Parent topic: Introductiondiff --git a/docs/sfs/umn/sfs_01_0030.html b/docs/sfs/umn/sfs_01_0030.html index 52d6c4743..ce171e914 100644 --- a/docs/sfs/umn/sfs_01_0030.html +++ b/docs/sfs/umn/sfs_01_0030.html @@ -20,6 +20,8 @@-Parent topic: Introduction+Parent topic: Introduction- Backup
+
- Managing SFS Turbo+OBS Storage Interworking
+- Monitoring
- Auditing
diff --git a/docs/sfs/umn/sfs_01_0032.html b/docs/sfs/umn/sfs_01_0032.html index e7a369030..c19a2022a 100644 --- a/docs/sfs/umn/sfs_01_0032.html +++ b/docs/sfs/umn/sfs_01_0032.html @@ -9,7 +9,7 @@-Restrictions
- Both system-defined policies and custom policies are supported in SFS Turbo file systems.
Process Flow
+Process Flow
- Create a user group and assign permissions to it.
Create a user group on the IAM console, and attach the SFS Turbo ReadOnlyAccess policy to the group.
- Create a user and add it to a user group.
Create a user on the IAM console and add the user to the group created in 1.
- Log in and verify permissions.
Log in to the SFS console using the created user, and verify that the user only has read permissions for SFS.
diff --git a/docs/sfs/umn/sfs_01_0044.html b/docs/sfs/umn/sfs_01_0044.html index ff8e04840..df7ca9f41 100644 --- a/docs/sfs/umn/sfs_01_0044.html +++ b/docs/sfs/umn/sfs_01_0044.html @@ -14,9 +14,9 @@Using a Backup to Create a File System
In case of a virus attack, accidental deletion, or software or hardware fault, you can use an SFS Turbo file system backup to create a new file system. Data on the new file system is the same as that in the backup.
- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your desired region and project. - Choose Storage > Cloud Backup and Recovery > SFS Turbo Backups.
- Click the Backups tab and locate the desired backup.
- If the status of the target backup is Available, click Create File System in the Operation column of the backup.
- Set the file system parameters. See Figure 1.
-diff --git a/docs/sfs/umn/sfs_01_0047.html b/docs/sfs/umn/sfs_01_0047.html index 581df451f..ef68f3f6d 100644 --- a/docs/sfs/umn/sfs_01_0047.html +++ b/docs/sfs/umn/sfs_01_0047.html @@ -1,7 +1,7 @@
- For detailed parameter descriptions, see table "Parameter description" under Table 3.
- Click Next.
- Go back to the file system list and check whether the file system is successfully created.
You will see the file system status change as follows: Creating, Available, Restoring, Available. You may not notice the Restoring status because Instant Restore is supported and the restoration speed is very fast. After the file system status has changed from Creating to Available, the file system is successfully created. After the status has changed from Restoring to Available, backup data has been successfully restored to the created file system.
+- Click Next.
- Go back to the file system list and check whether the file system is successfully created.
You will see the file system status change as follows: Creating, Available, Restoring, Available. You may not notice the Restoring status because Instant Restore is supported and the restoration speed is very fast. After the file system status has changed from Creating to Available, the file system is successfully created. After the status has changed from Restoring to Available, backup data has been successfully restored to the created file system.
SFS Metrics
-General purpose file systems do not support monitoring. The monitoring metrics described in this section apply only to SFS Capacity-Oriented file systems.
+General purpose file systems do not support monitoring. This section describes only the monitoring metrics of SFS Capacity-Oriented.
Function
This section describes metrics reported by Scalable File Service (SFS) as well as their namespaces and dimensions. You can use the console or APIs provided by Cloud Eye to query the metrics generated for SFS.
Namespace
SYS.SFS
@@ -139,7 +139,7 @@
- Log in to CBR Console.
Viewing Monitoring Statistics
- Log in to the management console.
- Choose Management & Deployment > Cloud Eye > Cloud Service Monitoring > Scalable File Service. In the file system list, click View Metric in the Operation column of the desired file system.
- View the SFS file system monitoring data by metric or monitored duration.
Figure 1 shows the monitoring graphs. For more information about Cloud Eye, see the Cloud Eye User Guide.
+diff --git a/docs/sfs/umn/sfs_01_0048.html b/docs/sfs/umn/sfs_01_0048.html index ba65dcda8..e4e93e3d5 100644 --- a/docs/sfs/umn/sfs_01_0048.html +++ b/docs/sfs/umn/sfs_01_0048.html @@ -22,7 +22,7 @@Viewing Monitoring Statistics
- Log in to the management console.
- Choose Management & Deployment > Cloud Eye > Cloud Service Monitoring > Scalable File Service. In the file system list, click View Metric in the Operation column of the desired file system.
- View the SFS file system monitoring data by metric or monitored duration.
Figure 1 shows the monitoring graphs. For more information about Cloud Eye, see the Cloud Eye User Guide.
- Log in to the management console using a cloud account.
client_connections
Client Connections
+File System Client Connections
Number of client connections
NOTE:Only active client connections are counted.
@@ -153,7 +153,7 @@
Viewing Monitoring Statistics
- Log in to the management console.
- View the monitoring graphs using either of the following methods.
- Method 1: Choose Service List > Storage > Scalable File Service. In the file system list, click View Metric in the Operation column of the target file system.
- Method 2: Choose Management & Deployment > Cloud Eye > Cloud Service Monitoring > SFS Turbo. In the file system list, click View Metric in the Operation column of the target file system.
diff --git a/docs/sfs/umn/sfs_01_0050.html b/docs/sfs/umn/sfs_01_0050.html index f21443076..03335b662 100644 --- a/docs/sfs/umn/sfs_01_0050.html +++ b/docs/sfs/umn/sfs_01_0050.html @@ -95,12 +95,12 @@Viewing Monitoring Statistics
- Log in to the management console.
- View the monitoring graphs using either of the following methods.
- Method 1: Choose Service List > Storage > Scalable File Service. In the file system list, click View Metric in the Operation column of the target file system.
- Method 2: Choose Management & Deployment > Cloud Eye > Cloud Service Monitoring > SFS Turbo. In the file system list, click View Metric in the Operation column of the desired file system.
- View the SFS Turbo file system monitoring data by metric or monitored duration.
For more information about Cloud Eye, see the Cloud Eye User Guide.
- Log in to the management console using a cloud account.
diff --git a/docs/sfs/umn/sfs_01_0056.html b/docs/sfs/umn/sfs_01_0056.html index 6ea05a11a..fafce3d30 100644 --- a/docs/sfs/umn/sfs_01_0056.html +++ b/docs/sfs/umn/sfs_01_0056.html @@ -4,7 +4,7 @@Querying Traces
- Log in to the management console.
- Click
in the upper left corner and select a region and project. - Choose Management & Deployment > Cloud Trace Service.
The Cloud Trace Service page is displayed.
+Querying Traces
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Choose Management & Deployment > Cloud Trace Service.
The Cloud Trace Service page is displayed.
- In the navigation pane on the left, choose Trace List.
- On the trace list page, set Trace Source, Resource Type, and Search By, and click Query to query the specified traces.
For details about other operations, see section "Querying Real-Time Traces" in the Cloud Trace Service User Guide.
Disabling or Enabling a Tracker
This section describes how to disable an existing tracker on the CTS console. After the tracker is disabled, the system will stop recording operations, but you can still view existing operation records.
-- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Choose Management & Deployment > Cloud Trace Service.
The Cloud Trace Service page is displayed.
+- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Choose Management & Deployment > Cloud Trace Service.
The Cloud Trace Service page is displayed.
- Click Trackers in the left pane.
- Click Disable on the right of the tracker information.
- Click Yes.
- After the tracker is disabled, the available operation changes from Disable to Enable. To enable the tracker again, click Enable and then click Yes. The system will start recording operations again.
-
-
- Mounting a File System Times Out
+ - Mounting a File System Times Out
- Mounting a File System Fails
diff --git a/docs/sfs/umn/sfs_01_0100.html b/docs/sfs/umn/sfs_01_0100.html
index 4eb95b7c4..f61693227 100644
--- a/docs/sfs/umn/sfs_01_0100.html
+++ b/docs/sfs/umn/sfs_01_0100.html
@@ -1,12 +1,12 @@
- A non-root user has been created on the ECS.
- A file system has been created and can be mounted to the ECS by the root user.
- The mount point of the file system has been obtained.
- A non-root user has been created on the ECS.
- A file system has been created and can be mounted to the ECS as root.
- The mount point of the file system has been obtained.
- Log in to the ECS as user root.
- Assign the permissions of user root to the non-root user.
- Run the chmod 777 /etc/sudoers command to change the sudoers file to be editable.
- Use the which command to view the mount and umount command paths.Figure 1 Viewing command paths-
- Run the vi /etc/resolv.conf command to edit the sudoers file.
- Add a common user under the root account. In this example, user Mike is added.Figure 2 Adding a user+
- Run the vi /etc/sudoers command to edit the sudoers file.
- Add a common user under the root account. In this example, user Mike is added.Figure 2 Adding a user
- Press Esc, input :wq, and press Enter to save and exit.
- Run the chmod 440 /etc/sudoers command to change the sudoers file to be read-only.
- Log in to the ECS as user Mike.
- Run the following command to mount the file system. For details about the mounting parameters, see Table 1.
sudo mount -t nfs -o vers=3,timeo=600,noresvport,nolock Mount point Local path
@@ -26,7 +26,7 @@Local path
Local path on the ECS, used to mount the file system, for example, /local_path.
+A local directory on the ECS used to mount the file system, for example, /local_path.
2024-11-21
+2024-12-20
+Updated the following content:
+Added section Managing SFS Turbo+OBS Storage Interworking.
+2024-11-21
Updated the following content:
- Updated the maximum capacity of a general purpose file system.
- Added What Are the Differences Between SFS, OBS, and EVS?
- Added Can I Migrate My File System Data to Another Region?
- Added Can a File System Be Mounted to Multiple Accounts?
- Added Does SFS Support Cross-Region Mounting?
- Added What Can I Do If Data of My File System Is Not the Same When Accessed from Two Client Servers?
-
-
- Overview
+ - Overview
- Configure a VPC Endpoint
diff --git a/docs/sfs/umn/sfs_01_0162.html b/docs/sfs/umn/sfs_01_0162.html
new file mode 100644
index 000000000..bd08fc607
--- /dev/null
+++ b/docs/sfs/umn/sfs_01_0162.html
@@ -0,0 +1,25 @@
+
+
+ - SFS Turbo file system types that support storage interworking: 250 MB/s/TiB, 125 MB/s/TiB, 40 MB/s/TiB, and 20 MB/s/TiB
- After you have configured storage interworking between OBS and a directory in SFS Turbo, operations like creating hard links, configuring directory quota limits, and renaming are no longer supported.
- You can configure a maximum of 16 interworking directories for a single SFS Turbo file system.
- Adding OBS buckets as storage backends depends on the OBS service, so you must have the OBS Administrator permissions.
- Files and directories with the same name cannot coexist in directories of the same level.
- The maximum supported path length is 1,023 characters.
- For import tasks, the length of a file or subdirectory name cannot exceed 255 bytes.
- If an OBS bucket has WORM enabled, you can only import data from OBS to SFS Turbo, but cannot export data from SFS Turbo to OBS.
- OBS buckets configured with server-side encryption and OBS parallel file systems cannot be added as storage backends.
- Log in to the SFS console.
- In the file system list, click the name of the desired file system to go to its details page.
- On the Storage Backends tab, click Add OBS Bucket.Figure 1 Add OBS Bucket+
- On the displayed Add OBS Bucket page, configure the following parameters.
+
+
+Table 1 Parameters required for adding an OBS bucket Parameter
+Description
+Constraints
+Can Be Modified
+Interworking Directory Name
+SFS Turbo will create a subdirectory with this name in the file system root directory and bind this subdirectory with the specified OBS bucket, so this name must be unique.
+- The subdirectory name must be unique.
- The subdirectory name must be a directory that cannot be found in the file system root directory.
- The subdirectory name cannot be a period (.) or two periods (..).
No
+Domain Name
+The name of an OBS bucket.
+- The bucket to be added must be available.
- OBS buckets configured with server-side encryption and OBS parallel file systems cannot be added as storage backends.
No
+OBS Endpoint
+The OBS domain name of the region.
+The OBS bucket and the SFS Turbo file system must be in the same region.
+No
+Auto Export
+If enabled, all updates made on the file system will be automatically exported to the OBS bucket.
+-
+Yes
+Data to Export
+This parameter shows up if you enable Auto Export.
+Select the type of updated data to export to the OBS bucket. Supported types include New, Changed, and Deleted. Data is exported from SFS Turbo to OBS asynchronously.
+New: Files created and then modified in the SFS Turbo interworking directory. Any data or metadata modifications made will be automatically synchronized to the OBS bucket.
+Changed: Files previously imported from the OBS bucket and then modified in the SFS Turbo interworking directory. Any data or metadata modifications made will be automatically synchronized to the OBS bucket.
+Deleted: Files deleted from the SFS Turbo interworking directory. Deletions will be automatically synchronized to the OBS bucket, and only such files that were previously exported to the bucket will be deleted.
+-
+Yes
+ - Select "Grant SFS Turbo the read/write permissions on the OBS bucket using a bucket policy" and click OK.
- OBS buckets configured with server-side encryption and OBS parallel file systems cannot be added as storage backends.
- When you add an OBS bucket as the storage backend, a bucket policy will be automatically created for the bucket, with the policy Sid set to PolicyAddedBySFSTurbo. Do not modify or delete this policy, or the interworking function cannot work normally.
- If you have added an OBS bucket as the storage backend for one or multiple SFS Turbo file systems, before you delete any file system or remove the bucket, do not delete the bucket. Otherwise, the interworking function cannot work normally.
- New: Files created and then modified in the SFS Turbo interworking directory. Any data or metadata modifications made will be automatically synchronized to the OBS bucket.
- Changed: Files previously imported from the OBS bucket and then modified in the SFS Turbo interworking directory. Any data or metadata modifications made will be automatically synchronized to the OBS bucket.
- Deleted: Files deleted from the SFS Turbo interworking directory. Deletions will be automatically synchronized to the OBS bucket, and only such files that were previously exported to the bucket will be deleted.
- Find the added OBS bucket and click Auto Synchronization in the Operation column.Figure 2 Auto Synchronization+
- Configure Auto Export.Figure 3 Auto Export+
- Enable or disable auto export.
- If auto export is disabled, this function is not supported. After auto export is enabled, select the types of data to be exported. Supported types include New, Changed, and Deleted. For more information, see Table 1.
- Click OK.
- Quick import: Use quick import if data in the bucket has not been exported from SFS Turbo before. A quick import only imports the object metadata (name, size, last modification time). After the import is complete, SFS Turbo will, by default, generate the additional metadata (uid, gid, directory permissions, and file permissions). If you want to specify the permissions of imported directories and files, follow the instructions in section "Creating a Data Import or Export Task" in the Scalable File Service API Reference. Such an operation is only valid for the current task. Quick import is faster, so you are advised to use quick import.
- Additional metadata import: Use additional metadata import if data in the bucket has been exported from SFS Turbo before. With additional metadata import, both the object metadata (name, size, last modification time) and the additional metadata (uid, gid, mode) will be imported. If there is no additional metadata, the permissions you specified will be used for imported directories and files.
- Find the added OBS bucket and click Import Metadata in the Operation column.Figure 4 Import Metadata+
- Set Object Prefix to the prefix of objects in the OBS bucket. It can be a specific object name. To import metadata of all the objects in the OBS bucket, leave the prefix field empty.
- Select Import Additional Metadata to import additional metadata. If this option is not selected, the system will perform a quick import.
- Click OK.
- After you import data from OBS to SFS Turbo, if new data is written to the bucket or existing data is modified, you need to import the data to SFS Turbo again.
- The length of a file or subdirectory name cannot exceed 255 bytes.
- Find the added OBS bucket and click Data import in the Operation column.Figure 5 Data import+
- Set Object Path to the path of objects in the OBS bucket (excluding the bucket name).+
If you enter the path of a directory, end it with a slash (/).
+- To import data of all the objects in the OBS bucket, leave the object path field empty. SFS Turbo will import data to the interworking directory and ensure that the file paths in the interworking directory are the same as those in the OBS bucket.
- Object path examples: (/mnt/sfs_turbo is the local mount point and output-1 is the interworking directory name.)
- If you enter dir/ as the object path, data will be imported to /mnt/sfs_turbo/output-1/dir.
- If you enter dir/file as the object path, data will be imported to /mnt/sfs_turbo/output-1/dir/file.
- If you leave the object path field empty, data will be imported to /mnt/sfs_turbo/output-1.
- Click OK.
- After you import data from OBS to SFS Turbo, if new data is written to the bucket or existing data is modified, you need to import the data to SFS Turbo again.
- You can also import data by calling the API. For details, see section "Creating a Data Import or Export Task" in the Scalable File Service API Reference.
- The length of a file or subdirectory name cannot exceed 255 bytes.
- Find the added OBS bucket and click More > Export in the Operation column.Figure 6 Export+
- Set File Prefix to the path of directories or files (excluding the interworking directory name) or that of a specific file. To export all files in the interworking directory to the bucket, leave the file prefix field empty.
- Click OK.
- Before data is exported, SFS Turbo starts asynchronous tasks to scan the files in the target directories. If there is any file that has been updated in the last 10 seconds, this file will not be exported.
- For a given file, if no changes were made since the last time it was exported to OBS, it will not be exported in the next export task even if the previously exported file has been deleted from the OBS bucket.
- After files are exported to OBS, any SFS Turbo metadata with a name starting with x-obs-meta-sfsturbo-st- will be included in the objects' custom metadata.
- The maximum file path that supports export is 1,023 characters.
- The maximum file size supported in an SFS Turbo file system is 320 TB, and the maximum file size that can be exported is 48.8 TB.
- When large files are exported, temporary files generated during the export will be stored in the x-obs-upload-sfsturbo-temp-part directory in the bucket. After the export is complete, SFS Turbo will automatically delete this directory as well as the temporary files in it.
- When a file is exported from SFS Turbo to OBS:
If it was previously imported to and then modified in SFS Turbo, it will overwrite its peer object in the bucket if it is newer. Otherwise, it will not overwrite its peer object in the bucket.
+If you upload an object to OBS when an object with the same name is being exported, the object you uploaded may be overwritten.
+ - If the OBS bucket is enabled with WORM, data cannot be exported.
- Log in to the SFS console.
- In the file system list, click the name of the created SFS Turbo file system to go to its details page.
- On the Basic Info tab, configure a cold data eviction duration.Figure 7 Setting a cold data eviction duration+
- Data can be evicted by time or capacity depending on which rule is triggered first.
- Cold data eviction is enabled by default, and the default duration is 60 hours. To configure a cold data eviction duration by calling the API, see section "Updating a File System" in the Scalable File Service API Reference.
- Services will be affected if the capacity of an SFS Turbo file system is used up, so you are advised to configure an alarm rule on Cloud Eye to monitor the file system capacity usage.
- When a file system capacity alarm is generated, change the cold data eviction duration to a shorter one, for example from 60 hours to 40 minutes to speed up data eviction, or simply expand the file system capacity.
- Above the storage backend list, click View Task Status.
- View the task records about export tasks. Click
to the right of the status to view the number of failures or success times. - In the search box in the upper right corner, enter the status, type, or creation time to filter tasks.
- In what cases will SFS Turbo evicts data?
For the files imported from OBS to SFS Turbo, if they not accessed within the configured eviction duration, they will be evicted.
+For the files created in SFS Turbo, they will only be evicted when they have been exported to OBS and meet the eviction rule. If they have not been exported, they will not be evicted.
+ - How do I import evicted data to my SFS Turbo file system?
- File data is loaded from the bucket to the file system when the file is read or written.
- You can use the data import function to manually load data to the file system.
- In what scenarios will data import fail?
When the SFS Turbo file system contains only the file metadata (only metadata is imported or data eviction happens) and the object in the OBS bucket has been deleted, importing data or access the file will fail.
+ - Are the import or export tasks synchronous or asynchronous?
Tasks are asynchronous. After a task is submitted, you can query the task status based on the task ID.
+ - If I delete the files in the SFS Turbo interworking directory, will the objects in the OBS bucket be deleted as well?
If auto synchronization is disabled, the answer is no. If auto synchronization is enabled, the answer is yes.
+ - Log in to the SFS console.
- In the file system list, locate the file system you want to delete and click Delete in the Operation column.
If you want to delete more than one file system at a time, select the file systems, and then click Delete in the upper left part above the file system list. In the displayed dialog box, confirm the information and then click OK. Batch deletion is only supported for SFS Capacity-Oriented file systems.
- - In the displayed dialog box for an SFS Turbo file system, as shown in Figure 1, confirm the information, enter DELETE in the text box, and click OK.
In the displayed dialog box for an SFS Capacity-Oriented or a general purpose file system, confirm the information and click OK.
- Only Available and Unavailable file systems can be deleted.
+Procedure
- Log in to the SFS console.
- In the file system list, locate the file system you want to delete and click Delete in the Operation column.
If you want to delete more than one file system at a time, select the file systems, and then click Delete in the upper left part above the file system list. In the displayed dialog box, confirm the information and then click OK. Batch deletion is only supported for SFS Capacity-Oriented file systems.
+ - In the displayed dialog box for an SFS Turbo file system, as shown in Figure 1, confirm the information, enter DELETE in the text box, and click OK.
In the displayed dialog box for an SFS Capacity-Oriented or a general purpose file system, confirm the information and click OK.
+diff --git a/docs/sfs/umn/sfs_01_0348.html b/docs/sfs/umn/sfs_01_0348.html new file mode 100644 index 000000000..d8dc18a86 --- /dev/null +++ b/docs/sfs/umn/sfs_01_0348.html @@ -0,0 +1,44 @@ + + + Only file systems whose statuses are Available or Creation failed can be deleted.
Mounting a File System Times Out
+++Symptom
When a file system is mounted to servers using the mount command, message timed out is displayed.
++Possible Causes
- Cause 1: The network status is not stable.
- Cause 2: The network connection is abnormal.
- Cause 3: The DNS configuration of the server is incorrect. As a result, the domain name of the file system cannot be resolved, and the mounting fails. This issue will not occur on SFS Turbo file systems.
- Cause 4: The server that mounts the file system runs Ubuntu18 or later.
+Fault Diagnosis
After the network fault is excluded, run the mount command again.
++Solution
- Cause 1 and Cause 2: The network status is not stable or the network connection is abnormal.
Re-mount the file system after the network issue is addressed.
+- If the patch is uninstalled successfully, no further action is required.
- If the problem persists, see the solution for cause 3.
- Cause 3: The DNS configuration of the server is incorrect. As a result, the domain name of the file system cannot be resolved, and the mounting fails.
- Check the DNS configuration of the tenant and run the cat /etc/resolv.conf command.
- If the DNS has not been configured, configure it. For details about how to configure the DNS, see Configuring DNS.
- If the DNS has been configured, run the following command to check whether the DNS is correct:
nslookup File system domain name
+If the resolved IP address is in network segment 100, the DNS configuration is correct. If the IP address is in another network segment, the DNS configuration is incorrect. In this case, go to 2.
+
- Modify the /etc/resolv.conf configuration file, configure the correct tenant DNS, and run vi /etc/resolv.conf to edit the /etc/resolv.conf file. Add the DNS server IP address above the existing nameserver information. The DNS server IP address is 100.125.4.25.Figure 1 Configuring DNS+The format is as follows:+ +
nameserver 100.125.4.25
+ - Press Esc, input :wq, and press Enter to save the changes and exit the vi editor.
- The default DNS of the ECS applied by the user is inherited from the VPC to which the ECS belongs. Therefore, when the ECS restarts, the ECS changes synchronously. For this reason, changing configurations of the ECS does not settle the issue completely. You need to modify configurations in the VPC. Set a correct tenant DNS for the subnet of the VPC to which the ECS belongs. See Figure 3 and Figure 4. + + +
- (Optional) Restart the server.
- Run the mount command again.
- If the problem is solved, no further action is required.
- If the problem persists, see the solution for cause 4.
- Check the DNS configuration of the tenant and run the cat /etc/resolv.conf command.
- Cause 4: The server that mounts the file system runs Ubuntu18 or later.
- Reconfigure DNS by referring to Configuring DNS.
- Check whether the target server running Ubuntu18 or later uses a private image. +
- Convert the public image server to a private image server.
- To create a private image based on an existing ECS, see section "Creating an Image" in the Elastic Cloud Server User Guide.
- Use the private image created in 3.a to create an ECS or change the ECS OS. For details, see section "Changing the OS" in the Elastic Cloud Server User Guide.
- Log in to the server and mount the file system again.
++ + + \ No newline at end of file++Parent topic: Troubleshooting+
Overview
++This section describes how to use SFS.
+After creating a file system, you cannot directly access the file system. Instead, you need to mount the file system to ECSs.
+Figure 1 shows the process for creating and mounting an SFS Turbo file system.
+Figure 2 shows the process for creating and mounting an SFS Capacity-Oriented file system.
+Figure 3 shows the process for creating and mounting a general purpose file system.
+ + + +++ + + \ No newline at end of file diff --git a/docs/sfs/umn/en-us_topic_0033386660.html b/docs/sfs/umn/sfs_01_0163.html similarity index 92% rename from docs/sfs/umn/en-us_topic_0033386660.html rename to docs/sfs/umn/sfs_01_0163.html index 0b516b743..aa109407b 100644 --- a/docs/sfs/umn/en-us_topic_0033386660.html +++ b/docs/sfs/umn/sfs_01_0163.html @@ -1,4 +1,4 @@ - +++Parent topic: Getting Started+Introduction
diff --git a/docs/sfs/umn/sfs_01_0334.html b/docs/sfs/umn/sfs_01_0334.html new file mode 100644 index 000000000..b8de606de --- /dev/null +++ b/docs/sfs/umn/sfs_01_0334.html @@ -0,0 +1,156 @@ + + +Managing SFS Turbo+OBS Storage Interworking
+++Overview
In scenarios like AI training and inference, high-performance data preprocessing, EDA, rendering, and simulation, you can use SFS Turbo file systems to speed access to your data in OBS buckets. After binding a directory in your file system with an OBS bucket, you can synchronize data between the file system and bucket through import and export tasks. You can enjoy the following benefits from SFS Turbo file caching: Before starting upper-layer training tasks, you can preload data in your OBS bucket to an SFS Turbo file system to speed up data access. Intermediate data and result data generated from upper-layer tasks is written to SFS Turbo file systems at a high speed. Downstream services can read and process the intermediate data, and you can asynchronously export the result data to OBS buckets for long-term low-cost storage. In addition, SFS Turbo allows you to configure a cache data eviction duration to delete data that has not been accessed for a long time to free up the cache space.
++Notes and Constraints
+Adding an OBS Bucket
+ +Auto Synchronization
After you add an OBS bucket as a storage backend, you can configure auto synchronization.
+If you enable auto export, SFS Turbo will asynchronously export data to OBS based on the types of data you select.
+Supported types include New, Changed, and Deleted.
+To configure auto synchronization when adding an OBS bucket, see Adding an OBS Bucket.
+To configure auto synchronization after an OBS bucket is added, perform the following steps:
++Metadata Import
After you add an OBS bucket as a storage backend, you can use the metadata import function.
+Before using an SFS Turbo file system to access data in your OBS bucket, you need to use metadata import to import the object metadata (name, size, last modification time) from the bucket to the file system. You can only access the object data in the interworking directory after the metadata is imported. This operation only imports the metadata. The data will be loaded from the bucket and cached in the file system when it is accessed for the first time. When the same data is accessed later, it will be accessed from the cache, instead of the bucket.
++
SFS Turbo supports two metadata import methods: quick import and additional metadata import. After the metadata import is complete, you can view the imported directories and files in the interworking directory.
++ +Data Import
After you add an OBS bucket as a storage backend, you can use the data import function.
+After a metadata import, data is not imported to the SFS Turbo file system. Instead, data will be loaded from the bucket to the file system when a file is accessed for the first time, which may take a long time. If your workloads are latency-sensitive and you know which directories and files need to be accessed, for example, AI training involves a large number of small files and is sensitive to latency, you can import specified directories and files in advance.
+During a data import, both data and metadata will be imported, and a quick metadata import will be performed, meaning that the additional metadata (such as uid, gid, and mode) will not be imported. If you want to specify the permissions of imported directories and files, follow the instructions in section "Creating a Data Import or Export Task" in the Scalable File Service API Reference. Such an operation is only valid for the current task.
++ +Data Export
After you add an OBS bucket as a storage backend, you can use the data export function.
+Data export allows you to export to the OBS bucket the files newly created in the interworking directory or the objects previously imported and then modified in the interworking directory. You can specify a prefix for data export. Then, only directories and files that match the specified prefix will be exported to the bucket.
++ +Cold Data Eviction
After you add an OBS bucket as a storage backend, you can use the cold data eviction function. Only data is deleted during an eviction. The metadata is retained. When the file is accessed later, the file data is loaded from OBS again.
+Evicting data by time
+After adding an OBS bucket, you can configure a cold data eviction duration to delete data from the cache by time. Files that have not been accessed within the specified duration will be evicted.
+The procedure is as follows:
+Evicting data by capacity
+SFS Turbo file systems also support data eviction by capacity.
+When the capacity usage of a file system reaches 95%, SFS Turbo will delete data that has not been accessed in the last 30 minutes until the capacity usage falls below 85%.
++ +Task Status
When you export data, a task record will be generated. You can view the task progress and status.
++ The system retains the latest 1,000 task records. Earlier records will be deleted automatically.
++FAQs
++ + + \ No newline at end of file diff --git a/docs/sfs/umn/sfs_01_0346.html b/docs/sfs/umn/sfs_01_0346.html index 21b27afe5..17360b1b4 100644 --- a/docs/sfs/umn/sfs_01_0346.html +++ b/docs/sfs/umn/sfs_01_0346.html @@ -11,7 +11,7 @@++Parent topic: Management+Name
Name of the file system, for example, sfs-name-001
+Name of the created file system
Data Redundancy Policy
diff --git a/docs/sfs/umn/sfs_01_0347.html b/docs/sfs/umn/sfs_01_0347.html index a3b7cdcc8..ac1158cee 100644 --- a/docs/sfs/umn/sfs_01_0347.html +++ b/docs/sfs/umn/sfs_01_0347.html @@ -4,9 +4,9 @@Data in a deleted file system cannot be restored. Ensure that files in a file system have been properly stored or backed up before you delete the file system.
-Prerequisites
The file system to be deleted has been unmounted. For details about how to unmount the file system, see Unmount a File System.
Procedure
Mounting a File System to a Linux ECS as a Non-root User
-Scenarios
By default, a Linux ECS allows only the root user to run the mount command to mount a file system. However, if the permissions of user root are assigned to other users, such users can also run the mount command to mount the file system. The following describes how to mount a file system to a Linux ECS as a common user. EulerOS is used as in this example.
+-Scenarios
By default, a Linux ECS allows only the root user to use the mount command to mount file systems, but you can grant the permissions of user root to other users. Then, such users can use the mount command to mount the file systems. The following describes how to mount a file system to a Linux ECS as a common user. EulerOS is used in this example.
Prerequisites
Prerequisites
Procedure
- Log in to the management console using a cloud account.
- Before creating an SFS Turbo, SFS Capacity Oriented, or a general purpose file system, ensure that a VPC is available.
- File sharing
