Snapshots are an important way of data sharing and migration. File systems created using a snapshot own all data in the snapshot. You can use a snapshot to create a file system (to ensure data security, only new file systems can be created from snapshots).
This document describes how to use a snapshot to create a file system on the snapshot list page. When creating a file system, you can configure the Snapshots parameter to specify a snapshot for creating the file system.
The following describes the parameters for creating a file system of Standard type as an example.
|Billing Mode||Select the desired billing mode. Two billing modes are supported: pay-as-you-go and prepaid.
Note: Only some products support the prepaid mode.
|File System Name||Customize the name of the file system to create.|
|Region||Select the region where the file system is to be created.|
|Availability Zone||Select the availability zone where the file system is to be created.|
|Protocol||Select a protocol type, NFS or SMB, for the file system. NFS is more suitable for Linux and Unix clients. CIFS/SMB is more suitable for Windows clients. The Turbo series can only be used by private clients and does not allow the selection of file system protocols.|
|Data Source||Optional. To create a file system using a snapshot, you need to select **Use a snapshot** and select the snapshot you want to use. If you create a file system using a snapshot, the initial data amount on the file system is the same as the snapshot size.|
|Permission Group||Each file system must be bound to a permission group. The permission group specifies an allowlist that can access the file system and lists the read and write permissions.|
|Scheduled Snapshot||Optional. When creating a file system, you can select **Scheduled Snapshot** to create snapshots for the file system periodically based on the created scheduled snapshot policy. For more information, see Scheduled Snapshot.|
|Storage Capacity||Required only for the Turbo series. The Turbo series is an exclusive cluster and has restrictions on the minimum cluster scale and expansion step. For Standard Turbo, the minimum initial cluster scale is 40 TiB, and the expansion step is 20 TiB. For High-Performance Turbo, the minimum initial cluster scale is 20 TiB, and the expansion step is 10 TiB.|
|CCN||Required only for the Turbo series. Select an existing CCN or create a new one. For more information about CCN, please see here.|
|IP Range||Required only for the Turbo series. This parameter allows you to reserve an IP range for Turbo related components. Ensure that the selected IP range does not conflict with the IP ranges of other instances on the cloud that need to communicate with Turbo. To ensure the number of IP addresses in the IP range, the mask must have 16 to 24 bits, for example, 10.0.0.0/24.|