# US 2022/0091942 A1 · Snapshot Backup And Recovery

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

- Number: US 2022/0091942 A1
- Document ID: US20220091942A1
- Status: Published application
- Kind: A1
- Application number: 17/028,891
- Filed: 2020-09-22
- Published: 2022-03-24
- Earliest claimed: 2020-09-22
- Assignees: Robin Systems, Inc.
- Applicants: Robin Systems, Inc.
- Inventors: Jagadish Mukku; Nitin Singla; Kallur Vasudeva Rao Narasimha Subban
- Web page: https://patentgrep.com/patent/US20220091942A1

## CPC

- G06F 11/1469: {Backup restoration techniques}
- G06F 3/0604: {Improving or facilitating administration, e.g. storage management}
- 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/1451: {by selection of backup contents}
- G06F 11/1464: {for networked environments}
- G06F 11/2094: {Redundant storage or storage space (G06F11/2056 takes precedence)}
- 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 2201/80: Database-specific techniques
- 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

Snapshots are created of a unit of storage such that the snapshot includes all segments allocated to the unit of storage until a subsequent snapshot is created. A backup of a first snapshot may be performed by copying segments of the snapshot to backup storage. If a preceding snapshot has been backed up, those segments of the first snapshot are copied to backup storage without copying the segments of the preceding snapshot, otherwise all segments of the snapshot are copied. Metadata describing the snapshot may be retained but storage may be freed to be overwritten. The metadata may reference identifiers of segments copied to backup storage. Data stored in backup storage may also be labeled as individual segments or be associated with snapshot metadata in backup storage.

## Claims

### Claim 1

A method comprising:
storing, on a storage computing device including one or more storage devices, a logical storage unit by allocating first segments of storage on the one or more storage devices to the logical storage unit;
creating, on the storage computing device, a first snapshot of the logical storage unit by associating segments of storage allocated to the one or more storage devices upon creation of the first snapshot with a first snapshot identifier;
receiving, on the storage computing device, a first instruction to create an off-premise backup for the first snapshot identifier; and
in response to the first instruction:
copying, by the storage computing device, data from the first segments of storage to second segments of storage on a remote backup storage system;
releasing, by the storage computing device, the first segments of storage to be overwritten; and
retaining, by the storage computing device in the one or more storage devices, first metadata referencing the first snapshot identifier and the data sufficient to identify the second segments of storage.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
assigning, by the storage computing device, first identifiers to the first segments of storage allocated to the logical storage unit;
associating, by the storage computing device, the first identifiers with the second segments of storage on the remote backup storage system; and
recording the first identifiers in the first metadata.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
creating, by the storage computing device, a second snapshot of the logical storage unit subsequent to creating the first snapshot, the second snapshot having a second snapshot identifier;
allocating, by the storage computing device, second segments of storage on the one or more storage devices to the logical storage unit and associating the second segments of storage with the second snapshot identifier;
assigning, by the storage computing device, second identifiers to the second segments of storage allocated to the logical storage unit;
receiving, by the storage computing device, a second instruction to create an off-premise backup for the second snapshot identifier;
evaluating, by the storage computing device, the first metadata;
determining, by the storage computing device, that the data corresponding to the first identifiers has already been copied to the remote backup storage system; and
in response to determining that the data corresponding to the first identifiers has already been copied to the remote backup storage system, copying only data stored in the second segments associated with the second identifiers.

### Claim 4 (depends on 3)

The method of claim 3, further comprising assigning the first identifiers and the second identifiers such that each identifier of the first and second identifiers is larger than a previously assigned identifier of the first and second identifiers.

### Claim 5 (depends on 4)

The method of claim 4, further comprising:
maintaining, by the storage computing device, a segment map that maps the first and second segments of storage to the logical storage unit and to the first and second identifiers.

### Claim 6 (depends on 2)

The method of claim 2, further comprising:
creating, by the storage computing device, a second snapshot of the logical storage unit prior to creating the first snapshot, the second snapshot having a second snapshot identifier;
allocating, by the storage computing device, second segments of storage on the one or more storage devices to the logical storage unit and associating the second segments of storage with the second snapshot identifier;
assigning, by the storage computing device, second identifiers to the second segments of storage allocated to the logical storage unit; and
in response to the first instruction to create an off-premise backup for first second snapshot identifier:
determining, by the storage computing device, that data corresponding to the second identifiers has not been copied to the remote backup storage system; and
in response to determining that the data corresponding to the second identifiers has not been copied to the remote backup storage system, copying, by the storage computing device, the data corresponding to the second identifiers to the remote backup storage system.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
receiving, by the storage computing device, a second instruction to restore the first snapshot identifier;
evaluating, by the storage computing device, the first metadata;
identifying, by the storage computing device, the data corresponding to the first segments on the remote backup storage system from the first metadata;
retrieving, by the storage computing device, the data corresponding to the first segments of storage from the remote backup storage system; and
storing, by the storage computing device, the data corresponding to the first segments of storage in third segments of storage on the one or more storage devices.

### Claim 8 (depends on 7)

The method of claim 7, further comprising, in response to the second instruction to restore the first snapshot identifier:
evaluating, by the storage computing device, second metadata for a second snapshot identifier associated with the logical storage unit, the second snapshot identifier corresponding to a second snapshot created prior to creating the first snapshot;
determining, by the storage computing device, that the second metadata indicates that data corresponding to fourth segments of storage of the second snapshot has been copied to the remote backup storage system; and
in response to determining that the second metadata indicates that the data corresponding to the fourth segments of storage of the second snapshot has been copied to the remote backup storage system:
retrieving, by the storage computing device, the data corresponding to the fourth segments of storage from the remote backup storage system; and
storing, by the storage computing device, the data corresponding to the fourth segments of storage in fifth segments of storage on the one or more storage devices.

### Claim 9 (depends on 1)

The method of claim 1, wherein the first metadata includes a time of creation of the off-premise backup of the first snapshot.

### Claim 10 (depends on 1)

The method of claim 1, further comprising one of:
labeling the second segments of storage on the remote backup storage system as corresponding to the first snapshot identifier; and
storing at least a portion of the first metadata on the remote backup storage system as second metadata, the second metadata referencing the second segments of storage.

### Claim 11

A system comprising:
one or more processing devices;
one or more storage devices coupled to the one or more processing devices; and
one or more memory devices coupled to the one or more processing devices, the one or more memory devices storing executable code, that, when executed by the one or more processing devices, causes the one or more processing devices to:
store a logical storage unit by allocating first segments of storage on the one or more storage devices to the logical storage unit;
create a first snapshot of the logical storage unit by associating segments of storage allocated to the one or more storage devices upon creation of the first snapshot with a first snapshot identifier;
receive a first instruction to create an off-premise backup for the first snapshot identifier; and
in response to the first instruction:
copy data from the first segments of storage to second segments of storage on a remote backup storage system;
release the first segments of storage to be overwritten; and
retain in the one or more storage devices, first metadata referencing the first snapshot identifier and data sufficient to identify the second segments of storage.

### Claim 12 (depends on 11)

The system of claim 11, wherein the executable code, when executed by the one or more processing devices, further causes the one or more processing devices to:
assign first identifiers to the first segments of storage allocated to the logical storage unit;
associate the first identifiers with the second segments of storage on the remote backup storage system; and
record the first identifiers in the first metadata.

### Claim 13 (depends on 12)

The system of claim 12, wherein the executable code, when executed by the one or more processing devices, further causes the one or more processing devices to:
create a second snapshot of the logical storage unit subsequent to creating the first snapshot, the second snapshot having a second snapshot identifier;
allocate second segments of storage on the one or more storage devices to the logical storage unit and associating the second segments of storage with the second snapshot identifier;
assign second identifiers to the second segments of storage allocated to the logical storage unit;
receive a second instruction to create an off-premise backup for the second snapshot identifier;
evaluate the first metadata;
determine that the data corresponding to the first identifiers has already been copied to the remote backup storage system; and
in response to determining that the data corresponding to the first identifiers has already been copied to the remote backup storage system, copy only data stored in the second segments associated with the second identifiers.

### Claim 14 (depends on 13)

The system of claim 13, wherein the executable code, when executed by the one or more processing devices to assign the first identifiers and the second identifiers such that each identifier of the first and second identifiers is larger than a previously assigned identifier of the first and second identifiers.

### Claim 15 (depends on 14)

The system of claim 14, wherein the executable code, when executed by the one or more processing devices to:
maintain a segment map that maps the first and second segments of storage to the logical storage unit and to the first and second identifiers.

### Claim 16 (depends on 12)

The system of claim 12, wherein the executable code, when executed by the one or more processing devices to:
create a second snapshot of the logical storage unit prior to creating the first snapshot, the second snapshot having a second snapshot identifier;
allocate second segments of storage on the one or more storage devices to the logical storage unit and associating the second segments of storage with the second snapshot identifier;
assign second identifiers to the second segments of storage allocated to the logical storage unit; and
in response to the first instruction to create an off-premise backup for first second snapshot identifier:
determine that data corresponding to the second identifiers has not been copied to the remote backup storage system; and
in response to determining that the data corresponding to the second identifiers has not been copied to the remote backup storage system, copy the data corresponding to the second identifiers to the remote backup storage system.

### Claim 17 (depends on 11)

The system of claim 11, wherein the executable code, when executed by the one or more processing devices to:
receive a second instruction to restore the first snapshot identifier;
evaluate the first metadata;
identify the data corresponding to the first segments on the remote backup storage system from the first metadata;
retrieve the data corresponding to the first segments of storage from the remote backup storage system; and
store the data corresponding to the first segments of storage in third segments of storage on the one or more storage devices.

### Claim 18 (depends on 17)

The system of claim 17, wherein the executable code, when executed by the one or more processing devices to:
evaluate second metadata for a second snapshot identifier associated with the logical storage unit, the second snapshot identifier corresponding to a second snapshot created prior to creating the first snapshot;
determine that the second metadata indicates that data corresponding to fourth segments of storage of the second snapshot has been copied to the remote backup storage system; and
in response to determining that the second metadata indicates that the data corresponding to the fourth segments of storage of the second snapshot has been copied to the remote backup storage system:
retrieve the data corresponding to the fourth segments of storage from the remote backup storage system; and
store the data corresponding to the fourth segments of storage in fifth segments of storage on the one or more storage devices.

### Claim 19 (depends on 11)

The system of claim 11, wherein the first metadata includes a time of creation of the off-premise backup of the first snapshot.

### Claim 20 (depends on 11)

The system of claim 11, wherein the executable code, when executed by the one or more processing devices to:
label the second segments of storage on the remote backup storage system as corresponding to the first snapshot identifier; and
invoke storing at least a portion of the first metadata on the remote backup storage system as second metadata, the second metadata referencing the second segments of storage.
