Feb 07, 2018

You’re facing an IT disaster, but it’s OK. You have a disaster recovery solution in place and can easily failover to it.

You sit back, heroic.

Then the support calls come in. Your branch office on the opposite coast is experiencing sweeping performance and latency problems. Now, you’re not just trying to get systems restored to your primary configuration, you have to get on the phone with your cloud provider to figure out what’s going on. By the time you’re off of hold and getting to the root of the problem, sales calls have been missed, marketing deadlines have passed, and thousands of dollars worth of productivity has been lost.

So much for heroics.

This may be a simplified example of how disasters can escalate, but it gets at an underlying and often neglected side of modern IT disaster recovery: Neglecting network performance, bandwidth, and stability can put organizations on the short path to chaos in the event of an emergency. What’s more, poor network performance, single points of failure, or inadequate data routing capabilities can become even more problematic as businesses rely on disaster recovery solutions that aren’t just about responding to an outage or similar event.

Disaster Recovery is Changing

The Forbes Technology Council reported that Disaster-Recovery-as-a-Service solutions give organizations an opportunity to branch out and use the technology for more than just responding to an outage. For example, the article noted that DRaaS can serve as an ideal counter to ransomware. Since disaster recovery solutions create secondary configurations in the cloud, companies hit by ransomware can simply cut the link between the primary and disaster recovery environment and switch over to their secondary or disaster recovery environment.  From there, businesses can keep going as if they weren’t attacked and gradually get the primary environment back on track. Developers and DevOps can test and utilize a secondary/disaster recovery environment before rolling out changes to the production environment.

Network Capabilities Are Essential for Disaster Recovery

While these secondary benefits of DRaaS, along with the primary uses for the service, are exciting, they are all reliant on the network. A few major issues to consider include:

  • Can the disaster recovery environment handle the data and provide service to all of your employees?
  • Will the sudden usage spike on the disaster recovery environment cause performance problem?
  • Does your disaster recovery provider offer network redundancy to ensure a connectivity issue doesn’t derail its function?

These questions represent major issues. Network World pointed out that traditional networks are often highly inflexible, preventing businesses from making easy changes and alterations. These kinds of problems only escalate when companies suddenly need to shift over to a secondary configuration. Switching to a disaster recovery environment can alter data pathways, straining different parts of your network.

In essence, you need a flexible, redundant, high-performance network capable of supporting a geographically diverse workforce in order to find success with modern disaster recovery solutions. This may sound intimidating, but the key is simple: Work with DRaaS providers that emphasize network performance and resiliency within their solution model. At Lume, we provide a global network of data centers, giving us a large, redundant, and high-performance network to deliver our disaster recovery solutions.

Leave a Comment