Hi Michael,
we experienced the same thing when we asked clients to upgrade to 5.4.1.2
( to avoid the security vulnerability in the dsmcad ): Incrementals started
backing up the entire filestore - which gave us a headache at the server end.
Running: dsmc incr -traceflags=service -tracefile=/path/to
I run a TSM 5.3.4.0 TSM server. I recently encounterered a problem where the
5.3.4.0 linux TSM client aborted every time it processed a given file system
on one of my servers.
Instead of upgrading to a newer 5.3.4 client level as would probably have
been the wisest thing to to, I promptly uninstal
