Re: Backup Exec 9.2 Netware - Server locks up
emerson...@charger.se
HP/Compaq......
1. Make sure nwtape isn't loaded, safe way is to simply rename
c:\nwserver\drivers\nwtape.cdm to anything else.
2. I just spent a couple of days trying to get a new LTO4 drive
working with BackupExec 9.2 over SAS. This isn't working, no device.
Also been trying to get a responce from Symantec, but none given.
Issue is; LTO4 driver is NOT supplied through BE9.2 and we could NOT
get it to work.
3. I've been in contact with LSI regarding their driver LSIMPTNW.HAM.
Same "driver/drivername" is used by them for both the SCSI and for the
SAS controllers. BUT, according to LSI, you can NOT use both types in
a Netware server because of this.
The revision of LSIMPTNW.ham that supports SAS is NOT supported for
SCSI and off course the reverse is true.
If you check the .ddi file, there's stated which controllers are
supported by the .ham driver in the names like xx1030 ( scsi)etc,,etc
In the later SAS version, xx1030 is remarked OUT and, again confirmed
by LSI as NOT supported/working config.
Don't know if this applies to HP, but theres a chance that HP like
Dell and other do use LSI chipsets for their SCSI,SAS and Raid.
So, my guess,
you might get around this if youre NOT using scsi and sas over LSI at
the same time and making sure that NWTAPE isn't loaded.
Then you can start backupexec just to find that the tapedrive isn't
found by BE......sorry to say....
On Thu, 22 Oct 2009 00:36:02 GMT, cadd <ca...@no-mx.forums.novell.com>
wrote:
>
>I have a brand new HP ProLiant DL360 G6 Quad-Core Xeon 7300 series E5530
>2.4 GHz.
>
>There is an HP Smart Array P212/Zero Memory Controller in the server
>and a HP StorageWorks Ultrium 1760 - tape drive - LTO 4 Ultrium - SAS
>attached.
>
>I have Netware 6.5 SP6 installed.
>
>Backup Exec 9.2 is installed.
>
>The server has been running for a week in a test environment. I have
>been waiting on a SAS cable and received the cable today.
>
>When I run BESTART.NCF it starts loading but stops at a point that is
>says it is searchling for update. At this point the server either locks
>up hard, or I see a deactivation of the controller and then a hard
>lockup.
>
>After a reboot, the server reports it experienced a failed controller
>during the boot up status screens.
>
>The same driver is loaded twice. Once for the hard drive RAID array
>and once for the P212 tape controller. Each LOAD statement has a
>different slot number designated. I am writing this from home and don't
>recall the driver name. I think it is hpqciss, but I'm not sure.
>
>Anyone have an idea as to why the server locks up ?
>
>Are there any ways to test the tape drive outside of Backup Exec ?
emerson...@charger.se
On Thu, 22 Oct 2009 13:36:02 GMT, cadd <ca...@no-mx.forums.novell.com>
wrote:
>
>I'll try removing NWTAPE.NLM.
>
>The HAM driver is HPQCISS.HAM.
>
>It is loaded twice. Once for the RAID drive array's controller and
>once for the tape drive controller.
emerson...@charger.se
controller since it manages to deactivate your drives.
But,, still I do think that the LTO4 won't work with BE anyway,
as stated I gave it a couple of day's testing and simply couldn't get
BE to pick it up. But,, if you do get it working,, I'd be happy to get
that info here....
On Thu, 22 Oct 2009 16:06:02 GMT, cadd <ca...@no-mx.forums.novell.com>
wrote:
>
>I'm not sure about the LSI OEM...
>
>When the server locks up, if I wait long enough, usually 10 minutes
>after it lockes up on the "Checking environmental settings", the BESTART
>load fails and unloads itself.
>
>I see these errors on the logger screen:
>
>HPQCISS-1.16-0
>
>HPQCISS: The controller in slot 2 has been failed by the driver and
>requires corrective action.
>
>At this point the pools have been deactivated, the volumes dismounted,
>and I have all kinds of NSS errors after that.