IP Library Granted Patent US 12,632,339
Granted Patent B2
US 12,632,339 · App. 18/478,242 · Granted May 19, 2026

Performing incremental indexing of image backups

Inventors: Sunil Yadav (Bangalore, IN); Shelesh Chopra (Bangalore, IN)
Assignee: Dell Products L.P.
G06F11/1435G06F11/1451G06F11/1464
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 12,632,339
App. No.
18/478,242
Granted
May 19, 2026
Kind
B2
Abstract

Techniques described herein relate to a method for performing backups of virtual machines on a host. The method includes obtaining an incremental image backup generation request associated with a virtual machine (VM) of the host; obtaining current file system metadata associated with the VM; obtaining previous backup metadata associated with the VM; generating updated file system metadata that includes status indicators associated with each file by comparing the current file system metadata with the previous backup metadata; obtaining a list of changed data blocks associated with the VM; writing changed data blocks associated with the VM to a backup storage; generating incremental backup metadata by associating portions of the updated file system metadata with each changed data block in the list of the changed data blocks; and writing the incremental backup metadata with the changed data blocks in the backup storage.

Claims (74)

1 . A method for performing backups of virtual machines on a host, comprising:

obtaining, by a data protection agent of the host, an incremental image backup generation request associated with a virtual machine (VM) of the host from a data protection manager;

in response to obtaining the incremental image backup generation request:

obtaining current file system metadata associated with the VM from a file system metadata repository stored on a storage of the host, wherein for each file of the system repository, the current file system metadata comprises:

a current file identifier associated with the file;

a current file size associated with the file;

a current VM identifier associated with the file;

a current parent file identifier associated with the file; and

at least one current data run associated with the file;

obtaining previous backup metadata associated with the previous backup of the VM, wherein for each file of the system repository, the previous backup metadata comprises:

a previous file identifier associated with the file;

a previous file size associated with the file;

a previous VM identifier associated with the file;

a previous parent file identifier associated with the file; and

at least one previous data run associated with the file;

generating updated file system metadata that includes status indicators associated with each file in the current file system by comparing the at least one current data run associated with the file of the current file system metadata with at least one previous data run associated with the file of the previous backup metadata, wherein the status indicators specify whether a file is new, modified, deleted, or unmodified since the previous backup was generated;

obtaining a list of changed data blocks associated with the VM;

writing changed data blocks included in a storage volume associated with the VM to a backup storage using the updated file system metadata;

generating incremental backup metadata by associating portions of the updated file system metadata with each changed data block in the list of the changed data blocks; and

writing the incremental backup metadata with the changed data blocks in the backup storage to generate an incremental image backup, wherein the incremental backup metadata is used to perform indexing of the changed data blocks.

2 . The method of claim 1 , wherein the host comprises a Hyper-V hypervisor.

3 . The method of claim 1 , wherein the previous backup metadata comprises file system metadata associated with a point in time that the previous backup was generated.

4 . The method of claim 1 , wherein the previous backup comprises one selected from a group consisting of:

a full image backup; and

a virtual synthetic full image backup.

5 . 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 performing backups of virtual machines on a host, the method comprising:

obtaining, by a data protection agent of the host, an incremental image backup generation request associated with a virtual machine (VM) of the host from a data protection manager;

in response to obtaining the incremental image backup generation request:

obtaining current file system metadata associated with the VM from a file system metadata repository stored on a storage of the host, wherein for each file of the system repository, the current file system metadata comprises:

a current file identifier associated with the file;

a current file size associated with the file;

a current VM identifier associated with the file;

a current parent file identifier associated with the file; and

at least one current data run associated with the file;

obtaining previous backup metadata associated with the previous backup of the VM, wherein for each file of the system repository, the previous backup metadata comprises:

a previous file identifier associated with the file;

a previous file size associated with the file;

a previous VM identifier associated with the file;

a previous parent file identifier associated with the file; and

at least one previous data run associated with the file;

generating updated file system metadata that includes status indicators associated with each file in the current file system by comparing the at least one current data run associated with the file of the current file system metadata with at least one previous data run associated with the file of the previous backup metadata, wherein the status indicators specify whether a file is new, modified, deleted, or unmodified since the previous backup was generated;

obtaining a list of changed data blocks associated with the VM;

writing changed data blocks included in a storage volume associated with the VM to a backup storage using the updated file system metadata;

generating incremental backup metadata by associating portions of the updated file system metadata with each changed data block in the list of the changed data blocks; and

writing the incremental backup metadata with the changed data blocks in the backup storage to generate an incremental image backup, wherein the incremental backup metadata is used to perform indexing of the changed data blocks.

6 . The non-transitory computer readable medium of claim 5 , wherein the host comprises a Hyper-V hypervisor.

7 . The non-transitory computer readable medium of claim 5 , wherein the previous backup metadata comprises file system metadata associated with a point in time that the previous backup was generated.

8 . The non-transitory computer readable medium of claim 5 , wherein the previous backup comprises one selected from a group consisting of:

a full image backup; and

a virtual synthetic full image backup.

9 . A system for performing backups of virtual machines on a host, comprising:

a host; and

a data protection agent of the host, comprising a processor and memory, which when executed by the processor performs a method comprising:

obtaining, by the data protection agent, an incremental image backup generation request associated with a virtual machine (VM) of the host from a data protection manager;

in response to obtaining the incremental image backup generation request:

obtaining current file system metadata associated with the VM from a file system metadata repository stored on a storage of the host, wherein for each file of the system repository, the current file system metadata comprises:

a current file identifier associated with the file;

a current file size associated with the file;

a current VM identifier associated with the file;

a current parent file identifier associated with the file; and

at least one current data run associated with the file;

obtaining previous backup metadata associated with the previous backup of the VM, wherein for each file of the system repository, the previous backup metadata comprises:

a previous file identifier associated with the file;

a previous file size associated with the file;

a previous VM identifier associated with the file;

a previous parent file identifier associated with the file; and

at least one previous data run associated with the file;

generating updated file system metadata that includes status indicators associated with each file in the current file system by comparing the at least one current data run associated with the file of the current file system metadata with at least one previous data run associated with the file of the previous backup metadata, wherein the status indicators specify whether a file is new, modified, deleted, or unmodified since the previous backup was generated;

obtaining a list of changed data blocks associated with the VM;

writing changed data blocks included in a storage volume associated with the VM to a backup storage using the updated file system metadata;

generating incremental backup metadata by associating portions of the updated file system metadata with each changed data block in the list of the changed data blocks; and

writing the incremental backup metadata with the changed data blocks in the backup storage to generate an incremental image backup, wherein the incremental backup metadata is used to perform indexing of the changed data blocks.

10 . The system of claim 9 , wherein the host comprises a Hyper-V hypervisor.

11 . The system of claim 9 , wherein the previous backup metadata comprises file system metadata associated with a point in time that the previous backup was generated.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 29, 2023
From: YADAV, SUNIL; CHOPRA, SHELESH
To: DELL PRODUCTS L.P.
Reel/Frame 065079/0303 →
Continuity (1)
Related Publication 20250110832A1 · Apr 3, 2025
References Cited (38)
US 9354907B1 · Teli · 2016 [cited by applicant]
US 9424136B1 · Teater et al. · 2016 [cited by applicant]
US 9569446B1 · Feathergill et al. · 2017 [cited by applicant]
US 10310949B1 · Chakraborty · 2019 [cited by applicant]
US 10387381B1 · Patwardhan · 2019 [cited by applicant]
US 10417099B1 · Yadav · 2019 [cited by applicant]
US 10664357B1 · Mallik · 2020 [cited by examiner]
US 10810089B1 · Gu et al. · 2020 [cited by applicant]
US 11042450B2 · Kang · 2021 [cited by applicant]
US 11397650B1 · Palaiah · 2022 [cited by applicant]
US 20140214899A1 · Ganapathy · 2014 [cited by applicant]
US 20150293817A1 · Subramanian · 2015 [cited by applicant]
US 20160019317A1 · Pawar · 2016 [cited by applicant]
US 20160070621A1 · Bushman · 2016 [cited by applicant]
US 20160292047A1 · Bender · 2016 [cited by applicant]
US 20170185488A1 · Kumarasamy et al. · 2017 [cited by applicant]
US 20180075166A1 · Pawar et al. · 2018 [cited by applicant]
US 20180255102A1 · Ward et al. · 2018 [cited by applicant]
US 20180349407A1 · Cisler · 2018 [cited by applicant]
US 20210406130A1 · Jorapur · 2021 [cited by examiner]
US 20220043717A1 · Yadav · 2022 [cited by applicant]
US 20220083426A1 · Chopra · 2022 [cited by examiner]
US 20220237071A1 · Wong · 2022 [cited by examiner]
US 20220245035A1 · Minarik et al. · 2022 [cited by applicant]
US 20220292196A1 · Bhagi · 2022 [cited by applicant]
US 20220318118A1 · Adamson et al. · 2022 [cited by applicant]
US 20220342770A1 · Jagannatha · 2022 [cited by applicant]
US 20220358215A1 · Shachar et al. · 2022 [cited by applicant]
US 20220374519A1 · Botelho et al. · 2022 [cited by applicant]
US 20220382641A1 · Chopra et al. · 2022 [cited by applicant]
US 20220398160A1 · Zou · 2022 [cited by applicant]
US 20220398221A1 · Zou · 2022 [cited by applicant]
US 20230141909A1 · Truscott et al. · 2023 [cited by applicant]
US 20230168970A1 · Pradhan · 2023 [cited by applicant]
US 20230297477A1 · Yadav et al. · 2023 [cited by applicant]
US 20240070034A1 · Bell et al. · 2024 [cited by applicant]
US 20240070321A1 · Minarik et al. · 2024 [cited by applicant]
US 20250023909A1 · Kumar et al. · 2025 [cited by applicant]