Tagging data for automatic transfer during backups
AssigneeRubrik, Inc.
InventorLooi Chow Lee
Life of this patent
Estimating the term…
Abstract
In one approach, data blocks or files that have a history of change are tagged for automatic transfer to backup on the assumption that they have changed since the last backup. Other data blocks and files are first tested for change, for example by comparing digital fingerprints of the current data versus the previously backed up data, before transferring to backup.
Claims23
In a data management and storage (DMS) system, a method for pulling a snapshot of a fileset from a compute infrastructure serviced by the DMS system, the method comprising:
- determining whether a data block in the fileset is currently tagged or not tagged by the DMS system for automatic transfer, wherein whether the data block is tagged or not tagged is based on an analysis by the DMS system of a change history of a portion of the fileset relating to the data block;
- if the data block is not currently tagged for automatic transfer, then:
- transferring a digital fingerprint of the previous snapshot of the data block to the compute infrastructure;
- causing the compute infrastructure to calculate a digital fingerprint of the data block and to determine whether the digital fingerprints of the data block and of the previous snapshot are the same;
- and
- if the digital fingerprints are not the same, then transferring the data block from the compute infrastructure to the DMS system but, if the digital fingerprints are the same, then not transferring the data block.
A data management and storage (DMS) cluster comprising:
- a plurality of peer DMS nodes that autonomously service a compute infrastructure;
- a DMS database implemented across the peer DMS nodes;
- a distributed data store implemented across the peer DMS nodes;
- wherein each of the peer DMS nodes includes a software stack for, in response to a job of pulling a snapshot of a fileset:
- determining whether a data block in the fileset is currently tagged oby the DMS system for automatic transfer, wherein whether the data block is tagged depends on the DMS system's analysis of a change history of a portion of the fileset relating to the data block or not tagged
- if the data block is not currently tagged for automatic transfer, then:
- transferring a digital fingerprint of the previous snapshot of the data block to the compute infrastructure;
- causing the compute infrastructure to calculate a digital fingerprint of the data block and to determine whether the digital fingerprints of the data block and of the previous snapshot are the same;
- and
- if the digital fingerprints are not the same, then transferring the data block from the compute infrastructure to the DMS system but, if the digital fingerprints are the same, then not transferring the data block.
A non-transitory computer-readable medium comprising instructions that when executed by a processor cause the processor to execute a method for pulling a snapshot of a fileset of a compute infrastructure serviced by a DMS system, the method comprising:
- determining whether a data block in the fileset is currently tagged by DMS system for automatic transfer, wherein whether the data block is tagged depends on the DMS system's analysis of a change history of a portion of the fileset relating to the data block;
- if the data block is not currently tagged for automatic transfer, then:
- transferring a digital fingerprint of the previous snapshot of the data block to the compute infrastructure;
- causing the compute infrastructure to calculate a digital fingerprint of the data block and to determine whether the digital fingerprints of the data block and of the previous snapshot are the same;
- and
- if the digital fingerprints are not the same, then transferring the data block from the compute infrastructure to the DMS system but, if the digital fingerprints are the same, then not transferring the data block.
Dependencies are inferred from the claim text.