I've started using my first Backup Copy Job that's backed by rotatable media.
The repository is 2 NAS rotated periodically, they both have the same IP and UNC share.
The Backup Copy is working fantastic, from what I understand there's a ForceDeleteBackupFiles registry key, which we've set to 3, but it nuked all files in the folder.
We're running Veeam v9 and have checked the Backed by rotatable media setting on the repository.
I understand that retention doesn't work as it should on a CIFS share as a new backup chain is created when the media is rotated.
So what we noticed, the Backup Copy Job was set to:
- Forever Forward Incremental (no synthetic fulls created)
- Restore points was set to 4
At any point there was 2 - 4 VBK files and 3 VIBs between each chain, which I would expect
We're looking for a way to remove the old chains once the new one is created, retaining just a single copy of the VBK and VIBs for the current chain
Is there any way to achieve this on CIFS, using PowerShell as a pre/post job?
Ideally, what we'd be after is if the backup chain no longer exists in the Veeam catalog, remove it from disk, but I'm not sure if this is possible in PowerShell, or too dangerous to do.
Has anyone implemented something like this, or going to?