During over the last few years, in ransomware era, some of my clients had issues with data loss due to “ransomware attack”. Few of them didn’t have any kind of backup solution, as well in few situations they didn’t have valid and tested backups. In worst case scenarios, their backups were encrypted, as well as all important data. In these situations, any kind of cloud (off-site) backup can help you to save your business. In this blog-post series, I will try to explain Azure Backup and show you how you can configure Azure Backup to protect your Azure workload, as well as on-premise workload.
At the start, just a few facts regarding Azure Backup as a Azure service.
- Azure Backup is the Azure-based service you can use to back up (or protect) and restore your data in the Microsoft cloud
- Azure Backup supports backing up Azure workload, as well as on-premise workload
- Azure Backup automatically allocates and manages backup storage, that you only pay for the storage that you consume
- Azure Backup offers two types of storage replication, LRS (Locally Redundant Storage) and GRS (Geo-Redundant Storage)
- Azure Backup does not limit the amount of inbound or outbound data you transfer
- All Azure Backup data are encrypted in transit, as well in rest
- Azure Backup provides application-consistent backups
- Azure Backup has a limit of 9999 recovery points per protected instance
So, after this information, we can start with configuring Azure Backup. Regardless what you want to protect, Azure workload, on-premise infrastructure or single machine files, you need to create Backup and Recovery Service vault. Backup and Recovery Service vault is a storage entity in Azure that houses backup data. To create your vault, like as all other resources, you need to click to Create a resource and find Backup and Site Recovery.
Once you click to create, you need to define a name, resource group name and location.
By default, your backup vault is created as Geo-redundant. If you don’t need that and want to configure backup vault as Locally-redundant, you need to do that before creating any protected instance in vault.
Now, we are ready to backup our workloads to Azure Backup. Stay tuned …