Mark B

So if you install it on 2 boot drives redundantly will changes and all of the settings after install be made on both images and if one of those fail will Hex let you know? And if that redundant drive does die can you replace it? If you have a lot of data that if the boot drive dies becomes inaccessible because you had your boot die and can't replace with a new drive or transfer to a new system(yes I have had computers literally kill boot drive after boot drive before.) Aside from finding someone else, setting up buddy and then transitioning over to a new system(killing your and your buddies bandwidth during xfer) I don't see any local way you can make sure you have boot redundancy, the focus just seems on the data storage. Rightfully so due to mechanical drives in most instances but to have complete redundancy have the boot duplicate to a second drive so you could spin up in the case of multiple component failure. 2 different scenarios. 1. boot drive dies, what do now. If redundant, can I build a new machine to fully xfer old boot and storage locally to create new redundancy. Or can I unplug bad drive, plugin new drive and it creates a new redundant image 2. Power surge kills most of server, storage drives are older or smaller then what I wanted so instead of expanding I just want to migrate data(to include my boot drive settings.) plug NIC into NIC, "install hex" reach transfer server option that literally ports over files, settings and asks you if for instance your raid type changes if you want to change it. If my data is that important then a machine upgrade after an unknown failure that replicates is sometimes warranted. Starting on a blank server would take forever depending on how built out your files, pools, users etc are setup. Also if helping family not local you could build a replacement, transfer the server in 3 clicks and a Ethernet cable, send the "broken" server back and the family member has zero downtime. Think of it almost like the millions of variations when you get a new phone. iCloud is unfeasible with data amounts, and buddy requires you actually know someone else who has Hex(nice but hard to find someone reliable or just find someone else.) if Hex isn't able to do cloud backups of the boot image then functionality to do it locally(or even transfer to a new server) would be game changing.

Could I recommend a "maintenance mode"? Or a local transfer mode or even a "Transfer from old server" mode? Basically only hex to hex transfer to allow a NIC to NIC transfer basically expanding not only the pool but also the format of the pool. While keeping majority of settings and applications and storage. Not Buddy backup but a full transfer to a differently configured pool if that makes any sense, while keeping all of the shares. Also what happens if a boot drive dies? Snapshot and replication goes out the window, ability to create a boot backup would be clutch. Maybe I'm missing it on the forums and info pages and videos online but if boot drive dies completely how can a new boot drive do anything but wipe your data. (May just be a beta restriction)

So maybe a dumb question but say I upgrade server 1 and build a blank server 2. If both servers were off of the Internet on a LAN would I be able to transfer the data locally? Also another question that may be pertinent, on my local network if the Internet drops connection but my local network is still working will I still have access to my server? When uploading things can you do those locally to avoid latency?

Magnus, So one use license at a time I am assuming? I would assume that license would be transferrable to a new server in the case of failure am I correct?