[no subject]
2015-10-04 17:52:21
Erwin,
If you
put 'quiet' in your options file I think you'll get what you're looking for
- only summary and error information go into the
dsmsched.log.
dsmsched.log.
Bill
Bill,
thanks for your help! I think I have
resolved the problem with the service! Since we run the ADSM-Client without
a password, I let this parameter blank! It seems that this was the problem.
After given him a password, the service started.
Well, trimming the log file this way is not
exactly what I'm looking for: We have an Operator who checks if the BACKUP
is doing well. He needs only the final statistics: how many files
transfered, what are the files where the backup failed; he don't need other
details! Is it possible to control the output that way?
erwin
Erwin,
You can trim the log file with the option
schedlogretention x
where x is a number of days prior to today. I usually put
in an errorlogretention at the same time to make certain the error log
doesn't grow unbounded, also.
I've never had trouble removing the schedule with dsmcutil.
Try a dsmcutil list command to ensure that it really got removed.
If not, the remove command should look like:
dsmcutil remove /name:"ADSM Scheduler"
with whatever you named the service between the
"".
Bill Smoldt
SSSI
Hello,
I have two problems:
1) I started the ADSM-scheduler (Client Version
3.1) on WinNT 4.0 as a service. Then I removed it with
the command 'dsmcutil rem' and now I'm not able to start
it again.
2) The Log-File is a monster, especialy after a full: Is there
a possibility to control the output of the Log-File (reduce it to
the essentials!)?
Is there anyone out there who can offer advice on
this!
Thanks in advance
Erwin
------=_NextPart_000_001D_01BDF74A.EB465EA0--
======================================================================= |
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
|
|
|