Batch Migrating Data to SFS Turbo Using MgC

Solution Overview

You can use MgC to migrate data to SFS Turbo file systems from the following data sources: NAS_GFS, NAS_NFS_V3_PROTOCOL, and NAS_NFS_V3_MOUNT.

This section describes how to use a batch file storage migration template to create a file storage migration workflow to migrate data from one SFS Turbo file system to another.

For more information about batch data migration operations between other data sources and SFS Turbo, see Creating a Batch File Storage Migration Workflow.

Constraints

See the constraints described in What Are the Restrictions on Using MgC for Storage Migration?

Warnings

When you create a workflow, there are three options for Overwrite Existing: Never, Always, and If older or different size. If you choose Never, restarting a migration after an interruption or pause may lead to incomplete data migration, even if the task may appear successful. This could impact data integrity, so use the Never option with caution.

Prerequisites

A batch file storage migration plan has been created based on Creating a Batch File Storage Migration Plan. The storage type of both the source and target file storage is set to NAS_NFS_V3_PROTOCOL.

Creating a Batch File Storage Migration Workflow

Sign in to the . In the navigation pane, under Project, select your from the drop-down list.
In the navigation pane, choose Workflows.
Click Create Workflow in the upper right corner of the page.
In the Batch File Storage Migration card, click Preview Steps to view the stages and steps predefined in the template and the detailed description of each stage and step. Automated steps are handled by the system. Click Configure Workflow in the lower right corner.

In the Basic Information area, enter a name and description for the workflow.

**Table 1** Basic parameters
Parameter	Example Value	Description
Name	Batch_data_migration	User-defined.

In the Migration Plan area, select the created migration plan. Then you could see the overview of the migration plan.

In the Migration Cluster area, select the cluster used for the migration. The cluster specified in the migration plan is preselected by default, but you can select another one if needed. The modification is only applied to the current workflow, not the migration plan.

**Table 2** Migration cluster parameter
Parameter	Example Value	Description
Name	Batch_data_migration_cluster	User-defined.

Configure migration task parameters based on Table 3.

**Table 3** Migration task settings
Parameter	Sub-parameter	Description
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, enter 20 or any number below.
Overwrite Existing	Always	Always indicates that files existing at the target will always 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 if the task may appear successful. This could impact data integrity, so use the Never option with caution.
Migrate Metadata	Select this option.	Determine whether to migrate metadata. If you select this option, metadata of the migration source will be migrated. If you do not select this option, only the Content-Type and Content-Encoding metadata will be migrated.

(Optional) Configure advanced options based on Table 4.

**Table 4** Advanced options
Parameter	Example Value	Description
Sync Incremental Before Cutover	Yes	If you select Yes, an incremental migration step will be automatically added after the migration verification step in the migration phase. If you select No, the service cutover phase starts after the migration verification step in the migration phase is complete.
Filter Source Data	Select this option.	Use exclude patterns, include patterns, start time, and end time to filter files to be migrated. For details about filters, see Source Data Filters.
Send SMN Notifications	Select this option.	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.
Limit Traffic	Select this option.	Set the maximum bandwidth to be used by the migration workflow during different periods. If you do not select this option, migration traffic is not 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 when the migration task runs 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 1048576 MB/s. A maximum of five rules can be added. The time is subject to the local standard time of the region you are migrating to.

Click Next: Confirm.
Confirm the workflow settings, and click Confirm. After the Run Workflow dialog box is displayed, the workflow has been created.
- If you want to start the migration immediately, click Confirm to run the workflow.
- If you want to add a stage or step to the workflow, click Cancel. The workflow enters a Waiting state, and the migration has not started yet. To start the migration, click Run in the Operation column.