1
00:00:00,940 --> 00:00:05,340
What is the process of Hyper‑V Replica failover and failback?

2
00:00:05,340 --> 00:00:08,570
Well, it's a lot easier than ASR for sure,

3
00:00:08,570 --> 00:00:11,650
because here we're talking about not an orchestration

4
00:00:11,650 --> 00:00:17,550
among multiple related machines, but basically single virtual machines.

5
00:00:17,550 --> 00:00:23,280
And because AZ‑801 is an exam that deals with administration and implementation,

6
00:00:23,280 --> 00:00:27,420
you can expect to see questions that require you to know where user

7
00:00:27,420 --> 00:00:30,050
interface elements are. Now before you think,

8
00:00:30,050 --> 00:00:30,980
well, wait a minute, Tim,

9
00:00:30,980 --> 00:00:34,590
isn't that trivia, not so fast. Remember that Microsoft is looking to

10
00:00:34,590 --> 00:00:37,930
validate that you not only understand the theory of,

11
00:00:37,930 --> 00:00:39,210
say, Hyper‑V Replica,

12
00:00:39,210 --> 00:00:43,230
but you know how to use it. And if you've gotten enough time or

13
00:00:43,230 --> 00:00:48,320
spent enough time using the technology in a practice test lab

14
00:00:48,320 --> 00:00:50,730
or even a production environment,

15
00:00:50,730 --> 00:00:54,740
then it's probably not that big a deal for you to answer these questions.

16
00:00:54,740 --> 00:00:59,770
So here I want to show you the user interface options that you see on

17
00:00:59,770 --> 00:01:05,140
both your primary and secondary Hyper‑V hosts. Here I want to draw your

18
00:01:05,140 --> 00:01:07,420
attention. What I've got in Hyper‑V Manager,

19
00:01:07,420 --> 00:01:12,040
I've got mem1, which is my primary host selected, and I

20
00:01:12,040 --> 00:01:15,630
furthermore right‑clicked on win1, which is a virtual

21
00:01:15,630 --> 00:01:18,290
machine running in that primary host.

22
00:01:18,290 --> 00:01:22,230
And notice the options you get. Right‑click Replication. You get

23
00:01:22,230 --> 00:01:25,510
Planned Failover, but you don't get the Failover option.

24
00:01:25,510 --> 00:01:27,510
Why do you think that's the case? Well,

25
00:01:27,510 --> 00:01:32,400
how could you do a failover from the primary if the primary site is

26
00:01:32,400 --> 00:01:37,390
unavailable or if the primary host is gone? The whole idea with replication

27
00:01:37,390 --> 00:01:41,610
is that we're providing that high availability. So notice that you can

28
00:01:41,610 --> 00:01:44,940
remove and pause and view replication health,

29
00:01:44,940 --> 00:01:47,530
but you can initiate only planned failover,

30
00:01:47,530 --> 00:01:51,910
which, again, is a great practice for you and your team to adopt so you can

31
00:01:51,910 --> 00:01:56,610
build up that muscle memory and see what happens when a failover actually

32
00:01:56,610 --> 00:02:01,750
occurs, all right? And planned also makes it a lot easier for you to undo the

33
00:02:01,750 --> 00:02:05,850
change. It'll actually, a planned failover will create a separate VM that you

34
00:02:05,850 --> 00:02:09,240
can just delete on the secondary server.

35
00:02:09,240 --> 00:02:14,690
So let's now look over to the partner, or the secondary Hyper‑V host, mem2,

36
00:02:14,690 --> 00:02:19,840
and notice that the replicated VM, win1, is in an off state. It is being

37
00:02:19,840 --> 00:02:24,150
actively replicated, and you can verify that by right‑clicking the virtual

38
00:02:24,150 --> 00:02:26,030
machine and going to Replication,

39
00:02:26,030 --> 00:02:30,340
View Replication Health. But notice that there is some additional options. Yes,

40
00:02:30,340 --> 00:02:32,140
there's Test Failover,

41
00:02:32,140 --> 00:02:36,110
but I want you to see that the actual failover control is on the

42
00:02:36,110 --> 00:02:39,150
secondary, and that should make all the sense in the world from a

43
00:02:39,150 --> 00:02:43,010
logic standpoint when you think of the disaster recovery

44
00:02:43,010 --> 00:02:45,340
underpinnings of this technology. Now,

45
00:02:45,340 --> 00:02:48,480
what is Extend? Pause Replication, that's pretty easy to

46
00:02:48,480 --> 00:02:52,040
understand, but what about Extend Replication?

47
00:02:52,040 --> 00:02:52,300
Well,

48
00:02:52,300 --> 00:02:57,460
Extend is where you can create a standby of a standby. If you

49
00:02:57,460 --> 00:03:00,770
want more than one level of disaster recovery,

50
00:03:00,770 --> 00:03:05,330
you can take this secondary and then extend it to yet a third

51
00:03:05,330 --> 00:03:08,330
Hyper‑V host. It kind of gets, in my opinion,

52
00:03:08,330 --> 00:03:11,680
a little bit abstract and reminds me of the old movie Inception,

53
00:03:11,680 --> 00:03:12,940
if you remember that.

54
00:03:12,940 --> 00:03:17,460
But that just is a feature that's baked in here that gives some

55
00:03:17,460 --> 00:03:26,000
businesses that extra level of redundancy that they might need to protect a virtual machine workload in Hyper‑V.