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
Show all
Copied.
Performing a Switchover
Scenarios
After you perform a switchover, services at the production site are switched to the DR site, and services at the DR site are switched over to the production site. Table 1 shows the direction change.
- |
Production Site |
DR Site |
---|---|---|
Before |
AZ1 |
AZ2 |
After |
AZ2 |
AZ1 |
After the switchover, data synchronization continues, but the DR direction is changed from the DR site to the production site. You can perform a switchover when you are certain that the production site will encounter an interruption. For example, if the production site (AZ1) is going to encounter a power failure, you can perform a switchover to switch services in AZ1 to the DR site (AZ2). The switchover does not affect data synchronization of the protection group.
SDRS will migrate NICs on the server during the switchover. Once completed, the IP, EIP, and MAC addresses of the production site server will be migrated to the DR site server, so that the IP, EIP, and MAC addresses remain the same.
- Check the status to ensure that all the servers in the protection group are stopped before a switchover.
- During a switchover, do not start the servers in the protection group. Otherwise, the switchover may fail.
- Once a switchover is complete, data synchronization will not stop, only the synchronization direction will reverse.
- Once a switchover is complete, the status of the protection group changes to Protecting. Then, you need to go to the protected instance details page and start the production site server.

Notes
For Linux servers with Cloud-Init installed, if you have changed hostname of the production site server before you perform a switchover for the first time, this modification will not synchronize to the DR site server.
To resolve this problem, see What Can I Do If hostname of the Production Site Server and DR Site Server Are Different After a Switchover or Failover?
Prerequisites
- All the servers in the protection group are stopped.
- The protection group has replication pairs.
- Protection is enabled for the protection group, and the protection group is in the Protecting or Switchover failed state.
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 desired protection group, click Protected Instances.
- In the upper right corner of the page, click Execute Switchover.
- In the displayed dialog box, check whether all the servers in this protection group are stopped.
- If yes, go to step 6.
- If no, select the servers to be stopped and click Stop.
- In the displayed dialog box, click Execute Switchover.
NOTE:
During a switchover, do not start the servers in the protection group. Or, the switchover may fail.
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