Database Backup Recoverability Verification via Archive Log Dependency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current backup systems face inefficiencies in identifying and managing database archive log dependencies, leading to incomplete backups and ineffective recovery processes, particularly in distributed environments like Oracle Real Application Clusters, where metadata management and storage become intensive and error-prone.
Innovation Solution
A system that extracts and processes backup metadata to generate data structures for identifying dependent system change numbers, enabling the identification of missing archive logs and ensuring complete backup dependencies, thereby preventing incomplete backups and ensuring recoverability by reporting statuses as recoverable or unrecoverable.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the backup system stores complete metadata for all backup copies in distributed environments, then the recoverability verification becomes more accurate, but the metadata management becomes intensive and error-prone
Solution Approach 1:
The patent extracts the essential dependency information (archive log sequence numbers) from the complete backup metadata, storing only the critical recovery dependencies rather than all metadata. This reduces metadata management complexity while maintaining the ability to verify backup recoverability by checking only the essential dependency chain.
Solution Approach 2:
The patent segments the metadata management into two parts: essential dependency information stored centrally for verification, and detailed backup copy information stored locally. This segmentation reduces the central metadata load while preserving the ability to verify backup completeness and recoverability.
2Reliability
If the system checks all backup dependencies to ensure complete recovery, then the backup recoverability is guaranteed, but the processing time and computational resources increase
Solution Approach 1:
The patent performs preliminary verification of backup dependencies during the backup creation process itself, rather than waiting until recovery time. The system checks archive log dependencies and verifies completeness upfront, storing verification results that can be quickly referenced later, thus reducing the time needed during actual recovery operations.
Solution Approach 2:
The patent implements a feedback mechanism where the system continuously monitors and verifies backup dependency chains, providing immediate feedback on backup completeness. This allows for real-time detection of missing archive logs and prevents incomplete backups from being marked as recoverable, reducing the need for lengthy verification processes later.
3Reliability
If the backup system identifies and manages all archive log dependencies, then the backup recoverability is ensured, but the system complexity and storage requirements increase
Solution Approach 1:
The patent extracts only the essential dependency information (archive log sequence numbers and their relationships) from the complete backup metadata, storing minimally sufficient data to verify recovery completeness. This extraction approach ensures recovery assurance while minimizing metadata storage requirements.
4Measurement precision
If the system performs comprehensive dependency checking for each backup copy, then the accuracy of recoverability determination improves, but the processing efficiency decreases
Solution Approach 1:
The patent performs partial dependency checking by focusing only on the critical archive log dependencies required for recovery, rather than comprehensively analyzing all backup metadata. This partial action approach maintains high accuracy in determining recoverability while improving processing efficiency by avoiding unnecessary analysis of non-essential metadata.
Data Source
AI summary
System extracts backup metadata, comprising system committed change numbers, system change numbers, types, and database version identifiers, for backup copies. System generates data structure, comprising start system change numbers, based on minimums of system committed change numbers, end system change numbers, based on maximums of system change numbers, database version identifiers, and identifiers for archive log backup copies. System identifies dependent system change numbers, based on start system change number to end system change number for backup copy corresponding to database version identifier. System identifies, in data structure, backed-up system change numbers, based on start system change numbers to end system change numbers for archive log backup copies corresponding to database version identifier, which are included in dependent system change numbers. If backed-up system change numbers include all of dependent system change numbers, system stores backup copy with each archive log backup copy corresponding to backed-up system change numbers.