Backup job state

[matteu]

Hello,

I use TAG to backup my VM.
As recommended per VM I create a catch all job in VBR with all my vcenter selected and exclude all VM with the TAG category.

My issue is the job will always be warning result when there is no VM to process and this alarm appears....

What is my solution to avoid it ?

The no tag job could have VM to backup and get success / warning / failed result state.... The idea is to get an alarm ONLY if there is a VM processed inside this JOB.

[RomanK]

Hello matteu,

The Backup job state alarm must return the same job state as VBR. Unfortunately, there is no per-warning filter, as there are a lot of warnings that could appear.
The possible solutions at the moment are: to disable the alarm, disable the warning rule or recreate the backup job another way.

Thanks

[matteu]

Thanks for your answer.

Disable the alarm is not good... This alarm is usefull.
Disable the warning rule means I lost all warning for other job > not good
Recreate the backup job an other way mean no automated way to backup missed tag VM -> not good too...

Maybe I have an other idea :
I could also accept to not monitoring this specific job for warning...
I can add rules to exclude the job name and it should work right ?
Then I create a new alarm only for this job for success and failed state

I think this alarm is a keep to know how backup job end.

So, improvement for this alarm could be to add a field to exclude backup job name as it exists on some other alarm

[RomanK]

Hello matteu,

The only complication with excluding could be that alarms support only ‘*’ (asterisk) and ‘?’ (question mark) wildcards. The ‘*’ (asterisk) character represents zero or more characters. The ‘?’ (question mark) stands for a single character.
Currently, negations are not supported in the rules.

Thanks