Imagine a company with a disaster recovery plan that depends on cell phone coverage along the Kona-Kohala coast.
How is that possible?
Because the one person in the organization who knows how to bring back critical systems — his name is Eddie Ray — is vacationing in Hawaii on the mellow beach of Makalawena when disaster strikes.
The person who enables near-zero downtime is down himself — for a suntan.
Eddie’s company needs digital data to run its systems, launch its marketing campaigns, interact with customers, and maintain regulatory compliance.
But its business continuity ran aground in the golden sand of Makalawena. Disaster struck during his honeymoon.
Emergency calls to his cell phone generate “call failed” messages.
Bye bye data! Aloha!
Documenting the process of data recovery
Eddie’s employer could have avoided the emergency calls. The company had the good sense to create a virtual standby and the critical machines should have been back up and running in only a matter of minutes.
But it didn’t document the steps to be taken during a disaster recovery.
Here’s how it’s done:
- Make sure to document which machines are readily available for virtual standby.
- Specify what hypervisor the standby VM is located on and how to log in and power on that VM.
- Provide instructions regarding any IP or DNS changes that may be required. Use scripting to automate IP changes whenever possible
- Make note of any special modifications or tasks that need to be performed after the standby VM is up and running.
It is also extremely important to test your virtual standbys ahead of time to ensure that you are familiar with the process.
A frank self-assessment
It’s time for Eddie’s company to engage in some frank self-assessment and review its data protection strategy. Is it relying too much on the heroics of longtime employees like Eddie?
Running backup jobs is the easy part. Knowing exactly what to do in the event of an outage makes Eddie an IT hero. It’s all too human to depend on him.
Data protection and recovery is the classic triad of people, process, and technology and, despite the wonders of automation, many companies struggle to get it right. Downtime adds up to at least 1.6 hours per week at 59% of Fortune 500 companies (Dunn & Bradstreet).
Our tech brief will help you plan, document, implement and test your virtual standby so that you will have a bulletproof disaster recovery plan when disaster strikes.
No matter who is on their honeymoon.
Get It Here.