In this lesson, you can learn how to protect your Azure virtual machines to a recovery vault in Azure, including the various configuration options.
- [Instructor] In this lesson, I'm going to show you how we can back up our Hyper-V virtual machines using the Azure backup server. Now before we jump right into the demo, I'd like to explain the environment that I have set up here. I have configured this entire environment in Azure, but you could use the same environment on-premise. I just did it in Azure because it was easier to configure and build there. I have one domain controller, I have one Azure Backup Server, and this server is configured exactly the same as the backup server that we configured in the previous lessons.
If you did not see those lessons, you may want to go back now to learn how to configure that backup server. I have one Hyper-V Server in Azure, and this Hyper-V Server is hosting two virtual machines, Server1 and Server2. And yes, I said that this is all in Azure. You can now host virtual machines on Azure Virtual Machines. How's that for confusing? And kind of cool. And all these servers are domain joined. For those of you who prefer a visual representation, this is what it looks like.
We have our Hyper-V Server with our two servers. By the way, that will only work with Server 2016. We have our domain controller, and our Azure Backup Server, which will then direct those backups to the Azure Recovery Services Vault. Now that we've seen what the environment looks like, let's go ahead and configure this. I have already logged into the Azure Backup Server server, and as you can see, we already had the application up and running, and as I already stated, I've already done all the configuration steps necessary.
I have already registered this backup server with Azure, and I've added disk storage. And don't think you can skimp on this, because it is in Azure, you still have to add it. Next, I'm going to go ahead and add in our production servers. Then this will be the exact same step that we saw before when we were backing up our workloads. I'm going to go ahead and click add, and then choose the server type. Now for this demo, we are backing up Windows Server Hyper-V virtual machines, but you'll notice that we can also do this with VMware virtual machines as well.
That is out of scope of this course. As before, we can either install our agents, or attach agents. We would install agents for computers that are not behind firewalls, or if the firewall exception has already been created within the firewall. You would attach agents for computers that are behind firewalls, if the agent is already installed, or if you need to install the agent externally. If you do select attach agents, then you have two additional options.
Those being, you're installing the agent on a computer on a trusted domain, so that would be a computer within the domain, or a domain that has a two-way trust with the domain that has the backup server on it. And finally, your last option is a computer in a workgroup or untrusted domain. As I've already managed all the firewalls, I'm going to go ahead and install agents. The list of servers will be presented to you. If your computer name is not there, just try typing it in.
The only one we're worried about here, is the Hyper-V server. I'm going to go ahead and add that to my selected computers, and then click next. Now I need to enter an administrative credential. As we saw in an earlier lesson, we now have to determine what our restart method is. If that server needs to restart, is it okay that that system restarts immediately after the agent is installed, or do we have to wait and manually reboot that a little bit later? For our demonstration, I'm going to go ahead and use yes, I don't care if it reboots.
But if this was a production server, I may not be clicking that one so fast. We have our summary page, and then click install. And this will take a few moments. Once the agent is installed, we can go ahead and close down the wizard. And as we saw before in a previous lesson, we can now see the computer is registered with an agent, but is still unprotected. Therefore, now we have to enable protection. To do that, click on protection, and now we can create the protection group.
And this'll be the same process we used before. The new protection group wizard will pop up, we're going to select servers, because we're backing up servers, not clients. We can select the workloads that we want to back up. In this case, we are going to focus in on our two virtual machines. And that's all I've done is selected those, and go ahead click next, provide a name, and as before, we can select our protection method, we can select short term and/or online protection.
Let's go ahead and do both. I'm going to leave the default of five days for our retention range, for the short term. We could modify our target storage if we had that option. I do not. I'm going to leave the review as is, and click next. We can choose to replicate automatically over the network, either do it now or later, or we can do it manually. If you choose manual, you'd be doing so because you're transferring the data manually using a removable disk, or media of some sort.
We'll leave the default as automatically now. We can run a consistency check on the replica if it becomes consistent, or we can configure a daily consistency check if we'd like to do so. I'm going to leave it as is, of running it if that replica becomes inconsistent. Next, select the workloads that you want to protect to your online data protection, which is Azure. Create a schedule for those backups.
I'm going to leave it as daily at 9 p.m. And I can only back up these Hyper-V virtual machines twice a day. You would then go ahead and configure your online retention policy. I'm going to leave the defaults for weekly, monthly, and yearly policies in place. Click next, and as before, we have the option to back up automatically over the network. If you cannot do that because of bandwidth constrictions, or the size of the backups, you can create an offline backup, which basically means you're going to prep up a hard drive, back up to that hard drive, shift the hard drive to the data center, the data will then be mounted on the Azure servers for you.
We'll do it automatically over the network. We have our summary page, and then you go ahead and create the group. And this will take a few moments. After a few minutes, your protection group will have been created, and the policies applied. You can go ahead and close that window. You'll notice that we do have the two Hyper-V virtual machines now replicating, as indicated under the protection status bar. And later on today, those virtual machines will then replicate into the Azure Recovery Services Vault.
Okay, I don't know about you, but that's really cool! And it's a great way to protect your Hyper-V virtual machines.
- Creating a Recovery Services vault for Azure Backup
- Protecting virtual machines, files and folders, databases, workloads, and file shares
- Restoring virtual machines, files and folders, databases, workloads, and file shares
- Azure Site Recovery scenarios
- Running failover and failback tests
- Replicating an Azure virtual machine