linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: David Madden <dhm@mersenne.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: OK to take hourly snapshots, then cull older ones?
Date: Tue, 15 Oct 2013 10:53:06 +0600	[thread overview]
Message-ID: <20131015105306.6a74ec5c@natsu> (raw)
In-Reply-To: <525CBF0D.1020609@mersenne.com>

[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]

On Mon, 14 Oct 2013 21:05:33 -0700
David Madden <dhm@mersenne.com> wrote:

> I'd like to use BTRFS to do something like the old NetApp snapshot
> system: every hour or so, there'd be a snapshot, then the 23 of the
> snapshots during a day would be deleted, leaving just a day snapshot,
> then after a month, 6 of 7 snapshots would be deleted, leaving just a
> week snapshot, and so on.
> 
> Is this a reasonable thing to do in a cron job with a BTRFS filesystem?
>  Apart from running out of space, are there any resources that might get
> used up?  Has anybody done this for a year or two in an active
> filesystem, and encountered success or weirdness?

Sure, that's one of the more awesome uses of btrfs.

But keep in mind that old snapshots on the same FS are not to be used instead
of a proper backup to external media/servers. If a block happened not to
change for a year, and it gets damaged on disk, it will become damaged in all
the snapshots all the way back to a year ago, and you lose that data.

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2013-10-15  4:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15  4:05 OK to take hourly snapshots, then cull older ones? David Madden
2013-10-15  4:43 ` Marc MERLIN
2013-10-15  4:47 ` Duncan
2013-10-15  4:53 ` Roman Mamedov [this message]
2013-10-15  5:05   ` David Madden
2013-10-15  5:14     ` Avi Miller
2013-11-03 11:50 ` Matthias G. Eckermann
2013-11-05  2:51   ` Marc MERLIN
2013-11-06  0:08     ` Matthias G. Eckermann

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=20131015105306.6a74ec5c@natsu \
    --to=rm@romanrm.net \
    --cc=dhm@mersenne.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;
as well as URLs for NNTP newsgroup(s).