Introduction

Scalable File System is designed to provide simple, scalable, and highly available file storage for cloud-based applications and services. It allows multiple E2E Node to access the same file system concurrently, enabling shared file storage across instances.

The Scalable File is commonly used for applications that require shared file storage, such as content management systems, web serving, big data analytics, and development environments. It simplifies the management and provisioning of file storage in the cloud, allowing applications to scale seamlessly and reliably.

Create Scalable File System

If you want to create an Scalable File System just go to left sidebar under the dashboard section then go to Storage -> Scalable File System

../../_images/SFS_new1.png

Then click on create button to create an Scalable File System

../../_images/SFS_new2.png

After clicking on create Scalable File System, give a name to your SFS and select the plan and VPC and then click on create SFS button.

../../_images/SFS_new3.png

After clicking on Create SFS button your created Scalable File System will be shown like this.

../../_images/SFS_new4.png

ACL

Using ACL configuration you can give the permission for and allow the Node with the SFS. For configure ACL Now go to ACL tab and click on configure ACL.

../../_images/SFS_new5.png

After clicking on configure ACL, The nodes which are attached with the same VPC network would be shown. Now select the permission according to your requirement and click on the Allow button to attach Node with SFS.

../../_images/SFS_new6.png

After clicking on the Allow button, the node will go into Configuring status and after some time it will again come in Available status.

../../_images/SFS_new7.png

How to Access Scalable File System(SFS)?

You need to connect your machine and follow the following command to mount the SFS.

1) For YUM Package Manager

Step - 1 :- Install nfs-utils on your machine using yum package installer.

# yum update
# yum install nfs-utils

Step-2 :- Make a MOUNT_POINT

# mkdir MOUNT_POINT

Step -3 :- Mount SFS on your machine.

# mount -t nfs -o soft,timeo=n, retrans=n, retry=n, SFS_SERVER_ENDPOINT:/data MOUNT_POINT

soft - When NFS tries to access a soft-mounted directory, it gives up and returns an error message after trying retrans times.

timeo - The timeout, in tenths of a second, for requests (read and write requests to mounted directories). If a request times out, this timeout value is doubled, and the request is retransmitted. Maximum value is 30 sec and the default value is 7sec.

retrans - The number of times a request (a read or write request to a mounted directory) is retransmitted after it times out. If the request does not succeed after n retransmissions, a soft mount returns an error. Default value is 4.

retry - The number of times the client attempts to mount a directory after the first attempt fails. Default value is 1.

2) For APT Package Manager

Step -1 :- Install nfs-common on your machine using apt package installer.

# sudo apt update
# sudo apt install nfs-common

Step -2 :- Make a MOUNT_POINT

# mkdir MOUNT_POINT

Step -3 :- Mount SFS on your machine.

# mount -t nfs -o soft,timeo=n, retrans=n, retry=n, SFS_SERVER_ENDPOINT:/data MOUNT_POINT

soft - When NFS tries to access a soft-mounted directory, it gives up and returns an error message after trying retrans times.

timeo - The timeout, in tenths of a second, for requests (read and write requests to mounted directories). If a request times out, this timeout value is doubled, and the request is retransmitted. Maximum value is 30 sec and the default value is 7sec.

retrans - The number of times a request (a read or write request to a mounted directory) is retransmitted after it times out. If the request does not succeed after n retransmissions, a soft mount returns an error. Default value is 4.

retry - The number of times the client attempts to mount a directory after the first attempt fails. Default value is 1.

3) For Windows Machine

Step -1 :- Make sure you have an NFS Client (Services for NFS) installed from Programs and Features.

Step- 2:- Mount SFS to a drive:

# mount -t nfs -o soft,timeo=n, retrans=n, retry=n, SFS_SERVER_ENDPOINT:/data  drive:

soft - When NFS tries to access a soft-mounted directory, it gives up and returns an error message after trying retrans times.

timeo - The timeout, in tenths of a second, for requests (read and write requests to mounted directories). If a request times out, this timeout value is doubled, and the request is retransmitted. Maximum value is 30 sec and the default value is 7sec.

retrans - The number of times a request (a read or write request to a mounted directory) is retransmitted after it times out. If the request does not succeed after n retransmissions, a soft mount returns an error. Default value is 4.

retry - The number of times the client attempts to mount a directory after the first attempt fails. Default value is 1.

Disallow Node

Now to disallow the node again go to the ACL tab and click on Disallow button to remove the established connection

../../_images/SFS_new8.png

Now to delete the SFS service click on the three dots which are present under the Actions button in the sfs listing and then click on delete button

../../_images/SFS_new9.png

Managing Snapshots in SFS Service

These steps to manage snapshots within the SFS (Scalable File System) service. Snapshots play a crucial role in capturing data states at specific points in time, allowing for data recovery, replication, and scheduled snapshot creation.

Viewing the Snapshot Section

To access the snapshot section, navigate to the SFS service on dashboard in Storage section and click the “Snapshot” tab.

../../_images/SFS_snap1.png

Upon clicking the “Snapshot” tab, the Snapshot page will open, providing options for managing snapshots.

Creating a Snapshot Manually

To create a snapshot manually, locate the “Snapshot Now” button on the Snapshot page and click on it.

../../_images/SFS_snap2.png

A pop-up will appear click on the “Create Snapshot” button within the pop-up to confirm the snapshot creation.

../../_images/SFS_snap3.png

Managing Created Snapshots

After the snapshot is successfully created, it will be displayed in the snapshot list on the Snapshot page.

../../_images/SFS_snap4.png

Actions on Snapshots

To perform actions on a snapshot, click on the three-dot “Actions” menu icon for the respective snapshot.

../../_images/SFS_snap5.png

Cloning a SFS

Click on the “Clone” option within the “Actions” menu to initiate the cloning process.

../../_images/SFS_snap6.png

On the “Clone SFS” page, select the desired Virtual Private Cloud (VPC) , then click on “Clone SFS” to proceed.

../../_images/SFS_snap7.png

The cloned SFS will be added to the list.

../../_images/SFS_snap8.png

Upgrading SFS

To upgrade the SFS associated with a snapshot, click on the “Upgrade” action for that snapshot.

../../_images/SFS_snap9.png

On the upgrade page, select the desired plan for upgrading the SFS, and then click on the “Upgrade” button.

../../_images/SFS_snap10.png

Deleting a Snapshot

To delete a snapshot, click on the “Delete” action for the specific snapshot.

../../_images/SFS_snap11.png

A pop-up will appear; click on the “Confirm Delete” button to permanently delete the snapshot.

../../_images/SFS_snap12.png

Scheduling Snapshots

To schedule snapshots, click on the “Schedule Snapshot” option.

../../_images/SFS_snap13.png

Configure the snapshot interval and specify the time when you want to take scheduled snapshots.

../../_images/SFS_snap14.png ../../_images/SFS_snap15.png

Deleting Scheduled Snapshots

To delete scheduled snapshots, click on “Configure Snapshot.”

../../_images/SFS_snap16.png

Select the interval after which the scheduled snapshots should be deleted.

../../_images/SFS_snap17.png ../../_images/SFS_snap18.png

By following these steps, you can effectively manage snapshots, perform various actions, and ensure the data integrity and availability of your files within the SFC service.