Scheduling for Background Retention Policy

[steamrick]

I like that the Retention Policy is now uncoupled from running at end of a successful job. Thanks for implementing that.

Unfortunately, 'daily at 00:30' is highly inconvenient for me. Right now, retention keeps failing because my repository is not reachable at that time and will remain unreachable at that time.

Is there any way to change that to, say, 03:30?

Or better yet, give it the same days-and-time scheduling options everything else gets.

Best regards
steamrick

[Gostev]

There's likely a registry value for this, let me check with the devs...

[steamrick]

A registry value would be great, thank you.

[Gostev]

RetentionJobStartTimeHours (DWORD)
RetentionJobStartTimeMins (DWORD)

For 3:30am start time you will need to set them to 3 and 30 respectively.

[steamrick]

Thank you.

This is the path?
HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication

edit: the retention job didn't trigger at 0:30, so I'm assuming it is the correct path.

[Gostev]

Yeah, virtually all of our registry mods go there.

[JaySt]

interesting registry values! i assume a VBR restart is needed to activate the schedule once the values have been adjusted?

[aszewc41]

Anyone know of a registry key to disable the background retention job?

[HannesK]

Hello,
and welcome to the forums.

Why would you disable the background retention? It helps to clean up and as far as I see, that option was removed in V12

i assume a VBR restart is needed to activate the schedule once the values have been adjusted?

according to internal documentation, a restart is not needed

Best regards,
Hannes

[Masch71]

Hello,
we have the same issue regarding the configuration of the automatic background retention (cleaning) in Veeam Backup & Replication v13.
The Windows Registry Keys previously used to control these cleaning processes are no longer available in version v13.
Veeam has changed over the management of these background processes. For Linux-based hardened repositories or virtual appliances, control is now performed centrally via the Veeam Host Management Service.
However, to start the retention and cleaning at an exactly defined point in time, A solution is required which is started or configured on the VBR server.
What has Veeam come up with as a solution?

[Mildur]

Solution for "reg keys" on our appliances: https://www.veeam.com/kb4779

Best,
Fabian

[Masch71]

Hello Fabian,

thanks for the answer but we need the solution for Windows based VBR.

regard
Markus

[Mildur]

The registry keys to configure when background retention starts are still available.
What makes you think they have been discontinued?
- For a Windows-based backup server, use the Windows Registry.
- For a VSA-based backup server, use the procedure in the KB link I shared.

Best,
Fabian

[Masch71]

As Hannes mentioned before in this post it was removed in V12.

[HannesK]

Hello,
maybe we start from the beginning because this thread is three years old and I do not remember details about things I wrote three years ago

Which registry key did you use in which version and which problem do you try to solve?

Best regards
Hannes