In this lesson, Sharon provides a high-level overview of the Azure Backup service, including what can be backed up using the service with which component.
- [Instructor] Let's start this chapter with an overview of Azure Backup. There are different types of Azure Backup that you can implement. You can use Azure Backup to backup your files and folders, Azure virtual machines, Linux and Windows systems, your Hyper-V and VMware virtual machines, as well as System states. You can use Azure Backup to backup SQL Server, SharePoint, and Exchange workloads, you can backup Bare Metal, and there are two new services, including backing up Azure file shares, as well as an Azure SQL Database long term backup solution.
There are several advantages to moving to Azure Backup. The biggest is that you can backup and restore data to and from Azure. You don't have anything on premise. Azure Backup can be used to replace tape backup, as long as you're using System Center. You only pay for what you use when it comes to backup, and this is one of the few cases in Azure where you are not charged egress charges, and keep in mind, all of your backups are incremental. The other advantage of using Azure Backup is that your storage is automatically provisioned as required.
You don't have to assign terabytes of storage for a what-if scenario, it's automatically done for you, and because storage is automatically provisioned, you're only paying for what is actually consumed, not what may be consumed, and Azure Backup provides for unlimited scaling of your storage. You've two storage options when configuring Backup. You can choose locally redundant storage, or LRS storage, which keeps three copies of your data within a single region, but those you who need a more robust solution, you can select geo-redundant storage, or GRS.
When you use GRS storage, the data is replicated to another region completely, and this protects against regional outages, but keep in mind, it costs more than LRS. I mentioned that you're not charged for outbound traffic. The exception to this rule is if you use the import/export service, and typically you would use this service for large amounts of data. There is a cost associated with this service, and basically, what you would do with the service is prop up a hard drive, ship it to the data center, and then the data would be mounted.
Azure Backup includes data encryption. Your data is encrypted from end to end, and to ensure data encryption a passphrase is used, and this passphrase is stored locally. Now keep in mind that this passphrase is the keys to the kingdom. Do not lose it. Do not back it up where it's inaccessible, because it could be required to restore data. If you've backed up this passphrase, and you can't assess it, you will not be able to restore that data. Azure Backup provides application-consistent backups as well, and it does so by capturing data in memory, it also captures pending I/O operations.
This reduces restore time. There are a few constraints that you need to know about when setting up Azure Backup. First, you can only have 25 recovery services or backup vaults per subscription. You can only register 50 machines per vault, and only 200 Azure virtual machines per vault, therefore, take these constraints in consideration when planning your Azure Backup solution. Azure Backup can be the perfect solution to protect your data from the unthinkable.
- 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