How to have an Inclusive only Backup Tag, and Healthy Backup Report?

DustinB

This is a bit of a test that I'm checking, basically with how does XO backup direct to B2 work, in my test I excluded 1 VM (obscured name below), and I created a new job (first screenshot) that included only this VM.

With the above inclusive only tag all of the other VM's on the Pool then show as "Not Belonging" or "Missing Schedule" on this job.

The fact that every other VM shows as being inclusive on the job, when they shouldn't be is weird.

Danp

To be clear, you're questioning why these items in the 2nd screenshot appear in the Backup > Health view following the addition of a new backup job?

DustinB

@Danp more specifically,

I have a backup job, that has a single VM included (via tags), and then within the health view, everything else is essentially "unhealthy" even though those other VMs are not a part of the obscured job at the bottom of the second screenshot.

The VM listed in the "This VM does not belong to this job" is the same VM that is included in the Obscured job name.

I'm just trying to make sense, how a Job that doesn't include a VM, but potentially could because they are all on the same pool, is considered unhealthy, why they aren't being backed up by that job.

Seems like a logic fault.

Danp

@DustinB I was able to reproduce this behavior, and someone from the XO team (likely @julien-f ) will take a closer look.

DustinB

@Danp Thanks for confirming!

Danp

@DustinB This appears to be fixed. Can you confirm?

DustinB

@Danp said in How to have an Inclusive only Backup Tag, and Healthy Backup Report?:

@DustinB This appears to be fixed. Can you confirm?

I'll update this Monday with what I find.

Thanks for getting back to this.

DustinB

@Danp Appears to be fixed