Hey Everyone, tons of great questions on AetherStore here! We’ve been enjoying watching the thread keep expanding over the past few days and have clarified some important points below. Please let us know if there are any other questions, we’re happy to expand on anything you want to know more about.
Redundancy: 4x is the default but this is customizable. We price per usable (fully replicated) space, so if you believe you need increased availability, the pricing model rewards higher replication. AetherStore also proactively maintains your redundancy level. As machines go down it will recopy chunks to live nodes to maintain full replication. Also important: machines going offline does not cause data loss. If you need to read or write to the drive, yes - some machines need to be turned on.
As @scottalanmiller pointed out, AetherStore will not allow you to write to the drive if it cannot achieve full replication. In past versions a write could be completed locally even if not enough machines were online, assuming redundancy would be achieved when machines come back on. We’ve changed the way writes are completed in AS 2.0 to prioritize redundancy instead. So now, every time you’ve completed a write you know it’s been successfully written to (n) machines. In the future, we look forward to introducing write profiles, so you can select how you would prefer to write.
Speed: AetherStore is a robust, affordable and secure backup target that provides quick enough read times to serve its intended purpose well – reducing downtime, helping you meet RTO when the crunch is on. That said, if fast write speeds are your most important requirement AetherStore may not be the product for you right now. For every write, data is chunked, encrypted (twice) and stored across many machines. The same is true for the metadata, and there are environmental factors in every network to consider. These things take time. AetherStore’s complexity under the hood is what enables it to be a truly resilient, secure, flexible product.
Resource Consumption on Machines: @NetworkNerd: what @JaredBusch said - nothing noticeable. We run AetherStore constantly and have not observed effects on the machines nor has it been reported by users. We do have numbers on this, our QA engineer is currently updating them for the 2.0 release so I will send them through when I have them!
Mount Machine: What you guys are referring to as the “head node” here. You’re correct that AetherStore supports one mount machine at a time. You can change the mount machine after deploying a Store at any time using the dashboard. If the mount machine goes down, just use the Dashboard to select a new one. The mounted drive is locked and password protected. It can also be unmounted completely which provides a cool veiled mode for the drive. Data remains perfectly intact but the drive is invisible/inaccessible until remounted. As @scottalanmiller pointed out, you don’t need the mount machine to contribute a certain amount of storage. However, choosing a fast/good machine as the mount will definitely help performance!
Linux: we don’t support Linux in the current release but it’s far not off. I’ll keep you updated on it!
AetherStore 2.0 Release: we’re in the process of rolling this out now! If you gave us your info at MangoCon you will already be in one of the Early Release groups and should receive an email shortly.
Thanks again for all the great input!