# US 2025/0165349 A1 · Volume group restore from remote object store

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

- Number: US 2025/0165349 A1
- Document ID: US20250165349A1
- Status: Published application
- Kind: A1
- Application number: 19/030,358
- Filed: 2025-01-17
- Published: 2025-05-22
- Earliest claimed: 2022-04-27
- Assignees: NetApp, Inc.
- Applicants: NetApp, Inc.
- Inventors: Rakesh Bhargava M.R.; Murali Subramanian; Tijin George; Ching-Yuk Paul Ngan
- Web page: https://patentgrep.com/patent/US20250165349A1

## CPC

- G06F 11/1448: {Management of the data involved in backup or backup restore}
- G06F 11/1469: {Backup restoration techniques}
- G06F 3/0604: {Improving or facilitating administration, e.g. storage management}
- G06F 3/0619: {in relation to data integrity, e.g. data losses, bit errors}
- G06F 3/065: {Replication mechanisms}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 2201/815: Virtual
- 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

Techniques are provided for volume group backup, volume group restore, and volume group garbage collection for volume groups backed up to an object store. A volume group workflow is implemented to orchestrate individual consistent volume workflows that are separately and individually implemented by nodes hosting constituent volumes of a volume group. The volume group workflow and the individual consistent volume workflows are performed to back up the volume group to the object store, restore a volume group backup from the object store to a restore destination, and/or perform garbage collection on slots of objects storing data unique to a volume group backup to delete.

## Claims

### Claim 1

A method comprising:
receiving a request to perform a restore operation for a subset of data of a volume group backed up to an object store as a volume group backup composed of a plurality of constituent volume backups of a set of constituent volumes forming the volume group;
evaluating a metafile to identify geometry information describing how the volume group is composed of the set of constituent volumes backed up to the object store as the plurality of constituent volume backups;
generating a restore target based upon the geometry information;
utilizing the metafile generate one or more constituent volume restore workflows; and
implementing, by one or more nodes, the one or more constituent volume restore workflows to restore the subset of data of the volume group to the restore target.

### Claim 2 (depends on 1)

The method of claim 1, comprising:
evaluating the metafile to identify:
a group root info object representing a volume group endpoint within the object store;
a constituent volume root info object per constituent volume endpoint within the object store; and
a group snapinfo object per constituent volume backup in the object store, wherein the group snapinfo objects are populated with group properties of the volume group backup; and
utilizing the group root info object, the constituent volume root info objects, and the group snapinfo object to generate the one or more constituent volume restore workflows.

### Claim 3 (depends on 1)

The method of claim 1, comprising:
restore a constituent volume or a single file of the volume group as the subset of data.

### Claim 4 (depends on 1)

The method of claim 1, comprising:
incrementally restore the subset of data.

### Claim 5 (depends on 1)

The method of claim 1, comprising:
restore a directory or qtree of the volume group as the subset of data.

### Claim 6 (depends on 1)

The method of claim 1, comprising:
restore the subset of data on-demand.

### Claim 7

A system comprising:
a container orchestration platform configured to host containers capable of executing applications having access to an object store; and
an active data connector, configured to perform a restore operation, hosted within a container of the container orchestration platform, wherein the active data connector is configured to:
parse metadata stitching together a plurality of constituent volume backups constituting a volume group backup of a volume group comprising a set of constituent volumes backed up to the object store as the plurality of constituent volume backups;
parse a metafile to identify geometry information describing how the volume group is composed of the set of constituent volumes backed up to the object store as the plurality of constituent volume backups;
utilize the metadata and the metafile to identify the volume group backup as the plurality of constituent volume backups; and
perform the restore operation to restore the volume group using the volume group backup.

### Claim 8 (depends on 7)

The system of claim 7, wherein the active data connector:
evaluates the metafile to determine a geometry of the volume group backup for generating constituent volume restore workflows performed by nodes to restore the volume group.

### Claim 9 (depends on 7)

The system of claim 7, wherein the active data connector:
utilizes the metafile, comprising information related to the plurality of constituent volume backups and the volume group backup, for generating constituent volume restore workflows performed by nodes to restore the volume group.

### Claim 10 (depends on 7)

The system of claim 7, wherein the active data connector:
utilizes a group root info object, representing a volume group endpoint within the object store, within the metafile to generate constituent volume restore workflows performed by nodes to restore the volume group.

### Claim 11 (depends on 7)

The system of claim 7, wherein the active data connector:
utilizes a constituent volume root info object, per constituent volume endpoint within the object store, within the metafile to generate constituent volume restore workflows performed by nodes to restore the volume group.

### Claim 12 (depends on 7)

The system of claim 7, wherein the active data connector:
evaluates the metafile to identify a constituent volume root info object per constituent volume endpoint within the object store for generating constituent volume restore workflows performed by nodes to restore the volume group.

### Claim 13 (depends on 7)

The system of claim 7, wherein the active data connector:
evaluates the metafile to identify a group snapinfo object per constituent volume backup in the object store for generating constituent volume restore workflows performed by nodes to restore the volume group, wherein the group snapinfo objects are populated with volume group information relating to group properties of the volume group backup.

### Claim 14 (depends on 7)

The system of claim 7, wherein the metafile comprises a copy of a group root info object and group snapinfo objects, and wherein the metafile comprises geometry information describing how the volume group is composed of the set of constituent volumes.

### Claim 15 (depends on 7)

The system of claim 7, wherein the active data connector:
utilizes the metafile and metadata to provide a user with snapshot browsing functionality of snapshots backed up to the object store.

### Claim 16

A non-transitory machine readable medium comprising instructions, which when executed by a machine, causes the machine to:
receive a request to perform a restore operation for a subset of data of a volume group backed up to an object store as a volume group backup composed of a plurality of constituent volume backups of a set of constituent volumes forming the volume group;
evaluate a metafile to identify geometry information describing how the volume group is composed of the set of constituent volumes backed up to the object store as the plurality of constituent volume backups;
generate a restore target based upon the geometry information;
utilize the metafile to generate one or more constituent volume restore workflows; and
implement, by one or more nodes, the one or more constituent volume restore workflows to restore the subset of data of the volume group to the restore target.

### Claim 17 (depends on 16)

The non-transitory machine readable medium of claim 16, wherein the instructions cause the machine to:
evaluate the metafile to identify:
a group root info object representing a volume group endpoint within the object store;
a constituent volume root info object per constituent volume endpoint within the object store; and
a group snapinfo object per constituent volume backup in the object store, wherein the group snapinfo objects are populated with group properties of the volume group backup;
utilize the group root info object, the constituent volume root info objects, and the group snapinfo object to generate the one or more constituent volume restore workflows.

### Claim 18 (depends on 16)

The non-transitory machine readable medium of claim 16, wherein the instructions cause the machine to:
incrementally restore the subset of data.

### Claim 19 (depends on 16)

The non-transitory machine readable medium of claim 16, wherein the instructions cause the machine to:
restore a directory or qtree of the volume group as the subset of data.

### Claim 20 (depends on 16)

The non-transitory machine readable medium of claim 16, wherein the instructions cause the machine to:
restore the subset of data on-demand.
