I think it's more of a need to fix the reason for the failure, rather than
ignore it. If this is Windows2003, then for full support of the System
State, System Services, and ASR you need a 5.2 client and a 5.2 server.
According to posts on this list, you can get a full recovery using the 5.1
client.

Look at the DSMERROR.LOG file to determine the error. You should also look
at the server activity log for around the time the schedule is ending for
any message there.

It's not always a good thing to ignore errors. If you ignore this one as not
significant, what about the next one?? That could very well be a real
failure of the backup and now you're not covered.

Bill Boyer
DSS, Inc.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Gilmore,Mindy
Sent: Tuesday, October 12, 2004 9:46 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: failed. Return code = 12.


We seem to be getting these errors lately on our Windows 2003 boxes running
TSM client 5.1.6.7.   Looks like we get a good backup but it shows as failed
with "failed.  Return code = 12" Is there a way to tell TSM to ignore these
return codes or files.   WE have scripts that run a rerun backup if it fails
and this is causing a rerun of a backup that we really do not need.