NBD Transport Fails... Despite 902 Hanging and ESX Resolution Working... HELP!
Got a mystery....
I've setup NBD transport VMWARE bakcups numerous times and have never seen this. I have a case open with Veritas but wanted to reach out to see if anyone has seen this before.
NBD transport fails, despite port 902 being able to hang between all NBU Servers and all ESX Servers.
We are using HOSTS file to resolve, and are all exact copies of each other, so the ESX server name is correct in all NBU servers.
When using the VMWARE Host as the Backup Media server, if the storage unit uses my Master Server only, the job works. If it uses my media servers, they fail...
This is again with all HOSTs files being 100% correct, and we can hang port 902 from all NBU servers to all ESX servers.
We thought perhaps this was an odd persmissions issue... we tested the NBU service account with full admin rights, still fails.
Vcenter is also correct and hangs on 443 from all NBU servers.
What might cause NBD transport to fail despite 902 being opened and the resolution to the ESX is correct?
- ESX server names are 100% correct in all hosts files.
- All Hosts files are exact copies of each other, the ESX server names match 100%
- We can hang Port 902 from all NBU servers to all ESX servers.
- We can hang Port 443 from all NBU servers to the vCenter server.
- NBU service account tested with full admin rights.
- NBD transport works from when the VMWARE Backup Host is the Master Server but not Media Servers, DESPITE all of the above.
- Turned of logging, can't find any red flags when the job fails.