You can configure an ECS instance as a data transmission transit node to migrate data from an external source to NAS.
Prerequisites
You must have a file system. For more information, see Create a file system.
Use a new ECS instance as a transit node
Because file transfers consume public bandwidth, we recommend that you create a dedicated ECS instance for data transfer to avoid affecting your application bandwidth.
The following limitations apply when you mount a NAS file system on a new ECS instance:
-
Image: Only official ECS images support automatically mounting a NAS file system.
If you use a custom image created from a snapshot, you must manually mount the file system after you create the instance.
-
For Linux, see Mount an NFS file system on a Linux instance.
-
For Windows, see Mount an SMB file system on a Windows instance.
-
-
Mount directory: You can only mount the root directory of the NAS file system. Mounting subdirectories is not supported.
When you create an ECS instance as a transit node, use the following recommended settings. For the full procedure, see Mount a NAS file system on a new ECS instance.
Table 1. Basic configurations
|
Parameter |
Description |
|
Image |
|
Table 2. Network and security
|
Parameter |
Description |
|
Public IP |
Select Assign Public IPv4 Address. |
|
Billing Method for Bandwidth |
Select Pay-By-Traffic. |
|
Peak Bandwidth |
Set the peak bandwidth to the maximum value of 100 Mbps. |
Use an existing ECS instance as a transit node
To use an existing ECS instance as the transit node, mount the NAS file system based on your operating system:
-
For Linux, see Mount an NFS file system on a Linux instance.
-
For Windows, see Mount an SMB file system on a Windows instance.
Next steps
After the configuration is complete, migrate your data by using a tool that suits your business needs. For more information, see Migrate data to Apsara File Storage NAS.