Application Scenarios
If users who store a large amount of data in third-party cloud vendors want to migrate their data to eSurfing Cloud SFS, they have to first download their data stored on the third-party cloud vendor to the local area, and then manually upload their data to local. This conventional methods is time-consuming and labor-intensive and is likely to cause issues like data transmission missing or mis-transmission.
This section recommends a method by configuring the mount file system for an ECS instance as a transfer node for data transmission and then migrating the data to eSurfing Cloud SFS through the migration tool. The migration tool can be an SFTP client. With simple configuration, you can transfer your data from third-party cloud vendors to SFS easily and smoothly.
Tool Introduction
This practice uses FileZilla as an SFTP client as the guiding example.
Migration Tool | Feature | Application Scenarios |
SFTP Client | Support numerous operating system platforms and provide graphical operation interfaces. | -Upload a small number of files to the NFS file system at one time. |
Prerequisites
Have an SFS of NFS protocol and make sure that the file system capacity is higher than the total amount of data to be migrated. If you have not purchased SFS, you need to first purchase one.
Have a Linux ECS under the same VPC network as the file system and configure an elastic IP for the ECS as uploading and downloading file data need to occupy the public network bandwidth of the ECS.
Making Preparations
Download and install the migration Client Tools and follow the prompts on the page to install.
The file system is the destination file system for receiving data. Select the capacity specification according to your actual needs. For specific operations, see Creating a File System.
In this operation practice, you need to create an ECS as a transfer node for migrating non-eSurfing Cloud data to the eSurfing Cloud SFS. The recommended configuration is as follows:
Note:
l The cloud server in this operation is only used as a transfer station for data migration, not for actual businesses. To save costs, it is recommended to order an ECS in the Pay-As-You-Go mode and elastic IP for data transfer. For billing description, see ECS Billing Instructions.
l The migration rate of high-specification and high-bandwidth cloud servers is faster but its cost is also higher. You can select a cloud server based on your needs. The overall migration rate is also affected by file system performance. For details, see Product Specifications.
Parameter | Description |
Payment Method | Pay-As-You-Go |
Specifications | Universal The migration rate of high-standard cloud servers is faster. For example, the migration rate of 4C8G is greater than that of 1C1G. You can select a cloud server based on your needs. |
Mirror | CentOS 7.6 |
Elastic IP | Automatic Allocation |
IP Version | IPv4 |
Bandwidth | 5 MB. The migration rate of high bandwidth is faster. For example, the migration rate of 10 MB is greater than the migration rate of 5 MB. You can select a cloud server based on your needs. |
Login Method | Password > Create Now |
Procedure
Here are several key steps to migrate third-party data to SFS: Download third-party data to local > Mount the file system > Install the SFTP client locally and establish a connection with the ECS that mounts the SFS > Migrate the local data to the SFS. The specific operation steps are as follows:
1. Download third-party data to a local directory.
2. Mount the SFS to the cloud server. Mount the file system to the /mnt/localpath directory in the Linux cloud server. For details, see Mounting an NFS File System to ECSs (Linux).
3. Connect the installed SFTP client to the ECS mounted with the SFS.
1) Run the client tool and enter the host, user name, password, and port on the page. See the table below for parameters. After the configuration is complete, click Quickconnect to establish a connection.
Parameter | Description |
Host | The public network IP of the ECS, that is, the elastic IP, for example: 49.7.18 2.110 |
User Name | The username of the ECS, such as root (note: You need to ensure that the user who establishes the connection has permission to read and write the file system directory.) |
Password | The login password of the ECS user, such as the login password of the root user |
Port | SFTP port number. The default value is 22. |
2) After the connection is established, the left side of the page displays the directory to migrate the data and the right area displays the file system of the server-side ECS. Set the remote site path to the local path of the mounted file system (such as /mnt/localpath).
4. Migrate the data. Right-click on the file or directory you want to migrate in the left area and click Upload to complete the data migration.
