IP Library Granted Patent US 11,269,735
Granted Patent B2
US 11,269,735 · App. 16/805,272 · Granted Mar 8, 2022

Methods and systems for performing data backups

Inventors: Mahesh Reddy Appireddygari Venkataramana (Bangalore, IN); Shelesh Chopra (Bangalore, IN); Sunil Yadav (Bangalore, IN); Divyangana Sisodia (Gwalior, IN); Yagnavalkya Chennojwala (Bangalore, IN); Asif Khan (Bangalore, IN); Aneesh Kumar Gurindapalli (Vijayawada, IN)
Assignee: EMC IP Holding Company LLC
G06F11/1464G06F3/064G06F3/067G06F3/0619G06F3/0631G06F3/0659G06F3/0683G06F11/1451G06F11/1461G06F11/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 11,269,735
App. No.
16/805,272
Granted
Mar 8, 2022
Kind
B2
Abstract

A method for backing up a storage volume that includes receiving, by a volume manager, a block allocation table of a cloned storage volume backup, selecting a modification entry that comprises a volume offset for modified file data, obtaining a backup offset for the cloned storage volume backup based on the block allocation table and the volume offset, updating, based on the backup offset, the block allocation table to obtain an updated block allocation table, and sending the modified file data and the updated block allocation table to a backup server.

Claims (58)

1. A method for backing up a storage volume, comprising:

receiving, by a volume manager, a block allocation table of a cloned storage volume backup, wherein prior to receiving the block allocation table, the method comprises:

receiving a command to initiate backup of the storage volume; and

sending, in response to the command, a request to create the cloned storage volume backup to a backup server;

selecting a modification entry that comprises a volume offset for modified file data;

obtaining a backup offset for the cloned storage volume backup based on the block allocation table and the volume offset, wherein obtaining the backup offset comprises:

identifying, in the block allocation table, a file offset associated with the modified file data; and

identifying the backup offset based on the file offset and the modified file data;

updating, based on the backup offset, the block allocation table to obtain an updated block allocation table; and

sending the modified file data and the updated block allocation table to a backup server.

2. The method of claim 1 , wherein updating the block allocation table comprises:

updating a block entry, of the block allocation table, to reflect the modified file data, wherein the block entry is associated with the volume offset.

3. The method of claim 2 , wherein prior to obtaining the backup offset, the method further comprises:

making a determination that the block allocation table comprises the block entry, wherein the block entry is associated with a block of the cloned storage volume backup that comprises unmodified file data,

wherein the backup offset is obtained in response to the determination.

4. The method of claim 2 , wherein prior to obtaining the backup offset, the method further comprises:

making a determination that the block allocation table does not comprise the block entry; and

creating, based on the determination, the block entry in the block allocation table associated with the volume offset.

5. The method of claim 1 , wherein sending the modified file data and the updated block allocation table further comprises:

instructing the backup server to write the modified file data at the backup offset.

6. A non-transitory computer readable medium comprising instructions which, when executed by a computer processor, enables the computer processor to perform a method for backing up a storage volume, comprising:

receiving, by a volume manager, a block allocation table of a cloned storage volume backup, wherein prior to receiving the block allocation table, the method comprises:

receiving a command to initiate backup of the storage volume; and

sending, in response to the command, a request to create the cloned storage volume backup to a backup server;

selecting a modification entry that comprises a volume offset for modified file data;

obtaining a backup offset for the cloned storage volume backup, based on the block allocation table and the volume offset, wherein obtaining the backup offset comprises:

identifying, in the block allocation table, a file offset associated with the modified file data; and

identifying the backup offset based on the file offset and the modified file data;

updating the block allocation table, based on the backup offset, to obtain an updated block allocation table; and

sending the modified file data and the updated block allocation table to a backup server.

7. The non-transitory computer readable medium of claim 6 , wherein updating the block allocation table comprises:

updating a block entry, of the block allocation table, to reflect the modified file data, wherein the block entry is associated with the volume offset.

8. The non-transitory computer readable medium of claim 7 , wherein prior to obtaining the backup offset, the method further comprises:

making a determination that the block allocation table comprises the block entry, wherein the block entry is associated with a block of the cloned storage volume backup that comprises unmodified file data.

9. The non-transitory computer readable medium of claim 7 , wherein prior to obtaining the backup offset, the method further comprises:

making a determination that the block allocation table does not comprise the block entry; and

creating, based on the determination, the block entry in the block allocation table associated with the volume offset.

10. The non-transitory computer readable medium of claim 6 , wherein sending the modified file data and the updated block allocation table further comprises:

instructing the backup server to write the modified file data at the backup offset.

11. A storage server, comprising:

memory; and

a processor, wherein the processor is configured to perform a method backing up a storage volume, comprising:

receiving, by a volume manager, a block allocation table of a cloned storage volume backup, wherein prior to receiving the block allocation table, the method further comprises:

receiving a command to initiate backup of the storage volume; and

sending, in response to the command, a request to create the cloned storage volume backup to a backup server;

selecting a modification entry that comprises a volume offset for modified file data;

obtaining a backup offset for the cloned storage volume backup, based on the block allocation table and the volume offset, wherein obtaining the backup offset comprises:

identifying, in the block allocation table, a file offset associated with the modified file data; and

identifying the backup offset based on the file offset and the modified file data;

updating the block allocation table, based on the backup offset, to obtain an updated block allocation table; and

sending the modified file data and the updated block allocation table to a backup server.

12. The storage server of claim 11 , wherein updating the block allocation table comprises:

updating a block entry, of the block allocation table, to reflect the modified file data, wherein the block entry is associated with the volume offset.

13. The storage server of claim 12 , wherein prior to obtaining the backup offset, the method further comprises:

making a determination that the block allocation table comprises the block entry, wherein the block entry is associated with a block of the cloned storage volume backup that comprises unmodified file data.

14. The storage server of claim 12 , wherein prior to obtaining the backup offset, the method further comprises:

making a determination that the block allocation table does not comprise the block entry; and

creating, based on the determination, the block entry in the block allocation table associated with the volume offset.

Assignments (13)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (052851/0917) 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
Reel/Frame 060436/0509 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (052852/0022) 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
Reel/Frame 060436/0582 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (052851/0081) 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
Reel/Frame 060436/0441 →
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 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 AT REEL 052771 FRAME 0906 Recorded Nov 2, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
Reel/Frame 058001/0298 →
SECURITY INTEREST Recorded Jun 5, 2020
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 052852/0022 →
SECURITY INTEREST Recorded Jun 5, 2020
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC; THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 052851/0081 →
SECURITY INTEREST Recorded Jun 5, 2020
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 052851/0917 →
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 May 28, 2020
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 052771/0906 →
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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 4, 2020
From: APPIREDDYGARI VENKATARAMANA, MAHESH REDDY; CHOPRA, SHELESH; YADAV, SUNIL; SISODIA, DIVYANGANA; CHENNOJWALA, YAGNAVALKYA; KHAN, ASIF; GURINDAPALLI, ANEESH KUMAR
To: EMC IP HOLDING COMPANY LLC
Reel/Frame 052012/0974 →
Continuity (1)
Related Publication 20210271563A1 · Sep 2, 2021