What Can I Do If a VRG VM Becomes Faulty in a Patched FusionCompute System, and Need to Add a New VRG VM?

27

1.Add the new VRG VM, install the VRG software of an unpatched version first.
2.Patch the VRG VM independently to upgrade it to the same version of the current system.

Other related questions:
The VRG VM Fails
Locate the VRG failure cause by following the alarm help. Check whether the alarm help can help remove the VRG failure. If yes, no further action is required. If no, go to 3. Log in to FusionCompute at the production site. For details, see Logging In to the FusionCompute in the FusionCompute V100R005C00 Software Installation Guide. Select VM and Template. The VM and Template page is displayed. Select the VRG VM and choose Operation > Stop. Stop the VRG VM as prompted. When the VM state becomes Stopped, the VM is successfully stopped. Log in to OceanStor ReplicationDirector and click Settings. The Settings page is displayed. In the navigation tree on the left, choose Resource Mapping > VRG. The VRG page is displayed. Select the faulty VRG. In the Protected VM area, select the VM in the VRG. Click Move and select Force Remove. Move the VM in the VRG to another normalVRG. In the VRG list, select a VRGto which the VM is moved. Click Start and choose Consistency verification to start DR.

Introduction to the VRG
For host replication disaster recovery, a Virtual Replication Gateway (VRG) is used. A VRG performs the following functions: 1. Aggregates, compresses, and encrypts VM I/O data and transmits the data to the remote site. 2. Receives data from the remote site and transmits the data to the specified host. 3. Provides management interfaces for delivering replication policies and querying statuses. 4. Ensures disaster recovery performance. Only one VRG VM can be deployed on a host. It is recommended that a VRG provide disaster recovery for a maximum of 150 VMs. The maximum write IOPS is 550. After a VRG VM is created, be aware of the following: 1. The VRG VM-related configurations (CPU, memory, disks, and network adapters) and attributes must not be modified. 2. Capacity expansion, capacity reduction, disk mounting, disk unmounting, storage migration, and VM migration must not be performed. 3. The VRG VM does not support clone and must be installed using a template. 4. The VRG VM does not support snapshots and restoration or VM backup and restoration. 5. You can start, restart, or stop VRG VMs only during VRG VM maintenance.

The logcache Disk of the VRG Fails
Log in to the FusionCompute at the production site. For details, see Logging In to the FusionCompute in the FusionCompute V100R005C00 Software Installation Guide. Select VM and Template. The VM and Template page is displayed. Select the VRG VM and choose Operation > Stop. Stop the VRG VM as prompted. When the VM state becomes Stopped, the VM is successfully stopped. Log in to OceanStor ReplicationDirector and click Settings. The Settings page is displayed. In the navigation tree on the left, choose Resource Mapping > VRG. The VRG page is displayed. Select the faulty VRG. In the Protected VM area, select the VM in the VRG. Click Move and select Force Remove. Move the VM in the VRG to another VRG. In the FusionCompute , detach the logcache disk from the VRG VM. For details. see Detaching a Disk from a VM in the FusionCompute V100R005C00 Storage Management Guide. The logcache disk of the VRG is the second disk whose capacity is 100 GB. Attach a new logcache disk to the VRG VM. For details. see Attaching a Disk to a VM in the FusionCompute V100R005C00 Storage Management Guide. In the FusionCompute, choose Operation > Start in the line where the VRG VM resides. Start the VRG VM. When the VM state becomes running, the VM is successfully started.

What Can I Do When the VRG at the Disaster Recovery End Encounters an Irrecoverable Fault?
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.

Methods used to unbind disks from faulty VMs and bind them to new VMs
1. In the FusionCompute, choose VDC Management > VM and Template. The VM and Template page is displayed. 2. In the navigation tree, expand Site, right-click the faulty VM, and choose Forcibly Stop from the shortcut menu. Click VM, and choose More > Forcibly Stop in the Operation column from the row where the faulty VM is located. 3. Click OK. 4. Choose VDC Management > Storage Management. 5. In the Site navigation tree, choose the site where the faulty VM is located. 6. Click the Disk tab. A disk list is displayed. 7. Click the name of the faulty VM, and click Disk on the Hardware tab. 8. Click the name of the data storage to which the disk attached to the faulty VM belongs, and click Disk. 9. Locate the row that contains the system disk (for example, disk 1) of the faulty VM, click MoreOperation, and select Unattach. Detach disk 1 from the faulty VM as prompted. 10. Locate the row that contains disk 1, click MoreOperation, and select Attach. The Attach dialog box is displayed. 11. Select user disk as the binding mode, and select the VM (for example, VM B) to which the disk is attached. 12. Click OK. 13. Attach disk 1 to VM B as prompted. 14. Log in to VM B using VNC. 15. Right-click My Computer, and choose Manage from the shortcut menu. The Server Manager window is displayed. 16. Choose Storage > Disk Management. Right-click disk 1, and choose Change Drive Letter and Paths from the shortcut menu. The Change Drive Letter and Paths dialog box is displayed. 17. Click Change, and set a drive letter, for example, E. Click OK. A confirmation dialog box is displayed. 18. Click OK. The Computer Management page is displayed. The data on drive E: is the data on disk 1. 19. Restore system files on drive E, and back up user data.

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