We have the RAM issue as iDeNt_5 mentioned and opened a case about it (07377314) since august 13th.
The workaround we got from Veeam support was using the registry value IndexRetentionDays or stop using Malware detection.
It might be good to note is that using the registry value will impact Veeam Enterprise Manager search results.
We found ourselves that restarting Veeam.Backup.CatalogDataService released its heavy RAM usage and did the trick.
This feels like a better workaround than the registry value.
Waiting on RnD for a proper fix.
The workaround we got from Veeam support was using the registry value IndexRetentionDays or stop using Malware detection.
It might be good to note is that using the registry value will impact Veeam Enterprise Manager search results.
We found ourselves that restarting Veeam.Backup.CatalogDataService released its heavy RAM usage and did the trick.
This feels like a better workaround than the registry value.
Waiting on RnD for a proper fix.
Statistics: Posted by sdv — Oct 04, 2024 3:57 pm
