You do not say which client version and operating system you are running.
Correct TSM behavior is to indicate a status of "Complete" for backups
where the only problems were skipped files. There was a bug in the 4.2.1.0
client that was reporting a status of "Failed" in such a situation, but
that has since been fixed.

Starting with version 5.1, the client reports a status of "Complete" and a
return code of '4' when the only problems were skipped files. See the
client manual chapter on "Automating Tasks" for info on the 5.1
backup-archive client return codes. From the TSM server, the RESULT column
in the EVENTS table and the Result column in the QUERY EVENTS output will
show you the client return code.

Regards,

Andy

Friday, March 28, 2003 08:23
To: ADSM-L AT VM.MARIST DOT EDU
cc:
From: "Hart, Charles" <charles.hart AT MEDTRONIC DOT COM>
Subject: Reporting Client Backup Competitions and SLA's



We have a backup environment where we have a lot of "Skipped Files" due to
users leaving files open which TSM appears to report as a Backup Failure
when actually its a Success with Errors?  I'm asking because I have to put
out a monthly backup report that must meet our current SLA's and am getting
killed with Skipped files showing up as a failure.  Our management feels
that being that we are operating under the assumption that there will be
opened files they are comfortable with Skipped file backups begin reported
as Successful.


Current Queries used to generate reports
q event * * begind=-1

SELECT EVENTS.SCHEDULED_START, EVENTS.DOMAIN_NAME, EVENTS.SCHEDULE_NAME,
EVENTS.NODE_NAME, EVENTS.STATUS FROM EVENTS EVENTS WHERE
(EVENTS.SCHEDULED_START>={ts '2003-02-01 00:01:00'}) AND
(EVENTS.STATUS<>'Uncertain')

Regards,

 Chalres