SOBR Capacity Tier Storage with GFS and Move

[BertM]

Hello all,

I'm trying to get some clarification to understand what I'm seeing in my SOBR capacity tier. I think I screwed up when configuring it. I've read the FAQ and a bunch of forums posts, but I had trouble tracking down my specific scenario.

Here's my setup for two of my SOBRs:
Performance Tier: local server on REFS/XFS (one SOBR on REFS, the other on XFS)
Capacity Tier: Backblaze B2 bucket
Policy: Move after 30 days
Jobs are set with GFS: 4 Weeklies, 6 Monthlies
Jobs are set to use weekly synthetic fulls.

I've read that the Object storage in the capacity tier should be forever incremental, but with the storage usage Backblaze is reporting, I'm definitely storing full backups on the GFS backups. Is that because I'm using Move instead of Copy for the SOBR? Or is that just how GFS behaves? My sales engineer told me GFS is always a full standalone chain, but after doing more reading, I'm not sure anymore.

[Gostev]

Capacity Tier format does not support standalone full backups in principle, so it will be forever-incremental no matter what you do.
Archive Tier format does support creating offloaded fulls as standalone, but this is not a default setting.

[BertM]

Thanks, Gostev. After your post, I did some more digging and realized I misunderstood some of the numbers in the console. Now I just need to figure out why one of them has like 57% overhead in storage usage between Veeam and Backblaze (most are like 5-7%). I already opened a ticket, so I'll see what support says.