Netware 5.0 w/sp6a. ArcserveIT 6.6 For NetWare w/Tape Changer Library Option. We been having problems with failing DAT drives for the last several years. The drive now in use is a external 12/24GB Dat 8 Casette Autoloader. The day the problem began the backups were running without problem, I unloaded the software to put a tape in for my G-F-S monthly backup. Arcserve loaded and about half way through died. The errors from Arcserve indicate problems communicating with the SCSI device. I thought I had hit the power button on the drive which when that happens mandates a re-boot otherwise NetWare can't see the device. So I did. During POST, the drive WAS SEEN. When NetWare loaded, I tried typing LIST DEVICES, and I did not see any unbound storage devices. Compaq & HP suggested copying the Nwaspi.cdm file from the NW5 Sp6a folder. I did, nothing still. Is it possible for the drive to be seen at POST, but not later on by NetWare?? I am in a spot here since NetWare 5 is not supported by Novell & Arcserve provides limited support with ArcserveIT 6.6? Help would be very much appreciated. If replacing the drive solves the problem, great. I just want to stress NO MAJOR CONFIG changes have been done to either NW5 or Arcserve in a very very long time.

Hi, First let me say you did an excellent job in describing the problem. Thank you for that, since it saves me consulting a phychic, or at least my magic 8-ball. I'd also like to say whenever I've found a problem in or with Novell, there has always been a fix. Sometimes instant, sometimes with a LOT of work, but always a fix. I haven't been this lucky with Arcserve, but I'm willing to try if you are. As you mentioned you've changed out tape drives before, I am assuming this is not a new issue. I seriously doubt changing the drive will help in the long run. As it is MHO, I've divided what I see as 3 major zones of investigation. Software: I would fully update any and all support packs for each product. Although it might appear that you have, I like to throw this in. Constantly. So much I hate me for it. Also check the log files to see if there are any suspicious activities written there. Though it may not say "Hey man, this is your problem!" It could provide much needed clues in tracking down the time waster. Hardware: Though I'm not familiar with your hardware, you might check, then recheck, all terminations to the SCSI devices. Never trust auto-termination. Verify everything. After that, I would look seriously at testing the SCSI cable connection, ports, and drive placement. Insure all qualified hardware specific drivers are used. Example: A Dell PowerServer has particular SCSI drivers. After a service pack application, the Novell issues drivers are installed. The SCSI fails, and fails abnormally. By reinstalling Dell's drivers (in say C:\nwserver), the SCSI works again. Config: After all that, the only thing left would be the configuration. Verify all is set correctly. As this has worked before, I doubt the problem could be here. But then, if the world was perfect, niether of us would be posting on a forum. As I've seen this before without Arcserve, I would find the SCSI setup suspect. With either device, cables, or termination, I'd eyeball that very carefully. HTH, -J

ArcServe has a utility called scsiscan in the ulitlty folder use it to detect the drive. When halting loading operation ArcServe will give you an error message, please post that.