Home > Netbackup Error > Netbackup Error Code 58 In Windows Client

Netbackup Error Code 58 In Windows Client

Contents

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Thank You! Can't Connect to Client Solved Go to Solution nbu123 Level 5 ‎04-06-2013 06:26 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page netbackup fails with status 58 cannot connect to weblink

TCP dotto:vnetd dotto.veritas.com:0 LISTENING TCP dotto:bpcd dotto.veritas.com:0 LISTENINGFor UNIX client verify the ports are listening by issuing the same command-# netstat -a |grep bpcd *.bpcd *.* 0 0 49152 0 LISTEN#netstat The error above is expected because telnet did not provide the expected input per the bpcd protocol.  Notice also that 'localhost' is correctly determined not to be a valid NetBackup server. Select Master Server in the left pane4. https://www-secure.symantec.com/connect/forums/exit-status-58 0 Kudos Reply PLEASE create bpcd log folder Marianne Moderator Partner Trusted Advisor Accredited Certified ‎08-08-2012 06:39 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print

Netbackup Error Code 58 In Windows Client

bpcd log entries are needed to check/verify reverse lookup on client. bptestbpcd -client apsydnm01 bptestbpcd -client -verbose. 0 Kudos Reply « Previous 1 2 Next » Contact Privacy Policy Terms & Conditions Menu Close Search SOLUTIONS Solutions Overview Unstructured Connecting to the client host properties from the master server would prove the master server can access the client without any problems.

  • No Yes Did this article save you the trouble of contacting technical support?
  • The problem is more than likely with the client hostname lookup or gethostbyname call made to DNS or local host file on the media server.If the master server can not connect
  • You should see something like this -16:47:45.986 [5296.3376] bpcd main: offset to GMT 2160016:47:45.986 [5296.3376] bpcd main: Got socket for input 316:47:46.017 [5296.3376] logconnections: getsockname(3) failed: 10038 16:47:46.017 [5296.3376] bpcd setup_sockopts:
  • No Yes Did this article save you the trouble of contacting technical support?
  • View solution in original post 0 Kudos Reply 24 Replies Accepted Solution!
  • Article:000029870 Publish: Article URL:http://www.veritas.com/docs/000029870 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
  • Double check the server's NIC's IP address and netmask to ensure they are configured correctly.A very useful command to help with testing client and server resolution is the command -bpclntcmd -pn
  • It is possible that updates have been made to the original version after this document was translated and published.
  • Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : NetBackup : The status code 58 Can’t connect to client Subscribe to RSS Feed Mark Topic

philip_wernberg replied Aug 7, 2014 Can you ping the client? Creating a bprd log on the master server should show the incoming connection as well.The same bprd log when create on the master server would show the attempt to connect to Sorry, we couldn't post your feedback right now, please try again later. Netbackup Port Numbers telnet  13782That should generate a log entry as seen below showing the source host being recognized as a valid NB server. 16:52:46.077 [1160.5436] <2> bpcd main: offset to GMT 21600 16:52:46.077 [1160.5436] <2>

No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Netbackup Error Code 59 In some cases (Windows platforms), it has also been reported that rogue processes were present (for which a reboot is required to clear them), keeping the Vault job active well after If the telnet to 'localhost' works, try to telnet to the same TCP port from the source host. https://vox.veritas.com/t5/NetBackup/Status-58-can-t-connect-to-client/td-p/592102 http://www.symantec.com/business/support/index?page=content&id=TECH68832 Check fourms.

If it's not there could be a firewall blocking connectivity - check this out. Connect Failed Status (18) Connect_failed Still facing issues for few clients with status 58. Ensure the hostname and IP Address in /etc/hosts file. Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters.

Netbackup Error Code 59

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 Services Overview No Yes Did this article save you the trouble of contacting technical support? Netbackup Error Code 58 In Windows Client Kindly check the entry in /etc/hosts file. Bptestbpcd: Exit Status = 25 All product names are trademarks of their respective companies.

telnet: connect to address 10.62.12.21: Connection timed out telnet: Unable to connect to remote host: Connection timed out [[email protected] ~]# Notice this result from the master nbuserver [[email protected] ~]# telnet sungtong1 have a peek at these guys Create/Manage Case QUESTIONS? Handy NetBackup Links 0 Kudos Reply As suggested i have added the nbu123 Level 5 ‎04-06-2013 09:36 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email For each duplication copy, Vault theoretically assumes therefore that there are 8 write drives and basis its batch calculation on this, but in reality when executed, there are less than 8 Netbackup Cannot Connect On Socket

You're now being signed in. Run the following from cmd on master (and media server if they are different): bptestbpcd -client -debug -verbose. If DNS - is reverse lookup enabled? check over here When executed, the command does the following.    1.

No Yes How can we make this article more helpful? Status: Failed, (42) Connect_refused Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? If so, port 13724 (vnetd) needs to be open in both directions).

Labels: 7.1.x and Earlier Backup and Recovery NetBackup Troubleshooting Windows Server (2003-2008) 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution!

The hostname compare succeeds ...16:52:46.092 [1160.5436] <4> bpcd valid_server: hostname comparison succeeded 16:52:49.476 [1160.5436] <16> bpcd main: read failed: The operation completed successfully. 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 Most likely firewall software of some sort; see the Firewall topics above for some possibilities.Checking for Name Resolution DelaysWhen testing connections to bpcd and other daemons be sure to check the time difference delta Netbackup Error Code 48 Solved Go to Solution Sathisp83 Level 3 Certified ‎08-26-2013 11:33 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I'm

Thanks Solved! 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 Error Message can't connect to client Solution Overview: A Status 58 will occur when the server cannot connect to the client.  This can occur for standard backups when there are problems http://nodatasource.com/netbackup-error/netbackup-error-code-233.html If so, please post.

Post bpcd log file. Top Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving... If client cannot resolve server IP address to valid hostname that appears in Client's SERVER list, either fix reverse lookup in DNS or add server to client's hosts file. Create/Manage Case QUESTIONS?

Enable the bpcd log directory revarooo Level 6 Employee ‎08-26-2013 11:36 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Select the Client Attributes section6. When I go to host properties then client the client list then SELECT the Client I get the following “cannot connect on socket” I can ping the client from the master In the Connect Options tab for the client, make the following changes:BPCD connect back -> "Random port"Ports -> "Reserved port"Daemon connection port -> "Daemon port only"Note: You DO NOT have to

Then it goes into the policy database and lookup what hostname it is using when backing up the client server. No Yes Did this article save you the trouble of contacting technical support? Email Address (Optional) Your feedback has been submitted successfully! No Yes How can we make this article more helpful?

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 Vision 2016 Vision Launch the NetBackup Administration Console, connecting to the master server2.