Veritas NetBackup™ OpsCenter 8.0 Reporting Guide
- Reporting in OpsCenter
- About OpsCenter reports
- About managing reports in OpsCenter
- About managing My Reports
- About managing My Dashboard
- About managing reports folders in OpsCenter
- About managing report schedules in OpsCenter
- About managing time schedules in OpsCenter
- OpsCenter reports
- Report Templates in OpsCenter
- About Report Templates descriptions
- About Audit reports
- About Backup reports in OpsCenter
- Job Activity > Variance > Backup Duration Variance report
- Job Activity > Variance > Backup Job Size Variance report
- Job Browser > Tabular Backup Report
- Status & Success Rate > Status > Week At A Glance report
- Status & Success Rate > Status > Job Attempt Status Detail report
- About Catalog reports in OpsCenter
- About Chargeback reports in OpsCenter
- About Client reports in OpsCenter
- Risk Analysis > Client Coverage report
- Virtual Client Summary report
- Job Success by Client report
- BMR client configuration backup failures report
- About Cloud reports
- About Disk and Tape Device Activity reports in OpsCenter
- About Media reports in OpsCenter
- About Performance reports in OpsCenter
- About Policy reports in OpsCenter
- About Restore reports in OpsCenter
- About Storage Lifecycle Policy reports
- About Workload Analyzer reports in OpsCenter
- Custom reports in OpsCenter Analytics
Status & Success Rate > Status > All Failed Backups report
This report is one of three using the advanced success or failure calculation logic around the notion of first, all and last job. They require schedule and window parameters enabling a precise definition of timeframes. Additionally, these reports have aggregation levels of job and client. The first job success or failure is the first job for a client/policy/schedule combination in its defined backup window and last job is the opposite. As failed jobs are rerun one or more times, the "last job" represents the last of the reruns within the window. This report produces the details of the failed jobs based on which one of the three (first or all or last) methods is chosen. The main use case for this report is based on last job where failure notification to users is based around last job and failures leading up to the last one is ignored.