Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On site we have near 3 dozen servers, a mixture of physical and virtual, some backup to tape and others to disk, a few important machines do both.

All in all we have about 40 backup jobs. I record the success or failure, and probable cause, for each job. Now I've been asked to put all this information in to a "report". Which will be viewed by non-IT persons. Lots of graphs

So, I would appreciate opinions on what could consider worthwhile and should be included.

So far I've got:

  • Overall Success Rate
  • Off-Site Backup Success Rate
  • Month Success Rate
  • Day Success Rate - just for IT, handy for seeing failing tapes.
  • Common Failure Causes

This can include items of worth just for IT.

share|improve this question
What did "they" ask you to include in the report? If they didn't define what it is "they" want to see then I would ask them to do so. – joeqwerty Mar 4 '11 at 12:08
up vote 2 down vote accepted

It might be useful to report time taken for each backup. As backup job duration usually increases over time, you want to be aware of any that suddenly take longer or might impinge on the operational timeframe of the applications on the host.

share|improve this answer
Increased time on backups may also indicate a possible device failure in the near future, either the device being backup up, or the device where the backups are being stored, especially if the backup size hasn't changed much. – JeffG Mar 4 '11 at 15:15

Successfully completed and tested restores is the most important metric you could provide.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.