IP Library Granted Patent US 11,763,017
Granted Patent B2
US 11,763,017 · App. 17/160,323 · Granted Sep 19, 2023

Method and system for proactive data protection of virtual machines

Inventors: Gururaj Kulkarni (Bangalore, IN); Anand Reddy (Bangalore, IN)
Assignee: EMC IP Holding Company LLC
G06F21/6218G06F9/45558G06F21/64G06F2009/45587G06F2009/45591
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,763,017
App. No.
17/160,323
Granted
Sep 19, 2023
Kind
B2
Abstract

A system for managing data protection of virtual machines (VMs) hosted by hosts of data clusters includes a data protection manager. The data protection manager identifies a data protection event associated with at least one VM, obtains, in response the data protection event, data protection rules and a protection policy associated with the at least one VM, spawn, by a monitoring engine orchestrator, a monitoring engine to the data cluster, initiates performance of the data protection services for the at least one VM using a first storage of storages, obtains, after the spawning, monitoring information from the monitoring engine, makes a determination that a data protection rule event of the data protection rule events occurred using the monitoring information, and in response to the determination, initiates the performance of a corrective action of corrective actions based on the data protection rules using a second storage of the storages.

Claims (93)

1. A system for managing data protection of virtual machines hosted by hosts of data clusters, comprising:

storages; and

a data protection manager programmed to:

identify a data protection event associated with at least one virtual machine (VM) of a data cluster of the data clusters;

obtain, in response the data protection event, data protection rules and a protection policy associated with the at least one VM;

based on the data protection rules and a protection policy associated with the at least one VM:

spawn, by a monitoring engine orchestrator of the data protection manager, at least one monitoring engine to the data cluster, wherein the monitoring engine monitors data protection services after it is spawned;

initiate performance of the data protection services for the at least one VM using a first storage of the storages;

obtain, after the spawning, monitoring information from the at least one monitoring engine;

make a determination that a data protection rule event of the data protection rule events occurred using the monitoring information, wherein the data protection rule events comprise:

utilization of a processor associated with the VM exceeding a threshold,

network bandwidth associated with a VM data manager exceeding a threshold, and

input/output operations per second (IOPS) of the storages exceed a threshold; and

in response to the determination:

initiate the performance of a corrective action of corrective actions based on the data protection rules using a second storage of the storages.

2. The system of claim 1 , wherein making the determination that the data protection rule event of the data protection rule events occurred using the monitoring information comprises;

identifying, based on the monitoring information and the data protection rules, the occurrence of the data protection rule event;

identifying, based on the data protection rules, the corrective action associated with the data protection rule event using the data protection rules; and

identifying, based on infrastructure information, the second storage to perform at least a portion of the corrective action.

3. The system of claim 1 , wherein deploying the at least one monitoring engine comprises:

generating the at least one monitoring engine;

sending the monitoring engine to the data cluster; and

initiating monitoring the data protection services by the at least one monitoring engine.

4. The system of claim 1 , wherein the data protection manager is further programmed to:

before identifying the data protection event:

obtain a protection policy associated with the VM; and

generate the data protection rules based on the protection policy.

5. The system of claim 4 , wherein the data protection rules comprise:

data protection rule events; and

corrective actions.

6. The system of claim 5 , wherein the data protection rules specify that the data protection rule event is associated with the corrective action.

7. The system of claim 2 , wherein the monitoring the data protection services comprises:

generating, by the at least one monitoring engine, the monitoring information associated with the performance of the data protection services; and

sending, by the at least one monitoring engine, the monitoring information to the data protection manager.

8. The system of claim 7 , wherein monitoring information specifies whether a data protection rule event has occurred and comprises the infrastructure information.

9. A method for managing data protection of virtual machines hosted by hosts of data clusters, comprising:

identifying a data protection event associated with at least one virtual machine (VM) of a data cluster of the data clusters;

obtaining, in response the data protection event, data protection rules and a protection policy associated with the at least one VM;

based on the data protection rules and a protection policy associated with the at least one VM:

spawning, by a monitoring engine orchestrator of the data protection manager, at least one monitoring engine to the data cluster, wherein the monitoring engine monitors data protection services after it is spawned;

initiating performance of the data protection services for the at least one VM using a first storage of the storages;

obtaining, after the spawning, monitoring information from the at least one monitoring engine;

making a determination that a data protection rule event of the data protection rule events occurred using the monitoring information, wherein the data protection rule events comprise:

utilization of a processor associated with the VM exceeding a threshold,

network bandwidth associated with a VM data manager exceeding a threshold, and

input/output operations per second (IOPS) of the storages exceed a threshold; and

in response to the determination:

initiating the performance of a corrective action of corrective actions based on the data protection rules using a second storage of the storages.

10. The method of claim 9 , wherein making the determination that a data protection rule event of the data protection rule events occurred using the monitoring information comprises:

identifying, based on the monitoring information and the data protection rules, the occurrence of the data protection rule event;

identifying, based on the data protection rules, the corrective action associated with the data protection rule event using the data protection rules; and

identifying, based on infrastructure information, the second storage to perform at least a portion of the corrective action.

11. The method of claim 9 , wherein deploying the at least one monitoring engine comprises:

generating the at least one monitoring engine;

sending the monitoring engine to the data cluster; and

initiating monitoring the data protection services by the at least one monitoring engine.

12. The method of claim 9 , further comprising:

before identifying the data protection event:

obtaining a protection policy associated with the VM; and

generating the data protection rules based on the protection policy.

13. The method of claim 12 , wherein the data protection rules comprise:

data protection rule events; and

corrective actions.

14. The method of claim 13 , wherein the data protection rules specify that the data protection rule event is associated with the corrective action.

15. The method of claim 10 , wherein the monitoring the data protection services comprises:

generating, by the at least one monitoring engine, the monitoring information associated with the performance of the data protection services; and

sending, by the at least one monitoring engine, the monitoring information to the data protection manager.

16. The method of claim 15 , wherein monitoring information specifies whether a data protection rule event has occurred and comprises the infrastructure information.

17. A non-transitory computer readable medium comprising computer readable program code, which when executed by a computer processor enables the computer processor to perform a method for managing data protection of virtual machines hosted by hosts of data clusters, wherein the method comprises:

identifying a data protection event associated with at least one virtual machine (VM) of a data cluster of the data clusters;

obtaining, in response the data protection event, data protection rules and a protection policy associated with the at least one VM;

based on the data protection rules and a protection policy associated with the at least one VM:

spawning, by a monitoring engine orchestrator of the data protection manager, at least one monitoring engine to the data cluster, wherein the monitoring engine monitors data protection services after it is spawned;

initiating performance of the data protection services for the at least one VM using a first storage of the storages;

obtaining, after the spawning, monitoring information from the at least one monitoring engine;

making a determination that a data protection rule event of the data protection rule events occurred using the monitoring information, wherein the data protection rule events comprise:

utilization of a processor associated with the VM exceeding a threshold,

network bandwidth associated with a VM data manager exceeding a threshold, and

input/output operations per second (IOPS) of the storages exceed a threshold; and

in response to the determination:

initiating the performance of a corrective action of corrective actions based on the data protection rules using a second storage of the storages.

18. The non-transitory computer readable medium of claim 17 , wherein making the determination that a data protection rule event of the data protection rule events occurred using the monitoring information comprises;

identifying, based on the monitoring information and the data protection rules, the occurrence of the data protection rule event;

identifying, based on the data protection rules, the corrective action associated with the data protection rule event using the data protection rules; and

identifying, based on infrastructure information, the second storage to perform at least a portion of the corrective action.

19. The non-transitory computer readable medium of claim 17 , wherein deploying the at least one monitoring engine comprises:

generating the at least one monitoring engine;

sending the monitoring engine to the data cluster; and

initiating monitoring the data protection services by the at least one monitoring engine.

20. The non-transitory computer readable medium of claim 17 , wherein the method further comprising:

before identifying the data protection event:

obtaining a protection policy associated with the VM; and

generating the data protection rules based on the protection policy.

Assignments (9)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (055479/0342) Recorded Jun 10, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
Reel/Frame 062021/0460 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (055479/0051) Recorded Jun 10, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
Reel/Frame 062021/0663 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (056136/0752) Recorded Jun 10, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
Reel/Frame 062021/0771 →
RELEASE OF SECURITY INTEREST AT REEL 055408 FRAME 0697 Recorded Nov 2, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
Reel/Frame 058001/0553 →
SECURITY INTEREST Recorded Mar 3, 2021
From: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 056136/0752 →
SECURITY INTEREST Recorded Mar 3, 2021
From: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 055479/0051 →
SECURITY INTEREST Recorded Mar 3, 2021
From: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 055479/0342 →
SECURITY AGREEMENT Recorded Feb 25, 2021
From: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 055408/0697 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 1, 2021
From: KULKARNI, GURURAJ; REDDY, ANAND
To: EMC IP HOLDING COMPANY LLC
Reel/Frame 055092/0592 →
Continuity (1)
Related Publication 20220237310A1 · Jul 28, 2022