So, I have upgrade our B&R 9.0 to 9.5 and upgraded to Windows 2016, redid the repository to REFS with 64K blocks and all is running well. I have decided to run a Synthetic Full on each Saturday, which is utilizing the Fast Clone without issue. It did, however, get me to wondering about how B&R 9.5 is handling file retirement in the case of the original Active Full VBK that is being leveraged by the Synthetic Fulls for Fast Clones once the original Active Full hits its backup retention window and is slated for deletion.
This question would also apply, I assume, for anyone who manually deletes (on the fly) an older VBK that may be the original Active Full to free up drive space on an emergency basis but doesn't do it within the B&R client, so the Veeam software has no way to know that the Active Full is going to be deleted and thus do whatever technical process it would undergo to assure those blocks are still available to the remaining Synthetic Full backups.
Any light you can shed on this question will be appreciated.