On 02/02 03:12 , John Goerzen wrote:
> So I should add that additional testing shows that it was only the first full
> backup that was fast.  Every subsequent backup, whether full or incremental,
> proceeded at the same very slow pace.  rsync pegged at almost 100% CPU on the
> machine being backed up either way.

You may want to experiment with using tar instead of rsync for your backups.
Tar is notably faster than rsync when you know you're going to grab a large
percentage of changed files.

Can you get the database backup broken into smaller chunks? Say per-table
backups rather than one giant dump of the whole database?

You may want to consider a separate backup profile of the database dumps. So
set up one backup for the rest of the machine; and another backup (using
$Conf{ClientNameAlias} to point to the desired machine) just to back up the
database. That way you can use rsync for one and tar for the other.

-- 
Carl Soderstrom
Systems Administrator
Real-Time Enterprises
www.real-time.com

------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/