Data backup and disaster recovery between environments

Patent metadata

Field	Value
Publication number	US-2020110675-A1
Application number	US-201816153480-A
Country	US
Kind code	A1
Filing date	Oct 5, 2018
Priority date	Oct 5, 2018
Publication date	Apr 9, 2020
Grant date	—

Abstract

A data management and storage (DMS) cluster of peer DMS nodes manages data backup and disaster recovery using a service level agreement. The backup data can be replicated from a primary compute infrastructure to the secondary compute infrastructure. For example, primary snapshots of virtual machines of the application in the primary compute infrastructure are generated, and provided to the secondary compute infrastructure. If the primary compute infrastructure is lost, the secondary compute infrastructure is initialized to replicate the primary compute infrastructure. Applications that were running in the primary compute infrastructure can failover to run in the secondary compute infrastructure. The replicated backup data is used to facilitate the migration. During a failover, the primary snapshots are deployed in the secondary compute infrastructure as virtual machines.

First claim

1 . A method for managing failing over an application between a primary compute infrastructure and a secondary compute infrastructure, comprising:
generating primary snapshots of one or more virtual machines in the primary compute infrastructure according to a first frequency in a first service level agreement, the one or more virtual machines together executing the application; replicating the primary snapshots to the secondary compute infrastructure in a form suitable for deployment as virtual machines in the secondary compute infrastructure according to the first frequency in the first service level agreement; in response to the first primary compute infrastructure becoming unavailable, initiating the failover from the primary compute infrastructure to the secondary compute infrastructure:
constructing a current state of the application using a snapshot before the failover, and
deploying the application in the current state by deploying a set of virtual machines on the secondary compute infrastructure, the set of virtual machines together executing the application; and
generating secondary snapshots of the set of virtual machines in the secondary compute infrastructure according to a second frequency in a second service level agreement.

2 . The method of claim 1 , wherein deploying the application in the current state comprises:
activating database servers corresponding to the application; activating file servers corresponding to the application; and activating web servers corresponding to the application.

3 . The method of claim 1 , wherein the virtual machines executing the application includes:
a database server for the application; a file server for the application; and a web server for the application.

4 . The method of claim 1 , wherein the secondary computing infrastructure includes a cloud computing infrastructure, and wherein the form suitable for deployment as virtual machines in the primary compute infrastructure is different from the form suitable for deployment as virtual machines in the secondary compute infrastructure.

5 . The method of claim 4 , wherein the form suitable for deployment as virtual machines in the primary compute infrastructure includes a native format for the primary compute infrastructure, and the form suitable for deployment as virtual machines in the secondary compute infrastructure includes a native format of the secondary compute infrastructure.

6 . The method of claim 4 , wherein the form suitable for deployment as virtual machines in the primary compute infrastructure includes a Virtual Machine Disk (VMDK) format and the form suitable for deployment as virtual machines in the secondary compute infrastructure includes an Amazon Machine Image (AMI) format.

7 . The method of claim 4 , further comprising converting the primary snapshots into the form suitable for deployment as virtual machines in the secondary compute infrastructure.

8 . The method of claim 1 , wherein a first data management and storage (DMS) cluster is coupled to the primary compute infrastructure to generate the primary snapshots and a second DMS cluster is coupled to the secondary compute infrastructure to generate the secondary snapshots.

9 . The method of claim 8 , wherein:
the first DMS cluster includes first peer DMS nodes and a first distributed data store implemented across the first peer DMS nodes; the first distributed data store stores the primary snapshots and provides the primary snapshots to the secondary compute infrastructure; the second DMS cluster includes second peer DMS nodes and a second distributed data store implemented across the second peer DMS nodes; and the second distributed data store stores the secondary snapshots and provides the secondary snapshots to the primary compute infrastructure.

10 . The method of claim 1 , further comprising:
replicating the secondary snapshots of the set of virtual machines in the secondary compute infrastructure in a form suitable for deployment as virtual machines in the primary compute infrastructure according to the second frequency; to initiate the failback from the secondary compute infrastructure to the primary compute infrastructure:
constructing a current state of the application by combining the primary snapshots generated before the failover and the secondary snapshots generated during the failover; and
deploying the application in the current state by deploying virtual machines on the primary compute infrastructure.

11 . The method of claim 10 , wherein failback is initiated responsive to resolution of a failure in the primary compute infrastructure that caused the failover.

12 . The method of claim 10 , further comprising receiving, by the primary compute infrastructure, the secondary snapshots from the secondary compute infrastructure, and combining, by the primary compute infrastructure, the primary and secondary snapshots.

13 . The method of claim 1 , wherein the secondary snapshots are generated in a native format of the secondary compute infrastructure, further comprising converting the secondary snapshots into the form suitable for deployment as virtual machines in the primary compute infrastructure.

14 . The method of claim 1 , wherein generating the primary snapshots of the virtual machines in the primary compute infrastructure includes:
associating the one or more virtual machines with the application; generating data fetch jobs for the virtual machines; determining whether each of the data fetch jobs for the virtual machines is ready for execution; and in response to determining that each of the data fetch jobs is ready for execution, executing the data fetch jobs by peer first data management and storage (DMS) nodes of a DMS cluster to generate the primary snapshots of the virtual machines.

15 . The method of claim 14 , further comprising, in response to determining that at least one of the data fetch jobs fails to be ready for execution, delaying execution of the data fetch jobs until each of the data fetch jobs is ready for execution.

16 . A system for failover and failback of an application between a primary compute infrastructure and a secondary compute infrastructure, comprising:
a data management and storage (DMS) cluster comprising peer DMS nodes that autonomously service the primary compute infrastructure, wherein each of the peer DMS nodes are configured to:
generate primary snapshots of one or more virtual machines in the primary compute infrastructure according to a first frequency in a first service level agreement, the one or more virtual machines together executing the application, and
replicate the primary snapshots to the secondary compute infrastructure in a form suitable for deployment as virtual machines in the secondary compute infrastructure according to the first frequency in the first service level agreement; and
the secondary compute infrastructure, configured to:
receive the primary snapshots; and
to initiate the failover from the primary compute infrastructure to the secondary compute infrastructure:
constructing a current state of the application using a snapshot before the failover, and
deploying the application in the current state by deploying a set of virtual machines on the secondary compute infrastructure, the set of virtual machines together executing the application; and

generate secondary snapshots of the set of virtual machines in the secondary compute infrastructure according to a second frequency in a second service level agreement.

17 . The system of claim 16 , wherein the form suitabl

Assignees

• Rubrik Inc

Inventors

• Wang Zhicong
• Meadowcroft Benjamin Travis
• Palit Biswaroop
• Vohra Hardik
• Malpani Mudit

Classifications

• H04L67/1034

  Reaction to server failures by a load balancer · CPC title

• H04L67/1095 Primary

  Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title

• H04L69/40

  for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06) · CPC title

• H04L67/34

  involving the movement of software or configuration parameters  (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title

• G06F11/1464

  for networked environments · CPC title