Storage System Retention Period Management via Event-Based Adjustment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data storage systems lack the ability to enforce retention periods for data, leading to accidental or intentional deletion or modification of critical records, which can result in data loss or legal violations, and do not allow users to specify a time frame for data retention or modification prevention.
Innovation Solution
A method and system that allow a host to request and manage retention periods for data stored in a storage system, enabling the extension or reduction of retention periods based on events, with authentication to prevent unauthorized changes, and using retention classes to simplify the management of large data groups.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional storage systems use read-only file status, then data cannot be modified or deleted, but the system lacks the ability to enforce time-based retention periods and administrators can still change the status
Solution Approach 1:
The system performs preliminary action by automatically enforcing retention periods without requiring continuous administrator intervention. The storage system proactively manages data retention by tracking retention periods and automatically allowing or blocking deletion requests based on whether the retention period has expired, eliminating the need for complex manual retention management while ensuring reliable data retention.
2Reliability
If data is written to non-overwrite media, then data cannot be modified, but the media cannot be reused and replacement requires physical destruction
Solution Approach 1:
The system applies dynamics by enabling the retention period to be dynamically adjusted based on changing needs. The storage system allows hosts to request reduction of retention periods for data that has been retained longer than originally specified. This dynamic adjustment mechanism maintains data integrity during the retention period while providing adaptability when retention is no longer needed, allowing media to be reused without physical destruction.
3Adaptability or versatility
If retention periods are extended for event-based reasons, then data can be kept longer than initially specified, but the system lacks automated mechanisms for event-driven retention management
Solution Approach 1:
The system implements feedback by enabling hosts to send requests to the storage system to reduce retention periods based on event-driven conditions. The storage system receives and processes these requests, automatically adjusting retention periods when events occur (such as data no longer needing retention). This feedback mechanism provides event-based flexibility while maintaining automation, as the system automatically handles retention period adjustments without manual intervention.
4Reliability
If authentication is required for retention period changes, then unauthorized changes are prevented, but the process becomes more complex
Solution Approach 1:
The system applies self-service by having the storage system automatically authenticate and process retention period requests without requiring complex authentication workflows. The host sends a request to reduce a retention period, and the storage system automatically verifies authority and executes the change. This self-service approach maintains security through automated authentication while minimizing process complexity, as the system handles authentication internally without requiring additional user actions or complex verification procedures.
Data Source
AI summary
One embodiment is a method and apparatus for modifying retention periods in a storage system, in which previously defined retention periods for units of data may be reduced. In another embodiment, the retention period of a unit of data may be modified in response to the occurrence of an event by renewing previously defined retention periods until the occurrence of the event is detected. If the occurrence of the event is detected, a retention period associated with that event may be established for the unit of data. In yet another embodiment, retention classes are used to define retention periods for units of data so that the retention period of a unit of data may be modified without modifying the unit of data itself. In a further embodiment, a request to the storage system to reduce a retention period includes authentication information that the storage system may use to verify the request.