Hello chaos,
I have checked with QA the labs and we found the next case. Synthetic GFS backups work for object-based backups. If a GFS backup is scheduled at the end of an incremental cycle, the system will create a synthetic GFS full backup by reusing existing blocks rather than duplicating data. In practice, this means the GFS backup itself doesn’t consume additional storage space, it’s virtual.
For example, in our case, the GFS backup only contains metadata, while the actual data footprint remains unchanged. On S3, the entire backup occupies 159.81 MB. The main repository view reflects the accurate total size, even though the interface may show both the regular full and the GFS full as having the same size.
We’re actively working on improving how sizes are represented in the interface, but for now, this is expected.
Thanks
I have checked with QA the labs and we found the next case. Synthetic GFS backups work for object-based backups. If a GFS backup is scheduled at the end of an incremental cycle, the system will create a synthetic GFS full backup by reusing existing blocks rather than duplicating data. In practice, this means the GFS backup itself doesn’t consume additional storage space, it’s virtual.
For example, in our case, the GFS backup only contains metadata, while the actual data footprint remains unchanged. On S3, the entire backup occupies 159.81 MB. The main repository view reflects the accurate total size, even though the interface may show both the regular full and the GFS full as having the same size.
We’re actively working on improving how sizes are represented in the interface, but for now, this is expected.
Thanks
Statistics: Posted by RomanK — Oct 23, 2025 10:37 am
