Date: Tue, 22 May 2007 13:39:39 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Gore Jarold <gore_jarold@yahoo.com> Cc: freebsd-fs@freebsd.org, Brooks Davis <brooks@freebsd.org> Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... Message-ID: <86r6p9xf2c.fsf@dwp.des.no> In-Reply-To: <475187.33232.qm@web63006.mail.re1.yahoo.com> (Gore Jarold's message of "Mon\, 21 May 2007 12\:16\:33 -0700 \(PDT\)") References: <475187.33232.qm@web63006.mail.re1.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Gore Jarold <gore_jarold@yahoo.com> writes: > Specifically, I have private departmental fileservers that other > fileservers rsync to using Mike Rubel-style rsync snapshots: > > http://www.mikerubel.org/computers/rsync_snapshots/ > > This means that the remote system runs a script like this: > > ssh user@host rm -rf backup.2 > ssh user@host mv backup.1 backup.2 > ssh user@host cp -al backup.0 backup.1 > rsync /files user@host:/backup.0 This is extremely inefficient, as you have discovered. Speaking in the abstract, what you want to do every day is the following: client1% rsync --archive --delete /vol server:/backup/client1 client2% rsync --archive --delete /vol server:/backup/client2 server% for vol in /backup/* ; do mksnap_ffs $vol $vol/.snap/`date` ; done No copying or deleting; you take a snapshot when the rsync job is done, and the next day you rsync again to the same directory; only what has actually changed will be transferred, and there is no need to create and populate full copies of each directory tree every time. The easiest way to do this (if you're not afraid to run experimental code) is to use ZFS on the server, as it lets you easily create separate file systems for each client, and creates and maintains snapshots far more cheaply than FFS. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86r6p9xf2c.fsf>