Veeam plugin for Scale leaves many Snapshots behind.

[stevenrodenburg1]

Hello,
I noticed that the Veeam Plugin v12.1.0.246 on B&R 12.3.2.3617 (obviously) creates a snapshot of VM's when a backup job starts (directly after the VeeamWorker VM on the scale cluster is powered-on and reports in). After running such daily backup-jobs for a while, I noticed it leaves a varying number of snapshots called "VeeamSnap_<some id number>" behind.
In one Lab HyperCore cluster, where, in the Veeam BackupJob, 14 days retention is set, 5 snapshots are left behind.
In another Lab HyperCore cluster, where, in the Veeam BackupJob, 31 days retention is configured, 22 to 23 snapshots are left behind.
Every day, HyperCore shows 5 and 22 snapshots are present on all VM's in that backup-job. Week after week, month after month. So snapshots are deleted normally, they are just kept for a varying length of time (5 days and 22 days respectively in these two clusters).

My question: where is this controlled? What's with the "14 days retention results in a steady 5 snapshots and 31 days retention results in 22 snapshots". What's the logic behind that?. It is not something one can configure (only the normal retention in the B&R Job-Edit GUI).

I would like to reduce the number of snapshots to 1 or maybe 2 because I don't see the point in keeping 22 snapshots around (it does not match the 31 days retention anyway, neither does the 5 snaps in the job with 14 days retention).


Ps. Looking for the 12.1.1.4 (1.1) version of the plugin but the only Downloadlink I can find anywhere is of 13.2.0.245

[ronnmartin61]

@stevenrodenburg1 Scale had reached out to me on this regarding your post in their community site also so please see our joint response there. 'net of it is that you should only see a single rolling snapshot between job runs so probably best to reach out to our support for troubleshooting. Scale is adding some API support for more granular snapshot processing which will allow us to implement snapshot hunter support for their platform which will definitely solve this in a future release. In the meantime feel free to remove all the Veeam snapshots save for the latest one per VM.

You can access the v12 plug-in the "previous releases" tab at - https://www.veeam.com/products/download ... b=previous