Simplifying Hyper-V Management for VMware Administrators
Download as PPTX, PDF0 likes121 views
5nine offers management, security, and migration solutions for Microsoft Azure and Hyper-V, helping over 1,000 customers in 100+ countries manage more than 5 million virtual machines. The platform simplifies hyper-v management for VMware administrators through automation, performance monitoring, and security features. Key services include hyper-v migration best practices, high availability setup, and virtual machine management tools to streamline the cloud deployment process.
Simplifying Hyper-V Management for VMware Administrators
- 1. www.5nine.com Simplifying Hyper-V Management for VMware Administrators
- 2. Trusted by Leading Enterprises, Analysts and Industry Experts Across the Globe 5nine provides the world’s leading management, security and migration solutions for Microsoft Azure and Hyper-V. Our powerful, integrated platform delivers scalable efficiency, automation and performance, empowering customers to accomplish every cloud initiative rapidly, securely and at exceptional value. Certified for Windows Server 2016, 2012 R2, 2012, Microsoft Hyper-V, Microsoft Azure 1,000+ Customers 100+ Countries 100K+ Cloud & Virtualization Administrators 5M+ Virtual Machines Managed & Protected
- 3. • VMware ESXi • Microsoft Hyper-V • Microsoft Azure • Amazon Web Services • RBAC & Workload Governance • Self-Provisioning Templates • Scheduled Backup & Recovery • Automated Lifecycle Management • Real-time Policy Configuration • Centralized Log Management • Threat Detection and Prevention • Automated Workload Protection • Real-time Alerts • Performance Monitoring • Capacity Planning • Dynamic Optimization Migrate Manag e Monitor Secure Our unified platform, ease of automation and network architecture increases performance, simplifies management, and protects against cyber attacks
- 4. Agenda Hyper-V Migration Best Practices • Requirements • Planning • Migration • Clean Up Hyper-V Deployment • High-Availability • Networking • Live Migration • Templates & Libraries Hyper-V Management • Production • Consumption • Monitoring • Maintenance Hyper-V Tools • SCVMM • SCOM • PowerShell • 5nine Manager
- 5. Hyper-V Migration Best Practices Reduce complexity with careful planning and the right tools
- 6. Automation Service Mgmt. Protection Monitoring Self-Service VM Management Hypervisor Orchestrator Service Manager Data Protection Manager Operations Manager App Controller Virtual Machine Manager Hyper-V vCenter Orchestrator vCloud Automation Center vSphere Data Protection vSphere Ops Mgmt. Suite vCloud Director vCenter Server vSphere Hypervisor
- 7. Build out the Hypervisor with the ISO • Check all VM requirements − CPU, RAM, hard disk, etc. − Maintaining a 20% buffer is recommended − Ensure both sides are on the same subnet − Ensure virtualization is turned on within the system BIOS Hardware component Minimum Recommended Processor Pentium 4, 2 gigahertz (GHz) (x64) Dual-processor, dual-core, 2.8 GHz (x64) or greater RAM 4 gigabytes (GB) 4 GB Hard disk space, without a local VMM database 2 GB 40 GB Hard disk space, with a local, full version of Microsoft SQL Server 80 GB 150 GB Managing up to 150 hosts Requirements
- 8. Build out the Hypervisor with the ISO • Check all VM requirements − CPU, RAM, hard disk, etc. − Maintaining a 20% buffer is recommended − Ensure both sides are on the same subnet − Ensure virtualization is turned on within the system BIOS Processor Pentium 4, 2.8 GHz (x64) Dual-processor, dual-core, 3.6 GHz or greater (x64) RAM 4 GB 8 GB Hard disk space 10 GB 50 GB Processor Pentium 4, 2.8 GHz (x64) Dual-processor, dual-core, 3.6 GHz or greater (x64) Managing more than 150 hosts Requirements
- 9. Build out the Hypervisor with the ISO • Check all VM requirements − CPU, RAM, hard disk, etc. − Maintaining a 20% buffer is recommended − Ensure both sides are on the same subnet − Ensure virtualization is turned on within the system BIOS Determine if you will use a GUI or non- GUI interface • Evaluate expertise, resources and complexity for script-based conversions Requirements
- 10. Build out the Hypervisor with the ISO • Check all VM requirements − CPU, RAM, hard disk, etc. − Maintaining a 20% buffer is recommended − Ensure both sides are on the same subnet − Ensure virtualization is turned on within the system BIOS Determine if you will use a GUI or non- GUI interface • Evaluate expertise, resources and complexity for script-based conversions • Use GUI interface for speed & simplicity Requirements
- 11. Build out the Hypervisor with the ISO • Check all VM requirements − CPU, RAM, hard disk, etc. − Maintaining a 20% buffer is recommended − Ensure both sides are on the same subnet − Ensure virtualization is turned on within the system BIOS Determine if you will use a GUI or non- GUI interface • Evaluate expertise, resources and complexity for script-based conversions • Use GUI interface for speed & simplicity Management VM • SCVMM instance • SQL Server for storing all data related to managing VMs Requirements Management cluster SQL cluster VMM cluster Scale-Out File Server Cluster for the gateway Server Provider Foundation endpoint Compute cluster Tenant A virtual machine Tenant B virtual machine Tenant C virtual machine Windows Azure Pack Portal Scale-Out File Server cluster File Shares • VVM Library • SQL • VM VHD • Cluster witness Gateway cluster Virtual Machines Gateway Virtual machine cluster
- 12. Monitoring tool • SCOM instance • Track VM health and application health on top • Up & down monitoring of loads and data stores Requirements
- 13. Planning Important questions to ask • Will I be using existing hardware or new hardware? • How many VMs am I migrating • Do I know which VMs are part of which workloads? • How much downtime will my migration require? • What will have the least impact on production? Pre-migration cleanup • Remove all attached CM/floppies • Review all VMs for any unneeded hardware • Clean up the disks • Commit snapshots
- 14. Migration Option 1: Built-in SCVMM tools • Very limited, especially for complex workloads • Error prone • Meant for ideal VMs with ideal workloads
- 15. Migration Option 1: Built-in SCVMM tools • Very limited, especially for complex workloads • Error prone • Meant for ideal VMs with ideal workloads Option 2: 5nine V2V Easy Converter • Low requirements (Server 2008 & above) • Low margin for error • Can exclude things that may not be compatible
- 16. Clean Up Clean migration source (within VMware) • Remove anything that was not removed via API or other method • Ensure all VMs that were copied are disabled, shutdown, or killed
- 17. Clean Up Clean migration source (within VMware) • Remove anything that was not removed via API or other method • Ensure all VMs that were copied are disabled, shutdown, or killed Perform analysis on new VMs (within Hyper-V and SCOM) • Review overall processing resources, memory resources and storage resources − Are you oversubscribing or undersubscribing? • Review each application − Use SCOM with management pack to trend out each virtualization workload − SCVMM Tuning • Test instances
- 19. High Availability Install failover clusters • Required 3 or more hosts (4 is recommended) • May require device controllers or adapters − Serial Attached SCSI (SAS) − Fibre Channel over Ethernet (FcoE) − ISCSI
- 20. High Availability Install failover clusters • Required 3 or more hosts (4 is recommended) • May require device controllers or adapters − Serial Attached SCSI (SAS) − Fibre Channel over Ethernet (FcoE) − ISCSI Build out clustered instance of Hyper-V • As simple as going into each VM and right-clicking on “make highly-available” • This makes copies of the metadata on the hosts • Provides an automatic restart on the other host if you have a failure on the primary host
- 21. High Availability Cluster management tools • Option 1: Failover Cluster Manager − Complex, disaggregated, generally unstable
- 22. High Availability Cluster management tools • Option 1: Failover Cluster Manager − Complex, disaggregated, generally unstable • Option 2: Windows PowerShell − Requires deep scripting knowledge
- 23. High Availability Cluster management tools • Option 1: Failover Cluster Manager − Complex, disaggregated, generally unstable • Option 2: Windows PowerShell − Requires deep scripting knowledge • Option 3: 5nine Manager − Simple GUI
- 24. High Availability Hyper-V networking consists of 2 parts • Virtual switch − External virtual switch − Internal virtual switch − Private virtual switch • Virtual network adapters − Hyper-V specific network adapter (Gen 1 & Gen 2 VMs) − Legacy network adapter (Gen 1 VMs only)
- 25. High Availability Hyper-V networking consists of 2 parts • Virtual switch − External virtual switch − Internal virtual switch − Private virtual switch • Virtual network adapters − Hyper-V specific network adapter (Gen 1 & Gen 2 VMs) − Legacy network adapter (Gen 1 VMs only) Match all networking on both sides such as • Production network • VOIP phones • Management network
- 26. High Availability Hyper-V networking consists of 2 parts • Virtual switch − External virtual switch − Internal virtual switch − Private virtual switch • Virtual network adapters − Hyper-V specific network adapter (Gen 1 & Gen 2 VMs) − Legacy network adapter (Gen 1 VMs only) Match all networking on both sides such as • Production network • VOIP phones • Management network Make sure all VMs are in proper network Make sure you can successfully communicate, route, or not route between networks
- 27. Live Migration Build live migration network
- 28. Live Migration Build live migration network Testing live migration with Hyper-V • Move workloads on the fly − Ex: Patch or upgrade cycle or upgrade of hardware − Zero downtime while upgrades are in progress
- 29. Important questions to consider: Application lifecycle vs. VM lifecycle • Do you have any drag in your current environment? • Is there anything worth rebuilding instead of migrating? • Example: In Exchange, mailbox servers are easier to migrate while hub transport servers are easier to rebuild Templates and Libraries
- 30. Important questions to consider: Application lifecycle vs. VM lifecycle • Do you have any drag in your current environment? • Is there anything worth rebuilding instead of migrating? • Example: In Exchange, mailbox servers are easier to migrate while hub transport servers are easier to rebuild Average lifecycle for VMs is about 1 year • OS drag kicks in in about 6-8 months from unnecessary updates, applications • This is especially prevalent in a GUI environments Templates and Libraries
- 31. To reduce work associated with manually rebuilding VMs every year, use templates: • Templates − Convert VMs into templates for later use − Can attach files like VHD, VHDX, and ISOs to templates − Clone and reuse VMs from templates • Libraries − Secure store for VM templates Templates and Libraries
- 32. Hyper-V Management & Best Practices
- 33. Environment Considerations • Standalone - admins using SCVMM − Light permissions • Tenant-based − Self-service − Allocate admins certain amount of CPU, memory and storage − Get what they get and carve it up as they will • Disparate tools − Hyper-V Manager − SCVMM − SCOM Production, Consumption, and Monitoring
- 34. Environment Considerations • Standalone - admins using SCVMM − Light permissions • Tenant-based − Self-service − Allocate admins certain amount of CPU, memory and storage − Get what they get and carve it up as they will • Disparate tools − Hyper-V Manager − SCVMM − SCOM Production, Consumption, and Monitoring
- 35. 5nine Manager Datacenter MISSION CONTROL FOR YOUR MICROSOFT CLOUD
- 36. Advanced Virtualization Security Built-In Backup & Recovery 5nine Manager Datacenter WHAT SETS 5NINE APART FROM SCVMM Simple Deployment & Configuration Unified Cloud Management Total Cost of Ownership Replication Between Sites
- 37. 5nine Manager Datacenter 2.0 Demonstration
- 38. THANK YOU! Questions? Contact us: sales@5nine.com Learn more: https://www.5nine.com/5nine- manager-datacenter/