There is an organisational disconnect between the board and the IT department on disaster recovery.
We asked over 400 UK IT decision makers how their Recovery Time Objective (the length of time it takes to restore IT systems following a disaster) compared with the expectation of the board. Around a quarter (26 per cent) said their recovery times were slower than their board’s expectation, and a further quarter (24 per cent) didn’t know if they were meeting its requirement. The results reflect what we see in the real-world. There is a lack of agreement on recovery requirements for businesses.  
Organisations that do business continuity planning well have recovery objectives agreed and approved by the board. This is important because it sets the goals for business continuity and individual disaster recovery plans.  Without a consensus agreement, those recovery plans just aren’t working towards a common end.
When planning a business continuity plan, there is a question we must all address. How quickly do you need your IT system back after a disaster?  Ask the accounts team about billing systems or a sales team about its CRM and the answer is likely “ASAP”. It is possible for an IT team to deliver that kind of speed of recovery but it comes at a high cost.  
Beyond that initial, knee-jerk reaction, if you get teams to think about how they would be able to continue working, using alternative methods you start to get to a more realistic recovery need.  But ultimately the business continuity team needs to collate this information and weigh the costs and implications of downtime against the cost of recovery solutions.
Once the business sets these objectives, it’s then the responsibility of the IT department to deliver on them – to build the internal capability or to select a service provider to help

View Entire Article on