@daftaupe @martin
Backups are Always needed of course. But it's a "last ressort solution" because when you restore you loose data... Maybe a day of work if you backup every night. So, be able to loose disks without any impact (notre even the need to umount the filesystem) is important.

@daftaupe
You said you have these magic send/receive #scripts, did you already #share them somewhere? Or could you #blog them maybe? 😬🙊
@hoper

@martin @hoper There's nothing magical :) it's basically having 2 btrfs partitionned drives, making a snapshot of a subvolume and sending that read-only snapshot from one to the other disk. That prevent us from the use a of a tool like rsync as there's an option to send only the increment when you already have subvolumes on the other drive. Based on : https://btrfs.wiki.kernel.org/index.php/Incremental_Backup

@daftaupe @martin
So... Just to be sure... Sending data to another drive on the same server is what you call a "backup" ? In this case, it's not only about tools that we disagree :)

@hoper @martin I did mention another disk or drive, it's up to you to think that it's in the same server.

@hoper obviously the (incremental) snapshot should be sent to a backup-machine... 🤓
sending it to another disk in the same server sound like poor-man's raid - and as we know, #btrfs has better raid options 💾

@martin
In m'y mind, a snapshot is not a clone. It's just a sort of "diff" of two devices. Something that you can't separate from it's source.
So I dont understand how you can have a filesystem somewhere, and a snapshot of it elsewhere that can be usefull. A copy, yes. Easy. But a snapshot ? Guess there is plenty of things I dont understand about btrfs.
Maybe the first reason for me to not like it :o)