Database Block-Level Mapping for Granular Restore

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database backup and restore methods are inefficient, as they often require restoring entire database files, consuming significant time and resources, and do not allow for granular access or conversion of database objects between different applications.

Innovation Solution

Implementing a block-level mapping and storage system that divides database files into granular blocks for backup and restore operations, enabling the restoration of specific database objects without restoring the entire file, and converting database objects between different application formats.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If entire backup database file is restored to access a specific database object, then data protection is ensured, but restore time and computing resource consumption increase significantly

Engineering Contradiction:
Improvedata protectionVSAvoidrestore time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The backup database file is divided into multiple blocks, and the system maintains mapping information that associates database objects with specific blocks. This segmentation allows the system to restore only the specific block containing the requested database object rather than the entire backup file, thereby reducing restore time while maintaining data protection through complete backup storage.

Inventive Principle:
Principle #1Segmentation

2Reliability

If entire backup database file is restored to access a specific database object, then data protection is ensured, but computing resource consumption increases

Engineering Contradiction:
Improvedata protectionVSAvoidcomputing resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The backup database file is divided into multiple blocks, and the system maintains mapping information that associates database objects with specific blocks. This segmentation allows the system to restore only the specific block containing the requested database object rather than the entire backup file, thereby reducing computing resource consumption while maintaining data protection through complete backup storage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system extracts and restores only the specific block containing the requested database object from the backup file, rather than restoring the entire file. This extraction approach minimizes computing resource consumption by processing only the necessary data portion while maintaining data protection through the完整性 of the full backup storage.

Inventive Principle:
Principle #2Taking out (Extraction)

3Productivity

If block-level mapping and storage is implemented, then restore speed and resource efficiency improve, but system complexity increases

Engineering Contradiction:
Improverestore speedVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by creating and maintaining block-level mapping information during the backup process. This mapping associates database objects with their corresponding blocks in advance, enabling fast and efficient restoration operations without requiring complex real-time analysis. The upfront organization of block-level metadata simplifies the restoration process while improving productivity.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12174710B2Restoring archived database data
Publication Date: 2024.12.24 COMMVAULT SYSTEMS INC
  • US12174710B2 patent drawing
  • US12174710B2 patent drawing
  • US12174710B2 patent drawing

AI summary

According to certain aspects, a system may include a data agent configured to: process a database file residing on a primary storage device(s) to identify a subset of data in the database file for archiving, the database file generated by a database application; and extract the subset of the data from the database file and store the subset of the data in an archive file on the primary storage device(s) as a plurality of blocks having a common size; and at least one secondary storage controller computer configured to, as part of a secondary copy operation in which the archive file is copied to a secondary storage device(s): copy the plurality of blocks to the secondary storage devices to create a secondary copy of the archive file; and create a table that provides a mapping between the copied plurality of blocks and corresponding locations in the secondary storage device(s).