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

Get Cooking in Cloud

Priyanka Vergadia
Nov 12, 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.

  1. Disaster Recovery Overview

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

What you’ll learn

  • Hot DR pattern with an example

Prerequisites

  • Basic concepts and constructs of Google Cloud so you can recognize the names of the products.

Check out the video

Let’s learn Warm DR pattern with an example

In the last two articles we have talked about Mane-street Art that runs their applications on-premises and are building a DR infrastructure on Google Cloud. And we saw that they started with a Cold DR plan and moved to Warm standby due to a need for lower RTO and RPO values.

Now, Mane-street-art has become really popular and cannot afford to be down for even seconds. Since their requirement is to achieve a near-zero RTO and RPO values, the only way is by running HA architecture across their production environment and google cloud concurrently.

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.

Hot DR Pattern — How does it work?

Steps to be taken before disaster hits

Hot DR, Steps to be taken before disaster hits
  • Create a VPC network

With this hybrid approach, you need to use a DNS service that supports weighted routing to the two-production environments so that you can serve the same application from both.

Steps to be taken when disaster hits

Hot DR, Steps to be taken when disaster hits

In case of a failure on-premise, you just disable DNS routing to the on-premise web server and that’s it! In most cases DNS service supports health checks and will automatically route all the traffic to the healthy servers on Google Cloud.

Steps to be taken after the disaster has passed

Hot DR, Steps to be taken when disaster hits

When the production environment is running on-premises again and can support production workloads, Mane-street art has to do the following:

  • Resynchronize databases.

Conclusion

If you are running your application on premise and are looking to achieve very very small RTO and RPO values then hopefully you learned how to approach recovering the environment from failure using Google Cloud hot HA across the two environments. 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