Help Center/ Object Storage Service/ Best Practices/ Migrating Data to OBS/ Migrating Data from a Third-Party Vendor to OBS
Updated on 2024-10-17 GMT+08:00

Migrating Data from a Third-Party Vendor to OBS

Usually, if you want to migrate a large amount of data stored on a third-party vendor's cloud to OBS, you need to download the data to your local server and then upload the data to OBS using OBS Console or other clients. The entire process is time- and labor-consuming, and also likely to encounter problems such as missing or incorrect transmission.

To address these problems, Huawei Cloud offers Object Storage Migration Service (OMS). With OMS, you can easily migrate data from a third-party cloud to OBS by only configuring connection parameters and migration tasks on OBS Console. Table 1 describes the migration solutions for you to choose from based on your needs.

Table 1 Migration solutions

Solution

Application Scenario

Supported Migration Source

Migration Speed

Pricing

Using OMS to Migrate Data

Full or incremental migration of large-scale object data (less than 500 TB)

See Third-Party Cloud Service Vendors Supported by OMS.

10 TB to 20 TB per day

See OMS Pricing Details.

Using Back to Source by Mirroring to Migrate Data (under beta testing)

Scenarios where data is seamlessly migrated to OBS. That is, service data is stored on the origin server created by the user and needs to be migrated to OBS without interrupting services.

Origin servers created by users

N/A

The price is subject to the billing mode of third-party cloud service vendors on cloud data reading.

To migrate data over 500 TB, you can submit a service ticket or contact customer service to ask for a tailored, cost-effective solution.

Using OMS to Migrate Data

OMS is an online data migration service that helps you securely and efficiently migrate your object data from other cloud service vendors to Huawei Cloud. During data migration, HTTPS data encryption channels are used to secure data transmission. If the data changes, only changed objects are migrated, lowering migration costs.

Figure 1 Migrating data to OBS using OMS
  1. Create an OBS bucket.

    Log in to OBS Console and create a bucket for storing migrated data.

  2. Create a migration task.

    On OMS Console, create a migration task and associate a third-party cloud service vendor (source) with OBS (destination) by configuring parameters such as access keys and bucket names.

    For details, see Creating an Object Storage Migration Task.

  3. Start data migration.

    Perform the OMS migration task. You can view the task progress and the migration result on OMS Console.

Using Back to Source by Mirroring to Migrate Data

Usually, if OBS does not contain the data requested by a client, a 404 error is returned to the client. However, OBS provides the back-to-source function (by mirroring) to help you obtain the requested data from its source site if it is not found in OBS.

If data that cannot be found in a bucket with back-to-source mirroring configured meet user-defined back-to-source rules, OBS will pull the data from the origin server and then return it to you. This process does not interrupt services. You can use this function to seamlessly migrate data from your source site to OBS at low costs. Figure 2 illustrates the mirroring back-to-source process.

Figure 2 Process of mirroring-based back to source

See Configuring a Back-to-Source Rule.