1 00:00:01,040 --> 00:00:05,740 In this demonstration, I'll show you how ASR, Azure Site Recovery, works. 2 00:00:05,740 --> 00:00:08,730 Let me open up the Azure portal here and zoom in a little bit. You 3 00:00:08,730 --> 00:00:11,090 can see I have two Recovery Services vaults. 4 00:00:11,090 --> 00:00:15,660 My primary one here where my workloads are is East US, and 5 00:00:15,660 --> 00:00:18,400 then I'm using West US as my failover. 6 00:00:18,400 --> 00:00:21,080 So let me show you how to set up ASR. 7 00:00:21,080 --> 00:00:23,270 It's going to depend on whether you're protecting 8 00:00:23,270 --> 00:00:25,410 Azure machines or on‑prem machines. 9 00:00:25,410 --> 00:00:29,670 Let's go into my primary vault, and we'll come down here under Getting 10 00:00:29,670 --> 00:00:34,540 started, Site Recovery, and we see this interface, I guess, for lack of 11 00:00:34,540 --> 00:00:38,220 a better term, that shows you the different topologies, if you're going 12 00:00:38,220 --> 00:00:41,040 to do Azure to Azure protection, 13 00:00:41,040 --> 00:00:46,540 if you're looking to protect VMware or Hyper‑V machines into Azure, 14 00:00:46,540 --> 00:00:49,080 if you're going to do cloud to local, 15 00:00:49,080 --> 00:00:52,000 all the different topologies. What I want you to see 16 00:00:52,000 --> 00:00:53,950 is from a top‑line perspective, 17 00:00:53,950 --> 00:00:58,340 it's incredibly easy to replicate your virtual machines from region to 18 00:00:58,340 --> 00:01:02,190 region. To show you that, actually, let me open up another browser tab as I 19 00:01:02,190 --> 00:01:06,850 normally do, and we could go to an individual VM here in the portal. I'll 20 00:01:06,850 --> 00:01:13,140 grab one that's running here. Let's pick on web1, and just like how we can 21 00:01:13,140 --> 00:01:16,200 enable backup on a single VM basis, 22 00:01:16,200 --> 00:01:19,890 we can go to disaster recovery, and with a couple of mouse clicks, 23 00:01:19,890 --> 00:01:22,680 you've got yourself this failover relationship. 24 00:01:22,680 --> 00:01:26,430 Now, the issue with this is that this makes it really easy to 25 00:01:26,430 --> 00:01:29,480 replicate Azure to Azure, region to region, 26 00:01:29,480 --> 00:01:34,020 but this would lead you to think that there is not any orchestration. 27 00:01:34,020 --> 00:01:37,400 The point of ASR really isn't so much protecting 28 00:01:37,400 --> 00:01:41,040 individual VMs, it's entire workloads. 29 00:01:41,040 --> 00:01:44,860 So the two main paths that I want you to look at for the purpose 30 00:01:44,860 --> 00:01:48,410 of the exam are Hyper‑V protection on one hand, 31 00:01:48,410 --> 00:01:50,490 and VMware protection on the other. 32 00:01:50,490 --> 00:01:53,280 So, if we look at the Hyper‑V scenario, 33 00:01:53,280 --> 00:01:55,970 we prepare the infrastructure, and it's going to 34 00:01:55,970 --> 00:01:57,840 step us through a number of steps, 35 00:01:57,840 --> 00:02:01,460 including verifying that we've run the deployment planner. 36 00:02:01,460 --> 00:02:04,240 The Azure Site Recovery deployment planner, 37 00:02:04,240 --> 00:02:04,890 believe it or not, 38 00:02:04,890 --> 00:02:09,980 is a command‑line executable that you can use to inspect your local environment. 39 00:02:09,980 --> 00:02:13,150 Once you've done that, you're ready to start setting things up. 40 00:02:13,150 --> 00:02:14,990 And as you can see, it asks, 41 00:02:14,990 --> 00:02:18,170 are you orchestrating your Hyper‑V hosts with System 42 00:02:18,170 --> 00:02:21,440 Center Virtual Machine Manager, which I'll say no. 43 00:02:21,440 --> 00:02:24,620 And then you create what's called a site. 44 00:02:24,620 --> 00:02:26,300 The site might be, for instance, 45 00:02:26,300 --> 00:02:31,160 a particular data center into which you then add one or more 46 00:02:31,160 --> 00:02:34,360 Hyper‑V servers. And you can see I've already added one in, 47 00:02:34,360 --> 00:02:38,380 mem3.timw.info. What does that mean? 48 00:02:38,380 --> 00:02:43,550 Well, Microsoft made this to where you have minimal reliance on agents. 49 00:02:43,550 --> 00:02:44,450 In other words, 50 00:02:44,450 --> 00:02:49,230 what you need to do is install the Microsoft Azure Site Recovery provider 51 00:02:49,230 --> 00:02:55,560 and install that agent on each of your Hyper‑V hosts. Not the guest VMs, 52 00:02:55,560 --> 00:03:00,660 understand, the Hyper‑V hosts. When you install that Azure Site Recovery 53 00:03:00,660 --> 00:03:03,040 provider on your Hyper‑V hosts, 54 00:03:03,040 --> 00:03:06,330 you'll then handshake or register into the Recovery 55 00:03:06,330 --> 00:03:10,320 Services vault by importing this vault registration key 56 00:03:10,320 --> 00:03:12,740 that you download in a separate step. 57 00:03:12,740 --> 00:03:16,920 So the bottom line is, it's a much lighter impact to your 58 00:03:16,920 --> 00:03:19,850 on‑premises environment when you're looking to replicate 59 00:03:19,850 --> 00:03:21,780 and protect local machines. 60 00:03:21,780 --> 00:03:22,740 All right. 61 00:03:22,740 --> 00:03:26,140 So you step through and you choose your sites and servers, 62 00:03:26,140 --> 00:03:28,300 and then you determine target settings, 63 00:03:28,300 --> 00:03:32,840 which is going to be where you want the failover to take place. 64 00:03:32,840 --> 00:03:37,560 I've configured mine to failover to the West US where I've created 65 00:03:37,560 --> 00:03:41,200 a recovery plan, and so on, and I'll show you that momentarily. And 66 00:03:41,200 --> 00:03:43,280 then we have a replication policy. 67 00:03:43,280 --> 00:03:45,060 What is a replication policy? 68 00:03:45,060 --> 00:03:48,120 Well, it's analogous to a backup policy. 69 00:03:48,120 --> 00:03:52,510 You specify what source, in this case, it's Hyper‑V, what your 70 00:03:52,510 --> 00:03:55,730 target is, and then your copy frequency, 71 00:03:55,730 --> 00:04:00,260 how many recovery points and snapshots you want, a little bit of 72 00:04:00,260 --> 00:04:04,540 metadata on how the actual replication will take place. 73 00:04:04,540 --> 00:04:09,320 Now it gets more complicated when you have a VMware environment. Let's go into 74 00:04:09,320 --> 00:04:13,470 Prepare Infrastructure there, and you're going to have to download a 75 00:04:13,470 --> 00:04:19,550 pre‑configured virtual machine image. This is a Windows server eval licensed 76 00:04:19,550 --> 00:04:21,770 image that you'll stand up in your environment. 77 00:04:21,770 --> 00:04:22,150 Now, 78 00:04:22,150 --> 00:04:28,640 another requirement is that you have to have your ESXi hosts, your VMware 79 00:04:28,640 --> 00:04:34,390 hosts, orchestrated under vCenter. So you're going to need to work. In fact, 80 00:04:34,390 --> 00:04:39,700 this ASR replication appliance will work in conjunction with vCenter, and 81 00:04:39,700 --> 00:04:44,340 that allows you to get past having to worry about installing agents on every 82 00:04:44,340 --> 00:04:46,640 one of your virtual machines. 83 00:04:46,640 --> 00:04:51,350 What is the purpose of that Prepare Infrastructure step for Hyper‑V and 84 00:04:51,350 --> 00:04:57,890 VMware? It's enabling you to equip those virtualization hosts to enumerate 85 00:04:57,890 --> 00:05:03,000 the VMs and make them then available when you enable replication and then 86 00:05:03,000 --> 00:05:05,410 ultimately create your recovery plans. 87 00:05:05,410 --> 00:05:09,380 You see what I mean? When you set up replication for 88 00:05:09,380 --> 00:05:11,070 Hyper‑V, as you can see again, 89 00:05:11,070 --> 00:05:14,630 you specify your Hyper‑V site to start with, and then 90 00:05:14,630 --> 00:05:16,650 you set up your target environment. 91 00:05:16,650 --> 00:05:21,250 In this case, I want my local Hyper‑V infrastructure and VMs to 92 00:05:21,250 --> 00:05:26,900 failover into my DR, or Disaster Recovery VNet, and then I would 93 00:05:26,900 --> 00:05:29,640 select which subnet or subnets. 94 00:05:29,640 --> 00:05:34,350 Now, the virtual machine selection is important because the idea, again, 95 00:05:34,350 --> 00:05:37,580 is that you've got an orchestrated collection of 96 00:05:37,580 --> 00:05:47,000 machines that you want to replicate, you see? It's not just necessarily one. Let me select the DR subnet and click Next.