# US 2019/0317862 A1 · Tagging data for automatic transfer during backups

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0317862 A1
- Document ID: US20190317862A1
- Status: Published application
- Kind: A1
- Application number: 16/453,234
- Filed: 2019-06-26
- Published: 2019-10-17
- Earliest claimed: 2017-12-23
- Assignees: Rubrik, Inc.
- Applicants: Rubrik, Inc.
- Inventors: Looi Chow Lee
- Web page: https://patentgrep.com/patent/US20190317862A1

## CPC

- G06F 11/1451: {by selection of backup contents}
- G06F 3/0608: {Saving storage space on storage systems}
- G06F 3/0613: {in relation to throughput}
- G06F 3/064: {Management of blocks}
- G06F 3/0641: {De-duplication techniques}
- G06F 3/065: {Replication mechanisms}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 11/1446: Point-in-time backing up or restoration of persistent data
- G06F 11/1464: {for networked environments}
- G06F 11/167: {Error detection by comparing the memory output}
- G06F 16/128: {Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion (error detection or correction of the data by redundancy in operations or in hardware G06F11/14, G06F11/16)}
- G06F 11/1461: {Backup scheduling policy}
- G06F 2201/815: Virtual
- G06F 2201/83: the solution involving signatures
- G06F 2201/84: Using snapshots, i.e. a logical point-in-time copy of the data
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## 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.

## Claims

### Claim 1

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.

### Claim 2 (depends on 1)

The method of claim 1, wherein if the data block is currently tagged for automatic transfer, then transferring the data block from the compute infrastructure to the DMS system without first determining whether the data block is the same as a previous snapshot of the data block already stored in the DMS system.

### Claim 3 (depends on 1)

The method of claim 1, wherein whether the data block is tagged or not tagged is based on an analysis by the DMS system of a change history of the data block itself.

### Claim 4 (depends on 1)

The method of claim 1, wherein the data block is part of a file, and whether the data block is tagged or not tagged is based on an analysis by the DMS system of a change history of the file.

### Claim 5 (depends on 4)

The method of claim 4, wherein whether the data block is tagged or not tagged is based on an analysis by the DMS system of a change history of other data blocks contained in the file.

### Claim 6 (depends on 1)

The method of claim 1, wherein the data block is part of a file, and all data blocks in the file are tagged the same or similarly.

### Claim 7 (depends on 1)

The method of claim 1, wherein the data block is part of a file, and different data blocks in the file are tagged differently.

### Claim 8 (depends on 1)

The method of claim 1, wherein the data block is part of a file, and whether the data block is tagged or not tagged is further based on a file type of the file.

### Claim 9 (depends on 1)

The method of claim 1, wherein the data block is part of a file, and whether the data block is tagged or not tagged is further based on a file extension of the file.

### Claim 10 (depends on 1)

The method of claim 1, wherein the data block is part of a file, and whether the data block is tagged or not tagged is further based on contents of the file.

### Claim 11 (depends on 1)

The method of claim 1, wherein the data block is part of a file, and whether the data block is tagged or not tagged is further based on a size of the file.

### Claim 12 (depends on 1)

The method of claim 1, wherein whether the data block is tagged or not tagged is further based on a change rate for the previous snapshot of the data block.

### Claim 13 (depends on 1)

The method of claim 1, wherein the data block is part of a file, and whether the data block is tagged or not tagged is further based on a change rate for a previous snapshot of the file.

### Claim 14 (depends on 1)

The method of claim 1, wherein whether the data block is tagged or not tagged is further based on a change history for two or more previous snapshots of the portion of the fileset relating to the data block.

### Claim 15 (depends on 1)

The method of claim 1, wherein whether the data block is tagged or not tagged is further based on whether an estimated probability that the data block has changed since the previous snapshot is greater than 1−(a cost of calculating the digital fingerprint of the data block and determining whether the digital fingerprints of the data block and of the previous snapshot are the same)/(a cost of transferring the data block).

### Claim 16 (depends on 1)

The method of claim 1, wherein a tag for automatic transfer of the data block expires after a predetermined period.

### Claim 17 (depends on 1)

The method of claim 1, wherein the digital fingerprint is a hash.

### Claim 18 (depends on 1)

The method of claim 1, wherein:
the DMS system comprises a DMS cluster of peer DMS nodes, a DMS database implemented across the peer DMS nodes and a distributed data store implemented across the peer DMS nodes;
whether the data block is tagged or not tagged is stored in the DMS database, and the previous snapshot is stored in the distributed data store;
jobs to transfer data blocks from the compute infrastructure to the distributed data store are posted to a job queue accessible by the peer DMS nodes; and
the peer DMS nodes autonomously fetch and execute jobs from the job queue.

### Claim 19

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.

### Claim 20 (depends on 19)

The DMS cluster of claim 19, wherein if the data block is currently tagged for automatic transfer, then transferring the data block from the compute infrastructure to the DMS system without first determining whether the data block is the same as a previous snapshot of the data block already stored in the DMS system.

### Claim 21 (depends on 19)

The DMS cluster of claim 19, wherein at least some of the peer DMS nodes are either (a) physical machines comprising a hardware processor, memory, and data storage in addition to the software stack; and/or (b) virtual machines.

### Claim 22

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.

### Claim 23 (depends on 22)

The non-transitory computer-readable medium of claim 22, wherein if the data block is currently tagged for automatic transfer, then transferring the data block from the compute infrastructure to the DMS system without first determining whether the data block is the same as a previous snapshot of the data block already stored in the DMS system.
