IP Library Granted Patent US 10,795,588
Granted Patent B1
US 10,795,588 · App. 15/192,841 · Granted Oct 6, 2020

Check point recovery based on identifying used blocks for block-based backup files

Inventors: Rangapuram Ravi Kishore Yadav (Bangalore, IN); Pavan Kumar Dattatreya Ati (Bangalore, IN); Sridhar Surampudi (Rajahmundry, IN)
Assignee: EMC IP HOLDING COMPANY LLC
G06F3/0619G06F3/064G06F3/067
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,795,588
App. No.
15/192,841
Granted
Oct 6, 2020
Kind
B1
Abstract

Check point recovery based on identifying used blocks for block-based backup files is described. At least one data block is identified that is used by a system since a point in time in response to receiving a request to restore the system based on the point in time. At least one data block, corresponding to the identified at least one data block, is recovered from at least one backup file for the system, without reading each data block backed up via the at least one backup file for the system. The system is restored based on the recovered at least one data block.

Claims (41)

1. A system for check point recovery based on identifying used blocks for block-based backup files of a volume, the system comprising:

a processor; and

a processor-based application, which when executed on a computer, will cause the processor to:

receive a request to restore the volume that was backed up at a user specified time;

initialize a vector for payload blocks to be recovered;

identify, in response to the receiving the request to restore the volume, data blocks within a plurality of backup files of the volume that were being used at the user specified time and data blocks that were unused at the user specified time, the identifying being performed using a disk layout files that lists used and unused data blocks within the corresponding backup files, the unused blocks having been deleted before the user specified time, the plurality of backup files includes a full backup file and a plurality of corresponding incremental backup files;

assign to the initialized vector the payload blocks that store the identified used data blocks in the plurality of backup files;

assign each of the backup files that store the payload blocks to a backup list;

recover only the data blocks that were being used at the user specified time as identified from the disk layout file by: (i) identifying the used data blocks stored in each of the incremental backup files, (ii) appending the payload blocks that store identified used data blocks to the initialized vector, and (iii) creating a merged file based on the backup files in the backup list for each payload block in the vector, the recovering being performed without reading each data block backed up via the at least one backup file for the system; and

restore the volume by restoring only the used data blocks within the merged file that were being used at the user specified time as identified from the disk layout file.

2. The system of claim 1 , wherein the identifying the data blocks further comprises identifying a data block backed up via a first sequential backup file of the at least one backup file for the system, identifying a data block backed up via a last sequential backup file of the at least one backup file for the system, and identifying a data block backed up via any sequential backup file, of the at least one backup file for the system, that is between the first sequential backup file and the last sequential backup file.

3. The system of claim 1 , wherein the identifying the data blocks further comprises reading a block map.

4. The system of claim 3 , wherein the block map comprises a bitmap that specifies whether each data block in a group of data blocks is one of used at the user specified time and unused at the user specified time.

5. The system of claim 1 , wherein the recovering without reading each data block backed up via the at least one backup file for the system comprises bypassing reading each data block that corresponds to any data block that is identified as unused by the system since the user specified time.

6. A computer-implemented method for check point recovery based on identifying used blocks for block-based backup files of a volume, the method comprising:

receiving a request to restore the volume that was backed up at a user specified time;

initializing a vector for payload blocks to be recovered;

identifying, in response to the receiving the request to restore the volume, data blocks within a plurality of backup files of the volume that were being used at the user specified time and data blocks that were unused at the user specified time, the identifying being performed using a disk layout files that lists used and unused data blocks within the corresponding backup files, the unused blocks having been deleted before the user specified time, the plurality of backup files includes a full backup file and a plurality of corresponding incremental backup files;

assigning to the initialized vector the payload blocks that store the identified used data blocks in the plurality of backup files;

assigning each of the backup files that store the payload blocks to a backup list;

recovering only the data blocks that were being used at the user specified time as identified from the disk layout file by: (i) identifying the used data blocks stored in each of the incremental backup files, (ii) appending the payload blocks that store identified used data blocks to the initialized vector, and (iii) creating a merged file based on the backup files in the backup list for each payload block in the vector, the recovering being performed without reading each data block backed up via the at least one backup file for the system; and

restoring the volume by restoring only the used data blocks within the merged file that were being used at the user specified time as identified from the disk layout file.

7. The method of claim 6 , wherein identifying the at least one data block comprises using the disk layout file to identify a data block that is used by the system since the user specified time.

8. The method of claim 6 , wherein the identifying the data blocks further comprises identifying a data block backed up via a first sequential backup file of the at least one backup file for the system, identifying a data block backed up via a last sequential backup file of the at least one backup file for the system, and identifying a data block backed up via any sequential backup file, of the at least one backup file for the system, that is between the first sequential backup file and the last sequential backup file.

9. The method of claim 6 , wherein the identifying the data blocks further comprises reading a block map.

10. The method of claim 9 , wherein the block map comprises a bitmap that specifies whether each data block in a group of data blocks is one of used at the user specified time and unused at the user specified time.

11. The method of claim 6 , wherein the point in time is associated with a backup file, of the at least one backup of the system, that sequentially precedes a use of the at least one data block that is used by the system since the user specified time.

12. The method of claim 6 , wherein the recovering without reading each data block backed up via the at least one backup file for the system, comprises bypassing reading each data block that corresponds to any data block that is identified as unused by the system since the user specified time.

13. A computer program product, comprising a non-transitory computer-readable medium having a computer-readable program code embodied therein to be executed by one or more processors, the program code including instructions to:

receive a request to restore the volume that was backed up at a user specified time;

initialize a vector for payload blocks to be recovered;

identify, in response to the receiving the request to restore the volume, data blocks within a plurality of backup files of the volume that were being used at the user specified time and data blocks that were unused at the user specified time, the identifying being performed using a disk layout files that lists used and unused data blocks within the corresponding backup files, the unused blocks having been deleted before the user specified time, the plurality of backup files includes a full backup file and a plurality of corresponding incremental backup files;

assign the payload blocks that store the identified used data blocks in the plurality of backup files to the initialized vector;

assign each of the backup files that store the payload blocks to a backup list;

recover only the data blocks that were being used at the user specified time as identified from the disk layout file by: (i) identifying the used data blocks stored in each of the incremental backup files, (ii) appending the payload blocks that store identified used data blocks to the initialized vector, and (iii) creating a merged file based on the backup files in the backup list for each payload block in the vector, the recovering being performed without reading each data block backed up via the at least one backup file for the system; and

restore the volume by restoring only the at used data blocks within the merged file that were being used at the user specified time as identified from the disk layout file.

14. The computer program product of claim 13 , wherein identifying the at least one data block comprises using the disk layout file to identify a data block that is used by the system since the user specified time.

15. The computer program product of claim 13 , wherein the identifying the data blocks further comprises identifying a data block backed up via a first sequential backup file of the at least one backup file for the system, identifying a data block backed up via a last sequential backup file of the at least one backup file for the system, and identifying a data block backed up via any sequential backup file, of the at least one backup file for the system, that is between the first sequential backup file and the last sequential backup file.

16. The computer program product of claim 13 , wherein the identifying the data blocks further comprises reading a block map, and wherein the block map comprises a bitmap that specifies whether each data block in a group of data blocks is one of used at the user specified time and unused at the user specified time.

17. The computer program product of claim 13 , wherein the point in time is associated with a backup file, of the at least one backup of the system, that sequentially precedes a use of the at least one data block that is used by the system since the user specified time.

18. The computer program product of claim 13 , wherein the recovering without reading each data block backed up via the at least one backup file for the system, comprises bypassing reading each data block that corresponds to any data block that is identified as unused by the system since the user specified time.

Assignments (5)
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 →
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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 3, 2017
From: EMC CORPORATION
To: EMC IP HOLDING COMPANY LLC
Reel/Frame 041872/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 18, 2016
From: YADAV, RANGAPURAM RAVI KISHORE; ATI, PAVAN KUMAR DATTATREYA; SURAMPUDI, SRIDHAR
To: EMC CORPORATION
Reel/Frame 039179/0659 →
Cited By (2)
US 12,333,185 US 12,407,651