Gold Image Library Deduplication via Hash Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data protection systems inefficiently manage Gold image data, leading to repeated storage and increased resource usage due to the static nature of Gold images being backed up alongside dynamic user content data, resulting in wasted storage and processing resources.

Innovation Solution

Implementing a Gold image library management system that centralizes Gold image data storage, using a Common Data Protection Target (CDPT) to store Gold image data separately from user content data, allowing deduplication and reducing redundant storage across multiple data protection targets.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If Gold image data is backed up alongside user content data on multiple data protection targets, then data protection coverage is improved, but storage resource usage increases due to repeated storage of static Gold image data

Engineering Contradiction:
Improvedata protection coverageVSAvoidstorage resource usage
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system segments data protection into two distinct components: Gold image data storage and user content data storage. Gold image data is stored centrally on a single data protection target, while user content data is stored on multiple data protection targets. This segmentation eliminates redundant storage of static Gold image data across multiple targets while maintaining comprehensive data protection coverage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The invention extracts static Gold image data from the routine backup process and separates it from dynamic user content data. By taking out Gold image data and storing it independently on a dedicated data protection target, the system prevents repeated storage of this static data while ensuring it remains protected and accessible when needed.

Inventive Principle:
Principle #2Taking out (Extraction)

2Quantity of substance

If Gold image data is stored centrally on a Common Data Protection Target, then storage efficiency is improved, but system complexity increases due to hash migration management across multiple targets

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

Solution Approach 1:

The system performs preliminary actions by establishing a centralized Gold image storage structure on a Common Data Protection Target before routine backups occur. Hash values of Gold image data are pre-calculated and stored, enabling efficient deduplication and avoiding the need for complex real-time analysis during backup operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The invention implements feedback mechanisms where hash values from the centralized Gold image storage are continuously compared against incoming backup data. This feedback loop enables automatic identification and elimination of redundant Gold image data, simplifying the management of distributed data protection targets through automated rather than manual processes.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11797206B2Hash migration using a gold image library management system
Publication Date: 2023.10.24 EMC IP HLDG CO LLC
  • US11797206B2 patent drawing
  • US11797206B2 patent drawing
  • US11797206B2 patent drawing

AI summary

Embodiments for migrating hash values for backup data blocks in a network of data protection targets (DPTs) and a common data protection target implementing a Gold image library management system in which backups of Gold images used as templates for physical machines and virtual machines are stored on the CDPT. The CDPT and each DPT stores backup data split into chunks that are uniquely identified by a respective hash of its contents, and maintains data structures comprising the hash, chunk size, chunk data, and a list of DPT and CDPT identifiers. The hashes are partitioned into a set of buckets in the CDPT. A Bloom filter is generated for each bucket of hashes, and stored in each DPT so that each DPT stores Bloom filters for all CDPTs in the network. Each DPT checks its list of hashes against the Bloom filters in each of the DPTs to determine whether to keep or free chunks of data.