Esta página ainda não está disponível no idioma selecionado. Estamos trabalhando para adicionar mais opções de idiomas. Agradecemos sua compreensão.
- What's New
- Product Bulletin
- Service Overview
- Getting Started
-
User Guide
- Permissions Management
-
Asynchronous Replication
- Managing a Replica Pair
- Managing a Protection Group
- Managing Protected Instances
- Managing DR Drills
- Managing Clients
- Synchronous Replication Management (for Installed Base Operations)
- Appendixes
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
-
SDRS APIs
- Job
- API Version
- Active-Active Domain
-
Protection Group
- Creating a Protection Group
- Querying Protection Groups
- Querying the Details of a Protection Group
- Deleting a Protection Group
- Changing the Name of a Protection Group
- Enabling Protection or Enabling Protection Again for a Protection Group
- Disabling Protection for a Protection Group
- Performing a Failover for a Protection Group
- Performing a Planned Failover for a Protection Group
-
Protected Instance
- Creating a Protected Instance
- Deleting a Protected Instance
- Querying Protected Instances
- Querying Details About a Protected Instance
- Changing the Name of a Protected Instance
- Attaching a Replication Pair to a Protected Instance
- Detaching a Replication Pair from a Protected Instance
- Adding an NIC to a Protected Instance
- Deleting an NIC from a Protected Instance
- Modifying the Specifications of a Protected Instance
- Batch Creating Protected Instances
- Batch Deleting Protected Instances
- Replication Pair
- DR Drill
- Tag Management
- Task Center
- Tenant Quota Management
- Appendixes
- Change History
- SDK Reference
-
FAQs
- Common Problems
-
Synchronous Replication (for Installed Base Operations)
- Do I Need to Manually Create DR Resources?
- What Can I Do When the EIP Cannot Be Pinged After I Perform a Switchover for a Protection Group Containing a SUSE Server?
- What Can I Do If the NIC Names of the DR Drill Server and Production Site Server Are Different?
- What Can I Do If hostname of the Production Site Server and DR Site Server Are Different After a Switchover or Failover?
- Why NICs of DR Site Servers Are Not Displayed After I Perform a Failover?
- What Are the Precautions If the Production Site Server Uses the Key Login Mode?
- What Should I Pay Attention to When Logging In to the Server After the First Time Ever I Executed a Switchover, Failover, or DR Drill?
- How Do I Use a Resource Package?
-
Asynchronous Replication
- How Do I Handle the drm Process Start Failure?
- Failed to Install and Configure Disaster Recovery Gateway When Process drm Exists But Port 7443 Is Not Listened
- What Can I Do If the Name of a Production Site Server or the Host Name Reported by the Gateway Is Incorrect and Always Displayed as "localhost"?
- What Can I Do If the Disaster Recovery Site VM Is Not Started After a Switchover?
- How Do I Obtain the Installation Package on a Production Site Server from the Gateway?
- How Do I Enable or Disable an ECS Firewall and Add a Port Exception to the Firewall?
- Why Can't I Find the Disaster Recovery Gateway When Associating a Replica Pair with It?
- Why Is No Production Site Server Displayed When I Create Protected Instances?
- Videos
- Glossary
- Best Practices
- General Reference
Copied.
Solution Principle
This section describes how the solution works in three fault scenarios: when the production site is functional; when the production site becomes faulty; when both the production site and cross-AZ DR site become faulty.
When the Production Site Is Functional
Figure 1 shows the work mechanism when the production site is functional.
- SDRS synchronizes the server data and configuration of the production site in AZ 1 in region A to the cross-AZ DR site in AZ 2 in region A. You can perform routine DR drills to periodically simulate fault recovery scenarios and formulate emergency recovery plans.
- CBR periodically backs up the entire server at the production site in region A and replicate the backup to the cross-region DR site in region B.
When the Production Site Becomes Faulty
If the production site becomes unavailable due to a small-scale fault such as a device fault, applications can be switched to the cross-AZ DR site without data loss.
In this phase, the Recovery Point Objective (RPO) is 0, and the Recovery Time Objective (RTO) is within 30 minutes.
RPO specifies the maximum acceptable period in which data might be lost.
RTO specifies the maximum acceptable amount of time for restoring the entire system after a disaster happens.

When Both the Production Site and Cross-AZ DR Site Become Faulty
If the production site and cross-AZ DR site become unavailable due to a large-scale disaster such as a natural disaster, applications can be switched to the cross-region DR site. You can create full-ECS images using the server backups periodically replicated to region B, use the full-ECS images to create ECSs, and restore applications at the cross-region DR site to ensure service continuity.
In this phase, the RPO ranges from 0 to the backup interval. The minimum backup interval is 1 hour, and the RTO is within 30 minutes.
In the cross-region DR phase, the RPO equals the difference between the time when a disaster occurs and the time when the latest backup file is generated.

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