----- Original Message ---- > From: Les Mikesell <lesmikesell at gmail.com> > To: CentOS mailing list <centos at centos.org> > Sent: Wed, January 13, 2010 2:49:11 PM > Subject: Re: [CentOS] Backup server > > Sorin Srbu wrote: > >> -----Original Message----- > >> From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On > > Behalf > >> Of Barry Brimer > >> Sent: Wednesday, January 13, 2010 2:15 PM > >> To: CentOS mailing list > >> Subject: Re: [CentOS] Backup server > >> > >> I use rsnapshot .. which manages sets of rsync backups using hardlinks. > >> IT may be similar to what you are using already .. > > > > Somewhat similar, thanks. I think however I need to get away from this sort > > of backups. They're just to space-consuming. > > Between compression and pooling, I get about 10x the raw data being archived > with backuppc - it beats juggling tapes and you can let the users access the > backups of their own machine through a web interface. There are some down sides > > to plan around though: the compression takes some CPU and is slower than a stock > > rsync run, and the pooling is done with hardlinks which forces the archive to be > > on a single filesystem and makes it hard to duplicate for offsite copies. > There's an RPM in epel that is easy to install on Centos. One thing that made me not use BackupPC was that (from the doc): "The advantage of the mod_perl setup is that no setuid script is needed, and there is a huge performance advantage.... The typical speedup is around 15 times. To use mod_perl you need to run Apache as user __BACKUPPCUSER__. If you need to run multiple Apache's for different services then you need to create multiple top-level Apache directories, each with their own config file. You can make copies of /etc/init.d/httpd and use the -d option to httpd to point each http to a different top-level directory. Or you can use the -f option to explicitly point to the config file. Multiple Apache's will run on different Ports (eg: 80 is standard, 8080 is a typical alternative port accessed via http://yourhost.com:8080)." Since I don't have a dedicated backup server, I did not want to mess up the existing apache configurations... JD