This topic describes how to configure an Elastic Compute Service (ECS) instance as a transit node for migrating data from an external source to Apsara File Storage NAS.
Prerequisite
A file system is created. For more information, see Create a file system.
Use a new ECS instance as a transit node
Data transfer to and from a NAS file system consumes the public bandwidth of an ECS instance. To avoid impacting your production services, we recommend you purchase a dedicated ECS instance to act as a transit node.
The following limits apply when mounting a NAS file system during ECS instance creation:
Image: Automatic mounting is supported only on official Alibaba Cloud images.
If you want to use a custom image created from an ECS snapshot, you must mount the NAS file system manually after the ECS instance is created.
For Linux, see Mount an NFS file system on a Linux ECS instance.
For Windows, see Mount an SMB file system on a Windows ECS instance.
Mount directory: You can mount only the root directory of a NAS file system. You cannot mount subdirectories.
When you configure a new ECS instance as a transit node, use the recommended settings in the following tables. For detailed steps on how to mount the file system during purchase, see Mount NAS file systems when you purchase an ECS instance.
Parameter | Recommendation |
Image |
|
Parameter | Recommendation |
Public IP Address | Select Assign Public IPv4 Address. |
Bandwidth Billing | Select Pay-By-Traffic. |
Peak Bandwidth | Set the peak bandwidth to the maximum value of 100 Mbit/s. |
Use an existing ECS instance as a transit node
To use an existing ECS instance as a transit node, see the following topics:
For Linux, see Mount an NFS file system on a Linux ECS instance.
For Windows, see Mount an SMB file system on a Windows ECS instance.
What to do next
After you configure the transit node, you must select a suitable migration tool based on your business requirements. For more information, see Migrate data to a NAS file system.