Write Controller Backup Data Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Solid state storage systems face inefficiencies in handling program failures due to the need for large storage capacity to save write data temporarily, which is unattractive in low-cost systems, and existing recovery techniques require excessive storage resources.
Innovation Solution
A process involving a write controller that generates backup write data through combining received write data using techniques like XOR encoding, allowing for incremental storage and release of data without waiting for confirmation, and utilizing internal or external memory for storing backup data to minimize storage requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the storage controller saves all write data until successfully committed, then program failure recovery is enabled, but storage capacity requirements increase significantly
Solution Approach 1:
The patent extracts only the essential information needed for recovery (write data associated with failed programs) rather than storing all write data. The system selectively saves backup write data only when program failures are detected, reducing overall storage requirements while maintaining recovery capability.
Solution Approach 2:
The system performs preliminary actions by saving backup write data in advance when programs are successfully written, so that recovery can be performed quickly when failures occur. This preliminary storage of critical data enables fast recovery without requiring large storage capacity to retain all historical data.
2Reliability
If the storage controller waits for write confirmation before releasing data, then data integrity is ensured, but processing time increases
Solution Approach 1:
The storage controller saves backup write data in advance (preliminarily) before waiting for program confirmation. This allows the system to prepare recovery data while the write operation is still in progress, reducing the time needed for subsequent recovery operations without compromising data integrity.
Solution Approach 2:
The system continues useful actions by saving backup data concurrently with the write operation rather than sequentially. The backup save operation and the write confirmation wait happen in parallel, maintaining system productivity while ensuring data integrity through the backup mechanism.
3Reliability
If larger amounts of DRAM or SRAM are used to store write data, then program failure recovery capability is improved, but system cost increases
Solution Approach 1:
The patent applies this principle by extracting only the necessary backup write data for recovery purposes rather than storing all write data in expensive DRAM/SRAM. This selective approach reduces the amount of high-cost memory needed while maintaining effective recovery capability.
Solution Approach 2:
The system creates a copy of only the essential write data (backup write data) rather than storing all original data in expensive memory. This copying approach preserves the necessary recovery information while using minimal additional storage capacity, reducing overall system cost.
Data Source
AI summary
A plurality of write data is received and combined to obtain backup write data. The plurality of write data is stored in storage. On a storage controller, the plurality of write data is released without waiting for a confirmation associated with writing the plurality of write data to the storage. The backup write data is stored.