Overview

Solution with OMS and Dual-Write

This practice is suitable to migration of a large amount of data, but it is expensive because your service data will be written to both the source and destination buckets.

Cross-cloud backup scenarios:

• Zero service interruptions

  Your services do not have to go down during the migration. You can adjust the service switchover time based on your service requirements.

• One-time migration and ease of use

Solution with OMS-based Multiple Incremental Migrations

This practice is suitable to rapid migration of a small amount of incremental data. The following methods can be used to quickly identify and migrate incremental data:

• Identify the incremental objects in advance and migrate these objects using the OMS object list function.
• Record the time when the previous migration task is created. When you create the next task, enable the incremental migration function of OMS and set the migration time to the time you recorded.

• Rapid migration
• Short service interruption
• Ease of use

You can use the following rule to estimate how much time will be needed for an incremental migration:

Incremental migration duration = Time required for identifying incremental objects (by comparing all objects in the source destination buckets) + Time required for migrating these incremental objects

Migrating Archived Data

This practice is suitable to migration of archive data.

Rapid migration enabled by restoration in advance