eSurfing Cloud DCS Redis uses a variety of data protection measures to ensure the security of your data on Redis instances.
Disaster Recovery
Depending on the reliability requirements for your data and services, you can deploy Redis instances in one AZ (a single server room) or across multiple AZs (intra-city disaster recovery AZs) when creating a Redis instance. For details, see Disaster Recovery Policies.
Replica Redundancy
After you create a standard active/standby, active/standby cluster, or active/standby cluster Redis instance, the instance is deployed with active and standby nodes. The standby node maintains cache data consistency through incremental data synchronization. When a network exception or node failure occurs, automatic failover between the active/standby nodes will ensure service continuity, and a full synchronization will be performed after recovery from the fault to maintain data consistency. For details, see Active/Standby Introduction, Active/Standby Cluster Introduction, and Active/Standby Cluster Introduction.
Data Persistence
In the daily operation of business systems, there is a small probability that some abnormal events occur. For those business systems that have extremely high reliability requirements, in addition to ensuring the HA of DCS instances, these systems also require security protection, recoverability, and even permanent data backup for cached data. In this way, when an exception occurs in the DCS instance, the backup data can be used for recovery, thereby ensuring the normal operation of the business. eSurfing Cloud DCS Redis deeply optimizes the persistence kernel mechanism. It persists data on disk by means of persistent unloading mode of RDB+AOF snapshots, which not only provides high-speed data read-write capabilities, but also meets data persistence requirements. It also supports automatic data backup, powerful data disaster tolerance, and backup & recovery with one click. For detailed backup and restoration operations, see Instance Backup and Restoration Management.