Runtime Volatile Memory Backup via Partial Bank Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems that backup data from volatile memory to non-volatile memory during power-loss events face issues such as reliance on a backup power source, potential data corruption, and time-consuming full backups, which can lead to system unreliability and increased boot times.
Innovation Solution
Implementing a backup controller that performs partial backups during normal system runtime, deactivating only the necessary volatile memory domains for backup, allowing the system to continue operating and using self-refresh modes to transfer data to non-volatile memory, thereby reducing the need for a large backup power source and minimizing data corruption risks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If full backup is performed during runtime, then data reliability is improved, but system productivity deteriorates due to memory bus occupation
Solution Approach 1:
The patent divides the memory system into multiple banks (first bank and second bank) that can operate independently. During runtime, only the necessary bank is deactivated for backup operations while other banks remain accessible, allowing partial backup without complete system halt and maintaining productivity.
Solution Approach 2:
The patent implements partial backup by deactivating only the specific memory bank containing critical data rather than performing a complete full backup of all memory. This selective approach reduces backup time and maintains system productivity while ensuring data reliability for the backed-up portion.
2Stability of the object's composition
If backup is performed at power-loss event, then data persistence is achieved, but system reliability deteriorates due to backup power dependency
Solution Approach 1:
The patent performs backup operations during normal runtime before power-loss events occur. The backup controller proactively copies data from volatile memory to non-volatile memory while the system is operational, eliminating dependency on backup power sources and improving system reliability.
3Productivity
If volatile memory is accessed during backup, then system productivity is maintained, but data corruption risk increases
Solution Approach 1:
The patent segments memory into multiple independent banks with separate controllers. During backup of one bank, other banks remain accessible for normal operations. The segmentation isolates the backup operation to specific memory regions, preventing corruption risks from propagating to the entire memory system.
Solution Approach 2:
The backup controller acts as an intermediary that manages the backup process without completely halting memory operations. It coordinates between the memory controller and non-volatile memory, allowing selective access to different memory banks during backup to maintain productivity while ensuring data integrity.
Data Source
AI summary
Examples provide systems and a method for handling errors during run-time back up of volatile memory. The method includes initiating a backup of a volatile memory domain to a non-volatile memory domain. Memory registers are polled for completion of the backup. It is determined if the backup was successful. If not successful, an operating system (OS) is notified that the backup failed, and the backup is completed to an alternate media.