RAID Controller Checkpoint Recovery for Storage Replacement

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing methods for replacing a failed storage device in a RAID array are complex, time-consuming, and can result in data loss or degraded I/O performance due to the need for rebuilding the array during the replacement process, especially if the source storage device fails before the transfer is complete.

Innovation Solution

A system and method where the RAID controller initiates a transfer of data from a failing storage device to a replacement device, and upon failure, uses a parity operation to rebuild the device from the successfully transferred data and other array devices, allowing the rebuild to start from a checkpoint rather than from scratch, thus minimizing downtime and resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a direct copy operation is performed from source storage device to replacement storage device, then the replacement speed is improved, but if the source device fails during transfer, the entire operation is lost and must restart

Engineering Contradiction:
Improvereplacement speedVSAvoiddata loss risk
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary data transfer from the source storage device to the replacement storage device before failure occurs. The RAID controller initiates a direct copy operation that progresses as far as possible before the source device fails, capturing whatever data can be transferred in advance. This preliminary action reduces the amount of data that needs to be recovered through parity operations later.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system converts the harmful effect of source device failure into a beneficial outcome by using the partially transferred data that already exists on the replacement device. Instead of treating the failure as a complete loss requiring full rebuild, the system recognizes that some data was successfully transferred and uses that as a foundation, converting the failure into a partial success that accelerates the recovery process.

Inventive Principle:
Principle #22Blessing in disguise (Convert harm into benefit)

2Reliability

If a parity operation is performed to rebuild the storage device, then data redundancy is maintained, but I/O performance is degraded during the rebuild process

Engineering Contradiction:
Improvedata redundancyVSAvoidI/O performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs only the necessary parity operations for the portions of data that were not successfully transferred, rather than performing parity operations on the entire storage device. This partial action approach maintains data redundancy where needed while minimizing the impact on I/O performance by limiting the scope of the rebuild operation to only the missing data segments.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If the Replace Member function is cancelled due to source device failure, then data integrity is protected, but the replacement process must restart from scratch

Engineering Contradiction:
Improvedata integrityVSAvoidreplacement time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary data transfer operations that capture data before source device failure occurs. This preliminary action ensures that whatever data was successfully transferred is preserved and can be used in the recovery process, preventing the need to restart from scratch while maintaining data integrity through the use of proven good data.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system discards the failed source device and recovers the partially transferred data that exists on the replacement device. Instead of treating the entire replacement operation as failed, the system recovers the valuable partial transfers that were successfully completed before the failure, using them as a foundation for completing the replacement process.

Inventive Principle:
Principle #34Discarding and recovering

Data Source

PatentUS8650435B2Enhanced storage device replacement system and method
Publication Date: 2014.02.11 DELL PROD LP
  • US8650435B2 patent drawing
  • US8650435B2 patent drawing
  • US8650435B2 patent drawing

AI summary

Recovery of a failed storage device of a RAID array to a replacement storage device is improved by initiating recovery before failure of the storage device occurs. If failure occurs before completing the transfer of all information from the failed storage device to the replacement storage device, then the RAID controller identifies untransferred information to recreate the failed storage device at the replacement storage device by re-building only the untransferred information with a parity operation using information stored at the array.