NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 89

Media Manager status code 89
HOWTO104468 | 2014-11-20
How To | CMS-XML

Device configuration status code 89

Device configuration status code 89
HOWTO104624 | 2014-11-20
How To | CMS-XML

NetBackup status code: 89

NetBackup status code : 89
HOWTO104016 | 2014-11-20
How To | CMS-XML

STATUS CODE 89: NetBackup could not allocate enough shared memory for backup buffer control on Solaris 10 media servers.

The Status 89 is an OS error (ENOMEM) Status 89 error comes from one or more of the following - Low shared memory limit (shmmax)
TECH56434 | 2012-12-30
Technical Solutions | CMS-XML

Backups running on a Solaris media server return status 89.

Backups running on a Solaris media server return status 89 .
TECH187992 | 2012-11-18
Technical Solutions | CMS-XML

Backups are failing with status code 89

2/1/2012 7:37:53 PM - Error bptm(pid=7896) The Global\NetBackup Media Manager SHM MPX Path 544580208 7896 0 shared memory file already exists. 2/1/2012 7:37:58 PM - end writing problems encountered during setup of shared memory( 89 )
TECH181624 | 2012-07-28
Technical Solutions | CMS-XML

Backups fail intermittently with status 89 if insufficient shared memory identifiers are available

Backups fail intermittently with status 89 if insufficient shared memory identifiers are available
TECH75597 | 2012-06-02
Technical Solutions | CMS-XML

Status 89: Shared memory error. Linux RedHat Media Server is not processing backup jobs.

BPTM LOG 07:59:49.664 [9290] 16 mpx_setup_shm: could not allocate enough shared memory for backup buffers, No space left on device 07:59:49.665 [9290] 2 send_brm_msg: ERROR 89
TECH171052 | 2011-10-06
Technical Solutions | CMS-XML

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).

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
TECH59841 | 2010-10-17
Technical Solutions | CMS-XML

Status 89, Job status is showing error: Could not attached shared memory. Errno = 22: Invalid argument

Status 89 , Job status is showing error : Could not attached shared memory. Errno = 22: Invalid argument
TECH66886 | 2009-01-11
Technical Solutions | CMS-XML

NetBackup status code 89: problems encountered during setup of shared memory

89
TECH58019 | 2009-01-12
Technical Solutions | CMS-XML

Shared Memory Errors STATUS 89 on hp-ux

Shared Memory Errors STATUS 89 on hp-ux
TECH64971 | 2009-01-03
Technical Solutions | CMS-XML

Backup failed with 89 error code... | Symantec Connect

Backup failed with 89 error code...
Connect Forums | HTML

Oracle RMAN restore fails with status 2801 when starting Client Direct job from the GUI

13:25:45.753 [28548] 4 dbc_write_to_progress_log: entering 13:25:45.753 [28548] 4 dbc_remotewritefile: myclient orac121 89 /usr/openv/netbackup/logs/user_ops/root/logs/jbp-2792441101690811705100 0000005-ottxbz.log a 26 INF - Restore id: 820.001
TECH225059 | 2014-09-29
Technical Solutions | CMS-XML

Restore of Microsoft Exchange Mailbox partially successful with 2810 ERROR:(BEDS 0xe000fe2d: The backup of the item is bad)

0,51216,158,352, 89 ,1401389273894,22308,19480,0:,87:fs_writeobj() Failure! (0xe000fe2d:The backup of the item is bad
TECH217963 | 2014-05-30
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?