public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Sander <sander@humilis.net>
To: Eric Mesa <ericsbinaryworld@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Understanding btrfs and backups
Date: Fri, 7 Mar 2014 16:14:16 +0100	[thread overview]
Message-ID: <20140307151416.GA29687@panda> (raw)
In-Reply-To: <loom.20140307T144540-512@post.gmane.org>

Eric Mesa wrote (ao):
> Duncan - thanks for this comprehensive explanation. For a huge portion of
> your reply...I was all wondering why you and others were saying snapshots
> aren't backups. They certainly SEEMED like backups. But now I see that the
> problem is one of precise terminology vs colloquialisms. In other words,
> snapsshots are not backups in and of themselves. They are like Mac's Time
> Machine. BUT if you take these snapshots and then put them on another media
> - whether that's local or not - THEN you have backups. Am I right, or am I
> still missing something subtle? 

Snapshots are backups, but only protect you against a limited amount of
disasters. Snapshots are very convenient to quickly go back in time for
some or all files and directories. 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.

The convenience of snapshots is that you can (almost) make them as often
as you want, fully automated, with (almost) no impact on performance,
without the need for extra hardware, and a restore is no more than a
simple copy.

	Sander

  reply	other threads:[~2014-03-07 15:14 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 [this message]
2014-03-09  4:13       ` Chris Samuel
2014-03-09 15:30         ` Duncan
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=20140307151416.GA29687@panda \
    --to=sander@humilis.net \
    --cc=ericsbinaryworld@gmail.com \
    --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