Create/Manage Case QUESTIONS? Improperly tuned TCP settings on the Windows backup servers. Veritas does not guarantee the accuracy regarding the completeness of the translation. Already a member? Source
Jonathan Dyck Re: [Veritas-bu] retrying Error on ... 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 Improper timeouts. Increase the client read and client connect timeouts. 4. https://www.veritas.com/support/en_US/article.000017083
ALL_LOCAL_DRIVES is set in backup selection list with multistreaming enabled. The backup said that it completed with a status 0. Weiterlesen... (http://www.symantec.com/connect/de/forums/could-not-write-keepalive-commsock) Skip to site navigation (Press enter) [Veritas-bu] retrying Error on job keeps going status 13 Preston, Douglas Mon, 12 Apr 2010 06:32:07 -0700 I had to replace the Can anyone help?AnasThis mail has been scanned by Symantec Mail Security for SMTP at UP.ORG.QA Justin Piszcz 2007-01-23 12:17:51 UTC PermalinkRaw Message The server version must be the newest version you
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 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 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 If the keep alive fails its often because the connection itself has been severed (broken TCP connection) This can also happen if the target machine is working on something and does
I just checked and it looks like 0 files backed up. No Yes How can we make this article more helpful? This greatly improved the stability of NetBackup.) -Michael -----Original Message----- From: Niehaus, Michael T. http://www.tek-tips.com/viewthread.cfm?qid=582093 Solution Adjust the Client Read Timeout on the Master Server to a smaller number. For example 60 seconds worked for the above issue.
Whenthe schedule runs, it connects to the client and then it just hangs andgives this statement:Error bpbrm(pid=5388) could not write KEEPALIVE to COMM_SOCKAfter about 4 hours, it gives back an error Can anyone help?AnasThis mail has been scanned by Symantec Mail Security for SMTP at UP.ORG.QA 1 Reply 1 View Switch to linear view Disable enhanced parsing Permalink to this page Thread Backups of the master server being taken while other backups are running. (Our guess: file locks and/or OTM prevent the image files from being updated, resulting in a failure on the 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
I increased the timeout settings on the client andMaster Server.Has anyone gone through this before? http://fixunix.com/veritas-net-backup/480799-could-not-write-keepalive-comm_sock.html Shekel Tal Re: [Veritas-bu] retrying Error on job keeps goi... 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
Resources Join | Indeed Jobs | Advertise Copyright © 1998-2016 ENGINEERING.com, Inc. http://birdsallgraphics.com/error-bpbrm/error-bpbrm-could-not-write-keepalive-to-comm-sock-netbackup.php 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 Virus software. I'd like to add one of my own to be considered: 5.
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) 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. Join Us! *Tek-Tips's functionality depends on members receiving e-mail. have a peek here URL: http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20060817/41662f59/attachment.html Thu Aug 17, 2006 6:24 am Display posts from previous: All Posts1 Day7 Days2 Weeks1 Month3 Months6 Months1 Year Oldest FirstNewest First Backup Central Forums Forum Index » Symantec
By joining you are opting in to receive e-mail. Thank You! VOX : Backup and Recovery : NetBackup : Backup failing for the drive which hosts the datab...
also,I would apply MP7 update which fixed a lot of things 0 Kudos Reply If this is an extremely alazanowski Level 5 02-23-2011 12:10 PM Options Mark as New Bookmark Subscribe Join UsClose Backup Central HomeMr. However, backup is failing for the drives which hosts the database. Dan -------------- next part -------------- An HTML attachment was scrubbed...
Turn off OTM and see if the problem continues to occur. You may also refer to the English Version of this knowledge base article for up-to-date information. Error Message Detail Status:7/3/2012 1:39:06 PM - Info bpbkar32(pid=3676) accelerator sent 283648 bytes out of 135932274688 bytes to server, optimization 100.0% 7/3/2012 1:39:22 PM - Error bpbrm(pid=1984) could not write KEEPALIVE Check This Out I just checked and it looks like 0 files backed up.
I'm seeing bundles and bundles of these errors and its on many of my NT servers. Register now while it's still free! Preston, Douglas [Veritas-bu] BPRESTORE flags.