IP Library Granted Patent US 11,023,332
Granted Patent B2
US 11,023,332 · App. 16/653,675 · Granted Jun 1, 2021

System and method for efficient backup system aware direct data migration between cloud storages

Inventors: Jayanth Kumar Reddy Perneti (Bangalore, IN); Rahul Deo Vishwakarma (Bangalore, IN); Kalyan C Gunda (Bangalore, IN)
Assignee: EMC IP Holding Company LLC
G06F11/1464G06F3/067G06F3/0617G06F3/0647G06F11/1451G06F11/1461G06F11/1469G06F11/324G06F3/065G06F11/1458
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,023,332
App. No.
16/653,675
Granted
Jun 1, 2021
Kind
B2
Abstract

A file is backed up to a backup system. A first cloud storage provided by a first cloud provider is connected to the backup system and the file is moved to the first cloud storage. Metadata is created at the backup system to reference the file moved to the first cloud storage. A second cloud storage is connected to the backup system. The file is moved from the first cloud storage to the second cloud storage. The metadata at the backup system is updated to reference the file now residing at the second cloud storage.

Claims (100)

1. A method comprising:

backing up, by a backup application, a plurality of files from a plurality of clients to an active tier of a backup server;

connecting a first cloud storage provided by a first cloud storage provider to the backup application to allow moving at least a first file from the backup server to the first cloud storage;

creating first and second metadata for the first file;

replacing the first file in the active tier with the first metadata;

storing the second metadata in a cloud tier of the backup server, separate from the active tier, the first metadata in the active tier comprising a reference to the second metadata in the cloud tier, and the second metadata in the cloud tier comprising a reference to the first file moved to the first cloud storage;

connecting a second cloud storage, separate from the first cloud storage, to the backup application to allow copying the first file from the first cloud storage to the second cloud storage, without recalling the first file to the active tier;

triggering, within the backup application, a data management operation comprising copying at least a portion of the first file from the first cloud storage to the second cloud storage; and

upon the copying, updating, by the backup application, the second metadata in the cloud tier to reference the first file now residing at the second cloud storage.

2. The method of claim 1 further comprising:

receiving a request from a client to restore the first file;

examining the second metadata in the cloud tier to determine a location of the first file;

determining from the examination that the first file is located at the second cloud storage;

recalling the first file from the second cloud storage to the active tier to the client, thereby fulfilling the request; and

updating metadata in the cloud tier with information indicating that the first file has been restored to the client from the second cloud storage.

3. The method of claim 1 further comprising:

generating and storing first information indicating a time and date when the first file was backed up to the active tier of the backup server;

generating and storing second information indicating a time and date when the first file was moved from the active tier to the first cloud storage;

generating and storing third information indicating a time and date when the data management operation was performed on the first file;

receiving a request to display a lifecycle of the first file; and

displaying, on a graphical user interface (GUI) of an electronic screen, a graphic having the first, second, and third information.

4. The method of claim 1 further comprising:

after the copying the at least portion of the first file from the first cloud storage to the second cloud storage, deleting the first file from the first cloud storage.

5. The method of claim 1 further comprising:

after the copying the at least portion of the first file from the first cloud storage to the second cloud storage, maintaining the first file at the first cloud storage.

6. The method of claim 1 further comprising:

defining a data management rule to control the triggering of the data management operation between the first and second cloud storages, wherein the data management rule comprises at least one user-defined condition of a plurality of user-defined conditions to satisfy, the plurality of user-defined conditions comprising a first condition associated with an age of a file, and a second condition associated with a size of the file.

7. The method of claim 1 further comprising:

moving the plurality of files from the backup server to the first cloud storage;

determining that the plurality of files should be moved from the first cloud storage to the second cloud storage;

calculating an estimated time required to move the plurality of files from the first cloud storage to the second cloud storage;

consulting a service level agreement (SLA) specifying an allotted threshold duration for moving the plurality of files from the first cloud storage to the second cloud storage to determine whether the estimated time exceeds the allotted threshold duration;

if the estimated time does not exceed the allotted threshold duration, proceeding with moving the plurality of files from the first cloud storage to the second cloud storage; and

if the estimated time exceeds the allotted threshold duration, creating a priority list indicating an order in which the plurality of files are to be moved from the first cloud storage to the second cloud storage, and proceeding with the moving the plurality of files from the first cloud storage to the second cloud storage according to the priority list.

8. A system comprising: a processor; and memory configured to store one or more sequences of instructions which, when executed by the processor, cause the processor to carry out the steps of:

backing up, by a backup application, a plurality of files from a plurality of clients to an active tier of a backup server;

connecting a first cloud storage provided by a first cloud storage provider to the backup application to allow moving at least a first file from the backup server to the first cloud storage;

creating first and second metadata for the first file;

replacing the first file in the active tier with the first metadata;

storing the second metadata in a cloud tier of the backup server, separate from the active tier, the first metadata in the active tier comprising a reference to the second metadata in the cloud tier, and the second metadata in the cloud tier comprising a reference to the first file moved to the first cloud storage;

connecting a second cloud storage, separate from the first cloud storage, to the backup application to allow copying the first file from the first cloud storage to the second cloud storage, without recalling the first file to the active tier;

triggering, within the backup application, a data management operation comprising copying at least a portion of the first file from the first cloud storage to the second cloud storage; and

upon the copying, updating, by the backup application, the second metadata in the cloud tier to reference the first file now residing at the second cloud storage.

9. The system of claim 8 wherein the processor further carries out the steps of:

receiving a request from a client to restore the first file;

examining the second metadata in the cloud tier to determine a location of the first file;

determining from the examination that the first file is located at the second cloud storage;

recalling the first file from the second cloud storage to the active tier to the client, thereby fulfilling the request; and

updating metadata in the cloud tier with information indicating that the first file has been restored to the client from the second cloud storage.

10. The system of claim 8 wherein the processor further carries out the steps of:

generating and storing first information indicating a time and date when the first file was backed up to the active tier of the backup server;

generating and storing second information indicating a time and date when the first file was moved from the active tier to the first cloud storage;

generating and storing third information indicating a time and date when the data management operation was performed on the first file;

receiving a request to display a lifecycle of the first file; and

displaying, on a graphical user interface (GUI) of an electronic screen, a graphic having the first, second, and third information.

11. The system of claim 8 wherein the processor further carries out the steps of:

after the copying the at least portion of the first file from the first cloud storage to the second cloud storage, deleting the first file from the first cloud storage.

12. The system of claim 8 wherein the processor further carries out the steps of:

after the copying the at least portion of the first file from the first cloud storage to the second cloud storage, maintaining the first file at the first cloud storage.

13. The system of claim 8 wherein the processor further carries out the steps of:

defining a data management rule to control the triggering of the data management operation between the first and second cloud storages, wherein the data management rule comprises at least one user-defined condition of a plurality of user-defined conditions to satisfy, the plurality of user-defined conditions comprising a first condition associated with an age of a file, and a second condition associated with a size of the file.

14. The system of claim 8 wherein the processor further carries out the steps of:

moving the plurality of files from the backup server to the first cloud storage;

determining that the plurality of files should be moved from the first cloud storage to the second cloud storage;

calculating an estimated time required to move the plurality of files from the first cloud storage to the second cloud storage;

consulting a service level agreement (SLA) specifying an allotted threshold duration for moving the plurality of files from the first cloud storage to the second cloud storage to determine whether the estimated time exceeds the allotted threshold duration;

if the estimated time does not exceed the allotted threshold duration, proceeding with moving the plurality of files from the first cloud storage to the second cloud storage; and

if the estimated time exceeds the allotted threshold duration, creating a priority list indicating an order in which the plurality of files are to be moved from the first cloud storage to the second cloud storage, and proceeding with the moving the plurality of files from the first cloud storage to the second cloud storage according to the priority list.

15. A computer program product, comprising a non-transitory computer-readable medium having a computer-readable program code embodied therein, the computer-readable program code adapted to be executed by one or more processors to implement a method comprising:

backing up, by a backup application, a plurality of files from a plurality of clients to an active tier of a backup server;

connecting a first cloud storage provided by a first cloud storage provider to the backup application to allow moving at least a first file from the backup server to the first cloud storage;

creating first and second metadata for the first file;

replacing the first file in the active tier with the first metadata;

storing the second metadata in a cloud tier of the backup server, separate from the active tier, the first metadata in the active tier comprising a reference to the second metadata in the cloud tier, and the second metadata in the cloud tier comprising a reference to the first file moved to the first cloud storage;

connecting a second cloud storage, separate from the first cloud storage, to the backup application to allow copying the first file from the first cloud storage to the second cloud storage, without recalling the first file to the active tier;

triggering, within the backup application, a data management operation comprising copying at least a portion of the first file from the first cloud storage to the second cloud storage; and

upon the copying, updating, by the backup application, the second metadata in the cloud tier to reference the first file now residing at the second cloud storage.

16. The computer program product of claim 15 wherein the method further comprises:

receiving a request from a client to restore the first file;

examining the second metadata in the cloud tier to determine a location of the first file;

determining from the examination that the first file is located at the second cloud storage;

recalling the first file from the second cloud storage to the active tier to the client, thereby fulfilling the request; and

updating metadata in the cloud tier with information indicating that the first file has been restored to the client from the second cloud storage.

17. The computer program product of claim 15 wherein the method further comprises:

generating and storing first information indicating a time and date when the first file was backed up to the active tier of the backup server;

generating and storing second information indicating a time and date when the first file was moved from the active tier to the first cloud storage;

generating and storing third information indicating a time and date when the data management operation was performed on the first file;

receiving a request to display a lifecycle of the first file; and

displaying, on a graphical user interface (GUI) of an electronic screen, a graphic having the first, second, and third information.

18. The computer program product of claim 15 wherein the method further comprises:

after the copying the at least portion of the first file from the first cloud storage to the second cloud storage, deleting the first file from the first cloud storage.

19. The computer program product of claim 15 wherein the method further comprises:

defining a data management rule to control the triggering of the data management operation between the first and second cloud storages, wherein the data management rule comprises at least one user-defined condition of a plurality of user-defined conditions to satisfy, the plurality of user-defined conditions comprising a first condition associated with an age of a file, and a second condition associated with a size of the file.

20. The computer program product of claim 15 wherein the method further comprises:

moving the plurality of files from the backup server to the first cloud storage;

determining that the plurality of files should be moved from the first cloud storage to the second cloud storage;

calculating an estimated time required to move the plurality of files from the first cloud storage to the second cloud storage;

consulting a service level agreement (SLA) specifying an allotted threshold duration for moving the plurality of files from the first cloud storage to the second cloud storage to determine whether the estimated time exceeds the allotted threshold duration;

if the estimated time does not exceed the allotted threshold duration, proceeding with moving the plurality of files from the first cloud storage to the second cloud storage; and

if the estimated time exceeds the allotted threshold duration, creating a priority list indicating an order in which the plurality of files are to be moved from the first cloud storage to the second cloud storage, and proceeding with the moving the plurality of files from the first cloud storage to the second cloud storage according to the priority list.

Assignments (9)
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 (051302/0528) Recorded Jun 23, 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; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO WYSE TECHNOLOGY L.L.C.); SECUREWORKS CORP.
Reel/Frame 060438/0593 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053311/0169) Recorded Jun 23, 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 060438/0742 →
RELEASE OF SECURITY INTEREST AT REEL 051449 FRAME 0728 Recorded Nov 2, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC; WYSE TECHNOLOGY L.L.C.; SECUREWORKS CORP.; EMC CORPORATION
Reel/Frame 058002/0010 →
SECURITY INTEREST Recorded Jun 5, 2020
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 053311/0169 →
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 Dec 31, 2019
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC; WYSE TECHNOLOGY L.L.C.; SECUREWORKS CORP.; EMC CORPORATION
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 051449/0728 →
PATENT SECURITY AGREEMENT (NOTES) Recorded Dec 16, 2019
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC; WYSE TECHNOLOGY L.L.C.; SECUREWORKS CORP.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 051302/0528 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 15, 2019
From: PERNETI, JAYANTH KUMAR REDDY; VISHWAKARMA, RAHUL DEO; GUNDA, KALYAN C
To: EMC IP HOLDING COMPANY LLC
Reel/Frame 050723/0078 →
Continuity (1)
Related Publication 20210109818A1 · Apr 15, 2021
Cited By (2)
US 12,323,484 US 12,645,637