Machine Learning Predicts Data Flushes for Journal Retention

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Continuous replication systems face challenges in handling large data flushes, leading to resource strain and disruption, as they often require switching to 'fast forward' mode, which loses journal history and reduces recovery capabilities.

Innovation Solution

Implementing a machine learning-based prediction system to anticipate large data flushes, allowing the replication system to switch to fast forward mode in advance while retaining journal history through snapshots, ensuring full recovery granularity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If the system switches to fast forward mode during large data flushes, then resource consumption is reduced, but journal history is lost

Engineering Contradiction:
Improveresource consumptionVSAvoidjournal history
Core Design Contradiction:
Loss of energyVSLoss of information

Solution Approach 1:

The machine learning model predicts large data flushes before they occur, allowing the system to proactively switch to fast forward mode in advance. This preliminary action enables resource optimization while the snapshot mechanism ensures journal history is preserved by capturing the state before the flush occurs

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates snapshots (copies) of the journal data before switching to fast forward mode during predicted large flushes. This copying mechanism preserves the journal history for recovery purposes while allowing the fast forward mode to reduce resource consumption during the actual flush operation

Inventive Principle:
Principle #26Copying

2Reliability

If the system maintains continuous replication mode during large data flushes, then journal history is preserved, but resource strain and disruption increase

Engineering Contradiction:
Improvejournal retentionVSAvoidresource efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system dynamically switches between continuous replication mode and fast forward mode based on predictions from the machine learning model. This dynamic adjustment allows the system to maintain journal retention through continuous replication during normal operation while switching to resource-efficient fast forward mode during predicted large flushes, with snapshots ensuring reliability

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The machine learning model continuously analyzes replication traffic patterns and provides feedback predictions about upcoming large flushes. This feedback loop enables the system to adjust its operational mode proactively, maintaining journal reliability through continuous replication while optimizing resource efficiency by switching to fast forward mode when large flushes are predicted

Inventive Principle:
Principle #23Feedback

3Loss of energy

If the system uses fast forward mode without prediction, then resource consumption is reduced, but redundant replication work is performed

Engineering Contradiction:
Improveresource consumptionVSAvoidredundant work
Core Design Contradiction:
Loss of energyVSLoss of time

Solution Approach 1:

The machine learning model performs preliminary analysis of replication traffic patterns to predict large data flushes before they occur. This prediction capability allows the system to switch to fast forward mode at the optimal moment, avoiding both premature switching that would cause redundant work and delayed switching that would maintain high resource consumption too long

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10909073B2Automatic snapshot and journal retention systems with large data flushes using machine learning
Publication Date: 2021.02.02 EMC IP HLDG CO LLC
  • US10909073B2 patent drawing
  • US10909073B2 patent drawing
  • US10909073B2 patent drawing

AI summary

Predicting large data flushes by collecting usage data for system assets, analyzing the data using machine learning on each asset and the whole system to determine usage trends, predicting a next large data flush using a time-series model, and determining if a size of the predicted next flush size is too large relative to journal storage space in order to advance fast forward mode. Further, protecting history information by pausing distribution of data from journal volumes to replica volumes, taking storage-level snapshots of the replica and the journal volumes, storing a snapshot timestamp for each of the storage-level snapshots in a snapshot database prior to advancing the fast forward mode or un-pausing distribution.