Reference-Based Air-Gapped Backup for No-Change Snapshots
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Backup systems face inefficiencies and increased costs due to no-change backup scenarios, where data remains unchanged between scheduled backups, leading to unnecessary resource consumption, redundant data transfers, and complex restore processes.
Innovation Solution
Implementing a reference-based technique that checks for data changes and creates a reference to the previous backup if no changes are detected, avoiding unnecessary data transfers and storage by incrementing a reference counter.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional backup systems perform scheduled backups regardless of data changes, then comprehensive data protection is ensured, but storage utilization increases and network bandwidth is consumed unnecessarily
Solution Approach 1:
The system performs a preliminary check to detect data changes before initiating the backup process. By checking whether data has changed since the last backup and only proceeding if changes are detected, the system avoids unnecessary network transfers and storage operations, thereby reducing network bandwidth consumption while maintaining data protection reliability
Solution Approach 2:
The system changes the backup execution parameter from a fixed schedule-based approach to a dynamic condition-based approach. The backup operation is conditioned on data change detection, allowing the system to adapt its behavior based on the actual state of the data, thus eliminating redundant backups and reducing network bandwidth usage
2Reliability
If traditional backup systems perform full backup workflows for no-change scenarios, then backup consistency is maintained, but processing time increases and resources are wasted
Solution Approach 1:
The system performs a preliminary data change detection step before initiating the backup workflow. By identifying no-change scenarios early in the process, the system can skip the time-consuming full backup workflow entirely, reducing processing time while maintaining backup consistency through conditional execution
Solution Approach 2:
The system applies partial action by performing only the necessary data change detection step rather than executing the complete backup workflow. This partial execution approach is sufficient to maintain backup consistency in no-change scenarios while significantly reducing the time and resources consumed compared to performing full backup operations
3Reliability
If backup systems transfer and store data for no-change scenarios, then backup completeness is ensured, but storage utilization increases unnecessarily
Solution Approach 1:
The system performs a preliminary check to detect data changes before initiating data transfer and storage operations. By identifying no-change scenarios in advance, the system avoids transferring and storing redundant data, thereby reducing storage utilization while maintaining backup completeness through conditional execution of transfer and store operations
Solution Approach 2:
The system changes the backup execution parameter from unconditional to conditional based on data change detection. This parameter change enables the system to adapt its data transfer and storage behavior, executing these resource-intensive operations only when necessary, thus reducing storage utilization while ensuring backup completeness
4Adaptability or versatility
If backup systems create multiple identical backup instances, then recovery options are increased, but restore process complexity increases
Solution Approach 1:
The system performs a preliminary data change detection before creating backup instances. By identifying no-change scenarios, the system avoids creating duplicate backup instances, thereby reducing restore process complexity while maintaining adequate recovery options through selective backup creation
Solution Approach 2:
The system changes the backup creation parameter from unconditional to conditional based on data change detection. This enables the system to create backup instances only when necessary, reducing the number of identical backups and simplifying the restore process while maintaining sufficient adaptability for recovery scenarios
Data Source
AI summary
In some implementations, a computer system includes one or more processors and a non-transitory computer-readable medium storing programming for execution by the one or more processors. The programming includes instructions to receive a request to create a second air-gapped backup corresponding to a second transient backup. The second transient backup is subsequent to a first transient backup corresponding to a first air-gapped backup. The programming includes instructions to determine, in response to the request, whether the second transient backup matches the first transient backup, and to create, in response to determining that the second transient backup matches the first transient backup, a database entry for the second air-gapped backup that references the first air-gapped backup. The programming includes instructions to increment, in response to determining that the second transient backup matches the first transient backup, a reference counter for the first air-gapped backup.