From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <alpine.BSF.2.21.1.1804161610070.99230@orthanc.ca>
References: <alpine.BSF.2.21.1.1804161610070.99230@orthanc.ca>
From: Steven Stallion <sstallion@gmail.com>
Date: Mon, 16 Apr 2018 21:15:42 -0500
Message-ID: <CAGGHmKF5QinRQQai8VB-5eCwiV3Z2M8aRF+WR0JV+nrTXdqp9A@mail.gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [9fans] fossil+venti vs. cwfs - dealing with backups
Topicbox-Message-UUID: d48c8bc2-ead9-11e9-9d60-3106f5b1d025

The easiest method with cwfs or Ken's is to keep track of the size of
the WORM - since everything is appended, it's fairly simple to copy
the set of blocks after each dump. It's been a few years since I've
done this, but it is just as reliable as venti, albeit less
convenient.

On Mon, Apr 16, 2018 at 6:15 PM, Lyndon Nerenberg <lyndon@orthanc.ca> wrote:
> What has kept me running fossil+venti is the ease of backing up the file
> server.  Copying the venti arenas offsite is trivial.  And Geoff put
> together glue to write sealed arenas to blu-ray as well.
>
> I don't see any simple way to do that with cwfs*.  Or hjfs.  I am very
> curious to know how the not-fossil/venti FS servers are backing up. Share?
>
> --lyndon
>
>