Halaman ini belum tersedia dalam bahasa lokal Anda. Kami berusaha keras untuk menambahkan lebih banyak versi bahasa. Terima kasih atas dukungan Anda.
- 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.
Preparation: Set Up a Disaster Recovery Network on the Cloud
Scenarios
A VPC provides an isolated virtual network for your disaster recovery site servers. You can configure and manage the network as required.
In asynchronous replication, data on the to-be-protected servers at the on-premises data center is continuously replicated to the cloud disaster recovery site through a network. When an outage occurs at your local data center, you can switch services to the disaster recovery site servers on the cloud to ensure service continuity.
Factors to consider when creating a network on the cloud:
- Scope of disaster recovery
Select a region considering the following factors: physical distance between two sites, network performance, and costs. For example, keeping at least 100-km physical distance between the production site and disaster recovery site, less than 100-ms network latency, and cost-effective network (Direct Connect not used due to a tight budget).
- Network between the on-premises data center and the VPC on Huawei Cloud
- Public network: suitable for scenarios that the data volume is stable and access to the cloud resources from the on-premises data center is infrequent.
- VPN: suitable for scenarios that the data volume is stable and access to the Huawei Cloud resources from the on-premises data center is frequent. If some of your services are deployed on Huawei Cloud, and the on-premises data center services interact with the cloud services through a VPN, you can use this VPN for asynchronous replication.
- Direct Connect: suitable for complex scenarios with a large volume of data. Make the plan based on the data change volume of your services.
- VPC CIDR block
Provide IP addresses for the servers created during failovers or disaster recovery drills. To keep the IP addresses unchanged, set the VPC CIDR block to the same as the network segments of production site servers in the local data center. In this case, server IP addresses will remain the same during failovers or drills, without any additional configurations.
Procedure
Create a disaster recovery network on the cloud according to your overall network plan. For details, see Creating a VPC.
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