Fault Recovery
GeminiDB can automatically create backups for your instances during the backup time window that you specified. The backups are stored based on the preset retention period (1 to 35 days).
- GeminiDB Redis provides methods for restoring instance data. For details, see Restoring Data to a New Instance.
- GeminiDB Influx provides methods for restoring instance data. For details, see Restoring Data to a New Instance.
- GeminiDB Cassandra provides methods for restoring instance data. For details, see Restoring Data to a New Instance and Restoring a Backup to a Point in Time.
- GeminiDB Mongo provides methods for restoring instance data. For details, see Restoring Data to a New or Existing Instance.
Active-active DR
GeminiDB Redis allows you to create a dual-active relationship between two instances. Once one instance becomes faulty, the other takes over workloads to ensure service continuity.
Intra-region DR
Primary GeminiDB Cassandra instances support HA. If a primary instance fails to be connected due to a natural disaster, services can be switched over to its DR instance.
Cross-region Dual-active DR
GeminiDB Cassandra supports dual-active DR and bidirectional synchronization between two instances at different regions. Once one instance becomes faulty, the other takes over read/write traffic to ensure service continuity.
Multiple-AZ Deployment
An AZ is a physical region where resources have their own independent power supply and networks. AZs are physically isolated but interconnected over a private network. Nodes of one GeminiDB instance can be evenly deployed across three AZs to provide DR support.
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
