Dynamic WORM Locking for Deduplicated Secondary Copies

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Deduplicated secondary copies do not readily fit within the usage patterns of WORM-enabled storage, leading to undesirable side-effects such as holding original reference data for longer periods due to the persistence of older reference data.

Innovation Solution

A data storage management system that enhances WORM-enabled storage platforms to optimize the storing and retention of deduplicated secondary copies by configuring WORM retention parameters and periodically sealing deduplication databases (DDBs), modulating WORM lock duration based on DDB sealing frequency, and pruning eligible copies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If WORM locking is applied to deduplicated secondary copies, then data security and immutability are improved, but storage duration and capacity requirements increase due to the persistence of older reference data

Engineering Contradiction:

Improvedata securityVSAvoidstorage duration

Core Design Contradiction:

ReliabilityVSDuration of action of stationary object

Solution Approach 1:

The system dynamically adjusts WORM lock durations for different data objects based on their reference patterns. Instead of applying a uniform static lock period, the system monitors which objects are referenced by subsequent deduplicated copies and selectively extends WORM locks only for those objects that remain references, allowing other objects to be released earlier.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system changes the WORM lock duration parameter from a fixed value to a variable value that depends on the specific data object's reference lifecycle. By calculating optimal lock periods based on actual reference patterns and extending locks incrementally only when necessary, the system optimizes the balance between security requirements and storage efficiency.

Inventive Principle:

Principle #35Parameter changes

2Reliability

If WORM locking is applied to deduplicated secondary copies, then data security is improved, but storage capacity requirements increase

Engineering Contradiction:

Improvedata securityVSAvoidstorage capacity

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The system continuously identifies and releases WORM locks on data objects that are no longer referenced by any active deduplicated copies. By monitoring reference patterns and automatically discarding (releasing) locks on obsolete objects, the system recovers storage capacity while maintaining security on objects that still require protection.

Inventive Principle:

Principle #34Discarding and recovering

Solution Approach 2:

Instead of applying WORM locks to all deduplicated copies uniformly, the system applies locks partially and selectively only to the extent necessary for security. By calculating the minimum required lock duration for each object based on actual reference needs, the system avoids excessive locking that would unnecessarily consume storage capacity.

Inventive Principle:

Principle #16Partial or excessive action

3Stability of the object's composition

If older reference data is retained for extended periods, then deduplication integrity is maintained, but storage costs increase

Engineering Contradiction:

Improvededuplication integrityVSAvoidstorage costs

Core Design Contradiction:

Stability of the object's compositionVSLoss of energy

Solution Approach 1:

The system implements continuous feedback monitoring of data object reference patterns to determine when WORM locks can be safely released. By tracking which objects are referenced by subsequent deduplicated copies and using this feedback to dynamically adjust lock durations, the system maintains deduplication integrity while minimizing unnecessary storage retention.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system periodically reviews and evaluates the reference patterns of data objects under WORM locks, adjusting lock durations based on observed usage patterns. This periodic assessment allows the system to maintain integrity during active reference periods while releasing locks during periods when objects are no longer needed, reducing overall storage costs.

Inventive Principle:

Principle #19Periodic action

Data Source

PatentUS20250307218A1Optimizing retention of deduplicated copies at write-once read-many (WORM)-enabled storage

Publication Date: 2025.10.02 COMMVAULT SYSTEMS INC

AI summary

A data storage management system is enhanced to accommodate, and moreover to optimize, the storing and retention of deduplicated secondary copies at write-once read-many (WORM) enabled storage platforms. Enhancements include without limitation: user interface (UI) options to enable WORM functionality for secondary storage, whether used for deduplicated or non-deduplicated secondary copies; enhancements to secondary copy (e.g., deduplication copy, backup) operations; and pruning changes. The storage manager is generally responsible for managing the creation, tracking, and deletion of secondary copies, with and without deduplication. Media agents that store secondary copies to and prune them from the WORM-enabled storage platforms also are enhanced for communicating and interoperating with both bucket-level and object-level WORM-enabled storage platforms to implement the features disclosed herein.