Re: restic backup with btrfs /

[Robert Krig <robert.krig@render-wahnsinn.de>]

Why don't you just create a backup script, where you create a list of 
subvolumes dynamically and then back those up, rather than hardcode 
specific subvolumes?

I would use btrfs tools to get a list of subvolumes and their paths, 
create snapshots and mount them in a similar directory tree and point 
restic at the snapshot and backup up from there.
Either that, or if you insist on use --one-file-system, backup up each 
subvolume snapshot individually.

Am 28.06.25 um 19:33 schrieb Ulli Horlacher:
> 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?
>