Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

Disaster recovery in a DevOps world

Jonathan Hassell | May 25, 2016
Organisations that are adopting DevOps methodologies are realizing actual benefits from taking that approach.

Questions to ask

As you begin thinking more about continuous disaster recovery, here are some points to consider with your team.

How do we “tabletop” our disaster recovery procedures? Who owns the checklist of procedures to follow? Who fires the scripts or is responsible for the automation? How can we simulate failure of a single application, an entire workload, and the infrastructure itself? What types of scenarios would cause failures in each of those key elements?

What natural employee strengths can I emphasize around disaster recovery? While DevOps tends to blend the roles of developers and operations folks, there will naturally be employees with stronger tendencies and experiences in operations who should be empowered to deal with the accountability that failover requires. On the development side, coders should be held accountable if their code is responsible for causing a failover event, and those coders who gravitate toward being superior debuggers might want to pick up some slack here.

How can I better utilize the disaster recovery sites and existing infrastructure I’ve already paid for? Is that environment set up for easy virtualization buildup and tear-down? And if it isn’t, what do I need to do to get to that ready state?

 

Previous Page  1  2  3 

Sign up for CIO Asia eNewsletters.