Tenant Database Restore via Snapshot Cloning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional storage systems disrupt other tenant databases during the restoration of a specific tenant database in a multitenant database system, as they require restoring the entire system before restoring the specific database, leading to downtime and inefficiency.

Innovation Solution

A management module and agent system that coordinates backup and restore operations, allowing for selective restoration of a tenant database without impacting other databases by using snapshot cloning and file-level restore methods based on storage layout, enabling continuous operation of other tenant databases during the restore process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional storage systems restore the entire multitenant database system before restoring a specific tenant database, then the specific tenant database can be restored, but all tenant databases become unavailable during the restore process

Engineering Contradiction:
Improverestoration completenessVSAvoidsystem availability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent divides the multitenant database system into separate tenant database components, each with its own restore capability. The storage system can identify and restore individual tenant databases independently rather than requiring full system restoration, thus maintaining availability of non-restored tenants while completing restoration of the target tenant.

Inventive Principle:
Principle #1Segmentation

2Reliability

If conventional storage systems restore the entire multitenant database system, then data integrity is maintained, but downtime increases for all tenants

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

Solution Approach 1:

The patent implements preliminary backup and snapshot mechanisms that capture the state of the multitenant database system before restoration begins. This allows the system to restore individual tenant databases from pre-captured snapshots without requiring full system downtime, as the preliminary backup state preserves data integrity while enabling selective, time-efficient restoration.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If conventional storage systems use full system restoration, then all tenant databases are protected, but operational disruption occurs for tenants not requiring restoration

Engineering Contradiction:
Improvecomprehensive protectionVSAvoidoperational continuity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent extracts and isolates the restoration process to only the specific tenant database requiring restoration, separating it from other tenant databases that continue normal operations. The storage system identifies the target tenant database, applies restoration operations exclusively to that component, and maintains operational continuity for all other tenants, thus eliminating unnecessary operational disruption while preserving comprehensive protection capabilities.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11636011B2Methods and systems for protecting multitenant databases in networked storage systems
Publication Date: 2023.04.25 NETAPP INC
  • US11636011B2 patent drawing
  • US11636011B2 patent drawing
  • US11636011B2 patent drawing

AI summary

Methods and systems for restoring a tenant database of a multitenant database system with multiple tenant databases is provided. In response to a request to restore a first tenant database, a system verifies that the first tenant database is present in the multitenant system database system with a same identifier when a backup of the first tenant database was taken during a backup operation and when the restore request was received. A restore method is selected based on a storage type used for storing the first tenant database. The selected restore method is executed for restoring the first tenant database utilizing an internal file associated with the first tenant database, while processing requests for other tenant databases.