IP Library Granted Patent US 11,520,669
Granted Patent B2
US 11,520,669 · App. 17/243,275 · Granted Dec 6, 2022

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,520,669
App. No.
17/243,275
Filed
Apr 28, 2021
Granted
Dec 6, 2022
Kind
B2
Art Unit
2138
USPC
711/162
Abstract

A first cloud vendor is registered by a backup application. A file is moved from backup storage of the backup application to the first cloud vendor. A reference is maintained at the backup storage to the first file residing at the first cloud vendor. A second cloud vendor is registered by the backup application. The backup application directs a migration of the file from the first cloud vendor to the second cloud vendor without recalling the file to the backup storage. A reference maintained at the backup storage is updated to refer to the file now residing at the second cloud vendor. The updated reference is maintained at the backup storage.

Claims (93)

1. A method comprising:

registering, by a backup application, a first cloud vendor;

moving at least a first file from a backup storage of the backup application to the first cloud vendor;

maintaining a reference at the backup storage to the first file residing at the first cloud vendor;

registering, by the backup application, a second cloud vendor;

directing, by the backup application, a migration of the first file from the first cloud vendor to the second cloud vendor, without recalling the first file to the backup storage;

updating the reference maintained at the backup storage to refer to the first file now residing at the second cloud vendor;

maintaining the updated reference at the backup storage;

before the moving the first file from the backup storage to the first cloud vendor, backing up, by the backup application, the first file from a client to an active tier at the backup storage;

establishing a cloud tier at the backup storage; and

upon the first file being moved from the backup storage to the first cloud vendor, creating first and second metadata,

wherein the first metadata is maintained in the active tier at the backup storage, and the second metadata is maintained in the cloud tier at the backup storage, the reference being the second metadata, and

wherein the first metadata in the active tier references the second metadata in the cloud tier.

2. The method of claim 1 further comprising:

tracking the migration of the first file from the first cloud vendor to the second cloud vendor;

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

examining the updated reference to determine a location of the first file;

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

recalling the first file from the second cloud vendor to the backup storage to the client; and

updating tracking information to indicate that the first file has been restored to the client from the second cloud vendor.

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 from a client to the backup storage;

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

generating and storing third information indicating a time and date when the first file was migrated from the first cloud vendor to the second cloud vendor;

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:

defining a plurality of rules to trigger the moving of the first file from the backup storage to the first cloud vendor, and the migration of the first file from the first cloud vendor to the second cloud vendor.

5. The method of claim 1 further comprising:

storing, by the backup application, first credentials for accessing the first cloud vendor; and

storing, by the backup application, second credentials for accessing the second cloud vendor.

6. 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:

registering, by a backup application, a first cloud vendor;

moving at least a first file from a backup storage of the backup application to the first cloud vendor;

maintaining a reference at the backup storage to the first file residing at the first cloud vendor;

registering, by the backup application, a second cloud vendor;

directing, by the backup application, a migration of the first file from the first cloud vendor to the second cloud vendor, without recalling the first file to the backup storage;

updating the reference maintained at the backup storage to refer to the first file now residing at the second cloud vendor;

maintaining the updated reference at the backup storage;

before the moving the first file from the backup storage to the first cloud vendor, backing up, by the backup application, the first file from a client to an active tier at the backup storage;

establishing a cloud tier at the backup storage; and

upon the first file being moved from the backup storage to the first cloud vendor, creating first and second metadata,

wherein the first metadata is maintained in the active tier at the backup storage, and the second metadata is maintained in the cloud tier at the backup storage, the reference being the second metadata, and

wherein the first metadata in the active tier references the second metadata in the cloud tier.

7. The system of claim 6 wherein the processor further carries out the steps of:

tracking the migration of the first file from the first cloud vendor to the second cloud vendor;

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

examining the updated reference to determine a location of the first file;

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

recalling the first file from the second cloud vendor to the backup storage to the client; and

updating tracking information to indicate that the first file has been restored to the client from the second cloud vendor.

8. The system of claim 6 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 from a client to the backup storage;

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

generating and storing third information indicating a time and date when the first file was migrated from the first cloud vendor to the second cloud vendor;

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.

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

defining a plurality of rules to trigger the moving of the first file from the backup storage to the first cloud vendor, and the migration of the first file from the first cloud vendor to the second cloud vendor.

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

storing, by the backup application, first credentials for accessing the first cloud vendor; and

storing, by the backup application, second credentials for accessing the second cloud vendor.

11. 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:

registering, by a backup application, a first cloud vendor;

moving at least a first file from a backup storage of the backup application to the first cloud vendor;

maintaining a reference at the backup storage to the first file residing at the first cloud vendor;

registering, by the backup application, a second cloud vendor;

directing, by the backup application, a migration of the first file from the first cloud vendor to the second cloud vendor, without recalling the first file to the backup storage;

updating the reference maintained at the backup storage to refer to the first file now residing at the second cloud vendor;

maintaining the updated reference at the backup storage;

generating and storing first information indicating a time and date when the first file was backed up from a client to the backup storage;

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

generating and storing third information indicating a time and date when the first file was migrated from the first cloud vendor to the second cloud vendor;

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.

12. The computer program product of claim 11 wherein the method further comprises:

tracking the migration of the first file from the first cloud vendor to the second cloud vendor;

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

examining the updated reference to determine a location of the first file;

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

recalling the first file from the second cloud vendor to the backup storage to the client; and

updating tracking information to indicate that the first file has been restored to the client from the second cloud vendor.

13. The computer program product of claim 11 wherein the method further comprises:

before the moving the first file from the backup storage to the first cloud vendor, backing up, by the backup application, the first file from a client to an active tier at the backup storage;

establishing a cloud tier at the backup storage; and

upon the first file being moved from the backup storage to the first cloud vendor, creating first and second metadata,

wherein the first metadata is maintained in the active tier at the backup storage, and the second metadata is maintained in the cloud tier at the backup storage, the reference being the second metadata, and

wherein the first metadata in the active tier references the second metadata in the cloud tier.

14. The computer program product of claim 11 wherein the method further comprises:

defining a plurality of rules to trigger the moving of the first file from the backup storage to the first cloud vendor, and the migration of the first file from the first cloud vendor to the second cloud vendor.

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

storing, by the backup application, first credentials for accessing the first cloud vendor; and

storing, by the backup application, second credentials for accessing the second cloud vendor.

Assignments (9)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (056295/0280) 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 062022/0255 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (056295/0001) 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 062021/0844 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (056295/0124) 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 062022/0012 →
RELEASE OF SECURITY INTEREST Recorded Nov 2, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
Reel/Frame 058297/0332 →
SECURITY INTEREST Recorded May 19, 2021
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 056295/0280 →
SECURITY INTEREST Recorded May 19, 2021
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 056295/0001 →
SECURITY INTEREST Recorded May 19, 2021
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 056295/0124 →
CORRECTIVE ASSIGNMENT TO CORRECT THE MISSING PATENTS THAT WERE ON THE ORIGINAL SCHEDULED SUBMITTED BUT NOT ENTERED PREVIOUSLY RECORDED AT REEL: 056250 FRAME: 0541. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded May 17, 2021
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 056311/0781 →
SECURITY AGREEMENT Recorded May 14, 2021
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 056250/0541 →
Continuity (2)
Continuation 16653675 · Oct 15, 2019
Related Publication 20210248044A1 · Aug 12, 2021
Cited By (1)
US 12,585,557