Feature Request:Fill "LAST RESULT" field for continuous jobs

[Dytech]

Hello,

we are checking the "Last Result" with Powershell to monitor if a Backup Copy Job Completed successfully. That works for normal jobs, but on a "Copy Job" the "Last Result" field is only filled, while the Job is deaktivated. As soon its enabled, the last result status is gone and we can't check it.

Also, it would be nice to it directly in the Gui at the Copy Job that something is wrong with the job, at the moment the job look great, even if its not working.



We already talked to support and as a workaround we, are deaktivating the job, then start the check and then reaktivate it. That is working, but now we get new History events every time a check is executed. This spams our history log.

Best Regards,
Rafael

[Gostev]

Hi, we'll take a look why it is not set. Thanks!

[billcouper]

+1 to this, have same issue, already raised a support ticket in the past and it couldn't be solved.
last result only shows for jobs that are not running. but continuous backup copies are continuous

[Vek17]

Definitely worth adding. Visibility for backup copies is relatively poor.

[Mgamerz]

Same issue here, I thought this was by design, though I thought it was pretty poor design.

[veremin]

We discussed this enhancement internally - the results were positive. So, there is a chance that the corresponding field (for bcj) will be added in the next product update. Thanks.

[Dytech]

Hello All.

any News on this ?

Best Regards

[foggy]

This is included in U4.

[Dytech]

Thanks a lot !

any news when U4 is coming out ?

[Dima P.]

Dytech,

The plan is to make Update 4 generally available on January 22nd. Cheers!

The biggest news today is actually old news from 2018, but something many of you have really been waiting for: we did ship the RTM build of long-awaited Update 4 for Veeam Backup & Replication 9.5, as well as Veeam Agents 3.0 before the end of last year - on December 28th. Kudos to our amazing R&D for all their hard work in the last weeks of the year! It is certainly the biggest release in the history of Veeam – not only by the sheer number of new features (and lines of code), but also by the number of new innovations. The best place to learn about all of them will be at the live launch web cast, currently planned on January 22nd - which is also when we're aiming to make all new releases generally available (GA).

[Gostev]

Having said that, you can get it through support already, in case you want to be a part of pilot deployments.

[Dytech]

Thanks for Your info, i will do that next time.

So, I have tested the new build and in the gui its looking good, but with Powershell its still not working, and thats the important part for monitoring.

$job = get-vbrjob -name "BackupSyncJob"
$job.GetLastResult() still returns "None". I still need to disable the Job to get the last result.

Best Regards.

[veremin]

Try the following the example and see whether there is something you're after:

Code: Select all

Asnp VeeamPSSnapin
$Job = Get-VBRJob -name "Name of your backup job"
$Job.Info.LatestStatus

Thanks!

[billcouper]

Another way is to specifically look for job failures.

Code: Select all

Asnp VeeamPSSnapin
$Job = Get-VBRJob -Name "Job Name"
$Session = $job.FindLastSession()
if ($session.Info.Failures -gt 0) {
  # Do something with the failures, eg pull the error text out of them
} else {
  # The job was successful
}