Help Center>
Distributed Cache Service>
FAQs>
Data Backup, Export, and Migration>
Why Is Memory of a DCS Redis Instance Unchanged After Data Migration Using Rump, Even If No Error Message Is Returned?
Updated on 2022-08-10 GMT+08:00
Why Is Memory of a DCS Redis Instance Unchanged After Data Migration Using Rump, Even If No Error Message Is Returned?
For details on how to use Rump, see the Data Migration Guide.
Possible causes:
- Rump does not support migration to cluster DCS instances.
- Commands are incorrectly run in Rump.
Parent topic: Data Backup, Export, and Migration
Data Backup, Export, and Migration FAQs
- How Do I Export DCS Redis Instance Data?
- Why Is Memory of a DCS Redis Instance Unchanged After Data Migration Using Rump, Even If No Error Message Is Returned?
- Can I Export Backup Data of DCS Redis Instances to RDB Files on the Console?
- Why Are Processes Frequently Killed During Data Migration?
- Where Are DCS Instance Backup Files Stored? How Are They Charged?
- Is All Data in a DCS Redis Instance Migrated During Online Migration?
- When Will AOF Rewrites Be Triggered?
- What Are the Common Causes of Redis Migration Failures?
- Can I Migrate Data to Multiple Target Instances in One Migration Task?
- How Do I Enable the SYNC and PSYNC Commands?
- Why Does Migration Task Creation Fail?
- Will the Same Keys Be Overwritten During Data Migration or Backup Import?
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
