Ok, I subscribed to the list, so no need to Cc me. Thanks to Andrew
and Ian for the helpful replies I have already received.
I suppose since there is no premade solution, I should outline
what I had in mind. It doesn't have much to do with tape
necessarily. Suppose the problem is to backu
What you're proposing is
If a change is made to a file it would automatically create a delta either
on the filesystem or in a special area.
A backup could collasp all deltas in the last timeperiod or back them all up
allowing rollback to previouse versions.
The problems with this are
Deltas wil
> So has anyone implemented this yet, or begun work on it or something
> similar? Thanks for any help. Please mail me directly as I am not
> subscribed to this list.
I don't know of anyone who has implemented this, although I don't
think it would be a huge amount of work. It would be excellent
Hi Ben
There was also work done on xdelta which uses the same algorithm as rsync
that was doing work in this area. I haven't looked at it in a while. I think
that it was hosted at source forge.
--
Ian Willis
-Original Message-
From: Ben Escoto [mailto:[EMAIL PROTECTED]]
Sent: F
Hi, I am curious about the incremental backup method suggested by
Andrew Tridgell on page 92 of his thesis describing rsync. The basic
idea is that signature information would be saved along with the data
and incremental changes could be produced using this data. Some
advantages for incremental
I am running rsync on lots of Win2K machines. It was built from the
rsync 2.4.6 sources using Cygwin.
One issue, the rsyncd.conf file requires a "use chroot=false" for
the deamon to run on Windows.
Martin Pool wrote:
> On 27 Jun 2001, Christina Kingsberry <[EMAIL PROTECTED]> wrote:
>
On 27 Jun 2001, Christina Kingsberry <[EMAIL PROTECTED]> wrote:
> Is there a version of Rsync for Windows 2000?
I don't know. Do the Win32 binaries not work?
--
Martin
If transfers complete normally, all the processes go away. But if I
hit ^C to stop the client side when connected to an rsync daemon, the
daemon does not go away. It also still has the file it was sending
open for read (according to lsof). Also, lsof shows the socket
descriptor is still open, a
