Sergey Nivens - Fotolia
Using a combination of public and private network elements -- a hybrid approach -- is a good way to achieve the best of both worlds. But how does that environment affect your disaster recovery architecture?
The proliferation of as a service technologies makes it possible to build a disaster recovery (DR) platform that satisfies your requirements. You may also use a private network infrastructure, a public cloud-based infrastructure or a combination of both: a hybrid network.
One of the reasons for using a cloud-based network infrastructure is that you can reduce your overhead by eliminating the need for data center space to house networking devices. You can acquire the amount and type of network bandwidth you need, for example, and lease it per month, or use another payment method. Moving infrastructure resources outside a traditional brick-and-mortar environment and into the cloud can provide excellent economies of scale.
If you decide to go with a hybrid disaster recovery approach, be sure you know your DR requirements, which IT assets are to be protected, and the recovery time and recovery point objective for each asset.
Next, decide how you will use public and private network assets for your disaster recovery architecture. It's not uncommon to start off slowly with new cloud-based network resources, implementing lower risk applications and systems using the cloud. Over time, and assuming cloud performance and security provisions are acceptable, you can consider migrating additional virtual machines, virtualized systems and other mission-critical assets to the cloud.
An organization can implement hybrid disaster recovery using locally based failover and failback systems, remotely hosted failover and failback systems, and newer disaster-recovery-as-a-service products. The selection of a specific network arrangement to support your disaster recovery architecture should be a joint decision between your IT organization and the network provider(s).
As you deploy the hybrid disaster recovery architecture, be sure to conduct acceptance testing and perform tests of the recovery capability to ensure it works as advertised.
Over time, you may wish to change the network services from private to public, or vice versa. Work closely with your network service providers and disaster recovery provider to ensure the DR platform can migrate to the other network infrastructure. Once a migration is completed, conduct one or more tests to ensure the disaster recovery architecture continues to perform correctly.
Finally, if the change to a different network infrastructure results in changes to procedures on your DR plans, be sure to update those procedures as soon as possible.
Make sure your data is safe when you use the cloud
Software-defined networking can help disaster recovery
Take a deep dive into cloud disaster recovery
Dig Deeper on Disaster recovery networking
Related Q&A from Paul Kirvan
Thinking of activating disaster recovery as a service? As you start this important process, consider these best practices that will help protect your... Continue Reading
As the remote workforce increases, network managers and users might opt to set up two concurrent VPN connections from the same remote device. But ... Continue Reading
It's time to review your strategy for ransomware backup and recovery. While there are standard ways to protect your organization, newer technologies ... Continue Reading