Add FQDN information for VM in job log

[rpetges]

Dear team,

In Veeam job logs, the Netbios name of the VM is used in the action column (see below)

09:41:39 Queued for processing at 4/14/2025 9:41:39 AM
09:41:39 Required backup infrastructure resources have been assigned 45:58
10:27:40 svr-server01 08:06
10:27:44 VM processing started at 4/14/2025 10:27:44 AM

However, if the job is processing VM's from multiple domains, it gets quite complicated to troubleshoot issues when only a part of the VM's fail.

It would be a great addition to replace the Netbios name by the FQDN name (see below)

09:41:39 Queued for processing at 4/14/2025 9:41:39 AM
09:41:39 Required backup infrastructure resources have been assigned 45:58
10:27:40 svr-server01.mydomain.com 08:06
10:27:44 VM processing started at 4/14/2025 10:27:44 AM

Best regards

[david.domask]

Hi Romain, welcome to the forums.

Request is understood, but those names for VMware/HyperV backups are populated from the hypervisor itself and the VM name provided, it's not polling for the Netbios or any other name on the network; at that stage in the job processing, no interaction has occurred with the VM or the GuestOS yet.

What sort of issues are you needing this for? It's best to open a Support Case in most instances as usually a review of the debug logs is required for quite a bit of troubleshooting.

[rpetges]

Hi David,

I already created a support case and was told to post it in the R&D forums as feature request

In fact, adding the FQDN in the logs would help to identify to which domain the machine belongs. Currently, we have machine from three domains in the same job and it may happen for example that a Windows update, firewall change breaks the backups. Having the FQDN in the logs would gave a quick overview which domain is impacted.

For example, instead of having the following:

server01 OK
server02 ERROR/WARNING
server03 ERROR/WARNING
server04 OK

it should be

server01.company.com OK
server02.sub1.company.com ERROR/WARNING
server03.sub2.company.com ERROR/WARNING
server03.company.com OK