Esta página ainda não está disponível no idioma selecionado. Estamos trabalhando para adicionar mais opções de idiomas. Agradecemos sua compreensão.
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
Show all
Help Center/
Storage Disaster Recovery Service/
User Guide/
Asynchronous Replication/
Managing a Protection Group/
Reprotecting a Protection Group
Copied.
Reprotecting a Protection Group
Scenarios
After a failback, data is not automatically synchronized from the production site to the disaster recovery site, and protection is disabled for protected instances. To start data synchronization from the production site to the disaster recovery site, reprotect the protection group.
Prerequisites
- Ensure that, in 24.6.0 or an earlier version, you have preconfigured the production site servers you want to reprotect according to Configuring Production Site Servers.
- In 24.9.0 or a later version, SDRS automatically configures the disaster recovery gateway, so you do not need to preconfigure the production site servers before performing a reprotection. In 24.6.0 or an earlier version, ensure that you have upgraded the SDRS software on the gateway and production site servers to 24.9.0 or later and reconfigured the gateway according to Configuring a Disaster Recovery Gateway.
- The status of protected instances in the protection group is Failback completed or Reprotection failed.
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.
- Choose Asynchronous Replication. In the right pane, locate the replica pair housing the protection group you want to reprotect and click the number in the Protection Groups column.
The Protection Groups tab page is displayed.
- In the navigation tree, choose the target protection group.
The protection group details page is displayed.
- In the upper right corner of the basic information area, choose More > Reprotect.
NOTE:
In 24.9.0 and later versions, SDRS automatically configures the disaster recovery gateway. After a failback, wait for 1 to 2 minutes and then use reprotection.
- Select protected instances and click Submit.
- The protected instance status changes to Under reprotection. Wait until the operation is complete.
- After the operation is complete, the protected instance status changes to Synchronizing, and the amount of data to be synchronized and estimated remaining time are displayed.
NOTE:
After the failback is successful, disaster recovery site servers will be automatically deleted.
Parent Topic: Managing a Protection Group
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
