Blockchain Snapshot Validation for Cloud Data Integrity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data management systems face challenges in validating snapshots before using them for failover recovery, which is crucial for ensuring data integrity and adherence to service level agreements.

Innovation Solution

The implementation of blockchain technology to store a history of snapshots, acting as a source of truth, by generating hash values associated with snapshots and storing them on the blockchain, allowing for subsequent verification of snapshot integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional centralized storage methods are used for snapshots, then storage and retrieval are simple, but data integrity and security cannot be guaranteed against tampering

Engineering Contradiction:
Improvesnapshot integrityVSAvoidvalidation system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces blockchain as an intermediary layer between snapshot storage and validation. Hash values of snapshots are stored on the blockchain, which acts as a trusted mediator that guarantees data integrity without requiring complex centralized validation mechanisms. This resolves the contradiction by improving reliability through the blockchain intermediary while keeping the overall system architecture relatively simple.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If blockchain technology is implemented for snapshot validation, then data integrity and security are enhanced, but system complexity increases

Engineering Contradiction:
Improvefailover recovery reliabilityVSAvoiddata management system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the data management system into distinct components: snapshot generation, hash computation, blockchain interaction, and validation. By dividing the system into modular segments with clear responsibilities, the complexity of implementing blockchain for failover recovery is managed and organized, making the system more maintainable and understandable.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by computing and storing hash values of snapshots on the blockchain before failover recovery is needed. This advance preparation ensures that when recovery is required, validation can be performed quickly and reliably without adding complex real-time validation mechanisms during the critical recovery process.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If snapshots are validated before failover, then data security is improved, but recovery time may increase due to validation overhead

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

Solution Approach 1:

The patent performs validation preparation in advance by storing snapshot hash values on the blockchain before recovery is needed. During actual failover recovery, validation is performed by comparing the recovered snapshot hash with the stored blockchain hash, which is a fast operation. This preliminary action approach ensures data security while minimizing the time loss during critical recovery operations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12306722B2Blockchain for cloud data management
Publication Date: 2025.05.20 RUBRIK INC
  • US12306722B2 patent drawing
  • US12306722B2 patent drawing
  • US12306722B2 patent drawing

AI summary

A method for data management is described. The method may include generating a first snapshot of a first state of a data object, generating, using metadata associated with the first snapshot of the first state, a first hash value, and storing the first hash value to a blockchain. If the data object or device or system supporting the data object fails, then a failover procedure may be used to recover the data object. The method may include receiving an instruction to recover the first state of the data object using the first snapshot, retrieving the first hash value from the blockchain, comparing the first hash value retrieved from the blockchain to a second hash value of the metadata associated with the first snapshot, and determining, based at least in part on a result of the comparing, whether the first snapshot stored in the data management system is unmodified.