What Are the Restrictions on Using MgC for Storage Migration?
The following table lists the constraints on storage migration using MgC.
Item |
Constraint |
---|---|
Objects with multiple versions |
By default, only the latest version of objects in source buckets is migrated. |
Storage class of target buckets |
The storage class of target buckets can only be Standard or Infrequent Access. You can change the storage class of target buckets after the migration is complete. |
Migration object |
|
Migration network |
Migrations over private and public networks are supported. |
Symbolic links |
|
Migration scope |
You can migrate a single bucket or multiple buckets in batches. |
Metadata migration |
Metadata migration is not supported for heterogeneous migrations. |
Archived data |
To migrate archived data from object storage, you must restore it first. You need to:
|
Concurrent subtasks |
You can define the number of concurrent subtasks based on the number of online migration nodes. 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. |
Object list files |
These files must be stored in the same region as the target 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