El contenido no se encuentra disponible en el idioma seleccionado. Estamos trabajando continuamente para agregar más idiomas. Gracias por su apoyo.
- 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.
Disaster Recovery Drill (Synchronous Replication)
Scenarios
Disaster recovery drills are used to simulate fault scenarios, formulate recovery plans, and verify whether the plans are applicable and effective. Services are not affected during disaster recovery drills. When a fault occurs, you can use the plans to quickly recover services, thus improving service continuity.
SDRS allows you to run disaster recovery drills in isolated VPCs (different from the disaster recovery site VPC). During a disaster recovery drill, drill servers can be quickly created based on the disk snapshot data. This way, drill servers will have the same server specifications and disk types as the production site servers.
After drill servers are created, production site servers and drill servers will independently run at the same time, and data will not be synchronized between these servers.
To guarantee that services can be switched to the disaster recovery site when an outage occurs, it is recommended that you run disaster recovery drills regularly to check that:
- Data between the production site and disaster recovery site is consistent at the moment you create a disaster recovery drill.
- Services run properly at the disaster recovery site after a planned failover.
Figure 1 Disaster recovery drill
Precautions
- If the disaster recovery site servers of a protection group are added to an enterprise project, the drill servers created will not be automatically added to the enterprise project. Manually add them to the project as needed.
- If an existing drill VPC is used for a new drill, the subnet ACL rule of the drill VPC will be different from that of the protection group VPC. Manually set them to be the same as needed.
- If a custom route table is configured and associated with a subnet in the protection group VPC, the corresponding route table will not be automatically created in the drill VPC. Manually create one as needed.
- If the disaster recovery site servers run Windows and use key pairs for login, ensure that the key pairs exist when you create the drill. Otherwise, drill servers may fail to create, resulting in the drill creation failure.
NOTE:
If a key pair has been deleted, recreate the key pair with the same name.
- If the disaster recovery site servers run Linux and use key pairs for login, the key pair information will not be displayed on the server details page, but login using the key pairs is not affected.
- After a disaster recovery drill is created and before it is executed, modifications made to Hostname, Name, Agency, ECS Group, Security Group, Tags, and Auto Recovery of disaster recovery site servers will not synchronize to drill servers. Log in to the console and manually make the modifications for the drill servers.
- If the synchronization progress of replication pairs in the protection group is not all 100%, the created drill servers may fail to start. It is recommended that you run disaster recovery drills after all replication pairs are synchronized.
Prerequisites
- The protection group is in the Available, Protecting, Failover complete, Enabling protection failed, Disabling protection failed, Planned failover failed, Re-enabling protection failed, or Failover failed state.
- Do not run disaster recovery drills before the first time data synchronization between the production site servers and disaster recovery site servers completes. Otherwise, drill servers may not start properly.
Procedure
- Log in to the management console.
- Click Service List and choose Storage > Storage Disaster Recovery Service.
The Storage Disaster Recovery Service page is displayed.
- In the pane of the protection group to which a DR drill is to be added, click DR Drills.
The protection group details page is displayed.
- On the DR Drills tab, click Create DR Drill.
The Create DR Drill dialog box is displayed.
- Configure Name and Drill VPC.
Table 1 Parameter description Parameter
Description
Example Value
Name
DR drill name
DR drill servername
Drill VPC
VPC that used for a DR drill. It cannot be the same as the VPC of the DR site server. The value can be Automatically create or Use existing.
- Automatically create: The system automatically creates a drill VPC and subnet for the protection group.
- Use existing: The system uses an existing VPC as the drill VPC. If you select to use an existing VPC, the subnet CIDR block of the drill VPC must be consistent with that of the production group VPC.
NOTE:
The drill VPC cannot be the same as the VPC of the protection group.
vpc-f9f7
- Click OK.
After the disaster recovery drill is created, you can log in to a drill server and check whether services are running properly.
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