Home > Cannot Connect > Cannot Connect On Socket 25 Netbackup Restore

Cannot Connect On Socket 25 Netbackup Restore

Contents

Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem The master server is getting a status code 25 (cannot connect on Close Reply To This Thread Posting in the Tek-Tips forums is a member-only feature. Exit Status 25 - cannot connect on socket. 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 http://electrictricycle.net/cannot-connect/cannot-connect-on-socket-netbackup-restore.html

If name resolution it exceeds that timeout then try using a host file entry to avoid DNS latency. 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 As soon as I switch Daemon connection port back to default we go back to the job failing. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? https://www.veritas.com/support/en_US/article.000042369

Netbackup Error 25 Cannot Connect On Socket

No Yes How can we make this article more helpful? 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... Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Step 7: Test telnet from the master server to the client's bpcd port:   telnet [client hostname] 13782   That should generate a log entry as seen below showing the master

Then, create a debug log directory for bpdbm, retry the operation, and check the resulting debug log.*If you can view the report and have not found an entry related to this 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. Terms of use for this information are found in Legal Notices.

Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may Bptestbpcd Main: Function Connecttobpcd Failed: 25 The values on the Network tab are written to the services file when the NetBackup Client service starts.Also, see "Verifying Host Names and Services Entries" in the Troubleshooting Guide.4.On Sun Solaris,

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 If any of these telnet tests fails to generate a log entry then there is something outside of NBU that is preventing access to the client's port. Thanks in Advance!!! https://www.veritas.com/support/en_US/article.000007335 from the master server, run telnet Client_Name 13782 ......

When the backup is run for the first time, the backup may fail with status 25. Bppllist Cannot Connect On Socket 25 What might be blocking the socket connection? Note the NetBackup daemon running and listening check and the bpps check in section three.On Windows, verify that the %SystemRoot%system32driversetcservices file has the correct entries for bpcd, bpdbm, and bprd.Also, verify 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

Netbackup Cannot Connect On Socket Linux

Most likely firewall software or a TCP wrapper was placed on the ports. https://www.veritas.com/support/en_US/article.000012138 Drive type: Open the NetBackup administration consoleExpand Media and Device ManagementSelect Devices.  The right column indicates the device topology in the upper view, and the lower view lists all drives.The Device Netbackup Error 25 Cannot Connect On Socket i dont know how to check the logs for bpbrm and other logs.i also dont know how to configure those logs so that i can see the error for this particular Netbackup Cannot Connect On Socket 25 Windows Veritas does not guarantee the accuracy regarding the completeness of the translation.

Probably 'Client hostname not found' (status 48). -S -C and -D are REALLY optional switches. click site Is the NB client running on the new client? Have tried the following: Rerun the jobs during the day (normally run at night) - Still fails Created a brand new policy (not copying the old one) - Also fails Telnet Sorry, we couldn't post your feedback right now, please try again later. Bptestbpcd Cannot Connect On Socket

C:\Program Files\Veritas\NetBackup\bin>bpcd -standalone C:\Program Files\Veritas\NetBackup\bin> (COMES BACK TO THE SAME PROMPT) Am i right or is the result right that shows nothing on the command prompt? No Yes Did this article save you the trouble of contacting technical support? Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Symantec: NetBackup Forum news The bpcd log shows status 98.The bptm log lists a message: mount_open_media: error requesting media, TpErrno = Requested number of drives are not configured.These error messages indicate a mismatch between the

Labels: 7.1.x and Earlier Backup and Recovery Error messages HP-UX NetBackup Restore 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution! <16>bptestbpcd Main: Cannot Connect On Socket No Yes How can we make this article more helpful? server.acme.com not just short name e.g. "server". 0 Kudos Reply i check client is able to ________o Level 4 ‎04-10-2012 03:01 AM Options Mark as New Bookmark Subscribe Subscribe to RSS

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

The server list in the Netbackup BAR GUI on the client must show the media servers in use Domain names must be FQDN eg. 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 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. Netbackup Cannot Connect On Socket 25 Solaris 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

in /etc/hosts.allow) Windows 2008 clients may have the Domain Firewall, Private Firewall, and Public Firewall turned on. Email Address (Optional) Your feedback has been submitted successfully! Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! More about the author Hosts entries?

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 Join your peers on the Internet's largest technical computer professional community.It's easy to join and it's free. 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) RE: cannot connect on socket PGPhantom (IS/IT--Management) 12 Jan 04 14:42 What error??Specifics??

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 As soon as I switch Daemon connection port back to default we go back to the job failing. 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 No Yes How can we make this article more helpful?

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 If it does, rerun the backup. All i did is the normal procedures that i do to all my other servers but this one is not able to connect. 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

It is possible that updates have been made to the original version after this document was translated and published. e.g. 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) try with hostname and ipaddress 2.

Coz this is really strange problem i never faced before. Close this window and log in.