このページは、お客様の言語ではご利用いただけません。Huawei Cloudは、より多くの言語バージョンを追加するために懸命に取り組んでいます。ご協力ありがとうございました。
- 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 Overview
What Is Two-Site Three-Center?
Two-site three-center is a disaster recovery (DR) solution used for service continuity. With three data center coexisted, the continuity of mission-critical services can be guaranteed even if any two centers fail. This significantly improves the availability of the solution.
The two-site three-center DR solution includes a production center, an intra-city DR center, and a remote DR center.
- Production center: It provides services for external applications.
- Intra-city DR center: It is usually dozens of kilometers away from the production center. Applications can be switched to the intra-city DR center without data loss. This is the level-1 DR protection of this solution.
- Remote DR center: It is usually built hundreds or thousands of kilometers away from the production center to protect against regional disasters. Data is periodically, asynchronously replicated to the remote DR center. This is the level-2 DR protection of this solution.
You can use Huawei Cloud SDRS and CBR to deploy two-site three-center DR. This solution responds quickly to small-scale failures and large-scale natural disasters, protecting service data and guaranteeing service continuity.
What Is SDRS?
Storage Disaster Recovery Service (SDRS) provides DR services for many cloud services, including Elastic Cloud Server (ECS), Elastic Volume Service (EVS), and Dedicated Distributed Storage Service (DSS). By leveraging technologies, such as storage replication, data redundancy, and cache acceleration, SDRS offers high data reliability and service continuity for users.
What Is CBR?
Cloud Backup and Recovery (CBR) enables you to back up ECSs, Hyper Elastic Cloud Servers (HECSs), Bare Metal Servers (BMSs), EVS disks, SFS Turbo file systems, a single or multiple files and databases on your local hosts, and on-premises VMware virtual environments with ease. In case of a virus attack, accidental deletion, or software or hardware fault, you can restore data to any point in the past when the data was backed up.
What Is the Two-Site Three-Center DR Solution (SDRS+CBR)?
In this solution, SDRS synchronizes data from the production site to a DR site in a different AZ of the same region for cross-AZ DR. CBR periodically backs up the production data to the other DR site in a different region for cross-region DR. The production site, cross-AZ DR site, and cross-region DR site all together form the geo-redundant architecture to meet the two-site three-center DR requirements.
The cross-AZ DR site corresponds to the intra-city DR center, and the cross-region DR site corresponds to the remote DR center.
In this document, the two-site three-center DR solution (SDRS+CBR) is called the SDRS+CBR DR solution for short.
In the SDRS+CBR DR solution, the solution is deployed in two regions and involves three sites: a production site, a cross-AZ DR site in the same region (cross-AZ DR center for short in the following document), and a cross-region DR site.
In this solution, SDRS synchronizes data from the production site to the cross-AZ DR site. CBR periodically backs up the production data to the cross-region DR site.
Application Scenarios
The SDRS+CBR DR solution is suitable if you use ECSs and EVS disks to run workloads.
Solution Advantages
Compared with two-site solutions (the cross-AZ DR solution and cross-region DR solution), the SDRS+CBR DR solution combines the advantages of both two-site solutions and can protect against both AZ-level failures and regional disasters.
- Disk data consistency is ensured during DR switchover if an AZ-level failure occurs.
- If a regional disaster occurs, this solution can restore the service data to the latest backup time point to ensure minimal data loss.
Table 1 compares the three types of DR solutions.
Notes and Constraints
- Cloud-Init must be installed on Linux ECSs, and Cloudbase-Init on Windows ECSs. After you perform a failover for the first time and start the servers, the system will run Cloud-Init/Cloudbase-Init to inject the initial data. The passwords or key pairs for logging in to the production and DR servers will change.
- If you use SDRS to set up DR, DR servers or disks can be restored only when protection is disabled for the servers.
For details about SDRS usage restrictions, see SDRS Usage Restrictions.
For details about CBR usage restrictions, see CBR Usage Restrictions.
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