btrfs
or zfs
send/receive. Harder to do if already established, but by far the most elegant, especially with atomic snapshots to allow versioning without duplicate data.
btrfs
or zfs
send/receive. Harder to do if already established, but by far the most elegant, especially with atomic snapshots to allow versioning without duplicate data.
And enables modular workflows and flexiblity.
Backblaze reports HDD reliability data on their blog. Never rely on anecdata!
https://www.backblaze.com/blog/backblaze-drive-stats-for-q1-2024/
Ah, thank you for explaining. I understand where you’re coming from. Nevertheless, from the point of a view a small NAS, RAIDZ1 is much more space and cost efficient so I think there is room for “pets” in the small homelab or NAS.
Do one thing and do it well. Oh well…
I get that. But I think the quote refers to corporate infrastructure. In the case of a mail server, you would have automated backup servers that kick-in and you would simply pull the rack of the failed mail server.
Replacing drives based on SMART messages (pets) means you can do the replacement on your time and make sure you can do resilvering or whatever on your schedule. I think that is less burdensome than having a drive fail when you’re quite busy and being stressed about having the system is running in a degraded state until you have time to replace the drive.
I mean if it’s homelab, it’s ok to be pets. Not everything has to be commoditized for the whims of industry.
As far as I’m aware, Calibre-Web serves are web front-end for calibre. I think you might have to install plugins manually on the desktop version, but it should be active when importing a book over the Calibre-web, especially DeDRM.