Application Data Backup and Recovery in Virtual Machines via LUN Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing backup and recovery systems for applications executing in virtual machines often require backing up the entire virtual machine, which is inefficient and unnecessary, as they fail to address the specific needs of individual applications, and do not account for changes in underlying physical storage topology due to virtual addressing.
Innovation Solution
A system and method for backing up and recovering application data in a virtual machine by discovering the underlying physical storage topology using virtual to physical mappings, allowing for separate backup and recovery of application data independent of the virtual machine, using techniques like Raw Device Mapping (RDM) and Virtual Machine Disk (VMDK), and enabling recovery to a previous state without requiring the backup of virtual machine metadata.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the entire virtual machine is backed up, then all data including application data is protected, but the backup size and time increase significantly
Solution Approach 1:
The patent extracts only the application data portion from the virtual machine disk image for backup, rather than backing up the entire virtual machine. This is achieved by identifying the virtual disk device associated with the application and selectively backing up only that portion, thereby reducing backup time and storage requirements while maintaining protection for the critical application data.
Solution Approach 2:
The patent segments the virtual machine disk into different portions corresponding to different virtual disk devices, each associated with specific applications. This segmentation allows the backup system to process and protect only the relevant portions containing application data, separating them from unnecessary system metadata and other virtual machine components.
2Reliability
If the entire virtual machine is backed up, then all data is protected, but the backup cost and storage requirements increase
Solution Approach 1:
The patent extracts only the application data portion from the virtual machine disk image for backup, rather than backing up the entire virtual machine. This is achieved by identifying the virtual disk device associated with the application and selectively backing up only that portion, thereby reducing backup time and storage requirements while maintaining protection for the critical application data.
3Reliability
If virtual machine metadata is included in backup, then complete recovery is possible, but recovery complexity and time increase
Solution Approach 1:
The patent extracts only the application data portion from the virtual machine disk image for backup, rather than backing up the entire virtual machine. This is achieved by identifying the virtual disk device associated with the application and selectively backing up only that portion, thereby reducing backup time and storage requirements while maintaining protection for the critical application data.
4Adaptability or versatility
If physical storage topology is not discovered, then mapping changes are not tracked, but accurate application data location cannot be determined
Solution Approach 1:
The patent performs preliminary discovery of the physical storage topology by querying the hypervisor for physical to virtual address mappings before the backup process begins. This preliminary action establishes the current mapping relationships, allowing the system to accurately locate application data on physical storage devices even as the virtualization environment evolves and mappings change over time.
Data Source
AI summary
Backup of application data associated with an application executing in a virtual machine managed by a hypervisor is performed. Backup of the application data includes retrieving a Logical Unit Number (LUN) identification (ID) used by the application to store the application data in a storage volume. Backup of the application data also includes performing a virtual storage resolution for the LUN ID to determine whether the application data is stored in the storage volume identified by the LUN ID based on a first virtual mapping or a physical mapping. Backup also includes storing in metadata for the backup the LUN ID and whether the LUN ID is based on the first virtual mapping or the physical mapping. Backup includes creating a backup of the application data stored in the storage volume. Application data can subsequently be restored based on the application data that is backed up.


