Recovery Module Monitoring for Data Migration Failure Events

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems lack effective methods for managing and recovering from failure events during data migration between logical devices, leading to incomplete or failed recovery processes.

Innovation Solution

A recovery module is employed to monitor, analyze, and remediate failure events during data migration by tracking event entries, determining failure occurrences, and implementing corrective actions such as re-establishing connections, adjusting packet sizes, or updating self-recovery policies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data migration is performed between logical devices, then data can be transferred and recovered, but failure events may occur during migration causing incomplete recovery

Engineering Contradiction:
Improverecovery completionVSAvoidfailure events
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary actions by establishing a recovery module before data migration occurs. This module proactively monitors for failure events and prepares remediation strategies in advance, ensuring that when failures do occur, the recovery process can immediately address them rather than reacting passively after damage occurs.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The recovery module continuously monitors the data migration process and receives feedback about failure events. Based on this feedback, the system dynamically adjusts recovery strategies and implements corrective actions, creating a closed-loop system that adapts to actual migration conditions rather than following a rigid predetermined path.

Inventive Principle:
Principle #23Feedback

2Reliability

If failure events are not monitored and addressed, then the recovery process remains simple, but data migration may fail or become incomplete

Engineering Contradiction:
Improvedata migration completionVSAvoidrecovery management system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The recovery module is designed to autonomously monitor for failure events, analyze their impact, and execute remediation actions without requiring external intervention. This self-service capability reduces the need for complex external management systems while ensuring reliable data migration completion through automated failure detection and recovery.

Inventive Principle:
Principle #25Self-service

3Productivity

If the recovery process does not account for failure events, then the process is faster and simpler, but system stability and data integrity cannot be maintained

Engineering Contradiction:
Improverecovery process speedVSAvoidsystem stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The recovery module operates continuously during data migration, constantly monitoring for failure events and immediately executing remediation actions when detected. This continuous monitoring and response ensures that the recovery process maintains system stability and data integrity without significant interruptions, balancing speed with reliability through uninterrupted proactive management.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS12405863B2Method and system for managing failure events of a recovery process using a recovery module
Publication Date: 2025.09.02 DELL PROD LP
  • US12405863B2 patent drawing
  • US12405863B2 patent drawing
  • US12405863B2 patent drawing

AI summary

A system for remediating a recovery process such as a migration of data includes an event database, a monitoring component, programmed to: monitor a source device to detect an initiation of a recovery process, wherein the recovery process is migration of application data from the source device to a target device, an analysis component programmed to: monitor the event database to detect a new event entry, wherein the event entry is associated with the recovery process of the source device, make a determination that the new event entry is associated with a failure event, based on the determination, provide the new event entry to a remediating component, programmed to obtain a recommendation for remediation based on the failure event and initiate the remediation based on the recommendation for remediation.