![veeam backup schedule best practices veeam backup schedule best practices](https://img.veeam.com/blog/wp-content/uploads/2016/08/05140203/img02.jpg)
In Azure terminology, objects are stored in a ‘Blob’, which can be thought of as similar to a volume on a disk but far more scalable. In fact, there is no way to modify part of an object’s data and any change requires deletion and replacement of the whole object.
![veeam backup schedule best practices veeam backup schedule best practices](https://www.veeam.com/blog/wp-content/uploads/2016/10/img06.png)
For example, in object storage, it’s intended that files are not modified. This blog post is aimed at helping backup administrators who wish to better understand from a Veeam perspective working with public cloud object storage, specifically Azure Blob.Ĭompared to the traditional NAS or disk-based block storage Object Storage is a completely different shift in how data is stored and accessed. With many organisations starting to dip their Veeam toes into object storage I thought I would write a bit more about the subject. According to Veeam’s quarterly report for the end of 2021, Veeam customers moved over 500 PB of backups just into the top 3 cloud object storage vendors alone. Sending Veeam backups to object storage such as Azure Blob has become a hot topic in the last few years.