Database Restoration with Dependency Map for Referential Integrity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database restoration methods fail to maintain referential integrity, leading to broken relationships between dependent items during the backup and restore operations, which can result in applications not functioning as intended.

Innovation Solution

A method and system that builds an index from a backup database to identify and retrieve relationships between list items, using metadata to map dependent items and restore them along with the requested items, ensuring that all necessary items are restored to maintain application functionality.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a user selects individual items to be restored from a backup database, then the restoration process becomes faster and more selective, but the referential integrity between dependent items may be broken

Engineering Contradiction:
Improverestoration speedVSAvoidreferential integrity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by building an index of all items in the backup database and reading metadata to identify dependent items before the actual restoration process. This allows the system to pre-determine which items need to be restored together to maintain referential integrity, resolving the contradiction by preparing the dependency information in advance rather than discovering it during restoration.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary mechanism - a dependency map built from metadata that mediates between the user's selection and the actual restoration process. This intermediary structure tracks relationships between items and automatically determines the complete set of items that must be restored together, allowing selective restoration while preserving referential integrity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If the system restores only the selected items without checking dependencies, then the restoration process is simpler and faster, but the application functionality may be compromised

Engineering Contradiction:
Improverestoration process complexityVSAvoidapplication functionality
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary analysis by building an index and reading metadata to identify dependent items before restoration. This preliminary action captures the dependency information in advance, allowing the restoration process to simply follow the pre-determined set of items without complex real-time dependency resolution, thus maintaining functionality while controlling complexity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service by automatically identifying and restoring all necessary dependent items without requiring user intervention. The metadata-driven approach allows the system to autonomously determine the complete restoration set, eliminating the need for users to manually identify dependencies while preserving application functionality.

Inventive Principle:
Principle #25Self-service

3Reliability

If the system builds an index and reads metadata to identify all dependent items before restoration, then referential integrity is maintained, but the restoration process becomes more complex and time-consuming

Engineering Contradiction:
Improvereferential integrityVSAvoidrestoration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs the time-consuming index building and metadata reading actions before the actual restoration process. By completing these preparatory steps in advance, the system establishes the dependency map that enables efficient restoration without repeated dependency checks during the copy process, thus maintaining referential integrity while minimizing restoration time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The restoration process is segmented into distinct phases: index building, metadata reading and dependency identification, and actual item restoration. This segmentation allows the system to perform the complex analysis work separately from the data copying work, optimizing resource usage and making the overall process more efficient while ensuring referential integrity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8606752B1Method and system of restoring items to a database while maintaining referential integrity
Publication Date: 2013.12.10 COHESITY INC
  • US8606752B1 patent drawing
  • US8606752B1 patent drawing
  • US8606752B1 patent drawing

AI summary

A system and method for restoring list items to a database while maintaining the referential integrity of the list items. Before requested list items are restored to a database, a dependencies tablemetadata is read to determine the links between list items of the database. A map is created, and the links between list items are stored in the map. When the requested list items are restored to the database, the requested items and any dependent items are identified from the map and restored to the database. By restoring the dependent items of the selected item to be restored, referential integrity of the database is maintained.