Deduplicated Copy Retention on WORM Platforms with Adaptive Locking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Deduplicated secondary copies do not fit well within WORM-enabled storage platforms, leading to undesirable side-effects such as prolonged retention of reference data due to the risk of later data referencing, which increases storage needs and costs.
Innovation Solution
A data storage management system that optimizes the handling of deduplicated secondary copies by configuring WORM-enabled storage platforms through user interface enhancements, periodically sealing deduplication databases, and setting WORM lock durations based on retention periods and sealing frequencies, allowing for efficient pruning of copies once their retention period is met.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If WORM locking is applied to deduplicated secondary copies to ensure data protection, then data security and integrity are improved, but reference data must be retained much longer than desired, increasing storage capacity requirements and costs
Solution Approach 1:
The system performs preliminary actions by sealing the deduplication database at strategically chosen points in time before WORM retention periods end. This allows the system to proactively identify and prune reference data that will no longer be needed, rather than waiting passively until WORM locks expire. The sealing operation prepares the system in advance to release unnecessary data locks, optimizing storage utilization while maintaining security.
Solution Approach 2:
The system dynamically adjusts WORM lock durations and sealing frequencies based on actual data reference patterns and retention requirements. Rather than applying static, uniform retention periods to all data, the system adapts lock durations to match actual needs, releasing locks earlier for data that is no longer referenced and maintaining them longer for data that requires extended protection. This dynamic approach optimizes the balance between security and storage efficiency.
2Adaptability or versatility
If WORM lock duration is extended to ensure reference data availability, then data accessibility for future references is improved, but average data storage time increases, lowering productivity
Solution Approach 1:
The system implements feedback mechanisms that continuously monitor data reference patterns and retention status. By tracking which data is actually referenced and when, the system receives feedback on real-world data usage patterns. This feedback enables the system to adjust sealing schedules and WORM lock durations dynamically, ensuring data remains accessible when needed while avoiding unnecessary extension of retention periods for data that is no longer referenced, thereby improving storage efficiency.
Solution Approach 2:
The system employs periodic sealing operations at optimized intervals to review and adjust WORM lock status. Rather than maintaining continuous, static lock periods, the system periodically assesses data reference patterns and adjusts locking status accordingly. This periodic action allows the system to maintain data accessibility when needed while efficiently releasing locks for data that has completed its retention requirement, improving overall storage productivity.
3Reliability
If deduplicated secondary copies are retained longer to prevent future reference issues, then data reliability is improved, but storage costs and resource consumption increase
Solution Approach 1:
The system performs preliminary sealing operations on the deduplication database to proactively identify data that has completed its retention period. By sealing the database before WORM locks naturally expire, the system can提前 identify and release data that is no longer needed, preventing unnecessary accumulation of retained data. This preliminary action ensures data protection requirements are met while avoiding excessive storage resource consumption.
Data Source
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.