IP Library Granted Patent US 11,934,283
Granted Patent B2
US 11,934,283 · App. 16/878,231 · Granted Mar 19, 2024

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

Inventors: Bing Liu (Tianjin, CN); Jehuda Shemer (Kfar Saba, IL); Kfir Wolfson (Beer Sheva, IL); Jawad Said (Kfar Yasif, IL)
Assignee: EMC IP HOLDING COMPANY LLC
G06F11/301G06F9/45558G06F11/1484G06F11/3055G06F2009/45562G06F2009/4557G06F2009/45591G06F2009/45595
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,934,283
App. No.
16/878,231
Granted
Mar 19, 2024
Kind
B2
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.

Claims (37)

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.

Assignments (9)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053574/0221) Recorded Jun 10, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
Reel/Frame 060333/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053578/0183) Recorded Jun 10, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
Reel/Frame 060332/0864 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053573/0535) Recorded Jun 10, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
Reel/Frame 060333/0106 →
RELEASE OF SECURITY INTEREST AT REEL 053531 FRAME 0108 Recorded Nov 2, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
Reel/Frame 058001/0371 →
SECURITY INTEREST Recorded Aug 21, 2020
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 053578/0183 →
SECURITY INTEREST Recorded Aug 21, 2020
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 053573/0535 →
SECURITY INTEREST Recorded Aug 21, 2020
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 053574/0221 →
SECURITY AGREEMENT Recorded Aug 18, 2020
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 053531/0108 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 19, 2020
From: LIU, BING; SHEMER, JEHUDA; WOLFSON, KFIR; SAID, JAWAD
To: EMC IP HOLDING COMPANY LLC
Reel/Frame 052703/0587 →
Continuity (1)
Related Publication 20210365340A1 · Nov 25, 2021