Systems and methods for performing data backups using a persistent cache

Patent metadata

Field	Value
Publication number	US-12339746-B2
Application number	US-202318480786-A
Country	US
Kind code	B2
Filing date	Oct 4, 2023
Priority date	Oct 4, 2023
Publication date	Jun 24, 2025
Grant date	Jun 24, 2025

Abstract

Disclosed herein are systems and method for performing data backups using a persistent cache. A method may include storing at least one archive metadata page of a plurality of archive metadata pages in a local persistent cache, wherein the archive metadata pages are associated with a plurality of files backed up from a local storage volume of the computing device to an archive; detecting that a file of the plurality of files is modified on the local storage volume; performing an incremental backup of the modified file, by: determining whether an archive metadata page of the modified file is stored in the persistent cache, in response to determining that the archive metadata page of the modified file is comprised in the at least one archive metadata page, retrieving the archive metadata page from the persistent cache; and executing the incremental backup of the modified file using the archive metadata page.

First claim

The invention claimed is:

1. A method for performing data backups using a persistent cache, the method comprising:
generating a persistent cache in a volume of a computing device and setting a maximum size of the persistent cache;
storing at least one archive metadata page of a plurality of archive metadata pages in the persistent cache, wherein the plurality of archive metadata pages are associated with a plurality of files backed up from a local storage volume of the computing device to an archive;
detecting that a file of the plurality of files is modified on the local storage volume;
performing an incremental backup of the modified file, by:
determining whether an archive metadata page of the modified file is stored in the persistent cache;
in response to determining that the archive metadata page of the modified file is comprised in the at least one archive metadata page, retrieving the archive metadata page from the persistent cache; and
executing the incremental backup of the modified file using information in the archive metadata page;

detecting that the maximum size is reached subsequent to storing the at least one archive metadata page; and
in response to detecting that the maximum size is reached, identifying at least one different archive metadata page in the persistent cache that has not been accessed for at least a threshold period of time, and removing the at least one different archive metadata page from the persistent cache.

2. The method of claim 1 , wherein the plurality of archive metadata pages include information indicating a list of recovery points in the archive, a list of files in each recovery point, a list of parts in each file, and respective locations of the parts in the archive.

3. The method of claim 1 , wherein the information in the archive metadata page indicates a recovery point in the archive comprising parts of an original version of the modified file and locations of the parts in the archive, further comprising:
identifying the locations indicated in the archive metadata page; and
uploading parts of the modified file to the locations.

4. The method of claim 1 , further comprising:
in response to determining that the archive metadata page of the modified file is not comprised in the at least one archive metadata page, retrieving the archive metadata page from the plurality of archive metadata pages stored in the archive; and
writing the archive metadata page to the persistent cache.

5. The method of claim 1 , wherein the volume is resizable, further comprising:
setting a size of the persistent cache to a percentage of a size of the volume; and
adjusting the size of the persistent storage in response to detecting a change in the size of the volume.

6. The method of claim 5 , wherein the adjusting is proportional to the change in the size of the volume.

7. A system for performing data backups using a persistent cache, comprising: at least one memory;
at least one hardware processor coupled with the at least one memory and configured, individually or in combination, to:
generate a persistent cache in a volume of a computing device and setting a maximum size of the persistent cache;
store at least one archive metadata page of a plurality of archive metadata pages in the persistent cache, wherein the plurality of archive metadata pages are associated with a plurality of files backed up from a local storage volume of the computing device to an archive;
detect that a file of the plurality of files is modified on the local storage volume;
perform an incremental backup of the modified file, by:
determining whether an archive metadata page of the modified file is stored in the persistent cache;
in response to determining that the archive metadata page of the modified file is comprised in the at least one archive metadata page, retrieving the archive metadata page from the persistent cache; and
executing the incremental backup of the modified file using information in the archive metadata page;

detecting that the maximum size is reached subsequent to storing the at least one archive metadata page; and
in response to detecting that the maximum size is reached, identifying at least one different archive metadata page in the persistent cache that has not been accessed for at least a threshold period of time, and removing the at least one different archive metadata page from the persistent cache.

8. The system of claim 7 , wherein the plurality of archive metadata pages include information indicating a list of recovery points in the archive, a list of files in each recovery point, a list of parts in each file, and respective locations of the parts in the archive.

9. The system of claim 7 , wherein the information in the archive metadata page indicates a recovery point in the archive comprising parts of an original version of the modified file and locations of the parts in the archive, and wherein the at least one hardware processor is configured to:
identify the locations indicated in the archive metadata page; and
upload parts of the modified file to the locations.

10. The system of claim 7 , wherein the at least one hardware processor is configured to:
in response to determining that the archive metadata page of the modified file is not comprised in the at least one archive metadata page, retrieve the archive metadata page from the plurality of archive metadata pages stored in the archive; and
write the archive metadata page to the persistent cache.

11. The system of claim 7 , wherein the volume is resizable, wherein the at least one hardware processor is configured to:
set a size of the persistent cache to a percentage of a size of the volume; and
adjust the size of the persistent storage in response to detecting a change in the size of the volume.

12. The system of claim 11 , wherein the adjusting is proportional to the change in the size of the volume.

13. A non-transitory computer readable medium storing thereon computer executable instructions for performing data backups using a persistent cache, including instructions for:
generating a persistent cache in a volume of a computing device and setting a maximum size of the persistent cache;
storing at least one archive metadata page of a plurality of archive metadata pages in the persistent cache, wherein the plurality of archive metadata pages are associated with a plurality of files backed up from a local storage volume of the computing device to an archive;
detecting that a file of the plurality of files is modified on the local storage volume;
performing an incremental backup of the modified file, by:
determining whether an archive metadata page of the modified file is stored in the persistent cache;
in response to determining that the archive metadata page of the modified file is comprised in the at least one archive metadata page, retrieving the archive metadata page from the persistent cache; and
executing the incremental backup of the modified file using information in the archive metadata page;

detecting that the maximum size is reached subsequent to storing the at least one archive metadata page; and
in response to detecting that the maximum size is reached, identifying at least one different archive metadata page in the persistent cache that has not been accessed for at least a threshold period of time, and removing the at least one different archive metadata page from the persistent cache.

14. The non-transitory computer readable medium of claim 13 , wherein the plurality of archive metadata pages include information indicating a list of recovery points in the archive, a list of files in ea

Assignees

• Acronis Int Gmbh

Inventors

• Kuleshov Andrey
• Per Yuri
• Bell Serg
• Protsaov Stanislav

Classifications

• G06F16/113

  Details of archiving (lifecycle management in storage systems G06F3/0649; point-in-time backing up or restoration of persistent data G06F11/1446) · CPC title

• G06F16/172

  Caching, prefetching or hoarding of files · CPC title

• G06F16/166 Primary

  File name conversion · CPC title

• G06F11/1451 Primary

  by selection of backup contents · CPC title