Seeding Backups to Azure Blob Storage
Seeding backups is an operation which can help in case you want to keep backups in object storage repositories and need to transfer backups in bulk to object storage. In this case, you can utilize the capabilities of the Azure Data Box device that will help you to transfer data from the local backup repository to Azure Blob storage and synchronize with the storage. Azure Data Box is a physical storage device that emulates a cloud storage endpoint and serves as an intermediate between the local backup repository and Azure Blob storage. With the help of Azure Data Box you will not need to create a full backup file and transfer it through the network which may result in high load on the network. Instead, you will transport all necessary data using Azure Data Box.
To seed data to Azure Blob storage, you need to order Azure Data Box from Microsoft, connect to it, copy backups from the local repository and ship it back to Microsoft. After the backup data is uploaded to your Azure Blob storage, you can perform initial sync and store your backups in Azure Blob storage later on.
For more information on ordering Azure Data Box, see Azure Storage Documentation.
Before you seed backups to Azure Blob Storage, make sure to review considerations and limitations.
To seed backups to Azure Blob Storage do the following:
- Set up Azure Data Box.
- Add Azure Data Box to the backup infrastructure and then offload the data.
- Prepare Azure Data Box for shipping.
- Synchronize the seeded data.
Before you add Azure Data Box to Veeam Backup & Replication, you need to set up the storage:
- Install Azure Data Box. For more information, see Azure Storage Documentation.
- Connect to Azure Data Box through REST APIs. For more information, see Azure Storage Documentation.
After you perform the steps in the Azure Storage Documentation, you will have a storage account name, access key, and blob service endpoint that you can use to add Azure Data Box to the backup infrastructure.
To offload backups to Azure Data Box, do the following:
- Add Azure Data Box as an Azure Data Box storage.
- Add Azure Data Box storage as a standalone object storage repository, the capacity tier or performance tier in a scale-out backup repository.
When you configure a scale-out backup repository with Azure Blob storage as the capacity extent, make sure to select the Copy backups to object storage as soon as they are created check box as described in section Add Capacity Tier. In this case, you will keep copy of the data on your local storage which will help you to reduce the risk of data loss if the device is damaged during shipping. It will also ensure that the backup data is available for restore operations while Azure Blob storage is in shipment.
If you use the other type of backup repository, make sure to keep a copy of your backup in your local storage.
- Press and hold the [Ctrl] key, right-click the scale-out backup repository from the previous step and select Run tiering job now.
After you have completed moving backup data to the Azure Data Box, you need to ship this device back to Microsoft so that this data can be synchronized with your Azure storage account.
Before shipping Azure Data Box back to Microsoft, do the following:
- Put an object storage repository that is associated with Azure Data Box into the Maintenance mode, as described in section Switching to Maintenance Mode.
- Perform the steps described in Microsoft Docs.
After shipping the device, wait for Microsoft to receive it and copy your data into your Azure storage account. You will be notified of successful data upload to your Azure storage account.
To connect Veeam Backup & Replication to your Azure storage account, do the following:
- Add an Azure Blob storage, as described in section Adding Azure Blob Storage.
- Edit settings of the object storage repository or scale-out backup repository used for offloading the data, and change your Azure Data Box object storage to the Azure Blob storage that you have created in the previous step.
- Enable importing backups from Azure Blob storage and wait for the synchronization to complete.
- Remove Azure Data Box object storage from the backup infrastructure, as described in section Removing Object Storage Repository.
Keep in mind that if you delete individual VMs from your backup in the period between mailing Azure Data Box and adding Azure Blob Storage, you may need to run Active Full instead of Incremental job after the final Azure synchronization. To avoid this, do not delete any VMs manually and disable the Retention Policy for Deleted Items option in the job settings for that period. After successful synchronization, you can re-enable this option and work as usual.