# US 2025/0156277 A1 · Rapid Access for Restored Cloud Backup Data

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

- Number: US 2025/0156277 A1
- Document ID: US20250156277A1
- Status: Published application
- Kind: A1
- Application number: 18/505,868
- Filed: 2023-11-09
- Published: 2025-05-15
- Earliest claimed: 2023-11-09
- Assignees: Commvault Systems, Inc.
- Applicants: Commvault Systems, Inc.
- Inventors: Xia Hua; Woonho Joseph Jung; Jinmyeong Kim; Junhwan Kim; Seunghyeon Kim; Yuchon Yi; Nicholas Gerald Zehender; Jason Sarich; Jaewon Wi
- Web page: https://patentgrep.com/patent/US20250156277A1

## CPC

- G06F 11/1451: {by selection of backup contents}
- G06F 11/1435: {using file system or storage system metadata}
- G06F 11/1464: {for networked environments}
- G06F 11/1469: {Backup restoration techniques}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Techniques are disclosed relating to providing fast access to restored data in a cloud storage environment. A computing system stores multiple sets of incremental backup data that reflect changes in data being backed up between backup intervals and metadata that indicates which set of incremental backup data stores a given object. The computing system generates an endpoint for a requesting computing system, where the endpoint supports requests for restored backup data and data responses. In response to a request from the requesting computing system via the endpoint, the computing system queries the metadata based on the request and stores metadata retrieved from the query in a key/value store using object identification information as key data and the retrieved metadata as value data. The computing system provides requested data according to a lazy loading technique, including providing requested data via the endpoint based on the metadata in the key/value store.

## Claims

### Claim 1

A method, comprising:
storing, by a computing system:
multiple sets of incremental backup data that reflects changes in data being backed up between backup intervals; and
metadata that indicates, for a given object, which set of incremental backup data stores the object;
generating, by the computing system, an endpoint for a requesting computing system, wherein the endpoint supports requests for restored backup data and data responses; and
in response to a request from the requesting computing system via the endpoint, the computing system:
querying the metadata based on the request;
storing metadata retrieved from the query in a key/value store using object identification information as key data and the retrieved metadata as value data; and
providing requested data according to a lazy loading technique, including providing requested data via the endpoint based on the metadata in the key/value store.

### Claim 2 (depends on 1)

The method of claim 1, wherein the object identification information includes an object name, a prefix, or both.

### Claim 3 (depends on 1)

The method of claim 1, wherein the metadata includes object location information, an object creation time, and a size of the object.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
in response to the request, performing a full restore of requested data to a data store of an account associated with the request, wherein the full restore is performed at least partially in parallel with the lazy loading technique.

### Claim 5 (depends on 1)

The method of claim 1, wherein the storing includes storing retrieved metadata in multiple different lookup tables of the key/value store.

### Claim 6 (depends on 5)

The method of claim 5, wherein the querying the metadata includes performing multiple queries at least partially in parallel to multiple different partitions of the multiple sets of incremental backup data.

### Claim 7 (depends on 6)

The method of claim 6, wherein the querying the metadata and the storing are based on a mapping of multiple partitions to a given lookup table of the multiple different lookup tables.

### Claim 8 (depends on 6)

The method of claim 6, wherein:
a given partition of the multiple different partitions includes an ordered list of objects; and
the storing maintains ordering from among the different partitions according to an ordered list of partitions.

### Claim 9 (depends on 1)

The method of claim 1, wherein the request specifies at least one protection group.

### Claim 10 (depends on 1)

The method of claim 1, wherein the request specifies restoration time information.

### Claim 11 (depends on 1)

The method of claim 1, wherein the generating the endpoint is performed in response to an endpoint request from the requesting computing system.

### Claim 12

A non-transitory computer-readable medium having instructions stored thereon that are executable by a computing device to perform operations comprising:
storing:
multiple sets of incremental backup data that reflects changes in data being backed up between backup intervals; and
metadata that indicates, for a given object, which set of incremental backup data stores the object;
generating an endpoint for a requesting computing system, wherein the endpoint supports requests for restored backup data and data responses; and
in response to an request from the requesting computing system via the endpoint:
querying the metadata based on the request;
storing metadata retrieved from the query in a key/value store using object identification information as key data and the retrieved metadata as value data; and
providing requested data according to a lazy loading technique, including providing requested data via the endpoint based on the metadata in the key/value store.

### Claim 13 (depends on 12)

The non-transitory computer-readable medium of claim 12, wherein the storing includes storing retrieved metadata in multiple different lookup tables of the key/value store.

### Claim 14 (depends on 13)

The non-transitory computer-readable medium of claim 13, wherein the querying the metadata includes performing multiple queries at least partially in parallel to multiple different partitions of the multiple sets of incremental backup data.

### Claim 15 (depends on 14)

The non-transitory computer-readable medium of claim 14, wherein the querying the metadata and the storing are based on a mapping of multiple partitions to a given lookup table of the multiple different lookup tables.

### Claim 16

A method, comprising:
sending, by a requesting computing system, a request for restored backup data via an endpoint provided by a backup computing system; and
receiving requested data via the endpoint, wherein the backup computing system generated the requested data by:
querying metadata based on the request, wherein the metadata indicates, for a given object in incremental backup data, which set of incremental backup data stores the object;
storing metadata retrieved from the query in a key/value store using object identification information as key data and the retrieved metadata as value data; and
providing the requested data based on the metadata in the key/value store.

### Claim 17 (depends on 16)

The method of claim 16, further comprising, the backup computing system performing the querying, storing, and providing.

### Claim 18 (depends on 16)

The method of claim 16, further comprising:
receiving a full restore of requested data to a data store of an account associated with the request, at least partially in parallel with receiving requested data via the endpoint.

### Claim 19 (depends on 16)

The method of claim 16, further comprising:
requesting, by the requesting computing system, the endpoint.

### Claim 20 (depends on 19)

The method of claim 19, wherein the request for the endpoint identifies a protection group and restoration time information.
