Creating a Migration Task

Scenarios

This section describes how to create a task to migrate your data.

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

• By default, if a task stays in a waiting state for more than 30 days, OMS automatically puts the task into a 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 destination 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 signed up for 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 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 buckets
    • Obtaining bucket locations
    • Listing objects
    • Obtaining object metadata
    • Obtaining object content
    • Listing uploaded parts
    • Restoring archived objects

    To learn 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 OMS console.
2. Click in the upper left corner and select the desired region.
3. On the Overview page, click Create Migration Task.
   Read the service disclaimer, select I have read and agree to the service disclaimer, and click OK.

   Figure 1 Creating a task
   

4. Disable Pre-migration Evaluation.
5. Configure the source and destination parameters.
   1. Configure source parameters by referring to Table 1.

      Table 1 Source parameters

      Parameter	Configuration
      Data Source	Select the cloud platform you are migrating data from.
      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 has 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 provided. If the source platform can be connected, the system will notify you.
      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.

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

      Table 3 Destination parameters

      Parameter	Configuration
      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 the Bucket drop-down list.
      Bucket	Select an OBS bucket for storing the migrated data.

6. Click Next.
7. Configure parameters in the Source Configuration area.
   1. Select the migration method File/Folder, as shown in Figure 2.
      Figure 2 Selecting a migration method
      

8. 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 3 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.

9. (Optional) Click before Advanced Settings to expand the advanced options. Configure advanced options by referring to Table 4.

   Table 4 Advanced settings

   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, you can choose to only migrate failed objects 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 it can be migrated. You can choose to enable this option if your source cloud service provider supports automatic restoration of archived data. If you enable this option, the system automatically restores and migrates archived objects in the migration task. If an archive object fails to be restored, the system skips it and 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 archive 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 do not enable 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	Decide whether to use SMN to get notifications about migration results. If you do not enable this option, no SMN message will be sent after the migration is complete. If you enable this option, 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 appear 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 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 Do I Do If SMN Does Not Work Properly?
   Traffic Limiting	Set the maximum bandwidth for the migration task during different periods. If you do not need to limit the migration traffic, disable this option. If you need to limit the 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 speed is limited to 20 MB/s when the migration task runs 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 will always skip 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 a same encryption attribute 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: With this default setting, the system will check object consistency with object size and last modification time. By CRC64 checksum: The system will check 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.

10. Click Next to enter the confirmation page.
11. 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 Next. 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 name is generated for quick identification. It is displayed in the upper left corner of the task list. It is formed by concatenating the source bucket name, the destination bucket name, and a time series identifier.