Basic Scenario
============
Windows 2008 Physical Server running BackupExec 2014 SP1
ESX 5.0 Host managed by Virtual Centre (on VM)
The Backup server is running on a backup LAN with complete separation from Data traffic, but can communicate with VC /and the ESX Host over this LAN and all names seem to resolve.
Backup LAN 10.x.x.x
Data LAN 15.x.x.x
Things that work
All over Backup LAN 10.x.x.x addresses
Ping Backup server <-> Virtual Centre
Ping Backup server <-> ESX Server
Ping ESX host <-> backup server
Ping Virtual Centre <-> Backup Server
Backup of local devices on Backup server
Backup of physical Host via Client
Backup of FULL VM and granular index over SAN Transport
Backup of VM via Client if extra NIC on Backup LAN is configured
Restore of files via Client if extra NIC on Backup LAN is configured
Issue
When trying to restore FULL VM Image the wizard runs fine and allows me to brose all the required resource folders (Hosts / storage / network / Resource pools and folders)
The job starts and contacts the VC and creates the VM shell as instructed on the correct host, confirms this - and then tries to establish a connection to transfer the data and according to the log files it decides to do this over the INCORRECT network.
I have tried all sorts on name resolution checks as historically this has been issues on other locations but with no reward, so any suggestions on either troubleshooting or resolution – or is this never going to work with a separate Backup LAN ???
Thanks
Rob