Soft Delete Tagging for Host Record Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems face inefficiencies in managing records on hosts, leading to potential data loss due to inadequate tagging and deletion processes, which can result in accidental loss of data.

Innovation Solution

A system that identifies and tags previously discovered records with soft delete tags or hard delete tags, allowing for configurable time periods before deletion, and resurrects records if they are rediscovered, thereby improving record management efficiency and preventing accidental data loss.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If records are deleted immediately when no longer discovered, then storage space is freed and system efficiency is improved, but data loss occurs due to inadequate tagging and deletion processes

Engineering Contradiction:
Improvesystem efficiencyVSAvoiddata loss prevention
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system applies soft delete tags to records before actual deletion occurs. This preliminary action allows records to be marked for deletion while maintaining them in the system temporarily, enabling potential recovery if rediscovered during the retention period, thus preventing permanent data loss while still freeing up system resources

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a configurable retention period between soft delete tagging and hard delete execution. This cushioning period acts as a safety buffer that prevents immediate permanent deletion, allowing for error correction or record recovery if the record is rediscovered before the hard delete is executed

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

2Reliability

If records are retained indefinitely to prevent data loss, then data integrity is maintained, but storage resources are wasted and system performance deteriorates

Engineering Contradiction:
Improvedata integrityVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system dynamically manages record retention based on discovery status. Records that are actively discovered and used are retained, while records that are no longer discovered are progressively transitioned through soft delete to hard delete after a configurable period, optimizing storage usage while maintaining data integrity for active records

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system discards records through a staged process (soft delete then hard delete) but maintains the ability to recover records during the soft delete period if they are rediscovered. This allows the system to efficiently discard obsolete records while preserving the ability to recover important data if needed

Inventive Principle:
Principle #34Discarding and recovering

3Reliability

If a staged deletion process with soft delete tags is implemented, then data loss is prevented through configurable retention periods, but system complexity increases due to additional tagging and verification steps

Engineering Contradiction:
Improvedata loss preventionVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system automatically manages the staged deletion process through discovery events. The local data manager autonomously identifies records to delete, applies soft delete tags, monitors for rediscovery, and executes hard deletes based on configurable policies without requiring manual intervention, reducing operational complexity despite the enhanced deletion process

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12007982B2Method and system for identifying and deleting records on hosts
Publication Date: 2024.06.11 EMC IP HLDG CO LLC
  • US12007982B2 patent drawing
  • US12007982B2 patent drawing
  • US12007982B2 patent drawing

AI summary

A system for identifying and deleting records of hosts includes a local data manager. The local data manager identifies a discovery event associated with the host and a record type of record types, obtains, in response to identifying, all previously discovered records on the host associated with the record type from a host record repository, obtains discovered records associated with the record type and associated with the host, after obtaining all discovered records and previously discovered records, selects a previously discovered record of the previously discovered records, makes a determination that the previously discovered record does not match any discovered records of the discovered records and is not tagged with a soft delete tag or a hard delete tag, and in response to the determination, tags the previously discovered record with a soft delete tag, and notifies a data manager of modifications to the previously discovered records.