I am guessing that this isn't a 5.1 or higher client, since RC 4 should
not result in a failure. For 5.1 and higher, return codes are in the
client manual chapter on "Automating tasks". For versions below 5.1,
return codes are not documented and you can not necessarily attach any
special meaning to them. You need to check the client schedule and error
logs to see what the problem is.
There was a bug in the 4.2.1.0 client that caused skipped files to result
in backup failures. 4.2.2 and up fix this problem.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Justin Bleistein <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
07/07/2003 13:18
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: Restore slows to a crawl
These return codes sometimes I notice them in the actlog and I also notice
them when I query a scheduled TSM backup event with the: "q event * *
node=node_name f=d" command. Does anyone know where a list of THESE return
codes are? A reference of some sort? Not server return codes or Unix
scripting return codes but client event return codes? Any assistance would
be appreciated thanks!.
07/07/03 12:10:27 ANR2579E Schedule DAILY.INCR in domain NUN.UNIX for
node
EAPPS.BACKUP1 failed (return code 4).
--Justin Richard Bleistein
Unix/TSM Systems Administrator (Sungard eSourcing)
Desk: (856) 566 - 3485
Cell: (856) 912 - 0861
Email: [EMAIL PROTECTED]
