linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: joshua@mailmag.net
To: "Ulli Horlacher" <framstag@rus.uni-stuttgart.de>,
	linux-btrfs@vger.kernel.org
Subject: Re: btrfs based backup?
Date: Tue, 12 Nov 2019 18:58:13 +0000	[thread overview]
Message-ID: <a862cfb2fc8feca06b510c7a8dfd1d2a@mailmag.net> (raw)
In-Reply-To: <20191112183425.GA1257@tik.uni-stuttgart.de>

I highly recommend something similar to snapper or btrbk (https://github.com/digint/btrbk) for the automation of snapshotting.

I've used snapper previously and currently use btrbk, and both allow you to set very customizable retention policies for snapshots.

Say you take snapshots every hour, you could configure something like:
- Keep Hourly snapshots for 24 hours.
- Keep Daily snapshots for 7 days.
- Keep Weekly snapshots for 4 weeks.
- Keep Monthly snapshots for 6 months.

Of course you can optimize what snapshots you keep based on your knowledge of the data, and balancing point-in-time recovery vs not having too many snapshots to make some btrfs operations slower.

btrbk is focused towards running it both on a source and a destination server to automate send & receive for backup purposes, but it can also simply manage snapshots on the local machine.


November 12, 2019 10:34 AM, "Ulli Horlacher" <framstag@rus.uni-stuttgart.de> wrote:

> I need a new backup system for some servers. Destination is a RAID, not
> tapes.
> 
> So far I have used a self written shell script. 25 years old, over 1000
> lines of (HORRIBLE) code, no longer maintenable :-}
> 
> All backup software I know is either too primitive (e.g. no versioning) or
> very complex and needs a long time to master it.
> 
> My new idea is:
> 
> Set up a backup server with btrfs storage (with compress mount option),
> the clients do their backup with rsync over nfs.
> 
> For versioning I make btrfs snapshots.
> 
> To have a secondary backup I will use btrfs send / receive,
> 
> Any comments on this? Or better suggestions?
> 
> The backup software must be open source!
> 
> -- 
> Ullrich Horlacher Server und Virtualisierung
> Rechenzentrum TIK 
> Universitaet Stuttgart E-Mail: horlacher@tik.uni-stuttgart.de
> Allmandring 30a Tel: ++49-711-68565868
> 70569 Stuttgart (Germany) WWW: http://www.tik.uni-stuttgart.de
> REF:<20191112183425.GA1257@tik.uni-stuttgart.de>

  reply	other threads:[~2019-11-12 19:03 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-12 18:34 btrfs based backup? Ulli Horlacher
2019-11-12 18:58 ` joshua [this message]
2019-11-12 19:09 ` Oliver Freyermuth
2019-11-12 19:14 ` Remi Gauvin
2019-11-12 20:05 ` Oliver Freyermuth
2019-11-20 16:36   ` freezes during snapshot creation/deletion -- to be expected? (Was: Re: btrfs based backup?) Christian Pernegger
2019-11-20 17:59     ` Oliver Freyermuth
2019-11-20 18:32     ` Chris Murphy
2019-11-21  1:51     ` Qu Wenruo
2019-11-21 16:44       ` Christian Pernegger
2019-11-21 19:37         ` Oliver Freyermuth
2019-11-21 20:30           ` Christian Pernegger
2019-11-21 21:34             ` Christian Pernegger
2019-11-21 22:39               ` Marc Joliet
2019-11-22  1:36                 ` Chris Murphy
2019-11-22 23:21                   ` Marc Joliet
2020-03-08 15:11                     ` Marc Joliet
2019-11-21 23:57             ` Oliver Freyermuth
2019-11-22 12:30               ` Christian Pernegger
2019-11-22 12:34                 ` Qu Wenruo
2019-11-22 14:43                   ` Christian Pernegger
2019-11-24  0:38                     ` Qu Wenruo
2019-11-24 19:09                       ` Christian Pernegger
2019-11-25  1:22                         ` Qu Wenruo
2019-11-21 22:22     ` Zygo Blaxell
2019-11-22  4:59       ` Zygo Blaxell
2019-11-22 14:36       ` Christian Pernegger
2019-11-23  3:49         ` Zygo Blaxell
2019-11-12 20:48 ` btrfs based backup? Michael
2019-11-13 15:04 ` Austin S. Hemmelgarn
2019-11-18 12:56 ` Ulli Horlacher

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=a862cfb2fc8feca06b510c7a8dfd1d2a@mailmag.net \
    --to=joshua@mailmag.net \
    --cc=framstag@rus.uni-stuttgart.de \
    --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).