IP Library Granted Patent US 11,461,188
Granted Patent B2
US 11,461,188 · App. 17/155,277 · Granted Oct 4, 2022

Automated failover backup reconfiguration management for storage systems

Inventor: Sunil Kumar (Bangalore, IN)
Assignee: EMC IP Holding Company LLC
G06F11/1464G06F11/0772G06F11/1451G06F11/1469G06F11/2023
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,461,188
App. No.
17/155,277
Granted
Oct 4, 2022
Kind
B2
Abstract

Techniques for managing backup plans in information processing systems are disclosed. For example, a method comprises managing a data backup plan for an information processing system comprising a set of host devices that execute application instances for which data is stored on a first storage system and mirrored on a second storage system. After a given condition is detected, managing the data backup plan comprises reconfiguring the data backup plan by: (i) automatically subscribing, to the data backup plan, one or more of the application instances that execute on one or more active ones of the set of host devices configured to store data on the second storage system; and (ii) automatically unsubscribing, from the data backup plan, one or more of the application instances that previously executed on one or more non-active ones of the set of host devices configured to store data on the first storage system.

Claims (48)

1. An apparatus comprising:

at least one processing device comprising a processor coupled to a memory, the at least one processing device, when executing program code, is configured to:

manage a data backup plan for an information processing system comprising a set of host devices that execute application instances for which data is stored on a first storage system and mirrored on a second storage system;

wherein, after a given condition is detected, managing a data backup plan comprises reconfiguring the data backup plan by: (i) automatically subscribing, to the data backup plan, one or more of the application instances that execute on one or more active ones of the set of host devices configured to store data on the second storage system; and (ii) automatically unsubscribing, from the data backup plan, one or more of the application instances that previously executed on one or more non-active ones of the set of host devices configured to store data on the first storage system;

wherein managing a data backup plan further comprises:

executing the data backup plan to:

collect information from one or more of the set of host devices, the first storage system, and the second storage system; and

detect occurrence of a failover-causing condition as the given condition and identifying application instances on one or more failed ones of the set of host devices;

identifying application instances on one or more non-failed ones of the set of host devices configured to store data on the second storage system; and

generating a mapping between applications instances on the one or more non-failed ones of the set of host devices and applications instances on the one or more failed ones of the set of host devices.

2. The apparatus of claim 1 , wherein when the given condition that is detected is a failover-causing event: (i) one or more of the application instances that execute on one or more non-failed ones of the set of host devices configured to store data on the second storage system are automatically subscribed to the data backup plan; and (ii) one or more of the application instances that execute on one or more failed ones of the set of host devices configured to store data on the first storage system are automatically unsubscribed from the data backup plan.

3. The apparatus of claim 1 , wherein the collected information comprises information relating to one or more of: (i) a status of links between the first storage system and the second storage system; (ii) a direction of data mirroring between the first storage system and the second storage system; and (iii) one or more storage volumes that are mirrored.

4. The apparatus of claim 3 , wherein detecting the occurrence of a failover-causing condition is performed subsequent to collecting information.

5. The apparatus of claim 4 wherein managing a data backup plan further comprises deploying an application-aware agent on each of the one or more non-failed ones of the set of host devices configured to store data on the second storage system.

6. The apparatus of claim 5 , wherein managing a data backup plan further comprises collecting information via the deployed application-aware agent on applications instances on each of the one or more non-failed ones of the set of host devices.

7. The apparatus of claim 6 , wherein the mapping is generated between applications instances on each of the one or more non-failed ones of the set of host devices and applications instances on each of the one or more failed ones of the set of host devices.

8. The apparatus of claim 7 , wherein managing a data backup plan further comprises using the mapping to: (i) subscribe the applications instances on each of the one or more non-failed ones of the set of host devices to the data backup plan; and (ii) unsubscribe the applications instances on each of the one or more failed ones of the set of host devices from the data backup plan.

9. The apparatus of claim 1 , wherein the first storage system comprises a production storage system and the second storage system comprises a disaster recovery storage system.

10. A method comprising:

managing a data backup plan for an information processing system comprising a set of host devices that execute application instances for which data is stored on a first storage system and mirrored on a second storage system;

wherein, after a given condition is detected, managing a data backup plan comprises reconfiguring the data backup plan by: (i) automatically subscribing, to the data backup plan, one or more of the application instances that execute on one or more active ones of the set of host devices configured to store data on the second storage system; and (ii) automatically unsubscribing, from the data backup plan, one or more of the application instances that previously executed on one or more non-active ones of the set of host devices configured to store data on the first storage system;

wherein managing a data backup plan further comprises:

executing the data backup plan to:

collect information from one or more of the set of host devices, the first storage system, and the second storage system; and

detect occurrence of a failover-causing condition as the given condition and identifying application instances on one or more failed ones of the set of host devices;

identifying application instances on one or more non-failed ones of the set of host devices configured to store data on the second storage system; and

generating a mapping between applications instances on the one or more non-failed ones of the set of host devices and applications instances on the one or more failed ones of the set of host devices; and

wherein the managing step is performed by at least one processing device comprising a processor coupled to a memory executing program code.

11. The method of claim 10 , wherein when the given condition that is detected is a failover-causing event: (i) one or more of the application instances that execute on one or more non-failed ones of the set of host devices configured to store data on the second storage system are automatically subscribed to the data backup plan; and (ii) one or more of the application instances that execute on one or more failed ones of the set of host devices configured to store data on the first storage system are automatically unsubscribed from the data backup plan.

12. The method of claim 10 , wherein the collected information comprises information relating to one or more of: (i) a status of links between the first storage system and the second storage system; (ii) a direction of data mirroring between the first storage system and the second storage system; and (iii) one or more storage volumes that are mirrored.

13. The method of claim 12 , wherein managing a data backup plan comprises detecting the occurrence of a failover-causing condition subsequent to collecting the information.

14. The method of claim 13 , wherein managing a data backup plan further comprises deploying an application-aware agent on each of the one or more non-failed ones of the set of host devices configured to store data on the second storage system.

15. The method of claim 14 , wherein managing a data backup plan further comprises collecting information via the deployed application-aware agent on applications instances on each of the one or more non-failed ones of the set of host devices.

16. The method of claim 15 , wherein the mapping is generated between applications instances on each of the one or more non-failed ones of the set of host devices and applications instances on each of the one or more failed ones of the set of host devices.

17. A computer program product comprising a non-transitory processor-readable storage medium having stored therein program code of one or more software programs, wherein the program code when executed by at least one processing device causes the at least one processing device to:

manage a data backup plan for an information processing system comprising a set of host devices that execute application instances for which data is stored on a first storage system and mirrored on a second storage system;

wherein, after a given condition is detected, managing a data backup plan comprises reconfiguring the data backup plan by: (i) automatically subscribing, to the data backup plan, one or more of the application instances that execute on one or more active ones of the set of host devices configured to store data on the second storage system; and (ii) automatically unsubscribing, from the data backup plan, one or more of the application instances that previously executed on one or more non-active ones of the set of host devices configured to store data on the first storage system;

wherein managing a data backup plan further comprises:

executing the data backup plan to:

collect information from one or more of the set of host devices, the first storage system, and the second storage system; and

detect occurrence of a failover-causing condition as the given condition and identifying application instances on one or more failed ones of the set of host devices;

identifying application instances on one or more non-failed ones of the set of host devices configured to store data on the second storage system; and

generating a mapping between applications instances on the one or more non-failed ones of the set of host devices and applications instances on the one or more failed ones of the set of host devices.

18. The computer program product of claim 17 , wherein when the given condition that is detected is a failover-causing event: (i) one or more of the application instances that execute on one or more non-failed ones of the set of host devices configured to store data on the second storage system are automatically subscribed to the data backup plan; and (ii) one or more of the application instances that execute on one or more failed ones of the set of host devices configured to store data on the first storage system are automatically unsubscribed from the data backup plan.

19. The computer program product of claim 17 , wherein the collected information comprises information relating to one or more of: (i) a status of links between the first storage system and the second storage system; (ii) a direction of data mirroring between the first storage system and the second storage system; and (iii) one or more storage volumes that are mirrored.

20. The computer program product of claim 19 , wherein managing a data backup plan further comprises:

deploying an application-aware agent on each of the one or more non-failed ones of the set of host devices configured to store data on the second storage system; and

collecting information via the deployed application-aware agent on applications instances on each of the one or more non-failed ones of the set of host devices.

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 Jan 22, 2021
From: KUMAR, SUNIL
To: EMC IP HOLDING COMPANY LLC
Reel/Frame 054995/0076 →