Logical Volume Record Management for Application Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In data storage systems, the movement of logical volumes from one physical device to another can lead to data loss during recovery processes, as existing systems lack the necessary history to accurately translate logical identifiers to the correct physical descriptors, resulting in the recovery of the wrong data set.
Innovation Solution
A method for managing data storage volume records that captures pairings of logical and physical volume identifiers, allowing for the detection of volume movements and the creation of updated records, ensuring accurate recovery by maintaining a history of physical storage configurations and updating inventory accordingly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If logical volumes are moved from one physical device to another for storage optimization, then storage efficiency and flexibility are improved, but data loss risk during recovery increases due to inability to track volume movements
Solution Approach 1:
The system performs preliminary tracking of volume movements by capturing configuration changes before they affect recovery operations. Storage configuration records are maintained and updated in advance to document the history of logical volume to physical device mappings, ensuring that when recovery is needed, the correct physical devices can be identified without data loss.
2Productivity
If storage configuration changes are frequent to optimize performance, then system adaptability is improved, but recovery accuracy deteriorates due to lack of historical configuration data
Solution Approach 1:
The system implements feedback mechanisms by continuously monitoring storage configuration changes and updating records accordingly. When volume movements or configuration changes occur, the system captures this information and maintains historical records that enable accurate recovery operations, thus preserving recovery precision despite frequent storage operations.
3Speed
If a simple backup system is used for quick backups, then backup speed is improved, but the ability to perform application-level recovery deteriorates due to lack of volume movement tracking
Solution Approach 1:
The system segments the backup and recovery operations into distinct functional components: a backup subsystem that maintains quick image copies of storage devices, and a recovery subsystem that uses stored configuration records to identify and locate volumes. This segmentation allows the backup process to remain fast while the recovery process benefits from detailed tracking information, enabling application-level recovery without sacrificing backup speed.
Data Source
AI summary
Provided are a computer program product, system and method for data storage volume record management for application-level recovery in accordance with the present description. In one embodiment, logical volume movement is addressed when performing enterprise application recovery. In one embodiment, a host-based recovery product in accordance with the present description, can detect logical volume movement from one physical device to another and proactively prevent application level recovery that potentially may result in data loss. In one embodiment, a time-based capturing of pairings of logical and physical volume identifiers or descriptors within storage configuration records and sub-records are used to surgically recover volumes of an application from enterprise level protection copy of physical media. This history of pairings facilitates many types of logical volume to physical media remapping, such as the regular migration of data to replacement storage controllers which can occur at various times.