(Virtual) Disaster Recovery

As virtualization takes the IT world by storm, the disaster recovery (DR) plans are only just beginning to catch up. The problem is this… you have a server and it runs an application. Traditional DR looks at the server and says ‘we need another one of those’ - so this is a little simplistic, but in essence its true, and more to the point, it works. Now lets bring in virtualization, one machine is no longer one machine it is multiple machines. Each could well be at different patch levels and so it is not just a case of duplicating the hardware but ensuring that the virtual environments are also up to date.

Results from a recent survey has said that 55% of people are revisiting their DR plans because of virtualization - which is good. BUT… it also highlighted that only 37% of respondents back up their virtual systems! Before virtualization that would be seen as a travesty and an accident (or disaster) waiting to happen, so why is this the case now? Lack of tools is the basic problem. But if you haven’t got the tools why go with the technology. There are the tools out there, including those to backup virtual systems - its time to look at the risks and avoid the hype. Virtualization offers great benefits, but treat it with the respect it deserves or it will come back to bite you.

Time To Check Your DR/BC Plans?

The UK had some unexpected power outages yesterday and it no doubt caught a few companies off guard. One hospital had to cancel operations as the backup power generator failed. We take power for granted, you switch on a light and it works - but this shows that we shouldn’t. While it was a ‘freak event’ that caused it, this is what usually causes ‘disasters’.

Disaster Recovery / Business Continuity (DR/BC) plans are only any good if they are regularly tested. You don’t need to carry out complete tests every week, but there should be a schedule for partial and complete testing. Power outages are probably the most likely cause of a disaster (although last year it was flooding), so regular testing of emergency generators need to happen. If generators are fired up then they do use fuel, so make sure that it is replaced (unlike one company who didn’t do this and so they stopped after 15 minutes). Regular testing of critical application fail-over also needs to happen. Application dependencies are increasingly complicated, so failing over to a disaster recovery sight becomes more complex. Service Oriented Architectures (SOA) add further to the complexity providing functionality that you may not be in control of - DR plans need to take these into account as well. What if your 3rd party mapping service goes down - what will replace it?

In the US they have rolling brownouts (scheduled blackouts) in South Africa there are regular blackouts (2-3 a week), this keeps the IT department and the DR/BC teams on their feet. We are lucky to have a better power supply, but it isn’t perfect - so check your contingency plans today.