Abstract/Description

What happens when everything that could go wrong, does? At The Ohio State University Libraries, one of our mission critical systems failed, and we couldn’t repair or restore the database. Historically, our Infrastructure and Development departments have had a collaborative relationship, leading us aspirationally to label our teams DevOps. However, it wasn’t until we found ourselves in a difficult disaster recovery situation that we transformed our culture from a transaction-oriented exchange of services to a true partnership. While we wouldn’t wish such a disaster on anyone, we invite you to learn from our hard-won success in this presentation. Your take-away will include a list of practical steps you, as an IT manager, can take to make sure your DevOps team is ready before disaster strikes.

You must be a Subscriber to view this post and you are currently not logged in.

You can either log in below or sign up here.