Add new comment

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Submitted by /dev/kev (not registered) on Fri, 2009-03-20 01:12.
I'm somewhat amazed that you found rdiff-backup to be faster over sshfs than rdiff-backup directly over ssh.

When rdiff-backup is running at each end of the ssh link, then the rdiff-backup processes can compute rolling checksums and exchange those to determine which files have changed (and where in the file the changes are). This is the main advantage (and the whole point, really) of the rsync algorithm.

But when using sshfs, rdiff-backup sees only two "local" files. It will then compute these rolling checksums on both files itself, by reading in each file. Surely this causes the entire file to be fetched by sshfs? And surely this will (in general) be slower than with an rdiff-backup process at the other end which is sending only checksums, not the whole file...

About the only time I can figure that sshfs access might be faster is during an initial backup, when none of the files actually exist in the backup, and so there are no rolling checksums to compute and compare.

Please do not use the comment function to ask for help! If you need help, please use our forum.
Comments will be published after administrator approval.

Reply

*
*
The content of this field is kept private and will not be shown publicly.


*

  • Images can be added to this post.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <div>
  • Lines and paragraphs break automatically.