Database Recovery Across Host Count Mismatches

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database backup and recovery processes are ineffective when the number of hosts in the source database system differs from the number of hosts in the target database system, preventing successful database copying and recovery operations.

Innovation Solution

A method is introduced where a backup of the source database system is created and used to configure and recover a target database system by modifying daemon.ini files and updating the topology to accommodate the differing number of hosts, allowing the target system to be configured with additional services and hosts to mirror the source system's state.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If database backup and recovery processes are used to copy a database system, then the database can be recovered on the target system, but the operation fails when the number of hosts in the source and target systems differs

Engineering Contradiction:
Improvedatabase recovery successVSAvoidhost number compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent modifies configuration parameters in daemon.ini files and topology information to adapt the target database system to match the source system's host configuration. By changing these parameters, the system enables recovery operations between database systems with different numbers of hosts, resolving the contradiction between recovery reliability and host number compatibility.

Inventive Principle:
Principle #35Parameter changes

2Stability of the object's composition

If the target database system is configured to mirror the source system, then a functional copy is achieved, but additional configuration steps are required when host numbers differ

Engineering Contradiction:
Improvedatabase system functionalityVSAvoidconfiguration process
Core Design Contradiction:
Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The patent performs preliminary modifications to daemon.ini files and topology configurations before executing the database recovery operation. By preparing these configuration changes in advance, the system ensures that the target database system can be successfully recovered and configured to mirror the source system, even when the number of hosts differs, thereby achieving functional stability without requiring complex post-recovery adjustments.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9766984B2N to M host system copy
Publication Date: 2017.09.19 SAP SE
  • US9766984B2 patent drawing
  • US9766984B2 patent drawing
  • US9766984B2 patent drawing

AI summary

A system includes obtaining of a backup of the source database system comprising N hosts and a first plurality of servers, where N is an integer greater than one, access of a target database system comprising M hosts, where M is an integer less than N, configuration of the target database system to include the first plurality of servers, and performance of a database recovery of the target database system using the backup of the source database system.