Windows Registry
Disclaimer:
Quest does not
provide support for problems that arise from improper modification of the
registry. The Windows registry contains information critical to your computer
and applications. Make sure you back up the registry before modifying it. For
more information on the Windows Registry Editor and how to back up and restore
it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.
The only way to resolve the problem is:
- Write down or screenshot all VMs that are protected under the cluster
- Select the Hyper-V cluster and remove it from protection, leaving all data intact
- Wait until all VMs will be moved into the "Recovery Points Only" section
- Click on Protect->Protect Multiple->Hyper-V Cluster and select all VMs that were protected previously
- Note: agents in protection wizard will be shown as yellow and warning "agent has been orphaned by this Core". This is normal.
- Wait until VM's will be relinked back under the Hyper-V Cluster.
Failure to do so may cause unexpected behavior. For example: VM after live migration will flicker between black (offline) and green (ready) and snapshots will fail. Also attempts to re-protect the same VM, will cause duplicate entries in the Core console.
If removing the Hyper-V cluster from protection fails with the following message "Error: Object reference not set to an instance of an object.", follow below steps:
- Write down or screenshot all VMs that are protected under the cluster
- Stop the Rapid Recovery Core service.
- Open registry editor by running command "regedit"
- Go to "HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\LicenseInfo"
- Locate the Hyper-V cluster and node registry keys, export them and remove them from registry.
- Re-start the Rapid Recovery Core service.
- Click on Protect->Protect Multiple->Hyper-V Cluster and select all VMs that were protected previously
- Note: agents in protection wizard will be shown as yellow and warning "agent has been orphaned by this Core". This is normal.
- Wait until VM's will be relinked back under the Hyper-V Cluster.