Why Choose AetherStore Over a NAS?
-
@Dashrender said in Why Choose AetherStore Over a NAS?:
Well the head node I would assume isn't a PC, but instead a VM (as JB mentioned before) but maybe that's just crazy on our parts as well.
Well, normally that's not what is assumed but that's fine. If that's the case, then just assign that VM enough storage and you have nothing to worry about.
-
@Dashrender said in Why Choose AetherStore Over a NAS?:
Frequency - daily and sometimes randomly multiple times a day.
Daily? You made it sound like it was ever ten minutes around the clock. You think it would be rough to ask them to hold off on a daily reboot during a critical system restore?
-
@Dashrender said in Why Choose AetherStore Over a NAS?:
syncing backups only after hours.
ANd that's when they do the rebooting?
-
@scottalanmiller said in Why Choose AetherStore Over a NAS?:
@Dashrender said in Why Choose AetherStore Over a NAS?:
Frequency - daily and sometimes randomly multiple times a day.
Daily? You made it sound like it was ever ten minutes around the clock. You think it would be rough to ask them to hold off on a daily reboot during a critical system restore?
I'm sorry you read that into it. It's still daily or better. If the onsite NAS was offline during a backup window (taken hourly) that will cause the system to hang or loose a backup.
Now is that the end of the world, if only on is missed, probably not. And clearly, if we are in an outage situation, I can tell people to leave their machines alone so I can get max performance, etc..
-
In the situation of writing the backup you'd only worry about the head having enough capacity to ingest the backup and staggered uptime from some of the other nodes. So probably okay.
For restores, that's the only time I'd anticipate telling people to delay reboots because the server restore out ranks whatever their reboots are for.
-
Would be nice if AetherStore could lock the machines during an emergency.
-
It's weird to think you'd just run the main node from any ol' PC in the network.
Like JB, I added the service of the head node to a VM that had nearly zero storage on it. I don't want this stuff on my hypervisor storage, otherwise why would I be using AetherStore at all?
-
@Dashrender said in Why Choose AetherStore Over a NAS?:
It's weird to think you'd just run the main node from any ol' PC in the network.
Like JB, I added the service of the head node to a VM that had nearly zero storage on it. I don't want this stuff on my hypervisor storage, otherwise why would I be using AetherStore at all?
You probably wouldn't do that. Well, you could if that machine needed the storage.
I'd assume most people just use it as a mounted "network" drive for backup targets.
-
@BRRABill said in Why Choose AetherStore Over a NAS?:
@Dashrender said in Why Choose AetherStore Over a NAS?:
It's weird to think you'd just run the main node from any ol' PC in the network.
Like JB, I added the service of the head node to a VM that had nearly zero storage on it. I don't want this stuff on my hypervisor storage, otherwise why would I be using AetherStore at all?
You probably wouldn't do that. Well, you could if that machine needed the storage.
I'd assume most people just use it as a mounted "network" drive for backup targets.
I don't follow - I wouldn't do what? Install the head into a VM? You're saying you would only install the head node into a VM if the head node itself needed the storage? uh OK.. sure.
Question - how many head nodes can you have for an AetherStore array? if it's only one, would you really install it on a PC out in userland?
I suppose it's one thing for the NAS to be unavailable here and there when used as a backup location, but, we forget, this solution can also be used as traditional network storage as well. So if this is acting as a file repository for work files - does it go offline when the head node goes offline?
-
@Dashrender said in Why Choose AetherStore Over a NAS?:
@BRRABill said in Why Choose AetherStore Over a NAS?:
@Dashrender said in Why Choose AetherStore Over a NAS?:
It's weird to think you'd just run the main node from any ol' PC in the network.
Like JB, I added the service of the head node to a VM that had nearly zero storage on it. I don't want this stuff on my hypervisor storage, otherwise why would I be using AetherStore at all?
You probably wouldn't do that. Well, you could if that machine needed the storage.
I'd assume most people just use it as a mounted "network" drive for backup targets.
I don't follow - I wouldn't do what? Install the head into a VM? You're saying you would only install the head node into a VM if the head node itself needed the storage? uh OK.. sure.
Question - how many head nodes can you have for an AetherStore array? if it's only one, would you really install it on a PC out in userland?
I suppose it's one thing for the NAS to be unavailable here and there when used as a backup location, but, we forget, this solution can also be used as traditional network storage as well. So if this is acting as a file repository for work files - does it go offline when the head node goes offline?
Wouldn't just install it "on any 'ol PC"
-
@scottalanmiller said in Why Choose AetherStore Over a NAS?:
@Dashrender said in Why Choose AetherStore Over a NAS?:
Well the head node I would assume isn't a PC, but instead a VM (as JB mentioned before) but maybe that's just crazy on our parts as well.
Well, normally that's not what is assumed but that's fine. If that's the case, then just assign that VM enough storage and you have nothing to worry about.
Well, no, that is not what you assume. It is not what a lot of others assume and had issues with during the original beta. Stop skimming.
-
@Dashrender said in Why Choose AetherStore Over a NAS?:
Question - how many head nodes can you have for an AetherStore array? if it's only one, would you really install it on a PC out in userland?
One, and you are damned right, I do not want it in userland.
-
@scottalanmiller said in Why Choose AetherStore Over a NAS?:
In the situation of writing the backup you'd only worry about the head having enough capacity to ingest the backup and staggered uptime from some of the other nodes. So probably okay.
Why would the head need that kind of capacity?
Wouldn't it be immediately writing it out to the nodes?
Maybe a little cache, but nothing major.
-
@scottalanmiller said in Why Choose AetherStore Over a NAS?:
@Dashrender said in Why Choose AetherStore Over a NAS?:
Well the head node I would assume isn't a PC, but instead a VM (as JB mentioned before) but maybe that's just crazy on our parts as well.
Well, normally that's not what is assumed but that's fine. If that's the case, then just assign that VM enough storage and you have nothing to worry about.
When you say assign it storage ... you mean storage in the Aetherstore store, correct?
-
@BRRABill said in Why Choose AetherStore Over a NAS?:
@scottalanmiller said in Why Choose AetherStore Over a NAS?:
@Dashrender said in Why Choose AetherStore Over a NAS?:
Well the head node I would assume isn't a PC, but instead a VM (as JB mentioned before) but maybe that's just crazy on our parts as well.
Well, normally that's not what is assumed but that's fine. If that's the case, then just assign that VM enough storage and you have nothing to worry about.
When you say assign it storage ... you mean storage in the Aetherstore store, correct?
More importantly - why doesn't Scott assume that the head node would be on a VM? Where would he assume it's installed?
-
@JaredBusch said in Why Choose AetherStore Over a NAS?:
@Dashrender said in Why Choose AetherStore Over a NAS?:
Question - how many head nodes can you have for an AetherStore array? if it's only one, would you really install it on a PC out in userland?
One, and you are damned right, I do not want it in userland.
Yeah, just one. Being a PC is fine. But you don't want it to be someone's desktop unless that's its function. A bit use case of AetherStore is for individual users who need their own expanded storage.
-
@Dashrender said in Why Choose AetherStore Over a NAS?:
@BRRABill said in Why Choose AetherStore Over a NAS?:
@scottalanmiller said in Why Choose AetherStore Over a NAS?:
@Dashrender said in Why Choose AetherStore Over a NAS?:
Well the head node I would assume isn't a PC, but instead a VM (as JB mentioned before) but maybe that's just crazy on our parts as well.
Well, normally that's not what is assumed but that's fine. If that's the case, then just assign that VM enough storage and you have nothing to worry about.
When you say assign it storage ... you mean storage in the Aetherstore store, correct?
More importantly - why doesn't Scott assume that the head node would be on a VM? Where would he assume it's installed?
Directly on whatever the backup head is if you are doing backups. Or directly where you will consider the data in most cases.
-
@BRRABill said in Why Choose AetherStore Over a NAS?:
@scottalanmiller said in Why Choose AetherStore Over a NAS?:
@Dashrender said in Why Choose AetherStore Over a NAS?:
Well the head node I would assume isn't a PC, but instead a VM (as JB mentioned before) but maybe that's just crazy on our parts as well.
Well, normally that's not what is assumed but that's fine. If that's the case, then just assign that VM enough storage and you have nothing to worry about.
When you say assign it storage ... you mean storage in the Aetherstore store, correct?
No, storage to the VM.
-
@scottalanmiller said
When you say assign it storage ... you mean storage in the Aetherstore store, correct?
No, storage to the VM.
But not a requirement. No reason you couldn't install the Aetherstore core (to use to store data) on 10 machines, and the head on a VM with NO storage dedicated to it, right?
-
@BRRABill said in Why Choose AetherStore Over a NAS?:
@scottalanmiller said
When you say assign it storage ... you mean storage in the Aetherstore store, correct?
No, storage to the VM.
But not a requirement. No reason you couldn't install the Aetherstore core (to use to store data) on 10 machines, and the head on a VM with NO storage dedicated to it, right?
Correct. The use of local storage on the head is purely for performance considerations.
