70-412 Chapter 4: Managing Virtual Machine Movement

Front 1

is the engine of virtualization, and virtualization that refers to hosting one or more instances of a host being defined as a collection of hardware, operating system, and other software resources; and the VMs actually run in software on the hardware host

Back 1

Hypervisor

Front 2

Hyper-V versions?

Back 2

-1.0: Part of WS2K8 release to manufacturing release (weak and roundly criticized ; outweighed by VM products
-2.0: Part of WS2K8R2, which gave excellent features such as “Dynamic Memory”, “Live Migration”, “CSV and HA VMs”
-3.0: Part of Server 2012, includes 2K8 features, builds upon them and gives us even more

Front 3

Hypervisors are divided into two general classifications...What are those?

Back 3

-Type 1: known as a bare metal hypervisor (Hyper-V)-means that the hardware on the physical host, network, storage, CPU, and memory>then we have the HyperVisor> then we have the OS; Since the hypervisor is so close to the hardware layer, it can provide VMs much better access (VM’s server product ESXI is a type 1)
-Type 2: is a hosted hypervisor; Has the HyperVisor layer farther up the stack; Hardware at the bottom>Then OS>Then the HyperVisor; this relates to applications like VMWare Workstation or Microsoft Virtual PC, Oracle Virtual Box; these don’t have as good as performance as a Type 1, because there is a longer run between the hypervisor and the hardware resources

Front 4

What are the specs of the virtual machines in Server 2012?

Back 4

Each of your virtual machines, can use up to 64 physical processors, 1 TB RAM, and multiple 64 TB vhdx; In other words we can create VMs (instances of a computer system represented in software) that can handle of virtualize any workload

Front 5

is where we move a VM, in or outside a cluster, this is what was available in previous versions (Hyper-V 1.0) and is still around for backwards compatibility

Back 5

Quick Migration

requires turning the VM off

Front 6

we use this option is we need to move or migrate a VM into or out of a cluster, or to a different cluster etc… ; which involves no “downtime”, and users could be using resources such as our virtual desktop and none of the users would know or experience any glitches or downtime

Back 6

Live Migration

Front 7

Microsoft strongly recommends this, because this software seamlessly blends services like Hyper-V, Failover Clustering, Virtual Network Infrastructure…etc; and makes working with larger robust virtual infrastructure a lost easier

Back 7

System Center Virtual Machine Manger 2012

Front 8

Virtual Machines consists of a couple different parts, what are those?

Back 8

-* The vhdx (virtual harddrive) x=extensible markup language (xml); bigger capacities and perform better than vhd formats
-* The memory footprint (RAM)- what’s going on in the current running state of the VM; involves running services, running applications, file handles…etc
-* The configuration/metadata (xml) regarding the VM; Any snapshots
(*)-When we do imports, exports, or migrations, Microsoft gives us the ability to separate out these different factors; so that we may just move just the storage, but keep the ownership and the hosting of the VM in its current spot

Front 9

means that we want a “Hot Standby” for our virtual machine

Back 9

Hyper-V replica`

Front 10

Replica uses what type of replication?

Back 10

Asynchronous Replication”-replicates every 5 minutes, replication schedule can be customized though
-The first copy will be huge, because we need to create a baseline of our primary
-Then subsequently, we will have replication events that will be smaller, that replicates only the delta differences from the primary, that go to the replica or backup site.
-* The primary site is “Online” and the secondary site is “Offline”

Front 11

How do we combine Failover Clustering Highly Available VMs with Replica?

Back 11

requires us to bring up an extra role on our servers (Hyper-V Replica Broker) that needs to part of the failover cluster.

Front 12

ensures that the new node will continue to replicate In the event of a failover, live migration, etc

Back 12

Hyper-V Replica Broker

Front 13

-Is it possible to go from a physical machine to a VM?

Back 13

Yes, but….Microsoft’s recommendation suggests that we use a tool such as “System Center Virtual Machine Manager 2012” that makes this strenuous process much easier
(Exam)- We need to know that when we are looking at P2V, it is possible to do with the inbox VM tools, but SCVMM 2012 is a better option, because it is optimized for this kind of situation.

Front 14

What if we are moving from a VMWare environment (Vsphere, XenServer environment), and we want to migrate into Hyper-V.
-Those vendors use different formats for the virtual harddrives. Therefore how is this possible?

Back 14

SCVMM 2012 is architected to identify and to be able to work with VMWare or Citrix VMs

Front 15

involves “virtual infrastructure” and “virtualized services” securely available to our user base

Back 15

Private Cloud

Front 16

has the private aspect, but also faces the public internet in certain cases (Ex: Office 365)

Back 16

Hybrid Cloud

Front 17

dropbox…etc

Back 17

Public Cloud

Front 18

concept in Hyper-V that is configured for hosted scenarios, when we need to deploy multiple virtual servers and multiple networks; and we should always isolate VMs from each other; this feature allows us to virtualize entire networks and keep the separate.

Back 18

Network Virtualization

Front 19

The number of virtual processors supported by a guest operating system

Back 19

64

Front 20

The amount of memory supported by VMs?

Back 20

1 TB

Front 21

Virtual hard disk capacity supported by VMs?

Back 21

64 TB supported by the VHDX format introduced in Windows Server 2012 and Windows® 8; 2040 GB supported by the VHD format.

Front 22

Amount of Virtual IDE disks supported by the VMs?

Back 22

4; requires integration services to be installed in the guest operating system

Front 23

Amount of Virtual SCSI disks supported by the VMs?

Back 23

256; Each SCSI controller supports up to 64 disks, which means that each virtual machine can be configured with as many as 256 virtual SCSI disks. (4 controllers x 64 disks per controller)

Front 24

Amount of Virtual Fibre Channel adapters supported by the VMs?

Back 24

4;As a best practice, we recommended that you connect each virtual Fibre Channel Adapter to a different virtual SAN.

Front 25

Size of physical disks attached directly to a virtual machine

Back 25

Varies; Maximum size is determined by the guest operating system.

Front 26

Number of snapshots a VM can have?

Back 26

50
The actual number may be lower, depending on the available storage. Each snapshot is stored as an .avhd file that consumes physical storage.

Front 27

How many virtual network adapters can a VM have?

Back 27

12; 8 can be the “network adapter” type. This type provides better performance and requires a virtual machine driver that is included in the integration services packages.

4 can be the “legacy network adapter” type. This type emulates a specific physical network adapter and supports the Pre-execution Boot Environment (PXE) to perform network-based installation of an operating system.

Front 28

Number of virtual drives and serial com ports?

Back 28

1 virtual floppy, and 2 virtual serial com ports

Front 29

How many logical processors can the Hyper-V host have? and how many virtual processors per each logical processor?

Back 29

320
Both of the following must be available and enabled in the BIOS:
Hardware-assisted virtualization

Hardware-enforced Data Execution Prevention (DEP)

*
No ratio imposed by Hyper-V

Front 30

How many simultaneously running VMs can be executed on Hyper-V hosts?

Back 30

1024

Front 31

How many virtual processors can Hyper-V Host produce the VMs?

Back 31

2048

Front 32

How much memory can the Hyper-V host use as a resource for the VMs?

Back 32

4 TB

Front 33

How much storage can a Hyper-V host have?

Back 33

Limited by what is supported by the management operating system. No limits imposed by Hyper-V.

Front 34

How much Virtual storage area networks (SANs) can the Hyper-V host optimize for the VMs?

Back 34

No limits imposed by Hyper-V

Front 35

How many Physical network adapters, Network adapter teams (NIC Teaming),Virtual switches,Virtual network switch ports per server can a Hyper-V host have?

Back 35

No limits imposed by Hyper-V.
None.

Front 36

How many Nodes per cluster can a Hyper-V host have?

Back 36

64; Consider the number of nodes you want to reserve for failover, as well as maintenance tasks such as applying updates. We recommend that you plan for enough resources to allow for 1 node to be reserved for failover, which means it remains idle until another node is failed over to it. (This is sometimes referred to as a passive node.) You can increase this number if you want to reserve additional nodes. There is no recommended ratio or multiplier of reserved nodes to active nodes; the only specific requirement is that the total number of nodes in a cluster cannot exceed the maximum of 64.

Front 37

How many running virtual machines can be going in a single cluster?

Back 37

8,000 per cluster;

Several factors can affect the real number of virtual machines that can be run at the same time on one node, such as:
Amount of physical memory being used by each virtual machine.

Networking and storage bandwidth.

Number of disk spindles, which affects disk I/O performance.

Front 38

Which Physical Computers Can I Convert, and what are the requirements?

Back 38

*Depends on whether you are performing an online or offline P2V.

*VMM temporarily installs an agent on the physical source computer that you want to convert. By using online P2V, VMM uses the Volume Shadow Copy Service (VSS) to copy data while the server continues to service user requests.

*The source computer is not restarted during the conversion. By using offline P2V, the source computer reboots into the Windows Preinstallation Environment (Windows PE) before VMM converts the physical disks to Virtual Hard Disks (VHDs).

*Must be in the same domain as the VMM server or a member of a domain that has a full two-way trust with the VMM server’s domain.

Front 39

HYPER-V CMDLETS

Installs a virtual Fibre Channel host bus adapter in a virtual machine (VM).

Back 39

Add-VMFibreChannelHba

Front 40

HYPER-V CMDLETS

Adds a network to the list of networks that can be used for virtual machine (VM) migration.

Back 40

Add-VMMigrationNetwork

Front 41

HYPER-V CMDLETS

Installs a network adapter in a virtual machine (VM).

Back 41

Add-VMNetworkAdapter

Front 42

HYPER-V CMDLETS

Creates an access control list (ACL) to apply to the traffic sent or received by a virtual machine (VM) network adapter.

Back 42

Add-VMNetworkAdapterAcl

Front 43

HYPER-V CMDLETS
Creates an extended ACL for a virtual network adapte

Back 43

Add-VMNetworkAdapterExtendedAcl

Front 44

HYPER-V CMDLETS

Adds a routing domain and virtual subnets to a virtual network adapter.

Back 44

Add-VmNetworkAdapterRoutingDomainMapping

Front 45

HYPER-V CMDLETS

Installs a SCSI controller in a virtual machine (VM).

Back 45

Add-VMScsiController

Front 46

HYPER-V CMDLETS

Adds a path to a storage resource pool.

Back 46

Add-VMStoragePath

Front 47

HYPER-V CMDLETS

Adds a network to a resource pool.

Back 47

Add-VMSwitch

Front 48

HYPER-V CMDLETS

Creates a snapshot of a virtual machine (VM).

Back 48

Checkpoint-VM

Front 49

HYPER-V CMDLETS

Compares a virtual machine (VM) to a host and returns a compatibility report.

Back 49

Compare-VM

Front 50

HYPER-V CMDLETS

Completes the failover process of the virtual machine (VM).

Back 50

Complete-VMFailover

Front 51

HYPER-V CMDLETS

Associates a host bus adapter with a virtual storage area network (VMSAN).

Back 51

Connect-VMSan

Front 52

HYPER-V CMDLETS

Converts the format version and type of virtual hard disk file of a virtual machine (VM).

Back 52

Convert-VHD

Front 53

HYPER-V CMDLETS

Enables replication of a virtual machine.

Back 53

Enable-VMReplication

Front 54

HYPER-V CMDLETS

Exports a virtual machine (VM) to disk.

Exports a snapshot as a virtual machine (VM) and writes it to disk.

Back 54

Export-VM

Export-VMSnapshot

Front 55

HYPER-V CMDLETS

Moves the storage of a virtual machine (VM).

Back 55

Move-VMStorage

Front 56

HYPER-V CMDLETS

Creates an authorization entry containing the allowed primary server and corresponding replica storage.

Back 56

New-VMReplicationAuthorizationEntry

Front 57

HYPER-V CMDLETS

Modifies the Failover IP settings of the network adapter for a virtual machine (VM).

Back 57

Set-VMNetworkAdapterFailoverConfiguration

Front 58

How do you create a Hyper-V failover cluster?

Back 58

Create a failover cluster, then add the Hyper-V role to each node of the cluster; User CSVs to store the VMs on a Hyper-V cluster

Front 59

Allows multiple cluster nodes to manage a single shared storage device

Back 59

Cluster Shared Volumes; enables us to put multiple virtual machines on the same shared storage device, but have those VMs hosted by different nodes in the failover cluster.

Front 60

How do we allow migration between Hyper-V nodes (servers) with different processor types or versions.

Back 60

Enabling the Process Compatibility Settings on the Virtual Machine?

Front 61

What does Shared Nothing Hyper-V Live Migration allow us to do?

Back 61

Enables us to migrate a VM running on one Hyper-V host to another Hyper-V hosts without the VM experiencing downtime and without requiring the use of share storage; Can be used to move a VM from one Hyper-V failover cluster to another.

Front 62

When configuring authentication for live migration, you can choose between Credential Security Support Provider(CredSSP) or Kerberos authentication; What are these protocols and what are the differences?

Back 62

*CredSSP requires an local sign on to both the source and destination servers to perform migration

*Kerberos enables you to trigger live migration from a remote server, but has to be configured for constrained delegation for the "cifs" & "Microsoft Virtual System Migration Services" on the computer accounts of the Hyper-v hosts.

Front 63

Enables you to move the virtual machine's storage from one location to another, this includes the virtual hard disk files, snapshot files and smart paging files

Back 63

Storage Migration

Front 64

You can only move VM storage to a shared folder only if the shared folder is hosted on a computer running Server 2012 +, why?

Back 64

Because Server 2012 uses SMB 3.0, and we can't use file shares that leverage previous versions of SMB protocol, such as Windows 2008 R2 file shares

Front 65

We can move all of our VMs to an external storage, while we perform maintenance on the Hyper-V host's storage, and as long as the host can access the storage and the VMs, then there is no downtime during the migration; how do we perform storage migration?

Back 65

Select "Move the Virtual Machine's Storage

Front 66

involves ensuring that an organization has access to critical resources in the even that a site goes unexpectedly offline

Back 66

Site-level fault tolerance

Front 67

provides organizations with a method of having critical VMs replicated to a second site allowing both planned and unplanned failover with minimal data loss

Back 67

Hyper-V Replica; the host running Hyper-V replica could be in the same room or a different continent;Doesn't require access to a shared storage or that the computers be part of the same domain

Front 68

involves configuring a cluster so that the cluster retains quorum in the event that a site goes offline unexpectedly.

Back 68

Multisite Clustering

Front 69

What are the steps in Configuring Hyper-V Replica

Back 69

1.Enable Replication
2.Choose the Authenticaton Method: Kerberors or certificate-based authentication. Kebereros is appropriate if the source and destination are in the same AD environment; Certificate is appropriate when the computers are not part of the same AD environment (domain)
3.Specify which authenticated servers replication can be performed from; From any server, or only specific servers; and specify the location where replicated files will be stored;
4. Specify the firewall rule
5.Specify the virtual hard disk and the number of reocvery points

Front 70

What is the built-in firewall rule for kerberos?

What is the firewall rule when using certificate based authenticaton

Back 70

Kerberos: Hyper-V Replica HTTP

Certificate: 443

Front 71

involve moving a VM configured for replication from its primary host to the replica server

Back 71

Planned failover; the VM being moved must be in a turned-off state; this is a huge difference from Hyper-V Live Migration; You can also configure the VM to start whenever the failover process completes

Front 72

How do you perform planned failover in Powershell?

Back 72

Start-VM Failover

Front 73

occurs when the primary server has failed unexpectedly

Back 73

Unplanned Failover; during unplanned failover, you have to connect to the replica server and trigger failover manually and specify a recovery point to use