Memory-Mapped File Crash Consistency via Segmentation Fault Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data protection systems require system shutdown during backups, limit recovery points in time, and have lengthy recovery processes, failing to provide continuous data protection with minimal downtime and precise recovery capabilities.
Innovation Solution
A system and method utilizing memory-mapped files, non-volatile storage, and segmentation fault handling to create crash-consistent checkpoints, allowing writes to be managed through undo and redo logs, enabling transparent data management and recovery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional tape backup drives are used for data protection, then data can be stored on periodic basis, but system shutdown is required during backup and recovery time is limited
Solution Approach 1:
The patent implements continuous data protection by maintaining a memory-mapped file that is continuously updated with transaction logs. The system uses a segmentation fault handler to intercept write operations, ensuring continuous data protection without requiring system shutdown. The memory-mapped file persists continuously in volatile memory, enabling recovery at any point in time.
Solution Approach 2:
The patent introduces a memory-mapped file as an intermediary between the application and the storage system. This intermediary layer captures all write operations through segmentation fault handling, creating a continuous log of changes. The memory-mapped file acts as a mediator that enables recovery without direct interaction with the storage medium during normal operation.
2Reliability
If conventional backup systems are used, then data can be backed up periodically, but recovery points are limited and recovery process is lengthy
Solution Approach 1:
The patent performs preliminary action by continuously logging all write operations to the memory-mapped file before they are committed to storage. The segmentation fault handler intercepts writes and records them in advance, creating a complete transaction log that enables precise recovery at any point in time. This preliminary logging ensures no data is lost and recovery can occur at any timestamp.
Solution Approach 2:
The patent creates a copy of the data structure in the memory-mapped file that mirrors the actual data. This copy is continuously updated through segmentation fault handling, creating a parallel representation of data at any point in time. The memory-mapped file serves as a copy that can be recovered without affecting the original data, enabling precise recovery points.
3Reliability
If memory-mapped files are used with segmentation fault handling, then continuous data protection is enabled, but device complexity increases
Solution Approach 1:
The patent implements self-service by using the segmentation fault handler to automatically intercept and log write operations. The memory-mapped file self-updates with transaction information without requiring external intervention. The system serves itself by capturing its own state changes through the segmentation fault mechanism, reducing the need for complex external monitoring and management systems.
Data Source
AI summary
A system, method, and computer program product for establishing a memory-mapped file, enabling the memory-mapped file data to be paged to a non-volatile storage medium, marking a portion of the memory-mapped file as protected, wherein a write to the memory mapped file throws a segmentation fault; receiving a write at the memory mapped file, throwing a segmentation fault; and handling the segmentation fault in a segmentation handler, where the handling comprises reading the information in the memory mapped file facility into the undo log, and writing the write IO to the storage medium.