Re: TSM 3.7.1 Nt Clients???
Clients were upgraded from ADSM 126.96.36.199 with no changes made to policies,
incl/excl etc. They ran fine no errors very dependable night in and night
out. Now when running with TSM 3.7.1 the backup dies, the scheduler
dies..... Not good. I didn't find any errors in the dsmsched or error log
but tried a few things based on Gary's comments. Sure seems like it's
related to files that are in use.
Guess I could try running a trace. Haven't played with that much. Anyone
have hints on what I want to trace? Would be nice to have some good data to
call into the support center.
Lockheed Martin EIS
From: James Thompson [mailto:mezron AT HOTMAIL DOT COM]
Sent: Friday, March 03, 2000 3:29 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM 3.7.1 Nt Clients???
Correct me if I am wrong, but my guess is that *sm uses the
call to backup(copy) a 'static' file as it would a file that
is 'in use'.
Have you tried using explorer to copy that same file that
*sm has trouble
If the file is 'in use' then it is up to the operating
system to gracefully
handle the attempted access and return to the calling
process that access is
denied. If the operating system crashes because of this
then it isn't really the fault of *sm. Especially since you
are telling *sm
to try and back that file up.
>From: "Magura, Curtis" <curtis.magura AT LMCO DOT COM>
>Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: TSM 3.7.1 Nt Clients???
>Date: Fri, 3 Mar 2000 12:51:10 -0500
> Do you have a PMR number for this? Does look to be a
problem. I played
>around with a couple of directories and sure enough
everytime I backup up a
>directory that has files in use the session crashes. Point
to a dir that I
>know isn't in use and the backup runs fine.
>That part that is a little strange is that 3.7.1 is working
on other NT
>boxes without any problems. The two that I'm having trouble
>Oracle and SQL. We are using the agents to backup up the
database. At this
>point the DBA's do their magic and we rely on *SM to pick
up the output of
>the backups that the DBA's run.
>Enterprise Information Systems
> -----Original Message-----
> From: Gary Ison
[mailto:Gary.Ison AT MAIL.STATE.KY DOT US]
> Sent: Thursday, March 02, 2000 8:44 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: TSM 3.7.1 Nt
> Look in the error and scheduler logs for
>Some of my clients were getting messages with an error code
of 933 and
>termination of the backup process. I have this on an ETR
with IBM, but
>haven't had a response yet. I got around the problem by
>failing file from backup (it was usually ntuser.dat.log and
> Gary L. Ison
> 101 Cold Harbor Drive
> Frankfort, Ky. 40601
> Phone: (502) 564-8724
> Fax: (502) 564-6856
Get Your Private, Free Email at http://www.hotmail.com