When considering where to target your DR plan, InterVision has seen five primary drivers that dictate where companies ultimately place their DR:
1. Broader Cloud Strategy
For businesses that are going to cloud anyway due to long-term strategy, but haven’t yet or are slowly in the process of making this move, InterVision has seen many companies gain value from a DR environment in the cloud where IT teams can get their feet wet before moving critical workloads into a cloud production environment. Having an IT team with little cloud experience play around with copies of your data in a DR environment vs. data in use in a production environment is a lower risk. If this is your scenario, you probably already know what cloud your business wants, or what your business wants to do in the cloud. This cloud environment will be your failover target; you then figure out a low-cost option in that target for your team to learn the ropes.
If you have a cloud-first strategy but not much experience with cloud, most companies start with DR in the cloud first
2. Mixture of physical and virtualized IT systems
It’s common to have legacy physical systems that are critical to business operations. However, these older applications tend to hinder the rest of the business from moving fast into the future. Sometimes these legacy applications can’t be controlled or retired. For example, airlines must first check the no-fly list before taking off, a federal application that is separate from the airline’s internal systems. Don’t let a scenario like this hold you back from success. With a hosted infrastructure environment, you can provision a hybrid setup for failover operations in the cloud, even if you have a few or more applications still running on-premise. A hosted DR target tends to have the most flexibility in levels of features and capabilities to protect assets. Plus, a hybrid environment for DR usually can meet pricing on par with the cost of cloud.
If you have essential physical applications that must be virtualized, most companies explore a hosted solution with hybrid options
3. Preferred Service Level and Model
Customers have long dictated the sway of the market. Now, there’s a demand for personalized, fast service in an always-on model. Think about e-commerce, streaming and ride sharing apps. All have upended their relative industries and emphasize a continuous level of service. For this reason, companies are rethinking their approach to technology in order to better meet their customers’ desires. If handling DR in-house isn’t a core goal of your business, we’ve found that offloading this responsibility in full to a trusted third party gives an IT team the ability to drive the business forward. A third-party vendor should be able to cater to your needs in any failover target and handle all aspects of design, implementation, testing and maintenance. The question then becomes what level of recovery speed you need and the cost of achieving it.
If handling DR internally isn’t core to your business strategy, a trusted third party can own DR management on your behalf
4. Cost Components
Cost is always a factor in any business decision. If your business is unable to dedicate large sums to DR for the short-term and this is the most important decision criteria, it’s key to think about where you eventually want to go before simply selecting the cheapest option out there. Maybe you won’t be able to provision the best-of solution for DR right now, but you could find a solution for a reasonable price that’s adjacent to where you want to go and that would enable a smooth transition down the road. We’ve found that cloud tends to offer the most options for a tight budget, with the ability to move workloads easily as needed, but the best fit will ultimately depend upon your environment.
If cost is a concern, your environment will dictate the best options. Consult with a third party for an assessment
5. Failover and Failback Capabilities
There’s no point in sending your critical data to a DR environment during an emergency if you’ll never be able to get it back. A disaster event will never be fully resolved until workloads are back in their normal location again. If your business depends upon having normalcy again quickly, don’t just consider the path your data will take during a disaster; consider how and when you’ll send that data back to normal production. Some cloud environments, such as AWS, don’t allow failback easily. If having your data back in a timely fashion is important following a disaster, a hosted infrastructure might be a good option to consider.
If fast failback after a disaster is a priority, evaluate your target options with this as the key consideration