IP Library Granted Patent US 10,860,440
Granted Patent B2
US 10,860,440 · App. 15/906,300 · Granted Dec 8, 2020

Scheduled recovery in a data protection system

Inventor: Shern S. Jauhal (Palo Alto, CA)
Assignee: EMC IP HOLDING COMPANY LLC
G06F11/1469
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 10,860,440
App. No.
15/906,300
Granted
Dec 8, 2020
Kind
B2
Abstract

Systems and methods for scheduling a recovery operation for a host. A user interface is displayed and a recovery operation is configured. Configuration information for the recovery operation is stored and associated with a schedule that is also set via the user interface. The recovery operation may be an ad hoc recovery operation, a periodic recovery operation, and/or a validating recovery operation.

Claims (42)

1. A method for scheduling a recovery operation to recover data of a host, wherein different types of data stored in the system are backed up using different client backup modules, the method comprising:

identifying a client backup module that backed up a host in order to determine a manner in which data of the host was backed up by the client backup module;

coordinating with a backup service to identify a recovery module from among multiple recovery modules based on the client backup module used in backing up the data of the host and based on circumstances of the host to which the data is being recovered by the recovery operation;

displaying a workflow in a user interface for recovering the host;

dynamically adapting the workflow based on the identified recovery module, at a time of scheduling the recovery operation, to account for the manner in which the data was backed up by the identified client backup module and the circumstances of the host;

saving the workflow as persistent data;

scheduling the recovery operation as an adhoc recovery operation or a periodic recovery operation; and

performing the recovery operation in accordance with the persistent data, wherein the recovery module is dynamically retrieved from the backup service when the recovery operation is performed, wherein the backup service is configured to maintain a plurality of recovery modules for selection by the recovery operation.

2. The method of claim 1 , further comprising validating the recovered data.

3. The method of claim 2 , further comprising performing heuristics on the recovered data to validate the recovered data.

4. The method of claim 1 , further comprising selecting the host for the recovery operation.

5. The method of claim 1 , further comprising coordinating with the backup service to select the recovery module, wherein the selection of the recovery module is further based on the host to which the data is being recovered by the recovery operation.

6. The method of claim 1 , further comprising displaying the user interface on the host being recovered or on a separate device.

7. A non-transitory computer readable medium comprising computer executable instructions that, when executed, perform a method for scheduling a recovery operation to recover data of a host, wherein different types of data stored in the system are backed up using different client backup modules, the method comprising:

identifying a client backup module that backed up a host in order to determine a manner in which data of the host was backed up by the client backup module;

coordinating with a backup service to identify a recovery module from among multiple recovery modules based on the client backup module used in backing up the data of the host and based on circumstances of the host to which the data is being recovered by the recovery operation;

displaying a workflow in a user interface for recovering the host;

dynamically adapting the workflow based on the identified recovery module, at a time of scheduling the recovery operation, to account for the manner in which the data was backed up by the identified client backup module and the circumstances of the host;

saving the workflow as persistent data;

scheduling the recovery operation as an ad hoc recovery operation or a periodic recovery operation; and

performing the recovery operation in accordance with the persistent data, wherein the recovery module is dynamically retrieved from the backup service when the recovery operation is performed, wherein the backup service is configured to maintain a plurality of recovery modules for selection by the recovery operation.

8. The method of claim 7 , further comprising validating the recovered data.

9. The method of claim 8 , further comprising performing heuristics on the recovered data to validate the recovered data.

10. The method of claim 7 , further comprising selecting the host for the recovery operation.

11. The method of claim 7 , further comprising coordinating with the backup service to select the recovery module, wherein the selection of the recovery module is further based on the host to which the data is being recovered by the recovery operation.

12. The method of claim 7 , further comprising displaying the user interface on the host being recovered or on a separate device.

13. A method for scheduling a recovery operation to recover data of a host, wherein different types of data stored in the system are backed up using different client backup modules, the method comprising:

coordinating with a data protection service to configure a recovery operation of a host by:

selecting the host from amongst a plurality of hosts;

selecting a backup associated with the selected host from a plurality of backups associated with the selected host;

determining a manner in which data of the host was backed up;

selecting a type of recovery based on the manner in which the data of the host was backed up;

displaying a workflow in a user interface for recovering the host;

dynamically adapting the workflow based on the type of recovery, at a time of scheduling the recovery operation, to account for the manner in which the data was backed up and a present circumstance of the host; and

saving the workflow including as persistent data;

scheduling the recovery operation as an ad hoc recovery operation or a periodic recovery operation or a validating recovery operation; and

performing the recovery operation in accordance with the persistent data.

14. The method of claim 13 , further comprising determining a manner in which the data of the host was backed up by identifying a client backup module that generated the selected backup.

15. The method of claim 14 , further comprising selecting a type of recovery by selecting a recovery module from a plurality of recovery modules maintained by the data protection service, wherein the recovery module dynamically adapts the workflow to account for the manner in which the data was backed up and the present circumstance of the host.

16. The method of claim 13 , further comprising scheduling the recovery operation, wherein at least one of:

the periodic recovery operation includes setting a relative date that is based on a date on which each recovery operation in the periodic recovery operation is performed; and

validating the recovery operation, wherein validating the recovery operation includes performing heuristics to validate the recovered data.

Assignments (7)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053546/0001) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC IP HOLDING COMPANY LLC
Reel/Frame 071642/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (046366/0014) Recorded May 20, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
Reel/Frame 060450/0306 →
RELEASE OF SECURITY INTEREST AT REEL 046286 FRAME 0653 Recorded Nov 2, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
Reel/Frame 058298/0093 →
SECURITY AGREEMENT Recorded Apr 22, 2020
From: CREDANT TECHNOLOGIES INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 053546/0001 →
SECURITY AGREEMENT Recorded Mar 21, 2019
From: CREDANT TECHNOLOGIES, INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 049452/0223 →
PATENT SECURITY AGREEMENT (NOTES) Recorded Jun 1, 2018
From: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 046366/0014 →
PATENT SECURITY AGREEMENT (CREDIT) Recorded Jun 1, 2018
From: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 046286/0653 →