Database Recovery via Live Mount and Reference Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database restoration techniques require significant storage resources and result in prolonged downtime due to the time-consuming process of migrating and applying transaction logs, making them inefficient for rapid database recovery.
Innovation Solution
The method involves live-mounting a backup asset onto a client device while allowing remote access, issuing a control file request to the backup storage system, and recovering the backup asset data file copy, enabling rapid switching of file system references between backup and local storage to minimize downtime.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If database restoration is performed using traditional techniques (migrating rollback database data from backup storage to target device and applying transaction logs), then database recovery is achieved, but database downtime is prolonged and recovery speed is reduced
Solution Approach 1:
The patent applies preliminary action by pre-generating and storing forward database data (incremental changes) separately from the rollback database data during the backup process. This forward data is prepared in advance and stored in a readily accessible format, eliminating the need to apply transaction logs during recovery. When restoration is needed, the system can immediately switch to using the pre-prepared forward data, significantly reducing database downtime while ensuring reliable recovery.
2Reliability
If vast storage resources are provisioned on target device for database restoration, then complete database recovery is enabled, but storage complexity and resource requirements increase
Solution Approach 1:
The patent applies segmentation by dividing database backup data into two distinct segments: rollback database data (base state) and forward database data (incremental changes). These segments are stored separately with different access patterns and storage requirements. During recovery, the system can work with smaller, more manageable portions of data rather than provisioning storage for the entire database, reducing target device storage complexity while maintaining reliable recovery capability.
3Reliability
If transaction logs are applied to migrated database data during recovery, then database consistency is maintained, but recovery time and processing duration increase
Solution Approach 1:
The patent applies copying by creating and storing a copy of forward database changes in a pre-processed format during the backup operation. Instead of applying transaction logs during recovery (which is time-consuming), the system uses this pre-copied forward data that already contains the necessary changes in an applied state. This eliminates the log application step during recovery while maintaining database consistency, significantly reducing recovery time.
Data Source
AI summary
A method and system for minimizing rolling database recovery downtime. Specifically, the disclosed method and system entail migrating and recovering database data from backup storage to local host storage while enabling database access operations through live mounts mapped to the database data on the backup storage. Database downtime may subsequently be reduced through the rapid switching of file system references between database data stored on backup storage and database data copies recovered on local storage.