Robert,

Ah, sounds very familiar.

You didn't identify your configuration, so let me guess.
- NBU 3.4.x (without Jumbo Patch 3 maybe?)
- Windows (NT or 2000)

If this is right, this is a well known problem.  Jumbo Patch 3 was supposed
to "mask" the problem, but we found that it did not.  Version 4.5 is a lot
more stable in that respect.  The issue is "Reserve Release", look it up on
the support web site for some background reading.  However, the "fixes" and
logic are just plain wrong.  A little corporate damage control is my
opinion!

We also had issues with Gigabit Ethernet NIC's and a non-Compaq Library in a
totally Compaq SAN, but that's another story.  We had to install a "back
channel" to allow the netbackup servers to communicate directly (avoiding
the very busy network connection).


David Anderson
ScrippsHealth Information Services
anderson.david AT scrippshealth DOT org


-----Original message --------
Message: 3
Date: Tue, 17 Sep 2002 13:41:35 -0500
From: Robert Johannes <robert_johannes AT udlp DOT com>
Organization: United Defense
To: nb <veritas-bu AT mailman.eng.auburn DOT edu>
Subject: [Veritas-bu] S.S.O with SDLT

Folks,
I've two servers I would like to enable SSO on.  I've the licenses
installed;  I've tried enabling SSO before, and ran into problems
because it seemed that if one server was using a drive, the other SSO
server did not seem aware that a drive was already being used, and so it
would down that particular drive that was being used by the other
server; I know it sounds like a scsi reserve_release issue, but I was
convinced that I had that setup corretly.

Can someone send me what their working st.conf file looks like, if you
are using SSO and SDLT drives over fiber-bridges?  Also, what other
quirks do I need to look at to make sure SSO can work, both on the
server and media server ends?

thanks
robert