Storage Volume Suspension During Site Switchover

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Non-detectable data loss occurs during site switchover in high availability data storage systems due to network disruptions, leading to incomplete data sets and potential errors in financial and manufacturing systems.

Innovation Solution

Implementing a volume-specific attribute to suspend storage volumes during switchover operations, ensuring data recovery and validation before resuming processing, thereby preventing automatic access and allowing for integrity verification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If automatic site switchover is implemented for high availability, then system availability is improved, but non-detectable data loss may occur due to network disruptions

Engineering Contradiction:
Improvesystem availabilityVSAvoiddata loss
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system performs preliminary actions by suspending the volume before switchover occurs and maintaining it in a suspended state after switchover. This preliminary suspension prevents automatic access and allows time for data recovery and validation, ensuring that incomplete data transfers during network disruptions are detected and handled appropriately.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by monitoring the suspended volume state and requiring explicit clearance before resuming processing. This feedback loop ensures that data integrity is verified before the volume returns to normal operation, preventing propagation of corrupted or incomplete data while maintaining high availability through controlled failover.

Inventive Principle:
Principle #23Feedback

2Manufacturing precision

If volume is suspended during switchover to prevent data loss, then data integrity is improved, but processing time is increased

Engineering Contradiction:
Improvedata integrityVSAvoidprocessing time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The volume is suspended in advance of potential data corruption risks during switchover, and remains suspended until validation is complete. This preliminary action ensures data integrity is maintained while the suspension duration is minimized through efficient validation processes, balancing precision requirements with time constraints.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If automatic resumption of processing occurs after switchover, then productivity is improved, but risk of errors increases

Engineering Contradiction:
Improveprocessing throughputVSAvoiderror rate
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary validation of data integrity before allowing automatic resumption of processing. The volume remains in a suspended state after switchover, preventing automatic access, and only resumes when validation confirms data completeness. This preliminary check ensures productivity is restored while minimizing error rates through verified data integrity.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11650891B2Preventing non-detectable data loss during site switchover
Publication Date: 2023.05.16 NETAPP INC
  • US11650891B2 patent drawing
  • US11650891B2 patent drawing
  • US11650891B2 patent drawing

AI summary

Methods, systems, and computer program products for preventing non-detectable data loss during site switchover are disclosed. A computer-implemented method may include receiving a request to perform a switchover from a first node to a second node, determining whether to place a storage volume involved in the switchover in a suspended state, setting the storage volume in the suspended state based on determining that the storage volume is to be placed in the suspended state, and maintaining the storage volume in the suspended state after completing the switchover. In an example, the storage volume may be placed in a suspended state based on examining a volume-specific attribute indicating whether the storage volume is to be suspended when involved in a switchover. In one example, each storage volume involved in a switchover may be placed in a suspended state when indicated as part of a switchover request.