3 ways to budget for cloud-based disaster recovery

November 11, 2013 by Diana Nolting

In our last webinar, Bluelock sought to tackle every IT professional’s least favorite topic: budgeting.

Budgeting is necessary in order to move all things business forward. Many IT professionals don’t enjoy it because it can rely on projections and intangibles that can’t be foreseen in the upcoming year.

In “How to budget for cloud-based disaster recovery,” we tackled an emerging technology that many are looking to evaluate for the coming year. New solutions can be the hardest to budget for because you may not be using the technology or be familiar with how it consumes costs or resources. Budgeting too little can result in poor vendor choices and budgeting too much can result in a “No,” from management.

Bluelock understands that this is a new territory for many individuals and outlined three different strategies that can be used on the journey to understanding new cloud-based recovery services.

Walk before you run

In this scenario a customer might not have a lot of cloud experience, or might not have a lot of DR experience. This is a situation where someone wants to actually try out the technology as a way to understand how it works, if it works, how much it costs and really get involved with understanding before moving full-speed ahead.

“Typically we see people using this approach by picking one single application,” explains Bluelock CTO Pat O’Day. “We’ll see people pick one important application that isn't currently protected from disaster, so any additional protection is an improvement.”

The customer can learn from their experiences with one application to help inform future decisions for more applications. 


Pick a set of applications

For customers that have classified their applications into tiers, or levels or protections, they may wish to start off by picking a set of applications to protect in the cloud.

“They will pick anything that is mission-critical and set a policy that all applications are protected in the cloud,” explains O’Day. “This is typically after they have already learned about cloud-based DR through one application, before they set a policy for a set of applications.”


Re-think everything

We have also met with companies that are under a lot of pressure to save costs. Or, their legacy DR implementation is so unreliable that they are comfortable throwing out the old ways and going entirely to the cloud.

“That may be too aggressive for many organizations,” explains O’Day. “But, we are seeing some companies moving that way for different reasons."

There is no one right path for all businesses, but these are three traditional paths that we’re seeing most from different companies and case studies.

To find out how to budget for each method, what your Recovery-as-a-Service costs are made up of and to hear case studies that align with each method, download the recording of the webinar here.