Again: Backup Jobs fail since NW6.5SP3/4 with AS9.01SP1: E6959 and E1145

Hello.

The full details are in a thread same subject, 06 Nov 2005 12:18:59 GMT, without
solutions howto track down the issue.

So please let me ask in a new thread:

The problem is fact for two identical Proliant ML 350 G4 3,4GHz, 1Gig RAM servers
and started with applying NW6.5SP3, and 100% persists up to now

Using the TAPESVR option do do testbackups with lots of sessions per tape is
running for hours without any problem. That's why I could imagine that could be a
problem *retrieving* the data, not *writing* to tape (wrong error message...)

unloading CIFS was a hint in some other thread, didn't help at all.

- Are there certain Arcserve (tapesvr load switchese.g.) or NetWare tools
available to track down this issue?

regards, Rudi

Have you opened an incident with CA? With the Arcserve product, they often
have patches for long-standing issues that you can't get from their support
site.

Jeff

"Rudolf Thilo" <spam...@nurfuerspam.de> wrote in message
news:77ief.2510$Ay4...@prv-forum2.provo.novell.com...

Jeffrey D Sessler wrote:

Not yet for this issue, due to poor results (reaction time, no solution) in the
past with other issues.

Also nice to read this *NOT* for the first time. Amazing what they think how to
service their paying customers!

But perhaps I may repeat the main question:

How to do debugging on my on AS side and NetWare side? Any TIDs someone could
point me towards, please?

Thanks, Rudi.

I've opened an issue with ARCserve on this very problem (for me, ProLiant
ML370 G4 running NetWare 6.5 SP4 and Sony External AIT-2 drives). Am having
the exact same problem.

I have noticed that if I was running a previous version of NetWare 6.5 (such
as SP1.1 or SP2 and THEN upgraded to SP4 instead of installing with the SP4
Overlay CD) I did not have this problem.

I do have one server running with SP4 installed new and I think it is
working because PSP7.30A is installed instead of PSP7.40A.

So far, CA has been WORTHLESS in helping me resolve this problem. I've gone
thru two techs and they've simply had me repeat the processes I've done on
my own.

I have even tried ARCserve 11.1 with the same results.

Once I backrev the PSP to 7.30A I will let you know the results.

I am also going to run a test via SBACKUP since the ARCserve Tape Test came
out clean.

>>> Rudolf Thilo<spam...@nurfuerspam.de> 11/15/2005 12:49:27 PM >>>

there are a couple of switches that can be applied to modules in the
ASCONFIG.INI file - but I've already tried them and they've failed.

>>> Rudolf Thilo<spam...@nurfuerspam.de> 11/15/2005 1:45:39 AM >>>

You are not going to like this - but we have a serious problem.

HP at some point switched out the Adaptec chipset (used by Compaq engineers)
in favor of the LSI chipset (used by HP for many years). The problem is
that my server (HP ProLiant ML370 G4) and your server (HP ProLiant ML350 G4)
both use the LSI SCSI chipset integrated on the HP mainboard.

It's a piece of junk.

It will fail even when running SBCON instead of ARCserve.

CA tech support does not recognize the LSI controller as a certified device.
As such, they refuse to support ARCserve in that configuration. They
suggest we add in a certified SCSI controller. As of date, ARCserve 9 and
11.1 support the following HP-branded SCSI controllers:

none

As of date, ARCserve 9 and 11.1 support the following Compaq-branded SCSI
controllers:

32-bit Dual Channel Fast-Wide SCSI-2/E

64-bit/66MHz Dual Channel Wide-Ultra 3 SCSI ($360 list - 284688-B21)

http://h18004.www1.hp.com/products/servers/proliantstorage/adapters/66mhz-du
al/index.html

Smart Array 5i (integrated into some models only)

It appears to work with NetWare 6.5 SP3 using LSIMPTNW.HAM 3.08 (HP ProLiant
Support Pack 7.30a).

It does not work with NetWare 6.5 SP4 using LSIMPTNW.HAM 3.09 (HP ProLiant
Support Pack 7.40a) or 3.08

I don't know if this is because I built up NetWare 6.5 using the broken SP4
overlay CD or not.

Interesting -- for 'regular' SCSI controllers I've not had problems
with either LSI or Adaptec chipsets.

For RAID controllers, LSI chipsets have been a better choice for many
folks.

--
Barry Schnur
Novell Support Connection Volunteer Sysop

well, even SBCON failed when running a backup on the HP ProLiant ML370 G4
server using the integrated LSI SCSI controller connected to a external Sony
AIT-2 (AITe130) tape drive - gave me errors about not being able to write
the source files (TSR fffeffce errors) to tape.

However, I am using the bad SP4 Overlay CD and will attempt to deploy SP4a
tonight to see if it gets any better. But I am looking at purchasing dozens
of new controllers or give up ever going to SP4 on my servers and staying
with SP3.

I'd also like to point out that HP does have a tendancy to ruin stuff. They
can take a good chipset and screw it up when they integrate it onto their
motherboards.

>>> Barry Schnur<BSc...@cox.net> 11/15/2005 5:24:48 PM >>>

For what it's worth, I've frequently used tekram controllers (which
have LSI chipsets) to handle DAT drives and these days AIT2 and LTO1
drives.

Is it possible that there are BIOS setting in the card that can be altered?
For example, maybe the card is running the SCSI bus at too high a speed for
the length and quality of the cable and you need to slow the transfer rate
down?

best,
jeff

"Dave P." <novel...@yahoo.com> wrote in message
news:qbLef.253$Pe3...@prv-forum2.provo.novell.com...

Have you already tried the LSIMPTNW.HAM 3.99.05, which is part of Sp4a.
I am running this on an IBM Xseries 225, with an integrated LSI_53C1030
SCSI chip and a DLT tape attached to this chip. Before Sp4a I was
running LSIMPTNW.HAM 3.08.00 (from Sp3) and LSIMPTNW.HAM 3.06.00 both
without problems.

W. Prindl

Dave P. wrote:

> mhz-du al/index.html

> problem retrieving the data, not writing to tape (wrong error

not using the integrated LSI SCSI controller on the ML370 like I am using it
is not.

btw, HP says that even that LSI SCSI controller is not compatible with their
own LTO tape drives.

>>> Jeffrey D Sessler<je...@scrippscollege.edu> 11/16/2005 4:50:27 PM >>>

3.08 is keeping me going as it is on one server running NW65 SP3.

currently, I am running 3.09.02 (7/28/2005) from HP PSP 7.40a with no luck.

I also tried 3.99.05 (7/5/2005) from SP4/4a with no luck on a different
server.

I am going for additional hardware at this point.

>>> W. Prindl<05...@pamtwbnospam.at> 11/17/2005 1:55:42 PM >>>

> Compatibility is squat at that point - it's no longer an LSI device, it's an
> HP controller now.
>
OK -- I hear you -- I've not messed much with HP servers -- more with
Compaq servers -- which, while expensive WORKED.

that may be fine and dandy for add-on cards, but I need to repeat that we
are talking *INTEGRATED* LSI SCSI controllers - which means HP has had their
hands all over the LSI BIOS firmware.

>>> Barry Schnur<BSc...@cox.net> 11/16/2005 11:56:26 AM >>>

Dave P. wrote:

Which ones do you know about to be useful?

What do you mean they 'failed'? Didn't report anything useful or what did fail?

Regards, Rudi.

Dave P. wrote:

That makes me feel much better :-//

That's different from 'my' servers: They were installed with 6.5.2 overlay and
later on upgraded to sp3 then sp4, the other one IIRC directly to SP4.

The Proliant Support Pack 7.30a right now tells as it's date the 29 Apr 2005. So
both of them should have been installed with 7.10a (as 7.20a is dated later then
they were installed). At least *I* didn't apply any PSP's later on, but that
might be a start.

A great thing would be a comaration chart NW-SP <-> PSP driver's version...

This sounds SOOO familiar to me <scnr>

Yes, there are several threads in the newsgroups reporting the same issue with
AS11.1 as well.

.. so I will wait with applying any PSPs until you report your results.

So was the AS tape server tape test for hours for both of the trouble servers...

Regards, Rudi.

Dave P. wrote:

Unbelievable!!

Where do you have that information from? That should (?could?) be sufficent to
complain a missing implied warrantie of fitness: They sold it together as a
server system.

That's the 'synergy' effects of the hp + compaq fusion :-((

Regards, Rudi.