Adding Azure Data Box Storage
Azure Data Box is a physical device which you can request for a short period of time from Microsoft. You can temporarily attach it to the backup infrastructure and use it as an object storage. For more information about ordering Azure Data Box and preparing to use it, see Microsoft Docs.
This device may become useful when you need to offload a significant number of backup files occupying storage space on your extents, as offloading data to the Azure Data Box device is much faster than transferring the same amount of data directly to Azure object storage. Once you have offloaded backups to Azure Data Box, you need to ship the device back to Microsoft for further data synchronization with your Azure storage account, as described in section Seeding Backups to Azure Blob Storage.
Consider the following:
- Veeam Backup & Replication supports only those Azure Data Box devices that are capable of reading and writing data using REST API.
- The Azure Data Box disk type is not supported.
- Direct data copy to the archive tier from Azure Data Box is not supported. When you place your order, do not enable Copy to archive option on the Data destination step.
- When you configure a scale-out backup repository with Azure Data Box as the capacity extent, it is recommended to only use the copy policy. This way you keep copy of the data on your local storage which helps you 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 Data Box is in shipment.
- You cannot offload immutable data to the Azure Data Box device.
- You can add only one Azure Data Box device to a scale-out backup repository.
- Veeam Cloud Connect service providers can use Azure Data Box only as a capacity extent of a scale-out backup repository.
For information about other limitations for Microsoft Azure Data Box storage, see Microsoft Docs.
To add Microsoft Azure Blob storage, use the New Object Storage Repository wizard.