Can you tell me what tools you are talking about ? I'm not very experienced in all that DLL-stuff.
Thanks. Wouter. -----Oorspronkelijk bericht----- Van: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]Namens Tab Trepagnier Verzonden: vrijdag 25 januari 2002 2:06 Aan: [EMAIL PROTECTED] Onderwerp: Re: Windows TSM-Client Crash Wouter, I have seen the Windows service crash from two different reasons: 1) corrupted file on the disk; use CHKDSK to fix any corrupted files. 2) wrong version of certain DLLs included with the client; check the DLLs in the client directory. There are tools that display the version of the DLL loaded into memory. If the DLL in memory is older than the one in the client directory, that might cause a crash. As for your tape activity, I see the same behavior on my HP DLTs during DB backups. Even though my RS/6000 is sending data (according to topas) at 8 MB/s, the HP writes for a few seconds, then idles for a few seconds. I think the HP drives have 16 MB memory and don't actually perform a write until the buffer is filled. Hope this helps. Tab Trepagnier TSM Administrator Laitram Corporation Wouter V <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/22/2002 01:49:42 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Windows TSM-Client Crash Hello, We just introduced TSM in our environment. We are now backuping up 1 unix server and 12 Windows clients (Windows 2000 Server, SP2). We are using TSM Server 4.2.1.9 on a Unix server (S7A) and use TSM Client 4.2.1.20 on all the windows clients. We use a 3583 Ultrium Tape Lib, with 2 drives. Problem 1 : Unfortunately we have problems with the TSM Client on 3 of our Windows machines, - 1 machine fails to start the TSM Scheduler service during boottime, if we start it manually, it runs, but crashes several times during backup. (we do an "autorestart", if the service fails) - the other 2 machines always start the backup, but the client (tsm scheduler) crashes after a certain time, are amount of files. There is not really a fixed point where the service crashes. If backup is launched from the scheduler, dsmsvc.exe crashes, if we start the backup manually with dsmc incr, dmsc.exe crashes. Does anybody know what the fastest way is to solve this ? Problem 2 : - During migration from disk to tape, I can see (on the display) that the 2 tapedrives are not constantly writing data to tape, it's always writing for a short period of time, waiting for a longer period, writing, and so on ... Is this normal ? Is there anything I can check or do ? Shouldn't the tapestreamers really stream data from disk ? I know our situation is not ideal (the whole diskpool is on 1 disk), but it is on another scsi-bus than the tapestreamers. Thank you very much in advance (sorry for all my questions, but this is just my second TSM installation), Wouter Verschaeve, Unix System Engineer.
