Virtual Machine Migration Data Integrity Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing virtual machine (VM) backup and migration systems lack effective data integrity checks during data transfer, which can result in data alteration or destruction, compromising the reliability and security of virtualized computing environments.

Innovation Solution

A management module is implemented to migrate VMs between computing devices, creating and comparing data signatures over time to detect any alterations, generating alerts for discrepancies and ensuring data integrity through hashing mechanisms during both transit and storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If VM migration and backup operations are performed without data integrity checks, then migration speed and system productivity are improved, but data reliability and security deteriorate due to potential data alteration or destruction

Engineering Contradiction:
Improvemigration speedVSAvoiddata integrity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system generates data signatures (hashes) of the VM data both before migration begins and after migration completes. These preliminary and final signatures are then compared to verify data integrity, ensuring that no data alteration occurred during the migration process while maintaining efficient transfer speeds

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where the post-migration data signature is compared against the pre-migration signature. If the signatures match, the migration is confirmed successful; if they differ, an alert is generated indicating potential data corruption or alteration, allowing for corrective action

Inventive Principle:
Principle #23Feedback

2Reliability

If data signatures are created and compared throughout the migration process, then data integrity and security are improved, but system complexity and computational overhead increase

Engineering Contradiction:
Improvedata integrityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system extracts only the essential integrity verification component - data signature generation and comparison - from the complex migration process. By focusing on this single critical function, the system achieves reliable data integrity verification without adding excessive complexity to the overall migration infrastructure

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system creates simplified copies of the data in the form of mathematical signatures (hashes) rather than duplicating the entire VM data set. These signature copies are much smaller and computationally efficient to generate and compare, reducing system complexity while maintaining integrity verification capability

Inventive Principle:
Principle #26Copying

3Measurement precision

If real-time signature comparison is implemented during migration, then detection precision of data alterations is improved, but migration time and processing duration increase

Engineering Contradiction:
Improvealteration detection accuracyVSAvoidmigration duration
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system uses cryptographic hash functions to create compact signature copies of the VM data. These signatures are exponentially smaller than the original data and can be generated and compared extremely quickly, providing high-precision alteration detection without significantly impacting migration duration

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The pre-migration signature is generated in advance before the actual data transfer begins. This preliminary computation allows the post-migration verification to be a simple, quick comparison operation rather than a time-consuming re-computation, minimizing the impact on migration timing

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10558484B2Systems and methods for securing virtual machines
Publication Date: 2020.02.11 THE BOEING CO
  • US10558484B2 patent drawing
  • US10558484B2 patent drawing
  • US10558484B2 patent drawing

AI summary

A system includes a first computing device comprising a virtual machine (VM), a second computing device, and a third computing device coupled to the first and second computing devices. The third computing device includes a management module configured to migrate the VM from the first computing device to the second computing device. The management module is also configured to create a first signature of data associated with the VM stored by the first computing device over a first period of time and create a second signature of data associated with the VM stored by the first computing device over a second period of time. The management module is further configured to compare the first signature and the second signature throughout the migration process to determine whether the data has been altered and generate an alert when a difference between the first signature and the second signature is detected.