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

We're in the midst of re-organizing our backup solution. We currently have several different tools and scripts running on various machines in our network which run backups autonomously. In the end, all the backups are to be consolidated onto a single NAS which will be rotated weekly.

What we'd like is something that tracks all of the final backups on the NAS and lets us know when one of them failed to occur. Before rotating the NAS', the invididual would first check some form of report to find out if all the "backup targets" have been updated.

Are there any existing solutions? We're a small enterprise so it can't be very expensive (ideally free).

share|improve this question
up vote 2 down vote accepted

You should look into centralizing your backup process with a solution like Bacula or the myriad of non-free solutions. Other solutions might fit your environment better, but you haven't listed any details of what OS, the quantity of servers/data, or other specifics.

Links provided for ideas and do not represent an exhaustive list by any means.

share|improve this answer
I'm not looking for an all-in-one backup solution. I want to keep it open to being a mixture of methods. I'm just looking for a way to report on the final backup to the NAS. We're mostly a Windows environment but I'll install linux on a box if I need to. – Mr Grieves Sep 9 '10 at 17:08
+1 for bacula. We backup several dozen servers with it, and it feeds its results into an EMC Networker (which then goes to tape). Works like a charm, with fully configurable notifications. – wolfgangsz Sep 9 '10 at 17:09
@Mr Grieves, without knowing what software you're currently using I have no way of knowing if it can be configured to report results or send notifications. I'm guessing that you're using a "solution" that's fairly duct-taped together and are simply hoping that everything works as intended. The reason most places ditch such methods are the very problems you are bringing up. Business mature, and their needs change; sounds like it's time for the Backup Methods to change with the business needs. – Chris S Sep 9 '10 at 17:13
@Mr Grieves - if you're hard-set on using your homebrewed solution, one thing you could do pretty easily is to add logic to your scripts to email you the stderr output of each script. At least with that, you'll know pretty quickly when something goes awry. – EEAA Sep 9 '10 at 17:37
All good advice. Thanks for replying. – Mr Grieves Sep 9 '10 at 19:24

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.