I have had recent issues with this as well. After researching it and the
I found there are various methods to handle this problem. In no specific
order; 1) edit the file reference out of the registry, 2) reinstall or
copy the missing file from another server and place it into the location
where the backup is looking for it, 3) create a "dummy" file for the one
missing using the exact name and location, 4) upgrade the TSM client
(see link below). Since editing the registry of production servers was
not an attractive option I went with the second option as recommended
from Microsoft and TSM. Once we are out of our "change blackout" during
the holiday season I will go back and upgrade the clients.

Hope this helps...here is a link to a posted IBM-TSM doc.
http://www-01.ibm.com/support/docview.wss?uid=swg21419884 


~Rick


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
duholm
Sent: Thursday, December 16, 2010 6:14 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] System statebackup

Hi All

I have a problem with TSM and system statebackup.

In the last couple of weeks we have exprienced an increase in the number
of backup with warnings in the system state backup. The system state
writer cannot find a certain file. When I look for the file it does not
exits. So there is a reason why, the system state writer cannot find it.
However how do I recreate the list of files, that the system writer
backups up, so I don't get this error.

At the moment I put the line SKIPMISSINGSYSWFILES YES into the option
file and that seems to work. However, thats a workaround and not a
solution. Maybe this is the only way for the backup to succeed
successfully.

I hope someone out there can help me  :D

Regards
Bo

+----------------------------------------------------------------------
|This was sent by bdh AT itrelation DOT dk via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------