Point-in-Time Database Restore via Extent Reference Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database systems face challenges in efficiently restoring a tenant's data to a specific point in time without affecting other tenants, as current methods require extensive resources, time, and hardware, and often result in data loss or manual reconciliation errors.

Innovation Solution

Implementing a point-in-time restore method using virtualization and immutable storage with extent references, which allows for quick and resource-efficient restoration of tenant data by mapping archival information into a target database, filtering out newer data, and using transaction filters to maintain transactional consistency without affecting other tenants.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional database restore methods are used to restore tenant data to a specific point in time, then data restoration is achieved, but it requires extensive resources, time, and additional hardware

Engineering Contradiction:
Improvedata restoration accuracyVSAvoidhardware requirements
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a virtual copy of the database state at a specific point in time by mapping extent references to archival data. Instead of physically copying entire datasets, the system uses reference mapping to create instantaneous virtual replicas, enabling point-in-time restoration without duplicating storage resources.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent introduces a virtualization layer with extent reference mapping as an intermediary between the physical storage and the database instance. This intermediary enables efficient data restoration by translating restore requests into targeted mappings of archival extents, avoiding the need for direct physical data copying or additional hardware infrastructure.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If traditional restore methods are used, then data can be restored to an approximate point in time, but data loss occurs and manual reconciliation is required

Engineering Contradiction:
Improverestore speedVSAvoiddata loss
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent performs preliminary actions by continuously maintaining archival copies of database extents and establishing a virtualization layer that can immediately map to any point in time. This preliminary preparation eliminates the need for approximate restoration, as the system can directly reference the exact state of data at any desired moment without manual reconciliation.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If snapshots are taken to restore database state at a specific point in time, then restoration capability is improved, but storage resources and time consumption increase

Engineering Contradiction:
Improvepoint-in-time restore accuracyVSAvoidrestore time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Instead of creating physical snapshot copies that consume storage resources, the patent uses virtual reference mapping to create instantaneous views of database state at any point in time. The extent reference mapping system allows multiple virtual snapshots without duplicating physical data, enabling fast restoration without storage overhead.

Inventive Principle:
Principle #26Copying

4Reliability

If full database restore is performed to restore a tenant's data, then complete data recovery is achieved, but it affects other tenants hosted in the same database instance

Engineering Contradiction:
Improvedata recovery completenessVSAvoidimpact on other tenants
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent segments the database into individual tenant extents with separate metadata and reference structures. This segmentation allows restoration operations to be isolated to specific tenant data only, enabling complete recovery for one tenant without affecting others hosted in the same physical database instance.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by allowing different restore operations to coexist in the same database instance, where each tenant's data has its own restore state and extent mappings. This enables localized restoration for individual tenants while maintaining the operational integrity and accessibility of other tenants' data.

Inventive Principle:
Principle #3Local quality

Data Source

PatentEP3646195B1Systems and methods of restoring a dataset of a database for a point in time
Publication Date: 2023.07.19 SALESFORCE INC
  • EP3646195B1 patent drawingFigure 1A
  • EP3646195B1 patent drawingFigure 1B
  • EP3646195B1 patent drawingFigure 2

AI summary

Systems and methods are provided for performing a point-in-time restore of data of a first tenant of a multitenanted database system. Metadata can be located to identify an archival version of first data of the first tenant stored in immutable storage of the database system. The archival version includes a most recently committed version of each datum prior to a first point in time. By using the metadata, a restore reference set is mapped into a target database instance of the database system. The mapping can be performed when all existing data for a tenant is to be the archival version, and where versions of data and records committed after the point in time are not available to the target database instance.