Bu sayfa henüz yerel dilinizde mevcut değildir. Daha fazla dil seçeneği eklemek için yoğun bir şekilde çalışıyoruz. Desteğiniz için teşekkür ederiz.
Storage Disaster Recovery Service
Storage Disaster Recovery Service
- 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
On this page
Help Center/
Storage Disaster Recovery Service/
Best Practices/
Two-Site Three-Center Disaster Recovery (SDRS+CBR)/
Cross-AZ DR Implementation/
Restoring Services If the Production Site Fails
Copied.
Restoring Services If the Production Site Fails
Scenarios
If the production site servers and disks fail due to physical faults, you can fail over services to the DR site servers and disks to guarantee service continuity.
DR site servers and disks can be used immediately after a failover. You can power on the servers, or use CBR to restore data to a specified data restore point.
NOTE:
- After a failover is started, data synchronization stops.
- After the failover is complete, the status of the protection group changes to Failover complete. Go to the protected instance details page and start the DR site server.
Constraints and Limitations
- For Linux servers with Cloud-Init installed, if you have changed hostname of the production site server before you perform a failover 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 Planned Failover or Failover?
- The protection group must contain replication pairs.
- Protection is enabled for the protection group, and the protection group is in the Protecting, Failover failed, or Planned failover failed state.
Restoring Services
- 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.
The protection group details page is displayed.
- In the upper right corner of the page, click More and choose Fail Over from the drop-down list.
The Fail Over dialog box is displayed.
- Click Fail Over.
During the failover, do not start or stop the servers in the protection group. Or, the failover may fail.
Parent topic: Cross-AZ DR Implementation
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot
