Hello. And thanks for joining me for Cyber Aires. Microsoft Azure Administrator A Z 103 course. I'm well, Carlson. And this is Episode 34 about virtual machine backups. In today's episode, we're gonna configure a backup for an azure virtual machine. And we're also gonna go through the process of restoring that virtual machine from an azure backup.
All located in a recovery service is vault.
We're gonna get right into portal. But instead of going straight into the recovery service is vault. We're gonna look real quickly at the virtual machines blade.
And what I want to call your attention to are the location of these two virtual machines. I have one in central us and one in South Central us. Remember those locations?
We're gonna come up here to all service's and search for recovery. Service is vaults
and click to get into that blade, I'm gonna click on the vault that I have set up already,
and I'm gonna come here to back up now we set up this recovery service is evolved in the previous episode. So if you'll go back and look through that episode, if you don't understand where we're at in the process, you'll get caught up very quickly.
We're gonna go ahead and leave this exactly as it sits. We're gonna back up in Azure workload and it is a virtual machine. We'll click back up.
You can accept this default backup policy or create a new one. We're gonna go ahead and create a new one
and you see that we have to name the policy.
And then we have some options as to the time of day in the time zone used. Remember time zones gonna be particularly relevant here to make sure that the backup doesn't fire off when you don't intend for it to.
We could also set the number of instant recovery snapshots, and these are gonna be snapshots just like any other environment. And these were gonna be the fastest way to restore your backup.
We can set the daily retention schedule. Currently it's set to 180 days.
We've also got a weekly backups set to be saved for every Sunday for 12 weeks. We've also got a monthly backup scheduled to be saved, and we're saving 60 months worth of monthly backups, and this is gonna be weak based and that means that it's on the first Sunday of every month. If I change this today based,
I can select the day of the month that I want that to happen.
And then there's also a yearly backup point to be said here and again. This saves a year's backup, so every year you'll have one of these backups and you can sit this toe week or day based just like the monthly backup.
I hope that was clear. So we have 180 daily backups were gonna keep 12 monthly backups,
and we're gonna also keep 10 yearly backups. So what this means is that we're gonna have 10 years worth of yearly backups, 60 months of monthly backups,
12 weekly backups and 180 daily backups. Another was satisfied with the way this backup Paulius policy is set up. We're gonna select, okay? And then we're gonna select the virtual machine that we want to back up. I'm gonna go ahead and select, okay
and point out the fact that virtual machines can only be backed up to a recovery service is vault that are in the same region as that vault.
Now we can select Enable backup another. That backup job has been deployed. We can come back in here to the Volt Tech recovery service is vault come down into backup items
and then we can see that are as your backup agent has been deployed on one machine. That was the Mars agent that we deployed. We also have azure files being backed up to this recovery. Service is vault for a previous video. And here is our azure virtual machine that we just configured. I click on that will get me into that particular backup item.
I can click on that again to see more details about the job. Now we can see that this hasn't run yet, But I'm gonna go ahead and manually start this back up. So we have a backup to restore later in the video and all I have to do to do that let's click back up Now
we're gonna set. How long to retain this backup? I'm gonna leave that in the default and select, Okay? And now we conceded the backup that we manually started has completed. We have a few options here. We can restore the entire VM or we can do a file level recovery as well. We're gonna go ahead and click through the final level recovery first.
And what this is gonna do is it's going to allow you to download and execute herbal file that you run that will mount the drives
for this virtual machine on the machine that you're connected to now. So in my instance, I would downloads this execute herbal, run it, and I would have the drives from the VM backup mounted on my computer. I could pull down the files that I needed to ultimately be able to restore,
and then I could simply amount the disks. So with as your backup for virtual machines, you can do file level restore.
We can come back in here to file sink, and we can also do a full virtual machine restore as well. In this case, the only backup we have is the crash consistent backup that we manually triggered. And I can select that and hit OK and we have a number of options here in the backup restored job.
Right now, we can select this to create a new backup will need to give it a new virtual machine name and all of the relevant things that we typically would need to assign for a virtual machine,
including the resource group, the virtual network associate ID, the sub net and the storage account. Or we can simply replace existing, and that's going to replace the existing copy of this virtual machine with the backup copy of that virtual machine.
Now we will need to go ahead and select a staging location for this so that the backup can be restored and then ultimately migrated over,
and we simply select okay, and that's all there is to backing up in restoring a virtual machine from here within Azure Azure makes us very simple because it deploys the backup agent to the virtual machine for us. And it manages a lot of the workloads as faras, the storage and the agent in the recovery time,
all for us. And that's all there is to packing up a virtual machine here in Azure and the recovery options both of a file level restore and a full of'em restore as well.
So in today's episode, we used a recovery service's fault that we had previously set up and the azure backup service to back up a virtual machine workload that was running in the azure environment.
We also went through and talked about the recovery options. Both will restore to a copy or a replacement of the existing virtual machine, and also how the final level restore was done by mounting the drives on your local machine, pulling the files of boulders down that you need and then disconnecting from that dry
coming up. Next, we're gonna migrate off the topic of virtual machines and begin talking about how we handle networking here in the azure environment.
Thanks for joining me, and I look forward to seeing you in the networking section.