IP Library Granted Patent US 11,461,189
Granted Patent B1
US 11,461,189 · App. 17/233,682 · Granted Oct 4, 2022

Method and system for archiving user data during backup generation

Inventors: Sunil Yadav (Bangalore, IN); Shelesh Chopra (Bangalore, IN); Amarendra Behera (Bangalore, IN); Tushar Dethe (Bangalore, IN); Himanshu Arora (Ghaziabad, IN); Deependra Pratap Singh (Kanpur, IN); Jigar Premjibhai Bhanushali (Valsad, IN); Sapna Chauhan (Bangalore, IN); Anjana Rao (Mangalore, IN); Vipin Kumar Kaushal (Bharthana, IN); Ravi Vijayakumar Chitloor (Bengaluru, IN)
Assignee: EMC IP Holding Company LLC
G06F11/1464G06F3/067G06F3/0619G06F3/0652G06F11/1435G06F11/1461G06F11/1469G06F16/113
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,189
App. No.
17/233,682
Granted
Oct 4, 2022
Kind
B1
Abstract

A system for providing data protection services for user data generated by an application includes persistent storage that includes an archive storage and a backup storage. The system also includes a manager. The manager is programmed to generate data chunks using user data, generate backup object metadata associated with the data chunks; obtain previously generated backup object metadata associated with the user data using an archive value, make a first determination that at least one data chunk of the data chunks is to be archived using the backup object metadata and the previously generated backup object metadata, and, in response to the first determination: store the at least one data chunk in the archive storage as a portion of a user data backup, and store remaining data chunks of the data chunks in the backup storage as the remaining portion of the user data backup.

Claims (79)

1. A system for providing data protection services for user data generated by an application, comprising:

persistent storage comprising an archive storage and a backup storage; and

a manager programmed to:

generate data chunks using the user data;

generate backup object metadata associated with the data chunks;

obtain previously generated backup object metadata associated with the user data using an archive value;

make a first determination that at least one data chunk of the data chunks is to be archived using the backup object metadata and the previously generated backup object metadata; and

in response to the first determination:

store the at least one data chunk in the archive storage as a portion of a user data backup; and

store remaining data chunks of the data chunks in the backup storage as a remaining portion of the user data backup, wherein the remaining portion of the user data backup does not comprise the portion of the user data backup, wherein the remaining data chunks do not comprise the at least one data chunk.

2. The system of claim 1 , wherein the archive value specifies a portion of a retention period associated with a protection policy after which unchanged data chunks may be stored in archival storage.

3. The system of claim 2 , wherein the archive value is one selected from a group consisting of:

a manual archive value, and

a default archive value.

4. The system of claim 2 , wherein obtaining the previously generated backup object metadata using the archive value comprises:

determining the portion of the retention period using the archive value and the retention period; and

obtaining previously generated backup object metadata generated during the portion of the retention period.

5. The system of claim 1 , wherein the backup object metadata comprises:

data chunk identifiers associated with the data chunks,

checksums associated with the data chunks, and

timestamps associated with the data chunks.

6. The system of claim 5 , wherein making the first determination comprises:

comparing the checksums of the backup object metadata associated with each data chunk with the checksums of the previously generated backup object metadata associated with each data chunk; and

identifying at least one data chunk associated with a checksum of the backup object metadata that matches all checksums of the previously generated backup object metadata associated with the at least one data chunk as the at least one data chunk.

7. The system of claim 1 , wherein a backup object metadata repository specifies storage locations associated with the data chunks.

8. The system of claim 1 , the manager is further programmed to:

prior to generating data chunks using the user data:

make a second determination that a protection policy is associated with a smart archive backup; and

in response to the second determination:

obtain user metadata associated with users;

make a third determination that the user metadata indicates at least one user is deleted; and

in response to the third determination:

move portions of user data backups associated with the at least one user from the backup storage to the archive storage.

9. A method for providing data protection services for user data generated by an application, the method comprising:

generating data chunks using the user data;

generating backup object metadata associated with the data chunks;

obtaining previously generated backup object metadata associated with the user data using an archive value;

making a first determination that at least one data chunk of the data chunks is to be archived using the backup object metadata and the previously generated backup object metadata; and

in response to the first determination:

storing the at least one data chunk in an archive storage as a portion of a user data backup; and

storing remaining data chunks of the data chunks in a backup storage as a remaining portion of the user data backup, wherein the remaining portion of the user data backup does not comprise the portion of the user data backup, wherein the remaining data chunks do not comprise the at least one data chunk.

10. The method of claim 9 , wherein the archive value specifies a portion of a retention period associated with a protection policy after which unchanged data chunks may be stored in archival storage.

11. The method of claim 10 , wherein the archive value is one selected from a group consisting of:

a manual archive value, and

a default archive value.

12. The method of claim 10 , wherein obtaining the previously generated backup object metadata using the archive value comprises:

determining the portion of the retention period using the archive value and the retention period; and

obtaining previously generated backup object metadata generated during the portion of the retention period.

13. The method of claim 9 , wherein the backup object metadata comprises:

data chunk identifiers associated with the data chunks,

checksums associated with the data chunks, and

timestamps associated with the data chunks.

14. The method of claim 13 , wherein making the first determination comprises:

comparing the checksums of the backup object metadata associated with each data chunk with the checksums of the previously generated backup object metadata associated with each data chunk; and

identifying at least one data chunk associated with a checksum of the backup object metadata that matches all checksums of the previously generated backup object metadata associated with the at least one data chunk as the at least one data chunk.

15. The method of claim 9 , wherein a backup object metadata repository specifies storage locations associated with the data chunks.

16. The method of claim 9 , wherein the method further comprises:

prior to generating data chunks using the user data:

making a second determination that a protection policy is associated with a smart archive backup; and

in response to the second determination:

obtaining user metadata associated with users;

making a third determination that the user metadata indicates at least one user is deleted; and

in response to the third determination:

moving portions of user data backups associated with the at least one user from the backup storage to the archive storage.

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 providing data protection services for user data generated by an application, the method comprising:

generating data chunks using the user data;

generating backup object metadata associated with the data chunks;

obtaining previously generated backup object metadata associated with the user data using an archive value;

making a first determination that at least one data chunk of the data chunks is to be archived using the backup object metadata and the previously generated backup object metadata; and

in response to the first determination:

storing the at least one data chunk in an archive storage as a portion of a user data backup; and

storing remaining data chunks of the data chunks in a backup storage as a remaining portion of the user data backup, wherein the remaining portion of the user data backup does not comprise the portion of the user data backup, wherein the remaining data chunks do not comprise the at least one data chunk.

18. The non-transitory computer readable medium of claim 17 , wherein the archive value specifies a portion of a retention period associated with a protection policy after which unchanged data chunks may be stored in archival storage.

19. The non-transitory computer readable medium of claim 18 , wherein the archive value is one selected from a group consisting of:

a manual archive value, and

a default archive value.

20. The non-transitory computer readable medium of claim 18 , wherein obtaining the previously generated backup object metadata using the archive value comprises:

determining the portion of the retention period using the archive value and the retention period; and

obtaining previously generated backup object metadata generated during the portion of the retention period.

Assignments (10)
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/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 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 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/0124 →
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/0280 →
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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 5, 2021
From: YADAV, SUNIL; CHOPRA, SHELESH; BEHERA, AMARENDRA; DETHE, TUSHAR; ARORA, HIMANSHU; SINGH, DEEPENDRA PRATAP; BHANUSHALI, JIGAR PREMJIBHAI; CHAUHAN, SAPNA; RAO, ANJANA; KAUSHAL, VIPIN KUMAR; CHITLOOR, RAVI VIJAYAKUMAR
To: EMC IP HOLDING COMPANY LLC
Reel/Frame 056139/0801 →