Hi Dennis

I do exactly the same on Version 3.1.0.3 on NT clients
(not upgraded from V2 however) and it works fine.
I don't even use the schedlogname parameter, because
 the path you define is the default if you installed ADSM
 in c:\ADSM iso the standard c:\win32apps\ibm\adsm
 (which I guess you did as I did).
The complete log is kept with timestamps and errors
 and summary in c:\adsm\baclient\dsmsched.log
 for 10 days.
Perhaps one thing to check is ; did you stop/start the
 scheduler service after(!) you ma      de the changes to your
 dsm.opt file ? Any change to dsm.opt (even a change
 in excl or incl) is not taken into account for the schedule if
 you don't do this. I would think it should make more sense
 if the scheduler-service should read the dsm.opt when he is
 contacted (prompted) or is contacting (polling) the server
 to start the schedule, but that is not the way it is working now.


---------------------------------------------------------------
Busschots Luc
Busschots Luc
B.I.C.S.
Straatsburgstraat 3 rue de Strasbourg
1130  Brussels
Belgium

E-mail :Luc.Busschots AT Cerix DOT com
Tel : Int-32-2-702.36.12 *******  Fax : Int-32-2-702.36.00

> -----Original Message-----
> From: Dennis Schaffer [SMTP:Dennis.Schaffer AT MUTUALOFOMAHA DOT COM]
> Sent: jeudi 25 juin 1998 17:31
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      ADSM/NT V3 Client Schedule Log Processing
>
> We recently upgraded one ADSM Win NT client from V2.1.0.6 to V3.1.0.3.
>
> In our DSM.OPT file, we include the following statements to direct the
> schedule log output to a particular location and to keep 10 days of
> scheduled backup log output:
>
> SCHEDLOGNAME C:\ADSM\BACLIENT\DSMSCHED.LOG
> SCHEDLOGR 10
> VERBOSE (we added this in V3 as a forum suggestion when we initially
> got
> only summary output)
>
> With the V3 client, we now get two versions of schedule log files and
> both
> versions only contain data for the most recent scheduled backup:
>
> DSMSCHED.LOG
> -  this log contains the normal kind of detailed, time-stamped output
> that
>    was produced by the V2 client but only contains the details from
> the
>    most recent backup
>
> DSMCSCH.LOG
> -  this log contains un-time-stamped log records showing the flow from
>    drive to drive, numbers of files backed up and any errors
> encountered.
>
> Does anyone know how I can coerce the V3 client to retain 10 days of
> log
>    data?
>
> Thanks in advance for your assistance,
>
> Dennis Schaffer
> Mutual of Omaha