Database Snapshot via Converter Table Marking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database systems require significant time and resources to restart to an earlier state, often necessitating the use of backup volumes and initialization processes, which decreases availability and is inefficient.

Innovation Solution

A system and method for creating a snapshot version of a database, where a current state of the converter table is identified, saved, and marked to prevent overwriting, allowing for efficient restoration to a previous state without referencing backup volumes or performing an initialization process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If existing backup techniques are used to reset the database to an earlier state, then data recoverability is ensured, but database availability decreases and valuable time and hardware resources are consumed

Engineering Contradiction:
Improvedata recoverabilityVSAvoidtime to reset database
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent creates snapshots of the database at specific points in time by saving the current state of the converter table and marking page identifiers to prevent overwriting. This preliminary action stores the database state in memory without requiring external backup media, enabling rapid restoration to previous states without the time-consuming process of retrieving data from external backups.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates a copy of the converter table state (snapshot) that records page identifiers and their physical locations. This copy is stored within the database system itself and can be rapidly restored by copying the snapshot restart record back to the current restart record, eliminating the need to retrieve data from external backup volumes.

Inventive Principle:
Principle #26Copying

2Reliability

If existing backup techniques are used to reset the database to an earlier state, then data recoverability is ensured, but hardware resources are consumed

Engineering Contradiction:
Improvedata recoverabilityVSAvoidhardware resources
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent performs preliminary actions to create snapshots by saving the converter table state and marking page identifiers within the existing database memory structure. This eliminates the need for separate external backup storage hardware, as the snapshot data is maintained within the database system's own memory and storage structures.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The converter table serves multiple functions: it tracks the current state of the database for normal operations and simultaneously serves as the storage mechanism for snapshot data. This multi-functionality eliminates the need for dedicated backup storage hardware, as the existing converter table infrastructure is reused for snapshot storage and restoration.

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

3Reliability

If database is restarted frequently to an earlier state using existing techniques, then data can be recovered, but availability of the database system decreases

Engineering Contradiction:
Improvedata recovery capabilityVSAvoiddatabase availability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent creates snapshots in advance by saving the converter table state and marking page identifiers to prevent overwriting. This preliminary action prepares the database for potential restoration without requiring external backup retrieval during the restoration process, enabling rapid recovery that minimizes downtime and maintains high availability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent enables rapid restoration by copying the snapshot restart record (which contains page identifiers and physical locations) back to the current restart record. This copying operation is performed within the database system's memory, eliminating the time-consuming process of retrieving data from external backup volumes and significantly reducing restoration time to maintain availability.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS7440979B2Snapshots for instant backup in a database management system
Publication Date: 2008.10.21 SAP SE
  • US7440979B2 patent drawing
  • US7440979B2 patent drawing
  • US7440979B2 patent drawing

AI summary

A system, method, apparatus, means and computer program code for processing a request to create a snapshot version of a database are provided which include identifying a current state of a converter table, the converter table including information identifying a plurality of page identifiers and a physical location of each of the page identifiers in a data area, saving the current state of the converter table, and marking each of the plurality of page identifiers to prevent overwriting.