Centralized Backup Deletion Engine for Database Retention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data protection systems face performance issues when attempting to delete expired backups, often failing due to uncataloged or unlocated backup pieces, which complicates the deletion process and leads to incomplete operations.
Innovation Solution
A data protection system with a deletion engine that independently manages backup pieces based on retention settings, identifying and deleting expired backups without reliance on the database recovery manager, using a script to handle present and missing backup pieces, ensuring accurate and efficient deletion operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional data protection systems attempt to delete expired backups, then backup retention management is achieved, but deletion operations fail when backup pieces are not cataloged or cannot be located
Solution Approach 1:
The deletion process is segmented into distinct phases: identification of expired backups, separation of cataloged versus uncataloged pieces, and independent handling of each category. This segmentation allows the system to process deletions in manageable stages, reducing overall complexity while improving success rates.
Solution Approach 2:
The system performs preliminary identification and cataloging of backup pieces before deletion operations. By pre-identifying which pieces are cataloged and which are not, the system prepares the deletion process in advance, preventing failures during actual deletion and improving operational reliability.
2Productivity
If the system deletes uncataloged backup pieces, then complete backup cleanup is achieved, but performance issues arise due to lack of catalog information
Solution Approach 1:
The system introduces an intermediary mechanism that tracks backup piece locations independently of the traditional catalog. This intermediary layer allows the deletion process to access location information for uncataloged pieces without requiring full cataloging, thereby maintaining deletion efficiency while avoiding information loss.
Solution Approach 2:
The system employs temporary tracking structures that exist only for the duration of deletion operations. These disposable tracking mechanisms provide necessary location information for uncataloged pieces during deletion, then are discarded, avoiding the need for permanent catalog entries and maintaining system performance.
3Loss of substance
If backup retention times are enforced, then resource management is improved, but deletion failures occur leaving residual backup data
Solution Approach 1:
The system implements feedback mechanisms that monitor deletion operation outcomes and report back to the retention management system. When deletion failures occur, the feedback loop triggers retry logic or alternative deletion strategies, ensuring that retention policies are reliably enforced and storage resources are properly reclaimed.
Solution Approach 2:
The system dynamically adjusts deletion parameters such as retry counts, timeout values, and deletion strategies based on the specific characteristics of backup pieces. By changing these parameters adaptively, the system overcomes deletion failures and ensures complete enforcement of retention policies, thereby achieving proper resource management.
Data Source
AI summary
Systems and methods for deleting backup pieces associated with an application such as a database application. Backup pieces are identified and deleted from the database records and from the backup application.