Re: Guide(s?) to backup philosophies
On Tue, Mar 14, 2017 at 12:15:15PM -0700, Miles Fidelman wrote:
> On 3/14/17 11:18 AM, Dan Ritter wrote:
>
> > On Tue, Mar 14, 2017 at 05:54:06PM +0000, Glenn English wrote:
> > > On Mon, Mar 13, 2017 at 12:38 PM, Dan Purgert <dan@djph.net> wrote:
> > > > David Christensen wrote:
> > > > > On 03/11/2017 07:10 AM, Richard Owlett wrote:
> > > > > > I've vague ideas of what backup pattern(s) I might follow.
> > > > > > I'm looking for reading materials that might trigger "I hadn't thought
> > > > > > of that" moments.
> > > > > >
> > > > > > Suggestions?
> > > I didn't see anybody talk about incremental backup (the backup
> > > consists of current versions as well as earlier ones -- often earlier
> > > work can replace erroneous or lost current work. Or work you don't
> > > notice is gone for a few days.). There are 2 I know of, and one (and
> > > probably many more) that may do that:
> > Having been there and done that, I can assure you that having a
> > live snapshot system -- rsnapshot or btrfs/zfs native tools --
> > is more fun and less work for everyone.
> >
> Only if they do versioning. Otherwise, live snapshots mirror deletes - not
> very useful if you want to restore an accidental delete!
All of the systems I mention are versioned (dated) snapshot
systems.
-dsr-
Reply to: