Database Snapshot Management via Automated Timer Jobs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Database snapshots are complex to create, delete, and restore, limiting their use to sophisticated DBMS users, and no current DBMS allows for restoring a subset of data within a snapshot, requiring full snapshot restoration even for small data recovery.

Innovation Solution

A user interface is provided for managing the automated creation, deletion, and restoration of database snapshots, allowing users to specify parameters for snapshot management, including frequency and retention time, and enabling manual data recovery from snapshots, accessible through a command line or programmable object model.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If database snapshots are used to create fine-grained records of a database, then the granularity and frequency of data records are improved, but the complexity of creating, deleting, and restoring snapshots increases

Engineering Contradiction:
Improvedata record granularityVSAvoidsnapshot management complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system enables automated snapshot management where the database management system automatically creates, deletes, and restores snapshots based on predefined schedules and triggers, eliminating the need for manual intervention by sophisticated database administrators

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

A user interface layer is introduced between the end user and the complex database snapshot functionality, providing simplified controls that abstract away the underlying complexity while enabling fine-grained snapshot operations

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If automated snapshot management is implemented, then ease of operation is improved, but device complexity increases

Engineering Contradiction:
Improvesnapshot management easeVSAvoidsystem architecture complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system implements automated snapshot creation and deletion based on predefined schedules and triggers, where the database management system self-manages the snapshot lifecycle without requiring complex manual configuration or intervention

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The snapshot management functionality is integrated into the existing database management system architecture, combining snapshot operations with regular backup and restore processes to avoid adding separate complex management systems

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If full snapshot restoration is performed to recover data, then data recovery completeness is improved, but loss of time increases

Engineering Contradiction:
Improvedata recovery completenessVSAvoidrestoration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system extracts and restores only the specific subset of data that needs to be recovered from the snapshot, rather than restoring the entire snapshot, thereby reducing restoration time while maintaining recovery completeness for the needed data

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The snapshot restoration process is segmented to allow selective recovery of specific data portions, enabling users to recover only the necessary tables, rows, or data elements instead of performing a full snapshot restore

Inventive Principle:
Principle #1Segmentation

4Productivity

If selective data recovery from snapshots is enabled, then productivity is improved, but device complexity increases

Engineering Contradiction:
Improvedata recovery efficiencyVSAvoidrestoration functionality complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system provides functionality to extract and restore only the specific subset of data needed from the snapshot, improving recovery efficiency by avoiding unnecessary data restoration while managing complexity through targeted operations

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS8121981B2Database snapshot management
Publication Date: 2012.02.21 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8121981B2 patent drawing
  • US8121981B2 patent drawing
  • US8121981B2 patent drawing

AI summary

Technologies are described herein for managing database snapshots. One user interface is provided for managing the automated creation and deletion of database snapshots. Parameters are received through the user interface that define how the database snapshots should be created and deleted. Once the parameters are defined, a timer job is executed that causes a DBMS to create and delete the database snapshots according to the specified parameters. A user interface is also provided for manually managing the creation, deletion, and restoration of database snapshots. A request may be received through this user interface to recover data from a database snapshot. In response to such a request, another user interface is provided for specifying the data that should be recovered. Once the data to be recovered has been specified, the desired data is recovered from the database snapshot.