Incremental Backup Baselines After Restore Operations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems inefficiently utilize resources and network bandwidth by performing full or incremental backup snapshots after a restore operation, as they either redundantly transmit stored data or include unnecessary data changes.
Innovation Solution
Implementing a constructive incremental backup snapshot that only sends data changed since a new tracking ID was created, reducing the need for full backups and minimizing resource usage by focusing on data changes post-restore.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a full backup snapshot is performed after a restore operation, then the backup system ensures complete data protection, but network bandwidth and storage resources are wasted by transmitting redundant data
Solution Approach 1:
The patent extracts only the necessary backup data by identifying and transmitting only the delta changes (new or modified files) since the restore operation, rather than transmitting the complete file system state. This is achieved through change detection mechanisms that compare the restored state with the current state to identify only the differences that need to be backed up.
Solution Approach 2:
The backup process is segmented into identifying changes, preparing only changed files for backup, and transmitting only those specific files. The system divides the backup operation into discrete steps: detecting changes since restore, selecting affected files, and transmitting only those files to the backup system, thereby reducing overall data transmission volume.
2Productivity
If an incremental backup snapshot is performed after a restore operation, then data changes are captured, but unnecessary data changes from before the restore are included
Solution Approach 1:
The system performs preliminary change detection by establishing a baseline of what changed since the restore operation before initiating the backup process. Tracking identifiers or change logs are maintained to record modifications occurring after restore, allowing the backup system to pre-identify which files need to be included and which can be excluded from the backup snapshot.
3Reliability
If traditional backup methods are used after restore, then complete data is backed up, but resource consumption increases significantly
Solution Approach 1:
The backup system incorporates feedback mechanisms where the restore target provides information about changes since restore (such as modification timestamps, change detection logs, or delta data) back to the backup system. This feedback enables the backup system to adjust its behavior and only process files that have changed, optimizing resource utilization while maintaining protection integrity.
Data Source
AI summary
A request to restore a specific backup instance is received. In response to the received request to restore the specific backup instance, a new reference backup instance based on the specific backup instance stored at the storage controlled by the backup system is created at a storage controlled by a backup system. Data associated with the specific backup instance is provided to a recipient system from the storage associated with a backup system. A constructive incremental backup snapshot of the recipient system is performed based on the new reference backup instance.