Netbackup Error 89
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 problems encountered during setup of shared memory (89) Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français technote 183702 Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE 89: Increasing shared memory does not prevent backups from failing with a NetBackup Status Code 89 (problems encountered during setup of shared memory). Article:000033538 Publish: Article URL:http://www.veritas.com/docs/000033538 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 STATUS CODE 89: Increasing shared memory does not prevent backups from failing with a NetBackup Status Code 89 (problems encountered during setup of shared memory). Error Message problems encountered during setup of shared memory Solution Overview: It is possible that increasing the shared memory kernel parameters based on the calculation in TechNote 183702 (see Related Documents below) will not prevent backup from failing with a NetBackup Status Code 89, especially when backing up a large number of windows clients using the backup selection directive ALL_LOCAL_DRIVES. If the amount of shared memory configured in the kernel is adequate based on the shared memory formula, then other possible sources of the status 89 will need to be investigated.Troubleshooting: Reducing the value configured in the /usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS file may resolve the problem.Log files: N/A Resolution: The shared memory calculation in TechNote 183702 is used to determine the NetBackup media server recommended minimum kernel requirements. It is also used for every UNIX platform that has the option to set tunable kernel parameters (Solaris, Linux, HP-UX). In large environments that are growing, it does become obvious that the recommended minimum kernel parameters (the ones include in the installation guide along with shared m
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 : Netbackup Error 89 https://www.veritas.com/support/en_US/article.TECH59841 VOX : Backup and Recovery : NetBackup : Netbackup Error 89 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 Netbackup Error 89 virankumar Level 4 12-29-2014 07:57 AM Options Mark as New Bookmark Subscribe Subscribe to https://vox.veritas.com/t5/NetBackup/Netbackup-Error-89/td-p/712566 RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello Team, We are facing issue with few client s in netbackup 6.5.6 version 89 error , for particular region 10 servers effected with this error client version and OS versions are solaris/6.5.6 Destails log for one client ----------------- Dec 28, 2014 6:53:00 PM - requesting resource bnmlw-Disk-stage Dec 28, 2014 6:53:00 PM - requesting resource south-nbumast-01.NBU_CLIENT.MAXJOBS.cnmlw-ivm-014-bsn Dec 28, 2014 6:53:00 PM - requesting resource south-nbumast-01.NBU_POLICY.MAXJOBS.cnmlw-ivm-014_rman Dec 28, 2014 7:05:56 PM - Error bpbrm (pid=26530) Could not get shared memory for bpbrm child process communication, No space left on device (28) Dec 28, 2014 7:05:53 PM - granted resource south-nbumast-01.NBU_CLIENT.MAXJOBS.cnmlw-ivm-014-bsn Dec 28, 2014 7:05:53 PM - granted resource south-nbumast-01.NBU_POLICY.MAXJOBS.cnmlw-ivm-014_rman Dec 28, 2014 7:05:53 PM - granted resource MediaID=@aaaam;Path=/bnmlw-medi-01-stu1;MediaServer=bnmlw-medi-01 Dec 28, 2014 7:05:53 PM - granted resource bnmlw-medi-01-nbu_staging-01 Dec 28, 2014 7:05:54 PM - estimated 0 kbytes needed Dec 28, 2014 7:05:55 PM - started process bpbrm (pid=2
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 https://www.veritas.com/support/en_US/article.000014140 Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English http://symcnbu.blogspot.com/2010/04/solaris-10-tuning.html Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Status 89: Shared memory error. Linux RedHat Media Server is not processing backup jobs. Article:000014140 Publish: Article URL:http://www.veritas.com/docs/000014140 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account netbackup error 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 Status 89: Shared memory error. Linux RedHat Media Server is not processing backup jobs. Error Message BPTM LOG 07:59:49.664 [9290] <16> mpx_setup_shm: could not allocate enough netbackup error 89 shared memory for backup buffers, No space left on device 07:59:49.665 [9290] <2> send_brm_msg: ERROR 89 Cause Linux OS is issuing an error - ENOMEM No memory could be allocated for segment overhead. Shared memory limit setting has been reached. To view active shared memory- # ipcs -m To view server SHMMAX limit- # cat /proc/sys/kernel/shmmax # grep shmmax /etc/sysctl.conf Solution Adjust Linux server OS SHMMAX setting. Check server memory size # cat /proc/meminfo | grep MemTotal # free -m (megabytes) # free -b (bytes) Change shared memory setting # echo
problems encountered during setup of shared memory Details: Introduction Prior to Solaris 10, shared memory tuning was performed by adding or changing entries in the/etc/systemfile and rebooting the server - see TechNote 295295 (linked below) for advice on tuning Solaris 9 and earlier. With the introduction of Solaris 10, Sun have deprecated the use of/etc/systemsettings and introduced the Resource Controls Facility. This allows projects to be created for applications and the resources tuned dynamically on a per-project basis. As part of this change, Sun set the default amount of shared memory to be 25% of the total system memory. For most NetBackup media server configurations this default will be sufficient. If not then NetBackup jobs may fail with the error: EXIT STATUS 89: problems encountered during setup of shared memory If this happens, the instructions in this TechNote should be used. This TechNote is divided into two sections:First Time Setup Modifying the Tuning To check if the first time setup has already been performed, use theprojectscommand. If first time setup has not been performed, a message similar to the following will be displayed: #/bin/projects -l NetBackup projects: project "NetBackup" does not exist First Time Setup Here are the steps to create a project for NetBackup and have the Solaris 10 Service Management Facility (SMF) launch NetBackup daemon processes in that project. This results in thebptmprocess being launched with the values tuned in the NetBackup project. First create a NetBackup project (id = 1000) and "tune" it. The following example sets the maximum amount of shared memory to 8GB: (The commands below have had line breaks inserted for readability, but each should be entered on a single command line.) #/usr/sbin/projadd -U root -c "NetBackup resource project" -p 1000 NetBackup #/usr/sbin/projmod -a -K 'project.max-shm-ids=(privileged,256,deny)' NetBackup #projmod -a -K 'project.max-sem-ids=(privileged,1024,deny)' NetBackup #projmod -a -K 'project.max-msg-ids=(privileged,256,deny)' NetBackup #projmod -a -K 'project.max-shm-memory=(privileged,8589934592,deny)' NetBackup Note:TechNote 183702 (linked below) contains advice on