Skip to main content

just moved veeam to a new server. All is good and working but backups are successful with warnings…

“failed to collect malware metadata from the backup proxy for the disk XXXXXX”

Any ideas? ports 2500-3300 are open so not sure the next steps to resolve unless I look at the logs…

 

thanks

Hi ​@MavMikeVBR,

How did you do the migration? Did you restore the config backup with the “migrate” function to a new server?

Which VBR version are you using?

 

Maybe you can temporarily disable the Windows firewall on the components to see if that makes any difference.

 

It can be quicker to open a Veeam Support case on that - in case you do, please keep us posted on what the teams replies.

 

Best

Lukas


It seems based on this forum post below that it has to do with the VBRCatalog folder -

https://forums.veeam.com/veeam-backup-replication-f2/failed-to-publish-malware-detection-metadata-to-the-catalog-processing-f-t91921.html

If that does not work then I would suggest in this instance to open a case with Support.  Never seen this happen previously when moving VBR to new server.


Another article about space for the VBRCatalog folder and using a separate drive - https://vinfrastructure.it/2024/07/veeam-catalog-space-usage-with-malware-detection-enabled/


I have seen in the logs, “failed to connect to the endpoint tVEEAMSRV:2500]. Will check for firewall blocks from each proxy to the backup server and see what we find.


I have seen in the logs, “failed to connect to the endpoint tVEEAMSRV:2500]. Will check for firewall blocks from each proxy to the backup server and see what we find.

That seems like a good place to start.  Always hated firewalls and port configurations.  😂


Comment