Hello Brian
I recommend to keep it simple.
Create new VMs and add them to the backup job. The Backup Job retention and Background Retention job will take care of the old restore points.
Best,
Fabian
The feature is called background retention and will clean up retired restore points.or if there is some feature in Veeam I could use to manage restore points if the job no longer can see a relationship between the old and new VM backups.
That could work as well. But too much work for multiple servers.I understand it is the new VM having a different UID, so I tested the only idea I’ve thought of so far as follows: I created a new VM and specified Server 2022 as OS just to see what VMware generates for RAM, disk controller types, NIC types, boot options, etc. just so I could reference and I then adjusted the settings of a 2016 VM to match then removed and re-added the OS disk. I could then do my typical process and next time the backup job ran, it successfully did an incremental and retention and GFS worked fine.
I recommend to keep it simple.
Create new VMs and add them to the backup job. The Backup Job retention and Background Retention job will take care of the old restore points.
Best,
Fabian
Statistics: Posted by Mildur — Jul 23, 2025 7:09 am
