Veeam released the Backup & Replication v10 on February, and with it comes over 150+ anticipated new features and enhancements. Veeam now also have support for the option “Copy backups to object storage as soon as they are created” at SOBR Repositories settings, it will create additional copy of your backups for added redundancy by having all backups copied to the capacity tier as soon as they are created on the performance tier. Let’s follow steps to configure it.

  1. Login to Azure portal, click Create resource.

  2. On the New page, select Storage account – blob, file, table, queue.

  3. On the Storage account page, click Create.

  4. On the Create storage account page, select Basics and configure as follow and then click Next:Networking:

    Subscription: select your Azure subscription, e.g. Pay-As-You-Go.

    Resource group: click create new and enter a name for the resource name and then click OK.

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

    Location: select your location.

    Performance: select Standard.

    Account kind: select Storage V2 (general purpose v2).

    Replication: select Locally-redundant storage (LRS).

    Access tier (default): select Cool.

  5. On the Networking page, select Public endpoint (all network) and then click Next:Advance.

  6. On the Advanced page, configure as follow and then click Next:Tags.

    Secure transfer required: select Enabled.

    Large file shares: select Disabled.

    Blob soft delete: select Disabled.

    Hierarchical namespace: select Disabled.

  7. On the Tags page, click Next:Review + create.

  8. On the Review + create page, make sure Validation passed and then click Create.

  9. It may need few mins to create the new storage account, click Go to resource after the storage account is ready.

  10. On the created storage account page, select Access keys.

  11. On the Access keys page, copy Storage account name and key of key1, we need them for Veeam storage repository settings later.

  12. On the created storage account page, select Containers.

  13. On the Containers page, click +Container.

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

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

  16. On the Home page, select BACKUP INFRASTRUCTURE.

  17. On the BACKUP INFRASTRUCTURE page, select Backup Repositories and click Add Repository…

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

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

  20. On the Microsoft Azure Blob Storage page, select Azure Blob Storage.

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

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

  23. Paste Azure storage account name as Account and paste key1 as Shared key (you copied them from Azure storage account Access key).

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

  26. On the Container page, select the new created Azure Blob container from Container.

  27. Click Folder Browse, select the new created Azure Blob container and then click New Folder to create folder and then click OK.

  28. 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.

  29. On the Summary page, click Finish.

  30. On the BACKUP INFRASTRUCTURE page, select Backup Repositories and click Add Repository…

  31. On the Add Backup Repository page, select Direct attached storage.

  32. On the Direct Attached Storage page, select Microsoft Windows.

  33. On the Name page, enter a name for local repository, click Next.

  34. On the Server page, select your storage server from local repository server. Click Populate and then select the Drive from path, click Next.

  35. On the Repository page, click Browse…

  36. On the select folders page, click New Folder.

  37. Create AzureBackup folder, click OK.

  38. On the Repository page, click Advanced….

  39. On the Storage Compatibility Settings, select Use per-VM backup files, click OK.

  40. On the Repository page, click Next.

  41. On the Mount Server, select your storage server as Mount server, click Next.

  42. On the Review page, click Apply.

  43. On the Apply page, make sure all messages are green (show successfully), click Next.

  44. On the Summary page, click Finish.

  45. On the BACKUP INFRASTRUCTURE, select Scale-out Repositories, click Add Scale-out Repository.

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

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

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

  48. On the Extents page, select the AzureBackup_local Repository as Extents and click OK.

  49. On the Performance Tier page, click Advanced.

  50. On the Advanced Settings, select Use per-VM backup files (recommended), click OK, and then click Next.

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

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

  53. On the Capacity Tier page, click Windows…to define time windows when uploading to object storage is allowed.

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

  55. Select Copy backups to object storage as soon as they are created. This is a new feature of v10, it will create additional copy of your backups for added redundancy by having all backups copied to the capacity tier as soon as they are created on the performance tier.

  56. 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 it.

  57. 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

  58. 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.

  59. On the Summary page, click Finish.

  60. On the Home page, select Backup (under Jobs).

  61. Click Backup Job and select Virtual machine….

  62. On the Name page, type a name for the new backup job, click Next.

  63. On the Virtual Machines page, click Add….

  64. Select the Host or Virtual machine which you would like to backup, in my case, I selected the host, Veeam will backup all Virtual Machines of the host, click Add.

  65. On the Virtual Machines page, click Next.

  66. On the storage page, select Azure Blob Scale-out Backup Repository as the Backup repository.

  67. In Veeam B&R v10, you can configure GFS retention policy settings for the backup job, on the Storage page, select Keep certain full backups longer for archival purpose, click Configure….

  68. In the Veeam B&R v10, there are two retention policy settings options for restore points -restore points and days.

  69. On the Guest Processing page, If you add to the backup job VMs running VSS-aware applications, you can enable application-aware processing to create a transactionally consistent backup, in my case, I won’t enable it, click Next.

  70. On the Schedule page, select to run the backup job manually or schedule the job to run on a regular basis, click Apply.

  71. On the Summary page, click Finish.

  72. Select the new created backup job and click Start.

  73. When you check the jobs status, it will start offload to Azure blob after a vm backup completed.

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

    Hope you enjoy this post.

    Cary Sun

    Twitter: @SifuSun

Advertisements