What we primarily covered on CC Backup was the reporting views. You can specify based on Netbackup server, host, date, whatever, and generate a visual report of what backups succeeded and failed, and the error codes. It ties onto a local knowledge base to get what the codes mean, and, if you like, what your local SOP is for resolving the problem.
From a business standpoint, you can assign dollar values to your backups and assign various backup volumes to different departments, so you can produce a report saying 'X department is costing us such-and-so for backups'.
You can do backup trending so you can see growth rates.
CC:backup keeps it's own database, so what it polls from Netbackup can be safely purged from Netbackup's logs and kept in CC for historical purposes.
You can, like the rest of CC, set up alerts so that if certain backups fail, you get an email, and IIRC, there's some form of automated response you can do, like rekickoffs, or something.
Unfortunately, and I may have mentioned this up top, but I can't recall, we were not really able to do any of the active stuff in an hour's time, so we ended up focusing on the reporting. Still very cool.
What I recall of CC: Backup
What we primarily covered on CC Backup was the reporting views. You can specify based on Netbackup server, host, date, whatever, and generate a visual report of what backups succeeded and failed, and the error codes. It ties onto a local knowledge base to get what the codes mean, and, if you like, what your local SOP is for resolving the problem.
From a business standpoint, you can assign dollar values to your backups and assign various backup volumes to different departments, so you can produce a report saying 'X department is costing us such-and-so for backups'.
You can do backup trending so you can see growth rates.
CC:backup keeps it's own database, so what it polls from Netbackup can be safely purged from Netbackup's logs and kept in CC for historical purposes.
You can, like the rest of CC, set up alerts so that if certain backups fail, you get an email, and IIRC, there's some form of automated response you can do, like rekickoffs, or something.
Unfortunately, and I may have mentioned this up top, but I can't recall, we were not really able to do any of the active stuff in an hour's time, so we ended up focusing on the reporting. Still very cool.