Validating Raw Device Mapping Files for Virtual Machine Disaster Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing Raw Device Mapping (RDM) during disaster recovery in virtualized computing environments poses challenges, particularly with issues like data corruption due to differing World Wide Number Identifiers (WWN IDs) and non-replicated mapping files, which existing technologies fail to address effectively.
Innovation Solution
The method involves assigning RDM file operations based on the validity of the RDM file, creating or replacing it if invalid, and handling shared RDMs and hypervisor-based replication scenarios to ensure correct configuration and replication of RDM files across sites.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If RDM file is not validated during disaster recovery, then the disaster recovery process is simpler and faster, but data corruption occurs due to invalid RDM files with mismatched WWN IDs
Solution Approach 1:
The patent applies preliminary action by validating the RDM file before completing the disaster recovery process. Specifically, the system checks whether the RDM file exists and whether the WWN ID in the RDM file matches the target storage device's WWN ID before allowing the virtual machine to access the storage. This prevents data corruption while maintaining a relatively simple recovery workflow.
2Reliability
If RDM file replication is not checked, then the replication process is faster, but the RDM file may be missing or invalid at the target site
Solution Approach 1:
The patent implements feedback by checking the validity and availability of the RDM file at the target site after replication. The system retrieves the RDM file from the target site, validates its existence, and verifies the WWN ID match. This feedback mechanism ensures RDM file availability while keeping the validation process efficient and integrated into the existing replication workflow.
3Measurement precision
If WWN ID verification is not performed, then the disaster recovery process is simpler, but storage device identification becomes unreliable leading to data corruption
Solution Approach 1:
The patent replaces complex mechanical or manual verification processes with an automated software-based WWN ID comparison mechanism. The system automatically extracts the WWN ID from the RDM file and compares it with the target storage device's WWN ID using software routines, eliminating the need for manual intervention while ensuring accurate storage device identification.
4Ease of operation
If RDM file operations are not managed during failback, then the failback process is simpler, but RDM configuration errors occur preventing proper virtual machine operation
Solution Approach 1:
The patent implements self-service by enabling the system to automatically manage RDM file operations during failback without requiring manual intervention. The system automatically creates, replaces, or validates RDM files based on the replication status and WWN ID matching, ensuring correct RDM configuration while keeping the failback operation simple for users.
Data Source
AI summary
Disclosed herein are methods, systems, and processes for managing raw device mapping during disaster recovery. A raw device mapping (RDM) file operation is assigned to a virtual device associated with a virtual machine that is replicated from a premise site. A determination is made that a RDM file associated with the virtual device is invalid or is not replicated after the virtual machine is replicated to a target site. Based on the determination that the RDM file is invalid or is not replicated, the virtual device is removed from the virtual machine and the assigned RDM file operation is performed.