From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: using snapshot for backup: best practise?
Date: Thu, 26 Jun 2025 21:35:37 +0200 [thread overview]
Message-ID: <20250626193537.GA653726@tik.uni-stuttgart.de> (raw)
In-Reply-To: <f36e47c9-f135-473c-b1f1-2fedaef8aa10@cobb.uk.net>
On Thu 2025-06-26 (13:41), Graham Cobb wrote:
> I do various sorts of backups but the main one built around snapshots
> uses btrbk. It doesn't solve the problem you mention below but it does
> reduce the problem to listing each subvolume once in the config file
btrbk does some sort of snapshot rotation?
For this I have already a perfect solution:
https://fex.belwue.de/linuxtools/snaprotate.html
But snapshots are not a backup.
--
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: https://www.tik.uni-stuttgart.de/
REF:<f36e47c9-f135-473c-b1f1-2fedaef8aa10@cobb.uk.net>
next prev parent reply other threads:[~2025-06-26 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 11:43 using snapshot for backup: best practise? Ulli Horlacher
2025-06-26 12:41 ` Graham Cobb
2025-06-26 19:35 ` Ulli Horlacher [this message]
2025-06-29 22:50 ` Ulli Horlacher
2025-06-30 10:09 ` Mark Harmstone
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=20250626193537.GA653726@tik.uni-stuttgart.de \
--to=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