File Level Restore with RP4VM Journal Inode Reconstruction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data protection systems require a lengthy process to restore a whole virtual machine (VM) to a specified point in time (PiT), involving user configuration and system recreation, which is inefficient for recovering from minor data disasters like file corruption or deletion.
Innovation Solution
A method to recreate individual files or directories corresponding to a specified PiT by using an inode event stream stored in a journal, reconstructing the file system inode structure, and rolling back data from a temporary file to the desired PiT, allowing for efficient restoration of specific files or systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If whole VM restoration is performed using PiT replication technology, then data recovery capability is improved, but restoration time and operational complexity increase significantly
Solution Approach 1:
The patent segments the VM restoration process into file-level operations. Instead of restoring the entire VM, the system identifies and restores only the specific corrupted or deleted files by parsing journal entries at the file level, extracting file metadata, and reconstructing individual files from journal data. This segmentation dramatically reduces restoration time while maintaining data recovery capability.
Solution Approach 2:
The patent extracts the essential file restoration functionality from the complex VM restoration process. By taking out only the necessary components (journal parsing, file metadata extraction, file reconstruction) and eliminating unnecessary VM-level operations, the system achieves rapid file-level recovery without the overhead of full VM recreation.
2Reliability
If whole VM restoration is performed using PiT replication technology, then data recovery capability is improved, but operational complexity and user configuration requirements increase
Solution Approach 1:
The patent implements self-service automation where the system automatically parses journal entries, identifies corrupted or deleted files, extracts file metadata, and reconstructs files without requiring user configuration. The system autonomously navigates the journal data structure, locates target files, and performs restoration, eliminating the need for users to configure complex VM restoration parameters.
Solution Approach 2:
The patent extracts and eliminates the complex VM configuration requirements from the restoration process. By focusing solely on file-level operations and removing the need for VM-level setup, the system simplifies user interaction to simple file recovery commands while maintaining robust data recovery capabilities.
3Reliability
If conventional data protection systems are used, then continuous data protection is achieved, but file-level restoration efficiency deteriorates
Solution Approach 1:
The patent segments the journal data structure into file-level units, enabling independent file restoration operations. By parsing journal entries to extract individual file metadata and separating file recovery from VM restoration, the system achieves high file-level restoration efficiency while maintaining continuous data protection through the underlying journaling mechanism.
Data Source
AI summary
A method, apparatus, and system for recreating a file that corresponds to a specified point in time (PiT) in a data storage system is disclosed. The particular PiT and the name of the file to be restored may be received from a user. A file system inode structure corresponding to the particular PiT may be recreated based on an inode event stream stored in a journal. One or more disk locations associated with the file to be restored may be determined based on the inode structure corresponding to the particular PiT. A temporary file may be constructed with data read from the one or more disk locations in a storage system of the backup site. Thereafter, the file to be restored may be obtained, which may comprise rolling back data of the temporary file to the particular PiT based on a data stream stored in the journal.