Azure Backup is a simple, automated, and offsite backup solution for your business. In this video, Sharon will provide an overview of this service. She will provide an overview of file, workload, physical, and Azure virtual machine backups. The configuration options for the various solutions will be explained.
- [Instructor] Azure Backup is a service that backs up and restores your data to and from the Azure Cloud. The backup can be used to protect not only your on-premise workloads, but also your Azure virtual machines, and restoring from Azure does not incur ingress or outbound data charges as most of the other Azure services do, which means if you need to restore data from Azure back to your on-premise, you will not incur a charge for that. A comparison to this would be using a third party backup solution and backing up into Azure Storage.
If you had to recover a file from Azure Storage, you would incur charges for that data to come back from Azure Storage back to your on-premise. Azure Backup is a critical component of your disaster recovery plans. Data is moved off-site, protecting it in case of an on-site disaster. If the on-premise data is not available, it can still be recovered from the Azure data centers. Azure Backup can back up files and folders either from your servers or your client systems.
You can backup your Hyper-V virtual machines, both Linux and Windows. You can also backup your application workloads. You may be wondering why you'd want to install Azure Backup on a desktop operating system. Think about your remote users. I know from experience, remote users didn't back up their data, it just didn't happen. By installing an agent and having their data backed up directly to Azure ensures that if something were to happen to their laptop, you still have that data available to you. The nice thing is, the filing folder backups only require an agent to be installed on the system.
If you'd like to back up other workloads, you're gonna require additional components and configuration. Azure Backup eliminates the use of what I consider pesky tape backups. A great example of this is the server 2003 operating system. The server needs to be replaced, in all likelihood it had tape backups. Instead of provisioning a new tape backup solution you could easily use Azure Backup. Your backups are encrypted and compressed, and I'm going to give you a warning about the encryption.
During the setup of the backup agent, you will be required to enter an encryption passphrase. This passphrase is used to recover your data. If you do not know the passphrase, you will not be able to recover your data. Don't save the passphrase in a folder that will be backed up to Azure. Once the backup agents are configured, the backups are completely automated and do not require any user intervention. As you backup data increases, the storage will auto-scale to meet that growing need, and these backups can be retained for up to 99 years.
Azure virtual machines by default are durable, meaning there are six copies of your virtual machines, but these copies do not protect you against a virtual machine accidentally being deleted, maybe a bad patch, a failed upgrade, an application mishap. Microsoft recommends that you backup your Azure virtual machines. This backup will not only protect the operating system disk, but also your data disks as well. But unlike the on-premise agent, the Azure virtual machine backup does not encrypt your data.
The Azure virtual machine backups are application consistent using volume shadow copy, or VSS. This ensures that the data both on the disk and in memory are captured by flushing the contents of the memory to disk prior to backup. Azure virtual machines can be backed up daily or weekly and the backups can be retained for up to 10 years. And restoring an Azure virtual machine is simply selecting the restore point and providing the networking details.
To backup the application workloads, the filing folder agent will not be enough. An Azure backup server or System Center Data Protection Manager will need to be used. Traditionally the System Center Data Protection Manager server was used to store backups from the environment to the server, and from there the backups were transferred to tape for long term storage. Using the System Center Data Protection Manager server you can now use Azure for that long term storage instead of tapes, enabling the offloading of data from the more expensive on-premise storage to the more cost effective storage in Azure.
And similar to the System Center Data Protection Manager, the Azure Backup Server stores the backups on the server and then pushes those backups to Azure for long term retention. The Azure Backup Server is very similar to the System Center Data Protection Manager server. It's more of a slimmed down copy of it, and it doesn't have all the capabilities of the System Center Data Protection Manager server. It also doesn't have the same cost associated with it.
- Understanding cloud technologies
- Why Azure?
- Creating virtual networks and storage
- Using Azure Active Directory for identity management and protection
- Disaster recovery with Azure Backup and Azure Site Recovery
- Working with virtual machines