Hyper-V

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.

Share tech news, updates, or what's on your mind.

Sign up to Post

Can you run Linux on a Windows system? Yep. Here's how.
1
Want to create a VM? Here's how you do it.
0
Take advantage of one of the most useful technologies available - virtualization!
0
Herein one will find an aggregate of some of my experience building and deploying virtualization stacks both in standalone, clustered Hyper-V, clustered Hyper-V with a Scale-Out File Server (SOFS) backend, and Storage Spaces Direct (S2D).
2

Expert Comment

by:Timothy Alexander
What are some good heuristics when considering the ratio of total Guest vCPUs to Host Physical Cores(ignoring HT/SMT); 2:1, 3:1?
The more involved followup might be how to measure core contention on a Hyper-V Host

Also when does core count matter more vs frequency, I guess the answer is workload dependent.
20 Cores @ 2.5Ghz (50k Ghz)
16 Cores @ 3.7Ghz (59.2k Ghz)
0
LVL 47

Author Comment

by:Philip Elder
Microsoft used to have a set of values for VM counts depending on processor core count and GHz. Those recommendations have essentially been sidelined due to the fact that CPU is pretty much not the bottleneck anymore.

That being said, we go for GHz before core count as a rule because it's just that much faster to get the smaller vCPU count VM's threads through the CPU pipeline.

And finally, a wide core count would indeed be needed for multi-threaded applications like SQL to get through the pipeline as soon and as wide as possible.
0
In previous parts of this Nano Server deployment series, we learned how to create, deploy and configure Nano Server as a Hyper-V host. In this part, we will look for a clustering option. We will create a Hyper-V cluster of 3 Nano Server host nodes with Storage Spaces Direct on it.
1
Previously, on our Nano Server Deployment series, we've created a new nano server image and deployed it on a physical server in part 2. Now we will go through configuration.
0
Optimized for private cloud infrastructures and datacenters, Nano Server is minimalistic, yet super-efficient, OS for services such as Hyper-V and Hyper-V cluster. Learn how you can easily deploy Nano Server and unlock its power!
0
Ransomware is a malware that is again in the list of security concerns. Not only for companies, but also for Government security and even at personal use. IT departments should be aware and have the right knowledge to how to fight it.
1
In this article, I am going to show you how to simulate a multi-site Lab environment on a single Hyper-V host. I use this method successfully in my own lab to simulate three fully routed global AD Sites on a Windows 10 Hyper-V host.
1

Expert Comment

by:PriteshW
Good Article, setup on my lab and works well.
0
Veeam Backup & Replication has added a new integration – Veeam Backup for Microsoft Office 365.  In this blog, we will discuss how you can benefit from Office 365 email backup with the Veeam’s new product and try to shed some light on the needs and use cases of email backups.
2
Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
0
Know what services you can and cannot, should and should not combine on your server.
3
Why should I virtualize? It’s a question that’s asked often enough. My response is usually “Why SHOULDN’T you virtualize?”
10
First I will try to share a design of a Veeam Backup Infrastructure without Direct NFS Access backup.

Veeam-Backup-no-NFS.jpg
Note: Direct NFS Access backup transport mechanism is only available in Veeam v9

In above I try to design the Veeam Backup flow between iSCSI vs NFS.

In this case we did not had the proper configuration so that Direct NFS Access backup transport mechanism could work.

In this case we have a Veeam Backup Server and a Veeam Backup proxy.

Actual Veeam Backup Infrastructure:

192.100.27.x is iSCSI subnet - vLAN 56
192.128.23.x is the NFS Subnet vLAN 55

192.168.6.x(vLAN 25) is Management subnet. Used by Veeam Backup Server, vCenter and most of our ESXi hosts. But we still have some ESXi hosts that use our old management subnet 192.168.68.x
This is why we build a new Proxy with this subnet 192.68.68.x(vLAN 29)

Veeam Server I have(physical server):

1 interface(is 2 with NIC Teaming) for 192.168.6.x for Management Network.
1 Interface(also 2 with NIC Teaming) for 192.168.27.x using iSCSI initiator for the iSCSI connections.

Veeam Proxy(Virtual Machine):
1 interface with 192.168.68.x (vLAN 29) for Management Network.

This was the initial configuration and where Veeam Backup Server and Proxy never use the Direct NFS Access backup transport mechanism. All backups were running always with the option [nbd] for network block device (or network) mode, [hotadd] for virtual appliance mode.

Future Veeam Backup Infrastructure:
2
LVL 25

Author Comment

by:Luciano Patrão
Hi,

Mounting NFS in a Windows Server is outside of Veeam. Is not Veeam related task.

This is just adding/mounting a NFS Share into a Windows Server. That you should configure in your NAS and then mount in the Windows. Then you can use as a Veeam Backup Repository
0
LVL 25

Author Comment

by:Luciano Patrão
Hi,

I did also change both Designs, hope now have a better quality.
0
Using the Hyper-V Manager requires administrator rights. This guide shows how to add shortcuts and Start Screen tiles for normal users to quickly connect to local virtual machines rather than using the otherwise recommended Remote Desktop connection.
0

Expert Comment

by:Curtis Booker
The Best I've heard it put yet

Thanks a bunch
0
LVL 61

Author Comment

by:Gustav Brock
Thanks Andrew!
0
The following article is comprised of the pearls we have garnered deploying virtualization solutions since Virtual Server 2005 and subsequent 2008 RTM+ Hyper-V in standalone and clustered environments.
17
Few best practices specific to Network Configurations to be considered while deploying a Hyper-V infrastructure. It may not be the full list, but this could be a base line.


1. Dedicated Network

Always consider dedicated network/VLAN for Hyper-V data, CSV, Live Migration and Management.

Hyper-V Data - The NIC which will be allocated with the Hyper-V Virtual Switch and will be used by the VMs to route network traffic. Priority should be give to have dedicated network interface for Hyper-V Data.

CSV - Its good to have a dedicated interface for CSV traffic. This will be really a life saver if one of the node loose the connectivity to the storage. I had an experience where all cluster nodes except one lost the connectivity to the storage and all the VMs on the problematic nodes where have CSV on IO Redirected mode which was in fact using my CSV Network. This could be an idle mostly, however its like a health insurance - very much valuable when the accident happens.

Live Migration - This will be used only while Live Migration happens. As we have more bandwidth, the live migration can complete more faster. In short, this network will be used to transfer the Virtual Machine memory and state.

Management - Obviously, Need to RDP or access the server through remoting which needs network connectivity.


2. Bios/Firmware/Drivers

It is also very critical to make sure that the server BIOS and Firmware is updated with the …
4
LVL 47

Expert Comment

by:Philip Elder
I'm not sure what "dedicate an interface" means?

Philip
0

Hyper-V

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.