Cross-AZ Disaster Recovery
Cross-AZ deployment is supported for disaster recovery. The source (local) and the replica (remote) are located at different AZs in the same city, with data replicated in real time via Tencent Direct Connect. The local source instance will get the request for data access first. If it is down or inaccessible, the request will go to the remote replica instance. The source/replica switchover is transparent to the user and removes the operational concerns associated with single-IDC deployment, with IDC downtime completely transparent to the business.
Cross-Region Disaster Recovery
Cross-region disaster recovery instances are supported to help you perform remote data sync for disaster recovery over the private network. When the source instances fail or become unavailable for other reasons, the remote disaster recovery instances allow you to quickly recover data access by setting up a business system and redirecting access traffic remotely. When data is synced from the source instances to the disaster recovery instances, data write performance will be limited. You can promote the disaster recovery instances to source instances in the web-based console and disconnect them from the data sync to resume their full performance. The promotion process takes only a few seconds, minimizing the impact of business interruption in the disaster.
Financial Solution for Three IDCs in Two Regions
TencentDB for MySQL offers deployment architectures for two IDCs in the same city and three IDCs in two different regions. When a failure occurs, you can restore normal database operations in minutes. This solution can be achieved with just a few clicks on the configuration page: select MySQL cross-AZ deployment and strong sync data replication to achieve the solution for two IDCs in the same city with strong data consistency; add a remote disaster recovery node to the cluster to achieve the architecture for three IDCs in two different regions.
Completed Hot Backup and Cold Backup
Physical machines with the same architecture are used to provide real-time hot backup. Based on cold backup and binlog files, data within 3 days can be recovered losslessly and cold backup data within 5 days can be dumped, making data recovery more secure.
Automatic Disaster Recovery
Automatic downtime detection and failover are supported. During source/replica switch, VIP is used to make the switch processes transparent to you, so you don't need to worry about the issues caused by failure and downtime of physical machines. You can finish the hot backup switch with no changes to the application layer, which is imperceptive to the business.