Client-Side Signature Repository for Collaborative Restore

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data management systems face challenges in efficiently managing and protecting data due to high demands on network bandwidth and system resources during backup and restore operations, particularly due to communication latency between primary and secondary storage, and the need for innovative techniques to handle rapidly growing data volumes.

Innovation Solution

The implementation of a client-side signature repository that stores signatures of data blocks in primary storage, allowing for efficient identification and retrieval of unique data blocks during backup and restore operations, reducing network traffic and latency by using a local repository to track and manage data blocks, and enabling collaborative sourcing across multiple clients.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data blocks are transferred between primary and secondary storage during backup and restore operations, then data protection and recovery are achieved, but network bandwidth consumption and communication latency increase

Engineering Contradiction:
Improvedata protectionVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts only the essential identifying information (signatures) of data blocks from the full data blocks themselves. The signature repository stores these compact signatures instead of complete data blocks, allowing the system to identify and track data blocks without transferring or storing their full content in the signature repository, thereby reducing network bandwidth consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs preliminary actions by pre-computing and storing signatures of data blocks in the signature repository before actual backup or restore operations. This allows the system to quickly identify which data blocks need to be transferred or have already been restored, reducing communication latency during operational phases.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If data blocks are transferred between primary and secondary storage during backup and restore operations, then data protection and recovery are achieved, but communication latency increases

Engineering Contradiction:
Improvedata recoveryVSAvoidcommunication latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent creates a copy of the signature information in the signature repository that mirrors the structure and organization of data blocks in primary storage. This signature copy enables rapid lookup and identification of data block locations without requiring actual data block transfers, thereby reducing communication latency during restore operations.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs preliminary actions by pre-computing and storing signatures of data blocks in the signature repository before actual backup or restore operations. This allows the system to quickly identify which data blocks need to be transferred or have already been restored, reducing communication latency during operational phases.

Inventive Principle:
Principle #10Preliminary action

3Quantity of substance

If deduplication is implemented to reduce redundant data storage, then storage utilization improves, but system complexity increases

Engineering Contradiction:
Improvestorage utilizationVSAvoidsystem complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent extracts only the essential identifying information (signatures) of data blocks from the full data blocks themselves. The signature repository stores these compact signatures instead of complete data blocks, allowing the system to identify and track data blocks without transferring or storing their full content in the signature repository, thereby reducing network bandwidth consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

4Reliability

If backup and restore operations are performed on rapidly growing data volumes, then data protection is maintained, but network bandwidth and system resources are heavily consumed

Engineering Contradiction:
Improvedata protectionVSAvoidsystem resource efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts only the essential identifying information (signatures) of data blocks from the full data blocks themselves. The signature repository stores these compact signatures instead of complete data blocks, allowing the system to identify and track data blocks without transferring or storing their full content in the signature repository, thereby reducing network bandwidth consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10956275B2Collaborative restore in a networked storage system
Publication Date: 2021.03.23 COMMVAULT SYSTEMS INC
  • US10956275B2 patent drawing
  • US10956275B2 patent drawing
  • US10956275B2 patent drawing

AI summary

A storage system according to certain embodiments includes a client-side signature repository that includes information representative of a set of data blocks stored in primary storage. During restore operations, the system can use the client-side signature repository to identify data blocks located in primary storage. The system can also use the client-side signature repository to identify multiple locations within primary storage where instances of some of the data blocks to be restored are located. Accordingly, during a restore operation of one client computing device, the system can source a data block to be restored to the client computing device from another client computing device that is in primary storage.