Agentless, cloud-native backup for Microsoft Azure
Post Reply
dgreg
Lurker
Posts: 1
Liked: never
Joined: Jul 11, 2025 5:22 pm
Full Name: Greg D
Contact:

Job/Policy Failure Notifications

Post by dgreg »

We had a scenario where an Azure VM had to be restored with Veeam, resulting in a new VM being created. We recently found out that the job/policy in Veeam for Azure wasn't updated to include the new VM, which is a procedural issue on our end. What I find odd is that we didn't receive a notification about a job failure. I did some testing and found that if the policy only has a single VM, and that VM is removed, no notifications are sent. If the policy has multiple VMs, and one is removed, you'll get a Success (if you have it checked) email for the VMs that were processed but no notice about the removed VM. Is this expected? It would be a nice safeguard if it's acted similarly to B&R that generates an error saying the VM cannot be found if a Hyper-V/VMware VM is removed.
nielsengelen
Product Manager
Posts: 5999
Liked: 1252 times
Joined: Jul 15, 2013 11:09 am
Full Name: Niels Engelen
Contact:

Re: Job/Policy Failure Notifications

Post by nielsengelen »

Hi Greg,

This looks like unexpected behavior and we'll verify this.

Have you considered using tags as a resource to protect your VMs? This way, when they get restored, the new one will be picked up as required by your policies.
GitHub: https://github.com/nielsengelen
Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests