Persistent Item Tags for Backup Erasure Tracking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In deduplication systems, it is challenging to determine when all data of a specific backup item has been erased, especially when shared chunks are not erased immediately, leading to inefficiencies and security concerns during secure erase procedures.

Innovation Solution

The implementation of persistent item tags in container indexes to track which backup items reference or have referenced specific chunks, allowing the system to determine when all chunks associated with a backup item have been erased, and the use of secure flags for efficient secure erasure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If shared chunks are retained for other backup items, then storage efficiency is improved through deduplication, but the ability to determine when all data of a specific backup item has been erased deteriorates

Engineering Contradiction:
Improvestorage efficiencyVSAvoiderasure status tracking
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The patent introduces persistent item tags as an intermediary mechanism between chunks and backup items. These tags are stored in container indexes and serve as mediators to track the relationship between backup items and chunks even after the backup items are erased. The tags persist in the system and allow the deduplication system to determine when all references to a backup item's data have been removed, resolving the contradiction between retaining shared chunks for storage efficiency and tracking erasure status.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If immediate erasure of chunks is performed when backup items are deleted, then data security is improved, but storage efficiency deteriorates due to loss of deduplication benefits

Engineering Contradiction:
Improvedata securityVSAvoidstorage efficiency
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent implements preliminary action by establishing persistent item tags in container indexes before backup items are erased. These tags are prepared in advance to track the fate of chunks associated with backup items. When a backup item is erased, the pre-established tags enable the system to monitor chunk references without requiring immediate erasure, thus maintaining both data security through tracking and storage efficiency through delayed erasure until all references are confirmed gone.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If persistent item tags are stored in container indexes, then the ability to track erasure status is improved, but device complexity increases

Engineering Contradiction:
Improveerasure status trackingVSAvoiddata structure complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent applies universality by designing persistent item tags with multi-functional capabilities. The tags not only track erasure status but also maintain references to chunks for deduplication operations, enable secure erasure procedures, and support data integrity verification. By making the tags multi-functional, the patent reduces the need for separate tracking mechanisms, thereby limiting the increase in device complexity while achieving comprehensive erasure status tracking.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11940956B2Container index persistent item tags
Publication Date: 2024.03.26 HEWLETT PACKARD ENTERPRISE DEV LP
  • US11940956B2 patent drawing
  • US11940956B2 patent drawing
  • US11940956B2 patent drawing

AI summary

Examples may include container index persistent item tags. Examples may store chunk signatures in at least one container index and, for each chunk signature, store at least one persistent item tag identifying a respective backup item that references or formerly referenced the chunk signature. Examples may determine that all chunks formerly referenced by a backup item have been erased based on the persistent item tags in the at least one container index and output an indication that the backup item has been erased.