Database Identifier Reconciliation Using Immutable Asset UIDs

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing data backup systems face challenges in maintaining consistent identification of assets over their lifetime due to database identifiers that change with asset attributes, leading to potential data loss when identifiers are updated.

Innovation Solution

Implementing an immutable unique identifier (UID) for each asset that remains unchanged throughout its lifetime, ensuring all asset copies are protected and managed consistently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If database identifiers are updated to reflect changes in asset attributes, then the identifiers remain accurate and up-to-date, but data loss occurs and protection continuity is broken

Engineering Contradiction:

Improveidentifier accuracyVSAvoidprotection continuity

Core Design Contradiction:

Measurement precisionVSReliability

Solution Approach 1:

The patent segments the identifier system into two distinct parts: database identifiers (DBIDs) that change with asset attributes and immutable unique identifiers (UIs) that remain constant. This segmentation allows each identifier to serve its specific purpose without interfering with the other, resolving the contradiction between accuracy and continuity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The immutable unique identifier acts as an intermediary that links multiple changing DBIDs to a single persistent asset. When a DBID changes due to attribute updates, the UI remains unchanged and continues to provide the stable reference needed for maintaining protection continuity across all asset copies.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If immutable unique identifiers are implemented, then protection continuity is maintained, but system complexity increases due to dual identifier management

Engineering Contradiction:

Improveprotection continuityVSAvoididentifier management

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary action by generating immutable unique identifiers upfront when assets are first created or imported, before any attribute changes occur. This preliminary establishment of stable identifiers simplifies subsequent operations, as the UI serves as a permanent anchor point that doesn't require updates or reassignment.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating and storing multiple DBIDs that reference the same immutable UI. Instead of modifying the UI when attributes change, the system generates new DBIDs that copy the linking function to the asset, maintaining simplicity in the core identifier while allowing flexibility in the references.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS12566880B2Seamless updating and reconciliation of database identifiers generated by different agent versions

Publication Date: 2026.03.03 DELL PROD LP

AI summary

In general, the technology relates to a method for managing databases, the method includes receiving, by a data manager, an asset notification comprising a first database identifier (DID) for a database and a second DID for the database, and performing, using the asset notification, an asset records update operation, wherein the data manager is configured to perform data protection on the database.