Hi Kurt.
Sorry I don't have anything further than maybe check if there has been any
ADSMSCSI and ADPU160M errors in the system event log, say the last hour
before the server dies. (Not necessarily right before crash.) Also check if
there are any newer Ultrium Device Drivers from IBM.
In my previous experience with this, I always had som of these errors also.
Another option - tedious and perhaps difficult (haven't tried it myself),
would be to contact Tivoli (or ADSM.ORG ;-)) for help on tracing the TSM
server, to see if there are any special actions taking place, causing the
reboot. I'm thinking it has to do with something in this direction --> Tsm
Server - TSM Device Driver - Adaptec Driver - Ultrium Driver. If you can do
a trace, you will perhaps be able to se what the last actions are before
serverdown.
Rgds.
Geirr G. Halvorsen
-----Original Message-----
From: Kurt Beyers [mailto:kurt.beyers AT PANDORA DOT BE]
Sent: 18. september 2002 18:31
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM 5.1.1 Win2000 server reboot
Hi,
Sorry I couldn't reply any earlier.
I've got some additional info. The server was already at the client since
august. The Adaptec SCSI controller and library were installed in september.
The server was already rebooting several times a day from the beginning,
I've found this in the event log.
So there is definitely a hardware problem causing the reboots and TSM or the
Adaptec SCSI controller can't be the cause. I'll check the Adaptec driver
version tomorrow.
Thanks,
Kurt
----- Original Message -----
From: "Halvorsen Geirr Gulbrand" <gehal AT WMDATA DOT COM>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Wednesday, September 18, 2002 3:10 PM
Subject: Re: TSM 5.1.1 Win2000 server reboot
> Hi Bill,
> I would very much like to know version data for the Adpatec driver you
are
> using.
>
> Rgds
> Geirr G. Halvorsen
>
>
> -----Original Message-----
> From: Bill Boyer [mailto:bill.boyer AT VERIZON DOT NET]
> Sent: 18. september 2002 15:03
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: TSM 5.1.1 Win2000 server reboot
>
>
> Adaptec has an updated driver on their site that works great. The default
> driver delivered with Win2k has problems with LTO tape. I haven't seen
> reboot problems, but severe throughput issues to where I would only get
> 1-2GB/hour throughput on the tape drives. Updating to the Adaptec drivers
> (even though the Tivoli support pages say to use the IBM drivers) has
gotten
> me to 1+GB/Minute throughput.
>
> Bill Boyer
> DSS, Inc.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Halvorsen Geirr Gulbrand
> Sent: Wednesday, September 18, 2002 4:37 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: TSM 5.1.1 Win2000 server reboot
>
>
> Hi Kurt,
> I have had a similar problem (maybe the same) with TSM v. 4.2.2 on an IBM
> x342, with adaptec 39160 SCSI controller, and LTO library IBM 3584.
> In my case it rebooted 1-2 times pr. day. I bugged me alot, but seemingly
it
> was a problem with the SCSI Controller Driver on w2k.
> To fix this I made a database backup of TSM, and installed w2k from
scratch,
> then installed the correct driver for the adapter-card (found on
> ftp://ftp.software.ibm.com/storage/devdrvr/Win2000/adaptec_lun.zip),
> reinstalled TSM, and restored the TSM database. I haven't had the problems
> after that. Now, I don't think reinstalling OS should be necessary, but I
> believe the problem is something related to registry settings for device
> adpu160m (the adaptec controller), and when updating this driver, some
> settings still are in registry or some files exist that are not replaced
> when updating the driver.
> Another problem is that because the server goes down unexpectedly, TSM is
> likely to have a corrupted database, and when you get the server to run
OK,
> you should do an AUDITDB on your tsm. (Oh my, this is slow...)
> The other option is to drop your database, and just do the full backup all
> over again.
>
> Hope this helps...
>
> Rgds.
> Geirr G. Halvorsen
>
>
> -----Original Message-----
> From: Kurt Beyers [mailto:kurt.beyers AT PANDORA DOT BE]
> Sent: 17. september 2002 22:56
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: TSM 5.1.1 Win2000 server reboot
>
>
> Hi,
>
> I've just installed TSM 5.1.1 on a Windows 2000 Advanced Server (SP2)
>
> The hardware of the TSM server is:
>
> IBM Netfinity X232 8668 (Pentium 4, 1133 MHz)
> 512 MB RAM
> IBM ServeRAID-4LX Ultra 160 controller (SCSI controller of internal disks)
> IBM LTO library connected via an Adaptec SCSI controller.
>
> During the setup of TSM and the full backup of a number of clients, the
> server has rebooted 6 times. There is no Dr. Watson or what so ever. In
the
> TSM activity log there are also no errors written. You just retrieve the
> latest commands before the shutdown and afterwards the normal startup
> messages of TSM.
>
> Only in the event log, there is an event stating 'An unexpected system
> shutdown has occured'. No other errors or warnings in the event log.
>
> Has anybody else experienced a similar situation and how did you solve it?
>
> Any input is more then welcome. Thanks,
>
> Kurt
>
>
|
