Data Protection Policies Using Data Loss Threshold Backup Triggers

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current data protection systems rely on time-based schedules for backups, which fail to adequately address the business need to manage the cost of data loss, as they do not consider the value of data or the acceptable amount of data loss.

Innovation Solution

Implementing data protection policies that trigger backups based on defined data loss levels, such as transaction counts, percentage change rates, or other metrics, rather than fixed time intervals, to manage data loss more effectively.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If time-based backup schedules are used, then the backup system is simple to operate and implement, but the business cannot effectively manage or quantify the cost of data loss

Engineering Contradiction:

Improveease of implementing backup scheduleVSAvoidability to manage data loss cost

Core Design Contradiction:

Ease of operationVSLoss of information

Solution Approach 1:

The patent changes the fundamental parameter for triggering backups from time-based intervals to data loss level thresholds. Instead of backing up at fixed time schedules, the system monitors data changes and triggers backups when the accumulated data loss reaches a predefined threshold level, allowing businesses to directly control and quantify acceptable data loss costs

Inventive Principle:

Principle #35Parameter changes

2Reliability

If continuous protection methods are used, then data loss is minimized, but expenses increase significantly

Engineering Contradiction:

Improvedata protection levelVSAvoidbackup expense

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The patent implements a dynamic backup system that adjusts backup frequency based on actual data loss accumulation rather than operating continuously or on fixed schedules. The system dynamically triggers backups only when necessary, based on whether data loss has reached acceptable thresholds, optimizing the balance between protection level and operational cost

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system changes from continuous operation to event-driven operation based on data loss parameters. By monitoring data loss levels and triggering backups only when thresholds are exceeded, the system reduces unnecessary backup operations and associated costs while maintaining adequate protection levels

Inventive Principle:

Principle #35Parameter changes

3Reliability

If frequent backups are performed, then data loss risk is reduced, but system resources and time are consumed unnecessarily

Engineering Contradiction:

Improvedata loss riskVSAvoidbackup execution time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent changes the backup trigger parameter from time-based to data-loss-based. Backups are performed not based on time intervals but when the amount of data loss reaches predefined acceptable thresholds, eliminating unnecessary backups during periods of minimal data change

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS12632343B2Implementing data protection policies based on defined data loss levels

Publication Date: 2026.05.19 DELL PROD LP

AI summary

Providing data protection by triggering backups for data protection based on data loss threshold. A protection policy is configured to protect an asset stored in a storage device in a network. A metric representing an amount of change of data of the asset is defined, along with a threshold value of the metric. The system is periodically monitored to determine if the metric reaches the threshold, and if so, a backup of the asset is triggered under the protection policy. The trigger-based data protection system backs up data on the basis specific data asset change thresholds, rather than on simple time periods or on a continuous basis.