Archived Database Log Deletion with Feedback-Based Retry
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database logs often fail to be deleted from storage entities, occupying unnecessary storage space and reducing available space, due to network errors, deletion script failures, or replication issues during backup processes.
Innovation Solution
Implement a log deletion table to track undeleted database logs, reissue deletion commands, and update metadata based on query responses to ensure complete deletion.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If transaction logs are deleted from the host after being backed up, then storage space at the host is freed, but deletion may fail due to network errors, script failures, or replication issues causing logs to remain stored
Solution Approach 1:
The system implements a feedback mechanism by querying the storage entity to determine whether database logs were successfully deleted. The data center receives query responses indicating deletion status and uses this feedback to identify logs that failed deletion, enabling reattempt of deletion commands for failed logs.
Solution Approach 2:
The system performs preliminary tracking of database logs in a log deletion table before attempting deletion. This preliminary action maintains metadata about logs that need deletion and enables the system to proactively identify and reattempt deletion of logs that fail, rather than waiting for manual intervention.
2Reliability
If deletion commands are reissued for failed logs, then complete deletion is ensured, but additional processing time and complexity are required
Solution Approach 1:
The system implements self-service by automatically reattempting deletion of database logs that fail to delete. The data center independently identifies failed deletions through query responses and reissues deletion commands without requiring manual intervention, making the system self-correcting.
Solution Approach 2:
The system replaces manual deletion processes with an automated electronic system. Instead of relying on manual operations, the data center automatically tracks, queries, identifies failed deletions, and reissues deletion commands through electronic processes, reducing human involvement and improving consistency.
Data Source
AI summary
During a backup a procedure, a first storage entity may backup a set of database logs from a second storage entity and metadata associated with the set of database logs may be stored in a log deletion table. In accordance with a user configuration of the second storage entity and the backup procedure, a first command to delete one or more database logs of the set from the second storage entity may be transmitted to the second storage entity. The log deletion table may be updated based on a query of second storage entity about whether the one or more database logs were deleted from the second storage entity in response to the first command. Based on the updated log deletion table, a second command may be transmitted to the second storage entity to delete database logs that were not deleted in response to the first command.