Cost-optimized true zero recovery time objective for multiple applications using failure domains

Patent metadata

Field	Value
Publication number	US-11934283-B2
Application number	US-202016878231-A
Country	US
Kind code	B2
Filing date	May 19, 2020
Priority date	May 19, 2020
Publication date	Mar 19, 2024
Grant date	Mar 19, 2024

Abstract

Data protection operations including replication operations are disclosed. Virtual machines, applications, and/or application data are replicated according to at least one strategy. The replication strategy can improve performance of the recovery operation.

First claim

What is claimed is:

1. A method for replicating a applications operating on production virtual machines at a production site to a plurality of replica virtual machines at replica site, the method comprising:
identifying, by a data protection system, a plurality of applications operating at the production site;
assessing, by a the data protection system, the plurality of applications based on a replication strategy wherein the assessing includes:
for each application in the plurality of applications, determining one or more hypervisors, one or more datastores, and one or more internet protocol (IP) addresses associated with each application;
identifying failure domains for each application in the plurality of applications in accordance with the replication strategy, wherein the replication strategy ensures: (1) applications are assigned to a same failure domain if they are associated with one or more criteria, wherein the criteria includes having a same IP address, (2) applications in the same failure domain are replicated to different replica virtual machines, and (3) applications that are not assigned to the same failure domain are allowed to be replicated to a same replica virtual machine;
dividing the plurality of applications into two or more subsets of applications according to the replication strategy, wherein each subset of applications can be replicated to the same replica virtual machine; and
creating a single topology for the two or more subsets of applications suggesting a respective replica virtual machine in the plurality of replica virtual machines to which each subset of applications in the two or more subsets of applications should be replicated; and

replicating, by the data protection system, the plurality of applications from the production virtual machines at the production site to the replica virtual machines in the plurality of virtual machines according to the created single topology.

2. The method of claim 1 , wherein applications in the same failure domain are replicated to the different replica virtual machine.

3. The method of claim 1 , the failure domains include one or more of datastores and hypervisors.

4. The method of claim 1 , wherein some of the failure domain overlap with each other in terms of applications.

5. The method of claim 1 , further comprising dividing the applications into subsets of applications based on the assessment, wherein applications in the same subset have no common failure domain.

6. The method of claim 5 , further comprising replicating each subset to a different replica virtual machine.

7. The method of claim 5 , further comprising accounting for networking constraints, operating system constraints, license constraints, and/or hardware constraints when assessing the applications.

8. The method of claim 1 , wherein the replication strategy includes one or more of:
replicating applications or data of the applications associated with the same datastore to different replica virtual machines;
replicating applications whose associated operating system disks are associated from the same datastore to different replica virtual machines.

9. The method of claim 1 , further comprising determining which applications can share the same replica virtual machine.

10. A non-transitory storage medium having stored therein instructions that are executable by one or more hardware processors to perform operations for replicating applications operating on production virtual machines at a production site to a plurality of replica virtual machines at replica site, wherein the non-transitory storage is not a signal, the method comprising:
identifying, by a data protection system, a plurality of applications operating at the production site;
assessing, by a the data protection system, the plurality of applications based on a replication strategy, wherein the assessing includes:
for each application in the plurality of applications, determining one or more hypervisors, one or more datastores, and one or more internet protocol (IP) addresses associated with each application;
identifying failure domains for each application in the plurality of applications in accordance with the replication strategy, wherein the replication strategy ensures: (1) applications are assigned to a same failure domain if they are associated with one or more criteria, wherein the criteria includes having a same IP address, (2) applications in the same failure domain are replicated to different replica virtual machines, and (3) applications that are not assigned to the same failure domain are allowed to be replicated to a same replica virtual machine;
dividing the plurality of applications into two or more subsets of applications according to the replication strategy, wherein each subset of applications can be replicated to the same replica virtual machine; and
creating a single topology for the two or more subsets of applications suggesting a respective replica virtual machine in the plurality of replica virtual machines to which each subset of applications in the two or more subsets of applications should be replicated; and
replicating, by the data protection system, the plurality of applications from the production virtual machines at the production site to the replica virtual machines in the plurality of virtual machines according to the created single topology.

11. The non-transitory storage medium of claim 10 , wherein applications in the same failure domain are replicated to the different replica virtual machine.

12. The non-transitory storage medium of claim 10 , wherein the failure domains include one or more of datastores and hypervisors.

13. The non-transitory storage medium of claim 10 , wherein some of the failure domains overlap with each other in terms of applications.

14. The non-transitory storage medium of claim 10 , the operations further comprising dividing the applications into subsets of applications based on the assessment, wherein applications in the same subset have no common failure domain.

15. The non-transitory storage medium of claim 14 , the operations further comprising replicating each subset to a different replica virtual machine.

16. The non-transitory storage medium of claim 14 , the operations further comprising accounting for networking constraints, operating system constraints, license constraints, and/or hardware constraints when assessing the applications.

17. The non-transitory storage medium of claim 10 , wherein the replication strategy includes one or more operations of:
replicating applications or data of the applications associated with the same datastore to different replica virtual machines;
or
replicating applications whose associated operating system disks are associated from the same datastore to different replica virtual machines.

18. The non-transitory storage medium of claim 10 , the operations further comprising determining which applications can share the same replica virtual machine.

Assignees

• Emc Ip Holding Co Llc

Inventors

• Liu Bing
• Shemer Jehuda
• Wolfson Kfir
• Said Jawad

Classifications

• G06F11/301 Primary

  where the computing system is a virtual computing platform, e.g. logically partitioned systems (virtual machines G06F9/45533; logical partitioning of resources G06F9/5077) · CPC title

• G06F9/45558

  Hypervisor-specific management and integration aspects · CPC title

• G06F11/1484

  involving virtual machines · CPC title

• G06F11/3055

  Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available (error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction of the data by redundancy in operations G06F11/14; error detection or correction by redundancy in hardware G06F11/16) · CPC title

• G06F2009/45562

  Creating, deleting, cloning virtual machine instances · CPC title