Home > Cannot Create > Cannot Create Data Socket Connection Timed Out Netbackup
Cannot Create Data Socket Connection Timed Out Netbackup
Article:000040691 Publish: Article URL:http://www.veritas.com/docs/000040691 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 This issue is currently being considered by Symantec to be addressed in the next major revisionof the product. We need to see what is happening on the client as well. *** EDIT *** The timestamps in the logs also do not correspond with the Job details. 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 Source
The next timestamp is14:36: bptm starts at14:59. Host properties loaded with in a minute or two on both clients, which is a lot better than in the past. DNS? Handy NetBackup Links 0 Kudos Reply Accepted Solution! https://www.veritas.com/support/en_US/article.000089039
Consider the below scenario where bpbrm wants to fork bpbkar in client. Thanks for the logs - I will Marianne Moderator Partner Trusted Advisor Accredited Certified 03-29-2013 01:35 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to 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 bprd seems to come from media server instead of master server: bprd: canopus is not the primary server pabkp.nextel.com.br...exiting We need a full set of logs that contain information about
Then I'd probably look the bpcd logs to see what kind of connection errors you're getting. Errno = 32: Broken pipe Solution Overview:When a network socket hangs and stops delivering data, the NetBackup client process will eventually timeout and fail the backup. In this case, a network Check that the server is not running out of disk space, especially on its system drive which could be affecting its performance and VSS capabilities 3. Sometimes one of the clients will back up without issue, or a drive or 2 will backup without issue, while the rest will fail (ie C: will back up, but D:
We see above that restore was started at12:44 and failed at 12:48. If not done already set Nicolai Moderator Partner Trusted Advisor 03-29-2013 01:41 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate If there is an authentication problem or something with the DB, then it will usually show up there. https://vox.veritas.com/t5/NetBackup/Problems-with-backup-cannot-connect-on-socket-25/td-p/397975 Thank You!
I have no idea what this means: ....restore not initialized on netbackup How else are restores done if not on NetBackup? The netsh takes effect instantly, the registry keys require a reboot. Labels: 7.1.x and Earlier Backing Up Backup and Recovery NetBackup 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! The fourth child will also eventually suffer vnetd timeouts due to dbclient exiting while the bptm child was waiting for the third job. 07:48:29.556  <2> bpbrm process_media_msg: media manager for
DNS for resolution of hostnames. Sorry, we couldn't post your feedback right now, please try again later. Also a good step is to try to do a RMAN backup on its own (backup to disk) just to see if RMAN is working (has proper authentication, etc). Anyone run in to anything similar that might be able to shed some light on how to resolve this?
I had one client error out with status 13 on the system state, but when I reran the job it completed sucesfully. this contact form 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. Hosts entries? Handy NetBackup Links View solution in original post 0 Kudos Reply Accepted Solution!
Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE: 25, some restores are failing after upgrading to NetBackup 6.0 MP5 Error Symantec is committedto product quality and satisfied customers. Seems there was a problem with 'feedback' of successful restore to master : 12:24:24.537  <2> bpbrm write_msg_to_progress_file: (2201645.001) INF - TAR EXITING WITH STATUS = 0 12:24:24.538  <2> bpbrm have a peek here Did you add separate hostnames for multiple NICs in hosts file on client itself?
No Yes How can we make this article more helpful? To see what the state of your ports are you could do a netstat on the client. Handy NetBackup Links View solution in original post 0 Kudos Reply Accepted Solution!
Check both, please.
The jobs fail more often than they succeed. If there is a time difference between media server and master, please tell us exactly how much. We also need media server's bptm log that corresponds with timestamps in bpbrm log. 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
First things first, make sure the client and media server both have an Oracle license. Hi,Guys Restoring from a msanches Level 3 03-29-2013 08:23 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi,Guys Restoring For first, enable debug logging Yasuhisa_Ishika Level 6 Partner Accredited Certified 10-25-2011 05:21 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report http://skimwp.org/cannot-create/cannot-create-data-socket-error-0-0.php bpbkar.txt 547 KB bpcd.txt 16 KB 0 Kudos Reply Hi Repeatedly in the log you Mark_Solutions Moderator Partner Trusted Advisor Accredited Certified 10-26-2011 03:26 PM Options Mark as New Bookmark Subscribe