Custom Job History Report Not Displaying Media Labels
Goal: Generate a report showing the latest weekly duplicate-to-tape jobs. This report will be stored along with the media in our offsite location so it can be referenced in case of DR (and loss of catalogs), letting us easily find the latest tape(s).
The custom report I've created contains the backup jobs that were duplicated to tape, date, status, and the media label.
Problem 1: The media label is not displayed in the report.
Problem 2: The preview looks good (other than missing media labels), but running the report generates about 20 duplicates per job. It appears to be displaying 1 entry per backup set (i.e. ServerName C:, ServerName D:, ServerName: SystemState, and then repeat everything again for verify). Is there any way to get the job history reports to list jobs by job name instead of backup set(?) so there is only one listing per job?
The report is configured as follows:
Job History Group
Job End Time
Total Data Size
Media set Name = 'LTO5 - Weekly'
Job End Time IN LAST 4 Days
Group by: Server
Sort on: Server
Then sort on: Job Name
This is a run of the report:
I looked through the Media Group fields, but there doesn't appear to be a way to show the jobs that are stored on the latest tape.
The media fields also appear to be different in the different report categories. The Job History Group has a field for Media Cartridge Name (where is this specified?) which also shows up blank in the above report, while the Media Group has a field for Media Cartridge Label, which does show the media label.
What is difference between Media Cartridge Name, Media Cartridge Label, and Media Label?
Why are Media Label and Media Cartridge Name available fields in the Job History group if they don't display any data? Is there a requirement for another field to be displayed in order to get these fields to show data?
Finally, if there is a better/correct way for me to get the desired report please let me know. If I can't get the above working I guess I'll have to write a few SQL queries and reports myself, but it doesn't seem like this should be necessary for what are fairly basic queries.