Guest Catalog Service is going nuts post 12.1 Upgrade

[sdv]

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.

[Dima P.]

Hello Stefan,

Thank you for sharing the update. We will review your case details with RnD folks!

[sdv]

Waiting on RnD for a proper fix.

To followup and update this post

We received a private fix and memory has been pretty stable for about 1,5 week.
Going up in memory about 1 to 2% a week instead of 30 to 40% before.

VBR: 12.2.0.334
PrivateFix: TF762258

[Dima P.]

Stefan,

Thank you for the heads up! Glad to hear it's working fine now!

[iDeNt_5]

Hi all,

I can also confirm the resolution of our issue, in this case after one day of "running-in" (with a very high CPU usage) after have been re-enabled both the anti-malware features, then no other issues have been faced.
I can also say neither the RAM usage is growing in time, it seems to remain pretty stable.

It seems like our issue was originally caused by a very large number of restore points marked as "infected" by Veeam.

Thanks.

[Dima P.]

Sounds great, thank you Matteo!