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
-----Original Message-----
From: Bill Smoldt <smoldt AT storsol DOT com>
To: <ADSM-L AT VM.MARIST DOT EDU>
Date: martedì 13 ottobre 1998 13.20
Subject: Re: NT 4.0: ADSM Client problems
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
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf
Of Erwin Pfeifer
Sent: Tuesday, October 13, 1998 2:35 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: NT 4.0: ADSM Client problems
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
|