public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Understanding btrfs and backups
Date: Sun, 9 Mar 2014 15:30:44 +0000 (UTC)	[thread overview]
Message-ID: <pan$4cd4c$ec8dd4e1$f6cb92a9$89c62709@cox.net> (raw)
In-Reply-To: 1959641.msLoxygPan@quad

Chris Samuel posted on Sun, 09 Mar 2014 15:13:42 +1100 as excerpted:

> On Fri, 7 Mar 2014 04:14:16 PM Sander wrote:
> 
>> But if the filesystem or underlaying disk goes up in flames, the
>> snapshots are toast as well. So you need additional backups, preferably
>> not on the same hardware, for real protection against data loss.
> 
> ...and don't forget to think about off-site backups too.
> 
> http://www.flickr.com/photos/94482242@N00/7746409996/

While I realize that was in reference to the "up in flames" comment and 
presumably if there's a need to worry about that, offsite backup /is/ of 
some value, for some people, offsite backup really isn't that valuable.

I figure if something like that happens here, I'll have FAR more pressing 
things to worry about for awhile than restoring my computer.  And by the 
time life does get somewhat back to normal and I can think about the data 
that was on the computer, I might as well do over from scratch, like I 
will have done with much of the rest of my life by that point.  The real 
valuable data is backed up where it counts -- to my head -- and if I lose 
that, well, I won't be very worried about it any more, will I?

Of course if I were a bush doctor like the guy who owned the computer in 
that photo apparently was, then there'd be other people's medical records 
and the like to worry about too, and having offsite backups of that 
/would/ be important!

And of course the same would apply if I had a bunch of family pictures on 
the computer to worry about, but for that I'd need a family first...

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2014-03-09 15:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06 18:18 Understanding btrfs and backups Eric Mesa
2014-03-06 21:33 ` Duncan
2014-03-07 10:13   ` Wolfgang Mader
2014-03-09 15:46     ` Duncan
2014-03-07 14:03   ` Eric Mesa
2014-03-07 15:14     ` Sander
2014-03-09  4:13       ` Chris Samuel
2014-03-09 15:30         ` Duncan [this message]
2014-03-13  8:18           ` Chris Samuel
2014-03-09 16:40     ` Duncan
2014-03-11  0:39       ` Testing BTRFS Lists
2014-03-11  1:02         ` Avi Miller
2014-03-11 19:08           ` Eric Sandeen
2014-03-11 20:30             ` Avi Miller
2014-03-12 11:15             ` xfstests btrfs/035 (was Re: Testing BTRFS) David Disseldorp
2014-03-13 18:10           ` Testing BTRFS Lists
2014-03-13 20:20             ` Avi Miller
2014-03-11 13:33         ` Josef Bacik
2014-03-13 17:12     ` Understanding btrfs and backups Chris Murphy
2014-03-17  5:42   ` Understanding btrfs and backups => automatic snapshot script Marc MERLIN
2014-03-21  5:57     ` Marc MERLIN
2014-03-21  7:41       ` Duncan
  -- strict thread matches above, loose matches on Subject: below --
2014-03-06 19:27 Understanding btrfs and backups Eric Mesa
2014-03-06 21:17 ` Brendan Hide
2014-03-06 20:37 Eric Mesa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='pan$4cd4c$ec8dd4e1$f6cb92a9$89c62709@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox