Leaderboard

OMG, I totally see the confusion now. I have edited that post and reworded it to be more clear. TrueNAS has no built-in means to do backups as part of their OS unless you consider rsync cron jobs/replication tasks as "backup". They don't facilitate the connection between servers or even setup the SSH permissions for you (you have to do all of that yourself). This is where our solution takes things a step further. We intend to make the experience much simpler. First you "friend" someone else that is a HexOS user (if you're doing the "buddy" approach). Then you will grant that user "permission" to backup to your system (and set a quota). Then they accept the request and authorize the backup in return (if you're doing that). Then we do the rest (establishing a secure VPN tunnel between systems, creating appropriate SSH users and handling the key exchange, etc.). You'll definitely be able to leverage the buddy backup system between two systems licensed under the same account. That would be silly of us to prohibit or unnecessarily complicate. I get the confusion. Buddy backup is just the marquee feature name for our backup solution between two servers. Every server needs a license. So if you and a buddy want to backup, you both have to have your own licenses under your own accounts. If you have two licenses for two systems under 1 account, you can use the same "buddy backup" system to handle that job as well. Apologies for muddying the water on my initial response. I can see how that had some folks confused, but I hope this clarifies.

Forgive me, but I'm really confused by what you're saying, which means there is clearly a disconnect in our marketing language and understanding with customers as well and I want to get to the bottom of that. Let's try some clarification here: Buddy backup is a feature that will allow two HexOS users (customers) to backup to each other's server in an encrypted fashion. There is no reason you cannot be your own buddy with a second license (e.g. you buy a second server license and put a server at a secondary location). If someone bought two licenses during black friday under two separate accounts, each account can backup to each other just the same (and if they want to merge those two accounts, we can handle that for the user). With this sale, however, we are not allowing someone to buy a second license to transfer to another user (as it would open the door to reselling licenses which we don't support). I get that the term "buddy backup" may not clearly identify that you can be your own buddy, but we thought it would be fairly obvious that if you could backup to someone else on a separate account, you could also backup to yourself on the same account. I think we could loosen the "encryption" requirement in the case of backups between two servers owned by the same account, but that's more of a technical detail than marketing. Let me know what's still unclear or how we can do better on the language here. Sometimes we can be a little too close to the trees to see the forest, so if you can help give us a better perspective, we'll work to improve our messaging in the marketing. Thanks!

Hello all! We are excited to announce HexOS Local, powering the new local UI/UX for HexOS and capable of so much more. Read more about it on the Blogpost - Introducing HexOS Local

Amazing news. I just hope adding HexOS Local will be seamless and won't require a fresh install/rebuild!

Just here to say - you guys are awesome and thanks for keeping your promises! I'm perfectly fine with deck and enjoy being able to pull up the stats quickly anywhere I am, but local hosting is so important to this community, so thank you.

This would require the app data folders themselves to be encrypted. Not impossible to do, but may not be with the first iteration of buddy backup. Definitely something we could consider!

Buddy backup will definitely work with two licenses under the same account. You will be your own buddy 😉

I would like to see an option of an one click full disk encryption at system setup (or disk/pool or per application setup). Then it should work like in the TrueNAS interface with a warning ⚠️ about the possibility to lose all data if the corresponding password/key is not stored properly and so on... It would be preferable to encrypt all the folders below automatically too, since the title “Full disk encryption ...".