Tablespace Export for Foreign Database Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database recovery systems are inadequate for real-time critical applications like ERP and CRM, as they fail to provide instant recovery, testing, and analysis capabilities.
Innovation Solution
A system utilizing a tablespace for exporting from a foreign database recovery environment, which involves a backup host receiving database information, generating script and file information, and communicating these via directories to a source host for recovery, enabling point-in-time restoration and recovery of a tablespace in a native database recovery environment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If traditional database recovery systems are used, then system stability is maintained, but real-time recovery capability is insufficient
Solution Approach 1:
The database is segmented into tablespaces that can be independently exported and recovered. The recovery system processes different tablespaces separately, allowing parallel recovery operations and faster overall recovery time while maintaining data consistency through controlled segmentation.
Solution Approach 2:
A tablespace export/import mechanism serves as an intermediary between the foreign database environment and the native recovery environment. This intermediary layer enables data transfer and recovery without requiring direct compatibility between different database systems, bridging the gap between environments.
2Productivity
If foreign snapshot files and incremental files are utilized, then recovery efficiency is improved, but system complexity increases
Solution Approach 1:
Snapshots are captured and stored in advance before recovery is needed. These pre-captured tablespace states allow for rapid recovery by simply applying incremental changes rather than rebuilding from scratch, significantly improving recovery efficiency while the complexity is managed through automated snapshot management.
Solution Approach 2:
Tablespaces are copied from the foreign database environment to the native recovery environment using export/import mechanisms. This copying approach enables efficient recovery by transferring only the necessary data portions rather than recreating entire database structures, improving productivity while managing complexity through selective copying.
3Measurement precision
If point-in-time recovery is implemented, then data precision is improved, but processing time increases
Solution Approach 1:
The system applies different recovery precision levels to different tablespaces based on their importance and change frequency. Critical tablespaces receive point-in-time recovery with high precision, while less critical ones use coarser recovery granularities, optimizing the balance between precision and processing time for the overall system.
Data Source
AI summary
Systems and methods for utilizing tablespace to export from a foreign database recovery environment are described. The system includes a backup host that operates in a foreign database recovery environment and receives a database from a source host operating in a native database recovery environment. The backup host receives export information including a tablespace identifier and a point-in-time. The tablespace includes file information for export from the backup host to the source host. A job is initiated on the backup host to generate script information (including logic for execution on the source host to recover the tablespace, at the point-in-time, in the database on the source host), create directories on the backup host, materialize file information including snapshots of the database and incremental changes to the database, and communicate the file information and the script information, via the directories, to the source host.