Automatic WORM-Retention State Transitions in File Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Manual designation of write-once-read-many (WORM) files in large computing systems is inefficient and performance-intensive due to the need for separate file operations to determine which files should be WORMED, leading to reduced system performance from unnecessary reads during file scans.
Innovation Solution
Implementing automatic WORM-retention state transitions integrated within the file system, where WORM file checks occur during natural file access, allowing the retention policy to be quickly referenced, eliminating the need for additional commands and reducing unnecessary file checks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual WORM designation is implemented through separate file operations and scans, then WORM file checks can be performed, but system performance deteriorates due to unnecessary reads during file scans
Solution Approach 1:
The patent merges the WORM file check operation with natural file access operations. Instead of performing separate scans to identify WORM files, the system integrates the check into the existing file access path, so that every natural file access automatically triggers a WORM status verification without requiring additional dedicated scan operations.
Solution Approach 2:
The patent implements preliminary action by maintaining a retention policy that pre-identifies candidate files for WORM status based on metadata criteria (file type, owner, creation date). This preliminary identification allows the system to quickly determine WORM eligibility during natural file access without performing full file scans, reducing the computational overhead.
2Ease of operation
If manual WORM designation is implemented, then administrators can control WORM file designation, but device complexity increases due to the need for separate file operations
Solution Approach 1:
The patent implements self-service by enabling the file system to automatically determine and enforce WORM status based on pre-configured retention policies. The system monitors file metadata and automatically applies WORM protection when criteria are met, eliminating the need for administrators to manually issue commands or track which files require WORM status.
Solution Approach 2:
The patent makes the retention policy mechanism universal by designing it to handle multiple functions: identifying candidate files, determining WORM eligibility, and enforcing WORM status all through a single integrated policy framework. This multi-functional approach consolidates what would otherwise require separate operational mechanisms.
3Productivity
If WORM file checks are performed during natural file access, then system performance is enhanced, but the complexity of integrating retention policy increases
Solution Approach 1:
The patent introduces an intermediary retention policy module that sits between the file system and the WORM enforcement mechanism. This intermediary layer receives natural file access requests, checks them against retention policy criteria using metadata, and determines whether WORM status should be applied. This mediator approach manages the integration complexity by providing a clear interface and decision-making layer.
Data Source
AI summary
Example embodiments relate to automatic WORM-retention state transitions. In example embodiments, a storage computing device may detect a request to access, via a file system, a file that is associated with a first retention state. The first retention state may indicate either a first type of WORM-retention protection for the file or no WORM-retention protection for the file. The storage computing device may determine, in response to the request, that the file should be designated with a second retention state. The second retention state may indicate a second type of WORM-retention protection for the file. The determination may be based on a retention policy file that is tightly integrated with the file system and metadata of the file. The storage computing device may transition the file (e.g., by communicating with the file system) to be associated with the second retention state instead of the first retention state.