Maintaining backups is critical to protecting data. Learn about the backup options in Azure that can be used to protect data, workloads, and virtual machines.
- [Instructor] Azure Backup is a cloud-based backup solution for your Azure virtual machines, and for your on-premise servers as well. When using Azure Backup, you can restore from Azure. And this is one of the few services that does not incur an egress charge. Your backups are encrypted and compressed, and these backups are incremental. Azure Backup does support disk deduplication. Your retention policy can be created for a daily, weekly, monthly, or yearly backup for up to 99 years.
There are a variety of workloads that are supported by Azure Backup: files and folders, Windows Hyper-V virtual machines, Linux Hyper-V virtual machines, Microsoft SQL server, Microsoft SharePoint, Microsoft Exchange, Linux Azure virtual machines, and Windows Azure virtual machines. There are four components to Azure Backup, and your needs and current infrastructure will dictate the component that you will use. These components are: Azure Backup Agent, System Center DPM, or data protection manager, the Azure Backup Server, or Azure IaaS virtual machine backup.
We're going to drill into each of these. The Azure Backup Agent, and this is how it all started way back when. This agent will back up your file and folders on your physical or virtual Windows operating systems. A backup server is not required, but be aware, the Azure Backup Agent is not application aware, and there is no Linux support. And your backups are contained within the Azure Backup vault. You can schedule up to three backups a day using the Azure Backup Agent.
The Azure Backup Agent is simply installed on the system that you wish to protect. Your backups are then transferred to the Azure Backup vault within Azure itself. This is a very simple and easy-to-use backup solution. Next we have System Center DPM. System Center DPM, or data protection manager, is the most flexible of all the options. It does support App Aware snapshots using volume shadow copy. This allows for backups even when the files are in use.
And no, that is not a typo. You can actually backup your VMware virtual machines if you're using DPM 2012 R2. Linux machines on Hyper-V can also be backed up. System center will back up file, folders, and volumes. It will also back up your virtual machines, applications and workloads, and is flexible on the backup location. So you can backup to an Azure Backup vault. You could backup to a locally attached disk, or if you have an on-premise tape backup solution, you can backup there as well.
And using System Center DPM, you can have two backups per day. As I have already mentioned, System Center DPM for your backups is the most flexible. But you will have to pay for licensing. You will also require a DPM server as well. Next we have the Azure Backup Server. This solution is also App Aware, using volume shadow copy. Linux is supported, when running on Hyper-V. The Azure Backup Server does not require a System Center license. I like to think of the Azure Backup Server as a slimmed-down version of System Center DPM.
It will backup your files, folders, and volumes, as well as your virtual machines, applications and workloads and it is flexible on the backup location, but will not backup to tape. And when using the Azure Backup Server, you can have up to two backups per day. As you can see here, what is required is an actual backup server. You actually install the application on the backup server itself. And finally, we have our Azure IaaS Virtual Machine Backup. Here, we can actually backup our Azure virtual machines.
An agent is not required. We actually do this through an extension within Azure. Your virtual machine disk can also be backed up, providing you do it via PowerShell. Everything is kept in the Azure Backup Vault. And you can have one backup per day. From here you can see that we have the backup extension installed on our Azure virtual machine. The snapshots are taken of our Azure virtual machine, and then that data is transferred to the backup vaault. So now you have to determine which component are you going to use.
If you're backing up file and folders on Windows Server and Clients, and I say Client, you can use the Azure Backup Agent, System Center DPM, or even the Azure Backup Server. If you need to backup Hyper-V virtual machines, or application workloads, you're going to be using either System Center DPM, or the Azure Backup Server itself. And finally, if you're going to backup your Azure Virtual Machines, your only option is to use the Azure Virtual Machine Backup extension. And from the field, I do like Azure Backup, but personally, I would never rip out an existing off-site solution for an Azure Backup.
It's great when implementing a new solution, or replacing or upgrading older solutions. I would also keep a local backup in addition to the Azure Backup, for those quick file and folder restores.
- Implementing storage blobs and Azure files
- Managing access
- Configuring diagnostics, monitoring, and analytics
- Enabling and viewing logs
- Implementing Azure SQL databases
- Implementing recovery services
- Creating an Azure Backup vault
- Configuring the Azure Backup agent
- Backing up and restoring files
- Backing up an Azure virtual machine