From: Nick Knight <nick@om...> - 2004-03-26 08:56:44
I am trying out 2.1beta - and so far it looks great, couple of things
1/ When you cancel a job sometimes it creates a partial backup and
sometimes it doesn't - any idea why?
2/ I saw mentioned in a doc or a previous thread that development of
storing diffs was under discussion, can I add a vote for that please?
The main reason is performing backups from Win32 machines (and or Linux
machines). When you backup the system state (or even Exchange for
example) you need to create an NT backup file, which are potentially
large but only contain a small number of diffs through them, this makes
the transfer through rsync really efficient but currently the storage
of them quiet poor.
As a second point to this, what about this as an improved transfer
method, the problems I am generally faced with
1/ Permissions from source server/pc differ and never get transfered,
when recovering a large install all the permissions on a server need to
2/ When some-one renames a directory - then slows down the backup,
rsync has to transfer the whole lot again
Use system dependent program to generate backup file (tar for Linux,
ntbackup for windows), this then gets transfered (and in my experience
is quite efficient - even when a directory is renamed), this preserves
the permission's much better, the only downside at the moment is
storage becomes very large - hence would require diff storage. The
second downside would be browsing the file structure would be more
tricky - especially cataloging an NT backup file!!
Just some of my thoughts and ramblings!!