On one host, I recently upgraded the TSM client from 5.4.0.0 to
5.4.1.5.  During the next backup run, it proceeded to backup all
files rather than just changes.  Has anyone else seen this behavior?
Is a simple client version switch enough to trigger a full backup?

I was able to repeat the behavior by reverting back to 5.4.0.0, at
which point it again backed up everything.  I then ran it again at
5.4.0.0 and nothing was backed up, as expected.  Then I upgraded
again to 5.4.1.5.  Everything was backed up.  Ran it again at
5.4.1.5.  Nothing was backed up, as expected.

TSM Server: Sun SPARC V880, Solaris 9, TSM EE Server 5.2.9.0
TSM Client: Sun X4500 "Thumper", Solaris 10 x86, TSM client 5.4.0.0
            and 5.4.1.5

The reason why this would be a huge problem for us is that our
X4500s (and other file servers) have many TBs of data on them.  I
don't want that going to tape for a second time after a TSM client
upgrade.

Any ideas?

Lance Nakata
Stanford Linear Accelerator Center