Written by Christoan Smit
29 May, 2019
Imagine you’re making a pie, and the recipe says you need 6 eggs. You happen to have a box with 6 eggs, but then you drop the box…
This is where Failover comes in.
Luckily for you, you have another box with 6 eggs – this means you can still make your pie. But what if you drop that box too? This is where owning a chicken comes in handy – except chickens lay 1 egg per day so you’ll have to wait 6 days for 6 new eggs before you can make your pie, and you really can’t wait that long. So, to be absolutely certain the pie gets baked, you’d want the following:
• 2 boxes with 6 eggs each, and
• 6 chickens to simultaneously lay 6 eggs so you can bake your pie even if you’ve dropped all the eggs you had in the boxes
So, in a network environment, imagine you have one physical server (the box) and it’s hosting 6 virtual servers (the eggs). This is exactly what we found during one of our site audits for a rather large company – just one old server wheezing away under the burden of 6 virtual servers, no failover. If that server dies, the entire company of 150+ people, would come to a grinding halt, no work – no pies.
Ideally, they should have:
• 2 identically-configured physical servers, one running as Active and one running as Standby, and
• An external Cloud solution where, even if both physical servers fail (e.g. power failure, flooding etc) the 6 virtual servers can quickly and easily be spinned up in the Cloud (6 chickens laying 6 eggs).
The moral of the story is this: The eggs come first. But, at the end of the day, it’s the virtual servers that do the real work – whether they are hosted onsite on your own physical servers (the box), or hosted in somebody else’s Cloud environment (the 6 chickens). You need those eggs, pardon, virtual servers, for your business to continue functioning.
Would you like to know if your backup services and Failover systems are fit for purpose and not going to crack?
Call us now to book a free onsite consultation* 0330 202 0220 or book online https://venomit.com/needs-analysis/
*Greater Manchester + 30 mile radius.