# US 2024/0202162 A1 · Immutable object locking for snapshot management

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

- Number: US 2024/0202162 A1
- Document ID: US20240202162A1
- Status: Published application
- Kind: A1
- Application number: 18/081,673
- Filed: 2022-12-14
- Published: 2024-06-20
- Earliest claimed: 2022-12-14
- Assignees: Rubrik, Inc.
- Applicants: Rubrik, Inc.
- Inventors: Haritha Elango; Prakhar Kumar; Partha Dhar; Animesh Kumar; Gaurav Maheshwari; Srikanth Hanumanula
- Web page: https://patentgrep.com/patent/US20240202162A1

## CPC

- 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/1448: {Management of the data involved in backup or backup restore}
- G06F 11/1451: {by selection of backup contents}
- G06F 11/1461: {Backup scheduling policy}
- 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

Methods, systems, and devices for data management are described. A data management system (DMS) may receive an indication of a storage configuration for an object storage location within a cloud environment. The DMS may generate a snapshot of a computing system in accordance with a backup policy associated with the computing system. The DMS may cause one or more data objects corresponding to the snapshot to be stored in the object storage location within the cloud environment in accordance with the storage configuration. The DMS may apply immutable object locks to the one or more data objects within the object storage location. The DMS may execute, in accordance with the backup policy associated with the computing system, one or more jobs that cause the respective immutable object locks for the one or more data objects to be extended one or more times during a retention period for the snapshot.

## Claims

### Claim 1

A method for data management, comprising:
receiving, at a data management system configured to manage data for a computing system, an indication of a storage configuration for an object storage location within a cloud environment:
generating, by the data management system and in accordance with a backup policy associated with the computing system, a snapshot of the computing system:
causing, by the data management system and in accordance with the storage configuration, one or more data objects corresponding to the snapshot to be stored in the object storage location within the cloud environment, wherein respective immutable object locks are applied to the one or more data objects within the object storage location; and
executing, by the data management system and in accordance with the backup policy associated with the computing system, one or more jobs that cause the respective immutable object locks for the one or more data objects to be extended one or more times during a retention period for the snapshot, the retention period based at least in part on the backup policy.

### Claim 2 (depends on 1)

The method of claim 1, wherein executing the one or more jobs comprises:
causing, by the data management system, an incremental object lock on a first data object to be extended after the retention period based at least in part on determining that the first data object is referenced in a subsequent snapshot of the computing system.

### Claim 3 (depends on 1)

The method of claim 1, wherein executing the one or more jobs comprises:
causing, by the data management system, a first data object to be deleted from the object storage location after the retention period based at least in part on determining that the first data object is not referenced in any subsequent snapshots of the computing system.

### Claim 4 (depends on 1)

The method of claim 1, wherein executing the one or more jobs comprises:
causing, by the data management system, the respective immutable object locks on the one or more data objects to be extended for a threshold lock duration specified in the storage configuration for the object storage location.

### Claim 5 (depends on 1)

The method of claim 1, wherein executing the one or more jobs comprises:
causing, by the data management system, an immutable object lock on a first data object to be periodically extended two or more times during the retention period of the snapshot in accordance with the backup policy associated with the computing system.

### Claim 6 (depends on 1)

The method of claim 1, wherein executing the one or more jobs comprises:
causing, by the data management system, a first immutable object lock on a first data object stored in the object storage location to be extended prior to a scheduled expiration of the first immutable object lock.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
receiving, at the data management system, an indication of an updated backup policy for the computing system, the updated backup policy indicating an updated retention period for the snapshot; and
determining, by the data management system, whether to extend the respective immutable object locks on the one or more data objects based at least in part on the updated backup policy for the computing system.

### Claim 8 (depends on 1)

The method of claim 1, wherein executing the one or more jobs comprises:
causing, by the data management system, an immutable object lock on a first data object stored in the object storage location to be extended for a duration that is less than a threshold lock duration based at least in part on a difference between an expiration time associated with the immutable object lock and an end of the retention period for the snapshot.

### Claim 9 (depends on 1)

The method of claim 1, wherein causing the one or more data objects to be stored in the object storage location comprises:
determining, by the data management system, that two or more instances of a data object are stored in the object storage location in association with different snapshots of the computing system; and
causing, by the data management system, an immutable object lock to be applied to at most one of the two or more instances of the data object stored in the object storage location.

### Claim 10 (depends on 1)

The method of claim 1, wherein executing the one or more jobs comprises:
detecting, by the data management system, a lock extension failure associated with execution of at least one of the one or more jobs; and
outputting, by the data management system, an indication of the lock extension failure.

### Claim 11 (depends on 1)

The method of claim 1, wherein causing the one or more data objects to be stored in the object storage location comprises:
transferring, by the data management system, the one or more data objects that correspond to the snapshot of the computing system from the data management system to the object storage location in the cloud environment a threshold time duration after generating the snapshot, the threshold time duration specified in the backup policy associated with the computing system.

### Claim 12 (depends on 1)

The method of claim 1, wherein the snapshot is a part of a snapshot chain that comprises at least one full snapshot of the computing system and one or more incremental snapshots of the computing system.

### Claim 13 (depends on 12)

The method of claim 12, wherein executing the one or more jobs comprises:
causing, by the data management system, an immutable object lock on a data object from a different snapshot in the snapshot chain to be extended for at least the retention period of the snapshot based at least in part on determining that the data object is referenced in the snapshot.

### Claim 14 (depends on 1)

The method of claim 1, wherein the respective immutable object locks comprise time-based object settings that prevent users from deleting or modifying the one or more data objects while the respective immutable object locks are active.

### Claim 15 (depends on 1)

The method of claim 1, wherein the snapshot comprises a full snapshot of the computing system or an incremental snapshot of the computing system, the full snapshot indicating a state of the computing system at a first time, the incremental snapshot indicating changes to the computing system between the first time and a second time.

### Claim 16 (depends on 1)

The method of claim 1, wherein:
the snapshot comprises backup data associated with the computing system; and
the backup data from the snapshot is partitioned into the one or more data objects.

### Claim 17

An apparatus for data management, comprising:
a processor:
memory coupled with the processor; and
instructions stored in the memory and executable by the processor to cause the apparatus to:
receive, at a data management system configured to manage data for a computing system, an indication of a storage configuration for an object storage location within a cloud environment:
generate, by the data management system and in accordance with a backup policy associated with the computing system, a snapshot of the computing system;
cause, by the data management system and in accordance with the storage configuration, one or more data objects corresponding to the snapshot to be stored in the object storage location within the cloud environment, wherein respective immutable object locks are applied to the one or more data objects within the object storage location; and
execute, by the data management system and in accordance with the backup policy associated with the computing system, one or more jobs that cause the respective immutable object locks for the one or more data objects to be extended one or more times during a retention period for the snapshot, the retention period based at least in part on the backup policy.

### Claim 18 (depends on 17)

The apparatus of claim 17, wherein, to execute the one or more jobs, the instructions are executable by the processor to cause the apparatus to:
cause, by the data management system, an incremental object lock on a first data object to be extended after the retention period based at least in part on determining that the first data object is referenced in a subsequent snapshot of the computing system.

### Claim 19 (depends on 17)

The apparatus of claim 17, wherein, to execute the one or more jobs, the instructions are executable by the processor to cause the apparatus to:
cause, by the data management system, a first data object to be deleted from the object storage location after the retention period based at least in part on determining that the first data object is not referenced in any subsequent snapshots of the computing system.

### Claim 20

A non-transitory computer-readable medium storing code for data management, the code comprising instructions executable by a processor to:
receive, at a data management system configured to manage data for a computing system, an indication of a storage configuration for an object storage location within a cloud environment:
generate, by the data management system and in accordance with a backup policy associated with the computing system, a snapshot of the computing system:
cause, by the data management system and in accordance with the storage configuration, one or more data objects corresponding to the snapshot to be stored in the object storage location within the cloud environment, wherein respective immutable object locks are applied to the one or more data objects within the object storage location; and
execute, by the data management system and in accordance with the backup policy associated with the computing system, one or more jobs that cause the respective immutable object locks for the one or more data objects to be extended one or more times during a retention period for the snapshot, the retention period based at least in part on the backup policy.
