Ten Essential Skills for the Next Generation of Hyper-V Brien Posey

Transcription

1 Ten Essential Skills for the Next Generation of Hyper-V Brien Posey Microsoft MVP

2 About Me Freelance technical writer and ten year Microsoft MVP Over two decades of IT experience Previously CIO for national chain of hospitals and healthcare facilities. Served as a network engineer for the DoD at Fort Knox Worked as a network admin for two large insurance companies

3 Hyper-V 2.0 vs Hyper-V 3.0 Hyper-V 2.0 and 3.0 look alike on the surface, but are actually very different. Hyper-V 2.0 Hyper-V 3.0

4 Essential Skills Having similar interfaces makes Hyper-V 3.0 easy to use for experienced admins. Hyper-V 3.0 has loads of new features, which means learning new skills. This Web cast gives you the top ten!

5 Top Ten Skills 1. External Live Migrations 2. Migrating VMs from Hyper-V 2 to Hyper-V 3 3. Failover Prioritization 4. Monitor Replication Health 5. Fix Replication Errors 6. Creating a VM Through PowerShell 7. Convert from VHD to VHDX 8. Storage Provisioning 9. NIC Teaming 10. Cluster Patching

6 External Live Migrations Live Migrations are no longer confined to clusters You can live migrate running VMs into and out of clusters (or even between clusters). This is useful for moving VMs between staging and production environments. Ideally all hosts should belong to a common domain.

7

8

9

10

11

12

13

14 VM Migrations In place upgrades are possible, but not always practical VM down time Can t perform in place upgrades within a cluster. You must temporarily create a second cluster. Many options exist for VM migrations including: Third party tools Backup / Restore Hyper-V Import / Export

15

16

17

18

19

20

21

22

23 Failover Prioritization Each cluster node has a finite set of hardware resources that limits the number of VMs that can run on it. When a failover occurs, VMs fail over to another cluster node. If the node is already running VMs it may not be able to run all of the VMs from the failed node. Prioritization lets you decide which VMs are the most important.

24

25 Monitoring Replication Health Replication is a low budget alternative to clustering in which replicas of VMs and virtual hard disks are created on a replica server. Replicas sometimes fall out of sync. It is important to periodically check the replica health. Important: Each replica may have a different assessment of the replication health!

26

27

28

29 Fixing Replication Errors Reset the health report to verify that there is really a problem Try the Resume Replication option first. Check network connectivity. Verify that adequate disk space is available and that disk quotas are turned off. Check the server s event logs.

30

31 Creating a VM with PowerShell Hyper-V can be fully managed with PowerShell. VM creation can be scripted. The New-VM cmdlet is used for virtual machine creation

32 PowerShell VM Creation New-VM Name PowerShellVM Path C:\VMs ComputerName Lab1 This command creates a virtual machine named PowerShellVM with the following specs: 512 MB of memory DVD drive No virtual hard disk No network connection 1 virtual processor

33

34

35 Convert VHD to VHDX VHD and VHDX are virtual hard disk formats Supported Maximum Capacity Error Correction VHD Introduced with Hyper-V 1.0, but still supported in 3.0 VHDX 2 TB 64 TB Minor error correction Only recognized in Hyper-V 3.0 Advanced integrity checking

36

37

38

39 Storage Provisioning Disk Management Console exists in Windows Server 2012, but only for backward compatibility. Storage should be provisioned through Windows Storage Spaces Physical disks are grouped into storage pools Virtual disks exist on top of storage pools Virtual disks can be thinly provisioned and additional physical storage space can be added to a pool on an as needed basis. Virtual disks can be mirrored or use parity.

40

41

42

43

44

45 NIC Teaming Network bandwidth is often a bottleneck on host servers. NICs can be teamed together as a way of aggregating bandwidth. You can use commodity NICs and mix match NIC vendors. Hyper-V 2.0 could only use NICs that were teamed at the hardware level. Hyper-V 3.0 / Windows Server 2012 offers software NIC teaming.

46

47

48 Cluster Aware Updating In Hyper-V 2.0 cluster patching was a tedious process Live migrate VMs Place node into maintenance mode Install the updates Reboot the server Take server out of maintenance mode Repeat the process for other nodes Hyper-V 3.0 automates cluster updating through the Cluster Aware Updating feature. Updates can run locally on cluster nodes or remotely from Windows 8 or Server 2012 machines. The update process can be scheduled (use off peak hours)

49

50

51 Thank You Q&A