Man of Honour
- Joined
- 30 Jun 2005
- Posts
- 9,515
- Location
- London Town!
Virtualisation done right is a fantastic solution and has been a boon for us, so much so we're now not doing it right (too many eggs in too few baskets ). unfortunately IMO to do virtualisation right for crazyswede I'd suggest almost doubling the budget
Still doesn't make it the solution to every problem. It's not the best solution for resiliency in all but a few very niche situations but that doesn't stop people thinking just copying the VM to a remote location and starting it up there is the best DR solution in the world. It's just not.
I'm seriously amazed about the ignorance to other potential solutions and blind belief in virtualisation that people have. Left alone for a few days our developers have started snapshotting database VMs and copying them to another site for DR purpose, they then fail completely to produce any good reason (any reason at all actually) for not choosing the simpler and better options of mirroring or even log shipping - I'm seriously curious how they managed to identify that as the best solution available...
how available are you expected to make the new solution?
What's the business' acceptable data loss in time of hardware failure (RPO)?
What's the business' acceptable outage in time of hardware failure in and out of business hours (RTO)? Does the hardware support added with time required to rebuild stuff cut it?
I very much doubt a business of that size is defining those values, more along the lines of 'it should break as little as possible'.