Feature Request: Job Aborted

[dellock6]

Hi guys,
I spent two hours with a customer last week, trying to explain me about some backup jobs failing without any apparent reason. Long story short, at the end we find out that another sysadmin was looking at those jobs, and since they were ending in the mid morning, he was worried about impacting production environment and he was cancelling them #facepalm

Maybe is a silly request, but is it possible to send the job report as "aborted" (and maybe also by who) instead of "failed"? Technically speaking, an aborted job is not failed...

Thanks,
Luca.

[Gostev]

Hi Luca, I will discuss with the devs if this is something easy to do. Thanks for the feedback! Although I am puzzled why the reason was not immediately clear for your customer from just looking at the job session history (aborted jobs say "terminated by user").

[dellock6]

I tried before all to ask "did someone killed the job?" and they confirm in first place noone did. Probably "noone" is one of their sysadmin

Luca.

[Yuki]

By the way - this is something i fully support and agree with. Furthermore, i think a distinction between Aborted and Failed should be mode not only in the GUI interface as far as how it's reflected, but also in the e-mail notification engine. So if the job is aborted - it is either shown as Aborted in the panic e-mail or even better - have a check mark to allow for exclusion of Aborted jobs from reporting.

[dellock6]

And obviously, even in the Get-VBRBackupSession.Result, so scripts can filter out (or search for) "aborted" in addition to the usual three states.

Luca.

[m.novelli]

+1

Marco