BackupPC-users

Re: [BackupPC-users] BackupPC very slow backing up 25GB files

2011-02-02 11:23:00
Subject: Re: [BackupPC-users] BackupPC very slow backing up 25GB files
From: Stephen Joyce <stephen AT physics.unc DOT edu>
To: "General list for user discussion, questions and support" <backuppc-users AT lists.sourceforge DOT net>
Date: Wed, 2 Feb 2011 11:08:30 -0500 (EST)
Wouldn't it be easier to eliminate the problem? BackupPC is comparing the 
files to determine if they're identical (normally using lots of CPU to 
uncompress the pooled file, but since you're not using compression, that's 
not your issue).

Why not simply name your database dump differently each time it occurs? My 
database dumps are named with YYYY-MM-DD in the name and my database dump 
script removes all but the last X dump files from the local disk (which is 
then backed up nightly by BackupPC).

This works incredibly well for me without the time disparity you mention 
between fulls and incrementals (since the incremental does a "full" backup 
of new files and incr of existing files). YMMV.

Cheers,
Stephen

On Wed, 2 Feb 2011, John Goerzen wrote:

> Carl Wilhelm Soderstrom <chrome <at> real-time.com> writes:
>
>> 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.
>
> That's an interesting point.  I will give tar a try.  For most servers, the
> drawbacks (relating to timestamp issues; see
> http://www.mail-archive.com/backuppc-users AT lists.sourceforge DOT 
> net/msg13478.html
> and the thread surrounding it) would be a problem.  For this particular one, 
> it
> probably wouldn't be.
>
> I think tar's exclude pattern matching works differently than rsync's, which
> will be a bit annoying, but livable.
>
>> Can you get the database backup broken into smaller chunks? Say per-table
>> backups rather than one giant dump of the whole database?
>
> This *is* the smallest possible chunk, sadly ;-)
>
>> 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.
>
> An excellent idea as well.  I like that and will give it a shot.
>
> -- John
>
>

------------------------------------------------------------------------------
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/