VM Migration Preserving Hypervisor Format
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity of managing and migrating virtual machines (VMs) from on-premises environments to service provider networks, requiring conversion to different hypervisor formats and tools, increases operational burdens and costs, and limits scalability and resiliency.
Innovation Solution
A method and system for migrating VMs to a service provider network that allows users to maintain their existing hypervisor type, using 'bare metal' servers and backup proxies to replicate and configure VMs without conversion, enabling seamless integration and management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If VMs are migrated to service provider networks using traditional methods, then VMs can be hosted on service provider infrastructure, but VMs must be converted to different hypervisor formats increasing operational complexity and costs
Solution Approach 1:
The patent creates a copy of the source VM that preserves the original hypervisor format. The backup proxy captures the VM image and configuration data, then provisions a new VM at the service provider network using the same hypervisor type (e.g., VMware, Hyper-V, KVM). This copying approach eliminates the need for format conversion while maintaining full VM functionality and compatibility with existing management tools.
Solution Approach 2:
The backup proxy acts as an intermediary between the source VM and the service provider infrastructure. It captures VM data, determines the hypervisor type, and coordinates with the service provider network to provision the destination VM with matching hypervisor configuration. This intermediary enables seamless migration without requiring direct conversion between different hypervisor formats.
2Adaptability or versatility
If VMs are converted to different hypervisor formats for migration, then VMs can run on service provider infrastructure, but existing management tools and processes cannot be used increasing operational burden
Solution Approach 1:
By copying the VM with its original hypervisor format intact, the patent ensures that the destination VM remains compatible with the same management tools and processes used at the source. Users can continue to manage their VMs using familiar tools without needing to learn new provider-specific management interfaces, thereby maintaining ease of operation while achieving infrastructure migration.
Solution Approach 2:
The service provider network is configured to support multiple hypervisor types simultaneously. This universal approach allows the provider infrastructure to host VMs from different hypervisor platforms (VMware, Hyper-V, KVM, etc.) without requiring conversion, enabling users to maintain their preferred management tools while benefiting from service provider infrastructure resources.
3Adaptability or versatility
If VMs are converted between hypervisor formats, then migration to service provider networks is possible, but migration costs and operational burdens increase
Solution Approach 1:
The patent implements a copy-based migration approach where the VM image is captured and replicated to the service provider network while preserving the original hypervisor format. This eliminates conversion costs and reduces operational burden, as no format translation or reconfiguration is needed. The process involves straightforward data transfer and provisioning, significantly lowering migration expenses compared to traditional conversion methods.
4Ease of operation
If VMs are migrated without hypervisor conversion, then existing management tools can be maintained, but service provider networks must support multiple hypervisor types
Solution Approach 1:
The service provider network is designed with universal support for multiple hypervisor types. The infrastructure can simultaneously host VMs running different hypervisors (VMware, Hyper-V, KVM, Xen) without requiring conversion. This multi-functional capability allows the provider to accommodate diverse customer requirements while maintaining simplicity in the migration process and enabling customers to retain their existing management tools and workflows.
Data Source
AI summary
Techniques for migrating servers from customer networks into service provider networks are described. A backup proxy can be deployed in a customer's network and associated with one or more servers in the customer's network and with a server migration service of a service provider network. A customer can identify a server in the customer's network to migrate and the server migration service coordinates the migration with the backup proxy. The backup proxy can be instructed to obtain replication data for the server, obtain configuration data associated with the server, and upload the replication data and configuration data to the service provider network. The service provider network uses the replication data and configuration data to create a migrated copy of the server at the service provider network.