WEBVTT
00:00:03.070 --> 00:00:05.580
[Music].
00:00:15.540 --> 00:00:17.950
>> I think my mic is on now.
00:00:18.290 --> 00:00:20.090
>> You think so?
>> Ouch.
00:00:21.660 --> 00:00:23.830
If you leave the room, make sure
you remic it.
00:00:25.000 --> 00:00:26.430
Is this good? Are you mic'ed?
00:00:26.490 --> 00:00:27.880
I don't know, talk to the producer.
00:00:29.280 --> 00:00:30.470
Now you're screwing me up.
00:00:30.520 --> 00:00:35.280
So welcome back to the hilarity
that is 417. Producer, can you
00:00:35.330 --> 00:00:38.000
verify that both of our mics are
on. We're good. We're good?
00:00:38.050 --> 00:00:39.440
Thank you. We got the thumbs up sign.
00:00:40.020 --> 00:00:43.500
To the audience that's in the room,
which is the producer, they
00:00:43.550 --> 00:00:47.240
can hear us, the online people can't
hear us. We are coming back
00:00:47.290 --> 00:00:49.990
from the last module talking about
Hyper-V and now we're talking
00:00:50.040 --> 00:00:52.330
about Hyper-V in a clustered environment,
that highly available
00:00:52.380 --> 00:00:54.310
environment, so really cool stuff.
00:00:55.170 --> 00:00:57.700
I need to get my other producer
to make sure that I've got my
00:00:57.750 --> 00:00:58.310
timer on.
00:00:58.360 --> 00:01:00.070
>> I've got your timer on here.
00:01:00.120 --> 00:01:00.790
>> The timer is on your machine?
00:01:00.840 --> 00:01:01.540
>> On the other machine,
good, good.
00:01:01.590 --> 00:01:02.720
>> We're going to
go for an hour.
00:01:02.770 --> 00:01:05.150
>> The reason why I'm saying I need
the timer on is because I
00:01:05.200 --> 00:01:09.100
could literally talk about Hyper-V,
high availability of Hyper-V
00:01:09.150 --> 00:01:11.750
and all the nuances around virtualization
and that sort of stuff
00:01:11.800 --> 00:01:12.500
for hours.
00:01:13.240 --> 00:01:13.890
I'm trying to respect...
00:01:13.940 --> 00:01:15.220
>> As we saw in the other
last module.
00:01:15.270 --> 00:01:19.070
>> I'm trying to respect the attendees
time to make it so that
00:01:19.120 --> 00:01:23.690
we're keeping this tight and focused,
which is a hard thing for
00:01:23.740 --> 00:01:27.230
us today for some reason, focus is
lacking right now. This module,
00:01:27.280 --> 00:01:27.610
if you didn't...
00:01:27.660 --> 00:01:27.730
>> What?
00:01:27.780 --> 00:01:28.530
>> This module is...
00:01:29.590 --> 00:01:33.180
this module is all about how to
implement failover clustering
00:01:33.230 --> 00:01:36.820
with Hyper-V. Now because as we
saw in the last module Hyper-V,
00:01:36.870 --> 00:01:40.760
you can now use SMB as one of your
storage locations, as opposed
00:01:40.810 --> 00:01:43.460
to using a cluster, it opens up
a new realm of possibilities
00:01:43.510 --> 00:01:45.790
for high availability, so we'll
touch on that at the end.
00:01:45.840 --> 00:01:48.470
And I'm also going to talk about some
cool stuff for SaaS recovery
00:01:48.520 --> 00:01:51.430
with replica broker and how that works,
so neat, neat stuff that's
00:01:51.480 --> 00:01:55.030
in there for the next ones coming
up. So again this is module
00:01:55.080 --> 00:01:57.750
nine of a 12 module course that
we're looking at right now.
00:01:57.800 --> 00:01:59.930
And this one is specifically for
working with failover clustering
00:01:59.980 --> 00:02:03.040
with Hyper-V. So far, so good, we're
on track and ready to go,
00:02:03.090 --> 00:02:03.600
my friend.
00:02:03.650 --> 00:02:04.460
>> All righty.
00:02:05.080 --> 00:02:08.880
>> So first off, clustering, what
does it do? It gives you the
00:02:08.930 --> 00:02:11.520
ability to have service or workloads
available in a highly available
00:02:11.570 --> 00:02:13.580
fashion, so it only makes sense
that you would make it so that
00:02:13.630 --> 00:02:16.450
you could have a Hyper-V workload
available in highly available
00:02:16.500 --> 00:02:19.870
fashion, obviously. So yes, we'll
talk about how to set that
00:02:19.920 --> 00:02:23.480
up, how to implement Hyper-V virtual
machines on failover clusters,
00:02:23.530 --> 00:02:25.240
it's slightly different if you haven't
worked with them before.
00:02:25.290 --> 00:02:28.660
Like if you are used to working
with just a Hyper-V manager to
00:02:28.710 --> 00:02:31.020
make your machines on a single box
and work with it on a single
00:02:31.070 --> 00:02:33.840
box, then that's one way of looking
at them, you actually have
00:02:33.890 --> 00:02:36.550
slight nuances or changes you have
to worry about when you are
00:02:36.600 --> 00:02:39.300
using a failover cluster for how to
be able to make these guys work.
00:02:39.980 --> 00:02:43.540
How to have some level of movement
with your Hyper-V machines,
00:02:43.810 --> 00:02:48.120
where we talk about the old way
of moving machines, the new way
00:02:48.170 --> 00:02:50.750
of moving machines and the really
cool new way of moving machines
00:02:50.800 --> 00:02:54.210
and storage all around between
your different systems, very,
00:02:54.260 --> 00:02:56.200
very cool stuff. I'll be able to
show you the stuff related to
00:02:56.250 --> 00:02:58.610
the clustering side of things because
current setup of the hardware
00:02:58.660 --> 00:03:00.930
that we have and finally how are
you going to be able to go off
00:03:00.980 --> 00:03:02.140
and manage your systems?
00:03:03.240 --> 00:03:07.000
So what are your choices for making
your workload virtual machine
00:03:07.050 --> 00:03:11.030
highly available? It comes down to
really three things and honestly
00:03:11.080 --> 00:03:13.580
we're only going to be covering
one of those three things in
00:03:13.630 --> 00:03:15.700
this entire session, which is the
first one, host clustering
00:03:15.750 --> 00:03:19.710
because that's where the physical
hosts in multi-node cluster
00:03:19.760 --> 00:03:23.760
are looking after those workloads
for Hyper-V. Glust... glust?
00:03:23.810 --> 00:03:28.750
Glust. Guest clustering. Gust clustering
is where your virtual
00:03:28.800 --> 00:03:32.940
machine guests are the ones that
are using the cluster node and
00:03:32.990 --> 00:03:36.840
the clustering technology, that's
the one that you can do yourself
00:03:36.890 --> 00:03:41.710
on a single individual lab system
environment or even in production
00:03:41.760 --> 00:03:45.550
environment, if you wanted to,
where all the guest clustering
00:03:45.600 --> 00:03:48.500
components or all the clustering
components are all installed
00:03:48.550 --> 00:03:54.310
on the VMs themselves. So for instance,
your iSCSI target would
00:03:54.360 --> 00:03:58.600
be VM running the ice iSCSI target
service running Server 2012.
00:03:58.650 --> 00:04:03.990
Your iSCSI initiators are your
two boxes. They are running oz
00:04:04.040 --> 00:04:06.650
guest on server 2012 and they are
going to initiate and talk
00:04:06.700 --> 00:04:10.160
to that iSCSI target. You then are
able to establish a cluster.
00:04:10.210 --> 00:04:14.090
You obviously can't put Hyper-V
inside a Hyper-V to be able to
00:04:14.140 --> 00:04:14.620
run it.
00:04:14.670 --> 00:04:15.380
>> Why not?
00:04:15.430 --> 00:04:17.910
>> But you can at least make a cluster
inside that virtualized
00:04:17.960 --> 00:04:20.340
environment with no hardware whatsoever
all in a single box if
00:04:20.390 --> 00:04:22.630
you want to play around with
it to be able to do it.
00:04:22.680 --> 00:04:25.330
Basically iSCSI or the new fiber
channel passthrough, if you
00:04:25.380 --> 00:04:28.570
wanted to, and it will be network
load balancing, which is also
00:04:28.620 --> 00:04:32.530
an option, basically for web workloads
to be able to have multiple
00:04:32.920 --> 00:04:36.220
web farms up and running, tables
to service those requests that
00:04:36.270 --> 00:04:39.290
come in. We're not going to be
talking about guest clustering
00:04:39.340 --> 00:04:42.190
because we're going to focus on the
main one, which is host clustering.
00:04:42.240 --> 00:04:44.680
>> I'm just picturing that Hyper-V
inside a Hyper-V is kind of
00:04:44.730 --> 00:04:47.130
like when you take a video camera and
you point it at the monitor...
00:04:47.180 --> 00:04:48.770
>> Or the mirror and it just...
00:04:48.820 --> 00:04:50.050
>> Or at the mirror and
you just get that.
00:04:50.100 --> 00:04:52.780
>> What was that movie about waking
up and dreaming and dream
00:04:52.830 --> 00:04:55.680
burglar dreaming and dreaming
"Inception," is that it?
00:04:55.730 --> 00:04:56.100
Something like that.
00:04:56.150 --> 00:04:57.970
>> I think you lived that, I
don't think that was...
00:04:58.020 --> 00:05:01.380
>> Could be. Failover
clustering.
00:05:01.430 --> 00:05:03.530
>> Oh, when the guy is on the train, I know
what you are talking about. Yeah.
00:05:03.580 --> 00:05:05.970
>> Yeah. That's a different
movie where the guy...
00:05:06.020 --> 00:05:07.810
>> We're not going to
talk about movies.
00:05:07.860 --> 00:05:09.410
>> You have limited time here.
00:05:10.170 --> 00:05:13.240
>> Node 1 and node 2, basically,
once again, they've got this
00:05:13.290 --> 00:05:16.920
cluster in the back end, sort of cluster
storage, they have dedicated
00:05:16.970 --> 00:05:21.590
bus of network transport to be able
to get access to that particular
00:05:21.640 --> 00:05:25.130
storage area and basically Hyper-V
is going to be running on
00:05:25.180 --> 00:05:28.040
those individual nodes. That clustered
storage is going to be
00:05:28.090 --> 00:05:32.260
known as clustered shared volume
or CSV, specifically set up
00:05:32.310 --> 00:05:35.200
as part of the failover cluster
manager to be able to make it
00:05:35.250 --> 00:05:38.050
so that the both nodes can actively
have access to that one piece
00:05:38.100 --> 00:05:42.240
of storage and then can then
go and share the processes.
00:05:43.020 --> 00:05:46.280
They can move the processes that
are the actual workloads back
00:05:46.330 --> 00:05:50.560
and forth amongst themselves as required
between the different systems.
00:05:51.460 --> 00:05:55.160
The idea, as well, is you also happen
to have dedicated network
00:05:55.210 --> 00:05:57.150
that is where you are going to be
having your heartbeats going
00:05:57.200 --> 00:06:00.740
back and forth between your different
nodes. The default heartbeat
00:06:00.790 --> 00:06:03.570
is going through basically at a second
or a thousand milliseconds.
00:06:03.620 --> 00:06:07.460
If it by default surpasses five
milliseconds or five seconds,
00:06:07.510 --> 00:06:10.860
which is 5000 milliseconds, it's
going to basically be in a drop
00:06:10.910 --> 00:06:13.230
state and basically have to go
in and transfer that workload
00:06:13.280 --> 00:06:14.710
over to node number 2.
00:06:15.670 --> 00:06:17.900
And there goes the machine. It's
all happy, restarts on the other
00:06:17.950 --> 00:06:20.000
side and you're all good to go.
This is unplanned failover when
00:06:20.050 --> 00:06:20.980
that happens.
00:06:21.720 --> 00:06:24.460
Once that other box is back up
again, you can do a controlled
00:06:24.510 --> 00:06:27.670
migration back to that other side
when that node happens to be
00:06:27.720 --> 00:06:31.020
back up and running again. So simple
sort of stuff. Here is another
00:06:31.070 --> 00:06:36.030
abrata that I found that is interesting.
Again, this course ware
00:06:36.080 --> 00:06:39.910
and the virtual machine demos that
we're showing you are actually
00:06:39.960 --> 00:06:42.280
based on the release candidate because
the timing when this mock
00:06:42.330 --> 00:06:45.200
course was actually created. At
the time we were only publicly
00:06:45.250 --> 00:06:51.570
speaking about a supported 4000 virtual
guests inside a 64-node cluster.
00:06:51.620 --> 00:06:55.720
We've now upped that and will officially
support as of the release
00:06:55.970 --> 00:06:59.160
to manufacturing and the launch.
We did our big announcement
00:06:59.210 --> 00:07:04.480
of 8000 virtual machines per cluster
of 64 nodes that's up there.
00:07:04.530 --> 00:07:07.540
So big support for number of virtual
machines that are increased.
00:07:07.590 --> 00:07:11.970
Now I don't know how this translates
to an exam environment and
00:07:12.020 --> 00:07:16.210
we're not talking specifically about
exams, but is the exam based
00:07:16.260 --> 00:07:19.820
on the RTM or based on the code
that it was written on, Mr.
00:07:20.850 --> 00:07:21.480
MCT?
00:07:21.530 --> 00:07:22.370
>> Um, yes.
00:07:23.340 --> 00:07:26.250
No, that is the answer and that
has been the answer and that
00:07:26.300 --> 00:07:29.800
is the typical question that
I get at all times.
00:07:30.340 --> 00:07:32.420
Same question comes out any time
a service pack comes out.
00:07:32.470 --> 00:07:35.400
Same question comes up every
time R2 comes out.
00:07:35.450 --> 00:07:37.730
>> My philosophy has always been
is you have you to take it from
00:07:37.780 --> 00:07:41.490
the perspective of when the exam
was written and find out...
00:07:41.540 --> 00:07:47.100
yeah, always know the latest stuff,
but however, there is a revision
00:07:47.150 --> 00:07:49.650
cycle and a lag that happens between
when lay stuff comes out
00:07:49.700 --> 00:07:52.260
and when the exams get revised,
as well, and...
00:07:52.310 --> 00:07:54.850
>> Here is what I can tell you my
experience has been. When you
00:07:54.900 --> 00:07:57.160
are going to get down to a bullet
point like that, that talks
00:07:57.210 --> 00:08:00.780
about 4000 versus 8000, it's probably
not going to come up, you're
00:08:00.830 --> 00:08:04.050
usually not going to get something
that is that specific to where
00:08:04.100 --> 00:08:07.130
you are going to be fooled
based upon RC and RTM.
00:08:08.400 --> 00:08:10.750
Microsoft Learning
is aware that...
00:08:10.800 --> 00:08:11.450
>> Numbers change.
00:08:11.500 --> 00:08:14.970
>> That happens and so therefore they
make sure to word a question...
00:08:15.020 --> 00:08:17.710
they want to know that you know how
to implement the technology,
00:08:17.760 --> 00:08:20.290
you want to know what the technology
is. You're not going to
00:08:20.340 --> 00:08:21.850
have to know 4000 versus 8000.
00:08:21.900 --> 00:08:22.180
>> Ok, good.
00:08:22.230 --> 00:08:25.290
>> Now that said, everybody... you
know, everyone just pound on
00:08:25.340 --> 00:08:28.110
me when you get that question
4000 versus 8000.
00:08:28.160 --> 00:08:32.780
>> You got it. His twitter handle
at sign underscore Ed.
00:08:32.830 --> 00:08:33.860
>> Good thing I don't
use Twitter.
00:08:33.910 --> 00:08:36.920
>> You got it. Send him an e-mail.
His e-mail is not up there,
00:08:36.970 --> 00:08:37.360
darn it.
00:08:37.410 --> 00:08:39.460
>> No, Facebook train signal.
00:08:39.510 --> 00:08:43.400
>> You got it. You can obviously
go off with failover clustering
00:08:43.450 --> 00:08:46.110
and go off and select multi-virtual...
multiple virtual machine
00:08:46.160 --> 00:08:49.420
for live migration. In the past,
you basically did sequentially,
00:08:49.470 --> 00:08:51.600
one machine would do the live migration,
finish and the next
00:08:51.650 --> 00:08:53.800
machine did live migration, finish.
Next machine did a live migration
00:08:53.850 --> 00:08:58.010
and finish. Now basically it goes in
batches and can handle multiple
00:08:58.060 --> 00:09:00.580
VMs at the same time. You are basically
limited by your hardware
00:09:00.860 --> 00:09:03.640
throughput to be able to do it.
You also have the ability to
00:09:03.690 --> 00:09:06.820
set a priority for the machines
during bootup and restarting
00:09:06.870 --> 00:09:10.220
so that they know these guys come
up first, these guys come up
00:09:10.270 --> 00:09:13.320
later with the delay process that's
in there, cluster shared
00:09:13.370 --> 00:09:16.600
volumes have improvement from the scaleability
perspective, dynamically
00:09:17.130 --> 00:09:20.160
reclaiming case perspective and
also the ability to now support
00:09:20.210 --> 00:09:23.460
bit lockering of those volumes for
added security layer, which
00:09:23.510 --> 00:09:24.340
is quite good.
00:09:25.080 --> 00:09:28.180
You can have more insight into what's
actually going on inside
00:09:28.230 --> 00:09:31.460
the machines with app monitoring
and finally you obviously want
00:09:31.510 --> 00:09:34.760
to be able to have the option to
not exclusively just use cluster
00:09:34.810 --> 00:09:38.270
technology, you also can now use
the highly available SMB file
00:09:38.320 --> 00:09:40.000
share and that sort of stuff,
how that works.
00:09:40.050 --> 00:09:42.620
>> I just like how you turn
bit locker into a verb.
00:09:42.670 --> 00:09:44.460
>> Bit lockered? What
do you mean?
00:09:44.510 --> 00:09:45.260
>> Bit lockering.
00:09:45.310 --> 00:09:47.580
>> Bit lockering, I guess
that is true.
00:09:47.630 --> 00:09:49.310
>> We are bit lockering.
00:09:50.010 --> 00:09:54.540
>> Um, the best practices for implementing
Hyper-V on a virtualized
00:09:54.590 --> 00:09:57.690
environment basically server
2012 is a Hyper-V host.
00:09:59.220 --> 00:10:01.620
Questions about can you do upgrades,
what is the upgrade process,
00:10:01.670 --> 00:10:04.210
they are being handled inside the
Q&A area, but yes, you obviously
00:10:04.260 --> 00:10:07.900
can go in and start to worry about
your upgrade process from
00:10:07.950 --> 00:10:11.820
service 2 up to server 2012 for
Hyper-V. You're going to want
00:10:11.870 --> 00:10:14.040
to plan for your failover scenarios
and this is something that
00:10:14.090 --> 00:10:15.990
can tend to be overlooked by someone
that's not familiar with
00:10:16.040 --> 00:10:20.440
clustering, where speck out the
hardware for a large number of
00:10:20.490 --> 00:10:23.890
systems to be running and they'll
stage it so that they have
00:10:23.940 --> 00:10:26.760
the appropriate resources spread
across the load and everything
00:10:26.810 --> 00:10:30.540
is being nicely used from a resource
perspective, but then when
00:10:30.590 --> 00:10:34.500
a failover occurs of one or more
nodes, that workload that is
00:10:34.550 --> 00:10:38.460
on those servers has to move to
one of the other guys and that
00:10:38.510 --> 00:10:40.760
other guy it's moving to has to
have the head room to be able
00:10:40.810 --> 00:10:43.220
to support them, otherwise you are going
to end up with problems, right?
00:10:43.270 --> 00:10:46.070
Machines won't be able to start.
So obviously you got to build
00:10:46.120 --> 00:10:50.440
for failure and make sure that
you have the ability to handle
00:10:50.490 --> 00:10:54.440
the reload, the reload, the resources
on the load of the servers
00:10:54.490 --> 00:10:57.380
when a failover happens to occur.
So plan for failovers, test
00:10:57.430 --> 00:10:59.300
those failovers, make sure they're
all good. Same thing with
00:10:59.350 --> 00:11:03.340
storage overall for overall size
and location of storage.
00:11:03.990 --> 00:11:08.000
We already talked about deploying Hyper-V
host and standard management
00:11:08.050 --> 00:11:11.390
practices, so I'm actually going
to drop out here and go to a
00:11:11.440 --> 00:11:13.210
little bit of a demo in just a
moment here where I'm going to
00:11:13.260 --> 00:11:15.270
show you the Hyper-V cluster manager.
00:11:15.820 --> 00:11:19.340
And show you a little bit about
this little cluster I'm using
00:11:19.390 --> 00:11:21.080
in the back end and maybe
it will make this work.
00:11:21.900 --> 00:11:27.630
So as I switch off and over here
to this guy to see where he's
00:11:27.680 --> 00:11:29.670
at, there we go. So tell this
00:11:31.720 --> 00:11:33.090
demo machine for an sec.
00:11:34.530 --> 00:11:39.230
We've got in this case, I am looking
at the failover cluster
00:11:39.280 --> 00:11:44.180
manager and I've got my cluster that
was created here, MSTE-TLU,
00:11:45.000 --> 00:11:47.790
that was created. It's up and running.
I do have again, some
00:11:47.840 --> 00:11:50.120
warnings which are all and errors
which are all related simply
00:11:50.170 --> 00:11:52.050
to network configuration,
nothing fancy.
00:11:52.790 --> 00:11:56.240
And then we have in this case,
two individual nodes, node 1,
00:11:56.290 --> 00:11:58.600
node number 2, they were all running
and happy just fine.
00:11:58.650 --> 00:12:02.010
This is actually workload is node
number 2, it's all still good.
00:12:02.060 --> 00:12:05.060
We talked about migration of workloads
and migrations of systems.
00:12:05.110 --> 00:12:08.410
If I just grab these guys over here,
select multiple, be I say
00:12:08.460 --> 00:12:12.890
move with a live migration to select
the node. I can move them
00:12:12.940 --> 00:12:15.450
all over to number 2 and you can
see that obviously it's going
00:12:15.500 --> 00:12:18.770
to migrate the harder ones, which
are the ones that are currently
00:12:18.820 --> 00:12:22.240
running and everything else will
migrate over to node number
00:12:22.290 --> 00:12:25.410
2 and if I take a look at that
copy process is taking place,
00:12:25.460 --> 00:12:26.520
this is basically
00:12:27.740 --> 00:12:29.690
checking the memory pages that
are running, seeing there has
00:12:29.740 --> 00:12:32.610
not been any changes, recreating
the machine configuration on
00:12:32.660 --> 00:12:35.630
the other side of the node, making
sure the drives are in sync
00:12:35.680 --> 00:12:39.530
and last possible moment it does the
last delta every page in code.
00:12:39.580 --> 00:12:45.190
This does it all within the TCP window,
which is basically a ping.
00:12:45.240 --> 00:12:47.880
It happens within a ping,
to be able to work.
00:12:48.490 --> 00:12:50.900
They're all now basically up and
running and good to go on the
00:12:50.950 --> 00:12:54.470
other side. I only have two that
are basically up and going on
00:12:54.520 --> 00:12:57.720
this side. The other guys were
not even running or active, so
00:12:57.770 --> 00:13:00.560
they didn't need to be live migrated.
They can be just moved.
00:13:00.610 --> 00:13:03.820
They are now continuing to run, everything
is good, nothing went
00:13:03.870 --> 00:13:06.160
down with those guys, they are
all happy, they are all fine.
00:13:06.210 --> 00:13:09.410
Those guys there are sitting there.
Interesting, I never even
00:13:09.460 --> 00:13:12.440
thought, I never realized, you can't
do a live migrate of machine
00:13:12.490 --> 00:13:13.100
turned off.
00:13:14.210 --> 00:13:15.550
>> It wouldn't be live then.
00:13:15.600 --> 00:13:18.250
>> I can do a move of it.
00:13:18.300 --> 00:13:20.150
>> That would be a
dead migration.
00:13:20.200 --> 00:13:22.230
>> I guess it's a dead migration.
I could do a storage migration,
00:13:22.280 --> 00:13:22.970
which is also new.
00:13:23.020 --> 00:13:28.070
But I've got those guys up and going, they're
all happy. Workload perspective.
00:13:28.120 --> 00:13:31.810
Now from a roles perspective, as
well, looking back at the entire
00:13:31.860 --> 00:13:34.230
list, you can now see that these
guys are running on node number
00:13:34.280 --> 00:13:38.120
2, these guys are still on node
number 1. If I wanted to go off
00:13:38.170 --> 00:13:43.380
into make a new machine with Hyper-V
cluster manager, similar
00:13:43.430 --> 00:13:46.030
to what you would do with regular
environment, I'm going to say
00:13:46.080 --> 00:13:49.580
any virtual machine, I'm going
to say target this guy on node
00:13:49.630 --> 00:13:51.850
number 2, just for the heck of it,
because it has resources available
00:13:51.900 --> 00:13:52.490
to them.
00:13:54.530 --> 00:13:58.730
The wizard pops up that you've seen before.
It gives me the name request.
00:13:58.780 --> 00:14:03.160
This is Rick's Demo Machine. I'm going
to store this in a different
00:14:03.210 --> 00:14:05.440
location and this is where it's
important to have that cluster
00:14:05.490 --> 00:14:08.870
shared reference volume because
I need to know the line and the
00:14:08.920 --> 00:14:11.220
drive volume has been mapped that
individual line if you want
00:14:11.270 --> 00:14:14.100
to use fiber channel (inaudible)
as an example. Instead because
00:14:14.150 --> 00:14:17.250
I'm using clustered shared volumes
I know that I simply need
00:14:17.300 --> 00:14:20.780
to go down and browse to my C drive
00:14:22.160 --> 00:14:25.380
or else I want to go back down here
to my C drive. There it is.
00:14:25.430 --> 00:14:29.340
Under Clustered Storage, volume number
1, I happen to have directory
00:14:29.390 --> 00:14:32.240
structure called VMs that I'm
throwing them in right now.
00:14:32.290 --> 00:14:35.860
Select that folder. This is going
to be the same reference on
00:14:35.910 --> 00:14:38.180
every single node of my cluster that
is using the cluster shared
00:14:38.230 --> 00:14:40.590
volumes, it's easy for me
to be able to find it.
00:14:41.260 --> 00:14:44.050
I'm going to say, use dynamic memory
for this virtual machine,
00:14:44.100 --> 00:14:47.790
start with 512. Finish off with
a network, these connected to,
00:14:48.440 --> 00:14:52.310
connectivity, here is the location
of the name of the file, location
00:14:52.360 --> 00:14:55.070
where that drive happens to be. Again,
this is that cluster shared
00:14:55.120 --> 00:14:56.670
volume that I created earlier.
00:14:57.460 --> 00:15:00.170
I'm just going to say, don't bother
operating system right now,
00:15:00.220 --> 00:15:03.550
go ahead and make that machine, configure
them, boom, it is there
00:15:03.600 --> 00:15:07.720
and done. This guy is now made
as a highly available resource
00:15:07.770 --> 00:15:11.050
and was now successfully set up.
I can live migrate him, move
00:15:11.100 --> 00:15:15.090
him and do anything I want to with
that individual box, all because
00:15:15.140 --> 00:15:18.720
of cluster manager. If I made a machine
outside of cluster manager,
00:15:18.770 --> 00:15:21.400
and I made it with the regular
hyper visor or Power Shell and
00:15:21.450 --> 00:15:24.770
it wasn't cluster aware because
the commands I was using and
00:15:24.820 --> 00:15:28.190
I didn't store it in the right
location, neat thing you could
00:15:28.240 --> 00:15:30.900
do is you can actually do an export
and import, if you will,
00:15:30.950 --> 00:15:34.440
of that system. So if I configure
my role, instead of doing a
00:15:34.490 --> 00:15:37.210
virtual machine, new machine, I
can actually say configure the
00:15:37.260 --> 00:15:43.860
role and then choose the role of a
Hyper-V workload virtual machine.
00:15:45.720 --> 00:15:48.490
And then actually will scan all the
nodes that are running right
00:15:48.540 --> 00:15:52.410
now, that are part of my cluster
and then choose which machine
00:15:52.460 --> 00:15:56.100
I can basically make available
to this environment. I'm going
00:15:56.150 --> 00:16:01.630
to say, test VM, bring it in and
bring it up to the individual
00:16:01.680 --> 00:16:04.670
system and now make it available
to my environment. It's going
00:16:04.720 --> 00:16:05.410
to say next.
00:16:05.980 --> 00:16:09.890
Bring it over, bring them up and
successful and done. I basically
00:16:09.940 --> 00:16:13.430
did a very quick export and import
on that new location to get
00:16:13.480 --> 00:16:15.810
that guy brought into as highly
available workload.
00:16:16.410 --> 00:16:19.450
There he is right there. My test
VM, very simple sort of stuff.
00:16:19.500 --> 00:16:21.500
Another thing that can come up,
which is rather interesting,
00:16:21.550 --> 00:16:26.550
with regards to working with this
environment is if I take a
00:16:26.600 --> 00:16:28.670
look at my Hyper-V manager
00:16:29.870 --> 00:16:35.170
for this one guy that said, non-HAVM,
I'm just going to go ahead
00:16:35.220 --> 00:16:36.910
and simply say shut this guy down.
00:16:39.940 --> 00:16:42.140
I'm going to look at the settings
on him just to see where I
00:16:42.190 --> 00:16:44.960
stored his location of files because
I forget where I put it.
00:16:45.880 --> 00:16:49.970
Hard drive currently is
on D drive, non-HAVMs.
00:16:50.600 --> 00:16:52.610
There we go. He's now there.
00:16:53.340 --> 00:16:56.790
I'm able to go in and this also will
show off the importing capabilities.
00:16:56.840 --> 00:17:02.240
If I choose my D drive VMs, there's
my non-HA machine, I'm not
00:17:02.290 --> 00:17:05.800
doing an export, just literally
doing a copy of this or a cut
00:17:05.850 --> 00:17:09.380
would be a better thing I guess I
should do and then I move them
00:17:09.430 --> 00:17:14.830
to my C drive clustered storage volume
1 and then drop them there.
00:17:20.590 --> 00:17:22.710
That's going to go ahead and take
a little time as it copies
00:17:22.760 --> 00:17:26.590
over 8 gigabytes worth of
data on that system.
00:17:27.100 --> 00:17:31.260
While that guy is copying, when he
is now inside the proper location
00:17:31.310 --> 00:17:35.210
of the cluster share volume between
those two Hyper-V nodes that
00:17:35.260 --> 00:17:38.530
are clustered, I can then do an
import and then simply point
00:17:38.580 --> 00:17:41.590
to him as my new import location
and then bring him inside my
00:17:41.640 --> 00:17:44.540
environment, which would then turn
him into a highly available
00:17:44.590 --> 00:17:47.940
system, too. So a couple of different
ways to make a machine
00:17:47.990 --> 00:17:51.560
highly available, natively through
wizard interface from the
00:17:51.610 --> 00:17:55.590
cluster manager, simply going in
and doing an import from the
00:17:55.640 --> 00:17:58.210
existing machines that are already
registered or even doing an
00:17:58.260 --> 00:18:00.460
import from looking at the local
drive to be able to bring it up.
00:18:00.510 --> 00:18:03.460
So simple sort of stuff to get him
all up and happy as long as
00:18:03.510 --> 00:18:06.940
he's in the right spot. You've got
access to those different systems.
00:18:07.640 --> 00:18:10.700
The cluster manager.
Something...
00:18:10.750 --> 00:18:13.230
>> I was just going to, before we
get too far, just real quick,
00:18:14.020 --> 00:18:17.690
you know couple things. One, you
know just to give everyone a
00:18:17.740 --> 00:18:20.020
break from this for just a second,
I thought I should point out,
00:18:20.700 --> 00:18:23.110
just for your sake, it is "Inception,"
and "Source Code," is
00:18:23.160 --> 00:18:23.970
the other movie, but
00:18:25.170 --> 00:18:27.070
a lot of people have
been asking about...
00:18:27.810 --> 00:18:28.950
this doesn't work as good.
00:18:29.000 --> 00:18:29.100
>> Nice.
00:18:29.150 --> 00:18:31.960
>> I didn't have good redundancy.
There are a lot of
00:18:33.460 --> 00:18:37.240
questions coming through because you
did bring up as far as testing.
00:18:37.730 --> 00:18:40.470
I just want to point out that later
on today at the end of the
00:18:40.520 --> 00:18:44.600
day, we are going to actually address
a little bit about the
00:18:44.650 --> 00:18:47.560
testing and some of what you can
do to help make sure that you
00:18:47.610 --> 00:18:50.380
can take this information and
be prepared for the test.
00:18:50.430 --> 00:18:55.260
>> Oh, you mean the...
the bonus section.
00:18:55.310 --> 00:18:57.060
>> Yes, so the bonus section,
is that better?
00:18:57.110 --> 00:18:59.870
>> Bonus section. There we go.
00:18:59.920 --> 00:19:02.230
>> So I just want to let everyone
know so we don't have to
00:19:03.570 --> 00:19:06.380
be flagging a lot of questions
about that and we're going to
00:19:06.430 --> 00:19:09.290
point you to some locations where you
can get those types of answers.
00:19:10.150 --> 00:19:13.610
All right, back to the awesome
clustering demo.
00:19:13.660 --> 00:19:15.400
>> You got it, man. I'm actually
going to switch back to slides
00:19:15.450 --> 00:19:16.080
for just a little bit.
00:19:16.130 --> 00:19:17.550
>> All right, back to slide text.
00:19:18.210 --> 00:19:22.080
>> Cluster nodes. Obviously for
Hyper-V clusters, they have to
00:19:22.130 --> 00:19:26.090
be physical machines, because you
can't do Hyper-V within Hyper-V.
00:19:26.910 --> 00:19:28.720
You are going to have to
basically identify...
00:19:28.770 --> 00:19:29.760
>> That would be "Inception." >> That
00:19:29.810 --> 00:19:30.950
would be "Inception." >> Okay.
00:19:31.000 --> 00:19:33.400
>> You would then want to go off
and basically identify which
00:19:33.450 --> 00:19:35.680
are my networks being used specifically
to support my cluster
00:19:35.730 --> 00:19:38.510
shared volume shared storage, which
is going to be set up for
00:19:38.560 --> 00:19:42.160
my virtual networks across my systems.
Making sure I have enough
00:19:42.210 --> 00:19:45.560
storage available and the type of
storage available and finally
00:19:45.610 --> 00:19:48.240
making my virtual machines highly
available on my systems.
00:19:49.060 --> 00:19:51.500
So hard requirements, basically make
sure you've got your server
00:19:51.550 --> 00:19:53.210
and hardware storage up and running.
Make sure you have your
00:19:53.260 --> 00:19:55.610
redundant network adapters and
storage adapters in place.
00:19:56.440 --> 00:19:59.600
Software requirements are set up
in such a fact that you have
00:19:59.650 --> 00:20:02.570
to have either standard or data center.
Again, there's no difference
00:20:02.620 --> 00:20:05.870
between the functional capabilities
between those two different
00:20:05.920 --> 00:20:09.230
systems and I also added in or the
Hyper-V server 2012 instance,
00:20:09.280 --> 00:20:11.300
as well, can be used
to set this up.
00:20:11.970 --> 00:20:14.490
You should have the same updates
and service back installed in
00:20:14.540 --> 00:20:18.390
the system and you either need to
be awful or all core install,
00:20:18.440 --> 00:20:20.560
you don't want to be mixing and matching
those individual requirements
00:20:20.610 --> 00:20:23.200
that are there. And finally, you're
going to want to make sure
00:20:23.250 --> 00:20:25.490
that you have all the proper addressing
set up, you know which
00:20:25.540 --> 00:20:27.660
cables are plugged into which switches,
you've got multiple pass
00:20:27.710 --> 00:20:31.690
if possible. You need to have DNS
up and running and domain running
00:20:31.740 --> 00:20:34.110
because if you forgot from the very
first section talking about
00:20:34.160 --> 00:20:37.320
clustering, we use active directory
as authentication mechanism
00:20:37.720 --> 00:20:39.720
between the different clusters to
be able to identify are they
00:20:39.770 --> 00:20:42.490
allowed to be part of the cluster
and can I manage them easily.
00:20:42.540 --> 00:20:46.400
And you have to have the ability
to administer the cluster, local
00:20:46.450 --> 00:20:50.330
admin rights on those cluster boxes
to be able to set that up.
00:20:50.380 --> 00:20:55.380
Physically setting up the systems
was the same as the setting
00:20:55.430 --> 00:20:58.530
up a cluster within the guest, which
I showed you in the first
00:20:58.580 --> 00:21:01.680
module today that we looked at,
which is module seven, so that
00:21:01.730 --> 00:21:07.070
was basically the same process of installing
the feature of clustering,
00:21:07.860 --> 00:21:10.680
making sure that you have shared
discs between the systems and
00:21:10.730 --> 00:21:14.960
then going into choose configure
the cluster, you simply add
00:21:15.010 --> 00:21:17.660
in the different nodes to be able
to get that guy up and happy
00:21:17.710 --> 00:21:20.180
and working and then after it's
created, you can tweak the type
00:21:20.230 --> 00:21:22.830
of quorum that you want to use.
It takes a default quorum, it
00:21:22.880 --> 00:21:23.550
goes up there.
00:21:23.600 --> 00:21:27.870
>> One thing real quick Rick, you said
you added in Hyper-V version,
00:21:28.460 --> 00:21:30.340
there are a number of questions
that have been coming through
00:21:30.390 --> 00:21:35.020
as far as what you can and can't do
specifically with that version.
00:21:35.070 --> 00:21:38.190
I know you... you've already pointed
out that those... that nodes
00:21:38.790 --> 00:21:42.630
or virtual machines from that
version can be clustered...
00:21:42.680 --> 00:21:43.470
>> Uh-huh.
00:21:43.520 --> 00:21:48.200
>> Can you do all of this strictly from
Windows Server 2012 Hyper-V?
00:21:48.250 --> 00:21:48.820
>> Yeah.
00:21:48.870 --> 00:21:50.360
>> Do you know?
00:21:50.410 --> 00:21:52.160
>> Yes, I do know.
00:21:52.870 --> 00:21:58.360
Hyper-V Server 2012, as I'll state
again, has a limitation where
00:21:58.410 --> 00:22:03.980
the only role that it can do is Hyper-V.
It can only virtualize,
00:22:04.030 --> 00:22:05.640
that is what you're licensed to
use, that is what you're able
00:22:05.690 --> 00:22:09.480
to do on that individual box. It's
able to be domain joined and
00:22:09.530 --> 00:22:12.470
because it is able to be domain joined
and because it is essentially
00:22:12.520 --> 00:22:17.350
the same capabilities of no hardware
restrictions and no other
00:22:17.400 --> 00:22:20.610
limitations placed on it from a
resource perspective, has the
00:22:20.660 --> 00:22:24.630
same capabilities to be a cluster,
be part of a 16-ounce cluster,
00:22:24.680 --> 00:22:28.680
you can have a 64-node cluster,
just of Hyper-V Server 2012,
00:22:28.700 --> 00:22:33.390
if you wanted to. The difference is
that there are no guest operating
00:22:33.440 --> 00:22:34.410
system licenses...
00:22:34.460 --> 00:22:34.620
>> Uh-huh.
00:22:34.670 --> 00:22:37.880
>> On that box whatsoever. You have
to basically procure your
00:22:37.930 --> 00:22:42.330
own licenses for it and for
the guest, that is...
00:22:42.380 --> 00:22:42.750
>> Uh-huh.
00:22:42.800 --> 00:22:50.420
>> And you manage it remotely, using
the tool, which is Server
00:22:50.470 --> 00:22:52.930
Manager to be able to manage it remotely.
Once you have S configed
00:22:52.980 --> 00:22:55.960
in there to make it part of the same
network and make it all happy.
00:22:56.010 --> 00:22:59.090
There are third party software,
there is third-party software
00:22:59.140 --> 00:23:02.220
out there that will allow you to
go ahead and manage it with
00:23:02.270 --> 00:23:05.180
an interface basically like a web
app that runs on the individual
00:23:05.230 --> 00:23:08.480
box, 59 software, I think makes
one, it's actually quite good.
00:23:08.980 --> 00:23:10.280
I've used that in the past.
00:23:10.810 --> 00:23:14.990
Someone was asking how you can manage
it with a standalone workgroup
00:23:15.040 --> 00:23:19.020
environment with Windows 8 machine.
A lot of little fun things
00:23:19.070 --> 00:23:21.150
you have to do to make it work in
workgroup environment, to be
00:23:21.200 --> 00:23:24.450
remotely managed. It is possible,
as well, some good log articles
00:23:24.500 --> 00:23:30.510
on how to do that. And essentially
it's a viable option.
00:23:30.560 --> 00:23:34.340
However, it's not designed primarily
for most enterprise customers
00:23:34.390 --> 00:23:36.120
that are going to be working because
they're going to be licensing
00:23:36.170 --> 00:23:39.020
and using standard and data center
additions that are out there.
00:23:40.930 --> 00:23:44.140
Back to slides for implementing
Hyper-V virtual machines on a
00:23:44.190 --> 00:23:46.790
failover cluster, you install it,
you configure shared storage,
00:23:46.840 --> 00:23:49.720
you install Hyper-V in failover clustering,
validate the cluster.
00:23:49.770 --> 00:23:52.260
Those are the exact same steps you
saw earlier. You create the
00:23:52.310 --> 00:23:55.770
cluster, as well, same steps. You
then go in and you basically
00:23:55.820 --> 00:23:58.200
create a virtual machine on one
of the cluster nodes, like I
00:23:58.250 --> 00:24:03.610
just showed you how to make one,
by saying new role and virtual
00:24:03.660 --> 00:24:06.670
machine is the role. And then that
becomes the location for how
00:24:06.720 --> 00:24:08.470
to make the virtual machine
highly available.
00:24:09.570 --> 00:24:12.590
The setup is great for the setup
that we have working right now
00:24:12.640 --> 00:24:13.830
to get this guy up.
00:24:15.030 --> 00:24:18.120
The one thing I haven't talked about
just yet is the configuring
00:24:18.170 --> 00:24:20.530
of the cluster shared volumes,
literally it's something that
00:24:20.580 --> 00:24:24.860
you simply have to turn on inside
the cluster manager. The cluster
00:24:24.910 --> 00:24:25.830
failover manager.
00:24:26.420 --> 00:24:29.980
The CSV, you then identify which
of your storage discs will be
00:24:30.030 --> 00:24:34.620
used for the CSV. Once you've done
that, basically you'll be
00:24:34.670 --> 00:24:38.470
referring to that clustered shared
volume always as the location
00:24:38.520 --> 00:24:42.170
of "C: Backslash cluster storage
slash volume 1" or whatever
00:24:42.220 --> 00:24:45.570
the volume happens to be and it
will be the same for all of the
00:24:45.620 --> 00:24:48.740
nodes of your cluster for
that exact same location.
00:24:49.360 --> 00:24:52.190
It's more efficient using disc space because
you're not hundred restricted.
00:24:53.940 --> 00:24:56.640
And there is no special hardware
required to be able to go off
00:24:56.690 --> 00:24:59.840
and have that guy running and basically
to implement it, you
00:24:59.890 --> 00:25:02.810
create and format the volume on shared
storage, you add the discs
00:25:02.860 --> 00:25:05.830
into your failover cluster. Has
to have network connectivity
00:25:05.880 --> 00:25:08.020
obviously, so it's going to be iSCSI
attached or it's going to
00:25:08.070 --> 00:25:14.720
be dez, seared Saas or fiber channel
and finally you add storage
00:25:14.770 --> 00:25:19.210
into the CSB itself. So I believe
we've got a good question you
00:25:19.260 --> 00:25:21.000
wanted to bring up here, bud?
00:25:21.050 --> 00:25:26.400
>> Yes, there is a question, and
everything is like scrolling
00:25:26.450 --> 00:25:27.040
through here.
00:25:27.090 --> 00:25:28.500
>> Now it says green hat.
00:25:28.550 --> 00:25:29.290
>> Green hat.
00:25:30.500 --> 00:25:32.600
>> This is great, where did the
question go, it was a question
00:25:32.650 --> 00:25:35.790
about can you please explain
shared nothing?
00:25:36.330 --> 00:25:40.730
So many people have tried to explain
it, but they fall over...
00:25:40.780 --> 00:25:44.790
I wanted to see if that was maybe fail
over, they fall over every time.
00:25:46.920 --> 00:25:47.560
>> Shared nothing.
00:25:47.610 --> 00:25:48.680
>> Are you going to fall over?
00:25:48.730 --> 00:25:50.080
>> Shared nothing migration.
00:25:50.400 --> 00:25:54.090
>> Shared nothing in quotes
"shared nothing." >> Shared
00:25:54.140 --> 00:25:58.370
nothing live migration is I believe
actually I talk about...
00:25:58.420 --> 00:26:00.620
let me see here quickly.
00:26:01.180 --> 00:26:07.430
You know what, I want to say, I
want to get to it in a couple
00:26:07.480 --> 00:26:12.020
seconds, but essentially, as long
as you have two Hyper-V systems
00:26:12.070 --> 00:26:16.270
on the same network, in the network,
not even the same network,
00:26:16.320 --> 00:26:19.000
but in the network, they were part
of the same domain, they were
00:26:19.050 --> 00:26:22.330
running Hyper-V server 2012. They
were running Hyper-V role on
00:26:22.380 --> 00:26:26.070
Server 2012 and they had networking
connectivity and you have
00:26:26.120 --> 00:26:30.500
administered access on those boxes,
you can take a workload or
00:26:30.550 --> 00:26:34.560
virtual machine in a nonclustered
environment, plan failovers
00:26:34.610 --> 00:26:36.860
when you'd be using this, right
mouse click on that server and
00:26:36.910 --> 00:26:39.970
say, move, and choose the destination.
You have to enable this
00:26:40.020 --> 00:26:40.850
on both boxes.
00:26:41.380 --> 00:26:44.120
You have to set up some level of
delegation called constrains
00:26:44.170 --> 00:26:49.310
delegation inside active directory
to be able to do it. And you
00:26:49.360 --> 00:26:53.330
simply say, move and then it's going
to go off and start to do a...
00:26:53.380 --> 00:26:56.330
again, copying of the data from one
location to another location
00:26:56.380 --> 00:26:58.360
while the machine is running. It's
going to basically get that
00:26:58.410 --> 00:27:01.120
in sync, everything is happy. It's
going to be able to recreate
00:27:01.170 --> 00:27:05.390
the computer configuration information
from that one VM to the
00:27:05.440 --> 00:27:08.570
new VM that is being created
on the new side of things.
00:27:08.620 --> 00:27:10.750
It's going to then start to synchronize
memory pages. You have
00:27:10.800 --> 00:27:13.240
the memory page all in sync, it's
all set and ready to go, the
00:27:13.290 --> 00:27:17.750
slowest part of this is data copy
of the 18 gigs of system files
00:27:17.800 --> 00:27:20.910
that are on that guy. Once it arrives
on that second side of
00:27:20.960 --> 00:27:23.350
the machine and there is that cutover
time period where basically
00:27:23.400 --> 00:27:26.850
almost identical across the board,
it does that switchover to
00:27:26.900 --> 00:27:29.940
be able to do it. You can literally
do a live migration with
00:27:29.990 --> 00:27:32.760
shared nothing live migration, with
nothing but ethernet cable
00:27:32.810 --> 00:27:35.870
connecting the different servers
and Jeff Woolsey has a great
00:27:35.920 --> 00:27:39.850
conversation going on where he's
gone in and had multiple Hyper-V
00:27:39.900 --> 00:27:43.700
boxes on different floors of particular
buildings here at Microsoft
00:27:43.750 --> 00:27:46.910
and he's able to simply say live
migrate upstairs, live migrate
00:27:46.960 --> 00:27:49.970
across the haul, live migrate to
building 20, live migrate back
00:27:50.020 --> 00:27:52.860
to building 43. And it's just a
matter of waiting for this copy
00:27:52.910 --> 00:27:55.830
process to finish and it just goes
literally like the holy graille,
00:27:55.880 --> 00:27:59.730
there is no cluster required to
be able to do it. Now obviously
00:28:00.170 --> 00:28:04.090
these machines are not highly available
if the machine that is
00:28:04.140 --> 00:28:08.530
now done and running an instance
goes down, that machine is dead.
00:28:08.580 --> 00:28:12.260
The VM guest is dead. But as far as
being able to have the mobility
00:28:12.310 --> 00:28:15.840
to move it from machine to machine anywhere,
any networking connectivity
00:28:15.890 --> 00:28:18.960
is totally possible to do from
a plan failover perspective.
00:28:19.010 --> 00:28:22.200
That's new with Server 2012, the
requirements are simply have
00:28:22.250 --> 00:28:27.030
server 2012 as your base hypervisor,
have the role of Hyper-V
00:28:27.080 --> 00:28:30.470
installed and then have common
networking connectivity, have
00:28:30.520 --> 00:28:33.230
constrained delegation, constrained
delegation can be a little
00:28:33.280 --> 00:28:36.500
bit scary. Let me actually... I
can't show you how to set this
00:28:36.550 --> 00:28:38.980
up with my environment right now,
but I can show you at least
00:28:39.030 --> 00:28:41.520
what I'm talking about, what I'm
saying constrained delegation.
00:28:41.570 --> 00:28:45.360
>> While you're looking that up,
I will say Martin, who asked
00:28:45.410 --> 00:28:47.590
the question, has already responded
with perfect, thank you.
00:28:47.640 --> 00:28:48.820
>> Oh, okay, good. Can I stop?
00:28:48.870 --> 00:28:52.040
>> What I want to know from Martin,
was the one line answer that
00:28:52.090 --> 00:28:53.360
upon can Simon gave you...
00:28:53.410 --> 00:28:53.660
>> Better?
00:28:53.710 --> 00:28:56.300
>> The perfect thank you or the five
minutes that Rick just gave
00:28:56.350 --> 00:28:59.760
you the perfect thank you.
00:28:59.810 --> 00:29:00.000
>> Oh!
00:29:00.050 --> 00:29:02.800
>> Nice, I can feel the love in
this room, let me tell you.
00:29:02.850 --> 00:29:09.090
What was I trying to show you again?
Oh, yeah. I want to show
00:29:09.140 --> 00:29:12.690
you the... this is the one thing
the hiccup some people don't
00:29:12.740 --> 00:29:13.400
quite get.
00:29:14.520 --> 00:29:17.460
Again, I'm doing this in my virtualized
environment. You would
00:29:17.510 --> 00:29:20.450
normally be doing this on the actual
live active directory outside
00:29:20.500 --> 00:29:21.600
of your Hyper-V, guys.
00:29:22.370 --> 00:29:27.260
Basically if I had two hosts machines
that are my physical install
00:29:27.310 --> 00:29:30.260
of Hyper-V, they are not clustered,
I would simply have to go
00:29:30.310 --> 00:29:34.300
in here, go and choose properties,
choose delegation, and say
00:29:34.350 --> 00:29:37.660
trust this computer for delegation
of any service or I can choose
00:29:37.710 --> 00:29:40.410
a specific service in which case
I need to go in and choose the
00:29:40.460 --> 00:29:43.440
service type and the what's involved,
I just choose this from
00:29:43.490 --> 00:29:47.170
a demo perspective to say any service
that's available, hit apply,
00:29:47.220 --> 00:29:50.120
and we're good. The other guys,
well, have to enable him, as
00:29:50.170 --> 00:29:51.730
well for constrained delegation.
00:29:52.340 --> 00:29:56.390
Turn that guy on. Hit apply and
okay. He's now done and then
00:29:56.440 --> 00:29:58.490
from the Hyper-V boxes themselves,
00:29:59.730 --> 00:30:02.540
that guy's set up from the
Hyper-V boxes themselves,
00:30:03.840 --> 00:30:05.980
look at my Hyper-V controller here.
00:30:06.850 --> 00:30:07.460
There we go.
00:30:08.160 --> 00:30:12.370
Under Hyper-V settings, I have to
simply say, is this guy sporting
00:30:13.030 --> 00:30:16.210
live migrations or not? And then
what type of authentication
00:30:16.260 --> 00:30:20.500
am I going to be using to be able
to get there? So that is good.
00:30:20.550 --> 00:30:21.430
So that's
00:30:23.850 --> 00:30:25.020
shared nothing migration.
00:30:25.070 --> 00:30:25.720
>> All right.
00:30:25.770 --> 00:30:30.610
>> That's also one of those things
that again, it's some people
00:30:30.660 --> 00:30:31.840
see it more as an
00:30:33.260 --> 00:30:38.710
add-on to live migration because
previously in 2008, R2, live
00:30:38.760 --> 00:30:41.930
migration was only possible if you
had that cluster shared volume,
00:30:41.980 --> 00:30:46.390
shared nothing live migration is
essentially similar technology
00:30:46.440 --> 00:30:48.670
for synchronizing the contents
back and forth, but there's no
00:30:48.720 --> 00:30:52.390
shared drive storage that's being used.
It literally is two different
00:30:52.440 --> 00:30:54.870
locations to be able to do it.
The thing I like about that is
00:30:54.920 --> 00:30:57.600
also coming back here to my slides
for just one second, when
00:30:57.650 --> 00:31:02.670
I get there, five to do it, Yep.
00:31:03.460 --> 00:31:07.360
You can have your systems up and
running and have your storage
00:31:07.410 --> 00:31:10.610
basically move around while leaving
the virtual machines and
00:31:10.660 --> 00:31:14.070
their configurations running on
the individual Hyper-V hosts.
00:31:14.840 --> 00:31:18.510
And so for instance, you can do
a storage migration, which is
00:31:18.560 --> 00:31:21.870
again getting the content of the
local machine, VHD files, config
00:31:21.920 --> 00:31:25.290
files, stuff like that, copied over
to the new location, brought
00:31:25.340 --> 00:31:27.890
in synchronization and
cut over when in
00:31:29.270 --> 00:31:32.530
stasis, if you will, while the
system is up and running.
00:31:32.580 --> 00:31:36.200
You could do a storage migration
to an SME file share, that's
00:31:36.250 --> 00:31:40.920
version 3 on server 2012, if you
wanted to. You also are able
00:31:40.970 --> 00:31:45.790
to go in and to move from a local
C drive location or D drive
00:31:45.840 --> 00:31:49.950
location of virtual machines with
storage migration up to a shared
00:31:50.000 --> 00:31:54.320
network or into an SMB file share
or into cluster shared volumes
00:31:54.370 --> 00:31:57.380
location, as well. So you're given
lots of flexibility for where
00:31:57.430 --> 00:31:59.980
and how you're going to be moving
stuff in and stuff out.
00:32:00.030 --> 00:32:04.830
One thing with this guy here is
that you can set this up with
00:32:04.880 --> 00:32:08.140
highly available virtual machines
on SMB 3.0 file shares.
00:32:08.190 --> 00:32:12.540
You can make that SMB 3 file share
highly available and then
00:32:12.590 --> 00:32:16.970
have individual hosts that are running
and talking to that highly
00:32:17.020 --> 00:32:20.050
available SMB file share and you
can do share nothing migration
00:32:20.100 --> 00:32:23.290
between them. Or you can
set that up as Hyper-V
00:32:24.570 --> 00:32:29.580
workload in a cluster that is using
the SMB file share for its
00:32:29.630 --> 00:32:32.610
storage location, not cluster shared
volumes, but SMB for location,
00:32:32.660 --> 00:32:35.780
as well, to get extra layers of
redundancy in there, which is
00:32:35.830 --> 00:32:36.700
very, very cool.
00:32:37.890 --> 00:32:41.200
Some consideration for Hyper-V
clusters, simply what apps are
00:32:41.250 --> 00:32:43.750
requiring high availability inside
your VMs. Are they going to
00:32:43.800 --> 00:32:45.670
be able to work inside that environment?
00:32:46.230 --> 00:32:48.380
What type of application characteristics
are there?
00:32:48.430 --> 00:32:51.890
Basically verify your design
is going to work for you.
00:32:51.940 --> 00:32:54.840
Identify data network adapter for
private virtual networks.
00:32:54.890 --> 00:32:58.070
Ideally, you are going to want
to have dedicate a network for
00:32:58.120 --> 00:33:00.940
your storage, maybe multi-path for
better performance and more
00:33:00.990 --> 00:33:04.890
redundancy, have a dedicated fast
network between your systems
00:33:04.940 --> 00:33:07.990
if you're going to be using the
two nodes of your cluster for
00:33:08.040 --> 00:33:12.020
moving those back and forth. One potentially
dedicated for management
00:33:12.070 --> 00:33:14.420
and then also one for your clients
to have access to, as well.
00:33:14.470 --> 00:33:16.920
So you can get quite elaborate with
your setups that you're using.
00:33:17.950 --> 00:33:20.910
Here is the actual slide about
the virtual migration options.
00:33:21.300 --> 00:33:24.830
I don't know if too many peep they'll
would still be using quick migration.
00:33:25.640 --> 00:33:29.000
Quick migration basically is where
you go in and you stop the
00:33:29.050 --> 00:33:31.860
virtual machine or you pause it
basically. You move it over and
00:33:31.910 --> 00:33:33.360
then you make it reanimated
again and rehydrated again.
00:33:34.470 --> 00:33:36.830
That was the old way of doing stuff
for 2008. We don't use that
00:33:36.880 --> 00:33:40.330
technology as the primary way of
doing stuff now. Live migration
00:33:40.380 --> 00:33:42.750
is what I talked about already,
using clustered shared volume
00:33:42.800 --> 00:33:46.850
as the back end between Hyper-V nodes.
Share nothing live migration,
00:33:46.900 --> 00:33:49.420
which does not appear on this slide,
is the one I went through
00:33:49.470 --> 00:33:52.780
at great detail because someone asked
me the question. You literally
00:33:52.830 --> 00:33:56.050
have just a network capable between
them N. Theory, although
00:33:56.100 --> 00:34:00.750
not supported, I've heard Microsoft
guy Ben Armstrong, I don't
00:34:00.800 --> 00:34:03.920
know if you know him, virtual guy,
PC guy, he actually did shared
00:34:03.970 --> 00:34:05.000
nothing live...
00:34:05.050 --> 00:34:06.210
>> You asking me or
you asking them?
00:34:06.260 --> 00:34:07.410
>> I'm asking both.
00:34:07.460 --> 00:34:07.960
>> Yeah.
00:34:08.600 --> 00:34:13.040
>> He actually did a share nothing live
migration over a wireless network.
00:34:13.090 --> 00:34:16.550
That's supported because it's just
not supported, he did it over
00:34:16.600 --> 00:34:17.170
wireless network.
00:34:17.220 --> 00:34:18.040
>> Not supported, but fun.
00:34:18.090 --> 00:34:23.320
>> You got it. Also the option of Hyper-V
replica and simple import
00:34:23.370 --> 00:34:25.830
and exporting virtual machines. Replica
is the one thing I haven't
00:34:25.880 --> 00:34:29.220
talked about just yet, it's
coming up in my system.
00:34:30.360 --> 00:34:33.950
So storage migration is the underpinning
of how share nothing
00:34:34.000 --> 00:34:36.840
live migration works. During the
migration of virtual machine
00:34:36.890 --> 00:34:39.470
and hard drive is basically copied
from one location to the other.
00:34:39.520 --> 00:34:42.210
Changes are written to both from
that point forward. The deltas
00:34:42.260 --> 00:34:44.840
are brought into sync, you have
very little left, you simply
00:34:44.890 --> 00:34:47.060
move the virtual machine storage
to the same host, to another
00:34:47.110 --> 00:34:50.510
host or different location. The storage
of the machine configuration
00:34:50.560 --> 00:34:53.400
can be different locations if you
wanted to and at the very last
00:34:53.450 --> 00:34:55.390
moment, just like you would do
a memory sync, the drives are
00:34:55.440 --> 00:34:58.180
in sync, boom, cuts over and you're
good to go from a storage
00:34:58.230 --> 00:34:59.410
migration perspective.
00:35:02.360 --> 00:35:04.550
Animated slide for live migration,
I covered this one here in
00:35:04.600 --> 00:35:07.360
great detail for where this guy
goes for the animation copies
00:35:07.410 --> 00:35:10.480
the files over, the smart paging
files, configuration files,
00:35:10.530 --> 00:35:11.880
gets them all sync to the side.
00:35:11.930 --> 00:35:12.770
>> You did that all by yourself?
00:35:12.820 --> 00:35:15.830
>> I did that all my myself, man,
and simply the cutover happens.
00:35:15.880 --> 00:35:20.580
It's not very terribly exciting.
A replica is my... I think my
00:35:20.630 --> 00:35:23.670
last major point I want to cover,
which is absolutely awesome.
00:35:23.720 --> 00:35:29.840
Inbox doesn't cost you a dime, for what
you can do with Hyper-V replica.
00:35:30.210 --> 00:35:34.890
Picture yourself where you know
in pending doom is arriving,
00:35:34.940 --> 00:35:39.360
let's say. And you need to get your
content of your data center
00:35:39.410 --> 00:35:41.970
out of the location where it is
right now, some place else.
00:35:43.570 --> 00:35:46.730
You would in the past, have to
go through and literally very
00:35:46.780 --> 00:35:50.030
expensive, do some kind of a replication
of the san data centers
00:35:50.080 --> 00:35:53.710
for the different networks outside
that location to do something
00:35:53.760 --> 00:35:55.570
to get that all up and running.
You'd have to have some type
00:35:55.620 --> 00:35:58.500
of agreement to do imports and
exports on a regular basis.
00:35:58.550 --> 00:36:01.410
Now you simply enable
the Hyper-V replica.
00:36:02.000 --> 00:36:04.640
You have to turn that on under Settings
for the local machine.
00:36:04.690 --> 00:36:07.890
Once it's turned on, you say Yes,
I'm alien hyper replica.
00:36:07.940 --> 00:36:11.520
You identify the destination for
where you're going. The really
00:36:11.570 --> 00:36:17.800
cool thing, you can identify a nondomain
joined even nonphysical
00:36:17.850 --> 00:36:21.130
same site only network connectivity,
like to a hosting provider,
00:36:21.180 --> 00:36:25.240
as an example, location, where
destination is going to be.
00:36:25.290 --> 00:36:26.550
You would identify and you use
00:36:28.060 --> 00:36:31.600
certificate base authentication
to that remote location to make
00:36:31.650 --> 00:36:35.350
sure it's secure. And you initiate
a replica between those two
00:36:35.400 --> 00:36:36.380
different systems.
00:36:37.340 --> 00:36:40.430
When you finish off the wizard,
what it basically does is sends
00:36:40.480 --> 00:36:43.680
a copy of the configuration file
traffic over to the other side.
00:36:43.730 --> 00:36:46.690
It then also starts a replication
or synchronization process
00:36:46.740 --> 00:36:50.610
between the running VM and
that destination side.
00:36:51.280 --> 00:36:54.400
And then what that basically means
is that this now is going
00:36:54.450 --> 00:36:57.510
to replicate on a per machine basis
across this WAN link to that
00:36:57.560 --> 00:37:00.920
destination, which could be a work
group machine, a hoster machine
00:37:00.970 --> 00:37:04.520
or another machine in your network
if you wanted to. It basically
00:37:04.570 --> 00:37:07.450
tracks all the changes that go on
that machine that is live and
00:37:07.500 --> 00:37:09.840
then bring its across
to the replica site.
00:37:11.240 --> 00:37:15.260
If you're doing this to a cluster,
as either the outbound location
00:37:15.310 --> 00:37:18.650
or the inbound location, because
there are multiple nodes that
00:37:18.700 --> 00:37:23.010
are your Hyper-V managers that are
in that cluster, you basically
00:37:23.060 --> 00:37:27.080
have to add in a cluster role called
the Hyper-V replica broker
00:37:27.130 --> 00:37:30.460
role and that simply says I am the
main contact point that will
00:37:30.510 --> 00:37:35.880
be used for all inbound and outbound replications
and you initiate synchronization.
00:37:36.230 --> 00:37:39.380
Now if you do this, make sure that
you're aware this is not a
00:37:39.430 --> 00:37:42.560
live migration, this is a copy of
the data file across the WAN
00:37:42.610 --> 00:37:46.580
link or we can seed it to do export
and import on either side
00:37:46.630 --> 00:37:47.790
to save yourself some time.
00:37:48.990 --> 00:37:50.920
And then it's a synchronization from
that point forward, whatever
00:37:50.970 --> 00:37:53.370
is done, you configure the intervals
of things that are synchronized.
00:37:53.420 --> 00:37:56.510
You then are able to go in and say,
do a fail over and fail this
00:37:56.560 --> 00:38:00.300
guy over to the other side. It finishes
up the last bit of replication
00:38:00.350 --> 00:38:03.150
over to the side and then tells that
guy to basically start out.
00:38:03.200 --> 00:38:04.950
That guy can now start
and it's good to go.
00:38:05.690 --> 00:38:08.350
You can then also do a replica
back to that first guy if you
00:38:08.400 --> 00:38:12.070
wanted to and then when you need
to, you can actually bring that
00:38:12.120 --> 00:38:16.460
guy back in again. Now the machine
is basically "down" while
00:38:16.510 --> 00:38:19.360
you are doing that move of the
final synchronization from one
00:38:19.410 --> 00:38:22.590
side to this side, but it's gotten
you as a free cost effective
00:38:22.640 --> 00:38:25.170
way of getting replicas to the other
side, outside of your data
00:38:25.220 --> 00:38:29.680
center, out to the other environment.
So replica is new, only
00:38:29.730 --> 00:38:33.280
part of server 2012, have to be
Server 2012 hypervisor roles
00:38:33.330 --> 00:38:36.120
installed on your servers to be able
to support this, but really
00:38:36.170 --> 00:38:38.870
way cool technology to be able to
cover your butt in case there's
00:38:38.920 --> 00:38:39.700
a problem.
00:38:41.050 --> 00:38:42.770
Any questions? Any good comments?
00:38:43.800 --> 00:38:44.230
Want to share...
00:38:44.280 --> 00:38:48.130
>> I will tell you that, you know,
you're going to have to thank
00:38:48.180 --> 00:38:53.820
Martin because now you pretty much
have a good like 20 questions
00:38:53.870 --> 00:38:56.080
on the same topic.
00:38:56.130 --> 00:38:56.870
>> Okay, great.
00:38:57.420 --> 00:38:58.630
(Laughter) >> I'm
00:38:58.680 --> 00:39:01.490
actually in the middle of answers some
certification questions, actually.
00:39:01.540 --> 00:39:02.540
>> Certifi >> quation.
00:39:02.800 --> 00:39:09.020
Certifi-quation. I learned that junior year
in high school, the >> certifi-quation.
00:39:09.070 --> 00:39:11.580
Back to slide for one quick little
second here for the actual
00:39:11.630 --> 00:39:15.050
configuration of Hyper-V replica.
Now I can't show you this because
00:39:15.930 --> 00:39:20.400
the demo environments that we have
basically I've got two nondomain
00:39:20.450 --> 00:39:23.670
joined machines, one of which is
currently down because Ed forgot
00:39:23.720 --> 00:39:24.980
to bring his power >> supply....
00:39:26.330 --> 00:39:28.200
It's it's >> on.
00:39:28.250 --> 00:39:30.650
It's on in time for me to be able
to prep the demo in the short
00:39:30.700 --> 00:39:32.310
times we have in between these >> sessions.
00:39:32.690 --> 00:39:36.130
Wait, wait. Let's just make this
clear, the only reason I'm here
00:39:36.740 --> 00:39:38.390
is to be your >> scapegoat.
00:39:39.010 --> 00:39:41.120
>> Nice. Two nonstop days of >> it.
00:39:41.170 --> 00:39:45.030
And I can't show the Hyper-V configuration
of the Hyper-V replica
00:39:45.080 --> 00:39:48.050
because it actually has to contact
the destination to make sure
00:39:48.100 --> 00:39:51.150
it's valid and working before I finish
off the configuration options.
00:39:52.080 --> 00:39:55.870
So basically you configure the authentication
mechanisms, certificate
00:39:55.920 --> 00:39:57.960
you're going to be using, the secure
path you're going to be
00:39:58.010 --> 00:40:01.690
using with port 443 to do the replica
traffic over it. You configure
00:40:01.740 --> 00:40:04.530
the firewall ports to allow for replication
to take place between
00:40:04.580 --> 00:40:07.750
the two different systems, you then
identify who is the replica
00:40:07.800 --> 00:40:11.750
server and then you right mouse
click on the individual work
00:40:11.800 --> 00:40:14.280
load of the machine that you want
to go off and move. This can
00:40:14.330 --> 00:40:17.520
be on a single standalone, noncluster
environment to another
00:40:17.570 --> 00:40:19.710
single standalone noncluster environment.
Cluster not a question
00:40:19.760 --> 00:40:23.290
requirement for this and then on
the destination you choose where
00:40:23.340 --> 00:40:26.970
that replica file will sit and then
finally you enable the replication
00:40:27.020 --> 00:40:30.030
for the select virtual machines
you want to do. Now obviously
00:40:30.080 --> 00:40:33.270
there is a massive amount of bandwidth
that can be consumed of
00:40:33.320 --> 00:40:36.810
trying to get multiple giga bytes
of data out of your network
00:40:36.860 --> 00:40:41.340
to that destination location....
So and also, ongoing traffic
00:40:41.390 --> 00:40:43.870
to basically keep them in sync,
so you then want to selectively
00:40:43.920 --> 00:40:47.280
choose which ones you enable replication
for and also do some
00:40:47.330 --> 00:40:50.660
throttling to this, maybe quality
of service this, as well.
00:40:50.710 --> 00:40:53.810
And so be aware of that before
you say, ah, I'm going to take
00:40:53.860 --> 00:40:58.300
all 30 machines and replicate them
to my offsite. Maybe not a
00:40:58.350 --> 00:41:00.890
good idea. Select the ones you need
to have and also as you're
00:41:00.940 --> 00:41:03.670
doing this, you need to be careful
that you have in a multi-tiered
00:41:03.720 --> 00:41:06.740
environment all the pieces you
need to have replicated to the
00:41:06.790 --> 00:41:10.490
other side, obviously for
the Hyper-V replica.
00:41:11.160 --> 00:41:14.280
That actually brings me up to able
to answer a couple of questions
00:41:14.330 --> 00:41:16.060
if you're interested, man.
00:41:17.870 --> 00:41:18.380
While we're doing...
00:41:18.430 --> 00:41:18.580
>> that >> Yeah.
00:41:18.630 --> 00:41:21.510
I'm going to quickly take a look
and say, look, I'm in the middle
00:41:21.560 --> 00:41:22.760
of answering another >> one.
00:41:22.810 --> 00:41:24.230
That's good. That's always good.
00:41:27.170 --> 00:41:30.440
Flip back to my machine for one second,
if you could there, Jeff.
00:41:31.340 --> 00:41:34.170
This is my failover cluster manager
and I actually configured
00:41:34.220 --> 00:41:37.750
and have what is known as the replication
broker already running
00:41:37.800 --> 00:41:40.370
because I was trying to do a demo
for you guys on this one here.
00:41:40.420 --> 00:41:43.190
If I want to take a look at this
under properties, it's simply
00:41:43.240 --> 00:41:46.190
identifies this guy's replication
broker and he's there.
00:41:47.520 --> 00:41:50.600
I guess I could delete them and
bring them back in again if I
00:41:50.650 --> 00:41:54.380
wanted to. If I go in and take a
look specifically on my Hyper-V
00:41:54.680 --> 00:41:57.310
server setting for this guy here,
if you remember, I have the
00:41:57.360 --> 00:42:00.200
ability to identify how many simultaneous
live migrations are
00:42:00.250 --> 00:42:02.980
allowed from my previous discussion.
00:42:03.810 --> 00:42:07.200
Also, I have my ability
to go through and
00:42:08.560 --> 00:42:12.730
take a look at my replica configuration.
Because this is all
00:42:12.780 --> 00:42:15.560
grayed out, you can kind of see
what I'm talking about here,
00:42:15.610 --> 00:42:19.440
but basically because this is on a
cluster, it says use the failover
00:42:19.490 --> 00:42:23.040
cluster manager to configure these
settings. Over here, simply
00:42:23.090 --> 00:42:25.960
which protocol do I want to use,
certificate-based authentication
00:42:26.010 --> 00:42:29.770
to prove who I am and who I'm talking
to and then... who where
00:42:29.820 --> 00:42:34.330
am I going to be placing my inbound
replication replica data
00:42:34.380 --> 00:42:37.470
from my system and then am I going
to only allow certain peep
00:42:37.520 --> 00:42:40.680
toll replicate into this particular
box? You do the same setting
00:42:40.730 --> 00:42:41.710
on the other side.
00:42:42.320 --> 00:42:45.370
And then you basically initiate
the connection, you initiate
00:42:45.420 --> 00:42:48.950
the connection by simply saying...
here here is an individual box.
00:42:49.900 --> 00:42:53.550
Rick's Demo, I say... replication
enable replication.
00:42:56.400 --> 00:42:58.640
The wizard kicks off and unfortunately,
the first thick it asks
00:42:58.690 --> 00:43:00.640
me that prevents me from going through
the rest of this wizard
00:43:00.690 --> 00:43:01.610
is "what is
00:43:03.180 --> 00:43:08.340
the name of the destination replication
server" that I set this
00:43:08.390 --> 00:43:11.930
up on. I can't put one in here
because it basically fails in
00:43:11.980 --> 00:43:14.440
my demo environment right now, but
it would allow me to basically
00:43:14.490 --> 00:43:18.780
choose how often, which VHDs want
to replicate, what kind of
00:43:18.830 --> 00:43:21.860
recovery do I want to have and then
the initial replication method
00:43:21.910 --> 00:43:26.320
you actually can choose exported
VM shipped on hard drive to
00:43:26.370 --> 00:43:29.400
your destination as your initial
source of replication to be
00:43:29.450 --> 00:43:32.750
able to bring it in on the other side
and save you a lot of bandwidth.
00:43:32.800 --> 00:43:35.620
Like they say, nothing beats bandwidth,
than a station wagon
00:43:35.670 --> 00:43:38.900
full of DVDs when you're talking
about >> distances.
00:43:39.660 --> 00:43:40.950
You got it, man >> Yeah.
00:43:41.000 --> 00:43:42.110
You got >> it.
00:43:42.160 --> 00:43:45.740
Rick, does it do any good I'm looking
at that machine and it's
00:43:45.790 --> 00:43:48.140
running and I've got Hyper-V already
up and running and I've
00:43:48.190 --> 00:43:50.750
got some VMs running, anything
you can do at this point or is
00:43:50.800 --> 00:43:50.960
it too >> late?
00:43:51.010 --> 00:43:51.260
All >> right.
00:43:51.310 --> 00:43:53.440
It's too late just because we're
going to be wrapping up.
00:43:53.490 --> 00:43:55.940
One thing I will mention, when you're
setting up Hyper-V replica,
00:43:55.990 --> 00:43:59.800
you must use DNS names or fully qualified
domain names as >> destinations.
00:43:59.850 --> 00:44:02.690
>> Uh-huh. If you try to do a shortcut
like I did during the break
00:44:03.720 --> 00:44:06.760
with IP addresses it actually will not
let you finish off the >> wizard.
00:44:06.810 --> 00:44:07.940
>> Right. In the IP address >> there.
00:44:07.990 --> 00:44:11.440
You want to explain to them for those
that weren't here yesterday,
00:44:12.290 --> 00:44:13.120
why I'm wearing a >> hat?
00:44:14.070 --> 00:44:15.160
Why are you wearing a >> hat?
00:44:15.210 --> 00:44:15.370
Well,...
00:44:15.420 --> 00:44:18.850
>> because I know why
I'm wearing a >> hat.
00:44:18.900 --> 00:44:21.050
Yesterday was backup, today
it's just redundancy.
00:44:21.690 --> 00:44:22.810
It's because I want to be like >> Rick.
00:44:22.860 --> 00:44:24.690
You know what, you're waiting
for the initial...
00:44:24.740 --> 00:44:26.110
>> replication >> Yes.
00:44:26.160 --> 00:44:29.490
Of the hat to your head and you just
have the placeholder right now.
00:44:29.540 --> 00:44:31.450
So maybe after the break we'll
be able to have...
00:44:31.500 --> 00:44:33.090
>> the We'll see. We'll >> see.
00:44:33.140 --> 00:44:36.130
Hey, real quick, by the way, for
anybody who's watch nothing
00:44:36.180 --> 00:44:41.010
full screen mode, just want you
to look for the poll questions
00:44:41.060 --> 00:44:43.290
that may be out there and then there
will be some more this afternoon,
00:44:43.340 --> 00:44:44.120
as >> well.
00:44:44.170 --> 00:44:46.320
Drop out of full screen mode to be
able to do the web page >> again?
00:44:46.370 --> 00:44:48.210
Yes, yes, >> yes.
00:44:48.260 --> 00:44:51.350
We'll go from that. So after the
extended break, basically at
00:44:51.400 --> 00:44:54.120
the top of the hour, we'll be back
and I think we're talking
00:44:54.170 --> 00:44:55.430
about dynamic access...
00:44:55.480 --> 00:44:57.090
>> control Or is it direct >> access?
00:44:57.140 --> 00:44:59.700
No, dynamic access control, that's
what we're talking about.
00:44:59.750 --> 00:45:02.620
So we'll see you after
the break, top of
00:45:13.900 --> 00:45:14.460
the hour.