KB4816 - File Version Protection

[DanielJ]

#Split from KB4816 - how to for Veeam Backup M365?

If I take this up with a customer, the first thing they will ask is how they can protect the last 10 versions rather than only the very latest one. From a backup perspective it sounds very risky. Make a bad change, the backup runs - now you can't recreate any good version of the object. And what will it look like when going to a previous point in time, will the object simply not appear? There is an obvious need for something in between "all" and "one". Preferrably a configurable number.

[msobm]

I think (and i hope) you are getting this wrong.
As far as i understand it:
All the File-Versions are still in the Repository and only one Change per Job-Run is protected.
If you did a Change on day 1, take a backup on day 1 and then did a change on day 2, the Backup of day 2 does not overwrite the Backup of day 1. Both of them are still in the Repo and can be restored.

BUT if you change the File two times on day 1, only the second change will be backed up by the daily Backup not the first change/Version.

[msobm]

I verified that now. After enabling „latest Version only“ and taking a backup, all restore points are still available for changed and unchanged Files in the Backup Repository.

[Mildur]

Hi all,

I moved all three comments to a new topic, since they’re not related to the question “how to enable it.” Please use dedicated topics for new questions; thank you.

Coming back to the question: as tested by msobm, this new setting won’t remove existing backups in your repository.

Best,
Fabian

[Polina]

On our end, I can share that we're planning to add version range selection — something like "protect the N latest versions." No firm timeline yet, but it's on the backlog.