Item | Limit |
Migration scope | Data Online Migration allows you to migrate only the data of a single bucket per task. You cannot migrate all data that belongs to your account at a time. |
Data address | When you create a data address, make sure that the data address is valid. |
Data migration | All sources that support static website hosting If the static website hosting feature is enabled for the files in the source data address, objects that do not really exist are scanned during data migration. For example, if you upload the myapp/resource/1.jpg file and enable static website hosting for the file, the following three objects are scanned during data migration: myapp/
myapp/resource/
myapp/resource/1.jpg
The myapp/ and myapp/resource/ objects fail to be migrated. The myapp/resource/1.jpg object is migrated as expected. Different types of data sources have different limits on migration. For more information, see the migration tutorials for the required types of data sources.
|
Migration bandwidth | Migration tasks may affect the continuity of your service. Proceed with caution. When Data Online Migration is used for migration, it consumes resources at the source and the destination data addresses. This may interrupt your business. If your business is important, limit the bandwidth for your migration task or start the migration task during off-peak hours. If you require higher bandwidth for data reads from a third-party cloud service, contact the provider of the cloud service to request a bandwidth increase. If the destination Object Storage Service (OSS) bucket is used by another business, make sure that the bandwidth consumed by your migration task does not affect the business. If the business requires higher bandwidth, contact technical support.
|
Result verification | To ensure data security and consistency, we recommend that you use HTTPS URLs. After a migration task is complete, you must check whether the data at the destination data address is consistent with the data at the source data address.
Warning Make sure that you verify the migrated data at the destination data address after a migration task is complete. If you delete the data at the source data address before you verify the migrated data at the destination data address, you are liable for the losses and consequences caused by any data loss. |
Archive data | Before you create a migration task to migrate data of the Archive storage class, you must manually restore the data. Take note of the following items when you restore the data: Before you create a source data address and a migration task, make sure that data of the Archive storage class is restored. Specify the number of days during which the restored data remains in the restored state based on the amount of data that you want to migrate. This can prevent data from entering the archived state during data migration. You may be charged for the restoration operation. The fee may be relatively high. For more information about the billing methods, contact the service provider that offers the source bucket.
Note Data Online Migration does not restore data in archived files at the source data address during data migration. The files that are not restored or are being restored cannot be migrated. |
Cross-border migration | During cross-border migration, we recommend that you enable the transfer acceleration feature to accelerate the migration. If you use the transfer acceleration feature to access OSS buckets, you are charged additional transfer acceleration fees. For more information, see Enable transfer acceleration. If you perform cross-border migration to migrate data from a third-party cloud service over the public bandwidth, data migration may fail and you need to retry multiple times due to network instability.
|