หน้านี้ยังไม่พร้อมใช้งานในภาษาท้องถิ่นของคุณ เรากำลังพยายามอย่างหนักเพื่อเพิ่มเวอร์ชันภาษาอื่น ๆ เพิ่มเติม ขอบคุณสำหรับการสนับสนุนเสมอมา
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/
Synchronous Replication Management (for Installed Base Operations)/
Managing Protected Instances/
Detaching a Replication Pair
Copied.
Detaching a Replication Pair
Scenarios
Detach replication pairs from protected instances. After a replication pair is detached from a protected instance, the replication relationship between the two disks remains, but the server data can no longer be written to the disks.
Prerequisites
- The protection group is in the Available, Protecting, Failover complete, Enabling protection failed, Disabling protection failed, Switchover failed, or Failover failed state.
- The protected instance is in the Available, Protecting, Failover complete, Enabling protection failed, Disabling protection failed, Switchover failed, Failover failed, Deletion failed, Re-enabling protection failed, Modifying specifications failed, Invalid, or Faulty state.
- The replication pair is in the Available, Protecting, Failover complete, Attaching failed, Detaching failed, Enabling protection failed, Disabling protection failed, Switchover failed, Failover failed, Deletion failed, Re-enabling protection failed, Expansion failed, Invalid, or Faulty state.
- The replication pair has been attached.
- Disks in the In-use state have been attached to the production and DR site servers.
NOTE:
- A system disk (attached to /dev/sda or /dev/vda) can be detached only when the server is in the Stopped state. Therefore, stop the server before detaching the system disk.
- Data disks can be detached online or offline, which means that the server containing the disks can either be in the Running or Stopped state.
For details about how to detach a disk online, see Disk > Detaching an EVS Disk from a Running ECS in the Elastic Cloud Server User Guide.
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.
- Locate the protection group where you want to detach replication pairs and click Protected Instances.
The protection group details page is displayed.
- On the Protected Instances tab, locate the row containing the desired protected instance and click Detach in the Operation column.
The Detach Replication Pair page is displayed.
- Select the replication pair to be detached and click Yes.
After the operation succeeds, the server data can no longer be written to the disks.
Parent Topic: Managing Protected Instances
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
