Backup Metadata Management for Incomplete Save Set Cleanup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Incomplete backups on storage devices due to failures during data transfer from client devices to storage devices result in unused storage space, and compatibility issues arise when upgrading application versions, leading to restoration challenges.
Innovation Solution
A method and system for detecting and deleting uncommitted save sets from storage devices and updating metadata formats to ensure compatibility with new application versions, utilizing lock files and metadata databases for identification and management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If backups are performed continuously to ensure data availability, then data protection reliability is improved, but storage space is wasted by incomplete backups that cannot be restored
Solution Approach 1:
The system performs preliminary actions by creating lock files before backups commence and deleting them only after successful completion. This preliminary marking mechanism allows the system to identify and clean up incomplete backups, freeing storage space while maintaining reliable backup operations.
Solution Approach 2:
The backup system serves itself by automatically detecting incomplete backups through the absence of lock files and initiating deletion of these incomplete save sets. This self-service mechanism eliminates the need for manual intervention to free storage space while maintaining backup reliability.
2Adaptability or versatility
If old backups are retained to provide restoration options, then data recovery capability is improved, but storage space consumption increases
Solution Approach 1:
The system discards incomplete backups that cannot provide recovery value and recovers storage space by deleting them. By using lock files to identify complete versus incomplete backups, the system selectively retains only those backups that can actually restore data, thereby maintaining recovery capability while reducing storage consumption.
3Adaptability or versatility
If metadata is maintained for all backup versions to enable restoration, then restoration flexibility is improved, but system complexity increases
Solution Approach 1:
The system extracts the essential metadata needed for restoration by maintaining lock file information that identifies complete backups. This extraction approach focuses on retaining only the critical metadata (lock file presence) required for restoration decisions, rather than maintaining complex metadata for all backup versions, thereby reducing system complexity while preserving restoration flexibility.
Data Source
AI summary
Embodiments are described for improved management of backed up data from a client device to a storage device. The storage device may be coupled to a backup server across a network. A backup of data from an application on a client device to a storage device may fail while the backup is in progress. Systems and methods described herein can detect and remove incomplete backups. Systems and methods described herein can also scan for, and delete, save sets of a backups within a specified time interval. Systems and methods described herein can update metadata that describes existing backup data so that existing backups may be used with an updated or changed application software.