Orphaned Azure Recovery Configuration Server

Hi Mattox, David

Here’s a step-by-step guide on what you can try to remove that orphaned server:
**
Disable protection**: Make sure that all virtual machines associated with that configuration server are not protected anymore. You can disable protection through the Azure portal.

1. Check for Replication Policies: Ensure there are no active replication policies associated with the configuration server. If there are, they need to be deleted first.
2. Remove Associated vCenter Servers: If there are any VMware vCenter servers linked to that configuration server, make sure to disassociate and delete those.
3. Using Azure Portal to Delete:
   • Go to the Azure portal.
   • Navigate to Site Recovery Infrastructure > Configuration Servers from the Vault menu.
   • Click on the configuration server that you want to delete.
   • On the details page, hit the Delete button and confirm your action.
4. PowerShell Option: If the Azure portal isn't working as expected, you can try using Azure PowerShell commands to forcefully delete the configuration server.
5. Uninstall Configuration Server: If you haven't done so already, follow the instructions to uninstall the configuration server and all associated components from the server where it was installed, making sure to delete the registration from the registry.

let us know if any help, we will always help as you needed.!

Please do not forget to "Accept the answer” and upvote it wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.

Hi Mattox, David
Your contribution is highly appreciated. Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Thank you Praney -

Tried this and did not work. No machines are connected to orphaned config server but when I go to delete, I get message it is in a connected state and cannot be deleted. This installation has been uninstalled on premises and the vm has been deleted from premises. Any other suggestions?

Hi Mattox, David

To remove an orphaned Azure Recovery Configuration Server that still appears as connected even after the associated VM has been deleted, please follow the steps below:

Connect to the MySQL database on the Configuration Server and run the following commands to identify any stale host entries:

mysql> use svsdb1;
mysql> select id as hostid, name, ipaddress, ostype as operatingsystem, from_unixtime(lasthostupdatetime) as heartbeat from hosts where name!='InMageProfiler'\G;

This will help you identify machines that may no longer be active but are still listed.

If you find any stale entries, unregister them using the command below:

Unregister-ASRComponent.pl -IPAddress <IP_ADDRESS_OF_MACHINE_TO_UNREGISTER> -Component <Source | PS | MT>

If the source machine is still online and accessible, restart the relevant services to allow it to re-register cleanly with the Configuration Server. If the machine is deleted, this step can be skipped.

After ensuring there are no stale entries remaining, return to the Azure portal and attempt to delete the Configuration Server again. It should now succeed without errors.

https://learn.microsoft.com/en-us/azure/site-recovery/vmware-azure-manage-configuration-server

https://learn.microsoft.com/en-us/azure/site-recovery/vmware-azure-troubleshoot-configuration-server#upgrade-fails-when-the-services-fail-to-stop

let us know if any help, we will always help as you needed.!

Please do not forget to "Accept the answer” and upvote it wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.

Hi Mattox, David

Your contribution is highly appreciated. Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.