Intra-backup Anomalous Object Management and Exclusion Rules

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing technologies struggle to effectively manage anomalous objects during backup operations in enterprise IT environments, leading to backup failures and reduced performance.

Innovation Solution

A method for anomalous object management during backup operations, which involves identifying target assets, partitioning them into slices, identifying anomalous objects, excluding them from backup data, creating metadata records, and writing the data and metadata to target storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If backup operations include all objects in target assets, then backup completeness is improved, but backup failure rate increases due to anomalous objects

Engineering Contradiction:

Improvebackup success rateVSAvoidbackup data volume

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The backup system segments the backup process into distinct phases: identification phase (detecting anomalous objects), exclusion phase (removing anomalous objects from backup), and execution phase (backing up remaining objects). This segmentation allows the system to maintain backup completeness for valid objects while excluding problematic anomalous objects, thereby improving backup success rate without unnecessarily reducing backup data volume.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system performs preliminary identification and exclusion of anomalous objects before the actual backup execution. By detecting and marking anomalous objects in advance, the system prevents backup failures during the main backup process, ensuring smoother operation and higher success rates while maintaining efficiency.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If backup operations process all target asset objects, then data protection coverage is improved, but backup performance deteriorates due to anomalous objects

Engineering Contradiction:

Improvedata protection coverageVSAvoidbackup speed

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system extracts and removes anomalous objects from the backup process before execution. By identifying these problematic objects and excluding them from the backup data stream, the system prevents performance degradation during backup operations while maintaining comprehensive protection for all valid objects, thus preserving both data protection coverage and backup speed.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The system skips over anomalous objects during the backup process, rapidly identifying and bypassing them without halting the overall backup operation. This allows the backup to continue at high speed for all valid objects, maintaining productivity while ensuring complete protection coverage for protectable data.

Inventive Principle:

Principle #21Skipping (Rushing through)

3Quantity of substance

If backup operations attempt to backup anomalous objects, then backup completeness is improved, but backup reliability decreases leading to failures

Engineering Contradiction:

Improvebackup data completenessVSAvoidbackup operation stability

Core Design Contradiction:

Quantity of substanceVSReliability

Solution Approach 1:

The system applies preliminary anti-action by proactively identifying and excluding anomalous objects before they can cause backup failures. This preventive measure maintains backup operation stability and reliability while preserving the completeness of backup data for all valid objects, as the system specifically targets only the problematic anomalous objects for exclusion.

Inventive Principle:

Principle #9Preliminary anti-action

4Reliability

If the system excludes anomalous objects during backup, then backup success rate is improved, but backup metadata complexity increases

Engineering Contradiction:

Improvebackup success rateVSAvoidmetadata structure

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system introduces an intermediary metadata structure that tracks excluded anomalous objects separately from the main backup data. This intermediary layer maintains a record of what was excluded and why, allowing the system to improve backup success rate by excluding problematic objects while managing metadata complexity through organized, structured tracking rather than unmanaged complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS12235739B2Intra-backup anomalous object management and post-backup exclusion rule creation

Publication Date: 2025.02.25 DELL PROD LP

AI summary

A method, non-transitory computer readable medium, and a system for intra-backup anomalous object management and post-backup exclusion rule creation. Enterprise information technology environments often include any number of assets maintaining vast quantities of data and state. Any asset, in turn, may be riddled with various anomalous objects that tend to cause backup failure. Embodiments described herein address backup failure due to the presence of anomalous objects by, while any number of assets undergo backup, objects across said asset(s) may be assessed against object exclusion lists, populated during a pre-backup stage, to identify any anomalous objects of said objects. Once identified, the anomalous object(s) (or metadata descriptive thereof) may be recorded as backup metadata, which may be used in the post-backup creation of one or many exclusion rule(s). The exclusion rule(s) impact, and thus adjust, the backup policy/policies associated with the asset(s) on which the anomalous object(s) had been identified.