Database Backup Preserving Physical Properties for Performance Debugging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database backup and restore processes often result in significant storage requirements and slow operations, leading to infrequent backups, which can result in restored databases having much older versions of data, compromising data integrity and performance debugging accuracy.

Innovation Solution

A database system that performs logical backups, preserving physical properties such as table statistics, layout, and deleted rows, allowing for the creation of a target database that mirrors the source database's performance characteristics without requiring exact hardware configuration, enabling effective performance debugging without affecting the source system's performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If traditional database backup methods are used, then data can be restored, but the restored database loses physical properties affecting performance debugging accuracy

Engineering Contradiction:
Improveperformance debugging accuracyVSAvoidphysical properties of database
Core Design Contradiction:
Measurement precisionVSLoss of information

Solution Approach 1:

The patent creates a copy of the source database that preserves physical properties (table statistics, layout, deleted rows) rather than just logical data. This copying approach allows the target database to mirror the source's performance characteristics while enabling independent performance debugging without affecting the production system.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent changes the backup approach from logical-only copying to physical property preservation. By capturing and restoring physical parameters (table statistics, data layout, deleted row information), the system maintains the performance characteristics of the source database in the target database, enabling accurate performance debugging.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If backups are performed frequently to maintain data currency, then data integrity improves, but storage requirements and operation time increase significantly

Engineering Contradiction:
Improvedata integrityVSAvoidstorage space
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts only the necessary physical properties (table statistics, layout information, deleted row data) from the source database rather than copying entire database files. This extraction approach reduces storage requirements while maintaining the ability to perform accurate performance debugging on the target database.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If backups are performed frequently to maintain data currency, then data version freshness improves, but operation speed decreases

Engineering Contradiction:
Improvedata version freshnessVSAvoidbackup operation speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The patent extracts only essential physical properties from the source database rather than performing complete database copies. This extraction method reduces backup operation time while maintaining data version freshness, allowing more frequent backups without significantly impacting system performance.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS9535932B1Backup and restore of databases
Publication Date: 2017.01.03 PARACCEL INC
  • US9535932B1 patent drawing
  • US9535932B1 patent drawing
  • US9535932B1 patent drawing

AI summary

A logical backup of a database is performed that allows physical properties of the database to be preserved upon restore. The physical properties of the database include properties related to storage of the data on the hard disk. Preserving the physical properties of a database allows performance debugging of the source database by performing performance tests on the target database rather than a production system. Incremental backup of metadata of a database is performed to minimize execution of statements that provide the final configuration of the database. Incremental backup is performed by restoring a database using a full backup and applying incremental backups to reach a particular state. The user can inspect the restored database after applying each incremental backup to determine whether the database has reached a desired state.