This Level 1 case has been with Veeam Support for 10 Days and I haven't heard anything in over a day, so it looks like I am on my own.
- The Server is at location A, on network A
The physical windows server to be protected is at location B on network B
The target Repository is at location B on network C
(etc.). We also tested using DNS, and tested credentials through the console.test-netconnection -computername 192.168.99.99 -port 2500
All networking connects with no issues and the credentials test good, however the job fails after about 6 minutes with:
Error: Managed session 81af3531-36a2-459f-aab8-6ddd7fa6ead4 has failed. JobId: 9dd3ea01-0f5b-4d5b-a19f-4cce367d2bff
There is a *.vbk and *.vbm created in the repo, but the *.vbk is too small to be meaningful (1.6 MB)
Other steps: clone the job and run, delete the *.vbk&vbm, rescan and Active Full, add hosts file entries to prevent subnet confusion, map SMB share from Protected PHYS server to repo (successful)
Looking for ideas.
THX,
-JB