Joel

I have seen similar problem in Unix clients.  The first time backup is run
the dsmsched.log can be very large specially if there are high number of
files to be backedup.  One way to stop the dsmsched.log growing is to add
quiet option in the dsm.opt file.

Sholeh




jocooper AT dttus DOT com on 11-May-1999 04:24 PM



Please respond to ADSM-L AT vm.marist DOT edu

To:   ADSM-L
cc:    (bcc: Sholeh Azimfar-1/CIS/PHRD/SB_PLC)
Subject:  Client log question




Hello:
I've just installed my first 17 clients (v3.1.0.6 on WinNT 4.0sp4 to AIX
server).
I'm using the scheduler service.

I have been looking at some of my clients with large #s of files. Not
necessarily size, but # of files.

I am trying to understand logging.

If I am looking correctly, errors are in dsmerror.log (baclient dir), and
the
results of scheduled events are in dsmsched.log. The documentation says the
default of the service is EVENTLOGGING:YES.
I had a client I added last night that only got through 400,000 files (only
8GB)
and the dsmsched.log is 45MB.

How are you all with similar situations handling this? Should I
EVENTLOGGING:NO?
 If I don't, or for that matter, even if I do, how do I prune or control
the
size of this file? I don't want it to eventually become so large it wastes
space
or is not managable to peruse.

Thanks again for all of the help of this list,

Joel Cooper
Site Tech Server Team
Deloitte & Touche LLP
jocooper AT dttus DOT com