1
00:00:00,940 --> 00:00:04,200
Now let's see what happens during a failover situation.

2
00:00:04,200 --> 00:00:05,570
We'll do a test first.

3
00:00:05,570 --> 00:00:08,380
Let's right‑click on the Replica server,

4
00:00:08,380 --> 00:00:12,300
Replication, Test Failover from the flyout,

5
00:00:12,300 --> 00:00:15,600
and it says we can create a separate virtual machine to

6
00:00:15,600 --> 00:00:18,580
verify that the recovery point is valid.

7
00:00:18,580 --> 00:00:23,410
We can choose our recovery point and then click Test Failover.

8
00:00:23,410 --> 00:00:27,640
So you'll notice what's happening here is that Hyper‑V

9
00:00:27,640 --> 00:00:31,740
immediately spawned another instance of that VM,

10
00:00:31,740 --> 00:00:36,340
gave it the name vm02 ‑ Test to avoid a conflict,

11
00:00:36,340 --> 00:00:39,070
and then we can start it and test it.

12
00:00:39,070 --> 00:00:42,400
But notice that the replication engine didn't make an

13
00:00:42,400 --> 00:00:46,080
assumption that we wanted to start it, but it made it available.

14
00:00:46,080 --> 00:00:48,220
And it's booting down below.

15
00:00:48,220 --> 00:00:50,490
It's probably in a stuck state because, like I said,

16
00:00:50,490 --> 00:00:52,890
I don't have an OS on that machine yet.

17
00:00:52,890 --> 00:00:56,780
It's probably not able to resolve the virtual DVD.

18
00:00:56,780 --> 00:00:59,080
In fact, I guarantee that's what the problem is.

19
00:00:59,080 --> 00:01:04,540
Then to clean up, we can come back to the secondary and go to Replication,

20
00:01:04,540 --> 00:01:07,160
and I'm going to do a Stop Test Failover,

21
00:01:07,160 --> 00:01:10,110
and it tells us that the Test VM will be deleted,

22
00:01:10,110 --> 00:01:11,640
and its data would be discarded.

23
00:01:11,640 --> 00:01:14,030
Again, that's for testing purposes anyway.

24
00:01:14,030 --> 00:01:15,840
That's why that's there.

25
00:01:15,840 --> 00:01:20,280
Now to do a real failover, let's right‑click on the secondary again,

26
00:01:20,280 --> 00:01:22,540
Replication, Failover.

27
00:01:22,540 --> 00:01:23,230
Same interface.

28
00:01:23,230 --> 00:01:26,940
You choose your recovery point and click Fail Over.

29
00:01:26,940 --> 00:01:29,690
Now it tells us here we cannot failover the machine

30
00:01:29,690 --> 00:01:32,640
because the primary is not turned off.

31
00:01:32,640 --> 00:01:36,990
We saw earlier in this course the ASR at least will attempt to

32
00:01:36,990 --> 00:01:39,940
stop the machines in the source environment,

33
00:01:39,940 --> 00:01:43,040
but notice that that's not the case with Hyper‑V.

34
00:01:43,040 --> 00:01:46,620
Now if we had a catastrophic problem on our MEM1 host,

35
00:01:46,620 --> 00:01:50,150
like if MEM1 went down, then, by definition,

36
00:01:50,150 --> 00:01:51,450
vm02 would be down.

37
00:01:51,450 --> 00:01:53,140
You see what I mean?

38
00:01:53,140 --> 00:01:57,370
So I'm going to simulate an outage by shutting down the virtual machine here.

39
00:01:57,370 --> 00:02:00,530
Actually, just going to go ahead and turn it off.

40
00:02:00,530 --> 00:02:05,880
And then on MEM2, let's right‑click, Replication,

41
00:02:05,880 --> 00:02:09,640
Failover, click Fail Over,

42
00:02:09,640 --> 00:02:12,820
and we'll see that that machine is simply coming up and online.

43
00:02:12,820 --> 00:02:17,200
And we can expect that, again, it's not mapping to a DVD at this time,

44
00:02:17,200 --> 00:02:19,210
so it's just showing a black error screen.

45
00:02:19,210 --> 00:02:23,470
But that's pretty straightforward and especially so when you think that

46
00:02:23,470 --> 00:02:26,330
you can automate all of this using Windows PowerShell.

47
00:02:26,330 --> 00:02:31,580
It's not like in the real world we have to babysit here in the Hyper‑V

48
00:02:31,580 --> 00:02:35,840
Manager MMC or possibly in Windows Admin Center.

49
00:02:35,840 --> 00:02:36,110
Now,

50
00:02:36,110 --> 00:02:41,120
what does it look like in terms of replication status now that vm02 is the

51
00:02:41,120 --> 00:02:45,530
running machine and the MEM1 instance is in an off state?

52
00:02:45,530 --> 00:02:48,450
What does that mean with regard to replication health?

53
00:02:48,450 --> 00:02:50,640
Let's actually go to the running instance,

54
00:02:50,640 --> 00:02:55,640
right‑click, Replication, View Replication Health.

55
00:02:55,640 --> 00:03:00,390
Okay, so it says Failover complete, and it says for Replication Health,

56
00:03:00,390 --> 00:03:01,450
it's in a Warning state.

57
00:03:01,450 --> 00:03:06,000
It says, Choose Reverse Replication to resume replication.

58
00:03:06,000 --> 00:03:09,310
So again, it's very similar to what we saw with Azure Site Recovery.

59
00:03:09,310 --> 00:03:13,800
After you perform a failover, the replication then is over with,

60
00:03:13,800 --> 00:03:17,140
and you have to manually re‑enable it.

61
00:03:17,140 --> 00:03:18,860
I like how if there is an error,

62
00:03:18,860 --> 00:03:24,140
notice that we can view events to tap into Event Log conveniently.

63
00:03:24,140 --> 00:03:25,560
Well, at least I tried.

64
00:03:25,560 --> 00:03:26,010
There we go.

65
00:03:26,010 --> 00:03:29,540
It looks like clicking the link slowly invokes the event

66
00:03:29,540 --> 00:03:33,740
viewer console and brings it in here.

67
00:03:33,740 --> 00:03:35,760
And this is actually a good log to know about,

68
00:03:35,760 --> 00:03:39,820
as you can see, Hyper‑V‑VMMS, Admin, Networking,

69
00:03:39,820 --> 00:03:41,100
Operational, and Storage.

70
00:03:41,100 --> 00:03:45,870
And this allows us to track enabling replication,

71
00:03:45,870 --> 00:03:48,610
initial replication completed successfully,

72
00:03:48,610 --> 00:03:49,790
and so on and so forth.

73
00:03:49,790 --> 00:03:54,400
And you can get to that Hyper‑V‑VMMS, let's follow the path here,

74
00:03:54,400 --> 00:03:58,180
we've got an Event Viewer, Applications and Services Logs,

75
00:03:58,180 --> 00:04:02,250
Microsoft, Windows, Hyper‑V‑VMMS.

76
00:04:02,250 --> 00:04:02,500
Okay.

77
00:04:02,500 --> 00:04:07,140
All right, so let's close out of here,

78
00:04:07,140 --> 00:04:10,060
and again we'll right‑click the virtual machine on the secondary,

79
00:04:10,060 --> 00:04:14,940
now the primary, and we'll do a Reverse Replication.

80
00:04:14,940 --> 00:04:19,300
This kicks open the wizard here, so let's go ahead to the first step.

81
00:04:19,300 --> 00:04:23,440
Our Replica server now is going to be replica one.

82
00:04:23,440 --> 00:04:27,040
Now it mentions, the text is kind of small, but I want to repeat this,

83
00:04:27,040 --> 00:04:30,840
that if the Replica server is in a failover cluster,

84
00:04:30,840 --> 00:04:36,420
you're going to specify not the node, but the Hyper‑V Replica Broker clustered

85
00:04:36,420 --> 00:04:40,000
role that you would create as a prerequisite. Important.

86
00:04:40,000 --> 00:04:45,450
So let's go Next here. Says that the specified Replica server is not configured.

87
00:04:45,450 --> 00:04:45,890
Well, again,

88
00:04:45,890 --> 00:04:49,010
it reminds me of how much of this is manual, and I'm just thinking of

89
00:04:49,010 --> 00:04:52,520
how we can automate this with PowerShell. Sure enough,

90
00:04:52,520 --> 00:04:56,520
we'd have to come back to MEM1, go back to Hyper‑V Settings, and make

91
00:04:56,520 --> 00:04:59,240
sure that now we have replication enabled here.

92
00:04:59,240 --> 00:05:03,860
So let me set here the settings that we previously had on

93
00:05:03,860 --> 00:05:06,950
MEM2. Looks like it didn't take my choice.

94
00:05:06,950 --> 00:05:11,640
So I've got Enable this computer, Use Kerberos,

95
00:05:11,640 --> 00:05:16,880
Allow replication from any. Click OK. All right. So let's go back to where we

96
00:05:16,880 --> 00:05:22,840
were before here on vm02, Replication, Reverse Replication.

97
00:05:22,840 --> 00:05:24,430
We'll go Next, MEM1.

98
00:05:24,430 --> 00:05:28,160
Yes, that's right. We're doing Kerberos. Yes, that's right. Compress.

99
00:05:28,160 --> 00:05:32,440
I'm just going to leave everything the same as it was originally here. Next,

100
00:05:32,440 --> 00:05:34,940
Next, Finish.

101
00:05:34,940 --> 00:05:35,840
Great.

102
00:05:35,840 --> 00:05:40,550
So at this point, now we've got vm02 running on MEM2 as the running

103
00:05:40,550 --> 00:05:45,700
active instance, and vm02 is in an off state on MEM1. You know what

104
00:05:45,700 --> 00:05:48,140
we're going to do to reinstate everything, right?

105
00:05:48,140 --> 00:05:51,440
We're going to right‑click, go to Replication.

106
00:05:51,440 --> 00:05:54,700
Well, actually, we can't do it here on the source.

107
00:05:54,700 --> 00:05:58,650
I had mentioned this before, planned versus unplanned failover, right.

108
00:05:58,650 --> 00:06:03,440
So we're going to want to go to what is now the replica, MEM1,

109
00:06:03,440 --> 00:06:10,140
right‑click vm02, Replication, Failover, Fail Over.

110
00:06:10,140 --> 00:06:13,320
Same problem I saw before. I keep getting hit by

111
00:06:13,320 --> 00:06:15,060
that over and over and over again.

112
00:06:15,060 --> 00:06:20,590
I'm just going to go ahead and turn off vm02. Let's go back to MEM1, clicky,

113
00:06:20,590 --> 00:06:23,860
clicky, click. Good repetition here. Good adult learning,

114
00:06:23,860 --> 00:06:24,430
right?

115
00:06:24,430 --> 00:06:27,340
Failover, Fail Over.

116
00:06:27,340 --> 00:06:28,440
Okay.

117
00:06:28,440 --> 00:06:30,390
And then, as we would expect,

118
00:06:30,390 --> 00:06:33,930
we're going to want to reverse replication one more time to

119
00:06:33,930 --> 00:06:37,570
reestablish the original directionality of the replication.

120
00:06:37,570 --> 00:06:38,810
So there you have it.

121
00:06:38,810 --> 00:06:48,000
I hope you're impressed with how straightforward the replication process is when you're doing Hyper‑V Replica here in Windows Server.