Change your surname to a domain that is available…
Of course I am kidding, but this kind of thing happens a lot, and it just ends up costing money to sort out. If you are happy with that then do it - if not then you will have to hope it becomes available on the free market at some time or see if it comes available in domain auctions as said. It really is that hit or miss, unless you are a Jones or Smith in which case there is zero chance
of course, but each to their own and all that. I just feel that parity on data is pretty much a free help to keep data secure. Not a magic bullet but a helping hand. And zfs does it very very well!
Not if you use raidz1, if you use raidz2 then yes. raidz in zfs is pretty decent. I have had a disk fail in raidz1 and replaced it with another and no data was lost after a resilver. Took a few hours but worked really well. Pretty much the whole idea of using zfs is the enhanced security of your data, seems strange to not put that to good use. The chances of BOTH drives failing before you can replace 1 are very very slim. I get that there is no easy way to just migrate to raidz1 but you could if you got 3 drives, make a new raidz1 pool, copy the data across and then add the old 2 drives to to the pool with a new vdev. You need to be able to add 5 drives to the system though. Of course there are many options here, but you already know that
If you add 2 more drives surely it would be better to use raidz1? I mean you’d add capacity AND get parity protection so if any 1 drive failed the data would still be safe. 4x4TB drives with raidz1 would give you around 14.5 TB of storage with added security
Cloudflare tunnels does exactly this…
You’d be better converting to ZFS or something else rather than just RAID (I’m assuming it is hardware raid) but I bet that has been mentioned a lot
Debian supports zfs so why the extra hassle of truenas? Seems to be a lot of extra work to add a vm when you could just use zfs in Debian. Or install something like Minio in Debian and use that to manage the data in s3 style buckets, again no vm needed