Capability VMware Hyper-V

Transcription

1

2

3

4 Capability VMware Hyper-V Host File System Management Virtual Disk Image Format Integration Tools / Drivers Connect LUN directly to VM from SAN VMFS (Virtual Machine File System) VMware allows you to extend (not recommended) Management via vsphere client, optional PowerCLI, vcenter, vrealize VMDK - VMware Virtual Disk Image VMware tools Drivers & tools installed in VM to improving performance / integration Raw Device Mapping Present raw LUNs on your physical storage to virtual machines directly NTFS/ ReFS Native Windows file systems can easily extend and use Cluster Shared Volumes (CSV) for HA support with performance and scalability Management via Hyper-V Manager (feature of Windows), integrated PowerShell Cmdlets, System Center, Windows Azure Pack (free) VHD/VHDX - Hyper-V Virtual Disk Image Integration services - Drivers & tools installed in VM to improving performance / integration Pass Through Disk Present raw LUNs on you physical storage to virtual machines directly Clustering vsphere HA - High availability (not-free) Failover Clustering - High availability Migration of Running VMs vsphere vmotion - (not-free) Hyper-V Live Migration Unlimited simultaneous live migrations

5

6

7

8 Microsoft Virtual Machine Converter Free standalone tool for conversion of physical & virtual servers MVMC 3.0 (Actually 3.1) Standalone tool to convert and migrate either physical servers or VMware-based virtual machines & disks to Hyper-V and Microsoft Azure. Benefits Deployed with minimal dependencies. Native support for Windows PowerShell for powerful automation capabilities Wizard-driven GUI for ease of use. Simple to download, install and use. Fully supported by Microsoft. Supports the conversion of the latest Guest OS s, along with conversion from vsphere hosts, to Hyper-V hosts.

9 Microsoft Virtual Machine Converter Physical Conversion: Supported Source & Destination Hosts Physical OS WS2008 / R2 WS2012 / R2 Windows Vista Windows 7 / 8 Microsoft Hosts (with Hyper-V enabled) WS2008 R2 SP1 (VHD) WS2012 (VHD) WS2012 R2 (VHD)

10 Microsoft Virtual Machine Converter Converting a Physical OS: The Process 4. Data copied to MVMC conversion host Hyper-V 4. Validate/fix-up, create VM & attach VHD 3. MVMC triggers Volume Shadow Snapshot of volumes Windowsbased OS 1. Connect to source OS, install agent & run system scan. 2. Select volumes, Configure VM settings & choose target Hyper-V host

11 Microsoft Virtual Machine Converter Virtual Machine Conversion: Supported Source & Destination Hosts VMware Source vcenter 4.1 vcenter 5.1 vcenter 5.5 ESX/ESXi 4.1 ESXi 5.1 ESXi 5.5 Microsoft Azure Microsoft Azure VHD Only Microsoft Hosts (with Hyper-V enabled) WS2008 R2 SP1 (VHD) WS2012 (VHD/VHDX) WS2012 R2 (VHD/VHDX)

12 Microsoft Virtual Machine Converter Supported Guest Operating Systems VMware VMs Hardware Version: 4, 7, 8, 9 & Microsoft Azure does not support x86 guests 2. Microsoft Azure does not support Windows Client guests. 3. Please refer to documentation for converting Linux guests additional pre-requisite steps may be required. Supported Guest OS s 1 Windows Server 2008 (x86/x64) Windows Server 2008 R2 (x64) Windows Server 2012 (x64) Windows Server 2012 R2 (x64) Windows Vista Enterprise (x86/x64) 2 Windows 7 Pro/Ent/Ultimate (x86/x64) 2 Windows 8 Pro/Ent (x86/x64) 2 Windows 8.1 Pro/Ent (x86/x64) 2 RHEL 5/6 (x86/x64) 3 Ubuntu 10.04/12.04 (x86/x64) 3 SLES 11 (x86/x64) 3 CentOS 5/6 (x86/x64) 3 Debian GNU/Linux 7 (x86/x64) 3 Oracle Linux 5/6 (x86/x64) 3

13 Microsoft Virtual Machine Converter Supported VMware Virtual Disk Configurations VMware Host & VM Supported Virtual Disk Types monolithicflat monolithicsparse twogbmaxextentflat twogbmaxextentsparse streamoptimized vmfs vmfssparse delta disk conversion

14 Microsoft Virtual Machine Converter Additional Requirements On the Destination Hyper-V Host User account must have write access to UNC path on Hyper-V host, used to copy the new virtual hard disks. Hyper-V host must have enough capacity available for new virtual hard disks. Windows Guests For online conversion, disable firewall, enable RDP & ensure VMware Tools are installed. VM should be domain-joined. Remote access through WMI is enabled on source VMware VM. Account being used for conversion is part of an AD domain, and has local administrator rights on VM.

15 Microsoft Virtual Machine Converter Additional Requirements On the Destination Hyper-V Host User account must have write access to UNC path on Hyper-V host, used to copy the new virtual hard disks. Hyper-V host must have enough capacity available for new virtual hard disks. Linux Guests Target VM requires VMware Tools to be installed. SSH required to remove VMware Tools ensure SSH is enabled and prepared to accept input on port 22. Root credentials currently required su/sudo not currently supported. Refer to documentation for more details.

16 Microsoft Virtual Machine Converter Additional Requirements when converting to Microsoft Azure VMware -> Microsoft Azure MVMC 3.0 performs virtual machine conversions to VHDs and uploads the disks to Microsoft Azure Blob Storage. Pre-Requisites Add a management certificate for Microsoft Azure that can be used for authentication with your subscription ID on Microsoft Azure. You have a storage account to upload and store the converted VHDs in Microsoft Azure. To convert and upload to Microsoft Azure, you have to install Windows PowerShell Runtime 3.0 on the machine on which MVMC 3.0 is running. See documentation for guidance.

17 Migration Automation Toolkit Free solution to automate & scale MVMC VM Conversions Migration Automation Toolkit for MVMC Series of PowerShell scripts that wrapper MVMC with automation to perform multiple virtual machine conversions simultaneously, not physical. Free to download, edit and customize Uses free SQL Server Express (or other SQL Server editions) to store information about the conversion process Supports multiple simultaneous conversions per MVMC machine Scales out across Helper Nodes multiple machines running MVMC and scripts all coordinated from central node More helper nodes = more conversions simultaneously. More info:

18 Migration Automation Toolkit Converting VMs with MVMC & MAT: The Process Helper Machines Physical/Virtual OS with MVMC Scale Hyper-V 1. Collect 2. Order vsphere Physical/Virtual OS with SQL Server MAT Control Machine User Ordered List

19

20

21

22 One migration solution for heterogeneous infrastructure Microsoft Azure Site Recovery Microsoft Azure Site Recovery Microsoft Azure Site Recovery Replication & Orchestrated Migration Replication & Orchestrated Migration NEW Replication & Orchestrated Migration NEW vcenter Primary Site Hyper-V Primary Site VMware Primary Site Physical & AWS Key features include: Automated VM protection and replication Remote health monitoring Near zero RPO No-impact migration testing Customizable recovery plans Minimal RTO few minutes to hours Orchestrated migration when needed Replicate to and recover in Azure Heterogeneous physical and virtual support

23 Comparing Other Migration Options High-level comparison for free & licensed conversion tools (excluding those already discussed) 5nine Software V2V Easy Converter Xtreme Consulting VM Migrator NetIQ PlateSpin Migrate Vision Solutions Double-Take Move / Cloud Migration Center Scale Small/Medium Medium/Large Large Large Source Hosts ESX/ESXi 4.1+ ESX/ESXi 4.1, 5.1, 5.5 Any Any Source Guests Windows & Linux Windows & Linux Windows & Linux Windows & Linux Target Hyper-V Hyper-V Hyper-V Any VMware Tools Not Removed Removed Removed Disabled Agent/Service No No Yes Yes Downtime Minutes/Hours Minutes/Hours Seconds/Minutes Seconds/Minutes Automation PowerShell (Full Ed.) SC Orchestrator Custom Scripts PowerShell/API/SC Costs Free or Buy Full Edition Buy IP or Incl. with consultancy Per Migration Cost Per Migration Cost Supportability 5nine Supported Xtreme Consulting Supported NetIQ Supported Vision Solutions Supported

24 Migrating to Microsoft: VMware to Hyper-V and Microsoft Azure Microsoft Virtualization for VMware Professionals Jump Start TechNet Radio: (Part 1) Hyper-V from a VMware Admin s Perspective

25