Agentless Backups Fail After Migrating Rapid Recovery Core to a New Server (4378370)

When moving the Rapid Recovery Core service to a new server and restoring settings from a previous setup using an XML file, some agentless (Rapid Snap) backups may stop working. The issue happens because the system retains the old Core server’s hostname instead of updating it to match the new one.

Symptoms:

• Physical machines protected with the Rapid Recovery agent continue backing up successfully.

• Agentless (Rapid Snap) backups for virtual machines fail.

• The Rapid Recovery Core web address displays the old Core server name.

The VMware proxy, responsible for handling snapshots and exports, kept using the old Core server's hostname instead of switching to the new one after the settings were imported. Normally, this change should happen automatically, but in this case, it did not.

To resolve this issue, update the registry entry to reflect the new Rapid Recovery Core hostname:

1. Open the Windows Registry Editor (regedit).

2. Navigate to:

   HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\VMProxy\HostAddress

3. Verify the value of HostAddress and update it to the new Rapid Recovery Core server's hostname.

4. Restart the Rapid Recovery Core service to apply the changes.

Recommendations:

• Review the registry settings to confirm that all references to the old hostname have been updated to match the new server.

• \HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\serviceHost\ServiceBaseAddress
  \HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\webServer\ServiceBaseAddress
  \HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\VMwareProxy\serviceHost\ServiceBaseAddress