Could you please let us know what exactly concerns you? You have a backup copy job running that synthesizes backup copies from existing backups and this process consumes space on the storage.
I have a 7-day daily backup on a volume. For that I use infinite incremental backup. It maintains one (VBK) + seven incrementals and recycles those incrementals.
Synthetic and active backup is not enabled, because I want only 7 days of infinite incremental.
I have a secondary copy task with GFS enabled which aims to keep just one week and three monthly in the other volume. My goal of separating the volumes is that I intend to enable windows deduplication on that other volume, where the secondary copy job data is stored.
That is what I was guided to configure so that I have a weekly and monthly data protection.
However, I have noticed that the GFS task is unable to finish due to lack of disk space, which to me does not make sense.
It might make sense, assuming the repository backup copy job is pointed to is unable to host that number of full backups (full from simple chain, GFS weekly full).
If there is enough on target repository and you still experience the same issue, kindly, reach our support team for further investigation.