Error Bpbrm Socket Read Failed
Contents |
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 error bpbrm socket read failed errno = 62 - timer expired Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語
Error Bpbrm(pid=) Socket Read Failed Errno = 62 - Timer Expired
한국어 Português Español USA Site: Veritas Veritas PartnerNet Backup fails with status 13 after bpbrm reports; socket read failed: netbackup error socket read failed errno = 62 - timer expired errno = 62 - Timer expired Article:000039058 Publish: Article URL:http://www.veritas.com/docs/000039058 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last
Socket Read Failed Errno = 62 - Timer Expired
Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem The backup is started and progressing, but then fails with status 13 after bpbrm reports the following condition. Error bpbrm (pid=XXXXX) socket read failed: errno = 62 - Timer expired netbackup socket read failed errno = 62 - timer expired Error Message The Job Details in the Activity Monitor shows that the backup was active and progressing until a time expired which caused the status 13. 09:00:12 started process bpbrm (pid=7249) 09:00:20 connecting 09:00:20 connected; connect time: 0:00:00 09:06:20 Error bpbrm (pid=7249) socket read failed: errno = 62 - Timer expired 09:06:20 end writing file read failed (13) The bpbrm debug log confirms that the media manager has mounted and positioned the media but after some amount of time a timer expired. The log may or may not show any meta data arriving from the client before the failure. However, the gap in the timestamps will exceed the current CLIENT_READ_TIMEOUT setting on the media server. This will cause bpbrm to terminate bptm. 09:00:20.183 [7249] <2> write_file_names: successfully wrote buffer to COMM_SOCK 09:00:20.183 [7249] <2> bpbrm write_filelist: wrote CONTINUE on COMM_SOCK 09:00:20.183 [7249] <2> bpbrm write_filelist: closing COMM_SOCK 12 09:00:42.975 [7249] <2> bpbrm mm_sig: received ready signal from media manager 09:06:20.087 [7249] <16> bpbrm readline: socket read failed: errno = 62 - Timer expired When bpbrm and bptm terminate, the network sockets to the client wil
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision
Netbackup Vmware Socket Read Failed Errno = 62 - Timer Expired
2016 Sign In
Symantec Socket Read Failed Errno = 62 - Timer Expired
CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches error bpbrm no worklist items returned from bpresolver on client as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : Error bpbrm (pid=12433) socket read failed: errno ... https://www.veritas.com/support/en_US/article.TECH71821 VOX : Backup and Recovery : NetBackup : Error bpbrm (pid=12433) socket read failed: errno ... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Error bpbrm (pid=12433) socket read failed: errno = 62 - Timer expired Avinash Level 2 Certified 04-17-2009 01:29 https://vox.veritas.com/t5/NetBackup/Error-bpbrm-pid-12433-socket-read-failed-errno-62-Timer-expired/td-p/230782 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Iam getting error 13 with the following details. Can anyone help with the cause/resolution of this error ? 04/17/2009 13:54:51 - requesting resource NTTA-Shared-Onsite-CDL1 04/17/2009 13:54:51 - requesting resource iadehbkwhms.NBU_CLIENT.MAXJOBS.srvr19031-be 04/17/2009 13:54:51 - requesting resource iadehbkwhms.NBU_POLICY.MAXJOBS.GMP-46002469-sol-os-enc-01 04/17/2009 13:54:52 - granted resource iadehbkwhms.NBU_CLIENT.MAXJOBS.srvr19031-be 04/17/2009 13:54:52 - granted resource iadehbkwhms.NBU_POLICY.MAXJOBS.GMP-46002469-sol-os-enc-01 04/17/2009 13:54:52 - granted resource AI0063 04/17/2009 13:54:52 - granted resource Drive025 04/17/2009 13:54:52 - granted resource iadehbkmd04-be-hcart2-robot-tld-6 04/17/2009 13:54:52 - estimated 58333401 kbytes needed 04/17/2009 13:54:53 - started process bpbrm (pid=12426) 04/17/2009 13:54:58 - connecting 04/17/2009 13:54:59 - connected; connect time: 0:00:00 04/17/2009 13:54:59 - mounting AI0063 04/17/2009 13:55:06 - mounted AI0063; mount time: 0:00:07 04/17/2009 13:55:06 - positioning AI0063 to file 55 04/17/2009 13:55:06 - positioned AI0063; position time: 0:00:00 04/17/2009 13:55:06 - begin writing 04/17/2009 13:59:51 - current media AI0063 complete, requesting next media Any 04/17/2009 13:59:52 - granted resource AI0090 04/17/2009 13:59:52 - granted resource Drive023 04/17/2009
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 https://www.veritas.com/support/en_US/article.TECH57100 Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet General Error: Status code 23, socket read failed, https://vox.veritas.com/t5/NetBackup/Error-bpbrm/td-p/380998 during client backups or restores, or when loading client properties. Article:000090314 Publish: Article URL:http://www.veritas.com/docs/000090314 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a socket read 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 General Error: Status code 23, socket read failed, during client backups or restores, or when loading client properties. Error Message Status code 23, socket read failed socket read failed Cause The keyfile.dat file in the
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : Error bpbrm VOX : Backup and Recovery : NetBackup : Error bpbrm Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution Error bpbrm mb_jedsv Level 4 Certified 03-22-2011 11:16 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi, when the backup time schedule changed , the backup written 50% from data andI got the follwoing err. 03/22/2011 14:25:00 - positioning MS0366 to file 55 03/22/2011 14:25:39 - positioned MS0366; position time: 0:00:39 03/22/2011 14:25:39 - begin writing 03/22/2011 14:32:23 - Error bpbrm (pid=15239) socket read failed: errno = 62 - Timer expired 03/22/2011 14:32:26 - Error bptm (pid=15242) media manager terminated by parent process 03/22/2011 14:32:55 - end writing; write time: 0:07:16 file read failed (13) Best Regard Solved! Go to Solution. Labels: 7.1.x and Earlier Backing Up Backup and Recovery Error messages NetBackup 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! http://www.symantec.com/docs/ RiaanBadenhorst Moderator Partner Tr