On Fri, Feb 06, 2009 at 08:04:57AM -0800, Michael L. Barrow wrote in a
non-list copied email:
>In my experience, rsync doesn't play nice with really big files for
>incremental updates. I recommend that you have a unique filename so
>that you basically end up with a full backup each time around.
In this problem I am backing up on the same lan, in production it will
be backed up offsite across a slow wan, so compression and rsync
algorithms will be key.
It was working well enough before the last major database change, so I
concur that large difference in a large file appear to be causing
issues, but it looks like the problem is on the backuppc end.
Hmm, maybe if I change the rsync command for that host to include
--whole-file I can get a new baseline. Does anybody know if the rsync
perl library used by BackupPC can handle whole-file mode?
Usually the incremental changes between the files are under 100MB of
the 36GB file which makes doing daily backups possible.
Using just plain rsync (2.x) on both sides across the wan works fine
and results in a huge speedup.
But thanks for the caution. That gives me another avenue to test at
least although it may result in having to dump backupc.
--
-- rouilj
John Rouillard
System Administrator
Renesys Corporation
603-244-9084 (cell)
603-643-9300 x 111
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
