Azure linux VM not visible to Azure Backup during VM discover

Walter, Shaun (S) 0

We have cloned a VM from Azure East US to Azure Central US as part of a Disaster Recovery Exercise. Dozens of VMs are included in this exercise and all have been cloned to the DR platform in Azure Central region. One Linux VM is not seen by the Azure Backup service (Azure Business Continuity Center) which is required for this VM to receive a database restore. All other servers in this exercise (application server and database server) are seen by Azure backup except this one server. Server is running SUSE Linux Enterprise Server 15 SP2. Other servers in the same subnet are visible and available to Azure Backup so this is unlikely a firewall issue. The Azure Backup agent in the guestOS "waagent" is running and has been restarted several times. How can we force this VM to be discovered by the Azure Backup service to enable database restores to this VM?

Steps taken to resolve this issue:

Verify "waagent" is running on this linux VM
Stop/Restart the "waagent" on this linux VM
Remove and re-install the "waagent" on this linux VM
Reboot the VM several times
Removed the "AzureBackupLinuxAgent" EXTENSION from this VM in Azure Portal
Removed the "enablevmAccess" EXTENSION from this VM in Azure Portal

If anyone has encountered this issue and found a consistent resolution, please share or provide steps that you have had success with. Any guidance or insights would be appreciated.

Thanks.

Ashok Gandhi Kotnana 555 Reputation points Microsoft Vendor

2024-11-14T13:04:07.7466667+00:00
HI Walter, Shaun,

Welcome to Microsoft Q&A Forum, thank you for posting your query here!

I see you have done the possible troubleshooting

But i have few questions before giving any resolution.

Does this SUSE Linux Enterprise Server 15 SP2 only Linux flavour vm we have in the discovered machines or else do we have any other vm with the same OS which is already discovered?

After replication have you done any failover or just you have replicated it? (If we have just replicated it i don't think we can see in the backup item)

Please let us know if you have any further queries. I’m happy to assist you further.
Walter, Shaun (S) 0 Reputation points

2024-11-15T13:12:25.28+00:00
Hi Ashok, here are the answers to the questions you posed:

Does this SUSE Linux Enterprise Server 15 SP2 only Linux flavour vm we have in the discovered machines or else do we have any other vm with the same OS which is already discovered?

ANSWER: We have multiple Linux VMs running SUSE Linux Enterprise Server 15 SP2 similarly replicated in our DR exercise. Four (7) of these VMs have already been registered in Azure Backup and the databases were successfully discovered. This is the only VM that is not visible/discoverable in Azure Backup to register for backup/restore.

After replication have you done any failover or just you have replicated it? (If we have just replicated it i don't think we can see in the backup item)

This VM was replicated and then a TEST FAILOVER was performed to deploy the VM and start up the VM to make it available and reachable by other VMs in the DR exercise test. The many other VMs included in the DR exercise went through the same replication/TEST FAILOVER procedure for deployment and were again able to be registered in Azure Backup, except this one.

Please let me know if you have any other questions or need additional information.

Thanks.

Shaun Walter

215-740-8470

swalter1@trinseo.com

Share via

Azure linux VM not visible to Azure Backup during VM discover

Your answer