Warm Disaster recovery on Google Cloud for applications running on-premises

Get Cooking in Cloud

Priyanka Vergadia
Nov 5, 2019 · 5 min read

Introduction

“Get Cooking in Cloud” is a blog and video series to help enterprises and developers build business solutions on Google Cloud. In this second miniseries I am covering Disaster Recovery on Google Cloud. Disasters can be pretty hard to deal with when you have an online presence. In this series of blogs, we will elaborate on how to deal with disasters like earthquakes, power outages, floods, fires etc. If you are interested in the prior mini series covered, checkout this.

Here is the plan for the series.

In this article, you will learn to set up a Warm DR pattern for your applications that are deployed on-premises. So, read on!

What you’ll learn

Prerequisites

Check out the video

Let’s learn Warm DR pattern with an example

In the last article we talked about Mane-street Art that runs their applications on-premises and are building a DR infrastructure on Google Cloud. And we saw how they would set up a Cold DR plan.

Mane-street Art’s situation has evolved since then, they now need to set up warm standby DR pattern to keep RTO and RPO values as small as possible without the effort and expense of a fully HA configuration. Which means, to support a disaster, they need some replication and redundancy built-in.

Note: If you are unfamiliar with the terms used here (RTO, RPO, DR Patterns) checkout the previous blog to get an overview.

In any DR pattern you need to understand what steps need to be taken before a disaster hits, what happens when a disaster hits and what needs to happen after the disaster has passed.

Warm DR Pattern — How does it work?

Steps to be taken before disaster hits

Warm DR, steps to be taken before disaster hits

Steps to be taken when disaster hits

Warm DR, Steps to be taken when disaster hits

Steps to be taken after the disaster has passed

Warm DR, Steps to be taken after the disaster has passed

When the production environment is running on-premises again and can support production workloads, Mane-street art has to reverse the steps that they followed during failover. Typically it goes something like this:

Conclusion

If you are running your application on premise, and need to keep the RTO and RPO values as small as possible without the expense of a fully HA configuration, then a Warm DR pattern is the way to go. We learned how to approach recovering the environment from failure in a Warm DR scenario. Stay tuned for upcoming articles, where you will learn to set up more DR patterns that make sense for your business.

Next steps

Google Cloud - Community

A collection of technical articles published or curated by Google Cloud Developer Advocates. The views expressed are those of the authors and don't necessarily reflect those of Google.

Priyanka Vergadia

Written by

Developer Advocate @Google, Artist & Traveler!

Google Cloud - Community

A collection of technical articles published or curated by Google Cloud Developer Advocates. The views expressed are those of the authors and don't necessarily reflect those of Google.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade