Dynamic Container Backup Scheduling via Alert Event Analysis

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Containers experiencing frequent alert events often have a backup frequency that is insufficient to maintain data integrity, leading to potential data loss or corruption.

Innovation Solution

A method is implemented where a scheduling agent analyzes event entries to detect repeating alert events and compares their frequency to the existing backup frequency, generating a backup schedule warning to recommend a more frequent backup schedule to maintain data integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If backup frequency is increased to match high alert event frequencies, then data integrity is improved, but system resource consumption and operational complexity increase

Engineering Contradiction:

Improvedata integrityVSAvoidbackup schedule complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The backup schedule is made dynamic by automatically adjusting backup frequency based on monitored alert event patterns. The system transitions from static predetermined schedules to adaptive schedules that respond to actual container stability conditions, resolving the contradiction by optimizing data integrity only when necessary while minimizing unnecessary backups during stable periods

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system implements feedback mechanisms by monitoring alert events and using this information to adjust backup frequencies. The scheduling agent continuously observes container behavior and modifies backup schedules based on detected patterns, ensuring data integrity during unstable periods while avoiding excessive backups during stable operation

Inventive Principle:

Principle #23Feedback

2Reliability

If backup frequency is increased for containers with repeating errors, then data loss prevention is improved, but system productivity decreases due to more frequent backups

Engineering Contradiction:

Improvedata loss preventionVSAvoidsystem throughput

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system applies different backup frequencies to different containers based on their individual stability characteristics. Containers exhibiting repeating errors receive higher backup frequencies locally, while stable containers maintain lower frequencies, thus preventing data loss where needed without unnecessarily reducing overall system productivity

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The system applies backup actions selectively rather than uniformly across all containers. By identifying containers with repeating error patterns and applying increased backup frequency only to those specific cases, the system prevents data loss for vulnerable containers while maintaining normal productivity for stable containers

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS11593221B2Methods and systems for determining backup schedules

Publication Date: 2023.02.28 EMC IP HLDG CO LLC

AI summary

A method for generating a backup schedule, that includes receiving, by a scheduling agent, an event entry specifying an event associated with a container, determining that the event entry specifies an alert event, adding the event entry to a plurality of historical event entries in a historical event repository, determining that the plurality of historical event entries indicates a repeating error state of the container, determining that an error frequency of the repeating error state is greater than an existing backup frequency of a container backup schedule, and generating a backup schedule warning indicating a recommended backup frequency.