Horizontal File Retention Locking for Large Namespace Backups
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data backup systems face inefficiencies in retention locking large namespaces due to the need to copy and lock millions of files, which requires significant computing resources and time, leading to application quiesce during the process.
Innovation Solution
The method involves generating point-in-time copies of a namespace and applying retention locks to horizontal files, rather than individual files, reducing the computational burden by stacking files into a flat structure using techniques like Virtual Synthetic processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If individual files are copied and retention locked in a traditional namespace, then data protection is achieved, but computing resources and time are excessively consumed
Solution Approach 1:
The patent merges millions of individual files into a single horizontal file within an object storage namespace. This consolidation allows the retention lock to be applied to one aggregated object rather than millions of individual files, dramatically reducing the computational overhead while maintaining data protection integrity across all original files
Solution Approach 2:
The patent creates a copy of the active namespace in an object storage namespace and transforms it into a horizontal file structure. This copying approach enables efficient retention locking on the copied data without affecting the original active namespace, achieving data protection with minimal resource consumption
2Reliability
If all files are enumerated for retention locking, then complete data protection is achieved, but application downtime increases
Solution Approach 1:
The patent performs the namespace copy and horizontal file generation as a preliminary action before the retention locking phase. By pre-processing the data into an optimized horizontal structure, the actual retention lock application becomes rapid and does not require enumerating individual files, thereby minimizing application downtime while ensuring complete data protection
Solution Approach 2:
The patent transitions from a traditional vertical file structure (millions of individual files) to a horizontal file structure (single aggregated file). This dimensional change in data organization enables the retention locking mechanism to operate on a coarser granularity level, reducing the time required to achieve complete data protection across the entire namespace
Data Source
AI summary
One example method includes generating in a shared protection namespace a first point-in-time copy of a first working frozen copy of an active namespace that includes first files associated with the active namespace that are stacked in a first horizontal file. A retention lock is applied to the first horizontal file. A second point-in-time copy of a second working frozen copy of the active namespace that includes second files associated with the active namespace that are stacked in a second horizontal is generated. A retention lock is applied to the second horizontal file. The second horizontal file is generated by copying files from the first horizontal file into the second horizontal file and copying files from the second working frozen copy of the active namespace into the second horizontal file.