

The backup data is stored within a regular Storage Blob which does not support tiering nor reserved capacity.Īzure Backup also provides a solution called soft delete, which ensures that data is always available 14 days after someone deletes it.

The backup data is stored within a recovery vault which compresses the data but does not provide deduplication of data. Regardless much of the other features are the same. The second part is Azure Backup using the Mars agent which runs as a agent on the server which can provide lower RPO which lacks native integration with the Azure Portal to do restore and such. Azure Backup providing different options for doing backup, first of is the native Azure Backup feature which provides IaaS level based backup and runs directly as a service in Azure.
VEEAM BACKUP CALCULATOR HOW TO
Now in this particular case we had a challenge, the customer had applications which required a low RPO, which was max 4 hours.The second part was providing a low RPO for Linux based workloads as well and also how to ensure that someone with access rights in Azure was not able to delete files from Azure Backup? Now my first response on the second part has always been Azure Backup. First of was how we were to handle Disaster Recovery both on a Storage level and on Virtual Infrastructure secondly how to handle backup of virtual machines in Azure. For a customer project I was working on a couple of issues came up with how to do backup of IaaS in Azure.
