1
00:00:01,040 --> 00:00:05,600
So once the Azure Migrate appliance has discovered your servers and your VMs,

2
00:00:05,600 --> 00:00:10,680
it now has a way to monitor them, and let it do so for a long time,

3
00:00:10,680 --> 00:00:13,750
and that way you'll get a higher confidence rating.

4
00:00:13,750 --> 00:00:16,560
Ultimately, you're looking at a couple of things here, aren't you?

5
00:00:16,560 --> 00:00:20,010
You're looking at what is this machine's readiness for Azure?

6
00:00:20,010 --> 00:00:25,340
Yes, yes, with conditions not ready, readiness unknown.

7
00:00:25,340 --> 00:00:28,100
Looks like I really didn't wait at all honestly.

8
00:00:28,100 --> 00:00:31,340
As soon as the discovery was finished, I created the assessment.

9
00:00:31,340 --> 00:00:36,470
So, notice that the engine here logically hasn't even determined the OS.

10
00:00:36,470 --> 00:00:40,740
It made a good guess, and it's correct, it is Windows Server 2022.

11
00:00:40,740 --> 00:00:43,500
Though the Azure readiness is an important piece,

12
00:00:43,500 --> 00:00:45,670
you can export these assessments.

13
00:00:45,670 --> 00:00:48,930
They come out as Excel files, and they're really nice and formatted,

14
00:00:48,930 --> 00:00:52,840
they're pretty much presentation‑ready right out of the box.

15
00:00:52,840 --> 00:00:56,580
The other thing you're concerned with it seems to me are the cost details.

16
00:00:56,580 --> 00:01:00,340
How much is this migration going to cost?

17
00:01:00,340 --> 00:01:01,910
And so, you've got your compute,

18
00:01:01,910 --> 00:01:05,490
as long as the virtual machine in Azure is allocated and running,

19
00:01:05,490 --> 00:01:08,820
you're being billed, and then there's the storage cost depending

20
00:01:08,820 --> 00:01:11,840
upon what kind of managed disk you're using.

21
00:01:11,840 --> 00:01:15,670
All right? so you might think, okay, so far so good, all right.

22
00:01:15,670 --> 00:01:17,610
We've configured the appliance.

23
00:01:17,610 --> 00:01:19,570
We've discovered our infrastructure.

24
00:01:19,570 --> 00:01:20,520
Optionally,

25
00:01:20,520 --> 00:01:25,140
we might have deeper insight with dependency analysis and software inventory.

26
00:01:25,140 --> 00:01:29,740
We've created our assessment here and put in our specifications,

27
00:01:29,740 --> 00:01:34,140
and that deliverable is awesome, it really gives us a good idea,

28
00:01:34,140 --> 00:01:36,920
but how do we then use that assessment?

29
00:01:36,920 --> 00:01:40,270
See, because now that we're finished with the discovery and assessment phase,

30
00:01:40,270 --> 00:01:43,700
it's time for us to come to the migration phase.

31
00:01:43,700 --> 00:01:45,590
And this here also says Discover.

32
00:01:45,590 --> 00:01:47,140
What in the world?

33
00:01:47,140 --> 00:01:48,890
Why would it discover again?

34
00:01:48,890 --> 00:01:50,120
I'm bleeding you.

35
00:01:50,120 --> 00:01:53,310
The good news is we can actually use that assessment,

36
00:01:53,310 --> 00:01:58,640
that output, as input to the server migration process.

37
00:01:58,640 --> 00:02:00,440
So when we step through Discovery here,

38
00:02:00,440 --> 00:02:04,240
it asks you what is your virtualization platform,

39
00:02:04,240 --> 00:02:08,440
and then it tells us again, depending upon what your scenario is,

40
00:02:08,440 --> 00:02:09,640
what to do.

41
00:02:09,640 --> 00:02:10,460
With Hyper‑V,

42
00:02:10,460 --> 00:02:13,000
it's a Microsoft virtualization product so it's

43
00:02:13,000 --> 00:02:15,440
officially an agentless approach,

44
00:02:15,440 --> 00:02:18,900
but you still do need to install this Azure Site Recovery

45
00:02:18,900 --> 00:02:22,420
provider agent on not your individual VMs,

46
00:02:22,420 --> 00:02:24,720
fortunately, but your Hyper‑V hosts.

47
00:02:24,720 --> 00:02:25,640
All right?

48
00:02:25,640 --> 00:02:26,760
So you do need that.

49
00:02:26,760 --> 00:02:28,880
Now if you're going to go the route of VMware,

50
00:02:28,880 --> 00:02:33,430
you need to have vSphere, absolutely, and there's two approaches here.

51
00:02:33,430 --> 00:02:36,970
And there's a Docs article that helps you choose whether you want to do

52
00:02:36,970 --> 00:02:40,850
agentless or agent‑based, there's some differences there,

53
00:02:40,850 --> 00:02:44,500
and the Azure Migrate appliance comes down as an OVA file that

54
00:02:44,500 --> 00:02:47,740
you can get going in your VMware environment.

55
00:02:47,740 --> 00:02:49,900
And then physical, it's very similar.

56
00:02:49,900 --> 00:02:54,740
Do you want to install a new replication appliance or scale out an existing?

57
00:02:54,740 --> 00:03:00,440
And there you've got, again, the configuration server virtual appliance.

58
00:03:00,440 --> 00:03:01,220
So that is that.

59
00:03:01,220 --> 00:03:02,480
Let me go back to Hyper‑V.

60
00:03:02,480 --> 00:03:06,580
And that's, I've already finished the discovery and the registration.

61
00:03:06,580 --> 00:03:09,490
So the discovery really should be registration,

62
00:03:09,490 --> 00:03:13,250
where we're making sure that the output of our discovery up

63
00:03:13,250 --> 00:03:16,540
here is being fed into the migration.

64
00:03:16,540 --> 00:03:19,540
The heavy lifting comes in here with Replicate,

65
00:03:19,540 --> 00:03:24,240
because here, we are again going to choose our scenario,

66
00:03:24,240 --> 00:03:28,820
and then here's the magic, apply migration settings from our assessment.

67
00:03:28,820 --> 00:03:30,340
I love this.

68
00:03:30,340 --> 00:03:32,420
So we bring in our core‑1 assessment.

69
00:03:32,420 --> 00:03:33,590
Now I've already done this,

70
00:03:33,590 --> 00:03:37,140
so it's not allowing me to select another virtual machine,

71
00:03:37,140 --> 00:03:40,230
but based on your assessment, if you're doing this in phases,

72
00:03:40,230 --> 00:03:43,170
you'll have only the VMs that are associated with a

73
00:03:43,170 --> 00:03:46,830
given assessment show up in this list, and then you can proceed.

74
00:03:46,830 --> 00:03:50,540
It's not letting me proceed but you've got Target settings,

75
00:03:50,540 --> 00:03:53,150
where are you going to place the virtual machines,

76
00:03:53,150 --> 00:03:57,550
any overrides with compute, and disks, and taxonomic tags,

77
00:03:57,550 --> 00:04:01,840
and then everything is good, review and start replication,

78
00:04:01,840 --> 00:04:05,080
and then it's going to be a replication process that could take a while.

79
00:04:05,080 --> 00:04:08,620
Another good reason to use phases here is that you don't

80
00:04:08,620 --> 00:04:11,370
saturate your internet connection too much.

81
00:04:11,370 --> 00:04:13,060
So at this point, as you can see,

82
00:04:13,060 --> 00:04:16,430
I've got two discovered servers and one that's replicating.

83
00:04:16,430 --> 00:04:19,240
And again, these are all live hyperlinks.

84
00:04:19,240 --> 00:04:20,080
So let's see here,

85
00:04:20,080 --> 00:04:26,040
we've got core1 that is healthy and protected so it's really ready to go.

86
00:04:26,040 --> 00:04:29,640
That other VM there is in a messed‑up state and that's fine.

87
00:04:29,640 --> 00:04:31,480
Can I actually remove it from here?

88
00:04:31,480 --> 00:04:32,010
Yeah,

89
00:04:32,010 --> 00:04:36,130
I can actually force a stop replication because I'm not going

90
00:04:36,130 --> 00:04:38,590
to do anything with that particular machine.

91
00:04:38,590 --> 00:04:42,610
And if you have already seen my modules on Azure Site Recovery,

92
00:04:42,610 --> 00:04:47,120
you know about the difference between a test failover and a real failover.

93
00:04:47,120 --> 00:04:49,010
You have a similar idea here.

94
00:04:49,010 --> 00:04:53,340
Let me come out of here and go to Migrate.

95
00:04:53,340 --> 00:04:57,220
Shutdown machines before migration to minimize data loss?

96
00:04:57,220 --> 00:04:58,640
Yes or No.

97
00:04:58,640 --> 00:05:01,500
What virtual machine are you ready to do your migrate?

98
00:05:01,500 --> 00:05:06,000
And then, migrate. It's pretty easy, isn't it?