As an industry professional, you're eligible to receive a printed copy of the journal.

Fill out your address below.

Please reset your password to access the new
Reset my password
Welcome aboard, !
You're all set. We've send you an email confirmation to
just to confirm you're you.

Welcome to DRJ

Already registered user? Please login here

Existing Users Log In

Create new account
(it's completely free). Subscribe

Companies have an ever-increasing dependence on technology. A fact that is both exciting, but also worrisome. Secure access and robust, minute to minute performance from IT is an expectation, and a competitive necessity. Downtime is not an option, both operationally and economically, in support of providing a consistently seamless customer experience.

So, with cloud adoption booming, one of the key objectives of a transformation strategy is to become as close to 100% virtualized as possible and construct an active-active environment for as much of your IT estate as possible. After all, your peers are trending in that direction: managing hybrid workloads and selecting the right ‘as a service’ eco-partners are today’s IT fundamentals.

And, if we start to selectively outsource key services and virtualize our own IT estate, then we have solved the challenge of both being highly available and resilient in production, and that automatically solves our disaster recovery requirements!

This is an interesting perspective, however, before we construct an ‘ideal’ future state in more detail, let’s delve a little deeper into the current state. 

Having a resilient operational posture is becoming mandatory for a growing segment of companies across disparate verticals. Previously, it had been only banks, healthcare, and some utilities that would spend the dollars necessary to construct an active-active, failover capability for mission-critical workloads. 

Today, the pursuit of being highly available for operational resiliency has a false narrative that ‘recoverability’ is automatically built-in. Workloads can just failover and then failback, simply ‘Hit the button and we are done!’ Not only that, but we also have very effective SLA’s to boot. 

Not quite…

AWS, Google, Azure etc., have similar capabilities: Disparate regions and availability zones (infrastructure, security, storage, network), leveraging high-speed, low latency, secure networks. Workloads can be balanced so an Availability Zone (AZ) outage causes degradation, not hard down scenarios. And assuming the customer has architected auto-scaling and elastic load balancing capabilities to reinstate affected workloads, the recovery effort is automated. If the ability to auto-scale within the provider’s AZ configurations is not proactively architected, customers retain the responsibility to initiate runbook execution to recover workloads in the AZ’s.


Steve Piggott

Steve Piggott is the head of enterprise resilience, global account at Cutover. Piggott works within all facets of Cutover to drive market awareness, revenue growth, and to align with our customers’ requirements and expectations in receiving exceptional enterprise resiliency results. He brings a wealth of experience in driving successful customer outcomes across business transformation, operational resilience, disaster recovery, and business continuity program development

Tips to Making the Best Cloud Backup Decision
Organizations of all sizes increasingly turn to cloud providers such as Amazon, Microsoft, Google, and others. They utilize them to...
Often Overlooked, Clinical Data Registries Need Same Security and Privacy Protocols as EHRs
Do you know where all of your electronic health records reside? Do you know whether they are safe? In answering...
Career Spotlight – Nate Bridges
EDITOR’S NOTE: The DRJ Career Development Committee is supporting this series of articles featuring the career paths of industry professionals....
What COVID-19 Can Teach Us About Seasonality
COVID-19 is causing a larger shift in many businesses that typical high seasons such as Christmas. While we can learn...