1
00:00:01,140 --> 00:00:02,210
In this demonstration,

2
00:00:02,210 --> 00:00:04,650
I'll show you how to back up Windows Server to the

3
00:00:04,650 --> 00:00:06,760
Azure Recovery Services vault.

4
00:00:06,760 --> 00:00:09,570
What you're looking at right now is the desktop of one of

5
00:00:09,570 --> 00:00:12,740
my many Windows Server 2022 machines.

6
00:00:12,740 --> 00:00:16,980
Let me open up an elevated PowerShell console and do a hostname.

7
00:00:16,980 --> 00:00:21,510
So this is mem2.timw.info, just a member server.

8
00:00:21,510 --> 00:00:24,030
And let me look at my command history because I was

9
00:00:24,030 --> 00:00:26,190
playing around before I started recording,

10
00:00:26,190 --> 00:00:29,900
and I did a Get‑WindowsFeature "backup" to verify that Windows

11
00:00:29,900 --> 00:00:32,750
Server Backup is available but not yet installed.

12
00:00:32,750 --> 00:00:36,650
So let's go ahead and do an Install‑WindowsFeature windows,

13
00:00:36,650 --> 00:00:41,940
if I can type, and I'll include the management tools.

14
00:00:41,940 --> 00:00:45,680
I don't think we'll need to restart, but just in case, I'll add that flag.

15
00:00:45,680 --> 00:00:52,540
Now I will type wbadmin to open the wbadmin command‑line tool.

16
00:00:52,540 --> 00:00:55,320
This is something that I just want you to be aware of as far

17
00:00:55,320 --> 00:00:58,070
as scripting local Windows Server Backup.

18
00:00:58,070 --> 00:01:04,100
I want to open the GUI console though, Windows server Backup, because I want to

19
00:01:04,100 --> 00:01:07,630
verify that right now it's truly a local backup solution.

20
00:01:07,630 --> 00:01:08,800
Why am I showing you this?

21
00:01:08,800 --> 00:01:10,280
Well, as I mentioned,

22
00:01:10,280 --> 00:01:13,950
if you're looking to back up individual Windows Server machines in

23
00:01:13,950 --> 00:01:17,040
a workgroup or Active Directory domain, you're going to need the

24
00:01:17,040 --> 00:01:20,950
Microsoft Azure Recovery Services, or MARS, agent, and that will

25
00:01:20,950 --> 00:01:24,370
extend this wbadmin console.

26
00:01:24,370 --> 00:01:24,680
Okay,

27
00:01:24,680 --> 00:01:28,120
so that's one machine on‑prem that we're going to enlist into our

28
00:01:28,120 --> 00:01:31,450
Recovery Services vault. Here we are in the Azure portal.

29
00:01:31,450 --> 00:01:35,350
I actually want to go over to Azure Arc to show you that I've

30
00:01:35,350 --> 00:01:38,790
onboarded another machine in my on‑premises domain.

31
00:01:38,790 --> 00:01:45,550
This is mem1.timw.info. Azure Arc for servers is a process where you

32
00:01:45,550 --> 00:01:49,400
install what's called the connected machine agent into an on‑premises

33
00:01:49,400 --> 00:01:53,390
Windows or Linux machine, and now we can do quite a bit of Azure

34
00:01:53,390 --> 00:01:57,500
administration and without any dependency on ExpressRoute or a

35
00:01:57,500 --> 00:02:01,540
site‑to‑site VPN in a very clean and nice way.

36
00:02:01,540 --> 00:02:06,360
So note that I've got mem1 already enlisted in Azure Arc. That's not a

37
00:02:06,360 --> 00:02:09,470
requirement. I'm just showing you a couple options.

38
00:02:09,470 --> 00:02:14,240
The MARS agent is one option for onboarding on‑prem machines.

39
00:02:14,240 --> 00:02:17,270
The Azure Arc for servers is another one.

40
00:02:17,270 --> 00:02:19,680
And in the second demo in this module,

41
00:02:19,680 --> 00:02:22,520
I'll show you the MABS, Azure Backup Server.

42
00:02:22,520 --> 00:02:24,440
That's yet another way to go.

43
00:02:24,440 --> 00:02:26,850
So let's head on over to Recovery Services vaults.

44
00:02:26,850 --> 00:02:28,440
Let me adjust my zoom.

45
00:02:28,440 --> 00:02:33,370
Now you'll see that my primary vault, az801‑rg‑vault is in East US.

46
00:02:33,370 --> 00:02:34,920
This is an exam alert.

47
00:02:34,920 --> 00:02:38,160
Now, when it comes to backing up your Azure VMs,

48
00:02:38,160 --> 00:02:40,240
you're going to need to make sure that the Recovery

49
00:02:40,240 --> 00:02:42,740
Services vault is in the same region.

50
00:02:42,740 --> 00:02:44,990
So if you have VMs in multiple regions,

51
00:02:44,990 --> 00:02:47,640
you are looking at having multiple RS vaults.

52
00:02:47,640 --> 00:02:53,240
However, for Azure Arc and the MARS and MABS scenarios, location doesn't matter.

53
00:02:53,240 --> 00:02:58,130
So let's go into our vault, and we're going to come down under Getting

54
00:02:58,130 --> 00:03:01,850
started, Backup, and you're asked, first of all,

55
00:03:01,850 --> 00:03:03,280
where is your workload running?

56
00:03:03,280 --> 00:03:08,330
Is it in Azure, the Azure cloud in other words, Azure Stack, or on‑premises?

57
00:03:08,330 --> 00:03:12,810
Let's start with Azure. The templates that I told you about are right here.

58
00:03:12,810 --> 00:03:15,340
We can protect Azure file shares,

59
00:03:15,340 --> 00:03:18,650
Azure VMs running particular database products, but we're

60
00:03:18,650 --> 00:03:21,070
going to do a standard virtual machine backup.

61
00:03:21,070 --> 00:03:24,000
Let's click Backup, and were asked here,

62
00:03:24,000 --> 00:03:27,260
what kind of backup policy are we looking at here?

63
00:03:27,260 --> 00:03:28,550
Standard or Enhanced?

64
00:03:28,550 --> 00:03:30,840
That's going to be our service tier.

65
00:03:30,840 --> 00:03:35,330
As you can see, there's some additional features. Because the Enhanced is in

66
00:03:35,330 --> 00:03:39,330
public preview, or at least part of it, that's not going to be in scope for our

67
00:03:39,330 --> 00:03:43,120
cert exam, so we're going to stay with Standard where we're doing daily

68
00:03:43,120 --> 00:03:46,310
backups. And as far as our backup policy goes,

69
00:03:46,310 --> 00:03:48,110
let me show you the components of that.

70
00:03:48,110 --> 00:03:54,570
We'll click Create a new policy. I'll call this az801‑policy. And

71
00:03:54,570 --> 00:03:58,780
our daily backup here can be in whatever time in our time zone. I'm

72
00:03:58,780 --> 00:04:04,030
going to choose 2:30 AM, and my particular time zone is ‑06:00

73
00:04:04,030 --> 00:04:05,900
Central, so let me find that.

74
00:04:05,900 --> 00:04:09,350
Where are you Central? There you are. The Instant Restore, like I said,

75
00:04:09,350 --> 00:04:10,910
is between 1 and 5.

76
00:04:10,910 --> 00:04:12,460
I love this feature a lot.

77
00:04:12,460 --> 00:04:16,010
I'm going to max it out. And then we have our retention range.

78
00:04:16,010 --> 00:04:21,070
How long do you need the RS vault to keep daily snapshots weekly,

79
00:04:21,070 --> 00:04:24,440
monthly, and yearly? I'll leave those at the default right now.

80
00:04:24,440 --> 00:04:26,490
We can take care of changing that.

81
00:04:26,490 --> 00:04:29,610
Of course, the policy is a separate artifact, and we can

82
00:04:29,610 --> 00:04:32,840
always go back and change it after the fact.

83
00:04:32,840 --> 00:04:37,200
And then lastly, we have this optional Azure Backup Resource Group.

84
00:04:37,200 --> 00:04:41,200
Azure Backup will create a default resource group, as you see here,

85
00:04:41,200 --> 00:04:45,460
AzureBackupRG_{Geo}_{n). I'm going to leave that alone. But it's nice

86
00:04:45,460 --> 00:04:49,380
because I'm sure Microsoft received a lot of customer complaints

87
00:04:49,380 --> 00:04:53,540
saying that the default separate resource group you create violates

88
00:04:53,540 --> 00:04:55,240
our naming standards, you see,

89
00:04:55,240 --> 00:05:00,000
so that's convenient and thoughtful of Microsoft to do. All right.