Your message dated 
with message-id <[email protected]>
and subject line faubackup removed from Debian unstable
has caused the Debian Bug report #144388,
regarding faubackup: make remote backup efficient 
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
144388: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=144388
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: faubackup
Version: 0.5pre1-1
Severity: wishlist

Hi,

after the second report I should probably confess that I quite like
faubackup!

Ok, now to my problem: backup up megabytes over the wire is slow.
Since faubackup's central idea is the discovery that most backupped
data is usually unchanged from the last backup, why not transfer only
the changed files?

I'd probably do it as follows: The local end (where I start faubackup)
sends the md5sums of the files from the last backup to the remote end
(where the data to backup lies). For each file the remote end either
sends a "no change" signal (if the md5sum is equal), or the new
version of the file (otherwise).

Another possibility is to build on the power of rsync. I don't know
the inner working of faubackup too well, but maybe it would be just as
simple as creating a new backup tree by recursive hardlinking the last
backup, and then running a "rsync -r" over the new tree.

-- 
Robbe


--- End Message ---
--- Begin Message ---
Version: 0.5.9+rm

faubackup has been removed from Debian unstable: http://bugs.debian.org/520013

Closing its bugs with a Version higher than the last unstable upload.

More information about this script at:
  
http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD


--- End Message ---

Reply via email to