Earlier quoted context omitted.
So, just buy another and leave it as a hot (or cold) standby in a different data-center. Or use AWS as the DR site an spin it up only if the local HW fails. This sounds expensive if your talking one server and vs a year of AWS charges, but is a tiny bump if it turns out you need to buy a dozen servers to replace a large AWS bill. Plus, I think most people underestimate how reliable server grade hardware is. Most of i…
> Or use AWS as the DR site an spin it up only if the local HW fails. Yep. This seems like the obvious setup to me: 1) make the usual case as economical as possible (and ownership and the associated control will probably help here, unless you have to lease the expertise too) 2) outsource the exceptional case (ownership is less likely to matter here, and will matter for less time even if it does)
I worked with a large customer to help build this for them. OpenShift running on-prem, but they had some failover equipment that would ansible them an OpenShift cluster on aws. Depending on the nature of the failure it did take a little time to fail over, but 15 to 30 mins of downtime in the event of a catastrophic failure is often worth it to save hundreds of millions per year.