With the cost of downtime estimated at $336,000 per hour*, the question “How would you rate your ability to execute a recovery following a disaster or business interruption?” can easily be a company’s “Million Dollar Question.” In fact, it can become a “Multi-Million Dollar Question” if your disaster recovery capabilities aren’t up to par. Given the stakes, the decision of whether to handle recovery internally – the DIY or “Do It Yourself” approach – or to contract with a Disaster Recovery as a Service (DRaaS) provider is of paramount importance.
Here are some questions to consider as you decide which route to take: DIY disaster recovery or disaster recovery as a service?
What is the Total Cost of Ownership (TCO)?
Whether you’re talking about remodelling a kitchen or recovering from a disaster, people typically make the assumption that “it’s cheaper if I do it myself.” But is it?
The (often unanticipated) costs involved in establishing and maintaining a DIY disaster recovery program are almost endless: hardware expenses, technology licenses, refreshes, system management, testing and exercises, upgrades and patches … the list goes on and on. Companies taking a DIY-route can end up adding to their total costs, rather than saving on the bottom line.
In contrast, a DRaaS environment rolls up all these costs into a single operational expense (opex) pricing structure. There is nothing hidden and nothing unanticipated. Costs are predictive and inclusive.
Will you create comprehensive documentation?
In a DIY disaster recovery scenario, documentation is one of the first things to go out the window. It’s easy for internal IT staff to say, “We know how to do that – we don’t need to write down the procedures.” But at time of crisis, you might find out (to your dismay) that the people who know how to perform certain tasks are unavailable. They may even have left the company.