Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Vstorage API and DFD

Created: 02 Mar 2012 • Updated: 19 Mar 2012 | 6 comments
This issue has been solved. See solution.

Hello,

We are working a problem (error 25 "cannot connect on socket) with our DMZ esx hosts. They both fail during, what I refer to as stage one.

The firewalls are not recording any drops to either the master, proxy, vcenter, or the esx host.

Any help would be appreciated.

Thanks,

Chris

Comments 6 CommentsJump to latest comment

Mark_Solutions's picture

Can you ping in both directions - or at least resolve host names?

This includes the VMWare Backup Host which needs to be able to resolve all hosted clients on the ESX Server to back them up

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Mark_Solutions's picture

In addition to me previous post also remember that the ESX Servers themselevs have a built in firewall:

http://www.symantec.com/docs/TECH61746

Please also confirm that all other setting and authentication have been set up in NetBackup - have you tested the credentials when they were added - or does it already work and this is just your DMZ firewalled ESX Servers having issues?

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

pikachu's picture

just worked with chris...

  • switched policy over to manual instead of VIP
  • fails with status code 58
  • reverse lookup does not resolv back correctly
  • admin will work on hosts or dns fixes

Nothing has changed...

cgoliver's picture

Had one of our Windows Admin remove the forward, but they didn't remove the reverse and now we two reverse records.

Mark_Solutions's picture

You need to add them not remove them .. and they need to resolve according to the host name specified (VMHost name or VM Display name - which ever you have configured it for)

Just used hosts files on the VMware Backup host  - an entry for each hosted server on the ESX Server that matches the name shown when the policy runs

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

cgoliver's picture

FIxed this issue. It was an asymmetric FW problem. Open from UNIX MS to backup host, but not vice versa.

SOLUTION