1 00:00:01,140 --> 00:00:06,340 Now let's double‑click into Azure Migrate Server Migration specifically. 2 00:00:06,340 --> 00:00:09,160 So we're talking about themes here that are going to recur when we 3 00:00:09,160 --> 00:00:12,040 look at the different Azure Migrate scenarios. 4 00:00:12,040 --> 00:00:14,680 We're talking about inventory assessment, 5 00:00:14,680 --> 00:00:18,790 we're talking about replication, and then ultimately a migration, 6 00:00:18,790 --> 00:00:22,160 and we can do that for physical, as well as virtual machines. 7 00:00:22,160 --> 00:00:25,040 The VMs can be Hyper‑V or VMware. 8 00:00:25,040 --> 00:00:27,330 There are some VMware specific requirements. 9 00:00:27,330 --> 00:00:30,470 You can't just have a fleet of ESX hosts, 10 00:00:30,470 --> 00:00:34,100 you have to have those hosts orchestrated under vCenter, 11 00:00:34,100 --> 00:00:39,370 and then your Azure Migrate appliance connects and works with the vCenter, 12 00:00:39,370 --> 00:00:41,110 that's something just to keep in mind. 13 00:00:41,110 --> 00:00:44,040 You can read all this in the Microsoft docs, of course. 14 00:00:44,040 --> 00:00:44,900 Important point, 15 00:00:44,900 --> 00:00:48,980 there is no dependency on having a virtual private network or ExpressRoute. 16 00:00:48,980 --> 00:00:55,240 We're talking about TCP Port 443 with TLS SSL encryption, 17 00:00:55,240 --> 00:00:55,900 and again, 18 00:00:55,900 --> 00:01:01,610 remember that Azure Migrate is the successor to Azure Site Recovery 19 00:01:01,610 --> 00:01:04,980 because I've mentioned this elsewhere in the AZ‑801 training when we 20 00:01:04,980 --> 00:01:07,340 were learning about Azure Site Recovery. 21 00:01:07,340 --> 00:01:11,850 ASR is for replication and failover, its for disaster recovery, 22 00:01:11,850 --> 00:01:15,650 and you absolutely can do ASR to failover on‑premises 23 00:01:15,650 --> 00:01:19,170 workloads into Azure virtual machines, but then with ASR, 24 00:01:19,170 --> 00:01:21,830 you'll want to failback on‑prem, you see. 25 00:01:21,830 --> 00:01:24,570 Now it used to be before Azure Migrate that we could 26 00:01:24,570 --> 00:01:28,200 use or co‑opt ASR to do migration, 27 00:01:28,200 --> 00:01:32,240 we would do the failover and just not re‑enable replication, 28 00:01:32,240 --> 00:01:36,370 but now a much cleaner way to go and tend would be to use Azure Migrate. 29 00:01:36,370 --> 00:01:38,770 I just want to give you that heads up. 30 00:01:38,770 --> 00:01:39,560 Now, 31 00:01:39,560 --> 00:01:42,110 if you're wondering well what's the step‑by‑step here and 32 00:01:42,110 --> 00:01:44,000 how much do we have to know for the exam? 33 00:01:44,000 --> 00:01:46,740 Well, you definitely need to know the step‑by‑step here. 34 00:01:46,740 --> 00:01:49,240 So I've got it laid out in 6 steps. 35 00:01:49,240 --> 00:01:53,100 To do an Azure Migrate Server Migration, you create a project. 36 00:01:53,100 --> 00:01:56,740 You'll want to download and set up the Azure Migrate appliance, 37 00:01:56,740 --> 00:02:00,930 you'll configure the appliance to run a discovery and build out an 38 00:02:00,930 --> 00:02:05,540 assessment which you do in the Azure portal by providing hints. 39 00:02:05,540 --> 00:02:07,750 Once you've got your assessment results, 40 00:02:07,750 --> 00:02:09,500 you'll configure replication, 41 00:02:09,500 --> 00:02:12,490 finalize what your Azure infrastructure will look like. 42 00:02:12,490 --> 00:02:15,500 Once the storage and configuration have reached a 43 00:02:15,500 --> 00:02:19,260 protected or synchronized state, you'll perform a migration, 44 00:02:19,260 --> 00:02:22,160 which is a cutover to Azure, and then ongoing, 45 00:02:22,160 --> 00:02:23,470 you'll verify and monitor. 46 00:02:23,470 --> 00:02:26,340 So that's the bird's eye perspective. 47 00:02:26,340 --> 00:02:30,020 What about migrating your old physical servers into Azure? 48 00:02:30,020 --> 00:02:31,940 What do you need to keep in mind? 49 00:02:31,940 --> 00:02:32,070 Well, 50 00:02:32,070 --> 00:02:35,410 one thing is that Windows Server 2003 and SUSE Linux 51 00:02:35,410 --> 00:02:37,880 are not supported for Azure Migrate, 52 00:02:37,880 --> 00:02:43,740 so you're going to have to have as a baseline say Windows Server 2008 or later. 53 00:02:43,740 --> 00:02:44,850 The assessment types, 54 00:02:44,850 --> 00:02:48,330 and this isn't necessarily limited to physical server migration, 55 00:02:48,330 --> 00:02:52,690 but you can specify in your assessment that you want Azure to 56 00:02:52,690 --> 00:02:55,590 model and give recommendations for feature, 57 00:02:55,590 --> 00:03:00,110 or performance parity rather, as in on‑premises or performance based, 58 00:03:00,110 --> 00:03:04,460 The performance based is where it's more of a dynamic thing where 59 00:03:04,460 --> 00:03:08,190 the Azure Migrate appliance is looking at the peaks and valleys of 60 00:03:08,190 --> 00:03:11,020 the actual VM that you're inspecting, or in this case, 61 00:03:11,020 --> 00:03:13,280 the physical server that you're inventorying. 62 00:03:13,280 --> 00:03:15,240 Otherwise, you could just specify, 63 00:03:15,240 --> 00:03:20,490 try to match how the current physical server or virtual server is set up. 64 00:03:20,490 --> 00:03:21,240 It's just, 65 00:03:21,240 --> 00:03:25,240 it's going to be a preference thing that you might want to test a little bit. 66 00:03:25,240 --> 00:03:28,990 And then the Azure Migrate appliance is pretty much a given here 67 00:03:28,990 --> 00:03:32,160 for any Azure Migrate Server Migration process, 68 00:03:32,160 --> 00:03:36,040 but the Azure Migrate appliance is absolutely necessary when 69 00:03:36,040 --> 00:03:38,850 you're doing physical migration to Azure, 70 00:03:38,850 --> 00:03:41,240 as well as the VMware path. 71 00:03:41,240 --> 00:03:44,650 Also, the physical server migration requires an agent. 72 00:03:44,650 --> 00:03:46,580 There is not an agentless option here, 73 00:03:46,580 --> 00:03:53,000 and you'll install that agent on the physical server that you're migrating. Let's do a demo.