How do I do keep a specific number of restore points without regular backups (v13)

[RubinCompServ]

With v13 removing the ability to configure retention based on points, how can I keep a specific number of restore points on a backup job that isn't run regularly?

Usage case:
We have a team that applies patches irregularly to one of their servers, and they run a backup of the server before applying the patches. In the current configuration, this allows them to keep the last 5 versions of the server, regardless if the oldest version is from 2 weeks ago or 6 months ago. In the new configuration, they either have to configure an absurdly-long retention period and risk having many more points or configure a much sorter time and risk not having sufficient points.

Variation on the theme:
We have a number of Financial-sector customers who perform multiple backups per day. Sometimes, one of those backups fail. When that happens, they don't want the oldest backup to drop off. In the new configuration, all of the oldest backup will drop off every day, regardless of the number of failures during the day.

In the original [V13] Deprecated and Discontinued features for our 2025 release thread, @Dima P. suggested "VeeamZip, GFS or at least take an active full", which all present a problem:
VeeamZip: We have a vCD environment and access to backups is presented via the BEM Self-Service portal. VeeamZip doesn't exist in that environment.
GFS: This doesn't resolve anything, as there remains the virtual guarantee of having too many/too few points
Active Full: In addition to this still being subject to the retention policy, this will also require a substantial amount of time to run

[tommy.oshea]

According to the Veeam Help Guide, the minimum amount of restore points held while using the "Days" setting is 3. You can change the minimum number of retained restore points with a registry value. You need to contact Veeam support to get this registry key.
However I assume this would be applied to the entire Veeam server, and not configurable on a per-job basis like you'd probably prefer.

[Gostev]

Unfortunately, you cannot keep a specific number of restore points on a backup job with V13, as the only option for automated retention is time-based.

However, you can use the existing Export Backup functionality to create an independent backup file from any required restore point which will not be a subject to any retention policy. And if you use a backup repository with block cloning, then such backup will not require extra disk space nor a substantial amount of time to run.

Besides, I believe we always had functionality where the last N restore points are never deleted, in order to prevent all existing backups from being deleted in a situation where backup job does not run for extended time for whatever reasons. However, I will need the responsible PMs to confirm this functionality still works and what N is by default (pretty sure it's 3 and that there's a registry value to control it).

P.S. Oops, Tommy has beaten me to that.