Step by Step to use Veeam archive on-premises data to Azure Blob #Veeam #Azure #Blob #MVPHOUR

Veeam released the Backup & Replication 9.5 Update 4 on January, also with this release, Veeam now also have support for Cloud based Object Storage, such as Azure Blob Storage which means that we can have the last 30 days of data stored on a local repository and then move the archive or later up to a Azure Blob but Azure Blob is capacity tier storage, you cannot use it as local backup repository and backup data to it directly. Let’s follow steps to configure it.

  1. Login to Azure portal and select Storage accounts.

  2. On the Storage accounts page, click +Add.

  3. On the Create storage account page, select Basics and configure as follow:

    Subscription: select your Azure subscription.

    Resource group: click create new and enter resource name and then click OK

    Storage account name: enter a name for your storage account.

    Location: select your location.

    Performance: select Standard.

    Account kind: select Storage V2 (general purpose v2)

    Access tier (default): select Cool.

  4. On the Create storage account page, select Advanced and configure as follow:

    Secure transfer required: select Disabled.

    Virtual Networks: select All networks.

    Hierarchical namespace: select Disabled

  5. On the Create storage account, select Review + create, make sure Validation passed and then click Create.

  6. It may need few mins to create the new storage account.

  7. Click the new storage account after the storage account is ready.

  8. Select Blobs and then click +Container.

  9. On the new container page, enter name for your new container.
  10. Select Private (no anonymous access) as Public access level and then click OK.

  11. Select Access keys and then copy Storage account name and key of key1.

  12. Login to Veeam server and open Backup & Replication console and then click Connect.

  13. Select BACKUP INFRASTRUCTURE, right-click Backup Repositories and then select Add Backup Repository…

  14. On the Add Backup Repository page, select Object storage.

  15. On the Object Storage page, select Microsoft Azure Blob Storage.

  16. On the Name page, enter name for Azure Blob repository, click Next.

  17. On the Account page, click Add on Credentials item.

  18. Paste Azure storage account name as Account and paste key1 as Shared key (you copied them from Azure storage account Access key, please check step 11 if you forgot them)

  19. On the Account page, select Azure Global (Standard) as Region.
  20. Click Use the following gateway server and then select a gateway server as proxy server and then click Next.

  21. On the Container page, select a Azure Blob container.

  22. Click Folder Browse if you has existing folder, if not, you can click New Folder to create one and then click OK.

  23. You also can select Limit object storage to help you control your cloud storage spend, but here I am going to keep the default settings (uncheck) and then click Next.

  24. On the Summary page, click Finish.

  25. Right-click Scale-out Repositories and select Add Scale-out Backup Repository…

    Note: please make sure you are using Veeam Backup & Replication Enterprise or Enterprise Plus if you don’t see the settings.

  26. On the Name page, enter name for Scale-out backup Repository, click Next.

  27. On the Performance Tier page, click Add….

  28. Select an existing backup repository (or repositories) as Extents and click OK and then click Next.

    Note: Please make sure they are not the same as the target backup repository of backup jobs.

  29. If the extent is using as a target repository of backup copy jobs, and it will pop extent will be automatically updated to point the scale-out backup repository warning message, click Yes.

  30. On the Placement Policy page, select Data locality and click Next.

  31. On the Capacity Tier page, click Extend scale-out backup repository capacity with object storage and select Azure Blob repository.

  32. On the Capacity Tier page, click Windows…..
  33. On the Time Periods, please select working hours as Denied time Periods, because it will use full network bandwidth to offload file to Azure Blob.

  34. If you need offload file to Azure Blob at working hours time periods, please use Global Network Traffic Rules to Throttle network traffic.

  35. On the Capacity Tier page, select Move Backups to object storage.. and keep the default setting as 30 days, you can change it if you need to.

  36. You also can click Override…. to get more options for moving oldest file to Azure Blob, click OK.

    Note: Every 4 hours Veeam collects the backup data from the extents and transfers it to object storage according to policies that define how and when such data should be offloaded.

  37. You can also define a master password that will be used to encrypt data uploaded to object storage, click Apply.

Note: This password will be used for encrypting all data moved to the cloud object storage.

  1. On the summary page, click Finish.

  2. You don’t need to change anything for your existing backup copy jobs if they were using the extent (Performance tier) repository as target backup repository.

  3. Every 4 hours Veeam collects the backup data from the extents and transfers it to object storage according to policies that define how and when such data should be offloaded. To offload the backup data, Veeam uses the SOBR Offload job.

  4. You also can check the Archive folder structure at Azure Blob.

    Hope you enjoy this post.

    Cary Sun

    Twitter: @SifuSun

About Post Author

Leave a Reply