Creating a Storage Migration Plan

Prerequisites

• Object storage buckets to be migrated have been discovered over the Internet.
• (Optional) A deep collection has been performed for the object storage buckets to be migrated.

Notes

• A migration plan can be used to migrate buckets from the same source platform and to the same target region.
• A source bucket can be included in multiple migration plans.
• Source buckets in a migration plan may have different prefixes. You can give them the same prefix after they are migrated to the target bucket.

Procedure

1. Log in to the MgC console. In the navigation pane, choose Design > Migration Plans.
2. Click Create Migration Plan in the upper right corner of the page.
3. In the Batch Object Storage Migration card, click Configure Migration Plan.
4. In the Basic Settings area, set parameters listed in Table 1.

   Table 1 Basic settings

   Parameter	Configuration
   Migration Plan Name	User-defined
   Description (Optional)	User-defined
   Source Platform	Select the cloud platform where the source resources are located.
   Target Region	Select the region where the target bucket is located.

5. Above the source bucket list, click Add.
6. Select the buckets to be migrated and click Confirm. Click Modify in the Operation column to configure the migration method for each bucket. For details about migration methods, see Table 2.
   

   • The selected resources must come from the source platform selected in Basic Settings.
   • A maximum of 100 buckets can be added.

   Table 2 Migration methods

   Migration Method	Description
   Full migration	Migrates all data in the source bucket or specified paths.
   List migration	Migrates objects recorded in the list files. The list files must be stored in the target bucket.
   Prefix migration	Migrates objects matched with the specified names or prefixes.

7. In the list of buckets to be migrated, click Modify in the Operation column.
8. Select the source credentials. It is best to enter the total number and size of objects to be migrated. Then click Confirm.
   • If the migration method configured for the bucket is List migration, in the List Path box, enter the directory that stores the lists of objects to be migrated. The directory must end with a slash (/).
   • If the migration method configured for the bucket is Prefix migration, add the names or prefixes of objects to be migrated. Note that you need to click Save each time you add an object name or prefix.
     

     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 name prefixes in the format of Directory/Prefix.

9. After you configure the migration settings for all buckets to be migrated, click Next.
10. For each source bucket, click Modify in the Operation column. Then select the credential used for accessing the target bucket, specify the target bucket, enter a prefix to rename or relocate migrated objects, and click Save.
11. After you configure the target bucket settings for all buckets to be migrated, click Next. You can assess how large of a migration cluster is required for the migration and then create a migration cluster with the recommended specifications. Alternatively, you can skip this step and use an existing migration cluster. For details about how to create a cluster, see Creating a Migration Cluster.
12. Click Next to select an existing migration cluster. All resources in this plan will be migrated using this cluster.
13. Click Select Cluster. The Select Cluster dialog box is displayed on the right.
14. In the cluster list, select the cluster you want to use and click Confirm. If you want to modify an existing cluster to meet your requirements, see Managing a Migration Cluster.
15. Click OK. After migration plan is created, you can see it in the list.
    • If you need to modify the plan settings, click Design in the Operation column.
    • After Progress appears as Completed, click Create Workflow in the Operation column to create a migration workflow to migrate all buckets in the plan in a batch.