Home > Cannot Connect > Cannot Connect On Socket Netbackup 7.1
Cannot Connect On Socket Netbackup 7.1
Although the problem doesn’t seem difficult to tackle but I’ve spent days just to get this error fixed, but all in waste. Because in some clients, they are able to connect. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : Status Code 25: cannot connect on socket VOX : Backup and Recovery : NetBackup Go to Solution Problems with backup, cannot connect on socket(25) Eamonn Level 3 05-31-2011 02:28 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a news
DNS for resolution of hostnames. Please create bpcd log directory on client, then post output of the following commands: On client: bpclntcmd -self bpclntcmd -hn bpclntcmd -ip On media server: bpclntcmd -hn (use After troubleshooting with our firewall guys we have found the problem in the network. Now vnetd uses the "IPC STING" port to direct the connection to bpbrm.
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 This can be verified by running nslookup against the IP address and hostname of the master server. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?
when i go to client properties and double client the same server it shows (25) cannot connect to socket. Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Thank You! How does media server resolve client hostname and IP for backup NIC?
Abby 0 Kudos Reply Enabeling logs Venkatesh_K Level 5 08-10-2009 12:34 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Launch registry editor (regedit) and go to HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config\ Check the following keys: EMMSERVER <= This should point to the Master Server unless EMM is configured on a dedicated server. 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 his comment is here the client had not been backed up for the last 10 days, am not sure before that. ... 14:44:59.975  <2> bpcd main: <---- NetBackup 6.5 0 ------------initiated 14:44:59.975 
Example : folder bpbrm for bpbrm logs and enable logging on master host properties and for client you can do it from BAR window from client side. Or are you restoring to the original devcie and location? Try these resources. Veritas does not guarantee the accuracy regarding the completeness of the translation.
all the clients which are working returns a zero and the command ends fast but all clients which are not work need a lot of time. https://vox.veritas.com/t5/NetBackup/Problems-with-backup-cannot-connect-on-socket-25/td-p/397975 Martin connect_problems.txt 7 KB 0 Kudos Reply Is there a firewall between watsons Level 6 09-22-2011 06:16 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email 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 You test seems to show that it is communication OK.
To test additionally I changed the setup to the following: BPCD connect back = Default Ports = Default Daemon connection port = Daemon port only Which also worked. 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. Create/Manage Case QUESTIONS? http://electrictricycle.net/cannot-connect/cannot-connect-on-socket-netbackup.html Then select Refresh List.
Make sure there is no network/hostname resolution issue. Thank You! Can you ping the server?
Go to Solution.
I am able to telnet the port 13782 Can you guys tell me how to enable logs in windows for bpbrm,bptm,bprd,bpdbm,bpcompatd and bpjobd. No Yes How can we make this article more helpful? Create/Manage Case QUESTIONS? Sorry, we couldn't post your feedback right now, please try again later.
Regards, Rochelle phgclbps01ms0f4b_log entries.txt 17 KB 0 Kudos Reply If it doesnt have a netbackup Mark_Solutions Moderator Partner Trusted Advisor Accredited Certified 02-05-2013 02:24 AM Options Mark as New Bookmark Force a client refresh in the NetBackupAdministration Console. After pressing enter it goes show nothing n comes back to comman prompt again... click site The failures I see appear to be 150 (termination by administrator) with associated 10054 (altho' there are no further details for these specific jobs) - are these the problem jobs? -
try with hostname and ipaddress 2. 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 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 firewall again MartinVi Level 6 10-04-2011 12:24 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi all, thanks for
Server <= The first name on the list must be the Master Server. 3. Solved! 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 : Backup server\cannot connect on socket\unable to r...
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 But i have a 5 days old bpcd log from client. Also run the following on client and post output: bpclntcmd -self Handy NetBackup Links 0 Kudos Reply Bclntcmd from Client to Master 16ris10 Level 6 03-03-2012 08:47 PM Options Mark as Make sure that the destination client is correct in the BAR GUI and that it is a fully configured NDMP device 0 Kudos Reply Hi Symantec Support, Thank rhyden26 Level 3
Abby 0 Kudos Reply no connection gilbert08 Level 5 Partner Accredited 08-09-2009 08:06 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report All i did is the normal procedures that i do to all my other servers but this one is not able to connect. Regards, Martin View solution in original post 0 Kudos Reply 4 Replies 1) Restart NBU on media watsons Level 6 09-22-2011 04:57 AM Options Mark as New Bookmark Subscribe Subscribe to Is the NB client running on the new client?