Our backups are copied to secondary archive server repository using copyjob. There is defined GFS principle giving monthly full backup for archve. A tapejob is setup based on archive to take backup of latest full backups to tape once every month for extrnal storing.
This job should really just take latest full archive, but it also creates virtual full. We do not want or beed this - OR - we need to have this virtual full ONLY, as now in effect the tape job take 2 full copies each month, which should not be the case (= as not to consume a lot of tapes).
Setteing for full backups are in 'schedule' and the 'advanced' option 'Process latest full chain only'.
I've tried your suggested work-around. This does not work - as the tapejob seemingly ONLY recognises the ARCHIVE fulls... That is finalized archives with letter suffix (M = Month and so on). As we also have latest month restore points, the _M archive will be delayed in creation. This is expected.
There IS a rool-up full without letter suffix, but that one is NOT recognised bu the tapejob, so the tapebackup is really not usable as the archive file is very old.
Based on that it actually seems best option will be provide a fix to allow 'synthetic full' option to recognized as latest full chain.
Alternative could be to mae it possible to deselect 'synthetic full' completely, as it seems that 'latest full' done together with following incrementals does actully do the work...