Failed to publish malware detection metadata to the catalog Processing

[vrmsot@nlicgulf.com]

Dear all,


Since yesterday I am getting warning in all Backup jobs, please advise


"Failed to publish malware detection metadata to the catalog Processing finished with warnings "


Support ID :- 07094268

[Mildur]

Hello Pankaj

I see that you have opened this case 15 minutes before creating this ticket.
Please give our customer support team a chance to investigate the logs. They already have answered you with the first troubleshooting steps.

Best,
Fabian

[AVavav]

In the same boat with the latest Veeam patch applied.
Any info to share, please?

[slappeee]

What was the solution???

[Dima P.]

Hello guys.

The issue is being investigated. If you see this behavior please raise a support case and share the case ID with us. Thank you!

[DaStivi]

hello there, got this error also since i've applied the veeam security recommendations... where there any easy fix for this issue?

[droegech]

Hi, for me recreating the VBRCatalog folder/share was the solution. At our instance the warnings appeared after the update to version 12.2.0.334

1. stop all Veeam services on your backup server
2. remove the VBRCatalog folder or rename it (for me this folder was located on primary backup volume)
3. create a new folder "VBRCatalog" and share the folder
4. start the veeam services

The problem ist also discussed in following community post:
https://community.veeam.com/vug-czech-r ... talog-6419

[Dima P.]

Hello Christian,

Thank you for sharing the workaround. To all newcomers - please raise a support case prior applying it as we would love to investigate and get the root cause fixed on the first place.

[DaStivi]

i might do this.. but its also time consuming ...
for me it happend after applying the veeam security best practices/hardening... in the end it where only 3 or 4 left... like SMB3 encryption enforcement... in this run i also enabled the block of the windows scripting host... i also noticed produces issues when running ah surebackup SQL Check Script, as this is failing after disabling the scripting host... but thats another topic...

[BenM2024]

Just a swift "Me Too" - ticket raised (community edition so not expecting anything).
Updated to 12.2.0.334 and get the error for new copy jobs after they have competed copying the backup data.
The backups from where the copy jobs get their source data work fine.

[BenM2024]

Final update - Stopped all veeam services, renamed VBRCatalog to VBRCatalog-old, created new one, added share/permissions as per old one. Restarted machine, waited till job ran. All OK... warnings gone away.

[Dima P.]

Hello Ben,

Please share the case ID with us. Thank you!

[droegech]

I had the issue at multiple customers. I opened veeam support Case # 07437057. I was advised to stop all veeam services, then change the user running the veeam catalog service to a local admin account and reboot the machine. This worked for me at first, but unfortunately after a few days the same warnings are now shown again.

[BenM2024]

Case No. #03479936

Holy thread ressurection Batman...

Had the issue happen again after 64 days. Opened a new ticket and submitted logs.

Veeam official response, so far, is "reboot the server" - which indeed makes the symptoms go away (so no more warnings on backup copy jobs last night, after the reboot); I will keep a closer eye on it.

Still no root cause though; I have asked if Veeam have any idea what is going on yet, or if we are in a "reboot clears the issue for a while; let's live with it" situation.

I suspect its a Windows/Veeam thing, where something that has been running for a while gets socially confused about which files are open/closed/should be open/locked etc.
Troubleshooting the issue will be tricky because of the apparently long interval (in my case) between ocurrances.

[Dima P.]

Hello Ben,

Are you still on 12.2? There are several improvements and fixes specifically for catalog behavior delivered with 12.3 update, so I'd recommend to install the latest version. Thank you!

[stewsie]

I have just experienced this issue after updating from 12.2 to 12.3 I restarted the Guest Catalog service and the test jobs completed with no warning. Unlucky? Possibly only time will tell. I haven't logged a support call but will do if it happens again