Item | Prerequisites |
Migration of Multi-version Objects | By default, only the latest versions of objects among multi-version objects on the source side are migrated. Object storage data of historical versions cannot be migrated. |
Scope of Migration | Only data in a single bucket can be migrated in a single task (migration task). If data in multiple buckets are to be migrated, you must create multiple tasks. |
Migration Task | For the same user, a maximum of five concurrent tasks are supported in a Region. A maximum of 5000 migration tasks can be created in a Region within 24 hours. |
Object List File | The size of the object list file cannot exceed 1024 MB. An object list file must be in .txt format, and ContentType in the metadata of the file can only be text/plain. An object list file must be in UTF-8 encoding format without a BOM. An object list file can contain only one object name per line, and object names are encoded using URL Encode. Do not add invalid spaces to each line in the object list file. Otherwise, the spaces will be included in the object name, resulting in migration failure. Each line in the object list file should not exceed 65535 in length. Otherwise, the migration will fail. Do not set ContentEncoding in the metadata of the object list file. Otherwise, the migration fails. |
Migration Failure List File | A single task failure object list contains a maximum of 100,000 failed objects. |
Character Limit | Chinese characters or Chinese symbols (whether encoded or not) cannot be migrated. |
Migration Speed | The migration speed depends on the number and size of objects on the source server, bandwidth, and transmission distance over the Internet. The actual maximum migration speed is five times the average speed of a single task. A maximum of five concurrent tasks are supported in a Region. |
Pullup and Support Limit of Complex Applications | When migrating complex businesses, record business information, and migrate, switch, and test business systems as needed. During application switching, you must stop related service processes to ensure consistency. After switching, relevant personnel familiar with the businesses should test and verify the migration so as to reduce downtime. |
Specific Requirements | If there are specific requirements such as confidential files and IP addresses that need to remain unchanged, you must submit a ticket for technical consultation to meet the corresponding requirements. |
Service Statement
You may not copy, distribute, transfer, license, or allow others to use eSurfing Cloud Migration Service (CMS) without the prior written consent of eSurfing Cloud.
Do not imitate, modify, translate, adapt, lend, sell, sublicense, disseminate, or transfer the services on this website. Do not perform reverse engineering, decompile, disassemble, or otherwise attempt to discover the source code of this site. For more information, see eSurfing Cloud Migration Service Agreement
Data Template Import Statement
After downloading the offline template based on the migration platform, fill in the specifications carefully and accurately. The Cloud Migration Service (CMS) is not responsible for data errors or other problems caused by incorrect template information.
Evaluation Result Statement
When using the cloud migration cost analysis capability of the CMS, fill out the data template accurately. This feature is designed to help users quickly implement eSurfing Cloud product mapping and cost analysis & comparison and then assist users in selecting cloud migration options that suit their needs. The Cloud Migration Service (CMS) is not responsible for price differences caused by incorrect data template information.
Assistant Tool Use Statement
When using the migration service tool of the CMS, ensure that the tool is used for its intended purposes. The Cloud Migration Service (CMS) is not responsible for any non-intended purposes.