Selective Application Data Backup Controller
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems fail to ensure complete persistence of application program data in system memory during system failures, as data backed up in non-volatile storage can be overwritten during subsequent failures or recovery processes, leading to data loss.
Innovation Solution
Implementing a system-level component that selectively enables and disables data backup for application data objects in system memory, using a memory backup controller to copy data to non-volatile storage and restore it upon recovery, while preventing overwriting during system restarts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is backed up to non-volatile storage during system failure, then data persistence is improved, but data can be overwritten during subsequent failures or recovery processes
Solution Approach 1:
The system performs preliminary actions by setting up protected backup locations and establishing encryption schemes before system failures occur. The memory backup controller is pre-configured to identify specific backup locations in non-volatile storage and apply encryption to protect data from being overwritten during recovery processes.
Solution Approach 2:
The patent introduces an intermediary protection mechanism through encryption. encrypted data stored in non-volatile storage acts as a protected intermediary that prevents unauthorized or accidental overwriting during system recovery. The encryption layer mediates between the vulnerable system memory and the storage medium, ensuring data integrity.
2Reliability
If data backup is continuously enabled in system memory, then data availability is improved, but system performance and memory management deteriorate
Solution Approach 1:
The patent segments the backup process by selectively enabling data backup only for specific application data objects that require persistence, rather than continuously backing up all system memory. This segmentation allows the system to maintain high performance while ensuring availability for critical data through targeted backup operations.
Solution Approach 2:
The system applies partial action by enabling backup only when and where needed - specifically for application data objects marked for persistence during system failures. This partial backup approach maintains system performance by avoiding unnecessary backup operations while still ensuring data availability for critical information.
3Reliability
If selective backup is implemented for application data objects, then data integrity is improved, but system complexity increases
Solution Approach 1:
The memory backup controller performs self-service by automatically identifying application data objects that require backup and managing the backup process without requiring complex external coordination. The controller independently determines which data to protect and executes backup operations, reducing overall system complexity while maintaining data integrity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Application program data stored in system memory may be selectively persisted. An indication may be provided to an application program that an application data object or a range of application data stored in system memory may be treated as persistent. Data backup may be enabled for the application data object or range of application data in the event of a system failure, copying the application data object or range of application data from system memory to non-volatile data storage. Upon recovery from a system failure, further data backup for the application data object or the range of application data may be disabled. In some embodiments, at least some of the application data object or range of application data may be recovered for the application program to access. Data backup for the application data object or the range of application data may also be re-enabled.