The Register VM Step Fails to Be Performed and Message Failed to register volumes and LUN that is required by the VM has not been mapped to the host, has become invalid or has not been managed by a consistent group Are Displayed When the Fault Recovery Step Is Performed

Symptom

After FusionCompute is refreshed, the Fault Recovery operation is performed. In the Register VM step, message Failed to register volumes. is displayed. FusionCompute is logged in to and the datastore created during fault recovery is deleted. When the Fault Recovery step is performed again, the Register VM step fails to be performed. Message LUN that is required by the VM has not been mapped to the host, has become invalid or has not been managed by a consistent group.

Possible Causes

UltraVR does not have the Enable data replication step during fault recovery. When this problem occurs, the automatic execution time for the protected group has not come or the protected group is not manually executed for data synchronization. Therefore, the LUN information on the production storage array (disks added) is inconsistent with that on the DR storage array. The volume information does not exist on the DR storage array. After the production FusionCompute is refreshed, the command for registering the DR disk delivered by UltraVR has been updated. Therefore, the DR FusionCompute registers a disk that does not have disk data on the DR LUN. As a result, the disk fails to be registered.

Procedure

Log in to UltraVR.
Delete the failed recovery plan.
1. On the menu bar, choose Recovery.
2. Select the recovery plan to be deleted and click More > Delete on the Operation list.
3. In the Warning dialog box that is displayed, read the content of the dialog box carefully and select I have read and understood the consequences associated with performing this operation.
4. Click OK.
Delete the protected group where the failed recovery plan resides.
1. On the menu bar, choose Protection.
2. Select the protected group that you want to delete and click More > Delete on the Operation list.
3. In the Warning dialog box that is displayed, read the content of the dialog box carefully and select I have read and understood the consequences associated with performing this operation.
4. Click OK.
Restore the network to the one before the fault is rectified and synchronize data from the primary LUN to the secondary LUN.
- Asynchronous replication: Synchronize the remote replication pairs again.
  1. Log in to the secondary FusionCompute, choose Resource Pool from the menu on the left, click Storage, and find the data store created for fault recovery. The name of the data store is as follows: Production data storage name +WWN.
  2. In the lower area, click the Details tab page, click Details next to VM Quantity, and record the VM name.
  3. Delete the VM on the data store based on the recorded VM name. After the VM is deleted successfully, click Disk List to delete all disks.
  4. After the disks are deleted successfully, click More > Disassociate.
  5. Log in to the storage device where the secondary LUN resides.
  6. On the menu bar, choose Data Protection > Remote Replication.
  7. Right-click the remote replication where the secondary LUN resides and choose Enable protection for secondary resource from the shortcut menu.
  8. Right-click the remote replication where the secondary LUN resides and choose Synchronize from the shortcut menu. Remote replication running status is Normal after synchronization.
- HyperMetro + asynchronous: Synchronize HyperMetro pair and the remote replication again.
  - Failback scenarios from DR center to HyperMetro data center:
    1. Log in to the secondary FusionCompute, choose Resource Pool from the menu on the left, click Storage, and find the data store created for fault recovery. The name of the data store is as follows: Production data storage name +WWN.
    2. Click Details next to VM Quantity to view the details and record the VM name.
    3. Delete the VM on the data store based on the recorded VM name. After the VM is deleted successfully, click Disk List to delete all disks.
    4. After the disks are deleted successfully, click More > Disassociate.
    5. Log in to the HyperMetro storage device at the Normal asynchronous leg of the asynchronous replication in DR Star solution.
    6. On the menu bar, choose Data Protection > HyperMetro > HyperMetro Pair > HyperMetro Pair.
    7. Select the HyperMetro pair corresponding to the protected group and check whether the HyperMetro pair status is normal. If yes, perform the following operations: Right-click on HyperMetro Pair and click Pause from the shortcut menu. After the HyperMetro is paused, a dialog box is displayed. If the current site is a preferred site, select Non-preferred Site. Otherwise, select Preferred Site and click OK.
    8. Log in to the storage device where the current production LUN resides.
    9. On the menu bar, choose Data Protection > Remote Replication > Remote Replication Pair.
    10. Right-click the remote replication on the current production LUN, and click Properties from the shortcut menu. In the displayed menu bar, set Secondary Resource Protection Status to Read-only, and click OK.
    11. Right-click the remote replication on the current production LUN, and click Synchronize from the shortcut menu. After the synchronization is complete, ensure that the running status of the remote replication is normal.
  - Failback scenarios from HyperMetro data center to DR center:
    1. Log in to the secondary FusionCompute, choose Resource Pool from the menu on the left, click Storage, and find the data store created for fault recovery. The name of the data store is as follows: Production data storage name +WWN.
    2. Click Details next to VM Quantity to view the details and record the VM name.
    3. Delete the VM on the data store based on the recorded VM name. After the VM is deleted successfully, click Disk List to delete all disks.
    4. After the disks are deleted successfully, click More > Disassociate.
    5. Log in to the HyperMetro storage device at the normal asynchronous leg of the DR Star asynchronous replication.
    6. On the menu bar, choose Data Protection > Remote Replication > Remote Replication Pair.
    7. Right-click the Remote Replication on the current production LUN, and click Properties from the shortcut menu. In the displayed menu bar, set Secondary Resource Protection Status to Read-only, and click OK.
    8. Right-click the Remote Replication on the current production LUN and click Synchronize from the shortcut menu. After the synchronization is complete, ensure that the running status of the remote replication is Normal.
Create protected groups and recovery plans on UltraVR at the production center.
On the menu bar, select Protection.
Select the protected group to be enabled and click Execute on the Operation list.
On the menu bar, choose Recovery.
Select the recovery plan to be tested, and click Test on the Operation list.
The Test dialog box is displayed.
Carefully read the content of the Warning dialog box that is displayed and click OK to confirm the information.
Select the recovery plan to be cleared, and click More > Clear on the Operation list.
Click OK.
Select the remote recovery plan for the Fault Recovery and click More > Fault Recovery on the Operation list.
In the Warning dialog box that is displayed, read the content of the dialog box carefully and select I have read and understood the consequences associated with performing this operation.
Click OK.

Suggestion and Summary

After adding or deleting disks for a protected VM or expanding the capacity of the array or datastore, refresh the information about the protected VM and manually execute the protected group where the VM resides. If the recovery plan fails to be executed, do not add, delete, and modify disaster recovery resources. Contact Huawei technical support.