What Can I Do If the Migration Fails Because the Frequency of Accessing the Source Object Storage Exceeded the Upper Limit?
To ensure a fast migration, OMS invokes the source object storage API at a high frequency during the migration task execution. Some source cloud vendors have set an upper limit on the frequency of accessing their object storage. If the access frequency exceeded the upper limit, the migration task fails.
- Contact the source cloud vendor to change the frequency upper limit to meet migration requirements.
- Create a task using the API and specify a smaller value for thread_num (number of threads used by the migration task) to reduce the access frequency of the migration threads.
Exception Recovery FAQs
- What Can I Do If Migration Tasks Fail To Be Created After Evaluation?
- What Can I Do If the Migration Fails Because the Frequency of Accessing the Source Object Storage Exceeded the Upper Limit?
- What Can I Do If a Migration Task Fails?
- What Can I Do If a Migration Task Group Fails to Be Executed?
- What Can I Do If SMN Is Not Working Properly?
- What Can I Do If a Migration Task Fails Due to Inconsistent Encryption Status?
- What Can I Do If the Migration Task Failed Due to an Archive Data Read Failure?
- What Problems May I Encounter If CDN Is Enabled at the Source?
- What Do I Do If All Objects Whose Names Contain Slashes (/) Fail to be Migrated from Alibaba Cloud?
- How Do I Resolve the Error "Failed to access the object. Make sure that the object exists and you have the rights to access" When I Enter Object Prefixes?
- What Can I Do If Consistency Checks Fail During the Migration of Data in a Parallel File System?
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.
Chatbotmore