Netbackup Error Bpbrm Could Not Write Keepalive To Comm_sock
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet NetBackup Accelerator Backups may show "could not write KEEPALIVE to COMM_SOCK" when they are small changes on the file system Article:000017083 Publish: Article URL:http://www.veritas.com/docs/000017083 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 to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem When they are no changes or small changes between the last full backup, NetBackup Accelerated backup may show "could not write KEEPALIVE to COMM_SOCK" in the Detail Status of the backup. 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 to COMM_SOCK Cause Since almost nothing changed since the last Full Backup, the client has to go through all back up selection without getting a chance to communicate with bpbrm, thus bpbrm could not communicate with bpbkar as it is quite busy processing. Solution Adjust the Client Read Timeout on the Master Server to a smaller number. For example 60 seconds worked for the above issue. Disabing Change Journal may also work, but this is unconfirmed. Terms of use for this information
FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: https://www.veritas.com/support/en_US/article.000017083 Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Symantec: NetBackup Forum at Tek-Tips HomeForumsServer RackBack-up SystemsSymantec: NetBackup Forum Could not write KEEPALIVE to COMM_SOCK thread776-582093 Forum Search FAQs Links http://www.tek-tips.com/viewthread.cfm?qid=582093 MVPs Could not write KEEPALIVE to COMM_SOCK Could not write KEEPALIVE to COMM_SOCK nb45 (IS/IT--Management) (OP) 20 Jun 03 12:57 When the backup is running in some momment the client report the follow error "could not Write KEEPALIVE to COMM_SOCK" and the task never ending.How can resolve this problem? RE: Could not write KEEPALIVE to COMM_SOCK PGPhantom (IS/IT--Management) 20 Jun 03 13:33 Is this a constant issue?Do it happen a specific times or is it random?What I have seen in errors like this is that network connections are either not set up such as the NIC being set for 100/full as well as switches, Flow control not being set to Rx/Tx and bad cables.I assume this is a backup from a client to a media server?I would also check your physical drive and connections as SCSI bins have been the culprit in some cases such as bent pins, not connecting properly etc - What kind of drive, how is it connected, what O/S and what version of NB
AT MarathonOil DOT com (Niehaus, Michael T.) Date: Tue, 20 Aug 2002 23:40:13 -0500 I've got two more items to add to my list: 6. Servers with flaky NIC drivers - upgrade to the latest from the appropriate vendor. (If you use Compaq https://adsm.org/lists/html/Veritas-bu/2002-08/msg00364.html NC adapters, consider using the Intel drivers instead of Compaq's, especially if you are doing teaming.) 7. Improperly tuned TCP settings on the Windows backup servers. Make sure the "MaxUserPort" setting is large enough, http://backupcentral.truthinit.com/phpBB2/viewtopic.php?t=54870&start=0&postdays=0&postorder=asc&highlight=&sid=14bb0522fa40e69ced45dcea523ee147 and consider shrinking the "TcpTimedWaitDelay". (I set mine to 65534 and 30, respectively. This greatly improved the stability of NetBackup.) -Michael -----Original Message----- From: Niehaus, Michael T. Sent: Friday, August 09, 2002 10:42 PM netbackup error 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 necessarily endorse all the suggestions - I'm just repeating them): 1. Improper network settings: duplex and speed should be forced to match switch settings on fast Ethernet connections. 2. Virus software. It may interfere with backups; turn it off for the duration of the backups. netbackup error bpbrm 3. Improper timeouts. Increase the client read and client connect timeouts. 4. OTM configuration issues. Turn off OTM and see if the problem continues to occur. I'd like to add one of my own to be considered: 5. 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 master server seen as a network drop from the client. We recently moved the backups for the backup servers [master and media] to a quiet time.) -Michael -----Original Message----- From: veritas-bu-admin AT mailman.eng.auburn DOT edu [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Day, Michael Sent: Friday, August 09, 2002 1:46 PM To: 'veritas-bu AT mailman.eng.auburn DOT edu' Subject: [Veritas-bu] could not write KEEPALIVE to COMM_SOCK Anyone have any info on the following error I keep on seeing in my 'Problem with backups' reports? "could not write KEEPALIVE to COMM_SOCK". I'm seeing bundles and bundles of these errors and its on many of my NT servers. I'm also getting many error 14's and 41's but my backups are completing with multiple retries due to network related problems. Michael H. Day QRS Systems Engineer [Morewiththissubject...] FAQForumsJoin Our Forums!General TopicsBakBone NetVaultCA Brighstor ARCserveCommVault GalaxyEMC NetWorkerHP Data ProtectorIBM TSMSymantec Backup ExecSyncSort Backup ExpressSymantec NetBackupOpen-Source AmandaOpen-Source BackupPCOpen-Source BaculaOpen-Source Rdiff-BackupOpen-Source RsnapshotWikiRecent ChangesSpecial PagesPopular PagesCategoriesContact CurtisYour AccountYour DetailsMaintain SiteLogoutYours Search • FAQ • Memberlist • Log in Backup Central Forums Forum Index » Symantec NetBackup » Linux Backup The time now is Thu Oct 20, 2016 6:29 pm View previous topic | View next topic Page 1 of 1 Linux Backup Author Message Anas Kayal Guest Linux Backup We just added a new RedHat 2.4 machine. Im running Netbackup 5.1 MP5. Now I installed the agent from Netbackup 6.0 on the RedHat Machine. 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 gives back an error 41. The total data size is only about 20GB. I increased the timeout settings on the client and Master Server. Has anyone gone through this before? Can anyone help? Anas Tue Jan 23, 2007 4:05 am Justin Piszcz Guest Linux Backup The server version must be the newest version you have. A 5.1 server cannot backup a 6.0 client. Is that what you are trying to do? Justin. On Tue, 23 Jan 2007, Anas Kayal wrote: We just added a new RedHat 2.4 machine. Im running Netbackup 5.1 MP5. Now I installed the agent from Netbackup 6.0 on the RedHat Machine. 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 gives back an error 41. The total data size is only about 20GB. I increased the timeout settings on the client and Master Server. Has anyone gone through this before? Can anyone help? 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 posts from previous: All Posts1 Day7 Days2 Weeks1 Month3 Months6 Months1 Year Oldest FirstNewest First Backup Central Forums Forum Index » Symantec NetBackup » Linux Backup The time now is Thu Oct 20, 2016 6:29 pm | All times are GMT - 8 Hours Page 1 of 1 You cannot post new topics in this forumYou cannot reply to topics in thi