Schedule Event Status Misleading

mbotticelli

ADSM.ORG Member
Joined
Dec 13, 2002
Messages
46
Reaction score
0
Points
0
PREDATAR Control23

We are a new installation of TSM 5.1 running on AIX and are backing up 90 clients of Unix/NT with various TDP for databases - Oracle, Sybase, MS Sequel.



We discovered that the Schedule Event Status screens ignores errors 3 and 4 in the schedule log thus if there are not any other errors, reports completed. We opened a support call with Tivoli support and they told us that errors 3 and 4 are ignored and the resolution is that we have to look at each individual log to see if there are errors! Has anyone encountered this and if so do you have any suggestions?
 
PREDATAR Control23

The q event command only tells you if the schedule event is about to start, started, or have completed.

The q event is not going to tell you that Node X backup failed because of .......... .



If the network is lost how will the client send the error message to the server?



The client logs its error in the dsmerror.log or in the dsmsched.log file.



If you have about 200+ clients, I know that you can not go to every client and look at the dsmerror.log and/or the dsmsched.log .



I think that there is a Tivoli product called Event Viewer that may produce the information that you are looking for.



Sias
 
Top