All right, now that we've set up our backup policy,
we'll add in some VMs,
and these are going to assume Windows and Linux VMs running in Azure.
Now, notice here that it says,
Discovering VMs that can be backed up are in the same region as
your vault and are not protected by another vault.
And the idea here is you can do a multiple selection.
I'm just going to protect web2 from my az801‑rg resource group and click OK.
What exactly is happening now once I click Enable backup?
Well, Azure is delivering the Azure Backup extension to that virtual machine,
all right?
So the RS vault, or the Recovery Services vault,
is really the main way to enable backup for your Azure VMs at scale.
Of course, you could use Azure CLI and PowerShell as usual.
Another thing we could do, of course, is go to the virtual machines themselves.
Here I'll pick on linux1.
I must have already configured backup for this.
But you'll see that backup is surfaced right in the portal settings.
No, it's not, actually.
And to set it up here is pretty easy on a VM‑by‑VM basis.
You can just choose the same options that we saw.
Of course, you still do need to have a Recovery Services vault, as you can see.
Is this machine running?
Let me go to Overview.
Surprised it didn't show up in the list, actually.
So, that is that.
Now,
what about the other option in the Recovery Services vault where you're
looking at machines that are in other clouds or on‑prem?
Let's go back to Recovery Services vaults.
Let's go into our vault.
We'll go back to where we were originally.
In other words, we go under Getting Started, Backup.
And this time, where is your workload running?
Let's choose On‑Premises.
Now,
what happens or what the Recovery Services vault needs
entirely depends on what you want to back up.
If you just choose something relatively simple like
Files and folders and System State,
those are things we know that an individual Windows Server can do on its own,
you'll find that when we go to prepare infrastructure we're installed,
or we're prompted to install the Recovery Services agent,
which I'll do right now on this machine,
the MARS agent installer.
And again, this is not going to be good for big production environments,
but for individual machines, for your test dev study singleton machines,
it's just fine.
So here I'm going to accept the default location for the binaries and the cache.
I'm not using a proxy.
It's going to ensure our prerequisites are available, which they are.
So I'm basically doing a Next, Next, Finish kind of installation.
Now we need to register the server with the vault.
So let's Proceed to Registration, and were asked for vault credentials,
which we can get right here in the portal.
Download vault credentials.
We have to verify that we've already downloaded the MARS agent,
and I'll bring those down here.
There it is.
There's the credentials file, so let me minimize.
Let's browse into our Downloads folder.
There's the VaultCredentials.
Let me double‑left‑click that.
That's going to handshake the machine into the Recovery Services vault.
In order to provide a salt to encrypt the backups,
we need to either generate or create a complex
passphrase and then store it somewhere.
Let's see if I've got a D drive on the system.
I don't, so I'm going to temporarily put it in the root of drive C.
Of course, Azure Backup here will complain.
Are you sure you want to do that?
I'm going to answer Y just for now.
Registering this server with Microsoft Azure Backup.
All right,
there's that warning here about storing the passphrase on the same disk.
I'm going to launch the agent here, so let's click Close.
What will happen is that we now have wbadmin, but it's got cloud capabilities.
So we can come over here to Actions, and we can schedule a backup.
And in this case, the backup is going to go out into the cloud.
You see what I mean?
So let me quickly step you through the Schedule Backup Wizard.
We'll Add items, and you don't have too much to choose from.
As I said, it's basically files and folders.
I'll back up my IIS wwwroot directory on this web server.
Its files and folders are at system state.
we've got our default backup settings.
We've got our retention policy, which comes,
again, the option anyway, comes from Azure.
But notice that we're not using an Azure Backup policy.
We're doing it just for this one single machine.
We're going to Transfer over the network, Files and Folders, and Finish.
Okay,
so we can follow the status of that job as we go on here. Because we
registered the server to the cloud, we don't have to worry about
handshaking or registration or choosing a location.
It's just going to transparently put those backups up there.
Now notice you can do a backup now,
which is where we want to execute a backup at this moment,
which I actually do.
It's the same thing that I configured for the schedule. And this will
actually run the job right now and put something in our vault.
Let me close this and let it run in the background.
We can change our properties here, not while the job is in progress though. We
can open the Azure portal. So that's the singleton approach.
It's not very flexible for obvious reasons.
If we come back to the vault,
I wanted to show you something else because I mentioned that
Azure Arc‑enabled server, and I was frankly a little
surprised that it didn't show up here.
So if you come back to the vault, go to Backup,
your workload is running in Azure, Virtual machine.
If you come down to Add, it will gradually enumerate all
the machines that are in your region.
Eventually, I'm going to see that Arc server on here. It's just some latency.
I just onboarded it not too long ago. And you saw just in the few minutes
that I've been running this demo, when I first came in here,
there were only two machines shown. This is all because I just
started up those machines prior to recording,
but in your environment,
as long as those machines have been running for a while and your Azure
Arc‑enabled servers have been connected for a while,
you'll eventually see them show up in this list. Because after all, that is one
of the great promises of Azure Arc, that you can manage these off‑cloud servers
in many of the same ways that you can in Azure. Lastly, if we choose for our
Azure Recovery Services vault option that we're backing up on‑prem, but instead
of just Files and folders,
we have something more robust like Hyper‑V, VMware, SQL Server bare metal,
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.