linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Fajar A. Nugraha" <list@fajar.net>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: How Snapshots Inter-relate?
Date: Fri, 22 Apr 2011 22:30:05 +0700	[thread overview]
Message-ID: <BANLkTinkYrzO8xA4B32=xFDP7zmWJ-zaHQ@mail.gmail.com> (raw)
In-Reply-To: <201104220803.20552.CACook@quantum-sci.com>

On Fri, Apr 22, 2011 at 10:03 PM,  <CACook@quantum-sci.com> wrote:
> Would it be good practice to say, once a year, do a completely new fresh snapshot?

There's no such thing as "new fresh snapshot".

You can create a new, empty subvolume.
Or you can create snapshot of existing root/subvolume, which once
created, behaves just like another subvolume (with the exception that
it contains identical content to the origin root/subvolume).
Or you can create snapshot of a snapshot (which, again, is just
another subvolume with identical content) so in practice there will be
no difference between the first snapshot and the second snapshot.

So if by "new fresh snapshot" you mean "creating a snapshot of
root/subvolume at that time", then you can do it as often as you need.
But if by "new fresh snapshot" you mean something like full backup in
traditional tape backup, then like Calvin said every snapshot is
already independent, so in a way it's a "full backup".

Of course if you're using it for backup purposes then it's usually
best to have a copy elsewhere (not on the same
disk/server/datacenter), but that's beyond the scope of this list.

-- 
Fajar

  reply	other threads:[~2011-04-22 15:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21 17:17 How Snapshots Inter-relate? CACook
2011-04-21 18:47 ` Calvin Walton
2011-04-22 15:03   ` CACook
2011-04-22 15:30     ` Fajar A. Nugraha [this message]
2011-04-22 15:39   ` Helmut Hullen

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='BANLkTinkYrzO8xA4B32=xFDP7zmWJ-zaHQ@mail.gmail.com' \
    --to=list@fajar.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;
as well as URLs for NNTP newsgroup(s).