B&R Update 3 how to backup physical machines

[PaulWo]

Hello, we recently updated our B&R 9.5 to Update 3 to take advantage of the new feature to backup physical machines.

We have a windows 10 machine that we are trying to backup.

We created the job as a "Windows Computer", the job mode is "Workstation" the name is the FQDN of the machine and the creds are the domain account creds, destination is Veeam backup repository.
We tried different different settings such as turning off the windows firewall completely on the Windows 10 machine, (by default we have firewall on for SC but all incoming and outgoing ports open), we tried turning off real-time protection on both the target machine and the Domain Controller where Veeam sits, and we tried different port numbers.

Is there something we are missing to get a physical backup running on Veeam 9.5? Looking in License info under "Agent for Windows" I can see the physical machine taking up a license.

Thanks

[Vitaliy S.]

Hi Paul,

Sorry, but I have missed that. What is the error message you see when running the backup job?

Thanks!

[PaulWo]

"Cannot send backup job configuration to machine.domain.com Error: Invalid job configuration. Connection problems. Exception has been thrown by the target of an invocation. No connection could be made because the target machine actively refused it [IP Address]:443"

[Vitaliy S.]

Do you see the same problem when backing up another computer (just as an experiment)? It does seem like a connection issue still. Can you double-check this once again and if the issue confirms with another computer (from the experiment), then please contact our technical team to review your setup.

[PaulWo]

This is the only physical machine we have tried, all our virtual machines have been backing up fine.
I have opened a support case, I will update the resolution here.

[andrie]

Hi Paul,

do you have a solution for this problem?

Thanks.

[Dima P.]

Hello Andy,

Since the case was not included to this thread we cannot comment how the previous issue was resolved. If you faced similar issue, please, raise a ticket and share it in this thread for future reference. Thank you in advance.