One of the new features I’ve been keen to try in the lab is the use of object storage with Scale Out Backup Repositories (SOBR) to understand how it works.
- To begin I need to create a new backup repository. Click Add Repository
2. Choose Object Storage. Note it’s currently not possible to backup directly to object storage.
3. Select what type of object storage you want to use. In my lab I have an Azure subscription so will choose Microsoft Azure Blob Storage
4. Give the new storage repository a name, in this example I’ve called mine Azure Storage Tier
5. Next I need to connect to provide credentials to access the object storage. You can set this up ahead of time but in this example I need to click Add and provide valid credentials for my Azure account. It is possible to configure a gateway server if the SOBR extents don’t have direct internet access.
6. Next I need to enter my Azure Storage account and shared key.
7. Once authenticated I need to choose the container and folder I wish to use with. I’ve already created a new container called veeam-be-test and I’ll click browse to select a folder.
8. Ahead of time in the Azure Portal I created a folder called VeeamBackup to use. I’ll choose this and click OK
9. Review the summary page to double check everything is correct before clicking finish.
10. The newly created Azure Blob Storage account is now showing under the backup repositories. To make use of Cloud Tier I need to create a new SOBR.
11. Click Add Scale-out Repository to launch the wizard.
12. Name the new SOBR
13. Click add to select the extent to be used as the performance tier
14. I’ve chosen Repo02 to use in the lab.
15. Next choose the placement policy that best suits your needs. I’ve selected to use Data Locality
16. Select Extend scale-out backup repository capacity with object storage and choose the extent to use. Configure the operational window, which is time before restore points are aged out to object storage.
There are also options to configure a time window where data transfer is allowed and a capacity threshold window to offload data if a capacity threshold is reached.
17. Click finish to complete the process.
18. We can see the newly created SOBR-01 repository has two extents configured which can be now used as a target for backup jobs.
To wrap up part 1 I’ve configured a new backup job with a 14 day retention period. I’ve reduced the operational window on the SOBR to 3 days, so soon I should see data being pushed out to blob storage and I’ll pick this up in part 2.