Disparity size local backup VS moved to Azure Blob Storage

[Jrouzies]

Hello,

We recently moved a repository from a local disk / repository to Azure Blob Storage using the Move-VBOEntityData.

One thing I noticed, is that the space consumed at the end on Azure is literally a whole 1 TB less than it was on the local disk.

Local disk space used:

Size on disk: 3.58 TB

Azure repo:

UsedSpace : 0 B
LocalCacheUsedSpace : 1.0 GB
ObjectStorageUsedSpace : 2.5 TB

I can confirm the source repo is now quite empty:

UsedSpace : 0 B
LocalCacheUsedSpace : 0 B
ObjectStorageUsedSpace : 0 B
IsAvailable : True

How come there is such disparity? Does Veeam 365 apply better compression on a Blob Storage VS local repository?

Thank you

[Mildur]

Hello Jrouzies

Yes, this is expected. The way we store the data on object storage, we can achieve much better compression.
- For Exchange data, 40-50% compression.
- For Sharepoint data, 45%-55% compression.
How much depends on the file types and structure of the data.
https://bp.veeam.com/vb365/guide/design ... orage.html

Best,
Fabian

[Jrouzies]

Hello Fabian,

Thank you for your quick reply, that's great to hear!

Indeed it is Exchange Data.

[Polina]

Additionally, note that Jet DB doesn't shrink if some data has been deleted from the database, and space consumed by the database on disk may not be equal to the space consumed by data within the database itself. To give an example, after the retention policy deleted outdated items from a Jet-based repository, the database size on disk doesn't reduce.