This topic describes how to migrate data between Network Attached Storage (NAS) file
systems that are located in different VPCs.
Background information
Assume that a Shenzhen enterprise is named Enterprise A. As Enterprise A grows and
needs to expand, it establishes a branch in Hangzhou, which is named Branch B. The
data of Branch B is stored in an Apsara File Storage NAS file system. You must synchronize
the data of Branch B to another Apsara File Storage NAS file system where the data
of Enterprise A is stored. Each day, Branch B generates about 100,000 files whose
size is about 100 GB.
The NAS file system of Enterprise A and the NAS file system of Branch B are located
in different Alibaba Cloud VPCs. The CIDR block used for the VPC where the file system
of Enterprise A is located is 172.16.1.0/24. The CIDR block used for the VPC where
the file system of Branch B is located is 10.0.0.0/24.
Note If you are using a third-party NAS file system, you must connect the NAS server to
an Alibaba Cloud VPC by using a dedicated leased line. For more information, see
Created a dedicated physical connection.
Migration solution
- Establish a connection between the two VPCs by using Cloud Enterprise Network (CEN)
and configure permission groups.
- Create a migration job to synchronize the data of Branch B to Enterprise A on a regular
basis.
Step 3: Create a migration job
- Create a Resource Access Management (RAM) user in the Alibaba Cloud console and grant
the RAM user the permission to create migration jobs. For more information, see Create and grant permissions to a RAM user.
- Create a source NAS data address. For more information about configuration parameters,
see Create a source data address. The following figure shows the configuration details.
- Create a destination NAS data address. For more information about configuration parameters,
see Create a destination data address. The following figure shows the configuration details.
- Create a migration job for data synchronization. To ensure business continuity, set the daily start time of a synchronization job
to 22:00. For more information about configuration parameters, see Create a migration job. The following figure shows the configuration details.
Notice
- A synchronization job keeps running until you manually stop the job. Therefore, you
only need to create one synchronization job to synchronize data on a regular basis.
- In this example, you can use the default settings in the Performance step because
the customer only synchronizes a small amount of data during off-peak hours. In actual
practice, you need to specify appropriate performance parameters based on your needs.
- After each synchronization job is complete, you must perform specific actions to ensure
data integrity. These actions include viewing the status of the job, and comparing
the data of the source data address with that of the destination data address. For
more information about how to view the status of synchronization jobs, see Manage synchronization jobs.