I'm just in the process of setting up SureBackup to test some VM's and they keep failing. The issue is that when the VM's boot the OS assigns the Public Firewall profile.
My VM can successfully ping the gateway and in this instance the VM I am testing is also a domain controller. My Virtual Lab network is set to replicate the production network (meaning the Virtual Lab IP has the same default GW as what the production servers have).
There is a section in this KB article (https://www.veeam.com/kb1067
) that references "STATIC ROUTE NOT BEING CREATED", but I can't do that can I? Because since my Virtual Lab network is on the same subnet as my production network, wouldn't that break routing for my Veeam Backup Server?
I have also setup a proxy as per this (https://helpcenter.veeam.com/backup/80/ ... xy_vm.html
). The port got changed to 80, but then it asks to change the proxy settings on each of the servers. I'm assuming this means the production servers, if that is the case, this is once again going to break internet access on my production servers, because I don't use a proxy in production.
I must be missing something.
PS. The VM I am testing this on is a Windows 2008 R2 DC, and have installed the following patch so that it keeps the same static IP (http://kb.vmware.com/kb/1020078
). Veeam 9.5 is being used on Windows Server 2016.