Memory Backup Controller Change Log for Flash Wear Reduction

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Flash memory devices have a limited number of write-erase cycles, leading to data integrity deterioration and potential loss of data due to wear and tear.

Innovation Solution

A memory backup system that includes a memory backup controller which stores data from random access memory, records block identifications in a change log, detects backup trigger events, and copies identified data from an active memory device to a backup device, while clearing the change log.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data is continuously written to flash memory devices, then data storage capacity is utilized, but the write-erase cycle limit is exceeded causing data integrity deterioration

Engineering Contradiction:

Improvedata storage utilizationVSAvoiddata integrity

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system segments memory management by maintaining a change log that tracks modified data blocks separately from the actual data storage. This allows the system to identify and backup only the necessary portions of data, reducing unnecessary write operations to the flash memory device and preserving write-erase cycles while maintaining data integrity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by recording data block identifications in a change log before actual backup operations are needed. When a backup trigger event occurs, the system already has the information ready to know exactly which blocks need to be copied, enabling efficient incremental backups that minimize write operations and extend the memory device lifespan.

Inventive Principle:

Principle #10Preliminary action

2Productivity

If incremental backup using change log is implemented, then backup efficiency is improved, but additional memory space for change log is required

Engineering Contradiction:

Improvebackup efficiencyVSAvoidmemory space requirement

Core Design Contradiction:

ProductivityVSVolume of stationary object

Solution Approach 1:

The change log is implemented with a localized quality approach, storing only the essential identification information of modified data blocks rather than duplicating the actual data. This minimizes the space required for the change log while maximizing backup efficiency, as the log contains only metadata needed to identify which blocks require backup operations.

Inventive Principle:

Principle #3Local quality

Data Source

PatentUS9836370B2Backup memory administration using an active memory device and a backup memory device

Publication Date: 2017.12.05 LENOVO GLOBAL TECHNOLOGIES SWITZERLAND INTERNATIONAL GMBH

AI summary

Methods, systems, and computer program products for backup memory administration are provided. Embodiments include storing in an active memory device, by a memory backup controller, blocks of computer data received from random access memory; recording in a change log, by the memory backup controller, identifications of each block of computer data that is stored in the active memory device; detecting, by the memory backup controller, a backup trigger event; and responsive to the detecting of the backup trigger event: copying, by the memory backup controller, from the active memory device, to a backup memory device, the blocks of data identified in the change log; and clearing, by the memory backup controller, the change log.