or after starting the restore , the job is failing with 25? 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 Account now! Welcome First Last Your Profile Logout Sign in Thanks 0 Kudos Reply Accepted Solution! Step 4: A very useful command to help with testing client and server resolution is the command bpclntcmd -pn when run from a NBU client or media server. http://kelcours.com/cannot-connect/exit-status-25-cannot-connect-on-socket.html
This problem can occur when a process tries to connect to the NetBackup request daemon (bprd) or database manager daemon (bpdbm) and the daemon is not running. (On Windows, these daemons telnet: connect to address 10.28.1.236: No route to host telnet: Unable to connect to remote host: No route to host Any help or suggestions would be appreciated Thanks Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Step 8: If the client had been working at NBU 5.x release but now fails after upgrading to NBU 6.x, you can try using 5.x defaults for the client connection to
Just a guess... Create/Manage Case QUESTIONS? I have had a similar issue and even after making the changes to update the hosts file, the connection would fail until services were restarted. 0 Kudos Reply I did not Bppllist -l Cannot Connect On Socket (25) before starting the restore?
telnet: connect to address 10.28.1.236: No route to host telnet: Unable to connect to remote host: No route to host [email protected]# telnet s56upapp620-bak vnetd s56upapp620-bak/vnetd: Servname not supported for ai_socktype [email protected]# bptestbpcd -verbose -debug -client
Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Bptestbpcd Main: Function Connecttobpcd Failed: 25 You may also refer to the English Version of this knowledge base article for up-to-date information. It is possible that updates have been made to the original version after this document was translated and published. Step 6: Locally on the client create a bpcd log and increase the verbose level to 5.
No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES https://vox.veritas.com/t5/NetBackup/quot-EXIT-STATUS-25-cannot-connect-on-socket-quot-while/td-p/624003 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 Netbackup Error 25 Cannot Connect On Socket In the Server Properties window, click Port Ranges and view all port range settings Figure 1 notes the default port settings, as seen on a master server. Netbackup Cannot Connect On Socket 25 Windows 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
Thank You! Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework. For UNIX clients you can try removing the BPCD port from inetd.conf and run the command "bpcd -standalone" to see if that gets the port listening. this contact form Error Message Exit Status 25 - cannot connect on socket.
in case anything else is blocking communications View solution in original post 0 Kudos Reply 18 Replies it looks to be a fqdn issue, Mark_Solutions Moderator Partner Trusted Advisor Accredited Certified Bptestbpcd Cannot Connect On Socket Here's Why Members Love Tek-Tips Forums: Talk To Other Members Notification Of Responses To Questions Favorite Forums One Click Access Keyword Search Of All Posts, And More... Veritas does not guarantee the accuracy regarding the completeness of the translation.
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 See bprestore command usage:http://www.symantec.com/docs/HOWTO43687 ANYTHING in square brackets is optional. Email Address (Optional) Your feedback has been submitted successfully! Netbackup Error Code 25 No Yes Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Veritas.com Support Communities
In my bprestore script there Marianne Moderator Partner Trusted Advisor Accredited Certified 01-16-2014 04:49 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend 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 Labels: Backup and Recovery Linux NetBackup Troubleshooting 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! http://kelcours.com/cannot-connect/exit-status-25-cannot-connect-on-socket-in-netbackup.html Exit Status 25 - cannot connect on socket.
© Copyright 2017 kelcours.com. All rights reserved.