Nymad and Alternative Networks will be running an event that will help address these and other issues associated with DR. For more details and to register – Click here.
Welcome to part 4 of our blog series. In blog one, we looked at defining a strategy, and refining an existing one. In blog two we reviewed how quickly a fit for purpose service can turn into silos that no longer deliver what is required for a business. And in blog three we looked at Public or Private Cloud, Insource or Outsource and what you need to understand in advance. In this blog we consider what’s required to make a start.
Realising your DR Strategy
Now you have considered the pros and cons of Public, Private and Hybrid Cloud and you have a clear idea of the value between internal and outsourced support, then it’s time to start planning requirements at a functional level.
How do we change to DRaaS? What could be the approach? Do we start with small and low impact or big and high impact? Making this decision successful is critical, so approach with full business visibility. Too many people in IT make decisions without engaging the business, more often than not they approach if from a technology perspective, which can have a negative impact.
There are lots of frameworks available to help you achieve this, but one that we find useful when working with our clients can be seen below.
The above diagram helps you to visualise 3 key attributes:
- Financial value of the service / application defined by bubble size
- Time to recover – where far right is immediate
- Recovery point – where uppermost is up to date recovery of fast changing data, through to lowermost that reflects static, rarely changing data
If you are able to create a similar model for your application estate you will have already defined both the business case and a prioritised plan for roll out.
The next step is to identify service partners to help you execute your strategy. Attending our event in February at the Tower of London will help!
Failing that, ensure you do your due diligence and understand the technical capability of your friendly, cost effective, cloud supplier. It’s very easy to dress up a shop window with non-disclosed delivery capability. This may be what you expect from a low risk commodity service, but maybe not from an enterprise class recovery service.
As a final point ALWAYS be aware of any licence liability that may come your way as a result of third party hosting. You may be liable for third party deployment decisions.
Join us for the final blog post where we deliberate living with DR as a Service and what you need to do.