-
-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can the config file be configured for use without subvolumes? #34
Comments
btrbk does not support recursive snapshots of btrfs filesystems, if that's what you are asking. You have to manually configure every btrfs subvolume to be backuped. btrbk has a Check the FAQ if your question was "Why is it not possible to backup '/' (btrfs root) ?". |
It seems that some distros, when choosing "root on btrfs", install the rootfs directly to btrfs root (i.e. subvolid=0), which I discourage to do. There might be a reason for this (apart from being the simplest approach), but in my opinion it makes things more complicated/confusing when it comes to snapshotting and backups. A simple and consistent setup may look like this: Sysadmin Guide. |
Thank you. On my setup, I am only using btrfs on a volume that is used for data. I have this volume mounted at /mnt/data which contains many files and directories. If I understand correctly, I must establish separate volumes for each subdirectory of /mnt/data and I can not take snapshots of the /mnt/data/. By the way, the link to the FAQs is broken. |
Closing this issue, as this is documented in FAQ, and we now have subvolume wildcard support in >=v0.23.0 |
I am trying to make snapshots of entire volume. Can the config file be configured for use without subvolumes? Commenting out the subvolume line leads to errors.
Thanks in advance
The text was updated successfully, but these errors were encountered: