Migrating Data from MinIO to Huawei Cloud OBS Using HTTP

Supported Regions

The following regions are supported:

• LA-Santiago
• LA-Sao Paulo
• TR-Istanbul
• AP-Bangkok
• AP-Singapore
• AP-Jakarta
• ME-Riyadh

A single object cannot be larger than 4.76837158203125 TB (500 MB x 10,000). Otherwise, the migration may fail.

Preparations

• Preparing a Huawei account

  Before using MgC, prepare a HUAWEI ID or an IAM user that can access MgC and obtain an AK/SK pair for the account or IAM user. For details about how to obtain an access key, see Making Preparations.

• Creating a migration project

  On the MgC console, create a migration project. For details, see Managing Migration Projects.

• Creating an OBS Bucket

  On Huawei Cloud OBS, create a Standard bucket in the target region for storing URL list files and receiving source data. For details, see Creating a Bucket.

  If an IAM user is used for migration, the IAM user must have the read and write permissions for the target bucket. For details, see Granting an IAM User the Read/Write Permissions for a Bucket.

• Creating a migration cluster

  You can create a dedicated migration cluster for this task. A cluster consists of a master node, and several list and migration nodes. For details about how to create a cluster, see Creating a Migration Cluster.

Step 1: Generate URLs for Sharing and Downloading MinIO Files

Replace minioLink, bucket-public01, and http://100.85.xxx.xx:xxxx in the following steps with the actual MinIO alias, bucket name, and access address.

1. Open the CLI on the server where MinIO is deployed.
2. Run the mc command to share file and generate URLs for downloading the file. The command format is as follows:

   mc share download --recursive --expire=<EXPIRE-IN-HOURS> <MINIO-ALIAS>/<BUCKET-NAME>/

   • --recursive: recursively shares files in all subdirectories.
   • --expire=<EXPIRE-IN-HOURS>: The expiration time of the share URLs, in hours. The maximum duration is 7 days (168 hours).
   • <MINIO-ALIAS>: user-defined alias of the MinIO service deployment.
   • <BUCKET-NAME>: bucket name

   For example, you have a bucket named bucket-public01. The bucket contains two files (dragon.png and share2.txt) and one subfolder (urlpath). The subfolder contains one file (share2.txt).

   

   

   Assume that you want to generate URLs for sharing and downloading all files in the bucket, set the URLs to expire after 12 hours, and save the URLs in the test2.txt file. You can run the following command:

   mc share download --recursive --expire=12h minioLink/bucket-public01/ >> test2.txt

   After the command is executed, the share URLs of the three files are generated and saved in the test2.txt file.

   

3. Open the generated URL list file (test2.txt in this example) and you will see the share URL for each file. Try to access these URLs using a browser to check whether the URLs are valid.

   If any URLs cannot be accessed, check whether the corresponding files are readable. If they are, generate URLs for them again.

4. Based on the MgC requirements, edit the URL list file to include the shared URLs and file names in the following format:

   <SHARED-URL> <FILE-NAME>

   A share URL and file name are separated by a tab character. The name of a file in a subfolder must contain the subfolder name.. For more requirements and restrictions on the URL list file, see What Are the Restrictions on Using MgC for Storage Migration?

   For example:

   http://100.85.xxx.xx:xxxx/bucket-public01/dragon.png dragon.png 
   http://100.85.xxx.xx:xxxx/bucket-public01/share2.txt share2.txt 
   http://100.85..xxx.xx:xxxx/bucket-public01/urlpath/share2.txt urlpath/share2.txt

5. After editing all URLs as required and verifying that the URLs are correct, save the URL list file.

Step 2: Upload the URL List File to the OBS Bucket

1. Sign in to the OBS console. In the navigation pane, choose Buckets.
2. In the bucket list, click the created OBS bucket to go to the Objects page.
3. Click Create Folder, enter a folder name (for example, minioUrl), and click OK.
4. Click the name of the folder created in the previous step. Click Upload Object.
5. Upload the URL list file (test2.txt in this example) to the folder in either of the following ways:
   • Drag the URL list file to the Upload Object box and click Upload.
   • In the Upload Object box, click add files, select the URL list file, and click Upload.

Step 2: Create a Storage Migration Workflow

1. Sign in to the MgC console.
2. In the navigation pane on the left, choose Migrate > Workflows. In the upper left corner of the page, select the migration project you created.
3. Click Create Workflow in the upper right corner of the page.

   

4. Select Storage Migration and click Configure Workflow.

   

5. Set workflow basics based on Table 1.

   

   Table 1 Basic parameters

   Parameter	Description
   Name	User-defined
   Region	Select the region where the target bucket is located from the drop-down list.
   Description	User-defined
   Cluster	Select the created cluster.

6. Configure the migration source and target based on Table 2 and Table 3.

   

   Table 2 Parameters for configuring a migration source

   Parameter	Description
   Location Type	Select HTTP/HTTPS Source.
   List Path	Enter the name of the folder (minioUrl/ in this example) where the URL list file is stored. Note that the folder name must be suffixed with a slash (/).

   Table 3 Parameters for configuring a migration target

   Parameter	Description
   Location Type	Select Huawei Cloud OBS.
   AK	Enter the AK/SK pair of the target Huawei Cloud account. The account must have the read and write permissions for the target bucket.
   SK
   Bucket	Select the created OBS bucket.
   Endpoint	Enter the endpoint of the region where the target bucket is located. For example, if the target bucket is located in the CN North-Beijing4 region of Huawei Cloud, enter obs.cn-north-4.myhuaweicloud.com. NOTE: You can view the endpoint in the OBS bucket overview.
   Specify Prefix	This parameter is optional. Specify a prefix to rename or relocate objects migrated to the target bucket. For example, if you specify the prefix /D, source file /A/B/C.txt will be relocated to /D/A/B/C.txt after being migrated to the target bucket. For details, see: Adding a Name Prefix or Path Prefix to Migrated Objects

7. Configure the migration settings based on Table 4.

   

   Table 4 Migration settings

   Parameter	Option	Description
   Task Type	List migration	Migrates objects recorded in the list files.
   Concurrent Subtasks	-	Specify the maximum number of concurrent subtasks. There cannot be more than 10 concurrent subtasks for each online migration node. For example, if there are 2 online migration nodes, the maximum number of subtasks can be 20 or any number below.
   Overwrite Existing	Never	Files existing at the migration target will never 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 a migration task is paused or interrupted and then restarted or resumed, the Never option will cause the system to skip files that were not completely migrated earlier, but the task may still be marked as successful. This affects data integrity. To avoid this issue, use the Never option with caution.
   	Always	Files existing at the migration target will always be overwritten.
   	If older or different size	Files that already exist at the target will be overwritten if they are older than or have different sizes from the paired files at the source. Verification will be performed for folders after their contents are migrated. Folders that already exist at the target will be overwritten if they have different last modification times, sizes,or permissions from the paired folders at the source. NOTE: For empty folders, the overwrite policy is the same as that for files.
   Clear Cluster	-	Determine whether to clear the migration cluster after the migration is complete. If you select this option, a step for clearing the migration cluster will be created in the workflow. You can also choose whether to clear resources used by the cluster, such as NAT gateways, security groups, and VPCEP resources. If you do not select this option, a step for clearing the migration cluster will not be created in the workflow.

8. (Optional) Configure advanced options based on Table 5.

   Table 5 Advanced options

   Parameter	Description
   Target Storage Class	Choose the storage class that your data will be migrated to in the target bucket. For details about storage classes, see Introduction to Storage Classes.
   Enable KMS Encryption	If you do not select this option, objects are in the same encryption status before and after the migration. If you select this option, all migrated objects will be encrypted before they are stored in the target bucket. NOTE: Using KMS to encrypt migrated data may slow down the migration speed by about 10%. This option is only available when KMS is supported in the region you are migrating to.
   Filter Source Data	Filter files to be migrated by applying filters. For details about filters, see Source Data Filters.
   Send SMN Notification	Determine whether to use SMN to get notifications about migration results. If you do not select this option, no SMN messages are sent after the migration is complete. If you select this option, after the migration is complete, SMN messages are sent to the subscribers of the selected topic. You can select the language and trigger conditions for sending messages.
   Limit Traffic	Allocate the maximum bandwidth to be used by the workflow during a specified period. If you do not select this option, migration traffic is not limited. If you select this option, 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 beyond this period. NOTE: The rate limit ranges from 0 MB/s to 1,048,576 MB/s. A maximum of five rules can be added. The time is the local standard time of the region you are migrating to.
   Schedule Migration	Schedule the migration to run during a period. If you do not select this option, you need to manually start or stop the migration. If you select this option, the migration runs during the specified period and stops beyond that period. For example: If you set Start Time to 08:00 and End Time to 12:00, the migration task runs from 08:00 to 12:00 every day. The migration stops beyond that period. If you set Start Time to 12:00 and End Time to 08:00, the migration runs from 12:00 of the current day to 08:00 of the next day. The migration stops beyond that period.

9. Click Next: Confirm.
10. Confirm the workflow settings and click Confirm. In the displayed dialog box, click Confirm to run the workflow immediately.
11. In the workflow list, click the workflow name to go to its details page. You can view the configuration information and migration progress of the workflow.