Agents Backups with empty folders still produce backup files

[uk1984]

We have some backup jobs where we do backup the content of only a specific folder.
(This happens with the Veeam Agent, we have this issue with VAL agent, but I assume it applies to all of them.)

This folder is normally (like 99% of the time) "empty" but when running the job, the pre-script
triggers the database (in our case MaxDB) to for example do a log dump or a fullbackup into this "temporary"
folder/directory, so we can fetch the data with Veeam into our backups and afterwards the files are deleted again by post-script.

The full database backup occurs twice a week, with that we have no issues.

The log backups are scheduled like every 4-6 hours.
But here it sometimes happens that there within that interval there weren't any "changes" within the Database so
it decides "No I will not do a new log dump again, since nothing happened".
Which is perfectly fine and I do understand that.
But then Veeam still creates a Backup file and therefore also a Restore Point.

And here are our issues with that.:

a) We then have incremental Backup files which are "empty" but produce depending on the job setting for run a file with like 4-20 megabytes.

b) It falsifies the "effective" retention period/policy. So if we want to keep 30 restore points for example 20 backups created are "valid" with
real log dumps in it and 10 backups could be "empty" ones. Which essentially makes us having only 20 restore points.

c) It makes restore processes inefficient. Since it creates a restore point entry also for "empty" backups.
So if we would have to restore the latest 10 restore points one would have to check every restore point and some of them could be "empty".
So here it is taking more time to go over "empty" backups.

d) The Job status for empty folders is still "success". I understand that from a technical standpoint. But it makes no sense from a logical standpoint.
Who wants to backup empty folders?

I have discussed this with Support here:
Case #07581147 — VAL: Failed to execute pre-job script.

And was advised to get in contact here in the R&D forum as currently it "works as designed".
In my opinion the needs to be logic implemented on dealing with empty folders...

Best Regards
Udo