Concurrent retention jobs in proxy pools

[Bjoern_ch]

Hi veeam team,

During one of my support cases it turned out that there is a limit for concurrent retention jobs in a proxy pool.
Logs showed that retention jobs could not start because limit was reached (“the limit of max retention sessions per pool was reached”).

Could anybody explain this limit to me?

Support already told me that it cannot be adjusted but did not have more information.
How does it work?
Is it a fixed limit like X retention jobs per pool? Is the limit determined by the number of proxies in a pool? Is it global limit like X retention jobs per all pools? etc.

How can I make sure that I do not reach that limit?

Best regards,
Bjoern
Case #07906161

[DanielJ]

Is that only visible in the logs? I haven't noticed until now that I don't see any retention jobs at all in the job history.

[Bjoern_ch]

yes, we found it in the logs. We searched the logs to find out why retention was not applied properly. Oldest restore points were not cut off.
You are right, you do not see any retention jobs in the history. I would consider them background jobs.

[Polina]

Hi Bjoern,

There's a default of 32 concurrently running retention tasks per a proxy pool (regardless of its size). The number of such tasks depends on the number of repositories your proxy pool is working with and your retention schedule. For instance, if there're 32 repositories, all with the same retention schedule, 32 retention tasks will be started at once. If the number of tasks to start exceeds the limit, they are queued and will start once there's an available slot. The limit is not configurable and is desinged to optimize the load on the PGSQL database.

Thanks

[Bjoern_ch]

Thanks for the explanations Polina.