Variable-Length Tree Database Repair via Selective Leaf Block Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data storage systems, particularly in cloud computing environments, face inefficiencies in repairing tree databases with variable-length records, as traditional methods often require complete system replacement, leading to excessive disk read operations and resource consumption, especially when dealing with minor damages or corruptions.

Innovation Solution

A method that iterates through the variable-length tree database block by block, detects recoverable leaf blocks, reduces them to legally formatted contents, removes branch blocks, and rebuilds them as necessary to provide a lookup and organizational index, allowing for efficient recovery and indexing of records without replacing the entire system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the entire data system is completely rebuilt block-by-block to repair data loss or failures, then data integrity is ensured, but excessive disk read operations and resource consumption occur

Engineering Contradiction:
Improvedata integrityVSAvoiddisk read operations
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the repair process by identifying and isolating only the corrupted blocks that need repair, rather than rebuilding the entire data system. The system divides the storage space into discrete blocks and selectively processes only those blocks containing errors, significantly reducing the scope of repair operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts and removes only the necessary metadata and branch blocks required for the repair operation, rather than processing the complete data system. By taking out only the essential components needed for reconstruction, the system minimizes disk read operations while ensuring data integrity.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If the entire data system is completely rebuilt to repair minor damages, then all data is correctly formatted and inserted, but time and resources are unnecessarily consumed

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

Solution Approach 1:

The patent applies partial action by performing only the minimum necessary repair operations to correct corrupted blocks. Instead of executing a complete system rebuild, the system performs selective metadata extraction and branch block removal only where needed, reducing repair time while maintaining data correctness.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent performs preliminary actions by first identifying corrupted blocks and extracting necessary metadata before executing the repair operation. This preliminary assessment allows the system to prepare only the essential components needed for repair, avoiding unnecessary processing time.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If complete system replacement is performed to locate and repair failed data, then all data is recovered, but the process is ineloquent and excessive for minor damages

Engineering Contradiction:
Improvedata recoveryVSAvoidrepair process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the repair process into distinct phases: identifying corrupted blocks, extracting necessary metadata, removing branch blocks, and reconstructing only the affected portions. This segmentation simplifies the overall repair process by breaking down the complex task of system recovery into manageable, targeted operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent uses metadata as an intermediary to facilitate the repair process. By extracting and utilizing metadata information, the system can locate and repair corrupted blocks without needing to perform a complete system replacement, thereby simplifying the repair process while ensuring complete data recovery.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10002055B2Efficient repair of B+ tree databases with variable-length records
Publication Date: 2018.06.19 NETAPP INC
  • US10002055B2 patent drawing
  • US10002055B2 patent drawing
  • US10002055B2 patent drawing

AI summary

Presented herein are methods, non-transitory computer readable media, and devices for efficiently repairing tree databases with variable-length records. Methods for repairing tree databases with variable-length records are disclosed which include: iterating the tree database, detecting at least one recoverable leaf block, reducing the at least one recoverable leaf block to its legally formatted contents, and writing the at least one recoverable leaf block back into the tree database; processing the at least one recoverable leaf block to ensure the at least one recoverable leaf block represents a disjoint region within a record space within the tree database; and rebuilding branch blocks as necessary to provide a lookup and organizational index for the at least one recoverable leaf block.