Database Recovery Using System Identifiers and Backup Catalog Markers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database recovery systems face challenges in seamlessly transferring and utilizing backups between database systems, particularly in maintaining accurate recovery states and integrating new backups generated post-recovery, which complicates the recovery process and data consistency.
Innovation Solution
The system employs a backup tool that uses system identifiers to manage and access backups across different database systems, allowing for the recovery of a source database system into a target system by determining appropriate configuration files and pipe names, and subsequently handling log and data backups to maintain data integrity and consistency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a backup tool abstracts storage and implements its own lifecycle management for backup files, then backup management is simplified and standardized, but integrating backups from different database systems becomes complex and difficult
Solution Approach 1:
The backup tool is designed to handle multiple database systems through a universal interface. The system uses standardized backup file formats and a common backup tool that can manage backups from different database systems (source and target systems) without requiring system-specific backup utilities, thus achieving multi-functionality while maintaining ease of operation.
Solution Approach 2:
The patent introduces an intermediary mechanism in the form of a standardized backup interface and common storage location. The backup tool acts as an intermediary that abstracts the underlying storage details and provides a unified way to access and manage backup files from different database systems, simplifying the integration process.
2Reliability
If the target database system generates its own backups after recovery, then data consistency and backup independence are improved, but managing and tracking backups across multiple systems becomes more complex
Solution Approach 1:
The system implements feedback mechanisms where the backup tool monitors and tracks backup files from both source and target database systems. The backup tool receives notifications about new backup files and updates its internal state accordingly, providing feedback loops that automatically track backup status across multiple systems without manual intervention.
Solution Approach 2:
The backup tool is pre-configured with knowledge of both source and target database system locations and identifiers. Before backups are generated, the system establishes the backup management framework and tracking mechanisms in advance, allowing seamless integration of backups from multiple systems once they are created.
3Productivity
If system identifiers are used to manage backups across different database systems, then backup identification and retrieval are simplified, but maintaining accurate system identification and configuration becomes more complex
Solution Approach 1:
The system uses system identifiers that are copied and associated with backup files during the backup process. These identifiers are embedded in the backup metadata, allowing quick retrieval and identification without requiring complex configuration lookups. The backup tool maintains a simplified mapping between system identifiers and backup locations.
Data Source
AI summary
A system includes reception, at a target database system, of a request to recover a backup created by a source database system into the target database system, where the request comprises a system identifier of the source database system, determination of a backup tool configuration file associated with the source database system based on the system identifier of the source database system, request of a recovery of the backup into the target database system using the backup tool configuration file, copying of a backup catalog of the source database system into a storage location associated with the target database system, and appending of a system change marker to the copied backup catalog, wherein the system change marker comprises the system identifier of the source database system.