How many file systems can I create for each account?
By default, you can create up to 10 file systems in a single region and you can apply to increase the number to 20.
1. After you submit the order, please keep an eye out for the order progress and SMS notification. Our staff may contact you by phone. Please keep communication open.
How do I choose the NFS and CIFS file system protocols?
NFS (Network File System) is a protocol for sharing files and directories over a network. The NPS protocol supports cross-platform file sharing, enabling users to access files on any operating system.
CIFS (Common Internet File System) is a network protocol for sharing files and printers between computers. Originally developed by Microsoft, it became the default file-sharing protocol for Windows operating systems.
We recommend that you select the file system protocol according to your needs and scenarios:
If you want to share files on a Linux system, select the NFS protocol to create the file system.
If you want to share files on a Windows system, select the CIFS protocol to create the file system.
You cannot mount the NFS protocol file system on Windows and cannot mount the CIFS protocol file system on Linux.
Does the file system support data backup?
Currently, the backup at the file system level is not supported. We recommend that you use Cloud Backup & Recovery (CBR). It is an easy-to-use, cost-effective, safe, and reliable backup solution, which only requires one-click. The centralized management interface offers unified data protection for resources like directories and files in cloud servers hosting user services within eSurfing Cloud.
Cloud backup simplifies data backup for enterprises deploying their services in eSurfing Cloud. In the event of software errors, virus intrusions, accidental deletions, or other unforeseen incidents, cloud backup enables the restoration of data to any backup point, thereby minimizing economic losses.
Differences between SFS and Traditional NAS
Feature | Cloud Storage NAS | Traditional NAS |
Definition | A solution for defining network-attached storage based on cloud computing | A solution for defining network-attached storage based on local network |
Deployment Location | Devices and services are stored in the data centers of the cloud provider. | Devices and services are stored in a local data center or local area network. |
Hardware and Device Management | The cloud provider is responsible for maintaining hardware and equipment. | The organization is responsible for purchasing, configuring, and maintaining NAS equipment |
Scalability | On-demand scaling with a high flexibility | Subject to the storage and performance limits on purchased NAS devices |
Cost | On-demand purchase | One-time purchase of equipment and maintenance may result in higher initial costs |
Management and Configuration | Console Management | Complex configuration and dedicated person management |
Applicable scenarios | Suitable for environments where flexibility and scalability are required. | Suitable for environments that require local storage and high data security requirements. |
What distinguishes the shared access function of the SFS from the shared disk of the EVS?
SFS supports multiple clients to mount and read/write simultaneously. That is, Client1 and Client2... ClientN can write and access data to the same file system, allowing for shared access. The shared disk of the EVS can be mounted to multiple cloud servers simultaneously but must be used in a cluster management environment. Directly mounting the shared disk to multiple cloud servers cannot realize the sharing function, and may result in a risk of data being overwritten, i.e., write conflicts. For details, see Supporting EVS Shared Function.