[Veritas-bu] status 89 out of the blue

Jorgensen, Bill Bill_Jorgensen at csgsystems.com
Wed Mar 23 09:36:37 CST 2005



As I read your value for shmmax it seems to be 16MB of shared memory. If
you are running a media manager on the same server as an Oracle database
or two this will most likely not be enough. This may also be the case on
the master when it comes to streaming data. If these are Sun servers Sun
recommends not exceeding the 25% mark when it comes to allocating shared
memory on the system. (If you have 4GB of physical try not to go over
1GB of shared memory.)

Take 1048576 (1MB) x # (number of megs) of shared memory you want. Do
not forget to bump up the number of semaphores. Not increasing the
semaphores can/will limit how many tape drives that can be accessed
simultaneously. It can mess with any multiplexing you are trying to do.

**----- determine shared memory segment size -----**
data buffer size x number of buffers
number of buffers = multiplex setting on the storage unit x number of

root[prod-backup:/export/openv/netbackup/db/config]# ls
.Grpid                cat_format.cfg        user_retention
NUMBER_DATA_BUFFERS   shm/                  user_retention.bak
SIZE_DATA_BUFFERS     storage_units         x.FIX_LENGTH_BLOCKS
behavior              sync
root[prod-backup:/export/openv/netbackup/db/config]# cat *BUFFERS

As a result this is what we have configured:
root[prod-backup:/]# prtdiag -v | head
System Configuration:  Sun Microsystems  sun4u Sun Enterprise 450 (4 X
UltraSPARC-II 400MHz)
System clock frequency: 100 MHz
Memory size: 4096 Megabytes

root[prod-backup:/]# sysdef -i | grep -i memory
* IPC Shared Memory
1073741824      max shared memory segment size (SHMMAX)

If I have done MY math right we have a gig defined. The basic formula
above has helped us I hope it will do the same for you.

Good luck,


     Bill Jorgensen
     CSG Systems, Inc.
     (w) 303.200.3282
     (p) 303.947.9733
     UNIX... Spoken with hushed and
     reverent tones.

-----Original Message-----
From: veritas-bu-admin at mailman.eng.auburn.edu
[mailto:veritas-bu-admin at mailman.eng.auburn.edu] On Behalf Of Dave
Sent: Wednesday, March 23, 2005 4:16 AM
To: veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] status 89 out of the blue

Has anyone seens a status 89 unable to setup shared memoty all of a 
sudden out of the blue when no changes have been made?

Im running netbackup 5.0mp3 master/media and then 2 extra media servers.

The 2 media servers are database servers also and have there own disk 
storage. I am running an L700 with 5 tape drives LTO2 utilizxing SSO. 
The media server 2 ( the one in question now showing this error ) has 
been working fine for 2 months. There are no other errors for clients or

the other media servers.

All of this is on solaris 9

I have the following tuneable paramets in /etc/system

set msgssys:msginfo_msgmap=512
set msgssys:msginfo_msgmax=8192
set msgssys:msginfo_msgmnb=65536
set msgssys:msginfo_msgssz=16
set msgssys:msginfo_msgtql=512
set msgssys:msginfo_msgseg=8192

set semsys:seminfo_semmap=64
set semsys:seminfo_semmni=1024
set semsys:seminfo_semmns=1024
set semsys:seminfo_semmnu=1024
set semsys:seminfo_semmsl=300
set semsys:seminfo_semopm=32
set semsys:seminfo_semume=64

*set shmsys:shminfo_shmmax=16777216
*set shmsys:shminfo_shmin=1
set shmsys:shminfo_shmmni=220
set shmsys:shminfo_shmseg=100

Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu

More information about the Veritas-bu mailing list