Virtual Machine Image Replication via Block Indexing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for replicating virtual machine images across wide area networks face challenges such as network latency, high costs, and difficulty in identifying suitable remote sites, especially when dealing with large data sizes and multiple users, leading to lag and inefficiencies in data replication.
Innovation Solution
A system and method that automatically selects primary and secondary remote sites for storing virtual machine images, monitors updates, partitions image components, indexes stale and active components, compares differences, and transmits only new active components to secondary sites for replication, using techniques like de-duplication and write coalescing to reduce bandwidth usage and storage costs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If virtual machine image is stored across wide area networks from one location to another, then data redundancy and disaster recovery capabilities are improved, but network latency and data transfer time increase
Solution Approach 1:
The virtual machine image is divided into multiple components or blocks, allowing selective replication of only changed portions rather than the entire image. This segmentation enables efficient incremental updates across wide area networks, reducing data transfer time while maintaining multiple replicas for disaster recovery.
Solution Approach 2:
The system extracts and identifies only the specific changed components or blocks of the virtual machine image that need to be replicated. By taking out only the necessary changes rather than replicating the entire image, the system reduces network transfer time and bandwidth consumption while still achieving reliable disaster recovery through distributed replication.
2Reliability
If entire virtual machine image is replicated to secondary sites, then data redundancy is improved, but network bandwidth usage and storage costs increase
Solution Approach 1:
The system performs partial replication by transmitting only the changed components or blocks of the virtual machine image to secondary sites, rather than replicating the entire image. This partial action approach maintains data redundancy for disaster recovery while significantly reducing network bandwidth consumption and storage costs at replica locations.
Solution Approach 2:
The replication approach changes from copying entire images to transmitting only differential changes. By changing the parameter of what is being replicated (from complete image to incremental changes), the system achieves the same reliability benefit with reduced bandwidth usage and storage requirements.
3Stability of the object's composition
If virtual machine image components are monitored and updated across multiple sites, then data synchronization is improved, but system complexity and processing overhead increase
Solution Approach 1:
The system performs preliminary indexing and categorization of virtual machine image components into active and inactive sets before replication. This preliminary action establishes an organized structure that simplifies subsequent monitoring and update operations, reducing the complexity of maintaining data synchronization across multiple sites while improving synchronization efficiency.
Data Source
AI summary
Systems and methods are disclosed herein to automatically replicate virtual machine image (VM) files on secondary VM computing devices, from a primary VM computing device. The secondary VM computing devices are automatically selected by constantly reviewing the operating parameter values (e.g., cost of resources, power consumption, etc.) of a number of secondary VM computing devices available of storing VM image replicas. The replica of the primary VM image is stored in the secondary VM computing devices in geographically disparate cloud locations. The primary VM image is automatically broken into constituent data blocks stored in an active index, which is compared against a stale index of data blocks. When an update is detected in the primary VM image, the comparison of indices will indicate that there is new data. Only the new data is used to update the secondary VM images, thereby reducing network traffic and latency issues.