Netbackup Error 50 Client Process Aborted
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 netbackup status code 50 Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research
Status Code 500
Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet client process aborted (50) : Error bpbrm ERR - Unable to backup System State or Shadow Copy. Article:000015095 Publish: Article URL:http://www.veritas.com/docs/000015095 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 NetBackup reports a failure when backing up System state or Shadow copy Components Error Message a) Identify the Clients related to the failed Backup Jobs in this case/example the problem is only related to 3 x Client … other Clients running fineb) check the Backup Policy File Selection ; in this case the Backup Policy set to backup ALL_LOCAL_DRIVES The backup fail with Status code 50 Oct 18, 2011 5:25:18 AM - connected; connect time: 0:00:00 Oct 18, 2011 5:25:22 AM - Error bptm (pid=28979) system call failed - Connection reset by peer (at child.c.1296) Oct 18, 2011 5:25:22 AM - Error bpbrm (pid=28976) from client
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 : Client process aborted(50) VOX : Backup and Recovery : NetBackup : https://www.veritas.com/support/en_US/article.000015095 Client process aborted(50) 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 Client process aborted(50) Mohannbu Level 4 08-02-2009 07:59 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content https://vox.veritas.com/t5/NetBackup/Client-process-aborted-50/td-p/252752 Dear All, Here is our NetBackup details: NetBackup 6.5.1 Master Server = HP UX B 11.11 Media Server = HP UX B 11.11 Client = Windows 2003 During the backup process it has failed with the below error. After couple of hours we have re-ran the backup it has completed successfully. We have checked in the Windows client, there hasn't been any error listed on the event log. 8/1/2009 11:17:09 PM - begin writing 8/1/2009 11:45:04 PM - Error nbjm(pid=29089) nbrb status: RB deallocated orphaned resources 8/1/2009 11:45:12 PM - end writing; write time: 00:28:03 client process aborted(50) Here is the artical which we have gone through, but it dosen't work for us. http://seer.entsupport.symantec.com/docs/295012.htm Policy Attributes: ~~~~~~~~~~~~~ Policy Name: WIN_W2K_FS_MERIDIAN_01 Policy Type: MS-Windows-NT Active: yes Effective date: 08/15/2002 13:13:19 Backup network drvs: no Collect TIR info: no Mult. Data Streams: no Client Encrypt: no Checkpoint: no Policy Priority: 0 Max Jobs/Policy: Unlimited Disaster Recovery: 0 Collect BMR info: no Residence: R08_VTL1L0_LTO_LCCNS052 Volume Pool: ONSITE Server Group: *NONE* Keyword:
backup or restore is in progress. Recommended Action: Do the following, as appropriate: Enable http://systemmanager.ru/nbadmin.en/nbu_50.htm detailed debug logging. Create a bpbkar debug log directory (UNIX, Linux, and Windows clients only). Create a bpcd debug log directory. (This log is created automatically on Macintosh clients.) On UNIX and Linux clients, add the VERBOSE option to the /usr/openv/netbackup/bp.conf file. On PC clients, increase the debug status code or log level. Retry the operation and examine the resulting logs. This error may occur if nbjm terminated while a backup job was running. Examine the unified logging files on the NetBackup server for nbjm (117) for more detail on the error. All unified logging is written to /usr/openv/logs status code 50 (UNIX and Linux) or install_path\NetBackup\logs (Windows). On UNIX and Linux clients, check for core files in the / directory. On UNIX and Linux clients, check the system log (/usr/adm/messages on Solaris) for system problems. This problem can sometimes be due to a corrupt binary. On UNIX and Linux clients, use the UNIX sum command to check the bpcd, bpbkar, and tar binaries, which are located in /usr/openv/netbackup/bin on the client. Reinstall them if they are not the same as in the client directory under /usr/openv/netbackup/client on the server. On a Windows client, check the bpinetd.exe, bpcd.exe, bpbkar32.exe, and tar32.exe files, which are located in the install_path\NetBackup\bin folder on the client. Reinstall the client if these files are as follows: Not the same size as on other Windows clients Not at the same release level Do not have the same NetBackup patches as other Windows clients