Update Failures and Agent Status Fluctuations in Rapid Recovery After SSL Certificate Changes (4376825)

1. Check SSL Certificate Setup:

   • Make sure the new SSL certificate on your vCenter server is correctly set up and trusted by all systems, including the Rapid Recovery Core. If the certificate is self-signed, import it into the trusted certificate store on the Core server.
   • Don’t forget to update the vCenter connection settings in Rapid Recovery to match any changes from the new SSL certificate. For step-by-step instructions, check out this guide: How to Change Credentials for ESXi/vCenter Connection (4037203).

2. Re-protect Your vCenter Server:

   • Re-protecting your vCenter will add it back to the Rapid Recovery Core, allowing you to protect VMs without agents. This process also ensures that the new SSL certificates are shared correctly between the Core and the vCenter.

3. Verify Network Connectivity:

   • Check that there are no network issues affecting communication between the Rapid Recovery Core, agents, and vCenter server. Make sure DNS resolution and IP addresses haven’t changed after the SSL update.

4. Restart Services:

   • Restart the Rapid Recovery Core service and any affected agents. This can help clear out temporary issues that might be causing the fluctuating agent status.

5. Test Protection on One VM:

   • Try unpausing protection for a single VM first and watch its status. If everything looks good, you can gradually unpause protection for the other VMs.

6. Ensure Time Synchronization:

   • Make sure that the time is synchronized across your vCenter server, Rapid Recovery Core, and agents. This helps prevent communication issues.

7. Update VMware Tools:

   • Check that VMware Tools are up to date on your VMs. This ensures optimal communication between the VMs, vCenter server, and Rapid Recovery Core.

Following these steps should help you resolve any update failures and stabilize the agent status in Rapid Recovery after making SSL changes to your VMware environment.