Veritas NetBackup™ OpsCenter 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
About data collection from EMM
The SLP1 performs the following operations:
data that is shown in the SLP reports is collected from the EMM worklist and the NetBackup catalog. The worklist is located in the EMM and contains metadata like how many copies need to be created, where they need to be created, when they are completed etc. In general, the copy data that is shown in the SLP reports (like Copies Completed, Completed Copy Size columns etc.) is based on the EMM worklist. EMM creates the worklist after a backup is complete based on lifecycle configuration parameters.
Consider a case when you configure an SLP named SLP1:
Backup (Stu1)
Duplication (Stu2)
Duplication (Stu3)
After the backup is complete, a worklist that contains an entry for each copy is created in the EMM database. In this example, the EMM worklist has three copy entries (corresponding to the number of copies that are defined in the SLP). The EMM worklist is updated as and when a duplication job is processed (for example, State for the copy changes from Not Started to In Process to Complete).