Re: TSM Client 5.2.0.0 on W2k

2003-08-26 Thread Janusz Wiszniowski
: Re: TSM Client 5.2.0.0 on W2k Manager [EMAIL PROTECTED] T.EDU

SV: TSM Client 5.2.0.0 on W2k

2003-08-26 Thread Christian Svensson
and the backup should work fine now. Best Regard Christian Svensson -Ursprungligt meddelande- Fran: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Janusz Wiszniowski Skickat: den 26 augusti 2003 09:20 Till: [EMAIL PROTECTED] mne: Re: TSM Client 5.2.0.0 on W2k I used PSKILL utility

Re: SV: TSM Client 5.2.0.0 on W2k

2003-08-26 Thread Janusz Wiszniowski
: [EMAIL PROTECTED] CRISTIE.SE DW: Wysane przez: Temat: SV: TSM Client 5.2.0.0 on W2k ADSM: Dist Stor Manager

SV: SV: TSM Client 5.2.0.0 on W2k

2003-08-26 Thread Christian Svensson
PROTECTED] mne: Re: SV: TSM Client 5.2.0.0 on W2k Hi! Thanks for info. The problem appears (I think) on different files. As I wrote, once it hangs on C:\WINNT\Temp\somefile.tmp, other time on some Outlook files, etc. What can be the reason ? Win 2000 has McCafee antivirus software installed

Re: SV: SV: TSM Client 5.2.0.0 on W2k

2003-08-26 Thread Janusz Wiszniowski
] CRISTIE.SE DW: Wysane przez: Temat: SV: SV: TSM Client 5.2.0.0 on W2k ADSM: Dist Stor Manager

SV: SV: SV: TSM Client 5.2.0.0 on W2k

2003-08-26 Thread Christian Svensson
we have. /Chris -Ursprungligt meddelande- Fran: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Janusz Wiszniowski Skickat: den 26 augusti 2003 10:24 Till: [EMAIL PROTECTED] mne: Re: SV: SV: TSM Client 5.2.0.0 on W2k I didn't try to perform backup without OFM (can I make full

TSM Client 5.2.0.0 on W2k

2003-08-25 Thread Janusz Wiszniowski
Hi all ! I have problem with TSM 5.2.0.0 Client on Win2000 Server. An Open File Support module is installed. The SNAPSHOTCACHELOCATION is set correctly. When performing incremental backup of filesystem,the operation sometimes hangs. Once it hangs on C:\WINNT\Temp\somefile, other time on some

Re: TSM Client 5.2.0.0 on W2k

2003-08-25 Thread Kamp, Bruce
Have you tried using the resource kit utility called PSKILL? I use it all the time on servers when the scheduler is stuck in a starting state All you need is the process number. Not a solution to the real problem but it save you a reboot! -- Bruce Kamp