Skipping data backed up in prior backup operations

US11669261B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11669261-B2
Application numberUS-202117445712-A
CountryUS
Kind codeB2
Filing dateAug 23, 2021
Priority dateMar 11, 2019
Publication dateJun 6, 2023
Grant dateJun 6, 2023

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Certain embodiments described herein relate to an improved selective data backup system. In some embodiments, one or more components in an information management system can determine that a portion of the primary data scheduled for backup was previously backed up or is scheduled to be backed up as part of another backup operation. For example, a data agent performing a cluster-level backup operation for an entire cluster of storage servers may check whether any part of the primary data was previously backed up by a prior server-level backup operation for one of the storage servers in the cluster. If so, the data agent may skip, in the cluster-level backup operation, any portion of the primary data stored in the storage server previously backed up as part of the prior server-level backup operation.

First claim

Opening claim text (preview).

What is claimed is: 1. A computer-implemented method comprising: receiving a request to initiate a first backup operation, wherein the first backup operation is configured to use a first type of data agent to create a backup copy of first primary data; determining, based on a mapping table indicative of one or more other backup operations, that a portion of the first primary data to be backed up as part of the first backup operation was previously backed up as part of a second backup operation of second primary data, wherein the second backup operation used a second type of data agent to back up the second primary data, wherein the first type of data agent is configured to protect the first primary data, and wherein the second type of data agent is distinct from the first type of data agent and is configured to protect the second primary data, which includes the portion of the first primary data; filtering the first primary data to exclude the portion of the first primary data that was previously backed up as part of the second backup operation; based on the filtering, excluding from the first backup operation the portion of the first primary data that was previously backed up as part of the second backup operation; and updating the mapping table to reflect the first backup operation. 2. The method of claim 1 , wherein the first primary data meets a first backup condition, wherein the second primary data meets a second backup condition, and wherein the first primary data includes at least some data that does not meet the second backup condition; wherein data meeting the first backup condition includes all data within one or more clusters of storage servers associated with the first backup operation, and data meeting the second backup condition includes all data within one or more storage servers associated with the second backup operation. 3. The method of claim 1 , wherein the first primary data meets a first backup condition, wherein the second primary data meets a second backup condition, and wherein the first primary data includes at least some data that does not meet the second backup condition; wherein data meeting the first backup condition includes all data associated with one or more software applications associated with the first backup operation, and data meeting the second backup condition includes all data in one or more file systems associated with the second backup operation. 4. The method of claim 1 , wherein the first primary data meets a first backup condition, wherein the second primary data meets a second backup condition, and wherein the first primary data includes at least some data that does not meet the second backup condition; wherein data meeting the second backup condition includes all data within one or more clusters of storage servers associated with the second backup operation, and data meeting the first backup condition includes all data within one or more storage servers associated with the first backup operation. 5. The method of claim 1 , wherein the first primary data meets a first backup condition, wherein the second primary data meets a second backup condition, and wherein the first primary data includes at least some data that does not meet the second backup condition; wherein data meeting the second backup condition includes all data associated with one or more software applications associated with the second backup operation, and data meeting the first backup condition includes all data in one or more file systems associated with the first backup operation. 6. The method of claim 1 , wherein updating the mapping table comprises modifying the mapping table such that the modified mapping table indicates that at least some primary data that was not backed up as part of the second backup operation has been backed up. 7. The method of claim 1 , wherein both of the first backup operation and the second backup operation are performed using a same data transfer protocol. 8. The method of claim 1 , further comprising: determining, based on the mapping table, that another portion of the first primary data was previously backed up as part of a third backup operation configured to create a copy of primary data meeting a third backup condition; and filtering the primary data to exclude said another portion of the primary data that was previously backed up as part of the third backup operation. 9. The method of claim 8 , wherein each of the first backup operation, and the second backup operation, and the third backup operation is a different one of (i) a cluster-level backup operation configured to back up data within one or more clusters of storage servers, (ii) a server-level backup operation configured to back up data within one or more storage servers, (iii) a file-system-level backup operation configured to back up data within one or more file systems, or (iv) an application-level backup operation configured to back up data generated by one or more applications. 10. The method of claim 1 , wherein the first primary data comprises a file generated by an application, and wherein the first type of data agent is associated with the application; wherein the second primary data comprises data stored at a file server, and wherein the second type of data agent is associated with the file server; wherein the file generated by the application is stored at the file server; and wherein the portion comprises the file. 11. The method of claim 1 , wherein the first backup operation comprises an application-level backup of an application that generates a file that is stored in a file system; wherein the second backup operation comprises a file-system-backup of at least part of the file system comprising the file; and wherein the portion comprises the file. 12. A non-transitory computer-readable medium comprising instructions that, when executed by a computing device comprising one or more hardware processors and computer memory, cause the computing device to perform operations comprising: receiving a request to initiate a first backup operation, wherein the first backup operation is configured to use a first data agent of a first type to create a backup copy of first primary data; determining, based on a mapping table indicative of one or more other backup operations, that a portion of the first primary data to be backed up as part of the first backup operation was previously backed up as part of a second backup operation of second primary data, wherein the second backup operation used a second data agent of a second type to back up the second primary data, wherein the first type of data agent is configured to protect the first primary data, and wherein the second type of data agent is distinct from the first type of data agent and is configured to protect the second primary data, which includes the portion of the first primary data; filtering the first primary data to exclude the portion of the first primary data that was previously backed up as part of the second backup operation; based on the filtering, excluding from the first backup operation the portion of the first primary data that was previously backed up as part of the second backup operation; and updating the mapping table to reflect the first backup operation. 13. The non-transitory computer-readable medium of claim 12 , wherein each of the first backup operation and the second backup operation is a different one of (i) a cluster-level backup operation configured to back up data within one or more clusters of storage servers, (ii) a server-level backup operation configured to back up data within one or more storage servers, (iii) a file-system-level backup operation configured to ba

Assignees

Inventors

Classifications

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US11669261B2 cover?
Certain embodiments described herein relate to an improved selective data backup system. In some embodiments, one or more components in an information management system can determine that a portion of the primary data scheduled for backup was previously backed up or is scheduled to be backed up as part of another backup operation. For example, a data agent performing a cluster-level backup oper…
Who is the assignee on this patent?
Commvault Systems Inc
What technology area does this patent fall under?
Primary CPC classification G06F11/1451. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Jun 06 2023 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 12 related publications on this page (citations in our corpus or others sharing the same primary CPC).