What Can I Do When the VRG at the Disaster Recovery End Encounters an Irrecoverable Fault?

5

1.On the OceanStor BCManager at the production end, delete the VM of the faulty VRG from the protected group. For details, see Deleting a Protected Object.
2.On the OceanStor BCManager at the production end, forcibly delete the VM that matches the faulty VRG. For details, see Delete a VM in Managing a Protected VM and select Forcible Remove.
3.Log in to the FusionCompute at the disaster recovery end and delete the VM of the faulty VRG at the disaster recovery end.
4.On the OceanStor BCManager at the production end, delete the faulty VRG match. or details, seeDeleting a FusionSphere.
5.On the OceanStor BCManager at the disaster recovery end, delete the faulty VRG. For details, see Deleting a FusionSphere.
6.On the OceanStor BCManager at the production end, add a new paired VM for the new VRG. For details, see Adding a VRG.
7.On the OceanStor BCManager at the production end, delete the VM of the faulty VRG from the protected group. For details, see Adding a Protected Object.

Other related questions:
What Can I Do If Protected Groups and Recovery Plans Cannot Be Deleted at the Production End When the Disaster Recovery End Encounters an Irrecoverable Fault?
1.Check whether backup data exists at the disaster recovery end. If yes, go to 2. If no, go to 3. 2.Backup data exists at the disaster recovery end. Reinstall the OceanStor BCManager at the disaster recovery end. For details, see Installing OceanStor BCManager Server. Import the backup data to the disaster recovery end to restore its data. For details, see Importing Backup Data. NOTE: After performing this operation, you do not need to delete the data and reconfigure the disaster recovery environment at the production site if the disaster recovery end recovers. 3.Backup data does not exist at the disaster recovery end. a.Reinstall the OceanStor BCManager at the disaster recovery end. For details, see Installing OceanStor BCManager Server. NOTE: When the OceanStor BCManager is installed, the management IP address and admin password of the OceanStor BCManager must be the same as those of the OceanStor BCManager at the disaster recovery end before the fault occurs. b.After the OceanStor BCManager is installed successfully, wait about 5 to 10 minutes. After the OceanStor BCManager Server starts, log in to the OceanStor BCManager at the disaster recovery end. If the login succeeds, the OceanStor BCManager is installed successfully at the disaster recovery end. c.On the OceanStor BCManager at the production end, delete the recovery plans, protected groups, resource mappings, and sites related to the OceanStor BCManager at the disaster recovery end before the fault occurs. d.On the OceanStor BCManager at the disaster recovery end, re-perform operations in Creating a Site and Adding Resources. e.On the OceanStor BCManager at both the production end and disaster recovery end, add the local management server of each other as remote management server. f.On the OceanStor BCManager at the production end, perform operations in Creating a Resource Mapping and Creating a Recovery Plan.

Policy-driven automatic disaster recovery supported by the OceanStor ReplicationDirector
The OceanStor ReplicationDirector (mainstream version: V100R003C10) supports policy-driven automatic disaster recovery by using Huawei disk array features (such as remote replication, snapshot, and three data centers in two cities) and VIS features (such as remote replication, snapshot, and mirror). Policy-driven automatic disaster recovery simplifies disaster recovery, reduces management complexity, and improves management efficiency. To implement disaster recovery, you only need to configure a disaster recovery policy based on your requirements. A disaster recovery policy defines the protection mode and scheduling policy that the disaster recovery system uses to provide protection for protected objects. A disaster recovery policy is created using the policy template when a protected group is created.

Applications scenarios supported by OceanStor ReplicationDirector in the disaster recovery data center solution (geo-redundant mode)
The disaster recovery data center solution (geo-redundant mode) supports the following applications: Mainstream databases: Oracle (RAC), Microsoft SQL Server (MSFC), and IBM DB2 (VCS and PowerHA) Mainstream application: Microsoft Exchange Server File system: NTFS Others: LUNs

Application types supported by OceanStor ReplicationDirector in the local protection solution
The local protection disaster recovery solution supports the following applications: Mainstream databases: Oracle (RAC), Microsoft SQL Server (MSFC), and IBM DB2 (VCS) Mainstream application: Microsoft Exchange Server Files system: NTFS Others: LUNs

How do I obtain documents about disaster recovery?
For details about disaster recovery documenation for FusionCloud 6.0, see CSDR User Guide. For details about disaster recovery documenation for FusionCloud 6.1, see FusionCloud Product Documentation. To be specific, see FusionCloud V100R006C10 Software Installation Guide (Region Type II) for instructions on installation; see FusionCloud V100R006C10 User Guide (Region Type II) for instructions on usage; see O&M documents (related to health check, backup and restoration, alarm handling, security management, O&M management, and so on) of each component for instructions on O&M.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top