Omniback v3.5 - Shared Memory Problem

[Alex Ring]

Hi Guys

Im trying to test an eval copy of Omniback v3.5. Heres a desc of my setup.

Cell Server runs on Win2k SP1 Machine.

I have a Sun StorEdge L20 Tape Library connected to a Sun E420R running Solaris 2.7. The E420R has the client s/w and agents (DA & MA) installed. Eveything seems to be running and talking to each other fine.

I have configured the Backup device/drives & media, and have tried to run a very small test backup. Unfortunately, i get the following errors reported ;

Any ideas ??

[Normal] From: BMA@masptest.masp.morse.com "DLT1" Time: 12/04/2001 15:38:10
STARTING Medium Agent "DLT1"

[Critical] From: BMA-NET@masptest.masp.morse.com "DLT1" Time: 12/04/2001 15:38:10
Can not allocate shared memory pool (IPC Can not Create Shared Memory Segment
System error: [22] Invalid argument
) => aborting

[Critical] From: BMA@masptest.masp.morse.com "DLT1" Time: 12/04/2001 15:38:10
[90:24] Unexpected close reading NETIO message (Details unknown.) => aborting

[Normal] From: BMA@masptest.masp.morse.com "DLT1" Time: 12/04/2001 15:38:10
ABORTED Medium Agent "DLT1"

[Critical] From: BSM@maspnts2.masp.morse.com "" Time: 12/04/2001 15:39:26
None of the Disk Agents completed successfully.
Session has failed.

[Normal] From: BSM@maspnts2.masp.morse.com "" Time: 12/04/2001 15:39:26

[Jim Moffitt_1]

Looks like a kernel problem. You might have to rebuild the kernel and increase the shared memory allocation variable. In HP-UX, I think it is shmmax. This should help, but I'm not sure about Sun

[Andrew Byrne]

Does this happen if you do a test backup to a local Win2000 drive?

Just trying to rule out whether this is a Media or Disk agent problem.

Did you use a manual install or HP-UX installation server method to install the client? You could patch the installation server and push out the upgrade to the client which will probably fix the problem.

You can contact me through Paul Tacq of Morse Professional Services if you need further help.

Andrew Byrne

[Ravi_8]

Hi,
in /etc/system file (in solaris) increase the
number of shmmax,shmmni and shmseg parameters.
and reboot the system.this may solve ur problem

[Alex Ring]

Ive got past the shared memory issue by adding the following lines to /etc/system

set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmseg=20
set shmsys:shminfo_shmmni=100

Unfortunately, another issue has now arisen, which i have posted in a new message.