# US 2026/0064631 A1 · Techniques for propagating retention policy changes for recovery from an archive

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

- Number: US 2026/0064631 A1
- Document ID: US20260064631A1
- Status: Published application
- Kind: A1
- Application number: 18/824,890
- Filed: 2024-09-04
- Published: 2026-03-05
- Earliest claimed: 2024-09-04
- Assignees: Rubrik, Inc.
- Applicants: Rubrik, Inc.
- Inventors: Harshadrai Gajendrakumar PAREKH; Aditya KHANDKAR
- Web page: https://patentgrep.com/patent/US20260064631A1

## CPC

- G06F 16/125: {characterised by the use of retention policies (retention policies for HSM systems G06F16/185)}
- G06F 11/1448: {Management of the data involved in backup or backup restore}
- G06F 11/1451: {by selection of backup contents}
- G06F 11/1458: {Management of the backup or restore process}
- G06F 11/1469: {Backup restoration techniques}
- G06F 16/113: {Details of archiving (lifecycle management in storage systems G06F3/0649; point-in-time backing up or restoration of persistent data G06F11/1446)}
- 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 may establish a first data system that stores and retains data objects in accordance with a service level agreement (SLA) retention policy. The data management system may also store one or more backups of the data objects in an archival location. In some aspects, the data management system may obtain an indication of one or more updates made to the SLA retention policy and may perform an on-demand job to propagate the updates made to the SLA retention policy to the backups stored in the archival location. The data management system may then establish a secondary data system having read-only permissions, and may promote the secondary data system from the read-only permissions to owner permissions in order to access, manage, and recover the archived data objects with a most up-to-date SLA retention policy.

## Claims

### Claim 1

A method, comprising:
establishing a first data system in accordance with a service level agreement (SLA) retention policy, wherein the SLA retention policy is indicative of a first duration that one or more backups of one or more data objects are retained by the first data system;
storing the one or more backups of the one or more data objects in an archival location in accordance with the SLA retention policy;
obtaining, from a user, an indication of one or more updates made to the SLA retention policy;
performing, in response to the obtaining the indication of the one or more updates made to the SLA retention policy, an on-demand job to propagate the one or more updates made to the SLA retention policy to the one or more backups of the one or more data objects stored in the archival location;
establishing a secondary data system to access the one or more backups of the one or more data objects stored in the archival location;
promoting the secondary data system from a read permission to an owner permission; and
restoring the one or more data objects in the secondary data system in accordance with the one or more updates to the SLA retention policy.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
tracking retention information associated with the SLA retention policy over a time duration, the retention information including at least the SLA retention policy corresponding to a creation time of the one or more backups and a most recently updated version of the SLA retention policy of the one or more backups.

### Claim 3 (depends on 1)

The method of claim 1, wherein performing the on-demand job comprises:
performing the on-demand job to update a history of updates made to the SLA retention policy of the one or more backups of the one or more data objects already stored in the archival location.

### Claim 4 (depends on 1)

The method of claim 1, wherein performing the on-demand job comprises:
adding an entry corresponding to the one or more updates made to the SLA retention policy to a queue, wherein the queue includes one or more retention policy changes that are pending propagation to the one or more backups of the one or more data objects stored in the archival location; and
performing the on-demand job to propagate the one or more updates made to the SLA retention policy to the one or more backups of the one or more data objects in accordance with an ordering of the queue.

### Claim 5 (depends on 4)

The method of claim 4, wherein the queue comprises a propagation queue table that stores entries corresponding to the one or more retention policy changes that are pending propagation to the one or more backups of the one or more data objects stored in the archival location.

### Claim 6 (depends on 4)

The method of claim 4, wherein the ordering of the queue comprises a creation time-based ordering, and a lowest priority entry of the queue has a most recent creation time.

### Claim 7 (depends on 4)

The method of claim 4, further comprising:
marking the entry as complete subsequent to propagating the one or more updates made to the SLA retention policy.

### Claim 8 (depends on 4)

The method of claim 4, further comprising:
initiating a background job to monitor for pending entries in the queue, wherein a pending entry triggers execution of the on-demand job.

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
generating updated metadata corresponding to the one or more updates made to the SLA retention policy; and
uploading an updated version of a metadata file including at least the updated metadata to the archival location, wherein the updated metadata indicates the one or more updates made to the SLA retention policy for a specific backup of a specific data object.

### Claim 10 (depends on 1)

The method of claim 1, wherein the one or more updates to the SLA retention policy are for respective backups of a specific data object, the method further comprising:
generating updated metadata corresponding to the one or more updates made to the SLA retention policy for the respective backups of the specific data object; and
uploading, to the archival location, updated metadata files for the respective backups of the specific data object, wherein the updated metadata files include at least the updated metadata that indicates the one or more updates made to the SLA retention policy for the specific data object and the respective backups of the specific data object.

### Claim 11 (depends on 1)

The method of claim 1, further comprising:
uploading, to the archival location, a new metadata file including the one or more updates to the SLA retention policy, wherein the new metadata file comprises a new version of one or more previously uploaded metadata files, the new version having a higher priority than the one or more previously uploaded metadata files; and
propagating the one or more updates made to the SLA retention policy to the one or more backups of the one or more data objects stored in the archival location in accordance with the new metadata file.

### Claim 12 (depends on 1)

The method of claim 1, wherein the indication of the one or more updates made to the SLA retention policy are applicable to the one or more data objects or to a subset of data objects of the one or more data objects.

### Claim 13 (depends on 1)

The method of claim 1, wherein performing the on-demand job comprises:
adding an entry corresponding to the one or more updates made to the SLA retention policy to a queue, wherein the queue includes one or more retention policy changes that are pending propagation to the one or more backups of the one or more data objects stored in the archival location;
delaying propagation of the one or more updates made to the SLA retention policy based at least in part on the archival location being inaccessible; and
propagating the one or more updates made to the SLA retention policy to the one or more backups of the one or more data objects stored in the archival location subsequent to the archival location becoming accessible.

### Claim 14 (depends on 1)

The method of claim 1, wherein performing the on-demand job comprises:
adding an entry corresponding to the one or more updates made to the SLA retention policy to a queue, wherein the queue includes one or more retention policy changes that are pending propagation to the one or more backups of the one or more data objects stored in a plurality of archival locations including the archival location;
propagating the one or more updates made to the SLA retention policy to the one or more backups of the one or more data objects stored in an accessible archival location of the plurality of archival locations, wherein the plurality of archival locations include accessible archival locations and inaccessible archival locations; and
maintaining the entry as a pending request until the inaccessible archival locations become accessible.

### Claim 15 (depends on 14)

The method of claim 14, further comprising:
initiating a job instance for the on-demand job based at least in part on at least one inaccessible archival location becoming accessible.

### Claim 16 (depends on 1)

The method of claim 1, further comprising:
uploading an updated file version that includes the indication of the one or more updates made to the SLA retention policy to the archival location.

### Claim 17 (depends on 16)

The method of claim 16, wherein the updated file version comprises a most recently uploaded file version of a plurality of file versions, the plurality of file versions corresponding to respective previous updates made to the SLA retention policy.

### Claim 18 (depends on 1)

The method of claim 1, further comprising:
propagating the one or more updates made to the SLA retention policy to the one or more backups of the one or more data objects stored in the archival location concurrently with updating the SLA retention policy in a local metadata store external to the archival location.

### Claim 19

An apparatus, comprising:
one or more memories storing processor-executable code; and
one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the apparatus to:
establish a first data system in accordance with a service level agreement (SLA) retention policy, wherein the SLA retention policy is indicative of a first duration that one or more backups of one or more data objects are retained by the first data system;
store the one or more backups of the one or more data objects in an archival location in accordance with the SLA retention policy;
obtain, from a user, an indication of one or more updates made to the SLA retention policy;
perform, in response to obtaining the indication of the one or more updates made to the SLA retention policy, an on-demand job to propagate the one or more updates made to the SLA retention policy to the one or more backups of the one or more data objects stored in the archival location;
establish a secondary data system to access the one or more backups of the one or more data objects stored in the archival location;
promote the secondary data system from a read permission to an owner permission; and
restore the one or more data objects in the secondary data system in accordance with the one or more updates to the SLA retention policy.

### Claim 20

A non-transitory computer-readable medium storing code, the code comprising instructions executable by one or more processors to:
establish a first data system in accordance with a service level agreement (SLA) retention policy, wherein the SLA retention policy is indicative of a first duration that one or more backups of one or more data objects are retained by the first data system;
store the one or more backups of the one or more data objects in an archival location in accordance with the SLA retention policy;
obtain, from a user, an indication of one or more updates made to the SLA retention policy;
perform, in response to obtaining the indication of the one or more updates made to the SLA retention policy, an on-demand job to propagate the one or more updates made to the SLA retention policy to the one or more backups of the one or more data objects stored in the archival location;
establish a secondary data system to access the one or more backups of the one or more data objects stored in the archival location;
promote the secondary data system from a read permission to an owner permission; and
restore the one or more data objects in the secondary data system in accordance with the one or more updates to the SLA retention policy.
