by Shane Sheppard
The technology involved in protecting a virtual environment from disaster is constantly evolving. I was reminded of this fact as we were recently conducting a proof of concept exercise for one of our clients. They are bringing a new application online in Europe and had specific requirements around GDPR that required in-region failover along with data localization considerations.
It wasn’t too long ago that a solution for these requirements would have included expensive infrastructure and additional resource requirements. That paradigm has been radically altered with solutions like Zerto. In the span of two weeks, we executed a proof of concept test plan replicating and ultimately failing this application workload into Azure. Not only did the solution meet the client’s requirements around GDPR and data localization, but it also allowed iVision to use the same processes and runbook that we have in place for their U.S. based data center.
Today’s disaster recovery solutions are incredibly flexible and offer us the capability to replicate our customer’s workloads to iVision Cloud’s IaaS infrastructure or a growing number of Public Cloud providers, such as Azure or AWS. With the One-To-Many replication capabilities available in Zerto, the possibilities are even more dramatic. Imagine a solution where your critical applications can be replicated to multiple Disaster Recovery sites simultaneously, all with a Recovery Point Objective in seconds, not hours or days. Combined with Zerto’s 30-day journaling capabilities and application level protection, we can now failover an application to one of thousands of point-in-time checkpoints to a location of your choice. This gives our customers the capability to recover from a malware attack or critical application failure with impressive Recovery Time Objectives.
As you evaluate your disaster recovery solution, it is important to understand how this tremendous flexibility not only helps you meet your business requirements but can also lead you to change them. Some examples of these changes may include:
Incorporating application level failover into Disaster Recovery planning and understanding which applications can be failed over into a Public Cloud or IaaS partner
Identifying network requirements for application-level failover, which may include application-level subnetting and specific virtual protection groups
Evaluating Recovery Point Objectives at a more granular level including considerations such as failover locations
Identifying any data localization or regulatory concerns which may impact failover locations and options
Identifying how security incidents may impact your Disaster Recovery plan, failover locations, and RTO/RPO
It is more important than ever to choose a partner with proven processes, technical expertise and an ability to support your applications in a Public Cloud and/or IaaS platform. It is critical to take advantage of the disaster recovery features available to you today without getting lost in the array of options available. iVision can help you navigate these options and take your Disaster Recovery solution to the next level.