public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: linux-btrfs@vger.kernel.org
Subject: restic backup with btrfs /
Date: Sat, 28 Jun 2025 19:33:08 +0200	[thread overview]
Message-ID: <20250628173308.GB847325@tik.uni-stuttgart.de> (raw)

restic (https://restic.net/) is a great backup tool but has some
limitations or design flaws: one is, it believes that any subvolume is on a
different filesystem. This means: "restic backup --one-file-system /" will
only backup the root subvolume, but no other subvolumes like /home
/var/spool etc... 

One has to add every subvolume to the argument list. Bad if you 
create new subvolumes and forget to update the backup cronjob.
When you later need to restore a file, there will be none...

My idea is now: I do not backup the original /, but do:

mount --bind / /backup/restic
restic backup /backup/restic
umount /backup/restic

Next evolution step: 
I could recursivly mount-bind other filesystems into /backup/restic/
For example:

mount --bind /local /backup/restic/local
mount --bind /data /backup/restic/ldata

That I would have a "all in one backup".

What do you think of this idea?

-- 
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:<20250628173308.GB847325@tik.uni-stuttgart.de>

             reply	other threads:[~2025-06-28 17:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-28 17:33 Ulli Horlacher [this message]
2025-06-30 10:07 ` restic backup with btrfs / Mark Harmstone
2025-06-30 13:41   ` Christoph Hellwig
2025-06-30 13:53     ` Mark Harmstone
2025-06-30 13:57       ` Christoph Hellwig
2025-06-30 17:30   ` Ulli Horlacher
2025-06-30 19:16     ` Ulli Horlacher
2025-07-03  8:00 ` Robert Krig
2025-07-04  9:39   ` Ulli Horlacher
2025-07-07 13:46 ` 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=20250628173308.GB847325@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