1
00:00:01,940 --> 00:00:04,480
All right, now that we've set up our backup policy,

2
00:00:04,480 --> 00:00:05,910
we'll add in some VMs,

3
00:00:05,910 --> 00:00:09,710
and these are going to assume Windows and Linux VMs running in Azure.

4
00:00:09,710 --> 00:00:11,590
Now, notice here that it says,

5
00:00:11,590 --> 00:00:16,110
Discovering VMs that can be backed up are in the same region as

6
00:00:16,110 --> 00:00:20,040
your vault and are not protected by another vault.

7
00:00:20,040 --> 00:00:23,100
And the idea here is you can do a multiple selection.

8
00:00:23,100 --> 00:00:29,060
I'm just going to protect web2 from my az801‑rg resource group and click OK.

9
00:00:29,060 --> 00:00:32,970
What exactly is happening now once I click Enable backup?

10
00:00:32,970 --> 00:00:38,090
Well, Azure is delivering the Azure Backup extension to that virtual machine,

11
00:00:38,090 --> 00:00:38,660
all right?

12
00:00:38,660 --> 00:00:42,100
So the RS vault, or the Recovery Services vault,

13
00:00:42,100 --> 00:00:46,420
is really the main way to enable backup for your Azure VMs at scale.

14
00:00:46,420 --> 00:00:51,000
Of course, you could use Azure CLI and PowerShell as usual.

15
00:00:51,000 --> 00:00:54,800
Another thing we could do, of course, is go to the virtual machines themselves.

16
00:00:54,800 --> 00:00:57,340
Here I'll pick on linux1.

17
00:00:57,340 --> 00:00:59,670
I must have already configured backup for this.

18
00:00:59,670 --> 00:01:04,040
But you'll see that backup is surfaced right in the portal settings.

19
00:01:04,040 --> 00:01:05,620
No, it's not, actually.

20
00:01:05,620 --> 00:01:09,910
And to set it up here is pretty easy on a VM‑by‑VM basis.

21
00:01:09,910 --> 00:01:12,620
You can just choose the same options that we saw.

22
00:01:12,620 --> 00:01:16,650
Of course, you still do need to have a Recovery Services vault, as you can see.

23
00:01:16,650 --> 00:01:18,120
Is this machine running?

24
00:01:18,120 --> 00:01:18,930
Let me go to Overview.

25
00:01:18,930 --> 00:01:22,520
Surprised it didn't show up in the list, actually.

26
00:01:22,520 --> 00:01:24,200
So, that is that.

27
00:01:24,200 --> 00:01:24,540
Now,

28
00:01:24,540 --> 00:01:29,350
what about the other option in the Recovery Services vault where you're

29
00:01:29,350 --> 00:01:31,790
looking at machines that are in other clouds or on‑prem?

30
00:01:31,790 --> 00:01:34,190
Let's go back to Recovery Services vaults.

31
00:01:34,190 --> 00:01:36,340
Let's go into our vault.

32
00:01:36,340 --> 00:01:38,560
We'll go back to where we were originally.

33
00:01:38,560 --> 00:01:40,880
In other words, we go under Getting Started, Backup.

34
00:01:40,880 --> 00:01:43,940
And this time, where is your workload running?

35
00:01:43,940 --> 00:01:46,340
Let's choose On‑Premises.

36
00:01:46,340 --> 00:01:46,650
Now,

37
00:01:46,650 --> 00:01:49,780
what happens or what the Recovery Services vault needs

38
00:01:49,780 --> 00:01:52,580
entirely depends on what you want to back up.

39
00:01:52,580 --> 00:01:56,040
If you just choose something relatively simple like

40
00:01:56,040 --> 00:01:58,330
Files and folders and System State,

41
00:01:58,330 --> 00:02:02,580
those are things we know that an individual Windows Server can do on its own,

42
00:02:02,580 --> 00:02:07,830
you'll find that when we go to prepare infrastructure we're installed,

43
00:02:07,830 --> 00:02:11,340
or we're prompted to install the Recovery Services agent,

44
00:02:11,340 --> 00:02:13,190
which I'll do right now on this machine,

45
00:02:13,190 --> 00:02:14,830
the MARS agent installer.

46
00:02:14,830 --> 00:02:18,690
And again, this is not going to be good for big production environments,

47
00:02:18,690 --> 00:02:23,200
but for individual machines, for your test dev study singleton machines,

48
00:02:23,200 --> 00:02:24,440
it's just fine.

49
00:02:24,440 --> 00:02:28,820
So here I'm going to accept the default location for the binaries and the cache.

50
00:02:28,820 --> 00:02:30,470
I'm not using a proxy.

51
00:02:30,470 --> 00:02:35,440
It's going to ensure our prerequisites are available, which they are.

52
00:02:35,440 --> 00:02:40,940
So I'm basically doing a Next, Next, Finish kind of installation.

53
00:02:40,940 --> 00:02:43,910
Now we need to register the server with the vault.

54
00:02:43,910 --> 00:02:49,360
So let's Proceed to Registration, and were asked for vault credentials,

55
00:02:49,360 --> 00:02:51,400
which we can get right here in the portal.

56
00:02:51,400 --> 00:02:54,040
Download vault credentials.

57
00:02:54,040 --> 00:02:58,040
We have to verify that we've already downloaded the MARS agent,

58
00:02:58,040 --> 00:02:59,940
and I'll bring those down here.

59
00:02:59,940 --> 00:03:00,650
There it is.

60
00:03:00,650 --> 00:03:03,640
There's the credentials file, so let me minimize.

61
00:03:03,640 --> 00:03:06,940
Let's browse into our Downloads folder.

62
00:03:06,940 --> 00:03:07,920
There's the VaultCredentials.

63
00:03:07,920 --> 00:03:09,760
Let me double‑left‑click that.

64
00:03:09,760 --> 00:03:13,910
That's going to handshake the machine into the Recovery Services vault.

65
00:03:13,910 --> 00:03:17,680
In order to provide a salt to encrypt the backups,

66
00:03:17,680 --> 00:03:21,130
we need to either generate or create a complex

67
00:03:21,130 --> 00:03:25,440
passphrase and then store it somewhere.

68
00:03:25,440 --> 00:03:27,850
Let's see if I've got a D drive on the system.

69
00:03:27,850 --> 00:03:31,660
I don't, so I'm going to temporarily put it in the root of drive C.

70
00:03:31,660 --> 00:03:34,470
Of course, Azure Backup here will complain.

71
00:03:34,470 --> 00:03:35,820
Are you sure you want to do that?

72
00:03:35,820 --> 00:03:38,100
I'm going to answer Y just for now.

73
00:03:38,100 --> 00:03:42,240
Registering this server with Microsoft Azure Backup.

74
00:03:42,240 --> 00:03:42,490
All right,

75
00:03:42,490 --> 00:03:47,140
there's that warning here about storing the passphrase on the same disk.

76
00:03:47,140 --> 00:03:50,620
I'm going to launch the agent here, so let's click Close.

77
00:03:50,620 --> 00:03:56,380
What will happen is that we now have wbadmin, but it's got cloud capabilities.

78
00:03:56,380 --> 00:04:01,020
So we can come over here to Actions, and we can schedule a backup.

79
00:04:01,020 --> 00:04:05,210
And in this case, the backup is going to go out into the cloud.

80
00:04:05,210 --> 00:04:06,440
You see what I mean?

81
00:04:06,440 --> 00:04:09,710
So let me quickly step you through the Schedule Backup Wizard.

82
00:04:09,710 --> 00:04:13,500
We'll Add items, and you don't have too much to choose from.

83
00:04:13,500 --> 00:04:16,550
As I said, it's basically files and folders.

84
00:04:16,550 --> 00:04:21,140
I'll back up my IIS wwwroot directory on this web server.

85
00:04:21,140 --> 00:04:23,220
Its files and folders are at system state.

86
00:04:23,220 --> 00:04:25,940
we've got our default backup settings.

87
00:04:25,940 --> 00:04:28,340
We've got our retention policy, which comes,

88
00:04:28,340 --> 00:04:31,410
again, the option anyway, comes from Azure.

89
00:04:31,410 --> 00:04:34,790
But notice that we're not using an Azure Backup policy.

90
00:04:34,790 --> 00:04:38,440
We're doing it just for this one single machine.

91
00:04:38,440 --> 00:04:44,940
We're going to Transfer over the network, Files and Folders, and Finish.

92
00:04:44,940 --> 00:04:45,360
Okay,

93
00:04:45,360 --> 00:04:49,700
so we can follow the status of that job as we go on here. Because we

94
00:04:49,700 --> 00:04:53,740
registered the server to the cloud, we don't have to worry about

95
00:04:53,740 --> 00:04:57,440
handshaking or registration or choosing a location.

96
00:04:57,440 --> 00:05:00,940
It's just going to transparently put those backups up there.

97
00:05:00,940 --> 00:05:03,440
Now notice you can do a backup now,

98
00:05:03,440 --> 00:05:06,650
which is where we want to execute a backup at this moment,

99
00:05:06,650 --> 00:05:07,770
which I actually do.

100
00:05:07,770 --> 00:05:11,620
It's the same thing that I configured for the schedule. And this will

101
00:05:11,620 --> 00:05:15,440
actually run the job right now and put something in our vault.

102
00:05:15,440 --> 00:05:17,800
Let me close this and let it run in the background.

103
00:05:17,800 --> 00:05:21,780
We can change our properties here, not while the job is in progress though. We

104
00:05:21,780 --> 00:05:25,500
can open the Azure portal. So that's the singleton approach.

105
00:05:25,500 --> 00:05:28,640
It's not very flexible for obvious reasons.

106
00:05:28,640 --> 00:05:30,120
If we come back to the vault,

107
00:05:30,120 --> 00:05:33,540
I wanted to show you something else because I mentioned that

108
00:05:33,540 --> 00:05:36,370
Azure Arc‑enabled server, and I was frankly a little

109
00:05:36,370 --> 00:05:38,110
surprised that it didn't show up here.

110
00:05:38,110 --> 00:05:40,970
So if you come back to the vault, go to Backup,

111
00:05:40,970 --> 00:05:45,540
your workload is running in Azure, Virtual machine.

112
00:05:45,540 --> 00:05:49,380
If you come down to Add, it will gradually enumerate all

113
00:05:49,380 --> 00:05:51,740
the machines that are in your region.

114
00:05:51,740 --> 00:05:56,280
Eventually, I'm going to see that Arc server on here. It's just some latency.

115
00:05:56,280 --> 00:06:00,930
I just onboarded it not too long ago. And you saw just in the few minutes

116
00:06:00,930 --> 00:06:03,650
that I've been running this demo, when I first came in here,

117
00:06:03,650 --> 00:06:07,490
there were only two machines shown. This is all because I just

118
00:06:07,490 --> 00:06:09,950
started up those machines prior to recording,

119
00:06:09,950 --> 00:06:11,040
but in your environment,

120
00:06:11,040 --> 00:06:14,290
as long as those machines have been running for a while and your Azure

121
00:06:14,290 --> 00:06:17,310
Arc‑enabled servers have been connected for a while,

122
00:06:17,310 --> 00:06:20,790
you'll eventually see them show up in this list. Because after all, that is one

123
00:06:20,790 --> 00:06:26,170
of the great promises of Azure Arc, that you can manage these off‑cloud servers

124
00:06:26,170 --> 00:06:31,100
in many of the same ways that you can in Azure. Lastly, if we choose for our

125
00:06:31,100 --> 00:06:35,690
Azure Recovery Services vault option that we're backing up on‑prem, but instead

126
00:06:35,690 --> 00:06:37,100
of just Files and folders,

127
00:06:37,100 --> 00:06:42,940
we have something more robust like Hyper‑V, VMware, SQL Server bare metal,

128
00:06:42,940 --> 00:06:53,000
then we're going to be asked, are you using the System Center DPM? Otherwise, you'll want to use MABS, aAnd we'll cover that in the next demo.