Server Virtualization with Windows Server Hyper-V and System Center - - PowerPoint PPT Presentation

Veeam 74-409 Study Webinar Server Virtualization with Windows Server Hyper-V and System Center

Orin Thomas @orinthomas

http://hyperv.veeam.com/ study-guide-microsoft-certification-exam-74-409-server-virtualization-windows-server-hyper-v-system-center-4202/

In this seminar we’ll cover:

• Study techniques
• Lab suggestion
• 74-409 Objectives

Study techniques

• You’ll learn more through practice than by reading
• The exam assumes you have used this technology in the “real

world”

• Build a lab and perform the tasks related to the objectives
• Get to the point that given a task related to the objectives, you

could perform it in a lab or a production environment

• Use practice tests from a reputable practice test provider such

as MeasureUp or Self Test Software

Lab Suggestion

• 2 or more computers configured as Hyper-V

virtualization hosts

• Virtualization hosts should be members of a domain
• Host domain controller as VM on one virtualization

host

• Configure the DC VM to start automatically
• Host VMM server on other virtualization host

OD 1: Configure Hyper-V

• Create and configure VM settings
• Create and configure VM storage
• Create and configure virtual networks

Some content covered from the perspective of Hyper-V, such as VM storage, is also covered from the perspective of VMM.

Dynamic Memory

• 2 options for assigning memory
• Can configure static or dynamic assignment
• Static RAM allocates a fixed amount over the VM’s

runtime

• Dynamic allocates variable amounts based on startup,

minimum, and maximum RAM.

Smart Paging

• Special case use of a page file
• Only used when startup RAM exceeds minimum RAM
• Can only be used when restarting a VM, not

performing a cold start of a VM

Resource Metering

• Allows you to track CPU, RAM, network, and storage

utilization for chargeback

• Enabled and monitored through PowerShell

Integration Services

• Allows the virtualization host to interact with the VM

including OS shutdown, time synchronization, and heartbeat monitoring

• Allows use of synthetic network adapters in

generation 1 VMs

• Included with the most recent operating systems,

must be installed for older operating systems

Generation 1 and Generation 2 VMs

• Gen 2 VMs new to Server 2012
• Gen 2 VMs are “virtual first” and don’t include legacy

emulated components such as COM ports and diskette drives

• Faster to install OS and boot
• Can’t convert between generations. Must choose at

creation

• Only certain OS support Gen 2 VMs
• Only support .vhdx virtual hard disks

Enhanced Session Mode

• Simplifies the process of cutting and pasting text and

files when using Virtual Machine Connection

• Allows audio and device redirection from VMs
• Functions similarly to a remote desktop connection
• Requires permission to connect via remote desktop

RemoteFX

• Provides virtual 3D graphics adapter and USB

redirection support for VMs

• Requires a compatible GPU
• Cannot be used with generation 2 VMs

VHD and VHDX formats

VHD

• Used since Virtual Server
• 2040 GB
• Supported on all Hyper-V

hosts

• Can’t be used with Gen 2

VMs

VHDX

• 2012 and later
• 64 TB
• Support larger block size
• Internal log file to reduce

chance of corruption

• Support trim & online

resizing

Dynamic, Differencing & Fixed

• Fixed requires all space allocated at creation
• Dynamic grow as required, but require little initial

space

• Differencing disks have parent/child relationship
• Modifying parent disk will break relationship with

child

Modifying Virtual Hard Disks

• Convert from VHD to VHDX and back
• Change disk size
• Change fixed to dynamically expanding and back
• Can only change disk format or type when VM is
• ffline
• Shrink virtual hard disk in VM OS before attempting to

shrink disk using Hyper-V

Online VHD resize

• Virtualization Host 2012 R2
• VHDX format
• Attached to a virtual SCSI controller
• If shrinking, have already shrunk in guest VM OS

Pass Through Disks

• Give the VM access to the underlying storage
• Allow VMs to access larger volumes
• Less necessary now that VHDX format virtual hard

disks support 64 TB volumes

Checkpoints

• Represent the state of a VM at a particular point in

time

• Called “snapshots” in previous versions of Hyper-V
• Can create checkpoints when VM is running or shut

down

• Hyper-V supports maximum of 50 checkpoints per VM
• VMM supports 64 checkpoints per VM

Virtual Fibre Channel

• Direct connection from VM to Fibre Channel SAN
• Requires compatible HBA on virtualization host
• Requires Server 2012 or later
• SAN must be NPIV enabled
• VM must be running compatible OS
• VMs support up to 4 separate Fibre Channel adapters

each of which can be associated with separate SAN

Storage QoS

• Specify maximum and minimum IOPS for virtual hard

disk

• VM cannot exceed maximum IOPS value
• If virtual hard disk falls below minimum IOPS, event

written to the event log

Hyper-V Virtual Switch

• External: VM is connected through external network

adapter

• Internal: VMs can communicate with each other and

host

• Private: VMs can communicate with one another, but

not host

Optimize Network Performance

• Configure bandwidth management at the virtual

network adapter level

• Configure minimum bandwidth reservation
• Configure maximum bandwidth utilization

SR-IOV

• Single Root Input Output Virtualization
• Physical network adapter is mapped directly to the

VM

• Increases throughput by bypassing virtual switch and

sends network traffic straight to the VM

• VM OS needs driver for physical network adapter
• Physical network adapter drivers need to support SR-

IOV

Dynamic Virtual Machine Queue

• Optimize VM network performance
• Network adapter must support virtual machine queue
• Network traffic is processed by an assigned processor

rather than network adapter

Hyper-V MAC Address Pool

• Allows you to configure the range from which virtual

network adapter MAC addresses are drawn

• Configure pools to ensure that no two VMs on

different virtualization hosts are assigned the same MAC address

VLAN tagging

• Supported at the network adapter and virtual switch

level

• VLAN tag at the virtual switch level overrides VLAN tag

assigned at the virtual network adapter level

• Virtualization host physical network adapters must

support VLAN tagging

Network Adapter Types

• Generation 1 support Synthetic and Legacy adapters
• Synthetic: Require integration components
• Legacy: Works with almost everything. Use for PXE boot
• Generation 2 has single network adapter type
• Only works with OS that support Generation 2 VMs
• Can be used to PXE boot Generation 2 VM

Virtual Machine NIC teaming

• Aggregate bandwidth and provide redundancy across

up to 32 NICs

• Can perform NIC teaming on virtualization host
• Can perform NIC teaming within VM OS
• Supported by Server 2012 and later with no special

hardware requirements

OD 2: Configure and Manage Virtual Machine High Availability

• Configure failover clustering with Hyper-V
• Manage failover clustering roles
• Manage virtual machine movement

Failover clusters

• Windows Server 2012/2012R2 support 64 node

failover clusters

• A 64 node failover cluster can host up to 8000 VMs
• Require shared storage for VM hard disk and

configuration files

• Can use SAS, iSCSI, Fibre Channel, Fibre Channel over

Ethernet for shared storage

Failover Cluster Quorum

• Quorum mode selected automatically when creating

clusters

• Quorum votes can be assigned to nodes, disk, or file

share witnesses

• Quorum modes: Node majority, node and disk

majority, node and file share majority, no majority disk only

Cluster Node Weight

• Allows you to configure whether nodes have quorum

votes

• Use to specify which side of a multi-site cluster will

retain quorum if inter-site communication fails

Dynamic Quorum

• Recalculates quorum model when nodes are removed
• r added to the cluster
• Ensures that outdated quorum model doesn’t push

cluster into a failed state

Cluster networking

• Use NIC teaming
• Configure separate networks
• Network for node to node communication
• Network for connection between node and shared

storage

• Network for client access to resources hosted on the

cluster

Force Quorum Resiliency

• Allows you to avoid partitioned cluster problem
• Used when you force start one side of a multi-site

cluster and reconnection occurs to other site

• Nodes in other site detect that nodes in the first site

were forced into quorum, so automatically restart to avoid partitioned cluster problem

Cluster Aware Updating

• Automates the process of applying software updates

to clusters

• Automatically evacuates a node, places it in

maintenance mode, applies updates, restarts if necessary, and shifts node out of maintenance mode.

• Works through all nodes in the cluster until software

updates have been applied to every node

Upgrading Clusters

• Windows Server 2008, Windows Server 2008 R2, &

Windows Server 2012 can be nodes in Windows Server 2012 R2 clusters.

• Only supported during upgrade scenarios
• Move workload from old OS node to new OS node

then upgrade old OS node to new OS

Cluster Shared Volumes

• High availability storage technology that allows

multiple nodes in a failover cluster to have read/write access to the same storage

• VMs on the same LUN can run on different cluster

hosts

• Minimizes storage failover time

Active Directory Detached Clusters

• Also termed “Clusters without network names”
• Allows cluster creation without requiring permission

to create Active Directory computer objects

• Cluster nodes still need to be members of the same

Active Directory environment

Preferred Owner & Failover Settings

• Allows you to specify which node is the preferred
• wner of a workload
• Workload will attempt to return to that node once

issue that caused failover is resolved

• Failover settings allow you to configure how many

failures occur in a specific period before left in a failed state

Guest Cluster

• A failover cluster where the cluster nodes are VMs
• Still requires access to shared storage
• VM cluster nodes can be on the same or different

failover clusters

Shared Virtual Hard Disk

• Virtual machines can use a shared virtual hard disk as

shared storage

• Requires
• 2012 R2 Host
• Disk must be in VHDX format
• Must be stored on a Scale Out File Server or Clustered

Shared Volume (CSV)

• Must be attached via virtual SCSI controller

Live Migration

• Allows you to move a running VM from one

virtualization host to another without disruption

• Supported between:
• Cluster nodes that use shared storage
• Between separate virtualization hosts that aren’t

participating in a failover cluster using an SMB 3.0 file share

• Between separate virtualization hosts using Shared

Nothing Live Migration

Storage Migration

• Move VM’s hard disk files, configuration files and

checkpoint files from one location to another

• Allows you to change the storage location of a running

VM

• Move data to any location accessible to the Hyper-V

host

Exporting, Importing & Copying VMs

• Export creates a duplicate of a VM
• Can export a VM, which exports all checkpoints
• Can export a checkpoint
• Can export a running VM (2012 R2 only)
• During import, you can:
• Register VM in place (use existing ID)
• Restore VM (use existing ID)
• Copy VM (create new ID)

Network Health Detection

• Mark certain networks as being protected
• If the network marked as protected becomes

unavailable, the VM automatically live-migrates to a cluster node where the network is available.

VM Drain On Shutdown

• Server 2012 R2 and later
• Automatically live migrates VMs from a cluster node

that is shut down by an administrator without being put into maintenance mode

• In previous versions of Windows, these VMs were put

into a saved state

P2V Migrations

• Physical to virtual migrations
• Not supported by VMM 2012 R2
• Supported by VMM 2012

V2V Migrations

• Migrate from 3rd party hypervisors to Hyper-V
• VMM 2012 R2 supports V2V from
• VMware ESX 4.1
• VMware ESXi 4.1
• VMware ESXi 5.1

OD 3: Implement a Server Virtualization Infrastructure

• Implement virtualization hosts
• Implement virtual machines
• Implement virtualization networking
• Implement virtualization storage
• Manage and maintain a server virtualization

infrastructure

Delegating Virtualization Management Tasks

• You create User Roles by selecting
• Role Profiles
• Members
• Scope
• Library servers
• Run As accounts

Role Profiles

• Determines what actions an account assigned a user

role can perform

• VMM role profiles:
• Administrator
• Fabric Administrator (Delegated Administrator)
• Read Only Administrator
• Tenant Administrator
• Application Administrator (Self Service User)

Run As accounts

• Run As accounts are preconfigured accounts that

include username and password

• When using a Run As account, the operation is

performed using the Run As account’s privileges, not the user’s privileges.

Scopes

• Allow you to define the objects with which the

permissions you are delegating can be used

• Fabric Administrator / Read Only Administrators role

profiles allow you to set scopes using existing private cloud or host groups

Quotas

• Allow you to limit the use of
• Virtual CPUs
• Memory
• Storage
• Virtual Machines
• Can be configured at the role level or member level

VMM Libraries

• Collection of file based and non-file based resources
• File based resources can include:
• Virtual Hard Disks
• ISO images
• Scripts
• Driver files
• Application packages
• Non file based resources include:
• VM templates
• Service template
• Hardware & Guest OS profiles

Equivalent Objects

• Allows you to mark specific file based objects stored in

VMM libraries as equivalent

• Allows you to make reference to these objects in

templates and have an equivalent object retrieved from the closest VMM library

Host Group Libraries

• Associate particular libraries to particular host groups
• VMM will use this information when determining

which resources to use if you need a resource marked as an equivalent object

Third Party Integration

• You can use VMM 2012 R2 to manage:
• VMware ESX
• VMware ESXi
• Citrix XenServer

Bare Metal Hyper-V Virtualization Host Deployment

• Deploy Hyper-V to a bare metal device
• Relies upon WDS role in Windows Server
• Configure Physical Computer Profiles.

Implementing Highly Available Virtual Machines

• Can be made highly available by deploying them to

Hyper-V failover cluster

• Can use Hyper-V replica to make them highly available
• Allows replication across site boundaries
• Does not require access to shared storage
• Is asynchronous. Replica copy is consistent, but lagged.
• Supports multiple recovery points
• Planned failover requires VM shutdown

Guest Resource Optimization

• Allows you to deploy to the virtualization host that

has the greatest available resources

• Allows you to ensure that virtualization host resource

utilization is equitable across the fabric

• Intelligent placement provides recommendation on

which virtualization host to use for deployment

Placement Rules

• Allows you to configure custom properties that you

can then use in rules that dictate where VMM can place a new VM during deployment

VMM Templates

• VMM Template allows you create VMs that have a

consistent set of configuration settings

• Templates include one or more of the following:
• Guest OS Profile
• Hardware Profile
• Virtual Hard Disks

Guest OS Profile

• Operating system settings including
• OS version
• Name information
• Administrator password
• Product key
• Time zone
• Roles & Features
• Domain/Workgroup Membership
• Answer File

Hardware Profile

• Gen 1 or Gen 2 VM
• Cloud compatibility
• Processor type
• Memory allocation
• Floppy drive
• COM Port
• Video Adapters
• IDE and SCSI configuration
• Network adapter

configuration

VMM Logical Networks

• Collection of network sites, VLAN information, and IP

subnet information

• Must have one logical network in VMM before you

can deploy VMs and services

• Network sites allow you to associate IP subnets,

VLANs & PVLANs with the logical network

VMM Port Profiles / Logical Switches

• Function as collections for configuration settings for

network adapters across multiple virtualization hosts

Network Virtualization

• Allows you to configure logical networks so that

different VM tenants can be assigned the same IP addresses on the same Hyper-V host without address collisions occurring

• If a logical network is configured for network

virtualization, you can connect multiple VMM Virtual Machine Networks to the same logical network

VMM Virtual Machine Networks

• Provide the interface through which VMs connect to a

VMM Logical Network

VMM MAC Pools

• MAC address pools allow MAC address information to

be managed across all virtualization hosts that VMM manages

VMM IP Address Pools

• IP address pools allow VMM to assign IP addresses to
• VMs. The benefit of this over DHCP is that you can

ensure the same IP address is assigned to a VM without having to create a DHCP reservation

• Includes default gateway and name server information

Windows Server Gateway

• A specially configured virtual machine that can route

traffic between different networks

Private VLANs (PVLANs)

• VLANs segment traffic at layer 2
• VLAN IDs are 12 bit numbers
• PVLAN is an additional ID that allows you to segment

VLANs

• Implement in VMM through logical networks

Configuring Hyper-V Host Clustered Storage

• When deploying on a Hyper-V host cluster the VM

configuration and storage files for highly available VMs are hosted on shared storage

• This can be
• iSCSI
• SAS
• Fibre Channel
• SMB 3.0
• Cluster Shared Volumes (CSV)

Guest Cluster Storage

• Guest clusters are where each cluster node is a VM
• Guest cluster shared storage can be:
• iSCSI
• Virtual Fibre Channel
• CSV
• Continuously Available File Shares
• Shared Virtual Hard Disks

Storage Optimization

• Deduplication. Built into Windows Server 2012 and

2012 R2

• Storage Tiering. Commonly used blocks are moved to

faster storage, such as SSD, with less commonly used blocks moved to slower storage, such as spinning magnetic disks.

Integrating Operations Manager with VMM

• Monitor health and availability of:
• VMM management server
• VMM database server
• VMM library servers
• Virtualization hosts
• Use Performance and Resource Optimization (PRO)
• Maintenance mode integration

Integrate Service Manager 2012 R2

• ITIL / MOF Service Management implementation
• Central Platform to manage incidents, problems,

changes, and releases.

Service Virtual Machine Images

• Update VM images in the library prior to deployment
• Can use
• Virtual Machine Servicing Tool (deprecated)
• Orchestrated Offline VM Patching Runbook

Data Protection Manager 2012 R2

• Protect virtualization hosts and VMs
• Provide protection within a VM
• Stores protected data on disk, tape and can replicate

to a second DPM server & Azure cloud

(As this is a Microsoft technology exam, it doesn’t mention Veeam)

OD 4: Monitor and maintain a server virtualization infrastructure

• Plan and implement a monitoring strategy
• Plan and implement a business continuity and disaster

recovery solution

Audit Collection Services

• Allows you to centralize and analyze event log audit

data

• Is an individual component of Operations Manager

System Center Global Service Monitor

• Cloud service that allows you to monitor web

applications from a variety of locations around the world

• Monitoring can perform complex tasks, such as

signing into an application, or checking that items can be added to and checked out from a shopping cart

Operations Manager Management Packs

• VMM Management Pack:
• Monitor all aspects of the VMM infrastructure
• VMM servers
• Virtualization hosts
• Virtual machines
• Fabric health dashboard
• View health of each VMM private cloud
• View health of fabric that supports that cloud

Operations Manager Reporting

• Use SQL Server Reporting Services to generate

complex reports based on data stored in the Operations Manager data warehouse database.

• Increase number of reports
• Add management packs
• Author your own reports

Operations Manager Management Packs

• Extend the functionality of Operations Manager
• Improve the product’s ability to interact with specific

applications or services

• Usually created by product vendors or subject matter

experts

• Management packs include: Monitors, rules, tasks,

knowledge, views, reports, object discoveries and Run As profiles

Domain Controller Cloning

• Requires virtualization host that support

VMGenerationID

• DC must be running 2012 or later
• PDC emulator must be available
• Template DC computer account must be member of

the Clonable Domain Controllers security group

Hyper-V Recovery Manager

• Service hosted in Azure cloud
• Manages Hyper-V replication
• Automates the process of Hyper-V replica failover
• Performs continuous health monitoring and
• rchestrated recovery

Thank You & Good Luck On Your Exam!