Hi David,
I already created a support case and was told to post it in the R&D forums as feature request![:-D]( "Very Happy")
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
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
Statistics: Posted by rpetges — Apr 24, 2025 8:13 am
