Richard Scott
richard-at-pointb.co.uk |Lists/Send to lists| wrote:
I'm guessing that your running mysqldump each night to dump to a flat file? If so, duplicity will see this "flat file" as a brand new file (each night) and take a full backup of it (each night) :-( I think its something to do with the file having a different inode or something?
If anyone else on this list as a different view, please shout :-)
Because it use librsync, large files that change only little lead to small backups, irrespective of inode or whatever.
Perhaps the mysqldump output contains many timestamps or other things, that make these large files very different. But if they're similar, that should lead to small incremental backups.
Peter
--
Peter Valdemar Mørch
http://www.morch.com
Hi,
But they are separate full Mysqldump's so they will be created seperately, I suppose it doesn't really matter and the real issue is with my backup method not duplicity.
Thanks,
Will