dcsimg

Tips for Migrating from VMware to Hyper-V

  • Tips for Migrating from VMware to Hyper-V-

    VMware to Hyper-V Migration Basics

    When planning a migration to Hyper-V, there are a number of things to consider, but the most important are an organization's budget and tolerance for downtime. IT managers commonly evaluate migration tools based on budget and application uptime requirements:

    ·         Low or no cost versus higher costs

    ·         Incredibly short or no downtime versus longer application outage

    (It should be noted that many applications can be moved without using tools since they have their own replication functionality.)

    Because Hyper-V is a Windows offering, migrating VMware to Hyper-V doesn't usually require a steep learning curve. The vast majority of IT staffers are fully conversant with Windows. Hyper-V VMs are similarly defined to VMware's VMs — where the VM "definition" is with hardware resources (vCPUs, RAM, NICs, SCSI and IDE controllers, attached drives, etc.) and the drives are typically encapsulated in a disk file, similar to a VMDK. The table below illustrates the common definitions and processes of each hypervisor.

    GridstoreCaption2

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9

Tips for Migrating from VMware to Hyper-V

  • 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
  • Tips for Migrating from VMware to Hyper-V-2

    VMware to Hyper-V Migration Basics

    When planning a migration to Hyper-V, there are a number of things to consider, but the most important are an organization's budget and tolerance for downtime. IT managers commonly evaluate migration tools based on budget and application uptime requirements:

    ·         Low or no cost versus higher costs

    ·         Incredibly short or no downtime versus longer application outage

    (It should be noted that many applications can be moved without using tools since they have their own replication functionality.)

    Because Hyper-V is a Windows offering, migrating VMware to Hyper-V doesn't usually require a steep learning curve. The vast majority of IT staffers are fully conversant with Windows. Hyper-V VMs are similarly defined to VMware's VMs — where the VM "definition" is with hardware resources (vCPUs, RAM, NICs, SCSI and IDE controllers, attached drives, etc.) and the drives are typically encapsulated in a disk file, similar to a VMDK. The table below illustrates the common definitions and processes of each hypervisor.

    GridstoreCaption2

Businesses around the world have embraced virtualization because it can deliver high performance and reduce both capital and operational expenditures, while freeing up valuable IT resources. The rise of VMware is testament to how server virtualization has helped and continues to help many data centers develop cost-effective IT strategies. However, IT managers today have more options when it comes to choosing the right virtualization solution. In the 2015 Gartner "Magic Quadrant for x86 Server Virtualization," seven companies are listed. For CIOs swayed by this data, the two virtually unchallenged leaders are VMware and Microsoft, causing many to consider migrating their VMware solution to Microsoft Hyper-V due to its reduced cost, feature set and, probably most important, its tight integration with Azure for cloud enablement.

Clearly, no amount of cost savings, advanced features or cloud enablement can make up for headaches caused by workload migration. According to Gridstore, with the proper planning and tools, migrating can be essentially risk-free with zero downtime to workloads. In fact, there are myriad migration tools and approaches that can fit any IT budget.

Common migration tools capabilities include:

  • Online data sync/migration
  • Offline disk conversion from VMDK/RAW to VHDX/Pass-through
  • Automated VMware Tool removal
  • Automated VM provisioning (not all tools create VMs – some just migrate data)
  • Disk controller fixup
  • Hyper-V Integration Services (IS) injection
  • Network information migration (ex. Static IP, MAC address, VLAN, other)