Home > Cannot Connect > Veritas Netbackup Error 25 Cannot Connect On Socket

Veritas Netbackup Error 25 Cannot Connect On Socket

Contents

Attaching both files. Labels: 7.1.x and Earlier Backing Up Backup and Recovery Basics Error messages NetBackup Tip-How to Troubleshooting 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution! 100% packet loss Yasuhisa_Ishika Level 6 Would appreciate if it could be done without the logs cause they’re too big to change IPs and hostnames. Email Address (Optional) Your feedback has been submitted successfully! this content

Are there multiple interfaces on the client? -Chris From: veritas-bu-bounces < at > mailman.eng.auburn.edu [mailto:veritas-bu-bounces < at > mailman.eng.auburn.edu] On Behalf Of Randy Samora Sent: Tuesday, January 29, 2008 12:05 PM Sorry, we couldn't post your feedback right now, please try again later. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE 25: Cannot connect on socket when manually submitting backup jobs. You may also refer to the English Version of this knowledge base article for up-to-date information.

Netbackup Cannot Connect On Socket Linux

It is possible that updates have been made to the original version after this document was translated and published. Article:000090181 Publish: Article URL:http://www.veritas.com/docs/000090181 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 every thing is working fine...but when i add the server in the policy and try to add the folders it show cannot connect to client. Error Message error connecting to oprdcannot connect to VMD(70)network protocol error(39)cannot connect on socket Solution Overview:Backup jobs fail with Status 25 "cannot connect on socket".

CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical Figure 1.   Media Server Log Files:  \volmgr\debug\daemon log13:10:27.432 [14832.14532] <16> emmlib_initializeEx: (-) Failed to resolve EMM server reference implies that EMM could not be initialized via the PBX componentbptm log03:55:58.955 It is possible that updates have been made to the original version after this document was translated and published. Bptestbpcd Main: Function Connecttobpcd Failed: 25 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

I'm running 7.5 M4 Thanks 0 Kudos Reply I wonder, do you have the epsilon22222 Level 4 ‎01-31-2013 08:07 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Netbackup Cannot Connect On Socket 25 Windows Providing you the BPCD log file around that time. No Yes Did this article save you the trouble of contacting technical support? All other types of communication are fine except for the actual attempt to backup data. 1.

I've rebooted, uinstalled, reinstalled, lit a few candles and organized an all night vigil and still no luck. Netbackup Bpclntcmd I've rebooted, uinstalled, reinstalled, lit a few candles and organized an all night vigil and still no luck. I'm able to resolve from the master/media server (which is the same) see below C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -hn hcndc02 host hcndc02: hcndc02 at 192.168.100.226 aliases: hcndc02 192.168.100.226 You might want to see if all the components are still there (e.g.

Netbackup Cannot Connect On Socket 25 Windows

Ever since that time, the backups have failed. The client was backing up fine until last Friday. Netbackup Cannot Connect On Socket Linux See screenshot attached, I have not been able to restart the services on the media server as backup to take library it is still running. Bppllist -l Cannot Connect On Socket (25) Expand Host Properties in the left pane and click Master Server or Media Server 3.

I've added fqdn names to the host files as you mentioned on both the media server and the client and still get cannot connect on socket = 25 error when news I was told that the server crashed as if someone had unplugged it but it came back up after a reboot. No Yes How can we make this article more helpful? Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Error : "Cannot connect to socket (25)"Backup fails with Status code 58: Can't connect Netbackup Error 58 Can't Connect To Client

  • I can bpclntcmd -pn, -hn, -self, -ip and I get proper responses to and from the Master, Media Server and Client. 2.
  • The NBU 6.5.5 is the old master server's (udin02)versionwhere client used to be.
  • Go to Solution Status Code 25: cannot connect on socket 16ris10 Level 6 ‎03-02-2012 02:55 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a
  • I defragged the one drive configured on the client.

Veritas does not guarantee the accuracy regarding the completeness of the translation. Coz this is really strange problem i never faced before. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? http://rinfix.com/cannot-connect/veritas-client-cannot-connect-on-socket.html I cannot backup any data and I cannot connect to the client via Client Properties on the Master Server GUI.

If it had been working try to determine what changes may have been made to the client server's OS or the network links. Bptestbpcd Cannot Connect On Socket Article:000007335 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 No Yes Did this article save you the trouble of contacting technical support?

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

Step 6: Locally on the client create a bpcd log and increase the verbose level to 5. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Abby Labels: 7.1.x and Earlier Backup and Recovery NetBackup 1 Kudo Reply 27 Replies Have you checked all the usual Andy_Welburn Moderator Trusted Advisor ‎08-06-2009 12:46 PM Options Mark as New Bptestbpcd Exit Status 25 Click Specific Local Ports, type in the numbers of the port 13782 and then click Next. 4.    On the Action page, select the desired behavior, and then click Next.5.    Select

Most likely firewall software or a TCP wrapper was placed on the ports. Also sometimes there are stray things in memory preventing backups from working. CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical http://rinfix.com/cannot-connect/veritas-server-status-cannot-connect-on-socket.html Go to Solution bptestbpcd: EXIT status = 25 cannot connect on socket MaykelF0209 Level 3 ‎01-30-2013 01:51 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email

Step 2: In 6.x and above environments you can use the command- bptestbpcd to verify you can connect to both the vnetd and bpcd ports on the client server. In-depth Troubleshooting Guide for Exit Status Code 25 in NetBackup (tm) Server / NetBackup Enterpr... 0 Kudos Reply can you ping \ telnet the server rj_nbu Level 6 Employee Accredited Certified Step 3: If the master server can not connect to the client when trying to access the client host properties, below are steps you can take to further troubleshoot this issue: If any of these telnet tests fails to generate a log entry then there is something outside of NBU that is preventing access to the client's port.

Veritas does not guarantee the accuracy regarding the completeness of the translation. It will be able to resolve using bpclntcmd but won't be able to connect until it is allowed. 0 Kudos Reply as pointed out by epsilon Mark_Solutions Moderator Partner Trusted Advisor Thank You! VOX : Backup and Recovery : NetBackup : bptestbpcd: EXIT status = 25 cannot connect on soc...

But i have a 5 days old bpcd log from client. Error Message cannot connect on socket (25) getsockconnected:unable to connect() to , Connection refused (146) Solution Overview:Manual requests to start backup jobs - immediate or user-directed - are submitted to the cat bp.conf SERVER = udin06 SERVER = udin06.my.company.com SERVER = udib06 SERVER = udib06.my.company.com CLIENT_NAME = sdib01 REQUIRED_INTERFACE = sdib01.my.company.com VERBOSE = 5 DAYS_TO_KEEP_LOGS = 3 0 Kudos Reply Ok, i Not sure of your NB version but the following probably cover the same things: In-depth Troubleshooting Guide for Exit Status Code 25 in Veritas NetBackup (tm) Server / NetBackup ...

Ever since that time, the backups have failed. Veritas does not guarantee the accuracy regarding the completeness of the translation. You shutdown things cleanly and can remove locks that were left in place by an unexpected hard boot.