In this video, Sharon demonstrates how to protect various workloads and then configure and explain the various backup options that can used to protect the data.
- [Instructor] Now that the Azure backup server is fully configured we can start protecting our workloads. If you're still in the management portion of the Azure backup server, go ahead and move up to protection. And the first thing we need to do is create a protection group. And to do so go ahead and select new and the new protection group wizard will appear for us. Our welcome page explains a little bit about how data protection works and then go ahead and click on next.
There are two types of protection groups in the Azure backup server application. We can either select servers or clients. As we are protecting server workload, I'm going to stay with servers. Now we can go ahead and select the workloads that we want to protect. When I select our member server, you'll notice that we have some additional options and I can expand these if I want. We can protect all shares, all volumes or we can enable system protection which will allow us to backup bare metal and system state.
I'm going to go ahead and select C and I'm just going to grab users and that's it. I'm going to scroll down. Now let's go ahead and select the sequel databases from our sequel server. Just going to go ahead and expand all sequel servers and then the actual server itself and now you can see we have the list of the three databases. I'm going to select all three. At this point you have the option to exclude folder or file types.
And I'll leave it as is, click next. We're going to go ahead and provide a group protection name. I'm simply going to call it workloads. Now we can select our protection method. And you'll notice that we have two of them here; we can have short term protection using a disk. This looks like its a drop down but really there is no other options. If you wanted to back up the tape you would need to use system centric configuration manager with DPM or data protection manager.
I'm going to go ahead and leave the short term protection enabled and I also want to protect our data by backing up to Azure. Go ahead and click next. Now we can go ahead and configure the retention policy for that short term backup. I'm going to leave the five days and every 15 minutes and I can go ahead and modify the file recovery points and the application recovery points if I needed to do so. I'm going to leave them and click next. If I had to change the target store's location I could do so in this screen as I only have one backup location I'm unable to change it.
Once you're happy with how the disk storage will be allocated, you can go ahead and click on next. Now we need to go ahead and configure whether or not we want a replica in the DPM server created now automatically over the network or if we're going to do it at a later date. You also have the option to do it manually if you need to transfer that data using removable media. I'm going to go ahead and select now and leave it as is. Our next step is to choose the consistency check options.
And the consistency check will ensure that our backup is correct. And we have two options here; we can run the consistency check if the replica becomes inconsistent or we can run it on a daily schedule. I'm going to leave the default. Now I can go ahead and select which workloads I want to be protected in Azure. As you can see, our sequel databases have already been selected for us. I'm going to go ahead and grab the users folder as well.
Now we can set up how often do we want this backup to occur. We can set it by day, week month or year and we can do it to twice a day. I'm going to leave it as a daily schedule everyday at 9pm and I'll just do it the once a day. This screen will look a little bit familiar, we can now go ahead and configure the online retention policy and modify our weekly, monthly and yearly retention policies as required. As always I'm going to leave it as is.
The next step in the wizard is choosing our online replication and again we've seen this before. We can either replicate directly over the network or we can do and offline backup. And to quickly recap the offline backup means you prep up your backups on site locally on a prepared hard drive and then that hard drive is shipped to the data center and the data is then mounted. We're going to go ahead and do it automatically over the network. We can review our settings and once we're happy we can go ahead and create that group.
And this will take a few moments. The new protection group will have been created, you can go ahead and close that window and you'll notice here we can see a list of that protection group which we called workloads, we can see our two servers; one where we're backing up the users folder and the second one where we're backing up the sequel databases. The protection status right now is that the replica creation is in process, and that'll take a few moments. As a replica is created you'll notice that the protection status then moves to okay.
Our workloads are now being backed up locally to that disk as well as to Azure a little bit later in the day when the backup schedule kicks in and that is all there is to it, to protecting your workloads on your servers to Azure.
- 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