Sorry, we couldn't post your feedback right now, please try again later. Go to Solution. including with bprd? 0 Kudos Reply Yes they are running Harry_NBAD Level 4 Certified 01-15-2014 10:52 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to MaykelF0209 Level 3 01-31-2013 08:01 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Thanks for the replies guy. http://kelcours.com/cannot-connect/exit-status-25-cannot-connect-on-socket-status-25.html
Veritas does not guarantee the accuracy regarding the completeness of the translation. Error Message Exit Status 25 - cannot connect on socket. I even typed in a fake server name along with the other Media Server names and the installation recognized that the server name was bad. 5. I uninstalled 6.0 and 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". https://www.veritas.com/support/en_US/article.000008360
For UNIX/Linux clients the /usr/openv/netbackup/bp.conf file should have the top line as "SERVER =
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 I will have to wait until the current queued jobs finish to restart services... Figure 1. Media Server Log Files:
Without -S bprestore will use 1st entry in bp.conf to know where to send restore request to. Netbackup Cannot Connect On Socket 25 Windows I can bpclntcmd -pn, -hn, -self, -ip and I get proper responses to and from the Master, Media Server and Client. 2. 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... https://vox.veritas.com/t5/NetBackup/bptestbpcd-EXIT-status-25-cannot-connect-on-socket/td-p/569792 Email Address (Optional) Your feedback has been submitted successfully!
Just a guess... Netbackup Error Code 25 is displayed. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Why does the bplist command fail with status 25? If I try to run a user backup from the client, the job also fails with a Status 25 but the failure is immediate where as the backup from the Master
It is possible that updates have been made to the original version after this document was translated and published. Thanks in Advance!!! Netbackup Cannot Connect On Socket Linux No Yes Did this article save you the trouble of contacting technical support? Netbackup Error 58 Can't Connect To Client 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
Create/Manage Case QUESTIONS? his comment is here No Yes How can we make this article more helpful? Cause Examine the bpcd log from the client for evidence of the following 10:44:50.087  <2> bpcd main: setup_sockopts complete10:44:50.091  <8> bpcd peer_hostname: gethostbyaddr failed : HOST_NOT_FOUND (1)10:44:50.091  <16> if yes please provide the detail status of the job 0 Kudos Reply Hello, I am executing the Harry_NBAD Level 4 Certified 01-15-2014 10:13 AM Options Mark as New Bookmark Subscribe Bppllist -l Cannot Connect On Socket (25)
Most likely firewall software or a TCP wrapper was placed on the ports. I was told that the server crashed as if someone had unplugged it but it came back up after a reboot. Any typo error will cause a failure! Bptestnetconn The client was backing up fine until last Friday.
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 If it had been working try to determine what changes may have been made to the client server's OS or the network links. NB Processes ------------ root 8573 1 0 Jan 6 ? 4:44 /usr/openv/netbackup/bin/nbevtmgr root 8580 1 0 Jan 6 ? 2:41 /usr/openv/netbackup/bin/nbaudit root 8686 1 0 Jan 6 ? 3:46 /usr/openv/netbackup/bin/bprd root http://kelcours.com/cannot-connect/exit-status-25-cannot-connect-on-socket-in-netbackup.html Go to Solution.
It is possible that updates have been made to the original version after this document was translated and published. Create/Manage Case QUESTIONS? Exit Status 25 - cannot connect on socket. I can telnet to bpcd on the client successfully. 4.
Please suggest, it's urgent. Article:000090014 Publish: Article URL:http://www.veritas.com/docs/000090014 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 See bprestore command usage:http://www.symantec.com/docs/HOWTO43687 ANYTHING in square brackets is optional. If this fails consult with your Network Administrator and client server System Administrator to resolve the layer 3 or IP network connectivity.Double check the server's NIC's IP address and netmask to
Veritas does not guarantee the accuracy regarding the completeness of the translation. Sorry, we couldn't post your feedback right now, please try again later. I cannot backup any data and I cannot connect to the client via Client Properties on the Master Server GUI. Thank You!
Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? 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 netstat -a |grep bp tcp 0 0 *.bpdbm *.* LISTEN tcp 0 0 *.bpjobd *.* LISTEN tcp 0 0 *.bprd *.* LISTEN tcp 0 0 *.bpcd *.* LISTEN 0 Kudos Reply This way you can verify how Netbackup sees the servers based on the hostnames and IP addresses] To test the master/media server resolution of the client server hostname run the following
The client is on the same subnet as the Master and Media and no firewalls. 10. You shutdown things cleanly and can remove locks that were left in place by an unexpected hard boot.
© Copyright 2017 kelcours.com. All rights reserved.