Hi Daniel, Ah, yes. In the case of system state backup, if you are using client versions 5.5 or older, or you are using version 6.1.3.0 or older, then yes, a skipped system state file will cause the return code 12. This is because it is not simply a case of a single file being missed; rather, the entire system state backup is no good because a missing system state file means the system state is not integral. This is a situation the Windows system owner needs to correct. Ideally the missing file will be reinstated or the system state metadata corrected to no longer include that file if it does not belong on the system.
Having said that, we have seen a large number of cases with missing system state files that resulted in some code changes. Starting with version 6.1.3.1 and higher, as well as 6.2.0.0 and higher, TSM has been modified to tolerate missing System Writer files (System Writer is the largest portion of the system state and is the usual source of missing files). You will still get an error message that says the file is missing, but the system state backup should otherwise continue, and the RC will be 8 (assuming there are no further, more severe errors that occurred during the backup). References: Missing system writer files: http://www.ibm.com/support/docview.wss?uid=swg21419884 http://www.ibm.com/support/docview.wss?uid=swg1IC65828 Other similar issues: Missing Windows Deployment Service (WDS) directory: http://www.ibm.com/support/docview.wss?uid=swg1IC67043 Missing event log file (Windows 2003 x64 only): http://www.ibm.com/support/docview.wss?uid=swg1IC68676 Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> wrote on 2011-08-17 07:34:11: > From: Daniel Sparrman <daniel.sparr...@exist.se> > To: ADSM-L@vm.marist.edu > Date: 2011-08-17 08:32 > Subject: Ang: Re: [ADSM-L] Ang: Re: [ADSM-L] Help tracking down > spurious "Failed 12" errors > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> > > The most common reason I see Failed 12 at our customers is when > parts of the systemstate backup fails. > > I just checked a customer TSM server and they had several Windows > boxes failing with Failed 12. When going through the activity log, > there isnt an actually error, but I can see that it's backing up 6 > parts of the systemstate object. The result from the backup says 4 > objects where successfully backed up, and 2 objects failed. > Unfortunately, the activity log doesnt tell me which part of the > systemstate backup that failed, only that it tried backing them up. > I have no access atm to the dsmerror.log / dsmsched.log so I cannot > tell you what kind of error (if any) to look for. > > Best Regards > > Daniel Sparrman > > > > Daniel Sparrman > Exist i Stockholm AB > Växel: 08-754 98 00 > Fax: 08-754 97 30 > daniel.sparr...@exist.se > http://www.existgruppen.se > Posthusgatan 1 761 30 NORRTÄLJE > > > > -----"ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> skrev: ----- > > > Till: ADSM-L@VM.MARIST.EDU > Från: Andrew Raibeck <stor...@us.ibm.com> > Sänt av: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> > Datum: 08/17/2011 14:10 > Ärende: Re: [ADSM-L] Ang: Re: [ADSM-L] Help tracking down spurious > "Failed 12" errors > > > "Failed 12" is a common error when TSM failed backuping a few files. > > Usual reasons are the file is locked, the file was removed during > > backup and the account running the TSM scheduler did not have access > > to the file. > > In the cases you mention, I would expect the return code to be 4, not 12, > provided that there are no other warnings or errors that would cause a > higher return code. RC 4 is very specific: except for some skipped files, > the backup was otherwise successful. > > Best regards, > > Andy Raibeck > IBM Software Group > Tivoli Storage Manager Client Product Development > Level 3 Team Lead > Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS > Internet e-mail: stor...@us.ibm.com > > IBM Tivoli Storage Manager support web page: > http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/ > Tivoli_Storage_Manager > > "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> wrote on 2011-08-17 > 06:06:29: > > > From: Daniel Sparrman <daniel.sparr...@exist.se> > > To: ADSM-L@vm.marist.edu > > Date: 2011-08-17 07:04 > > Subject: Ang: Re: [ADSM-L] Help tracking down spurious "Failed 12" errors > > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> > > > > "Failed 12" is a common error when TSM failed backuping a few files. > > Usual reasons are the file is locked, the file was removed during > > backup and the account running the TSM scheduler did not have access > > to the file. > > > > When you looked through your dsmerror.log and dsmsched.log, you > > couldnt see any failed files at all? Nor any issues with backuping > > specific filespaces (such as parts of systemstate). > > > > Best Regards > > > > Daniel Sparrman > > > > > > > > Daniel Sparrman > > Exist i Stockholm AB > > Växel: 08-754 98 00 > > Fax: 08-754 97 30 > > daniel.sparr...@exist.se > > http://www.existgruppen.se > > Posthusgatan 1 761 30 NORRTÄLJE > > > > > > > > -----"ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> skrev: ----- > > > > > > Till: ADSM-L@VM.MARIST.EDU > > Från: "Lee, Gary D." <g...@bsu.edu> > > Sänt av: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> > > Datum: 08/17/2011 12:42 > > Ärende: Re: [ADSM-L] Help tracking down spurious "Failed 12" errors > > > > Do a q act s=clientname for the backup times in question. > > You may see something there. > > > > Also, check the windows event log if the clients are windows. > > > > > > > > > > Gary Lee > > Senior System Programmer > > Ball State University > > phone: 765-285-1310 > > > > > > -----Original Message----- > > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On > > Behalf Of Davis, Adrian > > Sent: Wednesday, August 17, 2011 4:41 AM > > To: ADSM-L@VM.MARIST.EDU > > Subject: [ADSM-L] Help tracking down spurious "Failed 12" errors > > > > When using "query event" to check my scheduled backups, I seem to be > > getting "Failed 12" errors for a couple of backups which appear to > > have been successful (This occurs every day for the same servers). > > > > I've checked the client schedule and error logs - but there is no > > record of an error and all messages are what I would expect to see > > for a successful backup. > > > > Any ideas where else I should look? > > > > Many Thanks, > > =Adrian= > > > > DISCLAIMER > > > > This message is confidential and intended solely for the use of the > > individual or entity it is addressed to. If you have received it in > > error, please contact the sender and delete the e-mail. Please note > > that we may monitor and check emails to safeguard the Council network > > from viruses, hoax messages or other abuse of the Council's systems. > > To see the full version of this disclaimer please visit the following > > address: http://www.lewisham.gov.uk/AboutThisSite/EmailDisclaimer.htm > > > > For advice and assistance about online security and protection from > > internet threats visit the "Get Safe Online" website at > > http://www.getsafeonline.org
