Same-Region Replication Within an Account Using OMS
Scenarios
Same-region replication within an account is to replicate data from a source bucket in one region of an account to a destination bucket in the same region of the same account.
This section describes how to replicate data between buckets of the same account in the same region using OMS console, OMS APIs, OBS APIs, OBS SDKs, OBS Browser+, and obsutil.
Replication scope: files/folders, object lists, object prefixes, URL lists, and objects modified after a specified time
Replicable object data: object content, metadata (object name, size, last modification time, creator, version number, and user-defined metadata), ACL (supported by OBS APIs and obsutil), WORM retention policy (supported by OBS APIs), object tag (supported by OBS APIs), and storage class
OBS helps you replicate your service data stored in OBS to another bucket in the same region, but Huawei Cloud has no access to your data. You need to ensure the legal compliance of your use of OBS on your own.
Constraints
The following are constraints on migrating data using Object Storage Migration Service (OMS):
|
Item |
Description |
|---|---|
|
Objects with multiple versions |
By default, OMS migrates only the latest version of objects in source buckets. |
|
Storage class of destination buckets |
The storage class of destination buckets can be Standard, Infrequent Access, Archive, or Deep Archive. |
|
Migration network |
Migrations over the Internet or intranets are supported. Migrations over private lines are not supported. |
|
Metadata migration |
Only Chinese characters, English characters, digits, and hyphens (-) can be migrated. Other characters cannot be migrated.
Chinese punctuation marks cannot be URL-encoded during the migration. If metadata contains Chinese punctuation marks, the metadata and the corresponding object will fail to be migrated.
|
|
Migration scope |
A single migration task or migration task group can only migrate data of one bucket. If data of multiple buckets needs to be migrated, you need to create multiple tasks or task groups. |
|
Symbolic links |
Symbolic link files cannot be migrated. Symbolic link files will be recorded as failed, and the migration task will also be marked as failed. Other files can be migrated normally. If the source contains symbolic links, you need to enter the actual file path. |
|
Migration of object ACLs |
OMS cannot migrate object ACLs. |
|
Migration speed |
Generally, OMS can migrate 10 TB to 20 TB of data per day. For higher migration efficiency, you are advised to use storage migration workflows on MgC. MgC allows you to migrate data using dedicated, scalable migration clusters and up to 20 Gbit/s of bandwidth. However, the speed depends on the number and size of source objects, bandwidth, and transmission distance over the Internet between the source and destination buckets. You are advised to create a migration task to test the migration speed. The maximum migration speed is five times the average speed of a single task because up to five tasks can be executed concurrently in a region by default. If you need to define a higher number of concurrent tasks, you can create a storage migration workflow on MgC. |
|
Archived data |
You need to restore archived data before the migration. Note that when there is archived data to be migrated, you need to:
|
|
Migration tasks |
A maximum of five concurrent migration tasks are allowed for your account per region.
NOTE:
If your destination regions are CN North-Beijing1 and CN South-Guangzhou, you can run up to 10 migration tasks concurrently. |
|
A maximum of 1,000,000 migration tasks can be created in your account per region within a 24-hour period. |
|
|
Migration Task Groups |
A maximum of five concurrent migration task groups are allowed for your account per region.
NOTE:
If your destination regions are CN North-Beijing1 and CN South-Guangzhou, you can run up to 10 migration task groups concurrently. |
|
Synchronization tasks |
Synchronization tasks share quotas with migration tasks and migration task groups, but enjoy a higher priority. A maximum of five concurrent synchronization tasks are allowed for your account per region. |
|
Object list files |
|
|
URL list files |
|
|
Failed object list files |
A maximum of 100,000 failed objects can be recorded in a list file.
NOTE:
If more than 100,000 objects fail to be migrated in a migration task, you are advised to rectify the fault based on the existing failed object list and perform the migration again. |
Billing for Same-Region Replication Within an Account
- When you use the OMS console or APIs to migrate data, OBS APIs of the source and destination ends are invoked to upload and download data. You will be billed for the API requests and data download traffic. For details, see OMS Billing. In addition, you will be billed for storing the objects in the destination bucket. For details, see Storage Costs.
- When you use OBS APIs, SDKs, Browser+, or obsutil to replicate data within the same region, you will be billed for requests and storage. For details, see Table 2.
Table 2 Billing for data replication in the same region Action
Billing Item
Description
Billing Mode
Replicate data in the same region
Requests
You are billed for the number of successfully replicated objects. Successfully replicating one object creates a copy request. For details, see Copying Objects.
To learn about the request billing, see Requests.
Pay-per-use
Data transfer
Free, because data in the same region is replicated over an intranet.
N/A
Storage space
Storage space occupied by objects stored in the destination bucket.
If you have specified another storage class for object copies in the destination bucket, these copies are billed based on the new storage class.
Pay-per-use
Resource packages
Prerequisites
- A source bucket has been created in a region of an account.
- A destination bucket has been created in the same region of the same account. To create a bucket, see Creating a Bucket.
Same-Region Replication Within an Account
You can use the OMS console or APIs to migrate data within the same account and region or use OBS APIs, SDKs, or obsutil to replicate data within the same account and region.
OMS does not automatically migrate data. That is, data changes in the source bucket will not be automatically synchronized to the destination bucket. After data in the source bucket is modified, you need to execute the migration task again to synchronize the incremental data in the source bucket to the destination bucket.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
