Read-Only WORM File Retention with Event-Triggered Deletion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data storage systems lack an efficient method to automatically set and manage event-based retention periods for Write Once, Read Many (WORM) files without requiring proprietary APIs or privileged delete features, limiting the flexibility and automation of WORM file deletion.
Innovation Solution
Implement an 'event-retain' property on data volumes to convert regular files to event-based WORM files, set retention times using the 'set atime' command after the file is committed, and store the retention date in the rarely used last access time attribute, ensuring the file system enforces immutability and allows automatic deletion upon expiration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If regular files are converted to WORM files with fixed retention periods, then data integrity is improved, but flexibility in managing retention periods is worsened
Solution Approach 1:
The patent implements dynamic retention periods for WORM files by introducing event-based triggers that can modify the retention duration after the file is initially committed. The system allows retention periods to be extended or modified based on specific events (such as legal holds, audits, or user actions), transforming the static retention model into a dynamic one that adapts to changing requirements while maintaining data integrity.
2Productivity
If automatic deletion is implemented for WORM files, then storage efficiency is improved, but control over file deletion is worsened
Solution Approach 1:
The patent implements a feedback mechanism where the system automatically monitors WORM files for expiration events and triggers deletion only when appropriate conditions are met. The system provides feedback loops that allow administrators to set up event-based triggers (such as legal holds, audit requirements, or custom events) that can prevent or extend deletion, thereby maintaining both automation and control. The system continuously monitors file status and adjusts deletion timing based on feedback from various sources.
3Adaptability or versatility
If proprietary APIs are required for WORM file management, then functionality is improved, but system complexity is worsened
Solution Approach 1:
The patent implements a universal event-based retention framework that works across multiple file systems and storage platforms without requiring proprietary APIs. The system uses standard file system attributes (such as extended attributes or metadata fields) to store retention information and event triggers, making it compatible with different operating systems and file systems. This multi-functional approach allows the same mechanism to handle WORM file management across diverse environments, reducing the need for platform-specific implementations.
4Extent of automation
If retention periods are set at file creation, then automation is improved, but ability to respond to events is worsened
Solution Approach 1:
The patent implements preliminary action by setting up event-based triggers and retention policies at file creation time, while simultaneously preparing the system to respond to future events. The system pre-configures retention periods and monitors for specific events (such as legal holds, audits, or user actions) that may require modification. This allows the system to automatically adjust retention periods in response to events without requiring manual intervention, combining the benefits of initial automation with event-driven adaptability.
Data Source
AI summary
Systems and methods are disclosed for implementing an event based retention schedule for a read only file. When a regular file is to be converted to an event based retention read only file, an “event-retain” property may be enabled on the file allowing the feature to be implemented. Then, that file may have its permissions changed to read only. This will allow the file to be changed to a read only file without using a default retention time. Then, once the event is triggered, the retention time may be set so the file can be scheduled for automatic deletion.