Retention policy being applied much later than job completes

Hi @scottadamson423424 -

The fact it takes a while for your backup job to perform “transform” operations on the Backup Method (Reverse) you’re using, isn’t entirely out of the ordinary. I really love the Veeam “animation” KBs explaining each of the Backup method types. Here is the one for Reverse:
https://www.veeam.com/kb1933

If you were to use Veeam Fast Clone technology, your backup transforms would take almost no extra time at all since all your data is on storage and Veeam uses pointers to needed data already existing on disk. You could possibly rectify the behavior you’re experiencing by implementing Fast Clone. You can read more on that below:
https://helpcenter.veeam.com/docs/backup/vsphere/backup_repository_block_cloning.html?ver=120

To use it, you use XFS on Linux or ReFS on Windows for your Repositories. I just implemented it in my environment late last yr and hate myself for not implementing it sooner.

Anyway..hope that helps. Let us know if you have further questions.

@scottadamson423424 - yes, it should apply before the job completely finishes.

Hi @scottadamson423424 -

I’m just following up on your post here. Were you able to look in your Backup Job history to verify if the transform process (and thus retention) is running during your Tape Job? You should be able to double-click the Job causing you issues, then look at the Tasks on the right side. You should see some kind of “transform” statement task there before the Backup Job completes. The Job is finalized and then completed only after the transform (and retention) is configured. 

BTW, is there a reason you’re using Reverse? Is it possible for you to change to a different backup method, like Fwd Incremental, which should allow your Tape job to get all your backup files? Just a suggestion, if you’re open to considering the change.