restic icon indicating copy to clipboard operation
restic copied to clipboard

exclude read-only filesystems

Open Framsfex opened this issue 2 years ago • 1 comments

Output of restic version

restic 0.15.1 compiled with go1.19.5 on linux/amd64

What should restic do differently? Which functionality do you think we should add?

Please add a new flag --ignore-read-only-file-systems for "restic backup" (or a better/shorter flag name if you find one)

What are you trying to do? What problem would this solve?

I have a lot of read-only file-systems on my servers, which do not need to be backed up, mainly NFS and btrfs or ZFS snapshots.

"restic backup --one-file-system" is too narrow, because it skips btrfs (rw) subvolumes.

Any user can create btrfs snapshots, so I (the admin) do not know them. I first have to scan all file systems to find read-only snapshots for "restic backup --exclude-file" And then I have a race condition.

Did restic help you today? Did it make you happy in any way?

restic is a great alternative to our main backup system IBM SP, which is HORRIBLE COMPLEX :-} The support of S3 (we have an own Netapp based instance) is a killer criterion!

Framsfex avatar Feb 14 '23 07:02 Framsfex

It would be also great to have a "PRUNEFS" configuration option like updatedb:

man updatedb.conf

PRUNEFS A whitespace-separated list of file system types (as used in /etc/mtab) which should not be scanned by updatedb(8).

Then one could easily exclude nfs, proc, tmpfs, ...

Framsfex avatar Feb 23 '23 17:02 Framsfex