Error Bpbrm Could Not Write Exit Status To Outsock
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 Relations
Dps_proxydefaultrecvtmo
Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português netbackup could not write file added message to outsock Español USA Site: Veritas Veritas PartnerNet VMware backup with "File Level Recovery" fails with Status 636 due to disconnect overstock between Master and Media Server Article:000021452 Publish: Article URL:http://www.veritas.com/docs/000021452 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 Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem When performing a VMware Backup with File Level Recovery, if there is no updates to the Master server for an extended period of time then the Master and media server socket may be disconnected by a firewall in between. By default most firewalls will disconnect after 2 hours when they are no updates. Error Message bpbrm: 12:10:23.472 [3644.4264] <2> bpbrm main: ADDED FILES TO DB FOR VMCLIENT_1396281339 250 v4recovery19:24:46.066 [3644.4264] <2> put_strlen_str: cannot write data to network: An existing connection was forcibly closed by the remote host.19:24:46.066 [3644.4264] <16> bpbrm main: could not write FILE ADDED message to OUTSOCK19:24:46.066 [3644.4264] <2> set_job_details: Tfile (263102): LOG 1396308286 16 bpbrm 3644 could not write FILE ADDED message to OUTSOCK Detail Status: 3/31/2014 11:55:45 AM - begin writing3/31/2014 11:57:09 AM - Info bpbkar32(pid=2844) 0 entries sent to bpdbmread from input socket failed(636)3/31/2014 7:24:46 PM - Error bpbrm(pid=3644) could not write FILE ADDED message to OUTSOCK3/31/2014 7:24:51 PM - Error bpbrm(pid=3644) could not write FILE ADDED message to OUTSOCK3/31/2014 7:24:56 PM - Error bpbrm(pid=3644) could not write FILE ADDED message to OUTSOCK3/31/2014 7:25:01 PM - Error bpbrm(pid=3644) could not write FILE ADDED message to OUTSOCK3/31/2014 7:25:06 PM - Error bpbrm(pid=3644) could not write FILE ADDED message to OUTSOCK3/31/2014 7:25:11 PM - Error bpbrm(pid=3644) could not write FILE ADDED message to OUTSOCK3/31/2014 7:25:16 PM - Error bpbrm(pid=3644) could not wr
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 Status 87 and Status 40 on long running Client side deduplication jobs across a slow connection Article:000017962 Publish: Article URL:http://www.veritas.com/docs/000017962 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First https://www.veritas.com/support/en_US/article.000021452 Last 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 Client side deduplication backups are failing with Status 87 and/or Status 40 for remote clients across the WAN/firewall. The error occurred at either the end of a storage unit fragment https://www.veritas.com/support/en_US/article.TECH206337 or at the end of a backup when the last [or only] fragment is closed.Backups of short duration are not affected, but those that run longer are always affected. Error Message The Job Details will show the lengthy runtime for the job, the slow transfer performance over the WAN, and that the job ended with status 87 after the client had transferred the entire image.05/02/2013 18:51:04 - Info bptm (pid=5186) setting receive network buffer to 262144 bytes05/02/2013 22:21:41 - Info bpbkar (pid=8736) bpbkar waited 18630 times for empty buffer, delayed 578492 times05/02/2013 22:21:52 - Critical bptm (pid=5186) sts_close_handle failed: 2060017 system call failed05/02/2013 22:21:52 - Critical bptm (pid=5186) cannot write image to disk, media close failed with status 206001705/02/2013 22:21:53 - Info b7pnbmed1 (pid=5186) StorageServer=PureDisk:nbmed1; Report=PDDO Stats for (nbmed1): scanned: 24659201 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%05/02/2013 22:21:53 - Critical bptm (pid=5186) sts_close_server failed: error 2060005 object is busy, cannot be closed05/02/2013 22:23:32 - Info bptm (pid=5186) EXITING with status 87 <----------05/02/2013 22:23:34 - Info bpbkar (pid=8736) done. status: 87: media close error05/02/2013 22:23:34 - end writing; write time: 3:
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer https://www.veritas.com/support/en_US/article.TECH150369 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 STATUS CODE 24: Socket write failed Article:000011538 Publish: Article URL:http://www.veritas.com/docs/000011538 Support / Article Sign could not 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 Related Articles Article Languages Subscribe to this Article Manage could not write your Subscriptions Problem A write operation to a socket failed on a Windows client. Status code 24 is reported. These are possible causes for this issue: High network loadIntermittent connectivityPacket reorderingDuplex mismatch between client and master server NICsSmall network buffer size Error Message bpbkar logs:2:18:23.023 PM: [1912.2224] <2> TransporterRemote::write[2](): DBG - | An Exception of type [SocketWriteException] has occured at: | Module: @(#) $Source: src/ncf/tfi/lib/TransporterRemote.cpp,v $ $Revision: 1.51 $ , Function: TransporterRemote::write[2](), Line: 307 | Local Address: [::]:0 | Remote Address: [::]:0 | OS Error: 10054 (An existing connection was forcibly closed by the remote host. bpbrm logs:14:18:23.075 [32163] <32> bpbrm handle_backup: from client Lonzippy: FTL - socket write failed 14:18:23.130 [32163] <2> job_monitoring_exex: ACK disconnect
14:18:23.130 [32163] <2> job_disconnect: Disconnected
14:18:23.130 [32163] <4> db_error_add_to_file: from client Lonzippy: FTL - socket write failed
14:18:23.179 [32163] <2> bpbrm handle_backup: client Lonzippy EXIT STATUS = 24: socket write failed
14:18:23