In this demonstration,
I'll show you how to back up Windows Server to the
Azure Recovery Services vault.
What you're looking at right now is the desktop of one of
my many Windows Server 2022 machines.
Let me open up an elevated PowerShell console and do a hostname.
So this is mem2.timw.info, just a member server.
And let me look at my command history because I was
playing around before I started recording,
and I did a Get‑WindowsFeature "backup" to verify that Windows
Server Backup is available but not yet installed.
So let's go ahead and do an Install‑WindowsFeature windows,
if I can type, and I'll include the management tools.
I don't think we'll need to restart, but just in case, I'll add that flag.
Now I will type wbadmin to open the wbadmin command‑line tool.
This is something that I just want you to be aware of as far
as scripting local Windows Server Backup.
I want to open the GUI console though, Windows server Backup, because I want to
verify that right now it's truly a local backup solution.
Why am I showing you this?
Well, as I mentioned,
if you're looking to back up individual Windows Server machines in
a workgroup or Active Directory domain, you're going to need the
Microsoft Azure Recovery Services, or MARS, agent, and that will
extend this wbadmin console.
Okay,
so that's one machine on‑prem that we're going to enlist into our
Recovery Services vault. Here we are in the Azure portal.
I actually want to go over to Azure Arc to show you that I've
onboarded another machine in my on‑premises domain.
This is mem1.timw.info. Azure Arc for servers is a process where you
install what's called the connected machine agent into an on‑premises
Windows or Linux machine, and now we can do quite a bit of Azure
administration and without any dependency on ExpressRoute or a
site‑to‑site VPN in a very clean and nice way.
So note that I've got mem1 already enlisted in Azure Arc. That's not a
requirement. I'm just showing you a couple options.
The MARS agent is one option for onboarding on‑prem machines.
The Azure Arc for servers is another one.
And in the second demo in this module,
I'll show you the MABS, Azure Backup Server.
That's yet another way to go.
So let's head on over to Recovery Services vaults.
Let me adjust my zoom.
Now you'll see that my primary vault, az801‑rg‑vault is in East US.
This is an exam alert.
Now, when it comes to backing up your Azure VMs,
you're going to need to make sure that the Recovery
Services vault is in the same region.
So if you have VMs in multiple regions,
you are looking at having multiple RS vaults.
However, for Azure Arc and the MARS and MABS scenarios, location doesn't matter.
So let's go into our vault, and we're going to come down under Getting
started, Backup, and you're asked, first of all,
where is your workload running?
Is it in Azure, the Azure cloud in other words, Azure Stack, or on‑premises?
Let's start with Azure. The templates that I told you about are right here.
We can protect Azure file shares,
Azure VMs running particular database products, but we're
going to do a standard virtual machine backup.
Let's click Backup, and were asked here,
what kind of backup policy are we looking at here?
Standard or Enhanced?
That's going to be our service tier.
As you can see, there's some additional features. Because the Enhanced is in
public preview, or at least part of it, that's not going to be in scope for our
cert exam, so we're going to stay with Standard where we're doing daily
backups. And as far as our backup policy goes,
let me show you the components of that.
We'll click Create a new policy. I'll call this az801‑policy. And
our daily backup here can be in whatever time in our time zone. I'm
going to choose 2:30 AM, and my particular time zone is ‑06:00
Central, so let me find that.
Where are you Central? There you are. The Instant Restore, like I said,
is between 1 and 5.
I love this feature a lot.
I'm going to max it out. And then we have our retention range.
How long do you need the RS vault to keep daily snapshots weekly,
monthly, and yearly? I'll leave those at the default right now.
We can take care of changing that.
Of course, the policy is a separate artifact, and we can
always go back and change it after the fact.
And then lastly, we have this optional Azure Backup Resource Group.
Azure Backup will create a default resource group, as you see here,
AzureBackupRG_{Geo}_{n). I'm going to leave that alone. But it's nice
because I'm sure Microsoft received a lot of customer complaints
saying that the default separate resource group you create violates
our naming standards, you see,
so that's convenient and thoughtful of Microsoft to do. All right.