Pseudo-Volume Driver for Instant Application Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data recovery methods result in prolonged application downtime due to the time-consuming process of restoring large datasets from backups, especially for applications managing petabytes of data, leading to unacceptable downtime and productivity losses.
Innovation Solution
The implementation of an enhanced data agent and pseudo-storage-device driver allows the application to operate concurrently with the restore process by using a pseudo-volume for staging write operations and read responses, enabling 'instant application recovery' with minimal downtime by updating primary data once the restore is complete.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a full restore operation is performed from backup copy to production media, then data integrity is ensured, but application downtime increases significantly
Solution Approach 1:
The patent performs a preliminary restore operation to a pseudo-volume before the application actually needs the data. The pseudo-volume is prepared in advance with the restore destination mounted, and the restore process begins before the application downtime is officially recorded. This preliminary action allows the data to be restored while the application is still running or during minimal downtime periods.
Solution Approach 2:
The patent introduces a pseudo-volume as an intermediary storage layer between the backup copy and the production file system. This pseudo-volume acts as a mediator that receives restored data and allows the application to access it without directly modifying the production file system during the restore process. The pseudo-volume driver intercepts and manages all I/O operations, enabling seamless data transition.
2Productivity
If restore operation is performed on production file system directly, then data is restored, but application must be deactivated during the process
Solution Approach 1:
The patent segments the restore process into distinct phases: (1) mounting the restore destination to a pseudo-volume, (2) performing the restore operation to the pseudo-volume, (3) updating the production file system from the pseudo-volume, and (4) unmounting the pseudo-volume. This segmentation allows the application to remain active during phases 1-2 while only requiring brief deactivation during phase 3.
Solution Approach 2:
The pseudo-volume driver serves as an intermediary layer that manages all file system operations during the restore process. It intercepts I/O requests from the application, redirects them to the appropriate storage location (backup or restored data), and manages the transition between different data sources without requiring application modification or deactivation.
3Reliability
If traditional backup and restore methods are used, then data protection is achieved, but downtime of hours or days occurs for large datasets
Solution Approach 1:
The patent enables continuous useful action by allowing the application to remain operational throughout most of the restore process. The pseudo-volume maintains I/O connectivity, permitting the application to read and write data continuously while the restore operation progresses in the background. This continuity eliminates the traditional stop-start nature of restore operations.
Solution Approach 2:
The restore operation is initiated as a preliminary action before the application requires the restored data. The pseudo-volume is mounted and the restore process begins in advance, allowing data to be restored during periods when the application can tolerate minimal or no downtime. This preliminary timing strategy significantly reduces the impact on application availability.
Data Source
AI summary
The disclosed systems and methods enable an application to start operating and servicing users soon after and during the course of its backup data being restored, no matter how long the restore may take. This is referred to as “instant application recovery” in view of the fact that the application may be put back in service soon after the restore operation begins. Any primary data generated by the application during “instant application recovery” is not only retained, but is efficiently updated into restored data. An enhanced data agent and an associated pseudo-storage-device driver, which execute on the same client computing device as the application, enable the application to operate substantially concurrently with a full restore of backed up data. According to the illustrative embodiment, the pseudo-storage-device driver presents a pseudo-volume to the file system associated with the application, such that the pseudo-volume may be used as a store for primary data during the period of “instant application recovery.”