Database Export Between Recovery Environments

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database recovery systems are inadequate for real-time critical applications, as they fail to provide instant recovery, testing, and analysis capabilities across various environments.

Innovation Solution

The system enables the export of a database from a foreign database recovery environment to a native database recovery environment, utilizing foreign snapshot files and incremental files for storage, and includes methods for generating script information, creating directories, materializing file information, and communicating this information between nodes to restore and recover the database.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a single database recovery system is used, then system simplicity is maintained, but the ability to provide instant recovery, test, and analyze capabilities across various environments is insufficient

Engineering Contradiction:
Improverecovery capability across environmentsVSAvoidsystem architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system is divided into multiple specialized components: a foreign database recovery environment for initial recovery operations, and a native database recovery environment for extended recovery and analysis. This segmentation allows each environment to be optimized for specific recovery tasks while maintaining overall system versatility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary export process that transfers database state information between the foreign and native recovery environments. This intermediary mechanism enables seamless collaboration between different recovery systems, allowing capabilities to be combined without direct integration complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If database recovery is performed in a foreign database recovery environment, then initial recovery capability is provided, but extended recovery capability in the native environment is limited

Engineering Contradiction:
Improvedatabase recovery reliabilityVSAvoidrecovery environment setup
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The foreign database recovery environment performs preliminary recovery operations first, restoring the database to a usable state. This preliminary action prepares the database for subsequent extended recovery operations in the native environment, ensuring reliability through a two-stage approach.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The export process maintains continuity by transferring the database state from the foreign recovery environment to the native recovery environment without interruption. This continuous action ensures that recovery operations can proceed seamlessly across environments, enhancing overall reliability.

Inventive Principle:
Principle #20Continuity of useful action

3Adaptability or versatility

If export information is communicated between multiple hosts, then database portability and flexibility are improved, but communication overhead and processing time increase

Engineering Contradiction:
Improvedatabase portabilityVSAvoidexport processing time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system creates a copy of the database state information (including database identifier, timestamp, and state data) and transmits this copy between hosts. This copying approach enables rapid portability without requiring complex data transformation or verification processes, reducing communication overhead.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The export information is structured with key parameters (database identifier, timestamp, state) that can be efficiently serialized and transmitted. By changing the representation to a compact parameter format, the system reduces communication overhead while maintaining full portability capabilities.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20250068525A1Extended recovery of an exported database
Publication Date: 2025.02.27 RUBRIK INC
  • US20250068525A1 patent drawing
  • US20250068525A1 patent drawing
  • US20250068525A1 patent drawing

AI summary

Systems and methods for an extended recovery of an exported database are described. The method includes communicating a database from a source host operating in a native database recovery environment, the database being communicated to a backup host operating in a foreign database recovery environment, the native database recovery environment including native snapshot files and native incremental files for storing the database, the foreign database recovery environment including foreign snapshot files and foreign incremental files for storing the database. The method further includes receiving file information and script information, at the source host, the file information including the native snapshot files and the native incremental files, the script to perform operations for causing a recovering of the database in the foreign database recovery environment based on the changes to the database in the foreign database recovery environment after the point-in-time.