Backup Copy Job to cloud connect says quota is full, but repository has free space (100TB repo / 56TB used

It is the block cloning from XFS that is causing that.  Veeam does not report these file systems properly and been like that for a while.

Think about it this way;

You are a service provider and are standing up a Cloud Connect environment for customers to send backups to. However, your have multiple types of repositories at your disposal, perhaps even part of the same scale-out backup repository. 

1. Block repository, windows or linux, with no block cloning (NTFS,etc)
2. Block repository, Windows or linux, with block cloning (REFS, XFS)
3. A Deduplication appliance, which is able to dedupe at a much more aggressive rate that the options above.

You want to charge customers the same amount for usage regardless of the underlying infrastructure, because it’s not the customer’s concern what your underlying infrastructure looks like. This is why Veeam Cloud Connect shows the customer usage that doesn’t change across all these options: Backup Data Size. That is, the cumulative size of the VBK and VIB files on the repository, before dedupe/cloning. The tenant Veeam server is not block cloning aware for cloud repositories.

This incentivizes the service provider to optimize their backup storage infrastructure, to hold as much backup data, while minimizing it’s actual storage footprint.

Chris/Tommy - I’m wondering if that behavior is a VCC thing? Multi-tenant thing? Or SOBR thing?...or a combination of using multiple MSP-type Veeam utilities (VCC, etc)? I have Linux Repos, non-SOBRs, using XFS and my storage usage shows as pretty precise in VBR. I know I’ve heard of this misallocation of block cloned storage within Veeam before..but just wondering if the behavior is moreso within VCC?

Thanks.

​@coolsport00, the used space showing based on the backup data not actual storage is an XFS/REFS/Dedupe thing. However this can usually be calculated by subtracting the repository free space from the total capacity to find the actual used space.

(You’ll often see cases like ​@chamandeep’s where the used space is 130TB on a 100TB repository. The more synthetic full restore points, the higher that will get.)

What’s different for cloud connect customers is that the free space they’ll see is their Cloud Connect quota minus the backup data size.

Ok..thanks Tommy.

veeam is not working with size as you can check size of filesystem with cmd  like df -h /opt/veeam

like you see in repository section

it is using size of backups, which you can find under disk > backup section so like du -h /opt/veeam/*

so yes, if you have quota 100TB, it thinks that is full, because your data are 130TB

advantage of xfs is not considered into calculation, because this is so variable that is outside of veeam application 

Couldn’t have said it better myself.  Thanks Tommy 😋