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

Get Cooking in Cloud

Priyanka Vergadia
Nov 3, 2019 · 6 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 the next few articles, 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 cold DR pattern for your applications that are deployed on-premises. So, read on!

What you’ll learn

Prerequisites

Check out the video

Cold Disaster Recovery on Google Cloud

Disaster Recovery (DR) for different Applications

Your DR plan would depend on your specific application and recovery goals. Let’s consider a few scenarios

E-commerce website

Let’s learn Cold DR pattern with an example

Mane-Street Art is a company that runs their applications on-premise and are building a DR infrastructure on Google Cloud. They are now working out a DR plan, with a low budget and are okay with a bit high RPO and RTO values. This means they need to set up a Cold DR pattern.

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

In cold DR pattern Mane-street art needs minimal resources in the DR Google Cloud project — just enough to enable the recovery scenario. When a disaster occurs, the failover strategy requires a mirror of the production environment to be started in Google Cloud.

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.

Cold DR Pattern — How does it work?

Steps to be taken before a disaster hits

Visual for “Steps to be taken before a disaster hits in a Cold DR pattern”

Steps to be taken when disaster hits

Visual for “Steps to be taken during a disaster in a Cold DR pattern”

Steps to be taken after the disaster has passed

Visual for “Steps to be taken after a disaster has passed, in a Cold DR pattern”

When the production environment is running on-premises again, and it can support production workloads, reverse the steps that you followed. Typically it goes something like this:

Conclusion

If you are running your application on premise, have a constrained budget, and can work with high RTO and RPO values, then a cold DR pattern is the way to go. You learned how to approach recovering the environment from failure in a Cold DR scenario. Stay tuned for upcoming articles, where you will learn to set up more DR patterns that makes 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.

More From Medium

More from Google Cloud - Community

More from Google Cloud - Community

PHP Functions on Cloud Run 🐘 🎉

More from Google Cloud - Community

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