VIEWS: 22 PAGES: 75 POSTED ON: 2/10/2012
DATACENTER MANAGEMENT USING HYPER-V AND SYSTEM CENTER September, 19 Kurt Roggen Technical Consultant Email: email@example.com Blog: http://tryCatch.be/blogs/roggenk Agenda • DataCenter Management: Today – Deployment – Management – Monitoring – Backup/Restore & Disaster Recovery • DataCenter Management: Tomorrow Dealing with Server Virtualisation Using Windows Deployment Services 1. DEPLOYMENT: HOST Windows Deployment Services Windows Deployment Client Windows Deployment Server Automating Windows Setup • Using answer files • Multiple files replaced by a single XML answer file (unattend.xml) • Simplifies customization process • Only one tool needed – Windows System Image Manager (WSIM) – Available in WAIK (Windows Automated Installation Kit) • All Configuration Passes addressed in a single location Multicast Enhancements • Multiple Stream Transfer – Multiple bands to broadcast images to clients – Optimized rates per Fast client connection • Client Auto Removal – Slower clients can be dropped to unicast Medium or entirely • Boot Image Multicast – Windows PE boot Slow images can use multicast (clients with EFI) Dynamic Driver Provisioning Images Drivers Driver targeting to match drivers to hardware Reduces image size and Client centralizes deployment driver management Using Hyper-V R2 SP1 1. DEPLOYMENT: HYPER-V Hyper-V Capabilities • 32-bit (x86) & 64-bit (x64) VMs • Large memory support (64 GB) per VM – Dynamic Memory allocation • SMP VMs (up to 4 cores) • Integrated cluster support for HA & Live Migration • Live backup using Volume Shadow Service (VSS) integration • Virtual Machine snapshots/checkpoints • New hardware sharing architecture (VSP/VSC/VMBus) – Disk, networking, input, video • Networking: VLANs and NLB • Support for Full or Server Core installations Provided by: Hyper-V Architecture OS Hyper-V MS / XenSource / Parent Partition Child Partitions Novell ISV/IHV/OEM Virtualization Stack WMI Provider VM Applications Applications Applications Worker VM Process Service User Mode Windows Server 2008 Windows Server 2003, 2008 Non hypervisor Xen-enabled Linux Kernel Linux aware OS Windows Windows VSCs Kernel VSP Kernel VSC Hypercall Adapter VMBus VMBus Emulation VMBus Kernel Mode Windows Hypervisor “Designed for Windows” Server Hardware 12 Hyper-V Technologies • Hyper-V technology is available in two forms: – Microsoft Windows Server 2008 (R2) with Hyper-V • Full Windows Server product with Hyper-V Role • Available in Server Core and Full Installation • Supports up to 1 TB of memory (Enterprise/Datacenter) – Microsoft Hyper-V Server 2008 (R2) • Standalone server virtualization product • Micro-kernelized hypervisor with no third party devices • Server Core installation • Supports up to 32 GB of memory • Free, and no CALs required (Guest OS instances must be licensed, and do need CALs) Comparing Hyper-V Server and WS 2008 Hyper-V Hyper-V Server WS 2008 R2 WS 2008 R2 Capabilities 2008 R2 Standard Enterprise/Datacenter Processor Architecture - 64 bit Yes Yes Yes Hypervisor-based Yes Yes Yes Product Type Standalone product Operating System Operating System Number of Sockets Up to 4 Up to 4 Up to 8 = EE | Up to 64 = DC Memory Up to 32 GB Up to 32 GB Up to 1TB memory VM Migration None None Quick Migration (EE & DC) Command Line & Command Line, remote management, and Administrative UI remote management GUI (Hyper-V Manager MMC) Management Existing management tools Manageable by System Center Yes Yes Yes Virtual Machine Manager Virtualization Rights for Enterprise Edition = 4 VM 0 1 VM Windows Server 2008 guests DC = Unlimited VM (per proc) Number of running VM Guests Up to 384, or as many as physical resources allow Windows Server 2008 CALs Required No Yes Yes for Guest Server OS Direct Attach Storage (DAS): SATA, eSATA, PATA, SAS, SCSI, USB, Firewire Storage Storage Area Networks (SANs): iSCSI, Fiber Channel, SAS Network Attached Storage (NAS) Windows Server 2008 (R2), Windows Server 2003 SP2, Windows 2000 Server, Novell SUSE Guest OS support Linux Enterprise Server 10, RedHat Linux, CentOS, Windows Vista SP1 & Windows XP SP3/SP2 Windows Server 2008 R2 SP1 RemoteFX Dynamic Memory Virtual Memory (vRAM) - Static • Fully allocated at run-time • Up to 64 GB per VM • Can only adjust vRAM when VM is offline Virtual Memory (vRAM) - Dynamic • Only ‘Startup RAM’ allocated at run-time • Up to 64 GB per VM • Can only adjust vRAM when VM is offline Windows Server 2008 R2 SP1 feature Dynamic Memory - Advantages • Real time on demand memory sizing – Based on performance counters inside VM • Usable for both server and desktop workloads • Higher VM consolidation ratios per host Failover Clustering 1. DEPLOYMENT: HYPER-V CLUSTER Virtualization And High Availability Value of the physical server goes up Downtime is bad, but affects only Downtime is far worse because one workload multiple workloads are affected Hyper-V High Availibility: Quick/Live Migration & Failover Clustering • Provides solutions for both planned and unplanned downtime • Planned downtime – Quickly move virtualized workloads to service underlying hardware – More common than unplanned – Manual action! • Unplanned downtime – Automatic failover to other nodes (hardware or power failure) – Not as common and more difficult – Automatic – no manual action required Live Migration Planned Downtime Active server requires servicing Move virtualized workloads (3 + 1 Servers) to a standby server Ethernet VHDs Hyper-V Live Migration • Move a running VM from one host to another host with no downtime • Client is not aware of the migration • Maintain open TCP connections of the guest OS • Clients stay connected • Planned failover – Failover Clustering still recovers VM from a disk in an unplanned failover Cluster Shared Volumes Distributed-access to file system • All servers “see” the same storage Failover Clustering (HA) Unplanned Downtime Active server loses power Virtual machines automatically restart on (3 + 1 Servers) the next cluster node If there is not enough memory, the failover automatically moves to the Ethernet next node until done VHDs Using System Center Virtual Machine Manager 2008 R2 SP1 2. MANAGEMENT: HYPER-V HOST & VM “Virtualization without good management is more dangerous than not using virtualization in the first place.” – TOM BITTMAN, GARTNER VP AND ANALYST, 9 MAY, 2007 Virtualization Will Drive Major Change in IT Infrastructure and Operations in the Next Three Years, Tom Bittman, May 8, 2007 Virtual Machine Manager 2008 R2 A centralized, heterogeneous management solution for the virtual datacenter • Centralized virtual machine deployment and management for Hyper-V and VMware ESX/ESXi hypervisors • Intelligent placement of Virtual Machines • Comprehensive application and service-level monitoring with Operations Manager • Integrated Performance and Resource Optmization (PRO) • Fast and reliable P2V and V2V conversion • Increase Agility • Rapid VM provisioning with VM templates Virtual Machine Manager Topology Administrator Console Self Service User Windows PowerShell Perimeter Network (DMZ) Self Service Web Servers Library Servers Virtual Machine Hosts Administrator Console Virtual Virtual Server Machines VMware Cluster Context Sensitive Actions Hyper-V Cluster Filters Live Thumbnail VM Information Management Selection Library Server • Repository for VM building blocks – Templates – VHD’s – ISO’s – PowerShell Scipts – SysPrep Answer Files • Runs a VMM Agent • Use centralized or distributed Windows files servers as library servers – Move/copy/delete/modify files directly in the file system – SCVMM tracks changes and provides physical/logical view – SCVMM stamps objects to track objects and identify copies – Support for clustered library servers Delegation and Self Service • Administrators control access through User Roles which designate capabilities • Delegated Administrators – Manage a scoped environment • Self service user – Web user interface – Manage their own VMs – Quota to limit VMs – Scripting through PowerShell VMM and Powershell interaction PowerShell Cmdlet Job Progress Status Owner Affected objects Virtual Machine Templates • Consist of Hardware and Guest OS Profile • Consistent hardware and guest OS configuration across all VMs • Enables provisioning using Self Service Portal • Reduces provisioning time • Base for provisioning VMs VMware integration • Manages VMware using Windows Powershell and vCenter web service API • Requires no agent deployment on VMware ESX/ESXi or vCenter VMware Support • VMware vCenter Server – VMware vCenter Server 2.5 • VMware ESX Hosts – VMware ESX 3.5 – VMware ESX 3.0.2 – VMware ESX Server 3i • What about vSphere 4? – SUPPORTED (VI3 features only) – API Close enough to VI3 that we were able to complete our tests and it is supported Enterprise Topology Windows PowerShell Administrator Console Web-based Delegated Provisioning External UI Network (DMZ) Remote BRUSSELS Remote Library Library Server Server Virtual Machine Hosts MONS Scenario: Server Consolidation Physical Performance servers converted to data collected to Physical machines virtual machines identify retired Prioritized report of consolidation or repurposed consolidation candidates Intelligent Machine Performance data Virtual placement candidates ManagerVM VM of each agents collected fromon deployed to virtual optimal host hosts for intelligent Physical placement machine hosts Infrastructure Virtual Machine Hosts Scenario: Administrative Provisioning New VM created from configured Pre-configured template VM configuration template selected customized from for new VM template Intelligent placement Centralized Library of new VM data Performance on of VM Templates optimal host collected from VM hosts for intelligent placement Virtual Machine Hosts 40 Scenario: Delegated Provisioning Web- Based UI VM created Delegated UI for Updated webuser from delegated begins creating new adminstrator- provisioning virtual machine assigned template Centralized Library of VM Templates VM automatically placed on optimally designated host Virtual Machine Hosts Using System Center Operations Manager 2007 3. MONITORING: HOST & VM System Center OpsMgr 2007 R2 • Comprehensive health and performance monitoring of Hyper-V servers, VMs, VMM, and vSphere components – Hyper-V Management Pack – VMM 2008 R2 Management Pack – Partner Management Packs • Hyper-V Management Pack Component Monitoring – Hyper-V services (unresolved errors, alerts) – VM health (drive space for dynamically expanding VHD) – Virtual networks type and associated Hyper-V server • Hyper-V Management Pack Monitoring Views – Alert – Server Role – Virtual Machines – Virtual Network Monitoring • Discovery of Hosts, Virtual Machines and Virtual Machine Manager components • Performance and Health Monitoring, Reports, etc. • Application awareness • Performance and resource calibration and optimization HV Cluster VMs VM Hosts vNIC Host Groups DBs vHD VMM Library Server vSwitch OS VMM Server SCVMM 2008 integrates SCOM 2007 Administrator’s Self Service Web Console Portal Operator’s Web Windows Console Console PowerShell Windows® PowerShell Connector Virtual Machine Manager Operations Manager Server Server Management Interfaces Virtual Server VMM Library VMware VI3 Host Server Virtual Center Server VM VM Template VM VM VM VM ESX Host VM VM VM VM VM ISO VHD Script VM VM VM VM SAN Storage Performance And Resource Optimization (PRO) PRO – Out Of the Box • VMHost (Hyper-V and VMware) Performance – CPU and Memory • VMM 2008: Static (CPU: +90%, RAM: +75%) • VMM 2008 R2: Dynamic (CPU/RAM: 100% - Host Reserve CPU/RAM) • VM Right Sizing – CPU and Memory • Extensible Framework PRO Partners • Hardware performance monitoring – Servers, Power Supply, Cooling Fans, RAM, CPU, Blade Enclosures • HBA Performance Monitoring – Link congestion, Errors • Storage performance monitoring – Power Supply, Controllers, CPU • Application Performance Monitoring 4. BACKUP Backup • Virtual Machine level – Backup runs inside the VM (using agent) as if it were a physical machine • Application-specific granularity • Capture data on iSCSI/pass-through media • Host level – Backup runs on OS of Parent partition • Leverage “container” provided by a VM • Single Agent for all VMs in a physical machine – Enables Disaster Recovery Host based VSS Backups • Online backups of VM & configuration • Built on Volume Shadow Service (VSS) integration – Using Hyper-V VSS writer – Using VSS hardware or VSS software provider • Provides VM backup in consistent state – Recursive consistency using VSS inside Guest VMs Host based VSS Backups • Single Agent for all VMs on a physical machine • Hyper-V VSS Writer requests snapshot to VSS IC • VSS IC forwards request to all VSS writers inside the VM to prepare for snapshot (consistency) Online versus Offline Backup Online Offline • Running VM • Saved State VM • No downtime • Downtime • Uses VSS and IC • No VSS support or IC (Integration (Integration Components) Components) Using Hyper-V & System Center BUILDING YOUR VIRTUALISATION INFRASTRUCTURE Step 1: Ensure you have Active Directory Domain Controller Ethernet Step 2: Building a Virtualization Farm Domain Controller Virtualization Farm 1 (14 + 2 Servers) Ethernet Step 3: Adding (Shared) Storage Domain Controller Virtualization Farm 1 (14 + 2 Servers) SAN Ethernet 32 connections Fibre Channel Sw itch Step 4: Bare Metal Provisioning with System Center Configuration Manager Domain Controller System Center Configuration Manager Virtualization Farm 1 (14 + 2 Servers) SAN Ethernet 32 connections Fibre Channel Sw itch Step 5: Virtual Machine Provisioning with System Center Virtual Machine Manager Domain Controller System Center Configuration Manager Virtualization Farm 1 (14 + 2 Servers) SAN System Center Virtual Machine Manager Ethernet 32 connections Fibre Channel Sw itch Step 6: Health Monitoring with System Center Operations Manager Domain Controller System Center Configuration Manager Virtualization Farm 1 (14 + 2 Servers) SAN System Center Virtual Machine Manager Ethernet 32 connections Fibre Channel Sw itch System Center Operations Manager Step 7: Virtual Machine Backup with System Center Data Protection Manager Domain Controller System Center Configuration Manager Virtualization Farm 1 (14 + 2 Servers) SAN System Center Virtual Machine Manager Ethernet 32 connections Fibre Channel Sw itch System Center Operations Manager System Center Data Protection Manager Step 8: Virtual Machine Automation with System Center Orchestrator (Opalis) Domain Controller System Center Configuration Manager Virtualization Farm 1 (14 + 2 Servers) SAN System Center Virtual Machine Manager Ethernet 32 connections Fibre Channel Sw itch System Center Operations Manager System Center System Center Data Protection Manager Orchestrator (Opalis) Step 9: Virtual Machine Disaster Recovery with System Center Data Protection Manager Domain Controller System Center Configuration Manager Virtualization Farm 1 (14 + 2 Servers) Replication SAN System Center WAN Virtual Machine Manager Ethernet 32 connections Fibre Channel Sw itch System Center Operations Manager System Center Data Protection Manager Reviewing the System Center Suite Manage Hyper-V hosts Manage Templates Manage Virtual Machines Intelligent Placement Monitor Hyper-V Hosts Monitor Applications Monitor Virtual Machines Performance Optimization Deploy Operating Systems Deploy Updates Deploy Applications Asset Management Protect Hyper-V Hosts Protect Applications Protect Virtual Machines Protect Data Automate VM provisioning, resource allocation and retirement Extend virtual machine management to the cloud Orchestrate incident management and resolution Integrate across monitoring tools, service desks and CMDBs System Center Automated self-service portal for provisioning , chargeback, Virtual Machine Manager and reporting Self-Service Portal 2.0 DEVOTEAM PROJECT APPROACH Project Approach • Different teams (workgroups) work around following topics: 1. Hardware (Servers, Networking, Storage) 2. Deployment (Physical and Virtual) 3. Management (Physical and Virtual) 4. Monitoring (Physical and Virtual) 5. Backup/Restore & Disaster Recovery Project Approach vs Timing Project split up to: • Fasten result/delivery • Lower the complexity level • Shorten the learning curve into 3 Phases: 1. Standalone Virtualisation Host 2. Clustered Virtualisation Hosts in Single Site 3. Clustered Virtualisation Hosts in Multiple Sites Phase 1: Standalone Virtualisation Host SCVMM SCOM HV R2 Concept • Windows Server 2008 R2 standalone Hyper-V virtualisation host(s) • Management using SCVMM 2008 R2 • Monitoring using SCOM 2007 R2 • Backup/Restore using existing solution • Storage using current SAN infrastructure • No Server Disaster Recovery, no Site Disaster Recovery Phase 2: Clustered virtualisation Hosts in Single Site .BIN .VSV .XML .VHD SCVMM SCOM HV R2 HV R2 Concept • Windows Server 2008 R2 clustered Hyper-V virtualisation host(s) in single site • Management using SCVMM 2008 R2 • Monitoring using SCOM 2007 R2 • Backup/Restore using existing backup solution • Storage using current SAN infrastructure • Server Disaster Recovery, no Site Disaster Recovery Phase 3: Clustered virtualisation Hosts in Multiple Sites .BIN .VSV .BIN .XML .VSV .VHD .XML .VHD SCVMM SCOM SCVMM SCOM HV R2 HV R2 Concept • Windows Server 2008 R2 clustered Hyper-V virtualisation host(s) in multiple sites • Management using SCVMM 2008 R2 • Monitoring using SCOM 2007 R2 • Backup using existing backup solution • Storage using SAN infrastructure per datacenter • Server Disaster Recovery, Site Disaster Recovery GLIMPS AT THE FUTURE (2012) System Center 2012 Wave Available Now Coming Soon Beta Beta2 Beta Beta Beta Beta Beta RC System Center Virtual Machine Manager 2012 Deployment Fabric Cloud Services Infrastructure Fabric Cloud Service Enhancements Management Management Management Hyper-V Bare HA VMM Update Service Metal Application Server Management Templates Provisioning Owner Usage Hyper-V, Dynamic Application Upgrade VMware, Citrix Optimization XenServer Deployment Cloud Capacity and Network Power Capability Custom Custom Management Management Command properties Execution Delegation Storage Monitoring Image Based Powershell and Quota Management Integration Servicing CONCLUSION Thank you!
Pages to are hidden for
"Data Center Management using Hyper-V and System Center"Please download to view full document