In part 1 we considered the importance of both knowing the details of your company’s network and in part 2 we discussed the need for keeping data backup onsite in case of an emergency, along with the acronym D2D2C and the 3-2-1 rule for maximum protection.
When it comes to system outages or downtime, unless you have widespread system automation, the biggest effect of system outage will obviously be on the end user. It’s therefore important to factor in user experience to any data recovery or backup plan. Keep track of general problems users are having, from latency to inadequate response time during normal usage, as these can be an indicator of problem areas and lead to bigger glitches down the line if left unaddressed.
Questions to consider:
- What are the most common end user computing problems we have?
- How frequently do they occur?
- What is the cost of leaving them unaddressed?
- At what layer of the computing network does this problem originate? (If you can’t address this final question, keeping accurate tally will help your service provider identify it properly)
The difference between a cloud hosting provider and a provider with a service layer is that, in the event of an outage, you may be on your own with traditional purchase models, or there will at least be a longer process of recovery. With a service provider, however, you usually receive access to updates, monitoring, and reporting. Stay in close contact with your service provider to address these issues before there’s a full-blown outage. The best plan for data recovery is to prevent an outage in the first place!
Aim for minimal disruption for the end user during the planning and design phases in data recovery. Avoid peak usage times just as you would with routine maintenance and updating. Cloud hosting services usually offer globalized access to mission critical applications across devices. A disruption in service throws employee workload rhythms off, reducing productivity and increasing employee frustration. A properly formulated strategy will allow the user access to alternative resources in a specified time, usually according to a specified service-level agreement. Make sure you keep an accurate tally of your end user computing problems to ensure your protection and help the recovery process, especially if you were unable to address the issue as it arose.
In part four we’ll discuss the importance of controlling cloud traffic.