It’s most useful for something like /home so you have a full backup of your home directories without having to worry if some app has dumped its settings on a folder you don’t have marked for backup. But also backing up / is useful because it gives you an easy recovery in the event of say disk failure. Just restore the entire system from a backup.
I use borg with borgmatic. I just back up / (which includes home) and exclude some folders I don’t want (like /mnt or /tmp).
It does the same as you just said.
I have 20 borg snapshots of my nearly full 1tb drive which takes about 400gb of space on my NAS.
I do it at the file structure level, not at the block device level as the article suggests. Why would I want to back it up at the block device level instead?
I don’t really understand the advantage of backing up the whole btrfs volume.
It’s most useful for something like /home so you have a full backup of your home directories without having to worry if some app has dumped its settings on a folder you don’t have marked for backup. But also backing up / is useful because it gives you an easy recovery in the event of say disk failure. Just restore the entire system from a backup.
I use borg with borgmatic. I just back up / (which includes home) and exclude some folders I don’t want (like /mnt or /tmp).
It does the same as you just said.
I have 20 borg snapshots of my nearly full 1tb drive which takes about 400gb of space on my NAS.
I do it at the file structure level, not at the block device level as the article suggests. Why would I want to back it up at the block device level instead?
With snapshots it costs nothing if the OS files don’t change much
You misunderstood my question, because what you said is true either way with borg.
The question is, what is the advantage of backing up the whole subvolume “block device” vs just / file structure.