Tablespace Export from Foreign Database Recovery Environment

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current database recovery systems are inadequate for real-time critical applications, such as ERP and CRM systems, as they fail to provide instant recovery, testing, and analysis capabilities.

Innovation Solution

A system that utilizes a tablespace for exporting data from a foreign database recovery environment to a native database recovery environment, using foreign snapshot and incremental files to restore and recover data, enabling point-in-time recovery and metadata management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional database recovery systems are used, then system simplicity is maintained, but real-time recovery capability and productivity are insufficient

Engineering Contradiction:

Improverecovery speedVSAvoidsystem complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the database recovery process into distinct components: foreign snapshot files for baseline restoration, incremental files for point-in-time recovery, and metadata files for tablespace management. This segmentation enables parallel processing and optimized recovery paths while maintaining system modularity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces a tablespace export/import mechanism as an intermediary between foreign and native database environments. This intermediary layer enables seamless data migration and recovery between different database systems without requiring complete system reconstruction.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Loss of time

If complete database restoration is performed, then data completeness is ensured, but time consumption and resource usage increase

Engineering Contradiction:

Improverecovery timeVSAvoiddata completeness

Core Design Contradiction:

Loss of timeVSReliability

Solution Approach 1:

The patent performs preliminary actions by pre-generating foreign snapshot files and incremental files with associated metadata during normal database operations. These pre-prepared files enable immediate recovery without requiring complex real-time processing, thus reducing recovery time while ensuring data completeness.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements dynamic recovery capabilities that allow adjustment of recovery granularity. Users can recover entire databases or specific tablespaces based on needs, and can select different point-in-time recovery options. This dynamic approach optimizes recovery time while maintaining data completeness through selective restoration.

Inventive Principle:

Principle #15Dynamics

3Adaptability or versatility

If tablespace export/import functionality is added, then adaptability between database environments is improved, but system complexity increases

Engineering Contradiction:

Improveenvironment compatibilityVSAvoidsystem architecture

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal tablespace export/import mechanism that works across different database environments (foreign and native). The system uses standardized metadata formats and recovery protocols that enable compatibility between various database systems, allowing the same recovery infrastructure to serve multiple purposes and environments.

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Measurement precision

If point-in-time recovery is enabled, then data precision and reliability are improved, but processing complexity and time requirements increase

Engineering Contradiction:

Improverecovery precisionVSAvoidrecovery process

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

The patent replaces complex mechanical recovery processes with a file-based system using foreign snapshot files and incremental files. Each file contains timestamp metadata that enables precise point-in-time recovery through simple file selection and application, eliminating the need for complex recovery algorithms while maintaining high precision.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS11194761B2Optimizing utilization of a tablespace for exporting from a foreign database recovery environment

Publication Date: 2021.12.07 RUBRIK INC

AI summary

Systems and methods to optimize utilization of a tablespace for export from a native database recovery environment are described. The system receives a database from a source host, operating in a native database recovery environment, at a backup host operating in a foreign database recovery environment. The foreign database recovery environment utilizes foreign snapshot files and foreign incremental files for storing the database. The system receives a tablespace identifier that identifies a tablespace and a point-in-time that identifies file information for export from the backup host to the source host. The backup host initiates a job to generate script information; create directories; materialize the file information; utilize an auxiliary database to generate tablespace metadata information; and communicate the tablespace metadata information and the script information and the file information, via the directories, and over a network, to the source host, to enable the source host to recover the tablespace.