Re-Imagining the 3-2-1 Backup Rule for Cloud Native Applications Running on Kubernetes

US-CERT in its publication of Data Backup Options in 2012 recommended 3-2-1 backup rule. Have 3 copies of data, 2 copies on different media and 1 offsite. As simple as it seems, it applies to the applications running on kubernetes to protect against the node, disk failures, manual errors, natural disasters. In this presentation, we will present the storage architecture and various kubernetes building blocks to implement this practice. The details will include how to keep two copies of application data on two different disks (app replicated or CSI replicated storage). It will cover the intricacies and challenges of capturing the stateful app snapshot that includes kubernetes objects and persistent volume data to be able to transfer the backup copy to an offsite location. In the context of off-site copy, we will look into the storage architecture for using various cloud storage media including the object stores to enable use cases like disaster recovery, analytics and test and dev using cloud compute . It will be followed by a 3-2-1 rule demo of a complex distributed stateful app like mongodb/cassandra.

Learning Objectives

Present data protection and disaster recovery in the context of 3-2-1 copy file for cloud native applications on Kubernetes.,Discuss the challenges of data protection and backup for cloud native apps and propose solutions,Present storage architecture for enabling the data protection, backups using on-premise storage and cloud storage.