25
Server Virtualization Name Title Microsoft Technical Overview

Windows Server 2012 R2 Server Virtualization Technical Overview- Mod 3

  • Upload
    -

  • View
    71

  • Download
    7

Embed Size (px)

DESCRIPTION

Server 2012

Citation preview

Server Virtualization

NameTitle

Microsoft

Technical Overview

High Availability & Resiliency

Shared VHDX

Hyper-V Replica with

Extended Replication

Online Backup

Simplify infrastructure maintenance

Robust, reliable & resilient infrastructure foundation for running continuous services

Provide flexibility for application-level resiliency

High Availability & Resiliency

Cluster Aware Updating

Hyper-V Recovery Manager

Guest Clustering

Failover Clustering

NIC Teaming

Failover Priority & Affinity Rules

Integration with cloud services

Provide granular solutions for enabling disaster recovery

NIC Teaming

• Vendor agnostic and shipped inbox

• Provides local or remote management through Windows PowerShell or UI

• Enables teams of up to 32 network adapters

• Aggregates bandwidth from multiple network adapters whilst providing traffic failover in the event of NIC outage

• Includes multiple nodes: switch dependent and independent

• Multiple traffic distribution algorithms: Hyper-V Switch Port, Hashing and Dynamic Load Balancing

Integrated Solution for Network Card Resiliency

NIC Teaming

Virtual adapters

Team network adapter

Team network adapter

Operating system

Failover Clustering

• Massive scalability with support for 64 physical nodes & 8,000 VMs

• VMs automatically failover & restart on physical host outage

• Enhanced Cluster Shared Volumes

• Cluster VMs on SMB 3.0 Storage

• Dynamic Quorum & Witness

• Reduced AD dependencies

• Drain Roles – Maintenance Mode

• VM Drain on Shutdown

• VM Network Health Detection

• Enhanced Cluster Dashboard

Integrated Solution for Resilient Virtual Machines

Shared Storage

Node 1 Node 2 Node 3…

…Node 64

Cluster Dynamic Quorum Configuration

Node & Disk MajorityNode Majority

V= Vote

V V V V

V

Virtual Machine Monitoring

• Upon service failure, Service Control Manager inside guest will attempt to restart the service

• After 3 failures, Cluster Service willtrigger event log entry 1250

• VM State = Application in VM Critical

• VM can be automatically restarted on the same node

• Upon subsequent failure, VM can be failed over and restarted on alternative node

• Extensible by Partners

Monitor Health of Applications Inside Clustered VMs

Hyper-VCluster Node

Clustered VM with Monitoring Enabled

Hyper-V cluster with VMs on each nodeUpon failover, VMs restart in priority order

Failover Priority, Affinity & Anti-Affinity

• Failover Priority ensures certain VMsstart before others on the cluster

• Affinity rules allow VMs to reside oncertain hosts in the cluster

• AntiAffinityClassNames helps to keep virtual machines apart on separate physical cluster nodes

• AntiAffinityClassNames exposedthrough VMM as Availability Set

Ensure Optimal VM Placement and Restart Operations

iSCSI, FC or SMB Storage

Hyper-VHosts

1 2

Anti-Affinity keeps related VMs apart

Cluster Aware Updating

• Reduces server downtime and user disruption by orchestration of cluster node updates

• Maintains service availability without impacting cluster quorum

• Detects required updates and moves workloads off nodes for updates

• Uses Windows Update Agent or extensible plug-in

Integrated Patching Solution for Hyper-V Clusters

Windows Server Cluster

Application Client

Current Workload

Third-party plug-in for updates

Windows ServerUpdate Services (WSUS)

U

SMB share with third-

party update files

Guest Clustering

• Full support for running clustered workloads on Hyper-V host cluster

• Guest Clusters that require shared storage can utilize software iSCSI, Virtual FC or SMB

• Full support for Live Migration of Guest Cluster Nodes

• Full Support for Dynamic Memory of Guest Cluster Nodes

• Restart Priority, Possible & Preferred Ownership, & AntiAffinityClassNameshelp ensure optimal operation

Complete Flexibility for Deploying App-Level HA

iSCSI, Fibre Channel or

SMB Storage

Hyper-V HostCluster

GuestCluster

Guest Cluster running on a Hyper-V ClusterGuest cluster node restarts on physical host failure

Guest cluster nodes supported with Live Migration

Guest Clustering with Shared VHDX

• VHDX files can be presented to multiple VMs simultaneously, as shared storage

• VM sees shared virtual SAS disk

• Unrestricted number of VMs canconnect to a shared VHDX file

• Utilizes SCSI-persistent reservations

• VHDX can reside on a Cluster Shared Volume on block storage, or onFile-based storage

• Supports both Dynamic and Fixed VHDX

Guest Clustering No Longer Bound to Storage Topology

CSV onBlock Storage

SMB ShareFile Based Storage

GuestCluster

SharedVHDX File

GuestCluster

SharedVHDX File

Hyper-VHost Clusters

Flexible choices for placement of Shared VHDX

DemoGuest Clustering with Shared VHDX

Streamlined Incremental Backup

• Allows incremental backup of virtual hard disks

• Is Volume Shadow Copy Service (VSS)-aware

• Backs up the Hyper‑V environment

• Requires no backup agent inside virtual machines

• Saves network bandwidth

• Reduces backup sizes

• Saves disk space

• Lowers backup cost

Integrated Virtual Machine Backup Capabilities

VHD VHD VHD VHD VHD VHD

VHDVHDVHDVHDVHDVHD

Sunday Monday

First full backup after enabling incremental backup First incremental backupBefore backup During backup After backupBefore backup During backup After backup

Before backup During backup After backup Before restore During restore After restore

Differences 1 Differences 1 Differences 1 Differences 1 Differences 2

Differences 2

Differences 2 Differences 2 Differences 3

Differences 3

Differences 3

Differences 3

Differences 2

Differences 1

Merge

Second incremental backup Incremental restore

Files in blue are backed up

Tuesday Friday: Restore to Tuesday’s Backup

Merge

Merge

Windows Azure Backup Integration

• Simple installation and configuration

• Ability to leverage Windows AzureBackup cloud services to back up data

• Use either the Windows Azure Backup Service Agent or the Windows Azure Backup PowerShell cmdlets

• Reduced cost for backup storageand management

• Options for third-party cloud services

• Ideal for small businesses, branchoffices, and departmentalbusiness needs

Windows Server Backup Integrated with Cloud Services

Registration

• Sign up• Billing

Third-party cloud

• Sign up• BillingWindows Azure

Backup service

Windows AzureBackup portal

Third-party onlinebackup service

Third-party online

backup portal

Inbox engineInbox UI

Windows Server 2012 R2 backup (extensible)

Windows Server 2012 R2

Agents• Windows Azure Backup• Third-party agents

IT Pro

RegistrationBackup/Restore

Once Hyper-V Replica is enabled, VMs begin replication

• Affordable in-box business continuity and disaster recovery

• Configurable replication frequencies of 30 seconds, 5 minutes and 15 minutes

• Secure replication across network• Agnostic of hardware on either site• No need for other virtual machine

replication technologies• Automatic handling of live migration• Simple configuration and

management

Replicate Hyper‑V VMs from a Primary to a Replica site

Hyper‑V Replica

Primary Site Secondary SiteInitial Replica

Once replicated, changes replicated on chosen frequency

Replicated Changes

Upon site failure, VMs can be started on secondary site

CSV onBlockStorage

SMB Share

File BasedStorage

Replication configured from primary to secondary

Hyper-V Replica | Extended Replication

• Once a VM has been successfully replicated to the replica site, replicacan be replicated to a 3rd location

• Chained Replication

• Extended Replica contents match the original replication contents

• Extended Replica replication frequencies can differ from original replica

• Useful for scenarios such as SMB -> Service Provider -> Service Provider DR Site

Replicate to 3rd Location for Extra Level of Resiliency

DR Site

DASStorage

Replication can be enabled on the 1st replica to a 3rd site

Replication

Hyper-V Recovery Manager

• Protect important services bycoordinating replication and recovery of VMM-managed private clouds

• Automates replication of VMs within clouds between sites

• Hyper-V Replica provides replication, orchestrated by Hyper-V Recovery Manager

• Can be used for planned, unplanned and testing failover between sites

• Integrate with scripts for customization of recovery plans

Orchestrate protection and recovery of private clouds

Replication Channel

Datacenter 1

LOB cloud/Dev-testLOB cloud/Dev-test

Failover

Datacenter 2

Com

munic

atio

n

chan

nel

Com

munication

chan

nel

Windows AzureHyper-V Recovery Manager

Hyper-V Hosts

Hyper-V Hosts

System Center 2012 R2

System Center 2012 R2

DemoVM Replication

VirtualizationInnovation

Generation 2 Virtual Machines

Ease of Management & Operations

• PXE boot from Optimized vNIC

• Hot-Add CD/DVD Drive

Dynamic Storage

• VMs have UEFI firmware with supportfor GPT partitioned OS boot disks >2TB

• Faster Boot from Virtual SCSI with OnlineResize & increased performance

Security

• Removal of emulated devices reduces attack surface

• VM UEFI firmware supports Secure Boot

VMs built on Optimized, Software-Based Devices

Generation 2 Virtual

Machine

Synthetic NIC PXE Boot

Hot-Add CD/DVD

Drive

UEFI Firmware with Secure

Boot

Boot FromVirtual SCSI

Enhanced Session Mode

Improved VMBus Capabilities enable:

• Audio over VMConnect

• Copy & Paste between Host & Guest

• Smart Card Redirection

• Remote Desktop Over VMBus

Enabled for Hyper-V on both Server& Client

Fully supports Live Migration of VMs

Enhancing VMConnect forthe Richest Experience

Automatic Virtual Machine Activation

• Activate VMs without managingproduct keys on a VM by VM basis

• VMs activated on start-up

• Reporting & Tracking built-in

• Activate VMs in remote locations, with or without internet connectivity

• Works with VM Migration

• Generic AVMA key for VMs activatesagainst a valid, activated WindowsServer 2012 R2 Hyper-V host

Simplifying Activation of Windows Server 2012 R2 VMs 1

Windows Server 2012 R2 Datacenter host activated with regular license key

2Windows Server 2012 R2 VM is created, with an AVMA key injected in the build

3

On start-up, VM checks for an activated, Windows Server 2012 R2 Datacenter Hyper-V host

4Guest OS activates and won’t recheck against host until next guest reboot, or after 7 days.

Windows Server 2012 R2

Datacenter Hyper-V Host

Windows Server 2012 R2 VM

Summary

Summary

Scalability & Performance

Security & Multitenancy

Flexible Infrastructure

High Availability & Resiliency

VirtualizationInnovation

Hyper-V: A More Complete Virtualization Platform

Get the evaluation

Evaluate | Train | Certify

Microsoft Server and Cloud Platform:http://www.microsoft.com/en-us/server-cloud/windows-server/

Microsoft Virtual Academy:http://www.microsoftvirtualacademy.com

Microsoft Learning:http://www.microsoft.com/learning

Get trained

Get certified

© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.