So HA it is
-
Key steps to HA involve redundant generators, good fuel supply plan, high availability and very intensive HVAC solutions, that kind of stuff. Your plant is 10 fold as important as your gear.
-
@DustinB3403 said:
I haven't looked into any providers, but have considered it. I doubt that we're willing to invest into another server, plus racking cost. I can look into it, do you have any recommendations?
No, sorry we don't have many collocation facilities around here (without driving 3-5 hours). This is something that would be local to you.
I think the long term cost of a server and rackspace would be less then storing 24TB in the cloud (I'm not saying you will do that) you will need to do some cost analysis to see what is the better idea.
You also need to remember the time it takes to retrieve data from the internet. "Never underestimate the bandwidth of a station wagon full of tapes hurtling down the highway."
-
@coliver Yes, thank you for the reminder.
-
@coliver said:
You also need to remember the time it takes to retrieve data from the internet. "Never underestimate the bandwidth of a station wagon full of tapes hurtling down the highway."
If it was really important you could get ethernet to the colo and have your internet go out of the colo instead.
-
What's your bandwidth? Moving your entire infrastructure to an enterprise collocation site would probably be less expensive then building out a new server room with HVAC, generators, etc. @scottalanmiller beat me to it.
-
@coliver said:
What's your bandwidth? Moving your entire infrastructure to an enterprise collocation site would probably be less expensive then building out a new server room with HVAC, generators, etc. @scottalanmiller beat me to it.
Scott may have said something, but your suggestion puts it in black and white. If you're boss isn't willing to put this in a DC, it's probably not worth spending the money on HA.
-
I like the potentional not use a backup to get it offsite. I have not done the replication myself, but know another group that has. very little data replicating in each change.
They brought in the server locally, seeded the initial replicas, moved it to the colocation facility, and then let it catch back up.
-
@JaredBusch said:
I like the potentional not use a backup to get it offsite. I have not done the replication myself, but know another group that has. very little data replicating in each change.
They brought in the server locally, seeded the initial replicas, moved it to the colocation facility, and then let it catch back up.
I've never done replication over a high latency wire. Not sure how it would work.
-
@DustinB3403 said:
The next is the choice of storage, consumer or enterprise grade SSD's. Having a much lower weekly delta change for our shares than the daily delta for the consumer grade SSDs (which the write delta mark for the consumer grade SSD's is 20GB per day), so we have to ask: "Are enterprise drives really worth over double the cost of each SSD?"
Depends if they are part of the server support package or not, and if they will work with your controller or not. Often enterprise SSDs have special firmware to go with your hardware controller. The decision is holistic, not separated out to just consumer vs. enterprise.
-
@JaredBusch said:
I like the potentional not use a backup to get it offsite. I have not done the replication myself, but know another group that has. very little data replicating in each change.
They brought in the server locally, seeded the initial replicas, moved it to the colocation facility, and then let it catch back up.
We replicate ours every 5-10min depending on the server. So we see little traffic from this.. Most of the time.
-
@Dashrender said:
Scott may have said something, but your suggestion puts it in black and white. If you're boss isn't willing to put this in a DC, it's probably not worth spending the money on HA.
Or another way.... if your boss refuses to do HA, you can't do HA even if he requests HA
-
@coliver said:
@JaredBusch said:
I like the potentional not use a backup to get it offsite. I have not done the replication myself, but know another group that has. very little data replicating in each change.
They brought in the server locally, seeded the initial replicas, moved it to the colocation facility, and then let it catch back up.
I've never done replication over a high latency wire. Not sure how it would work.
Latency does not affect replication. That is the benefit of it.
-
@JaredBusch said:
@coliver said:
@JaredBusch said:
I like the potentional not use a backup to get it offsite. I have not done the replication myself, but know another group that has. very little data replicating in each change.
They brought in the server locally, seeded the initial replicas, moved it to the colocation facility, and then let it catch back up.
I've never done replication over a high latency wire. Not sure how it would work.
Latency does not affect replication. That is the benefit of it.
Good to know.
-
@coliver said:
I've never done replication over a high latency wire. Not sure how it would work.
If it is async, hardly affects it at all. As long as you are replicating in the "minutes" range and not in the "seconds" range. High latency wire is normally no more than 300ms and 2,000ms tops.
Full Sync is super latency sensitive because every write has to be confirmed before anything continues.
-
@coliver said:
Good to know.
It is basically just like transaction logging in SQL server. It writes the changes to a log file and then ships the log file. There is not a concern for latency. Obviously, you need to still have enough bandwidth for these changes. or you will always be getting farther behind, but because it is replicating, there is never a problem like a new full backup.
-
Another point I made is that if we really need HA between the host that we could simply increase our existing XenServer (which also answers several of the above questions) to support these future Virtual Servers and configure a single new Dell R720xd for fail over between the two.
This idea was declined with "I'd rather leave that server for development VM's"
So there is still some critical things that still need to be thought out.
-
@DustinB3403 said:
The next choice that must be made is what hypervisor are we going to use. XenServer or Hyper-V or lastly ESXi. As deciding this really refines our backup choices.
KVM would come in long before ESXi. ESXi would be like installing OpenVMS today. Just makes no sense on a new install. Costly and without benefits. Your budget doesn't allow it anyway.
-
Dustin, what does your company do?
-
@DustinB3403 said:
Specifically to try and find some pricing for Windstream, Amazon and BackBlaze as the top 3 contenders.
Windstream? Seriously? Why not just set the data on fire? That's not a business class company. They are infamous scammers and can't support their own links. Never do business with them, ever. They are so bad that they had to change their name to hide their bad reputation. As they are based around the corner from you, I'm shocked that anyone there would even allow their name to come up.
-
@DustinB3403 said:
Another point I made is that if we really need HA between the host that we could simply increase our existing XenServer (which also answers several of the above questions) to support these future Virtual Servers and configure a single new Dell R720xd for fail over between the two.
This idea was declined with "I'd rather leave that server for development VM's"
So there is still some critical things that still need to be thought out.
Ask him why he wants a newer server for development stuff. You usually put your old crap for your labs.
