VM in Azure subscription not detected anymore?

[enoch]

Hi all,

I've a Azure Subscription that have run fine for many month.

Suddenly I get "warning" in the backup job - if I go to the Backup Policy and check, the VM is not detected anymore?

The VM is running fine in West Europe, but I cannot backup it anymore.

Any ideas?

[david.domask]

Hi @enoch,

Please open a Support case from https://my.veeam.com and let's have the Support Team take a look at the situation.

Be sure to include logs from the affected job as per https://helpcenter.veeam.com/docs/vbazu ... tml?ver=60, and please provide as much information (with screenshots if possible and mentioning the specific job/vm in question) to ensure Support has the information it needs to assist.

Please post the case number once your case is created.

[nielsengelen]

Can you clarify how you back it up? Is this using the VM directly or are you using tags and did the tag maybe get removed from the VM?

[enoch]

Hi David,

It works now.

The weird things was, it worked when I dealocated the server in Azure and started it again. After that Veeam Azure could see the VM again.

[RobMiller86]

This is exactly what I am referring to in my thread: veeam-backup-for-microsoft-azure-f59/fa ... 90638.html

Question for you Peter, was it the same deal as in my post? "The last operation performed on this VM failed. The VM is still running. View error details". Then if you click that, in Azure it says "The virtual machine is in a failed state. The fabric operation failed. Reapplying the virtual machine may resolve the issue." Error code: InternalExecutionError. Provision state: Failed. If you click reapply, the VM is reprovisoned in Azure, rebooted, and all is well again.

Did you have this VM added to a policy only by a tag? Was your policy in a failed state or warning state? You did see some form of unsuccessful policy correct? I am worried about this issue not being detected as I have seen it in the past in previous VBAZ versions not fail it at all, as it couldn't see it, so couldn't see the tag, and I guess just thought it was removed. I'm trying to discover how it works now. To be sure we detect this condition. Thanks.

[enoch]

Hi,

In Veeem for Azure the job was in "Warning" state, because it could not see any VM's.

No matter what I tried, Veeam for Azure could not see the VM.

The VM was running fine in Azure and all services worked. I then did a "stop" (deallocated the VM), started it again and then Veeam for Azure could see the VM again.

Maybe a "bug" or "feature" in Veeam for Azure...

[RobMiller86]

Thanks. If you come across this again, check the VM overview blade and see what it says there. There is a "reapply" buttom that essentially does for you, what you did manually. If you do find one that is in that failed state in Azure, and was added to Veeam policy by tag, definitely come back here and update this thread and let us know how you found it, or how Veeam reported the issue. Thanks again.