Netbackup Error Cannot Connect To Socket
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs
Netbackup Cannot Connect On Socket Linux
Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research netbackup cannot connect on socket 25 windows Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português bppllist cannot connect on socket 25 Español USA Site: Veritas Veritas PartnerNet GENERAL ERROR: Cannot connect to socket (25) and Backup fails with Status code 58: Can't connect to client. Article:000007335
Netbackup Cannot Connect To Client 58
Publish: Article URL:http://www.veritas.com/docs/000007335 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this
Bptestbpcd Cannot Connect On Socket
Article Manage your Subscriptions Problem Error : "Cannot connect to socket (25)"Backup fails with Status code 58: Can't connect to client. Cause The problem turned out to be the Windows Firewall Service in Windows 2008 Server. Solution DETAILS:
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In netbackup cannot connect on socket 25 solaris CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down
Bptestbpcd Main: Function Connecttobpcd Failed: 25
your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX <16>bptestbpcd main: cannot connect on socket : Backup and Recovery : NetBackup : (25) cannot connect on socket VOX : Backup and Recovery : NetBackup : (25) cannot connect on socket Subscribe to RSS Feed Mark Topic as New https://www.veritas.com/support/en_US/article.000007335 Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page (25) cannot connect on socket Igselva Level 3 07-18-2014 08:16 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi Marianne I need a help.Yesterday we have restarted our exange server .After that backup not happened .We have DAG and Active https://vox.veritas.com/t5/NetBackup/25-cannot-connect-on-socket/td-p/660122 copy backup is configured. When I try to connect the client in Host properties .I am getting error (25) cannot connect on socket.I am able to telnet the client from Master & vise verrsa. /18/2014 9:23:27 AM - Error bpbrm(pid=146308) Cannot connect to abc.com 7/18/2014 9:23:27 AM - Info (pid=0) done. status: 58: can't connect to client Labels: 7.6 Agent for Microsoft Exchange Server Backup and Recovery NetBackup Windows Server (2003-2008) 1 Kudo Reply 6 Replies Check if the reboot maybe Marianne Moderator Partner Trusted Advisor Accredited Certified 07-18-2014 09:53 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Check if the reboot maybe enabled Windows firewall on Exch server. Disable Windows Firewall. If that is not the problem, ensure bpcd log folder exists on Exch server and try to connect again. Is anything logged in bpcd? Another thought - did Exchange maybe failover to other node when this server was rebooted? If that is the case, do the same tests on the new active node. Check that Windows Firewall is turned off and that node can resolve master/media server's IP address t
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership https://www.veritas.com/support/en_US/article.000008360 Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Unable to connect to a NetBackup client. Exit Status 25 - cannot connect on socket. Article:000008360 Publish: Article URL:http://www.veritas.com/docs/000008360 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas cannot connect Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Unable to connect to a NetBackup client. Exit Status 25 - cannot connect on socket. For example, if an attempt is made to cannot connect on connect to the client from the Host Properties tree in the NetBackup Administration Console. Error Message Exit Status 25 - cannot connect on socket. Cause Examine the bpcd log from the client for evidence of the following 10:44:50.087 [9501] <2> bpcd main: setup_sockopts complete10:44:50.091 [9501] <8> bpcd peer_hostname: gethostbyaddr failed : HOST_NOT_FOUND (1)10:44:50.091 [9501] <16> bpcd peer_hostname: gethostbyaddr failed to return peer host, herrno = 110:44:50.091 [9501] <16> bpcd main: Couldn't get peer hostname Solution This condition is indicative of a problem with host name resolution via either DNS or the hosts file. Verify that the client's hostname resolves correctly to its IP address and that the reverse is true. That is, that the IP address reverse lookup corresponds to the client's hostname. Perform this verification on both the client and the master server. Terms of use for this information are found in Legal Notices.
Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version a