このページは、お客様の言語ではご利用いただけません。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
Show all
Copied.
Step 1: Create a Replica Pair
Procedure
- Log in to the SDRS console.
- Log in to the management console.
- In the upper left corner of the page, select the region where the service is located from the drop-down list.
- Click the service list icon in the upper left corner and choose Storage > Storage Disaster Recovery Service.
- Go to Create Replica Pair page in either of the following ways:
- In the upper right corner of the SDRS console, click Create Replica Pair.
- Locate Create Replica Pair in the process flow and click Create Now.
Figure 1 Service Overview - Select the type of the replica pair you want to create and configure parameters by referring to the table below.
- Cross-AZ: The production site and disaster recovery site are located in different AZs of the same region.
Figure 2 Creating a cross-AZ replica pair
- Cross-region: The production site and disaster recovery site are located in different regions.
Figure 3 Creating a cross-region replica pair
- IDC-to-cloud: The production site is deployed in a local data center.
Figure 4 Creating an IDC-to-cloud replica pair
Table 1 Parameter description Parameter
Description
Example Value
Type
Type of the replica pair
The supported types are IDC-to-cloud, Cross-region and Cross-AZ.
Cross-AZ
Scenario
Select the replication scenario you want to set up.
Supported scenarios are: H2C (HCS Online DR to the public cloud) and V2C (VMware DR to the public cloud).
NOTE:
This field shows up only when you are creating an IDC-to-cloud replica pair.
H2C
Name
Name of the replica pair
The name can contain letters, digits, underscores (_), hyphens (-), or periods (.), can be no more than 64 characters long, and cannot contain spaces.
Site-replication-001
Production Site
NOTE:
You only need to configure the production site when creating a cross-region or cross-AZ replica pair.
Region
Region where the production site resides
NOTE:
You only need to select a region when creating a cross-region replica pair.
-
AZ
AZ where the production site servers reside
NOTE:
You only need to select an AZ when creating a cross-region or cross-AZ replica pair.
AZ1
Network
VPC where the production site servers reside
VPC01
Disaster Recovery Site
Region
Region where the disaster recovery site resides
Select the region you selected when you set up the disaster recovery network. For details, see Preparation: Set Up a Disaster Recovery Network on the Cloud.
NOTE:
You only need to select a region when creating an IDC-to-cloud or a cross-region replica pair.
-
AZ
AZ where the disaster recovery site servers reside
AZ2
Network
VPC where the disaster recovery site servers reside
VPC02
- Cross-AZ: The production site and disaster recovery site are located in different AZs of the same region.
- Click Next to go to he Deploy Disaster Recovery Gateway page.
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