DAIV / PRODUCT ARCHITECTURE

DRaaSMulti-site & Cloud Disaster Recovery

Connect customer production and standby data centers with a cloud data center for inter-site replication, cloud protection, drills and authorized recovery. Data traffic passes through each site's core switches; service management connects through separate management networks.

Interactive 3D architecture

01 / Product Architecture

Two data centers.
Extended into a recovery cloud.

Customer Production Site A, Customer Standby Site B, Cloud Data Center, Multi-site DR Service Management. Select a zone or device to inspect its structure and responsibilities.

  • 01Dual-site Protection
  • 02Cloud Data Center DR
  • 03Inter-site Replication
  • 04Drills & Authorized Recovery
Read the full architecture notes

02 / Operating Workflow

Follow three-site synchronization.
Understand cloud protection and takeover.

Explore the DRaaS workflow step by step. Paths follow the selected step; critical actions retain human confirmation.

Configure Three-site Protection

Identify application and database resources through each site's management switch and configure inter-site replication and cloud protection policies.

Product simulation only. No production connection or real business operations.

03 / AI-assisted Management

Evidence for decisions.
Boundaries for execution.

Identify issues, explain evidence and suggest actions throughout the multi-site & cloud disaster recovery workflow.

01 / Assisted Capability

Check three-site replication and recovery resource readiness

02 / Assisted Capability

Review cloud drill plans, application dependencies and impact

03 / Assisted Capability

Explain inter-site anomalies and provide reviewable recovery advice

AI explanations and advice do not imply automatic execution.
Deterministic rules, permissions and human approval govern high-risk actions.

Review the full architecture notes ↗

ARCHITECTURE NOTES

Multi-site & Cloud Disaster Recovery,
Clear responsibilities at every layer.

The three sites, synchronization paths and resources illustrate the service architecture. Replication relationships and recovery order follow project policies. Cloud protection does not imply automatic takeover of all production services; drills and recovery remain subject to rules, permissions and human authorization. AI assistance does not replace human authorization.

01Customer Production Site A

A · Application Servers

Multiple application server resources connect to core switching and separate management networks according to protection policies.

A · Databases

Site database resources send and receive replication through the local core switch, not through the management platform as a data front end.

A · Core Switch

Aggregates the site's application and database synchronization traffic and carries the inter-site synchronization backbone.

A · Management Switch

Provides separate local management access between service management and resource management ports, without carrying inter-site replication data.

02Customer Standby Site B

B · Application Servers

Multiple application server resources connect to core switching and separate management networks according to protection policies.

B · Databases

Site database resources send and receive replication through the local core switch, not through the management platform as a data front end.

B · Core Switch

Aggregates the site's application and database synchronization traffic and carries the inter-site synchronization backbone.

B · Management Switch

Provides separate local management access between service management and resource management ports, without carrying inter-site replication data.

03Cloud Data Center

Cloud · Application Servers

Multiple application server resources connect to core switching and separate management networks according to protection policies.

Cloud · Databases

Site database resources send and receive replication through the local core switch, not through the management platform as a data front end.

Cloud · Core Switch

Aggregates the site's application and database synchronization traffic and carries the inter-site synchronization backbone.

Cloud · Management Switch

Provides separate local management access between service management and resource management ports, without carrying inter-site replication data.

04Multi-site DR Service Management

DRaaS

Unified service management connects to all three management networks to coordinate protection policies, replication monitoring, cloud drills and authorized recovery. It does not proxy synchronization traffic.

01 / Configure Three-site Protection

Identify application and database resources through each site's management switch and configure inter-site replication and cloud protection policies.

02 / Synchronize Through Core Networks

Production replicates to the standby and cloud sites; standby may also synchronize to the cloud according to policy. All three independent backbones enter and leave through core switches.

03 / Authorize Drills & Recovery

Check replication, resource readiness and permissions, then schedule standby or cloud drills and recovery through management networks. Cloud protection is not unauthorized production takeover.

Human authorization required

04 / Verify & Report Service Status

Standby and cloud application and database verification results return through their management networks, providing service status and recovery evidence.