Date: Sat, 7 Apr 2007 17:00:08 +0100 (BST) From: Mike Wolman <mike@nux.co.uk> To: Jim Rees <rees@umich.edu>, freebsd-fs@freebsd.org, freebsd-questions@freebsd.org Subject: Re: some thoughts about gmirror Message-ID: <20070407164235.F33915@nux.eros.office> In-Reply-To: <20070407115854.GA14402@citi.umich.edu> References: <219395.34786.qm@web30302.mail.mud.yahoo.com> <20070407103057.P20396@nux.eros.office> <20070407115854.GA14402@citi.umich.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> if you were keeping track of the blocks which had changed > then you do not need to generate this list and simply send over the > changed blocks. > > Unison keeps a list of files at each end and only exchanges block lists for > files that have changed. I use it to sync 40GB (10K files) over a 1Mbps > link and it's very fast. It also will do two-way sync. > Unison and rsync both work on the filesystem level and not with the blocks directly so would not be able to achieve the same result as the live network backup on netbsd - ie allowing a simple dd restore of a machine. As this would be filesystem independent and if you are running zfs or other snapshot capable filesystem i think rsync or unison would have a problem working with the snapshots. i do use rsync with close to about 1Tb of data and a lot hard links for - but if the remote file changes you have to store the entire copy of new file and not just the actual blocks which have changed. Mike. On Sat, 7 Apr 2007, Jim Rees wrote: > Mike Wolman wrote: > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070407164235.F33915>