WEBVTT

00:05.580 --> 00:11.580
Server and network virtualization have been with us for quite a while now but I still run across people

00:11.580 --> 00:13.320
that are new to the idea.

00:13.590 --> 00:20.850
The basic concept is this a very low level application is installed on a server and it makes an inventory

00:20.850 --> 00:29.790
of physical hardware to assess how that hardware can be offered up to simulate multiple isolated machines.

00:29.790 --> 00:36.360
It can then assign virtual processors and portions of physical RAM as well as simulated network and

00:36.360 --> 00:41.430
storage controllers and bundle all these resources together in a single file.

00:41.430 --> 00:43.670
That is the virtual machine.

00:43.980 --> 00:49.070
Then one or more files are created that emulate hard drives.

00:49.080 --> 00:56.400
This allows you to open up a virtual machine consisting of only two or three files one representing

00:56.400 --> 01:03.010
the resources available and one or more representing the hard drives that store the data.

01:03.020 --> 01:09.860
This will allow you to more completely utilize all of the hardware available in high power servers and

01:09.860 --> 01:11.350
configured correctly.

01:11.480 --> 01:16.100
It can allow you to keep a server online even when some hardware issues may occur.

01:18.190 --> 01:24.800
There are several major players in the virtualization space each with their own strengths and weaknesses.

01:24.910 --> 01:33.180
Hyper V is Microsoft's virtualization platform and it's been around since Windows Server 2008 and on

01:33.180 --> 01:39.980
professional and enterprise workstations since Windows 8 and some of the features that we've already

01:39.980 --> 01:45.920
discussed have had an impact on hyper v on Windows 20 19 servers.

01:46.040 --> 01:53.600
The addition of data duplication in our CFS means virtual hard drives can now be stored on those volumes

01:54.020 --> 02:00.090
in a way that is not only faster and more resilient but now also more efficient as well.

02:00.730 --> 02:07.630
The improvements made to storage replica and storage spaces direct allow separate physical hosts to

02:07.630 --> 02:14.470
maintain synchronized copies of the virtual hard drive which can allow for zero downtime even if an

02:14.470 --> 02:22.150
entire datacenter goes dark unexpectedly but hyper v does have a few limitations more so in earlier

02:22.150 --> 02:25.230
releases on Windows workstations.

02:25.360 --> 02:31.540
The virtualization environment has created some conflicts when watching high resolution video through

02:31.540 --> 02:34.300
common third party software.

02:34.310 --> 02:41.540
This is still the case on current versions but that shouldn't be a problem when configuring a server.

02:41.550 --> 02:49.110
The biggest limitation was that hyper v was designed to host Windows servers and had little consideration

02:49.110 --> 02:50.920
for anything else.

02:51.090 --> 02:57.210
The virtualize hardware was easy enough to understand but none of the features that make servers resilient

02:57.270 --> 03:04.140
and protected worked on Linux environments virtualizing Mac environments is still a challenge because

03:04.140 --> 03:06.600
of the way Apple licenses their product.

03:06.600 --> 03:09.050
But Linux is a different story.

03:09.060 --> 03:16.590
Linux servers are growing in popularity and in Windows Server 20 19 Microsoft has made some noteworthy

03:16.590 --> 03:25.090
steps to accommodate Linux guest machines on hyper v hosts one of the features previously not available

03:25.090 --> 03:32.890
to Linux guest machines was the server 2016 feature of shielded virtual machines and the host Guardian

03:32.890 --> 03:34.000
server.

03:34.000 --> 03:39.430
Going forward we're going to take a look at how that's been expanded to include this new market.