See the following Qarticle from MS concerning keepalives (and other topics) http://support.microsoft.com/kb/120642/en-us Hope that helps Steve On 8/16/06, Sixbury, Dan
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 Can anyone help? Day QRS Systems Engineer [Morewiththissubject...]
Improperly tuned TCP settings on the Windows backup servers. Increase the client read and client connect timeouts. 4. Thanks.
No Yes How can we make this article more helpful? RC = 126 (0x7e) - The specified module could not be found.!!! 10:50:39.753 AM: [5496.4724] <2> ov_log::V_GlobalLog: INF - loaded nbbeese.dll 10:50:39.753 AM: [5496.4724] <2> ov_log::V_GlobalLog: INF - loaded nbbedsmdoc.dll 10:50:39.753 Speed, duplex, flow control, checksum offloading. Any ideas on what causes the keepalive on comm_sock errors and how to fix?
Close Reply To This Thread Posting in the Tek-Tips forums is a member-only feature. Justin. Preston, Douglas Reply via email to Search the site The Mail Archive home veritas-bu - all messages veritas-bu - about the list Expand Previous message Next message The Mail Archive home http://www.tek-tips.com/viewthread.cfm?qid=582093 Preston, Douglas [Veritas-bu] BPRESTORE flags.
You may also refer to the English Version of this knowledge base article for up-to-date information. There are three local volumes on the client. Microsoft SQL server 2008 is installed on the client the error is : 2/22/2011 11:13:46 AM - Error bpbrm(pid=5128) could not write KEEPALIVE to COMM_SOCK 2/22/2011 11:22:22 AM - Error bpbrm(pid=5128) I saw multiple errors that read Error bpbrm (pid-14867) could not write KEEPALIVE to COMM_SOCK The backup was just one file system, not a ton of data, and a 7 year
You are welcome to try and let us know. http://dbaspot.com/arch/254818-veritas-netbackup-could-not-write-keepalive-comm_sock-help.html I'm seeing bundles and bundles of these errors and its on many of my NT servers. The other problem jobs show backup for a while but never complete. Master server Job log 4/6/2010 10:01:33 AM - requesting resource scacidoc05-hcart2-robot-tld-0 4/6/2010 10:01:33 AM - requesting resource svcacibu1.NBU_CLIENT.MAXJOBS.scacidoc05 4/6/2010 10:01:33 AM - requesting resource svcacibu1.NBU_POLICY.MAXJOBS.1-doc05-test 4/6/2010 10:01:33 AM - granted resource
Has anyone gone through this before? navigate here Click Here to join Tek-Tips and talk with other members! Review this technote: http://www.symantec.com/business/support/index?page=content&id=TECH56950&actp=search&viewlocale=en_U... Dan -------------- next part -------------- An HTML attachment was scrubbed...
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... These have the following messages in my bpbrm log.
23:59:02.526  <2> put_long: (11) network write() error: Broken pipe (32); socket = 8
23:59:02.526  <16> bpbrm hostcentric ! Check This Out Has anyone gone through this before?
Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Servers with flaky NIC drivers - upgrade to the latest from the appropriate vendor. (If you use Compaq NC adapters, consider using the Intel drivers instead of Compaq's, especially if you From: "April Kelley"
Any ideas on what causes the keepalive on comm_sock errors and how to fix? Sent: Friday, August 09, 2002 10:42 PM To: 'veritas-bu AT mailman.eng.auburn DOT edu' Subject: RE: [Veritas-bu] could not write KEEPALIVE to COMM_SOCK Some reasons I've seen so far (not that I Now I installed the agent from Netbackup 6.0 on the RedHat Machine. this contact form Preston, Douglas Re: [Veritas-bu] retrying Error on job k...
com> Date: 2005-03-29 8:08:25 Message-ID: AF1B69593785D847AF580EA413F5E87029A684 () fmtmail ! No connection time outs, \ nothing. They are all windows clients. You can disable VSS or VSP snapshotting under the client attributes portion on the master server properties.
Register now while it's still free! Don't really know what the problem is. Join UsClose Backup Central HomeMr. Anas Tue Jan 23, 2007 4:05 am Justin Piszcz Guest Linux Backup The server version must be the newest version you have.
I increased the timeout settings on the client and Master Server. Anas This mail has been scanned by Symantec Mail Security for SMTP at UP.ORG.QA _______________________________________________ Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu Tue Jan 23, 2007 4:20 am Display The backup said that it completed with a status 0. All rights reserved.Unauthorized reproduction or linking forbidden without expressed written permission.
When the schedule runs, it connects to the client and then it just hangs and gives this statement: Error bpbrm(pid=5388) could not write KEEPALIVE to COMM_SOCK After about 4 hours, it Cancel Red Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts.The Tek-Tips staff will check this out and take appropriate action. Any one have ideas? Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : Backup failing for the drive which hosts the datab...