1 00:00:01,040 --> 00:00:02,180 In this demonstration, 2 00:00:02,180 --> 00:00:05,910 we're going to do a very light touch introduction to MABS, the 3 00:00:05,910 --> 00:00:09,810 Microsoft Azure Backup Server. You saw at the end of the previous 4 00:00:09,810 --> 00:00:13,030 demo that if you're configuring your Recovery Services vault to 5 00:00:13,030 --> 00:00:15,050 back up off‑cloud workloads, 6 00:00:15,050 --> 00:00:18,450 particularly Microsoft ones, that's the exam alert here if you're 7 00:00:18,450 --> 00:00:21,150 asked about backing up on‑premises Exchange, 8 00:00:21,150 --> 00:00:25,700 SQL Server, SharePoint, and particularly bare metal recovery. The MABS, 9 00:00:25,700 --> 00:00:29,440 or Microsoft Azure Backup Server, is a free download. 10 00:00:29,440 --> 00:00:31,130 It takes a while to install. 11 00:00:31,130 --> 00:00:35,740 You'll definitely want to pay close attention to the docs and follow it along. 12 00:00:35,740 --> 00:00:38,200 I have installed it, I should say, 13 00:00:38,200 --> 00:00:43,980 on a Windows Server 2019 machine. You do have to have SQL Server, so 14 00:00:43,980 --> 00:00:47,940 got SQL Server 2017 installed on this machine. 15 00:00:47,940 --> 00:00:52,200 And once you've got the Azure Backup Server loaded up, it's a question 16 00:00:52,200 --> 00:00:54,950 of mastering the learning curve of the interface, 17 00:00:54,950 --> 00:00:58,970 which isn't particularly user‑friendly, in my humble opinion. Let me just give 18 00:00:58,970 --> 00:01:02,140 you the high‑level view of what you've got going on here. 19 00:01:02,140 --> 00:01:04,140 So if we go down under Management, 20 00:01:04,140 --> 00:01:10,340 you are going to need to register the Azure Backup Server with the RS vault. 21 00:01:10,340 --> 00:01:10,760 And again, 22 00:01:10,760 --> 00:01:15,020 you do that using the vault credentials that we talked about before, you see. 23 00:01:15,020 --> 00:01:18,270 So we go to Register. Are you using a proxy? 24 00:01:18,270 --> 00:01:18,660 No. 25 00:01:18,660 --> 00:01:22,550 Where is your vault credential? So, onboarding MABS into the Recovery 26 00:01:22,550 --> 00:01:26,870 Services vault is actually the easiest part. More to the point, you need 27 00:01:26,870 --> 00:01:31,250 to configure disk storage, local storage because the idea is that you can 28 00:01:31,250 --> 00:01:33,520 do disk‑to‑disk to cloud backups. 29 00:01:33,520 --> 00:01:37,580 So, you can keep your backups locally and have a copy go 30 00:01:37,580 --> 00:01:39,460 up to the Recovery Services vault. 31 00:01:39,460 --> 00:01:43,810 So I've brought in an e‑volume here to serve as my local disk 32 00:01:43,810 --> 00:01:48,400 storage. And then we can enumerate our protected servers. Looks 33 00:01:48,400 --> 00:01:50,770 like my agent is out of date here. 34 00:01:50,770 --> 00:01:52,330 And as you can see, 35 00:01:52,330 --> 00:01:57,400 the MABS interface allows you to centrally manage the agent 36 00:01:57,400 --> 00:02:01,010 that you'll need to install on each machine. And you see the 37 00:02:01,010 --> 00:02:02,680 text is probably pretty small, 38 00:02:02,680 --> 00:02:07,920 but down below it's referencing DPM DPM administrator console. You're 39 00:02:07,920 --> 00:02:11,610 going to see some of those things that may scratch your head if you don't 40 00:02:11,610 --> 00:02:16,210 understand, fortunately, you do, that MABS is simply a stripped‑down 41 00:02:16,210 --> 00:02:21,650 version of the licensed product, the commercial product, System Center 42 00:02:21,650 --> 00:02:24,840 Data Protection Manager, or DPM. 43 00:02:24,840 --> 00:02:27,420 So once you've got the back end up and running, 44 00:02:27,420 --> 00:02:29,940 you'll want to go over to Protection, and you wind up 45 00:02:29,940 --> 00:02:33,740 creating what are called protection groups. And I created one 46 00:02:33,740 --> 00:02:36,660 protection group called SQL‑DPM‑DB, 47 00:02:36,660 --> 00:02:40,750 where I've enlisted one computer, which is this one, and then 48 00:02:40,750 --> 00:02:45,040 I've gone in and selected a workload to protect. 49 00:02:45,040 --> 00:02:48,650 And those workloads can be very flexible, as you can see here. 50 00:02:48,650 --> 00:02:53,970 I have specifically selected protection in terms of SQL Server 51 00:02:53,970 --> 00:02:57,500 databases, and I'm right‑clicking a lot, and you can see a lot of 52 00:02:57,500 --> 00:03:00,140 the options that show up when you do that. 53 00:03:00,140 --> 00:03:03,930 If you click New, it's going to walk you through creating a new protection group. 54 00:03:03,930 --> 00:03:07,690 Let me just quickly show you that. I'm going to back up servers, of 55 00:03:07,690 --> 00:03:11,810 course, and then we're asked to enumerate any members here. 56 00:03:11,810 --> 00:03:15,740 I've deployed to DC1 and WIN2019. 57 00:03:15,740 --> 00:03:17,570 We can grab file shares. 58 00:03:17,570 --> 00:03:21,890 We can grab entire volumes. If there's any workloads, like in this 59 00:03:21,890 --> 00:03:25,540 case, it's a domain controller, so there's Active Directory. I'm 60 00:03:25,540 --> 00:03:27,650 just going to grab my shares folder here. 61 00:03:27,650 --> 00:03:30,610 What does it say? You've already enabled protection for this if 62 00:03:30,610 --> 00:03:34,140 you want to protect it. I don't want System State. I just want to 63 00:03:34,140 --> 00:03:37,060 grab this backup of this file share. 64 00:03:37,060 --> 00:03:41,270 Now if I expand Windows Server 2019, you can see that it's a Hyper‑V 65 00:03:41,270 --> 00:03:45,130 server, so we can bring up host and individual VMs. 66 00:03:45,130 --> 00:03:48,500 It's a SQL Server, so we can enumerate that workload. 67 00:03:48,500 --> 00:03:53,880 This is one of the nice benefits of DPM and Azure Backup Server, 68 00:03:53,880 --> 00:03:57,460 as I've said before. Do you want to use short‑term protection 69 00:03:57,460 --> 00:03:59,830 on disk, or do you just want to do online? 70 00:03:59,830 --> 00:04:01,700 What's the name of the protection group? 71 00:04:01,700 --> 00:04:05,740 I'll call it DC1‑Shares. Click Next. 72 00:04:05,740 --> 00:04:07,400 What is our retention range? 73 00:04:07,400 --> 00:04:12,450 Our recovery point objective? Just verifying if we have enough storage locally 74 00:04:12,450 --> 00:04:15,850 to handle the backup. Are we going to go over the network? 75 00:04:15,850 --> 00:04:20,320 Are we going to do it now, later, or manually? Consistency checking, 76 00:04:20,320 --> 00:04:23,090 select the data source you want to protect online. 77 00:04:23,090 --> 00:04:23,570 Okay. 78 00:04:23,570 --> 00:04:29,150 Here's our backup interval. Here is our retention, transfer over the 79 00:04:29,150 --> 00:04:32,700 network, Create Group, and then we're off and running. 80 00:04:32,700 --> 00:04:37,660 So that's just a really quick and fast little explanation about how 81 00:04:37,660 --> 00:04:40,110 to get off the ground with Azure Backup Server. 82 00:04:40,110 --> 00:04:40,860 But ultimately, 83 00:04:40,860 --> 00:04:44,900 I think you saw that the vault credential is really what unlocks 84 00:04:44,900 --> 00:04:47,570 that registration between your local solution, 85 00:04:47,570 --> 00:04:53,190 whether it's the individual MARS agent, or if it's using the much more robust 86 00:04:53,190 --> 00:04:59,190 MABS, or Azure Backup Server solution. Ah, looks like I've got an agent 87 00:04:59,190 --> 00:05:03,550 incompatibility here, and we can go through and troubleshoot that. I'm not 88 00:05:03,550 --> 00:05:09,000 going to, and you don't have to sit through it. I'll call this demo done now.