Look at the client parm:
SCHEDLOGRETENTION nn,D
This goes in the dsm.opt file on the client.
There are several choices, but if you specify
SCHEDLOGRETENTION 10,D
The log will prune itself every time the client does a backup, and keep only
the most recent 10 days of log data.
Now your first backup will be the largest, because it backs up everything,
and after that, 10 days worth of incremental data should never get very
large.
For most clients this handles the issue adequately.
************************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu
"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
************************************************************************
> -----Original Message-----
> From: Joel Cooper [SMTP:jocooper AT DTTUS DOT COM]
> Sent: Tuesday, May 11, 1999 11:25 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> 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
|
