Home > Cannot Write > Cannot Write Data To Socket 10054 Netbackup

Cannot Write Data To Socket 10054 Netbackup

How you restore your databases from backup exchange 2007 when you migrate to 2010 ? status: 174: media manager - system error occurred
06/30/2015 18:41:11 - Error bpbrm (pid=5224) client restore EXIT STATUS 174: media manager - system error occurred A restore failing with a status 24:06/30/2015 EVIDENCE: bptm: 10:18:27.102 [3864.3952] <2> write_blocks: [1044] writing 4194303 data blocks of 512 10:18:32.696 [3864.3952] <2> set_job_details: Sending Tfile jobid (14050) 10:18:32.696 [3864.3952] <2> set_job_details: LOG 1265804312 16 bptm 3864 cannot Sorry, we couldn't post your feedback right now, please try again later. Check This Out

It is possible that updates have been made to the original version after this document was translated and published. What is Client Read Timeout set to on the media server? Best regards Rem Monday, January 02, 2012 5:29 PM Reply | Quote Answers 0 Sign in to vote Yes, original 2007 CCR servers are still in the org but without databases Maybe this is problem with Netbackup not Exchange ?

Connection seems OK but then everything stops - check the Application event log on the destination client to see if there are any clues 0 Kudos Reply Seems "something" terminated Anything in the logs? Email Address (Optional) Your feedback has been submitted successfully! I'm trying to restore this database like I always did, but this time with no success.

bpbkar on a media server is not involved in client restore. cannot write data to socket... On media server: bpbrm and bptm On destination client: bpcd and tar Please rename logs to reflect process names (e.g.bpbrm.txt) and post as attachments. How to Subscribe to Email Notification:Directly to this Article:Subscribe to this article by clicking on the Subscribe via email link on this page to receive notification when this article is updated

No Yes Did this article save you the trouble of contacting technical support? Privacy statement  © 2016 Microsoft. Error Message Status 24 - Socket write failed Solution Listed below are the contents of the bptm log:<16> write_bytes: cannot write data to socket, Broken pipe.<2> bpbrm read_media_msg: read from media https://vox.veritas.com/t5/NetBackup/Restore-on-Unix-failling-cannot-write-data-to-socket-10054/td-p/752784 No Yes How can we make this article more helpful?

My environement: 2 mailbox servers in CCR cluster, databases were backuped by Netbackup 7.0/7.1 with option VSS snapshot. HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config Buffer_Size = REG_DWORD = "262144" Terms of use for this information are found in Legal Notices.

Related Articles Article Languages x Translated Content Please note that this document is I would ask NetBackup on this one. I have ontrack powercontroll trial and when I use it, restor fails like above.

Labels: 7.6 Backup and Recovery NetBackup Windows Server (2003-2008) 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! How you restore your databases from backup exchange 2007 when you migrate to 2010 ? bpbkar on the media server and tar on the client are also relevant to have a look in. 0 Kudos Reply Re: Restore on Unix failling - cannot write data

Sorry, we couldn't post your feedback right now, please try again later. his comment is here You may also refer to the English Version of this knowledge base article for up-to-date information. Thank You! Maybe this is problem with Netbackup not Exchange ?

Thanks 0 Kudos Reply Re: Restore on Unix failling - cannot write data to socket, 10054 philalbert Level 4 ‎12-08-2015 08:04 AM Options Mark as New Bookmark Subscribe Subscribe to RSS I CAN do a restore from DESTINATION to DESTINATION, and from SOURCE to SOURCE, what I can´t do is from SOURCE to DESTINATION, so I assume it must be something related The error 10055 means "An operation on a socket could not be performed because the system lacked sufficient buffer space or because a memory queue was full." At this point, it this contact form Article:000025618 Publish: Article URL:http://www.veritas.com/docs/000025618 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

tar was ready to receive data, bptm tried to send data. nbsetconfig TAR_VERBOSE = 3 ??? The Ramiro-Magan Level 5 Certified ‎08-22-2012 01:46 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content oh, one more thing.

cannot...

Need help Please!!! bptm.txt) and upload as File attachments. status 5 2012-01-02 15:02:21 - Info tar32(pid=5376) done. Go to Solution.

It is possible that updates have been made to the original version after this document was translated and published. Destination client: Windows 2008 R2, Netbackup 7.1.0.4. Monday, January 02, 2012 6:20 PM Reply | Quote 0 Sign in to vote Ok, I wasnt clear when I saw "How you restore your databases from backup exchange 2007 when navigate here Handy NetBackup Links 0 Kudos Reply Re: Restore on Unix failling - cannot write data to socket, 10054 Michael_G_Ander Level 6 Certified ‎12-08-2015 01:56 AM Options Mark as New Bookmark Subscribe

Also, nothing was written on the destination server. 0 Kudos Reply « Previous 1 2 3 Next » Contact Privacy Policy Terms & Conditions Veritas.com Support Veritas Open Exchange Login Please suggest 04/06/2009 14:10:03 - begin Restore 04/06/2009 14:10:08 - number of images required: 1 04/06/2009 14:10:08 - media needed: 330078 04/06/2009 14:10:08 - media needed: 330068 04/06/2009 14:10:47 - restoring Create/Manage Case QUESTIONS?

Back to Top