Backup Initiation via Data Change Thresholds
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In enterprise environments, there is a risk of data loss between scheduled backup operations due to long time differences between backup sessions, leaving data unprotected until the next scheduled backup.
Innovation Solution
Implementing a backup/restore application that initiates backup operations based on data changes, using a write tracking driver and block-based bitmap to identify data changes exceeding a threshold, thereby reducing the window of potential data loss by initiating backups before the next scheduled operation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If scheduled backup operations are performed at fixed intervals, then the backup system is simple to manage and predict, but data protection is insufficient during long intervals between backups
Solution Approach 1:
The system performs preliminary actions by proactively initiating backup operations when data changes exceed the threshold before a scheduled backup occurs. The write tracking driver continuously monitors data changes and triggers an unscheduled backup in advance when significant changes are detected, ensuring data protection without waiting for the next scheduled interval.
Solution Approach 2:
The backup scheduling system transitions from a static fixed-interval approach to a dynamic adaptive approach. The system adjusts backup timing based on actual data change patterns, using the write tracking driver to detect changes and dynamically triggering backups when needed, making the backup frequency variable rather than constant.
2Reliability
If continuous monitoring of data changes is implemented, then timely backup initiation is achieved, but system resource consumption increases
Solution Approach 1:
The write tracking driver implements local quality monitoring by focusing surveillance on specific data blocks that have changed, rather than continuously monitoring all data. The block-based bitmap tracks changes at the block level, allowing the system to identify only the portions of data that require backup, reducing overall monitoring overhead.
Solution Approach 2:
The system uses a configurable threshold parameter to control when backups are triggered. By adjusting this threshold, the system balances between timely backup initiation and resource consumption - a higher threshold reduces the frequency of triggered backups and resource usage, while a lower threshold provides more timely protection.
3Reliability
If the backup threshold is set low, then more frequent backups are initiated providing better protection, but backup operations consume more time and resources
Solution Approach 1:
The system applies partial action by initiating backups only for the portions of data that exceed the change threshold, rather than performing full redundant backups every time. The block-based bitmap enables the system to identify and backup only the changed blocks, providing adequate protection while avoiding excessive backup operations.
Data Source
AI summary
Initiating backups based on data changes is described. A system identifies an amount of data changed for a client since a previous backup operation for the client. The system determines whether the amount of data changed meets a threshold requirement. The system initiates a backup operation for the client if the amount of data changed meets the threshold requirement.