Creating a Migration Task Group

Scenarios

If there is more than 3 TB of data or more than 5 million objects to migrate in a source bucket, you can create a migration task group to migrate the source data quickly. The system will group the source objects into multiple sub-tasks for concurrent migrations.

Prerequisites

• You have registered a HUAWEI ID and enabled Huawei Cloud services.

• You have obtained the AK/SK pairs and required permissions for the source and destination platform accounts.
  • The source platform needs have the ReadOnlyAccess permission.
  • The destination platform account needs the permissions required to list buckets, obtain bucket locations, list objects, obtain object metadata, obtain object content, upload objects, list uploaded parts, and restore archive objects. For details about how to obtain these permissions, see Destination Permissions.
• You have created a bucket in OBS.
• You have created less than 1,000,000 migration tasks within the past 24 hours.
• You have less than 1,000,000 migration tasks in Waiting state.

Procedure

1. Log in to the Huawei Cloud console.
2. Click in the upper left corner and select the region where the destination bucket is located from the drop-down list.
   Figure 1 Selecting the region where the destination bucket is located
   

3. Click Service List in the upper left corner, and choose Migration > Object Storage Migration Service.
   You can also enter OMS in the search box to quickly find OMS.

   Figure 2 Choosing OMS
   

4. In the navigation pane on the left, choose Migration Task Groups.
5. On the Migration Task Groups page, click Create Migration Task in the upper right corner.
   Figure 3 Creating a migration task group
   

6. Read the service disclaimer, select I have read and agree to the service disclaimer, and click OK. The Create Migration Task Group page is displayed.
   Figure 4 Select Source/Destination
   

7. Set parameters in the Select Source area. For details, see Table 1.

   Table 1 Parameters for configuring a source bucket

   Parameter	Configuration
   Data Source	Select Tencent Cloud.
   appID	Enter the appID of your Tencent Cloud account. NOTE: You can view the appID on the account information page of the Tencent Cloud console.
   Access Key ID	Enter the SecretId of your Tencent Cloud account to which the source bucket belongs.
   Secret Access Key	Enter the SecretKey of your Tencent Cloud account to which the source bucket belongs.
   Specify Source Bucket	Disable Specify Source Bucket (This feature is disabled by default.) Select the bucket where the source data is stored from the Bucket drop-down list. OMS will check whether the source platform can be connected using the information you provided. Once the source platform is connected, all buckets in your account will be listed in the Bucket drop-down list, provided your account has the necessary permissions to list buckets. NOTE: If the source account does not have the permissions required to list buckets, you need to enable Specify Source Bucket.
   	If you enable Specify Source Bucket, you need to: Select the region where the source bucket resides from the Region drop-down list. In the Bucket text box, enter the name of the bucket or the directory to be migrated. The directory must have the bucket name included. NOTE: The entered bucket name should not contain appID. Click Connect.

8. Set parameters in the Select Destination area and click Next. For details, see Table 2.

   Table 2 Parameters for configuring a destination bucket

   Parameter	Configuration
   Access Key ID	Enter the AK for the Huawei Cloud account to which the destination bucket belongs.
   Secret Access Key	Enter the SK for the Huawei Cloud account to which the destination bucket belongs.
   Bucket	Select a destination OBS bucket for storing the migrated data.

9. Click Next. The Set Task Group Parameters page is displayed.
   Figure 5 Set Task Group Parameters
   

10. Select a migration method.
    • Object name prefix
      1. Enter the names or name prefixes of the objects to be migrated in the text box under Bucket. If no object names or name prefixes are specified, all objects in the source bucket will be migrated.
         Figure 6 Entering the names or name prefixes of objects to be migrated
         
         

         • If the files to be migrated are stored in the root directory of the source bucket, add their prefixes directly. If the files are stored in a non-root directory, add their directories and their prefixes in the format of Folder name/Prefix.
         • If no object names or prefixes are specified, all objects in the source bucket will be migrated.
         • The objects to be migrated are recorded in .txt files, and each migration task has a list file. The storage path of the files is oms/taskgroup/ in the destination bucket. These object list files will be retained after the migration, and you can manually delete them.
      2. Click Add. The system will automatically list the matched objects. You can click to delete the objects that do not need to be migrated from the list.
    • Object list
      1. In the Object List Bucket (Huawei Cloud) drop-down list, select the bucket where the list files are stored.
         

         The bucket used for storing the list files must be located in the same region as the destination bucket, or you cannot select the files.

      2. Under Object List Folder, click Select. In the displayed Object List File dialog box, select the folder where the list files are stored, and click OK.
         Figure 7 Selecting object lists
         
         

         • An object list file cannot exceed 1,024 MB.
         • A maximum of 2,000 object list files can be stored in the folder.
         • An object list file must be a .txt file, and the ContentType metadata of the file must be text/plain.
         • An object list file must be in UTF-8 without BOM.
         • Each line in an object list file can contain only one object name, and the object name must be URL encoded if it contains special characters or spaces.
         • Spaces are not allowed in each line in an object list file. Spaces may cause migration failures because they may be mistakenly identified as object names.
         • Each line in an object list file cannot be longer than 65,535 characters, or the migration will fail.
         • The ContentEncoding metadata of each object list file must be left empty, or the migration will fail.
         • Archived data can only be accessed and obtained by OMS after it is restored. If the object list files are archived, manually restore them before migration.

11. Configure parameters in the Destination Configuration area.
    1. Specify Prefix
       • If you choose to disable this feature, the names of objects remain unchanged before and after the migration.
       • If choose to enable this feature, you can specify a prefix to rename or redefine the paths for objects migrated to the destination bucket.
         Figure 8 Entering a prefix
         
         

         To learn how to use Specify Prefix, see Adding a Name Prefix or Path Prefix to Migrated Objects.

    2. Object Storage Class

       Choose the storage class that your data will be migrated to. For details about storage classes, see Storage Classes.

12. Click on the left of Advanced Settings to expand advanced options. Configure advanced options by referring to Table 3.
    Figure 9 Advanced settings
    

    Table 3 Advanced Settings parameters

    Parameter	Configuration
    Object Metadata	Determine whether to migrate metadata. If you select Do not migrate, OMS will only migrate the Content-Type and Content-Encoding metadata. If you select Migrate, OMS will migrate supported metadata. NOTICE: Only Chinese characters, English characters, digits, and hyphens (-) can be migrated. Other characters cannot be migrated. Even if you choose not to migrate metadata, the Content-Type and Content-Encoding metadata will still be migrated to ensure that the migration runs properly.
    Selective Migration	Determine whether to filter source data to be migrated by time. If you do not need to filter source data by time, disable this option. If you need to filter source data by time, enable this option and specify a date and time. Then only source data modified after the specified date and time will be migrated.
    Server-Side Encryption	Determine whether to enable server-side encryption. If you choose to disable this option, objects will not be encrypted before they are stored to the destination bucket. If you choose to enable this option, objects will be encrypted before they are stored to the destination bucket. NOTE: SSE-KMS is used by default. Other encryption methods or custom encryption is not supported. If the destination is a parallel file system (PFS), KMS encryption is not supported. Enabling KMS-based server-side encryption may slow down the migration speed by about 10%. KMS encryption is only available if KMS is supported in the region you are migrating to.
    Failed Object Record	Determine whether to record the objects that fail to be migrated. If you choose to disable this option, the system will not record the objects that fail to be migrated. If the migration fails and needs to be retried, all objects in the source bucket need to be migrated again. If you choose to enable this option, the system will record the objects that fail to be migrated. If the migration fails and needs to be retried, only failed objects need to be migrated again. NOTE: For a migration task, no matter it is contained in a task group or not, the objects that fail to be migrated are recorded in a list named after the task name, and the list is uploaded to the oms/failed_object_lists/ directory of the destination bucket. A maximum of 100,000 failed objects can be recorded in the failed object list. If more than 100,000 objects fail to be migrated in the migration task, you are advised to rectify the fault based on the existing failed object list and perform the migration again. This file contains information about the failed migration task, including the failure cause and time (in local UTC), URL-encoded names of failed objects, non-URL-encoded names of failed objects, and error codes returned by source SDKs. This file is retained in the destination bucket even after the objects in the file are successfully re-transferred. If you do not need the file, delete it manually.
    Archive Data Restoration	Archived data must be restored before being migrated. You can choose to enable this option if your source cloud service provider supports automatic restoration of archived data. If you choose to enable this option, the system automatically restores and migrates archived objects in the migration task. If an archived object fails to be restored, the system records it in the list of objects that failed to be migrated and continues to migrate other objects in the migration task. NOTICE: The following cloud service providers can automatically restore archived objects: Huawei Cloud, Alibaba Cloud, Kingsoft Cloud, and Tencent Cloud. It takes at least a minute to restore an archived object. The larger the archived object is, the longer it takes to restore it, but if an archived object cannot be restored within three minutes, the restoration fails. The time needed depends on the cloud service provider. For details, see the documentation of your source cloud service provider. Two types of fees are generated during archived data restoration: fees for API calls and fees for archived object restoration. These fees are billed by the source cloud service provider. After the restoration is complete, archived objects will be in restored state for a certain period of time. During this period, objects can be downloaded or read. After this period expires, archived objects need to be restored again for migration. For details about how long they stay in the restored state, see the documentation of the cloud service provider. The copies generated for restoring archived objects will be stored for three days by default. If there is more than 3 TB of data or more than 3 million objects in a source bucket, create a migration task group to migrate data in case the migration fails because the restored data is archived again. Pausing or restarting a migration task will result in restoration of all archived data again, no matter it has been restored or not. After objects are migrated from the source platform to Huawei Cloud, they are in the same storage class as the destination bucket. If you choose to disable this option, the system directly records archived objects in the list of objects that failed to be migrated, skips them, and continues to migrate other objects in the migration task.
    SMN Notification	Determine whether to use SMN to get notifications about migration results. If you choose disable this option, no SMN message will be sent after the migration is complete. If you choose to enable this options, you will receive an SMN message informing you of the migration results. Perform the following steps: Click Add next to the SMN Topic box. The Select SMN Topic dialog box is displayed. Select a topic for publishing SMN messages and click OK. If OMS is not authorized to publish messages to the selected SMN topic, a Warning dialog box will display after you click OK. If you need to complete the authorization, click OK to authorize OMS. Otherwise, click Cancel to return to the Select SMN Topic page and select another SMN topic. Click Add next to the SMN Template box. The Select SMN Template dialog box is displayed. If this parameter is specified, SMN messages will be sent using the specified template. The template must use the default protocol. Select a template for publishing SMN messages and click OK. Configure Trigger Condition. You can select one of the following options or both: Migration succeeded: An SMN message will be sent after the migration task succeeds. Migration failed: An SMN message will be sent after the migration task fails. NOTE: If you experience trouble in using SMN, see What Can I Do If SMN Is Not Working Properly?
    Traffic Limiting	Set the maximum bandwidth for the migration task during different periods. If you do not need to limit migration traffic, disable this option. If you need to limit migration traffic, enable this option. Perform the following steps: Specify Start Time, End Time, and Maximum Bandwidth. The maximum bandwidth ranges from 1 MB/s to 200 MB/s. NOTICE: For example, if you set Start Time to 08:00, End Time to 12:00, and Maximum Bandwidth to 20 MB/s, the maximum migration rate is limited to 20 MB/s when the migration task is running in the period from 08:00 to 12:00. The migration speed is not limited beyond this period. The time is the local standard time of the region you are migrating to. Click Add Rule. An empty traffic limiting rule is displayed. Repeat 1 and 2 to add another traffic limiting rule. You can click Delete in the Operation column to delete a rule. NOTE: A maximum of five rules can be added for a migration task. You can set traffic limiting rules in the task details even after the task is created.
    Object Overwrite	Overwrite if source newer or different size: If a source object is not as large as or was last modified more recently than its paired destination object, the source object will overwrite the destination object. Otherwise, the source object will be skipped. Never overwrite: The system always skips source objects and keeps their paired destination objects. Overwrite if different CRC64 checksum: If a source object has a CRC64 checksum different from the paired destination object, the source object will overwrite the destination object. Otherwise, the source object will be skipped. If either of them does not have a CRC64 checksum, their sizes and last modification times are checked. NOTE: This option is only available for migration on Huawei Cloud or from Alibaba Cloud or Tencent Cloud. This option is applied only when the source object has the same encryption status as the paired destination one. Always overwrite: The system always allows source objects to overwrite their paired destination objects.
    Consistency Check	By size and last modification time: This is the default setting. The system checks object consistency with object size and last modification time. By CRC64 checksum: The system checks object consistency with CRC64 checksums. If a source object and the paired destination object have CRC64 checksums, the checksums are checked. Otherwise, their sizes and last modification times are checked.
    Description	Enter a brief description about this migration task. Enter a maximum of 255 characters.

13. Click Next to enter the confirmation page.
14. Confirm the source information, destination information, task group parameters, and advanced settings, and click Next. A message is displayed indicating that the task group has been submitted. The task group is displayed in the migration task group list.

Related Operations

You can perform the following operations on a created migration task group.