# US 2023/0267100 A1 · Extending retention lock protection from on-premises to the cloud

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

- Number: US 2023/0267100 A1
- Document ID: US20230267100A1
- Status: Published application
- Kind: A1
- Application number: 18/307,575
- Filed: 2023-04-26
- Published: 2023-08-24
- Earliest claimed: 2020-09-16
- Assignees: EMC IP Holding Company LLC
- Applicants: EMC IP Holding Company LLC
- Inventors: Jagannathdas Rath; Kalyan C. Gunda
- Web page: https://patentgrep.com/patent/US20230267100A1

## CPC

- G06F 11/1453: {using de-duplication of the data}
- G06F 16/1774: {Locking methods, e.g. locking methods for file systems allowing shared and concurrent access to files}
- G06F 11/1451: {by selection of backup contents}
- G06F 11/1464: {for networked environments}
- G06F 11/1469: {Backup restoration techniques}
- G06F 16/164: {File meta data generation}
- G06F 16/1734: {Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs}
- G06F 16/1748: {De-duplication implemented within the file system, e.g. based on file segments (de-duplication techniques in storage systems for the management of data blocks G06F3/0641)}
- G06F 2201/80: Database-specific techniques
- G06F 2201/825: the problem or solution involving locking
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Embodiments for retention locking a deduplicated file stored in cloud storage by defining object metadata for each object of the file, and comprising a lock count and a retention time based on an expiry date of the lock, with each object having segments, the object metadata further having a respective expiry date and lock count for each segment, where at least some segments are shared among two or more files. Also updating the lock count and retention time for all segments of the file being locked; and if the object is not already locked, locking the object using a retention lock defining a retention time and updating the object metadata with a new lock count and the retention time, otherwise incrementing the lock count and updating the retention time for the expiry date if expiry date of a previous lock is older than a current expiry date.

## Claims

### Claim 1

A method of providing retention lock governance (RLG) and retention lock compliance (RLC) protection to deduplicated data stored in cloud storage, comprising:
determining which of the RLG and RLC mode of retention is used to originally lock an object in the cloud storage;
determining a lock time of the retention;
determining an amount of data shared between the RLG and RLC retention locks; and
copying, in response to a new lock request and based on the lock time of the retention and amount of shared data, the object to a new object locked by a new lock mode from the original lock mode.

### Claim 2 (depends on 1)

The method of claim 1 further comprising:
defining object metadata for the object comprising a lock mode, a lock count and a retention time based on an expiry date of the retention lock, wherein the object comprises a plurality of segments, the object metadata further comprising a respective expiry date and lock count for each segment of the object, and further wherein at least some segments are shared among two or more files;
updating, for the copied object, the lock count and retention time in the metadata object for all segments of the file being locked;
updating the lock mode of the copied object to the new lock mode; and
incrementing, in the metadata object of the copied object, the lock count and updating the retention time for the expiry date if expiry date of the original lock is older than the new lock mode expiry date.

### Claim 3 (depends on 2)

The method of claim 2 wherein the object is copied to the new object when threshold values are met for a lock time of an original RLC retention lock and an amount of data shared between the RLG and RLC lock modes.

### Claim 4 (depends on 3)

The method of claim 3 wherein the object is copied to the new object when certain heuristic measurements between the RLG and RLC lock modes are met.

### Claim 5 (depends on 1)

The method of claim 1 wherein the object is originally locked using a retention lock software process provided by a cloud provider supporting the cloud storage through an application programming interface (API).

### Claim 6 (depends on 5)

The method of claim 5 wherein the retention lock software process is one of a synchronous process and an asynchronous process with a callback function.

### Claim 7 (depends on 1)

The method of claim 1 wherein the deduplicated data is produced by a deduplication backup system producing deduplicated segments within the object with different respective retention times.

### Claim 8 (depends on 7)

The method of claim 7 wherein the cloud storage comprises storage media resident in a cloud computing network maintained by a cloud service provider, and provided for long term retention of data processed using the metadata, and further wherein the deduplication backup system is executed by a data storage server running a Data Domain file system (DDFS).

### Claim 9 (depends on 2)

The method of claim 2 wherein the object expiry date metadata element comprises a maximum expiry date among all the segments, and the object lock count metadata element comprises a sum of the lock counts of all the segments.

### Claim 10 (depends on 4)

The method of claim 4 wherein the RLG retention lock can be reverted, and the RLC retention lock cannot be reverted.

### Claim 11 (depends on 10)

The method of claim 10 further comprising reverting the RLG by:
decrementing the lock count of the object and on each segment of the object;
reassessing the segments of the object to find a remaining maximum expiration date; and
locking the object again for a duration of the maximum expiry date, if the remaining maximum expiry date is not less than the remaining maximum expiration date.

### Claim 12 (depends on 11)

The method of claim 11 wherein the locking is performed by temporarily unlocking the object and re-locking it with the remaining maximum expiry date.

### Claim 13 (depends on 12)

The method of claim 12 further comprising:
deleting the expiry date of a segment when the lock count of the segment is decremented to zero; and
reverting the RLG lock when the lock count of the object is decremented to zero.

### Claim 14 (depends on 4)

The method of claim 4 wherein the object metadata for the object further comprises a lock mode indicator, and wherein the step of determining if the object is already locked further comprises determining if the object is already locked in a different lock mode between the RLG and RLC lock modes, and if so, copying the object to a new object locked by the new lock mode.

### Claim 15 (depends on 14)

The method of claim 14 further comprising:
updating the lock mode indicator of the copied object with the new lock mode; and
updating the retention time of the copied object with a new retention time for the new lock mode.

### Claim 16

A system for providing retention lock governance (RLG) and retention lock compliance (RLC) protection to deduplicated data stored in cloud storage, comprising:
a component determining which of the RLG and RLC mode of retention is used to originally lock an object in the cloud storage, and determining a lock time of the retention; and
another component determining an amount of data shared between the RLG and RLC retention locks, and copying, in response to a new lock request and based on the lock time of the retention and amount of shared data, the object to a new object locked by a new lock mode from the original lock mode.

### Claim 17 (depends on 16)

The system of claim 16 further comprising:
yet another component defining object metadata for the object comprising a lock mode, a lock count and a retention time based on an expiry date of the retention lock, wherein the object comprises a plurality of segments, the object metadata further comprising a respective expiry date and lock count for each segment of the object, and further wherein at least some segments are shared among two or more files;
an updater updating, for the copied object, the lock count and retention time in the metadata object for all segments of the file being locked, and updating the lock mode of the copied object to the new lock mode; and
an increment component incrementing the lock count and updating the retention time for the expiry date if expiry date of the original lock is older than the new lock mode expiry date.

### Claim 18 (depends on 17)

The system of claim 17 wherein the object is originally locked using a retention lock software process provided by a cloud provider supporting the cloud storage through an application programming interface (API), and wherein the retention lock software process is one of a synchronous process and an asynchronous process with a callback function.

### Claim 19 (depends on 18)

The system of claim 18 wherein the deduplicated data is produced by a deduplication backup system producing deduplicated segments within the object with different respective retention times, and wherein the cloud storage comprises storage media resident in a cloud computing network maintained by a cloud service provider, and provided for long term retention of data processed using the metadata, and further wherein the deduplication backup system is executed by a data storage server running a Data Domain file system (DDFS).

### Claim 20

A tangible computer program product having stored thereon program code that when executed by a processor, cause the processor to perform a method of providing retention lock governance (RLG) and retention lock compliance (RLC) protection to deduplicated data stored in cloud storage, comprising:
determining which of the RLG and RLC mode of retention is used to originally lock an object in the cloud storage;
determining a lock time of the retention;
determining an amount of data shared between the RLG and RLC retention locks; and
copying, in response to a new lock request and based on the lock time of the retention and amount of shared data, the object to a new object locked by a new lock mode from the original lock mode.
