Creating a Migration Task

Scenarios

This section describes how to create a task to migrate your source objects.

The following uses the File/Folder migration method as an example.

• By default, if a task stays in waiting state for more than 30 days, OMS automatically puts the task into Failed state and clears the AK/SK pair used by the task. To prevent task failures caused by blocking, do not create tasks too frequently.
• If an object is larger than 500 GB, migrating it takes a long time. You can submit a service ticket to whitelist the object for migration in segments.
• During the migration, the system automatically creates a temporary folder named OMS in the target bucket. Do not perform any operations on this folder, including but not limited to modifying, deleting, or adding data in the folder. Otherwise, the migration will be interrupted or fail.

Background

OMS supports the following migration sources:

• Huawei Cloud
• AWS
• Alibaba Cloud
• Microsoft Azure
• Tencent Cloud
• Google Cloud
• Qiniu Cloud
• QingCloud
• Baidu Cloud
• Kingsoft Cloud
• UCloud
• HTTP/HTTPS data sources

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 account needs the permissions for:
    • Listing all buckets
    • Obtaining bucket locations
    • Listing objects
    • Obtaining object metadata
    • Obtaining object content

    To learn how to obtain these permissions, see Source Permissions.

  • The destination platform account needs the permissions for:
    • Listing all buckets
    • Obtaining bucket locations
    • Listing objects
    • Obtaining object metadata
    • Obtaining object content
    • Listing uploaded parts
    • Restoring archive objects

    To learn how to obtain these permissions, see Destination Permissions.

• You have created at least one bucket on 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 OMS console.
2. Click in the upper left corner and select the desired region.
3. Click Create Migration Task in the upper right corner.
   Read the service disclaimer, select I have read and agree to the service disclaimer, and click OK.

   Figure 1 Creating a task
   

4. On the Select Source/Destination page, perform the following operations:
   1. Configure source parameters. For details, see Table 1.

      Table 1 Source parameters

      Parameter	Operation
      Data Source	Select the cloud platform from which you are migrating data.
      Access Key ID	Enter the AK for accessing the source platform. It can contain a maximum of 100 characters.
      Secret Access Key	Enter the SK for accessing the source platform. The SK matches the AK, and they group into a pair. It can contain a maximum of 100 characters.
      Specify Source Bucket	Enable this option if your source account does not have the permissions required to list buckets but have the permissions to list objects in buckets, obtain object metadata, and obtain objects. Then specify the bucket or path to be migrated. For details, see Table 2.

      Table 2 Description of Specify Source Bucket

      If You...	Then...
      Enable Specify Source Bucket	Select the region where the source bucket is located from the Region drop-down list. In the Bucket text box, enter the bucket or the path to be migrated. The path must have the bucket name included. For example, if the source bucket is obs-test, Enter obs-test to migrate all data in the source bucket. Enter a path in format of Bucket name/Path, for example, obs-test/file, to migrate data in that path. Click Connect. OMS will check whether the source platform can be connected using the information you entered. If the source platform can be connected, the system will prompt you.
      Disable Specify Source Bucket (This feature is disabled by default.)	Click List Buckets. OMS will check whether the source platform can be connected using the information you entered. After the source platform is connected, all buckets in your account will be listed in the Bucket drop-down list on the premises that your account has the permissions needed to list buckets. In the Bucket drop-down list, select the bucket where the data to be migrated is stored.

   2. Configure destination parameters. For details, see Table 3.

      Table 3 Destination parameters

      Parameter	Operation
      Access Key ID	Enter the AK for accessing Huawei Cloud. It can contain a maximum of 100 characters.
      Secret Access Key	Enter the SK for accessing Huawei Cloud. The SK matches the AK, and they group into a pair. It can contain a maximum of 100 characters. Then click List Buckets.
      Bucket	Select a destination OBS bucket for storing the migrated data.

5. Click Next.
6. Set parameters in the Source Configuration area.
   1. Select the migration method File/Folder, as shown in Figure 2.
      Figure 2 Selecting a migration method
      
   2. Determine whether to migrate metadata.
      

      • Only English characters, numbers, and hyphens (-) in metadata can be migrated. Chinese characters and symbols cannot be migrated, regardless of whether they are encoded.
      • Even if you choose not to migrate metadata, the Content-Type metadata will still be migrated to ensure that the migration runs properly.
   3. Set Selective Migration.
      • If you do not need to filter source data by time, set this option to No.
      • If you need to filter source data by time, set this option to Yes. Then only source data modified after the specified time will be migrated.

7. Configure parameters in the Destination Configuration area.
   1. Data Encryption If the destination bucket is a parallel file system (PFS), KMS encryption is not supported.
      • If KMS is not selected, all migrated objects will not be encrypted before they are stored into the destination bucket.
      • If KMS is selected, all migrated objects will be encrypted before they are stored into the destination bucket.
        

        • Using KMS to encrypt migrated data may decrease the migration speed by about 10%.
        • Data encryption is only available if KMS encryption is supported in the region you are migrating to.
   2. Specify Prefix
      • If this option is set to No, the names of objects remain unchanged before and after the migration.
      • If this option is set to Yes, you can specify a prefix to rename or redefine the paths of objects migrated to the destination bucket.
        Figure 3 Specifying a prefix
        
        

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

   3. Object Storage Class

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

8. (Optional) Click Show next to Advanced Settings to expand the advanced options. Configure advanced options by referring to Table 4.

   Table 4 Advanced Settings parameters

   Parameter	Configuration
   Failed Object Record	Determine whether to record the objects that fail to be migrated. If this option is set to No, 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 this option is set to Yes, 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	Archive data must be restored before being migrated. You can select this option if the source cloud service provider supports automatic restoration of archive data. If you select this option, the system automatically restores and migrates archive objects in the migration task. If an archive 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. CAUTION: Currently, the following cloud platforms can automatically restore archive objects: Huawei Cloud, Alibaba Cloud, Kingsoft Cloud, and Tencent Cloud. The system will restore archive data before migrating it, and you will pay to the source cloud service provider for the API requests and storage space generated accordingly. The copies generated for restoring archive data 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 archive data again, no matter it has been restored or not. After data is migrated from the source platform to Huawei Cloud, the storage class of the migrated data is the same as that of the destination bucket. If you do not select this option, the system directly records archive 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	Decide whether to use SMN to get notifications about migration results. Set to No No SMN message is sent after the migration. Set to Yes You will receive an SMN message informing you of the migration results. Perform the following steps to set SMN parameters: Click Add next to SMN Topic. The Select SMN Topic dialog box is displayed. Select a topic for receiving 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 the authorization, click OK to authorize OMS. Otherwise, click Cancel to return to the Select SMN Topic page and select another SMN topic. Configure Trigger Condition. You can select one of the following options or both: Migration succeeded An SMN message will be sent if the migration task succeeds. Migration failed An SMN message will be sent if the migration task fails. NOTE: If you experience trouble in using SMN, see What 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, select No. If you need to limit migration traffic, select Yes. Perform the following steps to set traffic limits: Click Add Rule. A traffic limiting rule is displayed. 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. Repeat 1 and 2 to add another traffic limiting rule. You can click 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 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.
   Priority	If there are a large number of tasks, you can set task priorities to control which tasks take precedence over other tasks.
   Description	In the Description area, enter a maximum of 255 characters to briefly describe the migration task.

9. Click Next to enter the confirmation page.
10. Confirm the migration settings and start the migration.
    1. Check that the migration settings are correct.

       If the settings are incorrect, click Previous to return to the previous page for modification.

    2. Click Migrate Now. A message is displayed, indicating that the migration task is created successfully.

       You can see that the migration task is displayed in the task list.

       For details about migration task statuses, see Viewing a Migration Task.

       

       After the task is created, a task ID is generated for quick identification. It is displayed in the upper left corner of the task list. It is composed of the source bucket name, destination bucket name, and time sequence ID.