This is exactly what I was looking for. I'm going to join the
duplicity list, as I do have some rookie questions.
Thanks, Dean!
On Aug 12, 2009, at 22:42:34, Dean Cording wrote:
rdiff-backup gets most of its advantage by running running a server
process on
the destination machine that keeps a lot of the disk access local.
When you
run rdiff-backup on a networked drive you lose this advantage
because the
client and server processes bot run on the local machine and all
disk access
is across the wire.
You might find Duplicity (http://duplicity.nongnu.org) is better
suited to your
arrangement. Duplicity also uses the rdiff algorithm but it keeps
the metadata
locally and creates local backup archives which are uploaded when
completed.
Dean
_______________________________________________
rdiff-backup-users mailing list at [email protected]
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
_______________________________________________
rdiff-backup-users mailing list at [email protected]
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
