tencent cloud

Direct Connect

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Features
Application Scenarios
Use Limits
Connection Access Point
Relevant Products
Network Planning
Purchase Guide
Billing Overview
Purchasing in the Console
Renewing Connections
Getting Started
Operation Guide
Connections
Direct Connect Gateways
Dedicated Tunnels
Monitoring and Alarming
MACsec Encryption
Cloud Exchange
Cloud Access Management
Overview
Access Policy Types
Access Policy Syntax
Practical Tutorial
Connecting a Local IDC to CVM by Using a VPC NAT Gateway and Direct Connect
Hybrid Cloud Primary/Secondary Communication (DC and VPN)
Best Practices on Direct Connect High Availability and Hybrid Cloud Network
Migrating Cross-Region Dedicated Tunnel to CCN
Migrating IDC to the Cloud Through CCN
Accelerating Routing Convergence Through BGP+BFD (Layer 3)
IDC Local Configuration
Establishing Direct Connect Between Tencent Cloud and Various Cloud Vendors Through Equinix
API Documentation
History
Introduction
API Category
Making API Requests
Direct Connect APIs
Data Types
Error Codes
FAQ
Basic FAQs
Billing Issues
Function Issues
Troubleshooting
General Troubleshooting Solutions
Access Failure and Packet Loss
Agreements
Tencent Cloud Direct Connect Service Level Agreement
Tencent Cloud Direct Connect Service Agreement
Tencent Cloud Direct Connect Review Standards
Contact Us
Glossary

Disaster Recovery Deployment

PDF
Focus Mode
Font Size
Last updated: 2024-01-13 16:02:36

Application Scenarios

The user already has large scale applications. His/Her focus has been shifted from the balance between infrastructure deployment and business growth to the stability and reliability of the infrastructure for multi-center development. He/She hopes to eliminate business risks caused by single IDC failure through eliminating single IDCs.
User's core pain point
How to realize multi-location disaster recovery and improve infrastructure reliability.
How to realize fast deployment while reducing infrastructure construction period.
How to re-use stock IDC to reduce operating costs (use existing servers first).

Solutions:

Hybrid cloud disaster recovery deployment

Multi-location IDC deployment: Build master/slave clusters in local IDC and public cloud IDC.
Data synchronization: Synchronize data via Direct Connect or VPN to avoid single IDC failure.
Traffic forwarding: Provide lossy but uninterrupted services by forwarding the traffic to normal IDCs.

2-region-3-DC disaster recovery deployment in cloud

Cross-availability zone deployment: You can create subnets and deploy services in different availability zones within one VPC. Data can be synchronized between subnets of different availability zones. The goal of using different availability zones is to ensure that the failures are isolated from each other.
Cross-region deployment: You can deploy the same service in the VPC of another region to achieve multi-location disaster recovery and avoid failures in one region from spreading to other regions.
Cross-region high-speed interconnection: VPCs of two different regions achieve interconnection via cross-region peering connection. Traffic forwarding: it provides lossy but uninterrupted services by forwarding the traffic to other normal IDCs when an IDC breaks down.

Procedure

Steps of hybrid cloud disaster recovery deployment

1. Create a VPC on Tencent Cloud and deploy IDCs. For more information, please see VPC Instructions.
2. Synchronize the local IDC and the VPC IDC on the cloud via Direct Connect. For more information, please see Direct Connect Instructions.
3. Forward the traffic to other normal IDCs when an IDC breaks down.

Steps of cloud 2-region-3-DC disaster recovery deployment

1. Cross-availability zone deployment. You can create subnets and deploy master and slave synchronization service in different availability zones within one VPC. Data can be synchronized between subnets of different availability zones. The goal of using different availability zones is to ensure that the failures are isolated from each other. For more information, please see Subnet Instructions.
2. Cross-region deployment. You can deploy the same service in the VPC of another region to achieve multi-location disaster recovery and avoid failures in one region from spreading to other regions. For more information, please see VPC Instructions.
3. Cross-region high-speed interconnection. Create a cross-region peering connection to achieve high-speed data synchronization between two VPCs. For more information, please see Peering Connection Instructions.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback