Compliance Recycling Algorithm for Targetless Snapshot Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
High capacity data storage systems face resource exhaustion due to regular creation of targetless snapshots without adequate discard mechanisms, which inhibits the implementation of different snapshot schedules and leads to unnecessary resource consumption.
Innovation Solution
A targetless snapshot scheduler that implements concurrent independent snapshot schedules and a compliance recycling algorithm to selectively discard oldest snapshots not in use, while exempting in-use snapshots from discard, thereby managing resource usage efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If targetless snapshots are created regularly without discard mechanisms, then snapshot availability is improved, but resource consumption increases and leads to resource exhaustion
Solution Approach 1:
The patent implements a compliance recycling algorithm that automatically discards old targetless snapshots when a predetermined count is exceeded. The algorithm determines whether snapshots are in use before discarding them, and recovers resources by removing snapshots that are no longer needed while maintaining those that are still in use, thus resolving the contradiction between maintaining snapshot availability and preventing resource exhaustion
Solution Approach 2:
The system employs a feedback mechanism where the snapshot scheduler continuously monitors the number of existing targetless snapshots and their usage status. When the snapshot count exceeds the predetermined limit, the system receives feedback about which snapshots are in use and adjusts its behavior by exempting in-use snapshots from discard, thereby dynamically balancing resource consumption with snapshot availability
2Quantity of substance
If snapshots are discarded to manage resources, then resource utilization is improved, but risk of discarding in-use snapshots increases
Solution Approach 1:
The compliance recycling algorithm incorporates a feedback loop that checks whether each snapshot is in use before discarding it. The system receives usage status information and adjusts its discard decisions accordingly, exempting snapshots that are currently in use from the discard process. This feedback mechanism ensures that resource management actions do not compromise snapshot utility
Solution Approach 2:
The snapshot management system performs self-service by automatically determining which snapshots are in use and which can be safely discarded without external intervention. The algorithm autonomously monitors snapshot usage, makes intelligent decisions about which snapshots to retain or discard, and manages resources accordingly, reducing the risk of inadvertently discarding in-use snapshots
3Quantity of substance
If a predetermined snapshot count limit is enforced, then resource exhaustion is prevented, but flexibility in snapshot scheduling is reduced
Solution Approach 1:
The system implements dynamic snapshot management where the effective snapshot count can flexibly exceed the predetermined limit when in-use snapshots are present. The compliance recycling algorithm dynamically adjusts which snapshots count toward the limit based on their usage status, allowing the system to adapt to changing requirements while maintaining resource management control. This dynamic approach preserves schedule flexibility without compromising resource management
Solution Approach 2:
The system changes the parameter of snapshot count enforcement by introducing an exemption mechanism for in-use snapshots. Instead of rigidly enforcing a fixed count limit, the system modifies how the limit is applied by excluding certain snapshots from the count based on their usage status. This parameter change allows flexible snapshot scheduling while maintaining resource management through the predetermined count limit
Data Source
AI summary
Targetless snapshots that are in use are excluded from discard and exempted from inclusion against a snapshot retention count limit. Snapshots that are linked to a target volume are considered to be in use. Snapshots having a persist attribute set are considered to be in use. Snapshots having an expiration attribute set are considered to be in use until at least the expiration time. Snapshots having an age limit attribute set are considered to be in use until reaching at least the specified age. The snapshot retention count limit can be updated with a command. Other commands discard snapshots created before a specified time or older than a specified age, provided the snapshots are not in use. A terminate all command prompts discard of all snapshots that are not in use.