On Fri, 17 Sep 2004, TSM_User wrote:

> If you believe that the client accurately reports files it skips, which we 
> do, then you can have a script run against the TSM server to list out all the 
> files that were skipped or failed.  We have a report that runs every morning 
> that give us such a list.  We use that to determine what things we might want 
> to add to our exclude list.  In addition the TSM reporting tool gives you the 
> same thing.  It groups files by node and then files in general
>
> In this case you have to first run the backup which seems to be different 
> then what you want.  But after that you have your delta.  Ever file that 
> didn't backup up has an error message in the TSM act log and in the 
> dsmerror.log.

The problem I find with the reports I'm getting, and with TSM,
is that TSM (like all computers) do just exactly what you tell
it to do. If in your dsm.opt you have 'domain c:\ d:\ e:\' and
someone adds a 'g:\', the 'g:\' is not backed up. The enhancement
I am requesting will compare the live filesystem with TSM and
tell me what is not in TSM. I know I can look in the logs and
find those files that had problems or were skipped for some
reason... that's not the problem. I have not seen TSM have a
problem restoring files *that have made it to TSM*. I have seen
(many times) where something has changed and either the
dsm.opt, dsm.sys, or inclexcl.list, have not been changed
accordingly. As such TSM is not able to restore the files that
never made it to TSM.

The TSM log does not list 'I didn't backup this file because
you didn't tell me to in the inclexcl.list' type of messages.

Mike