Excluded Hyper-V VM still being backed up?

[BrianBuchanan]

Hello,

I have case #07656572 open about a backup job that backs up three hosts and two VMs need to be excluded from Application Aware Processing but they stopped being excluded after the latest upgrade. I'm not sure the upgrade is the cause because last night I excluded the two VMs entirely (e.g. Edit the job, Virtual Machines, Exclude and then added the two VMs) but they are still getting included in the backup.

This job started life as backing up a VMM Host Group but since then we've decided to move away from VMM and we've been adding the hosts directly to Veeam. We then changed the job's selection criteria from the VMM Host Group to the hosts. I have a feeling the problem is because the job has the old VMM reference and the exclusion is the VMID so they get backed up. Then the same is happening for the Application Aware Processing, the backup reference and the exclude reference don't match so the VMs are not excluded from AAP. I found KB 1299 which is the opposite situation, and I've removed and added the hosts and removed and added the exclusion but they still get backed up.

I don't think Veeam uses the CLUSTER-INVARIANT tag on the VMs but since those are still in the notes for the VMs maybe that's coming into play?

Maybe if I clean up VMM by removing the hosts and clearing the CLUSTER-INVARIANT tag the exclusion will start matching? I don't think I can change the VMID.

The original case was about failing to make a production snapshot, but I think it's more about the selection and exclusion criteria not matching.

Thanks for any advice!

[PetrM]

Hi Brian,

I believe the best action plan is to wait for the results of the investigation from our support engineers. I think they should compare the VMIDs in the debug logs to determine the root cause, but it is definitely not something we can address through forum posts.

Thanks!