Adaptive Backup Scheduling via Reliability Metrics
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data backup systems face challenges in ensuring robustness due to unreliable scheduling, particularly when devices go offline or experience poor connectivity, leading to potential data loss and corruption, and inefficient pruning practices that can delete critical backup data.
Innovation Solution
An adaptive data backup scheduling method that modifies backup frequencies based on time differentials and reliability metrics, such as connectivity and environmental conditions, to ensure more frequent backups during offline periods and unreliable conditions, and adjusts pruning schedules to retain critical data points.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If backup frequency is increased during offline periods, then data recovery robustness is improved, but system resource consumption increases
Solution Approach 1:
The backup system dynamically adjusts backup frequency based on device availability and reliability metrics. During offline periods or when reliability is low, the system automatically increases backup frequency to ensure data safety. When the system is stable and online, it reduces frequency to conserve resources. This dynamic adaptation resolves the contradiction by making backup intensity variable rather than fixed.
Solution Approach 2:
The system changes the backup schedule parameter based on detected conditions such as device offline status or reliability metric thresholds. When reliability drops below a threshold or devices go offline, the backup interval parameter is adjusted to create more frequent backups. This parameter adaptation allows the system to maintain high reliability during critical periods while using normal resource levels during stable periods.
2Reliability
If backup frequency is increased to ensure data safety, then data integrity is improved, but backup time consumption increases
Solution Approach 1:
The system implements periodic backup actions with variable intervals based on system conditions. Instead of continuous or uniformly frequent backups, it uses timed intervals that adapt to reliability metrics and device availability. This periodic approach with dynamic timing ensures data integrity when needed while avoiding unnecessary time consumption during stable periods.
Solution Approach 2:
The system performs preliminary assessments of device availability and reliability metrics before executing backups. By evaluating conditions in advance, it determines whether increased backup frequency is necessary, preventing unnecessary backup operations that would consume time without adding value to data integrity.
3Quantity of substance
If pruning is performed to manage storage space, then storage efficiency is improved, but risk of deleting critical data increases
Solution Approach 1:
The pruning process incorporates feedback mechanisms that evaluate backup criticality before deletion. The system monitors reliability metrics, device availability history, and backup importance to determine which backups can be safely pruned. This feedback loop prevents deletion of critical data while enabling storage space management through selective pruning of redundant backups.
Solution Approach 2:
The system applies different pruning strategies to different backup data based on their characteristics and criticality. Rather than uniform pruning, it identifies and protects critical backup points while allowing non-critical backups to be pruned for storage efficiency. This localized differentiation resolves the contradiction by treating different data differently based on their retention requirements.
Data Source
AI summary
The disclosure provides methods and systems to perform data backups of protected data. According to an embodiment, a nominal backup schedule is received, and a time differential between the nominal backup schedule and a current time metric is determined. If the time differential is greater than a threshold, the backup schedule is modified so that times indicated in the modified backup schedule are at a higher frequency than a frequency of the indicated times of the nominal backup schedule. In another embodiment, if a reliability metric is greater than a corresponding threshold, the backup schedule is modified so that times indicated in the modified backup schedule are at a higher frequency than a frequency of the indicated times of the nominal backup schedule.