Graduated Backup Version Expiration via Currency Span Curtains
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The accumulation of multiple versions of backed-up data leads to inefficiency, chaos, and high storage costs, as existing methods fail to effectively manage data version expirations, often deleting valuable versions too early or too late, and do not account for the number of existing versions when determining expiration times.
Innovation Solution
Implementing policies and rules that determine the expiration time of backup versions based on both the creation time of the current and successive versions, using a 'currency span' concept, where designated time points ('curtains') dictate the lifespan of each version, ensuring only the current version remains unexpired, with others being automatically deleted at calculated expiration times.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If continuous backups are performed to ensure data availability, then data recovery reliability is improved, but storage costs and system complexity increase due to accumulation of millions of versions
Solution Approach 1:
The system performs preliminary actions by calculating and setting expiration times for backup versions before they accumulate excessively. The expiration time is determined in advance based on the currency span formula, preventing uncontrolled accumulation of backup versions and optimizing storage resource usage before the problem escalates.
Solution Approach 2:
The system changes the parameter of backup version retention by introducing dynamic expiration times rather than static retention policies. The expiration time is calculated using the currency span parameter, which transforms how backup versions are managed from indefinite retention to time-bound retention, reducing storage costs while maintaining necessary versions.
2Ease of operation
If simple expiration dates are set for backup versions, then storage management is simplified, but valuable versions may be deleted too early without considering the number of existing versions
Solution Approach 1:
The system uses feedback by considering the creation time of the current backup version and the successive backup version when determining expiration time. This feedback mechanism ensures that expiration decisions are made with knowledge of the version history, preventing premature deletion of valuable versions while maintaining operational simplicity.
Solution Approach 2:
The system performs preliminary calculation of expiration times using the currency span formula before backup versions are deleted. This preliminary action ensures that valuable versions are not deleted too early by calculating the appropriate retention period in advance, while still maintaining simplified storage management through automated expiration.
3Reliability
If all backup versions are retained for long periods to ensure data availability, then data recovery options are improved, but storage costs increase rapidly with little return on investment
Solution Approach 1:
The system changes the parameter of data retention from indefinite to time-bound by introducing expiration times calculated using the currency span formula. This parameter change reduces the quantity of backed up data by automatically expiring versions that are no longer needed, while preserving data recovery options for versions within their useful currency span.
Solution Approach 2:
The system applies discarding and recovering by automatically deleting backup versions that have exceeded their expiration time calculated through the currency span formula. This process discards redundant data that provides little recovery value while maintaining necessary versions for data recovery, optimizing the balance between storage costs and recovery options.
4Adaptability or versatility
If files are backed up independently at high granularity, then flexibility in managing individual files is improved, but management complexity increases significantly compared to container-level backups
Solution Approach 1:
The system applies universality by implementing a unified expiration time calculation mechanism that works across different backup granularities (individual files and containers). The currency span formula provides a universal approach to determining expiration times regardless of the backup level, maintaining file management flexibility while reducing complexity through consistent rules.
Data Source
AI summary
In one example, a method for managing backed up data includes marking a current backup version to indicate that the current backup version has no expiration time, and then determining a currency span for a backup version that immediately precedes the current backup version. Next, one or more curtains crossed by the currency span are identified, each curtain being associated with a respective expiration rule. The expiration rules are then applied to the immediately preceding backup version, and an expiration time assigned to the immediately preceding backup version based on application of the expiration rules.