Reliability Functions
Cluster HA
DCS provides master/standby, Proxy Cluster, and Redis Cluster instances. Each instance has multiple nodes for instance-level DR. If the master node is faulty, a failover is triggered automatically. Services may be interrupted for less than half a minute during exception detection and the failover.
Data Backup and Restoration
Data in DCS instances can be backed up to OBS. If a DCS instance becomes faulty, data in the instance can be restored from the backup. DCS instances support scheduled and manual backup. Backup is scheduled in days, can be stored for a maximum of seven days, and at least one backup file is retained. Users can perform manual backup before service system maintenance, upgrade, and other high-risk operations. The retention period is not limited.
DCS instances can be restored from a specified backup set. During the restoration, DCS instances do not accept data operation requests from clients because existing data is being overwritten by the backup data.
For details, see DCS Backup and Restoration Overview.
Cross-AZ DR
Cross-AZ DR is supported for master/standby, Redis Cluster, and Proxy Cluster DCS instances. If one AZ is faulty, nodes in another AZ are not affected. The standby node automatically becomes the master node and takes over services.
Monitoring
Using Cloud Eye, you can monitor DCS resources such as vCPUs, memory, disks, and networks.
For details, see DCS Metrics.
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