Home > Cannot Connect > Cannot Connect Socket Netbackup 6.5
Cannot Connect Socket Netbackup 6.5
Click Here to join Tek-Tips and talk with other members! The netbackup server, the netapps, and a domain controller are in a seperate test vlan, part of the same domain. Hosts entries? 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 news
Go to Solution. Resources Join | Indeed Jobs | Advertise Copyright © 1998-2016 ENGINEERING.com, Inc. Sorry, we couldn't post your feedback right now, please try again later. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : Problems with backup, cannot connect on socket(25) VOX : Backup and Recovery : NetBackup https://www.veritas.com/support/en_US/article.000012138
I ran the bptestbpcd at around 14:39:55 and it ran till 14:45:07. 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 To troubleshoot create a bplist log on the client at verbose 5 and rerun the command.The client connects to the bprd port on the master server and the master server performs Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?
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 write: "Ensure that PBX is installed and running". All rights reserved.Unauthorized reproduction or linking forbidden without expressed written permission. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem When trying to open the Netbackup Client properties from Master Server Administrator console, getting
NBU client service should be running Netstat -a shows PBX running. But, I've checked the settings on the Netapps and am not able to find any settings where any ports are blocked or a firewall is enabled. Email Address (Optional) Your feedback has been submitted successfully! https://www.veritas.com/support/en_US/article.000007335 check your version of NDMPalso try this command..[[email protected] AIX5]# set_ndmp_attr -probeProbe Host name: file01aHost "miafile01a" tape device model "IBMULTRIUM-TD3":Device "rst0l" attributes=(0x5) REWIND RAWDENSITY=LTO rd only 200GB cmpELECTRICAL_NAME=2a.0SERIAL_NUMBER=1013001D7CWORLD_WIDE_NAME=WWN[2:21f:0090a5:001d7c]ALIAS 0=st0Device "nrst0l" attributes=(0x4) RAWDENSITY=LTO
Does anyone know where the problem is? Veritas does not guarantee the accuracy regarding the completeness of the translation. But .... 0 Kudos Reply Re: cannot connect a linux client Andy_Welburn Moderator Trusted Advisor 12-04-2008 06:51 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Forum Operations by The UNIX and Linux Forums Login with LinkedIN Or Log In Locally Email Password Remember Me Forgot Password?Register ENGINEERING.com Eng-Tips Forums Tek-Tips Forums Search Posts Find A
bptestbpcd -verbose -debug -client Note: See the Related Article linked below for additional details on use of the bptestbpcd command. https://vox.veritas.com/t5/NetBackup/25-Cannot-connect-to-Socket/td-p/253715 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 RE: cannot connect on socket (25) santhas (TechnicalUser) 23 Sep 09 06:09 Hi,Have you setup NDMP credentials ( a valid user / password) and have you added the filers as NDMP As soon as I switch Daemon connection port back to default we go back to the job failing.
Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : (25) Cannot connect to Socket VOX : Backup and Recovery : NetBackup : (25) http://electrictricycle.net/cannot-connect/cannot-connect-on-socket-25-netbackup-7-0-1.html Handy NetBackup Links 0 Kudos Reply Sorry what I meant was I had Eamonn Level 3 06-01-2011 08:47 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! As soon as I switch Daemon connection port back to default we go back to the job failing.
View solution in original post 0 Kudos Reply 7 Replies Example job Eamonn Level 3 05-31-2011 02:28 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email All the commands were run from Master server. from the master server, run telnet Client_Name 13782 0 Kudos Reply Checked the usual stuffs MOIMOI Level 4 08-06-2009 11:03 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed http://electrictricycle.net/cannot-connect/cannot-connect-on-socket-netbackup.html To be checked in your case: Please check vnetd logs for IPC Sting port during the backup and also find via "netstat -a -o" to know which 'non-netbackup' process is trying
Any ideas or suggesstions? Just mentioning it as another step I tried. From Client: C:\>bpclntcmd -self gethostname() returned: server01 host server01: server01.domain.com at 10.193.176.51 (0x33b0c10a) host server01: server01.domain.com at 10.193.176.31 (0x1fb0c10a) host server01: server01.domain.com at 10.193.168.20 (0x14a8c10a) host server01: server01.domain.com at 10.193.176.61 (0x3db0c10a)
Through GUI hostproperties too, it doesnt connect.
No Yes How can we make this article more helpful? Error Message Status Code 25: Cannot connect on socket Cause Windows Firewall was enabled on Windows 2008 R2 server and port numbers 13782, 13724 & 1556 are blocked due to windows Thank you both for the log commands, helped point me in the right direction, and find a work around until I get a solution in place. DNS for resolution of hostnames.
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> Error Message Exit Status 25 - cannot connect on socket. So going by that article I'll needto identify the non-NetBackup process that is randomly connecting, as leaving the setting as Daemon port only is not a desired setup for us. click site No Yes How can we make this article more helpful?
e.g. These commands should be run against the master and all of the media servers that may be trying to backup the client server: /netbackup/bin/bpclntcmd -hn /netbackup/bin/bpclntcmd -ip Join your peers on the Internet's largest technical computer professional community.It's easy to join and it's free. Veritas does not guarantee the accuracy regarding the completeness of the translation.
Exit Status 25 - cannot connect on socket. from the master server, run telnet Client_Name 13782 ...... Looking further however I can't find anything connecting on the ports being requested in the vnetd log, so again I'm left with a puzzle of why this is failing on the 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
Close this window and log in. Go to Solution. It is possible that updates have been made to the original version after this document was translated and published. Article:000009351 Publish: Article URL:http://www.veritas.com/docs/000009351 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
Step 5: Ensure the client server has the bpcd and vnetd port in listening mode using the command netstat -a: On Windows: TCP dotto:vnetd dotto.veritas.com:0 LISTENING TCP dotto:bpcd dotto.veritas.com:0 LISTENING 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 try configuring user backup to this client and try staarting backup from client side and check what is the errror msg you get NB console. 0 Kudos Reply Is there any