Thanks for the question. Could you please clarify your use case? Are you looking to use the backup server name to segment jobs through template rules, or is there another specific goal you’re aiming to achieve? 

Hi Jamie, thanks for reverting. The thinking behind this is that we will know the name of the clients Veeam server in case we need to connect to it to review the job configuration in detail.

Currently we can see:
Company name
Device name (device that is being backed up)
Job name

No way to see which Veeam server actually generated the backup information. Some clients can have multiple Veeam servers in different sites, or a not easily recognisable server name running Veeam B&R. Having this info available in the audit would make troubleshooting some of the failed jobs easier.

Thank you for clarifying the use case.

Currently, Backup Radar provides data like company name, device name, and job name but does not surface the originating server name. The upcoming Backup Metadata feature, set to release next month, may address this in part. It will allow more granular template rules by filtering backups based on API data (e.g., server attributes like name or other properties). However, surfacing this data in templates doesn’t seem to align fully with your use case, as it’s more about simplifying troubleshooting.

To better understand how you’d ideally like to “connect” to this data - would having the server name visible directly within a ticket generated by Backup Radar be the ideal scenario? Looking to get a better understanding of what the backup tech is looking at when troubleshooting, which I presume is a ticket. You had mentioned seeing this data in the Audit table? Curious to understand why - is there a reason this page is being looked at while troubleshooting.

We’ve only just started implementing Backup Radar so I haven’t really considered _where_ I’d like to see the info. 
If it can be populated in the ticket, great. If it can be populated in the job details, great. Just so long as the tech doesn’t need to look up the info from a different source.