Synchronized Database Backup via Master Server Catalog

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database management systems face challenges in maintaining consistency and efficiency across heterogeneous database systems, where different database management systems (DBMSs) are used on various servers, making backup and recovery processes complex and inconsistent.

Innovation Solution

A master server maintains a master transactions log and backup catalog to synchronize transaction operations and facilitate synchronized backup and recovery across cohort servers running different DBMSs, using a two-phase commit protocol and snapshot-based data backup to ensure global consistency and efficient recovery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a heterogeneous database system uses multiple different DBMSs on various servers to enhance capabilities, then the system's functionality and storage capacity are improved, but the backup and recovery processes become complex and inconsistent across different systems

Engineering Contradiction:
Improvedatabase system functionalityVSAvoidbackup and recovery process complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a coordinator server as an intermediary component that manages backup and recovery operations across multiple heterogeneous DBMSs. The coordinator server receives backup requests, determines the appropriate backup strategy for each DBMS type, coordinates the backup operations, and consolidates backup data. This intermediary layer abstracts the complexity of dealing with multiple different DBMSs, providing a unified backup and recovery interface while maintaining compatibility with diverse database systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If each database system uses its own implementation-specific backup and recovery strategies, then the backup process is optimized for that particular system, but consistency across the heterogeneous database system cannot be ensured

Engineering Contradiction:
Improvesystem-specific backup optimizationVSAvoidbackup consistency across systems
Core Design Contradiction:
ReliabilityVSStability of the object's composition

Solution Approach 1:

The patent divides the backup and recovery process into distinct segments: (1) a coordination layer that manages the overall backup operation and ensures consistency, and (2) execution layers that handle DBMS-specific backup operations. Each DBMS is backed up using its optimized strategy, but these operations are segmented and coordinated by the coordinator server, which tracks the state of each backup operation and ensures that all components are consistently backed up together as a unified system.

Inventive Principle:
Principle #1Segmentation

3Stability of the object's composition

If synchronized backup is implemented across heterogeneous DBMSs, then global consistency is achieved, but the coordination overhead and time required for backup operations increase

Engineering Contradiction:
Improveglobal backup consistencyVSAvoidbackup coordination time
Core Design Contradiction:
Stability of the object's compositionVSLoss of time

Solution Approach 1:

The patent implements preliminary actions by having the coordinator server prepare and communicate backup requests to all DBMSs before the actual backup operations begin. The coordinator determines the backup scope, identifies all relevant DBMSs and data components, and initiates the backup process in a coordinated manner. This preliminary coordination phase allows subsequent backup operations to proceed more efficiently with minimal ongoing overhead, as the synchronization framework is established in advance.

Inventive Principle:
Principle #10Preliminary action

4Ease of operation

If a unified backup management approach is used across all DBMSs, then operational simplicity is improved, but the ability to leverage DBMS-specific optimizations is reduced

Engineering Contradiction:
Improvebackup management simplicityVSAvoidbackup efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The coordinator server is designed with universal functionality to work with multiple different DBMS types through standardized interfaces and protocols. It can issue backup requests, receive status information, and consolidate backup data from various DBMSs using a unified approach. Simultaneously, the system maintains the ability to leverage DBMS-specific optimizations by allowing each DBMS to execute its native backup procedures under the coordination of the universal coordinator, thus achieving both operational simplicity and backup efficiency.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS9575849B2Synchronized backup and recovery of database systems
Publication Date: 2017.02.21 SAP SE
  • US9575849B2 patent drawing
  • US9575849B2 patent drawing
  • US9575849B2 patent drawing

AI summary

Disclosed herein are system, method, and computer program product embodiments for utilizing a backup catalog to perform synchronized backup and recovery of heterogeneous database systems. An embodiment operates by performing a global data backup of a heterogeneous database system comprising a first database management system (DBMS) at a first server and a second DBMS at a second server and recording a global data backup entry identifying the global data backup into a backup catalog. Upon receiving log backup notifications regarding asynchronous log backups on the first server and the second server, log backup entries identifying the asynchronous log backups are recorded into the backup catalog. To successfully perform a point-in-time recovery, the embodiment operates by using the backup catalog to identify data and log backups required for the recovery of the first and second servers to a recovery timestamp associated with the point-in-time recovery.