Thank You! is displayed. Solution Check the bpclntcmd -ip, pn, -hn this works fine.Telnet working from Netbackup Client but does not work from Netbackup Master Server to NetBackup client for port numbers 13782, 13724We need Think the best option is to Michael_G_Ander Level 6 Certified 04-21-2015 12:39 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate navigate here
Why can not we take backup along with Firewall Enabled ? I have install the NB client in windows servers & when i try to connect i get the error as "socket read failed" ./bptestbpcd -host 10.13.123.32 -verbose <16>bptestbpcd main: Function ConnectToBPCD(10.13.123.32) bpclntcmd -clear_host_cache Thanks 0 Kudos Reply Hi All Thanks for the Igselva Level 3 07-21-2014 06:43 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email Remember to chmod 777 dbclient.
Netbackup Cannot Connect On Socket Linux
When I try to connect the client in Host properties .I am getting error (25) cannot connect on socket.I am able to telnet the client from Master & vise verrsa. 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 Veritas does not guarantee the accuracy regarding the completeness of the translation.
Create/Manage Case QUESTIONS?
Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?
Using "bpclntcmd" command to verify name resolution for nbu systems.
I just wanted to get confirmed from NBU end, as yes the Ports are not open for Communication.
Please create bpcd log folder on the client under /usr/openv/netbackup/logs Run bptestbpcd again on master: bptestbpcd -client -debug -verbose http://www.symantec.com/docs/HOWTO43696 5.
View solution in original post 0 Kudos Reply 12 Replies Accepted Solution!
Is "telnet " the only way by which we can be sure about Port is not open. 0 Kudos Reply i believe..
Can you ping MOIMOI Level 4 08-06-2009 11:22 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content hi Rajeev, 1. And PLEASE use hostnames in NBU. but you need to add the netbackup ports to the firewall excepsssion list..(1556,13782,13724) by default window firewall does not keep the ports in excepsssion list, becasue it does not know about Bptestbpcd Cannot Connect On Socket Email Address (Optional) Your feedback has been submitted successfully!
This command does the following: The client retrieves the first server listed in it's server's list (this should be the master server) does a forward lookup of that hostname with 'gethostbyname Netbackup Cannot Connect On Socket 25 Windows Thank You! Windows Firewall is a Microsoft product. Found that "Windows Firewall" service is running on the server.
On the server, if "telnet client 1556" does not work, then the bptestbpcd and NetBackup will not work. Bptestbpcd Main: Function Connecttobpcd Failed: 25 set loging level to 5 to get complete details since your saying ping telnet and host resolution is fine, if this is the newclient that is having problem try restarting NB If that is the case, do the same tests on the new active node. No Yes Did this article save you the trouble of contacting technical support?
Netbackup Cannot Connect On Socket 25 Windows
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 ... If NBU server and clients are on the same internal network and protected from external threats by the Company firewall, there is actually no need for individual firewalls. Netbackup Cannot Connect On Socket Linux Just simply click apply and OK to commit those changes. If unable to resolve this issue, place a call to Symantec Technical Support for NetBackup for help in troubleshooting this Netbackup Cannot Connect To Client 58 HankHill Level 5 05-29-2013 08:32 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Error stopped, not sure why. 0
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://softwaredevelopercertification.com/cannot-connect/veritas-netbackup-error-cannot-connect-on-socket.php Check Windows Firewall is turned off, or make sure the relevant nbu ports is not blocked. 2. 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 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 Bppllist Cannot Connect On Socket 25
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) Handy NetBackup Links 0 Kudos Reply Thanks Nagalla & Vickie Level 6 07-27-2013 09:51 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Sorry, we couldn't post your feedback right now, please try again later. http://softwaredevelopercertification.com/cannot-connect/veritas-server-status-cannot-connect-on-socket.php Hostname lookup: Use 'bpclntcmd -hn ' and 'bpclntcmd ip
Because it blocks all port connection - including NetBackup. Netbackup Bpclntcmd Did you try a telnet test? It is possible that updates have been made to the original version after this document was translated and published.
View solution in original post 0 Kudos Reply 6 Replies looks like its duplicate for RamNagalla Moderator Partner Trusted Advisor Certified 02-28-2013 08:38 AM Options Mark as New Bookmark Subscribe Subscribe
Why NBU connection failed when server is Behind firewll ? Did they only open to one NetBackup Server, or to all the NetBackup Servers? Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Unable to connect to a NetBackup client. Exit Status 25 - cannot connect on Netbackup Error Code 25 Can you ping the server?
https://www-secure.symantec.com/connect/forums/oracle-rman-backup-issue#comment-6036911 0 Kudos Reply Oracle RMAN backups inn_kam Level 6 Partner Accredited 12-30-2014 04:25 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a If any changes to hostname/IP/DNS, using the following command to clear cache. lets isolate from one error first... 0 Kudos Reply Error from logs, shows that Vickie Level 6 02-28-2013 12:09 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight http://softwaredevelopercertification.com/cannot-connect/veritas-netbackup-error-25-cannot-connect-on-socket.php 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
Think the best option is to Michael_G_Ander Level 6 Certified 04-21-2015 12:39 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate 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 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 Solution Troubleshooting: Step 1: When troubleshooting status 25 errors on a NetBackup client, verify that the client was working prior to the issue.
After next failure, check bprd log on master for incoming request from client's IP. Check forward and reverse lookup works fine between master/media/client. 3. Port TCP/1556 bi-directional should be enough on it's own. Ensure that master can resolve client's IP address to the Client name contained in the policy.
If you can tell Windows Firewall to allow comms on port 1556 (PBX) and vnetd (13724) it won't be necessary to disable it completely. from the master server, run telnet Client_Name 13782 ...... Even if you need to add hosts entries. bptestbpcd -verbose -debug -client Note: See the Related Article linked below for additional details on use of the bptestbpcd command.
You now need to go with this information to the admins of that firewall to open up ports.