We went really simple with all the rsync commands being run from the same machine. We point all the output from the rsync to a log file in /var/log and then I usually just tail the file on a daily basis. Also if it runs into actual errors cron ends up mailing directly. We use this on our clusters to good effect though we use batched ssh calls to tell each cluster node to run their backups but it is all called from the same script on our head node so that only one backup opperation is running at a time. It makes the logs cleaner and we don't run into a problem with dozens of boxes all trying to sync data back to the head node at the same time and slowing things down. Rob On 8/28/07, Les Mikesell <lesmikesell at gmail.com> wrote: > > dnk wrote: > > Hi there, I was wondering whay people were using to monitor rsync > > backups on centos? > > > > I have been looking around sourceforge for various programs (IE Backup > > Monitor), but am hesitant to trust any of them without hearing about > > some user experiences. > > > > We currently just use rsync for backups (like a slightly more > > "Vanilla" setup), but just want to be sure everything is going as it > > should each day.... > > I like backuppc (http://backuppc.sourceforge.net/) which is a little > more than a monitor, but it will email you if things go wrong and has a > nice web page to check. > > -- > Les Mikesell > lesmikesell at gmail.com > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070830/16007c73/attachment-0005.html>