Report show's failed on form header even though the session is successful about powershell HOT 6 CLOSED

Hi @gveater. Can you please double check whether the job failed on a synthetic operation, such as incremental backup file merge or synthetic full creation? This is typically the reason for such reports.

from powershell.

Adding author @tdewin as well.

from powershell.

We are currently testing on how to move our copy to external media jobs so I have had multiple failures for various reasons on this job. The last two failure were unexpected failures, from me stopping the job. Before that there were a lot of media not found. This itself is a Backup Copy job. From my understanding it does a synthetic full with whatever backup is currently on that HDD.

from powershell.

Confirmed, this can be checked by running limited code below. Backup Copy Job (or backupsync) return status None

$jobtype = "BackupSync"
#$jobtype = "Backup"
$Jobs = @(Get-VBRJob | ? { $_.JobType -ieq $jobtype }) | Sort-Object -Property Name

$allsessions = Get-VBRBackupSession | ? { $_.jobtype -ieq $jobtype } 
$allorderdedsess = $allsessions | Sort-Object -Property CreationTimeUTC -Descending  

foreach ($Job in $Jobs) {
     $lastsession = $allorderdedsess | ? { $_.jobname -eq $Job.Name } | select -First 1
     if ($lastsession -ne $null) {
            write-host ("Name : {0} Last Result : {1}  Date : {2}" -f $Job.Name,$lastsession.Result,$lastsession.CreationTime)
     } else {
           write-host ("Could not find Session for {0}" -f $Job.Name)
     }
} 

from powershell.

Update is in pull request now. Code manually evaluates "Success". Case can be closed when PR is committed.

from powershell.

Closing. Fixed in PR #11. Thanks @tdewin and @gveater.

from powershell.