From: Marc MERLIN <marc@merlins.org>
To: "Matthias G. Eckermann" <matthias.g.eckermann@t-online.de>
Cc: David Madden <dhm@mersenne.com>, linux-btrfs@vger.kernel.org
Subject: Re: OK to take hourly snapshots, then cull older ones?
Date: Mon, 4 Nov 2013 18:51:11 -0800 [thread overview]
Message-ID: <20131105025111.GG20447@merlins.org> (raw)
In-Reply-To: <20131103115024.GA5139@t-online.de>
On Sun, Nov 03, 2013 at 12:50:24PM +0100, Matthias G. Eckermann wrote:
> Hello David and all,
>
> On Mon, Oct 14, 2013 at 21:05 David Madden 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.
>
> This is implemented in "Snapper", see:
> http://snapper.io/
> It's by default delivered with openSUSE and SUSE Linux
> Enterprise, binaries are available for "everything else"
> as well.
Just curious, what does it do more than the 20 line shellscript I
posted?
http://marc.merlins.org/linux/scripts/btrfs_snaps
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2013-11-05 2:51 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
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 [this message]
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=20131105025111.GG20447@merlins.org \
--to=marc@merlins.org \
--cc=dhm@mersenne.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=matthias.g.eckermann@t-online.de \
/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).