Creating a Batch File Storage Migration Plan

Preparations

• Create a migration project.

  Create a migration project on the MgC console. For details, see Managing Migration Projects.

• Create a migration cluster.

  Create a dedicated migration cluster for this migration. A cluster consists of a master node as well as several list and migration nodes. For details about how to create a cluster, see Creating a Migration Cluster.

• Create target file systems.

  Create target file systems for receiving migrated source data. For details, see Creating a File System or Creating an SFS Turbo File System.

Warnings

When creating a workflow, there are four overwriting policies for objects with the same name at the source and target: If older or different size, Never, Always, and If different CRC64 checksum. If you choose Never, restarting a migration after an interruption or pause may lead to incomplete data migration, even though the task may appear successful. This could impact data integrity, so use the Never option with caution.

Constraints

• Migration plans can be created only in the AP-Singapore and TR-Istanbul regions.
• Only one migration workflow can be created for a migration plan.
• A migration plan can include a maximum of 100 file systems.
• Target file systems included in a migration plan must be in the same region.
• A target file system must have more available space than the total data volume of the paired source file system.

Step 1: Create a Migration Plan

1. Sign in to the MgC console. In the navigation pane, under Project, select your application migration project from the drop-down list.
2. In the navigation pane, choose Migration Plans (NEW).
3. Click Create Migration Plan.
4. Set migration plan parameters based on Table 1.

   Table 1 Parameters for creating a migration plan

   Parameter	Configuration
   Migration Plan Template	Select Batch File Storage Migration.
   Plan Name	The system assigns a default plan name. You can also specify a plan name.
   Description (Optional)	Enter a description.

5. Click Confirm. The migration plan for batch file storage migration is created, and the page for configuring source and target resources is displayed.

Step 2: Configure Migration Resources

1. On the Configure Source/Target page, from the Target Region drop-down list, select the region where the target file systems are located.
2. In the File Systems area, click Add. A new row will be added below, allowing you to configure a source file system. Each click of this button will add another row, enabling you to include multiple source file systems in this plan.
3. Configure source file systems based on Table 2.

   Table 2 Parameters for configuring source file systems

   Parameter	Description	Remarks
   Source Storage Type	Supported source storage types include NAS_GFS, NAS_NFS_V3_PROTOCOL, and NAS_NFS_V3_MOUNT. Select a type based on your needs.	NAS_GFS: Google Cloud file systems NAS_NFS_V3_PROTOCOL: file systems that support standard NFSv3 NAS_NFS_V3_MOUNT: file systems that support non-standard NFSv3
   Source File System Address	Enter the mount address of the source file system. If the storage type is NAS_GFS, the file system address can include a host name, domain name, (optional) subdomain, port, and path. If the storage type is NAS_NFS_V3_PROTOCOL or NAS_NFS_V3_MOUNT, the file system address must match any of the following formats: <IP-address>:/ <IP-address>:/<path> <domain-name>:/ <domain-name>:/<path>	For both full and list migrations, a unique combination of source file system address and path or list path is required. In each case, the prefix matching rule applies. For example, if you have added the file system address 192.168.0.1:/a with a migration path /abc/a, an error will be reported if you try to add the file system address 192.168.0.1:/a with a migration path /abc. To overwrite an existing path, you need to delete the existing address and path combination first.
   Source Path	Enter the directory that contains the files to be migrated. The format is /<folder-name>.	For a list migration, enter / for the path.
   Target Storage Class	Currently, only NAS_NFS_V3_MOUNT (non-standard NFSv3 file systems) is supported.	-
   Target File System Address	If a General Purpose file system is used as the target, enter the mount address of the file system. To obtain the mount address, go to the file system list and click the icon next to the address in the Mount Point column. If an SFS Turbo file system is used as the target, enter the shared path of the file system. To obtain the shared path, go to the SFS Turbo file system list and click next to the path in Shared Path column.	Combinations of target file system addresses and paths can be duplicated.
   Target Path	Enter the directory for storing migrated files. The format is /<folder-name>.	-

4. Click Save in the Operation column. You can also click Save All after setting multiple records. After the settings are saved, batch modification is supported. Click Next to configure migration settings.

Step 3: Configure Migration Settings

1. In the Migration Method Configuration area, modify or remove resource, and Select a migration method for each resource.
   • Full migration: This method enables the migration of all data in a specific path in a source file system.
   • List migration: This method enables the migration of specific files and folders recorded in predefined lists.

2. In the Migration Settings area, set the parameters based on Table 3.

   Table 3 Migration settings

   Parameter	Sub-parameter	Description
   Migrate Metadata	-	Determine whether to migrate metadata. If you select this option, object metadata will be migrated. If you do not select this option, only the Content-Type and Content-Encoding metadata will be migrated.
   Concurrent Subtasks	-	User-defined. There cannot be more than 10 concurrent subtasks for each online migration node. For example, if there are 2 online migration nodes, the maximum number of subtasks can be 20 or any number below.
   Overwrite Existing NOTE: NAS systems do not allow any files or folders with identical names, regardless of case. The migration fails if a source file has the same name as a target folder or vice versa.	Never	Files existing at the target will never be overwritten. WARNING: If you choose Never for the initial migration, the attributes of involved parent folders at the source will not be migrated to the target. As a result, the folder attributes may be incomplete at the target. To avoid this issue, use the Never option with caution for the initial migration. If you choose Never, restarting a migration after an interruption or pause may lead to incomplete data migration, even though the task may appear successful. This could impact data integrity, so use the Never option with caution.
   	Always	Files existing at the target will always be overwritten.
   	If older or different size	The system replaces existing target files if they are older than or differ in size from their source counterparts. Files with matching modification times and sizes remain unchanged and are skipped during migration. The system verifies folders after their content is migrated. Folders that already exist at the target will be overwritten if they have different last modification times, sizes, or permissions from the paired folders at the source. NOTE: The same overwriting policy is applied to empty folders as files.
   Limit Traffic	-	Set the maximum bandwidth for the migration task during different periods. If you do not select this option, migration traffic will not be limited. If you select this option, you can limit the migration traffic by setting Start Time, End Time, and Bandwidth Limit. For example, if you set Start Time to 08:00, End Time to 12:00, and Bandwidth Limit to 20 MB/s, the maximum migration speed is limited to 20 MB/s from 08:00 to 12:00. The migration speed is not limited outside this period. NOTE: The bandwidth limit ranges from 1 MB/s to 1,048,576 MB/s. A maximum of five rules can be added. The time is the local standard time of the region you are migrating to.

3. (Optional) Configure advanced options based on Table 4.

   Table 4 Advanced options

   Parameter	Description
   Sync Incremental Before Cutover	If this option is selected, incremental data will be migrated before the migration reaches the cutover phase. If this option is not selected, the migration will proceed directly to the cutover phase without transferring incremental data.
   Filter Source Data	Use exclude patterns, include patterns, and time ranges to filter files to be migrated. For details about the filters, see Source Data Filters.
   Send SMN Notifications	Determine whether to use SMN to get notifications about migration results. If you do not select this option, no SMN messages will be sent after the migration is complete. If you select this option, after the migration is complete, SMN messages will be sent to the subscribers of the selected topic. You can select the language and trigger conditions for sending messages.

4. After the migration settings are configured, click Next to open the Configure Migration Cluster page.

Step 4: Configure a Migration Cluster

1. In the Migration Cluster area, select the cluster to be used. To modify the cluster, click Modify in the Operation column and modify the cluster by referring to Managing a Migration Cluster.
2. After the migration cluster is configured, click Next to open the confirmation page.

Step 5: Confirm the Configurations

After performing steps 1 to 4, check the resource and migration settings on the Confirm page. To update the settings, click Previous to return to the corresponding stage for modification.

Step 6: Perform Follow-Up Operations

After confirming that the configurations are correct, perform follow-up operations as required.