I would still need local disk on the Azure IaaS backup repositories to handle the first 7 days of data before it could be offloaded to Cold Storage. So for this example we could setup Veeam agents on our virtual machines running in Azure do to backup to a centralized Veeam B&R solution, which could then offload those backup’s to a Azure Storage Blob, where data is hitting a cold based blob storage. Secondly to ensure that no one was able to accidently delete the data from this backup solution using the VDC (Virtual Datacenter model) This solution would be added as another spoke using VNET Peering which would be pushing backup data over a VNET Peering. This means that backup data from agents would first need to hit a regular disk based VBR before being pushed out to a Azure Blob Storage.

Veeam in its current form as the support for using Azure Storage Blob as a scale-out repository option, essentially you can use it to offload old data to Azure Blob Storage as part of a scale out repository. NOTE: There is a new solution from Veeam coming soon, which provides native backup of Azure VM’s –> which will allow this to be even easier since it will be copying backup data directly into a storage blob. So instead of using these services, what if I used a Veeam agent based backup instead? Essentially setting up a Veeam VBR solution in Azure using Agents which point directly to an Azure Storage Blob? However someone can disable this feature trough the Portal ( ) 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. 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.

Veeam vul calculator