Storage Node Switch Data Collision Prevention

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In data storage systems, switching from a primary storage node to a backup node can cause data collisions and resource inefficiencies due to ongoing data backup operations, particularly when the regular backup node is not synchronized in real-time with the primary node, leading to costly full backups and resource wastage.

Innovation Solution

A method that determines if there is an ongoing data backup operation between the primary and regular backup nodes during a switch, ceasing the data backup operation to prevent collisions and allowing incremental backups based on common snapshots, thereby avoiding full backups and optimizing resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If real-time backup storage node switches to primary storage node, then service availability is improved, but data collision occurs with ongoing regular backup operations

Engineering Contradiction:
Improveservice availabilityVSAvoiddata collision
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary detection to check whether a regular backup operation is in progress before executing the switch operation. If a backup is detected, the switch is postponed or adjusted to avoid data collision. This preliminary checking mechanism prevents the harmful effect of data collision while maintaining service availability.

Inventive Principle:
Principle #10Preliminary action

2Loss of energy

If regular backup operation continues during node switch, then backup cost is reduced, but data consistency is compromised

Engineering Contradiction:
Improvebackup costVSAvoiddata consistency
Core Design Contradiction:
Loss of energyVSManufacturing precision

Solution Approach 1:

The system implements feedback by detecting the status of regular backup operations and using this information to control the timing of switch operations. The detection mechanism provides feedback about ongoing backups, and the switch operation is adjusted based on this feedback to ensure data consistency while allowing regular backups to continue.

Inventive Principle:
Principle #23Feedback

3Manufacturing precision

If full backup is performed after data collision, then data consistency is restored, but resource consumption increases

Engineering Contradiction:
Improvedata consistencyVSAvoidresource consumption
Core Design Contradiction:
Manufacturing precisionVSQuantity of substance

Solution Approach 1:

The system applies preliminary anti-action by preventing data collision from occurring in the first place through the detection mechanism. By detecting ongoing regular backup operations before the switch, the system avoids the need for corrective full backups, thereby preventing resource consumption associated with restoring data consistency after collision.

Inventive Principle:
Principle #9Preliminary anti-action

Data Source

PatentUS11314599B2Method, apparatus and computer program product for data replication
Publication Date: 2022.04.26 EMC IP HLDG CO LLC
  • US11314599B2 patent drawing
  • US11314599B2 patent drawing
  • US11314599B2 patent drawing

AI summary

Techniques perform data backup. Such techniques involve: in response to a first storage node to be switched to a second storage node, determining whether there is an ongoing data backup operation between the first storage node and a third storage node; and in response to the ongoing data backup operation between the first and third storage nodes, ceasing the data backup operation. The second storage node is used for backing up data of the first storage node in real time and the third storage node is used for backing up the data of the first storage node periodically. Accordingly, colliding operations can be prevented, system resource can be saved and processing efficiency can be improved.