Immutable Unique Identifiers for Database Protection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data protection systems face challenges in efficiently managing and protecting assets like databases, especially when database identifiers change, leading to data loss and unavailability.

Innovation Solution

The implementation of immutable unique identifiers for assets, which are generated based on asset attributes and remain unchanged throughout the asset's lifetime, allowing for effective protection and management of assets across system changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If database identifiers are used to manage and protect assets, then asset protection can be implemented, but data loss and unavailability occur when identifiers change

Engineering Contradiction:
Improveasset protection reliabilityVSAvoiddata loss
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system performs preliminary actions by capturing the complete set of asset attributes at the moment of identification and storing them as an immutable identifier. This preliminary capture ensures that regardless of future attribute changes, the original identification remains valid, preventing data loss and maintaining protection reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a copy of the asset's identification state by generating an immutable identifier from a snapshot of attributes. This copy preserves the identification across time despite attribute changes, allowing the system to maintain reliable protection without data loss when attributes evolve.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If database identifiers are changed to reflect updates, then system adaptability improves, but existing protection relationships are broken

Engineering Contradiction:
Improvesystem adaptabilityVSAvoidprotection relationship reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system segments the identification into two parts: a mutable attribute set that can change to reflect updates, and an immutable identifier that remains constant. This segmentation allows the system to adapt to changes while maintaining reliable protection relationships through the unchanging identifier.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The immutable identifier acts as an intermediary between the changing asset attributes and the protection system. It mediates the relationship by providing a stable reference point that connects protection policies to assets even when attributes change, thus maintaining reliability while allowing adaptability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If backup copies are created with current identifiers, then backup efficiency improves, but copies become inaccessible when identifiers change

Engineering Contradiction:
Improvebackup efficiencyVSAvoidcopy accessibility
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The system performs preliminary action by attaching the immutable identifier to backup copies at the time of creation. This ensures that copies retain their accessibility through the unchanging identifier even after the asset's attributes change, maintaining both efficiency and accessibility.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates backup copies that inherit the immutable identifier from the asset. This copying mechanism ensures that copies remain accessible through the stable identifier throughout the asset's lifecycle, preventing information loss while maintaining backup efficiency.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12314141B2Utilizing immutable unique identifiers to manage database protection
Publication Date: 2025.05.27 DELL PROD LP
  • US12314141B2 patent drawing
  • US12314141B2 patent drawing
  • US12314141B2 patent drawing

AI summary

In general, the technology relates to a method for managing databases, the method includes receiving a database identifier (DID) for a database, generating, using the DID, a unique identifier (UID) for the database, determining, after the generating, that the database is associated with a data protection policy, and permitting backup operations specifying the UID to be serviced by an agent operatively connected to the database.