Application-Aware Backup Access via Namespace-Mounted VHDX
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data protection methods for application data in on-premises and cloud environments are inefficient, requiring kernel drivers or virtual file systems, which introduce dependencies and do not scale, and result in time-consuming and resource-intensive application data recovery and access.
Innovation Solution
The implementation of VHDX format for mounting virtual hard disk files natively across all operating systems, enabling application-aware item-level backups without kernel drivers or virtual file systems, allowing for efficient restoration and access by fetching only needed data while restricting access to specific application portions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If kernel drivers or virtual file systems are used for data protection, then application data can be protected, but system complexity increases and scalability is reduced
Solution Approach 1:
The patent introduces a backup volume mounted at a namespace path that acts as an intermediary between the application and the backup storage. This mediator handles all backup operations without requiring kernel drivers or virtual file systems, thus maintaining application data protection while reducing system complexity
Solution Approach 2:
The system creates a copy of the backup volume in the namespace that applications can access directly. This copy allows applications to read backup data without complex driver interactions, simplifying the system architecture while maintaining data protection capabilities
2Reliability
If kernel drivers or virtual file systems are used for data protection, then application data can be protected, but productivity decreases due to time-consuming recovery processes
Solution Approach 1:
The backup volume is pre-mounted in the namespace at the appropriate path before recovery is needed. Applications can directly access the backup data through this pre-configured namespace path, eliminating the time-consuming processes of traditional driver-based recovery methods
Solution Approach 2:
Applications can directly access their backup data through the namespace-mounted backup volume without requiring complex driver interactions or administrative procedures. This self-service capability significantly speeds up data recovery and improves overall productivity
3Reliability
If full VM backups are restored, then all application data is recovered, but access efficiency decreases due to unnecessary data loading
Solution Approach 1:
The backup volume in the namespace is segmented by application, allowing each application to access only its specific backup data through dedicated paths. This segmentation enables selective access to only the necessary data portions, reducing access time while maintaining complete recovery capability when needed
Data Source
AI summary
Techniques described herein relate to a method for performing data protection of file system data on a host. The method includes identifying a backup access event associated with a backup of a virtual machine (VM) stored on a backup storage, wherein the VM comprises a plurality of applications; obtaining backup metadata associated with the backup from a data protection manager; generating a placeholder file structure using the backup metadata and storing the placeholder file in a virtual hard disk file; loading the virtual hard disk file on a host associated with the VM; instantiating single application instances of the VM on the host; and performing application aware backup access services using the placeholder file structure, the backup metadata, and the single application instances of the VM, wherein the single application instances of the VM have limited access to placeholder file structure portions associated with the single application instances.