Cannot remove non existent ASR applicance in Azure using the new modernized experience

Question

We’ve encountered an issue with our Azure Site Recovery (ASR) appliances. Specifically, we have two instances: one active and the other a stale version that no longer exists. Unfortunately, the stale version continues to generate alerts related to heartbeat and connectivity, despite its nonexistence.

While replication remains unaffected, the constant alerts are disruptive. Disabling them would also silence alerts for the actively used ASR appliance. We attempted to seek assistance from Azure support, but they declined due to our lack of a paid support plan.

Given this situation, what alternative options can we explore to resolve the issue?

Answer 1

Hi @juanramirez-1555

It sounds like you need to remove the stale Azure Site Recovery (ASR) appliance from the management console to prevent it from generating alerts

For the stale instance, if it is still under a protection plan, you need to stop the protection. This might involve removing any replication policies associated with it.

Once the protection is stopped, you should be able to remove or delete the stale instance. Ensure that you are deleting the correct appliance

If the console doesn't let you delete the stale instance because it's not communicating, you might need to use PowerShell or Azure CLI commands to forcefully remove it.

az backup container list --vault-name YourVaultNa --resource-group YourResourceGroupName --backup-management-type AzureIaasVM

Use the az backup protection command to stop protecting the specific appliance and remove it:

az backup protection disable --container-name YourContainerName --item-name YourItemName --vault-name YourVaultName --resource-group YourResourceGroupName --delete-backup-data true --yes

Reference: https://learn.microsoft.com/pt-pt/cli/azure/backup/protection?view=azure-cli-latest#az-backup-protection-backup-now-examples

https://learn.microsoft.com/en-us/azure/site-recovery/physical-manage-configuration-server#delete-or-unregister-a-configuration-server

Get in touch if you need more help with this issue.

--please don't forget to "[Accept the answer]" if the reply is helpful--