If you've been through a real-world IT disaster, which parts of your disaster recovery plan were most effective? Any significant gaps you discovered that led to process revisions?

261 views3 Comments

Sort By:

Oldest

Vice President - Enterprise Platforms & Cybersecurity in Energy and Utilities13 days ago

We did have a breach right before we purchased CrowdStrike. We were down to our last good backup, as all our other backups had been overwritten or timed out. This was a huge wake-up call for us, highlighting the risks of having all our eggs in one basket.
As a result, we implemented new technology and moved to Rubrik for our backups. We now use cloud backups and have made them immutable. These adjustments were crucial because if you get down to your last good copy, you don't have anything to start with. Leveraging cloud storage and choosing different applications have been key improvements in our disaster recovery plan.

Worldwide Strategy & Portfolio, Cross Industry (Supply Chain, ESG, Engineering, Customer Experience, Intelligence Automation, ERP) in Manufacturing13 days ago

One effective strategy we've employed is conducting dry runs and setting up a standby hotline for status reporting. Simple communication tools like these are vital for coordinating next steps, especially when predecessor activities are involved.

Another key element is ensuring everyone understands their roles and responsibilities during a disaster. Practice dry runs help clarify who is responsible for what and when. Effective change management and clear communication lines are essential for a successful disaster recovery.

Please join or sign in to view more content.

By joining the Peer Community, you'll get:

Peer Discussions and Polls
One-Minute Insights
Connect with like-minded individuals

CIO in Healthcare and Biotech13 days ago

Five years ago, we experienced a catastrophic SAN failure and, in the same month, an EF4 tornado that took out power and internet in our area. The main lesson we learned was that we had not invested appropriately in disaster recovery infrastructure. This disaster forced us to reevaluate and significantly improve our DR plans.

The most effective part of our DR plan was identifying the inadequacies when faced with a real-world scenario. It's crucial to learn from other real-world scenarios as well. For instance, in healthcare, ransomware attacks are unfortunately common. While legal constraints often prevent public sharing of details, private conversations at conferences can provide valuable insights. These discussions can reveal new threat vectors and help improve your disaster recovery strategies.