Capacity mismatch between Veeam and S3 Object Storage

[Stupots]

Hi, we have some very large differences between Veeam and our S3-Compatible onsite Object Storage, this is causing us a lot of issues. Is there a way to resync and get them to agree with each other, as a rescan does nothing. Case number 07481030
------------Veeam Used TB-----Object Store Used TB
Extent 1-----183.7------------------177.6
Extent 2-----229.9------------------216.0
Extent 3-----198.4------------------179.9
Extent 4-----243.5------------------250.1
Extent 5-----228.5------------------250.3
Extent 6-----189.7------------------189.9
Extent 7-----166.5------------------9.9
Extent 8-----107.9------------------108.1

As you can see, some are accurate enough, but most are a very long way out.

In one instance I "delete from disk" 160TB of backups from the Veeam GUI (Extent 7), this caused it to be freed up in the Object Storage GUI, but not show as freed up in the Veeam GUI (this was over a month ago now).

Other extents show capacity free, but the namespaces in the Object Storage is full.

Thanks, Stu.

[Mildur]

Hi Stuart

Our Veeam console shows the value in TiB. If your object storage works with TB in the UI, then the numbers won't be the same. But It only would make sense for Extent 5 in your list.

I suggest to investigate with our customer support team why this numbers are not consistent with what you see on the object storage appliance. The requested logs can be exported with the help of this KB: https://www.veeam.com/kb1832

Best,
Fabian

[DataDefender]

Hi, we have some very large differences between Veeam and our S3-Compatible onsite Object Storage, this is causing us a lot of issues. Is there a way to resync and get them to agree with each other, as a rescan does nothing. Case number 07481030

Did you resolve this? I am having similar trouble, but not in the scale like you have. I just wanted to ask before I reach out to support.

Best,
DD

[vitalii.fesh]

We encountered the same discrepancy before. In our case, it was due to TiB vs TB. Typically, Veeam reports about 10% less.

[DataDefender]

It's not TiB vs TB here. We're talking 50% discrepancy here