Hello, very interesting problem... good follow up guys. Just a small comment, why are you still in 5.2 TSM server version? The 5.2 is not supported since a while and 5.3 will end in july 2008. And... client 5.4 is not supported with 5.2 server, it should 5.3 at least BUT as say my notice is only a comment, not a solution advise.
A presto. Cordiali saluti / Meilleures salutations Maurizio Teruzzi http://www.teruzzi.ch ftp://ftp.teruzzi.ch Skype user: TERUZZI Rainer Wolf ha scritto:
Hi Lance, we have the same problem and it is caused because you are using a zfs filesystem (i assume) and this appears in 5.4.0 as UNKNOWN and now you should see the filespace as ZFS . this support comes with 5.4.1.x I don't believe that the sending of all data can be suppressed. A much more bigger problem for us here is that the backup-performance is strongly degraded for filepaces > 5mioFiles. Even skipacl and other things didn't help on this performance Problem. The backup session takes around 50% more time to get through. After your 'full-backup' : can you please take a look at the total-elapsed time before and after the update ? I would be interested if you get about the same times running incrementals on the 'tsm-zfs' filespaces as before. It would be interesting if you have > 5mio files to scan. On smaller filespaces we have no problems at all. I had an pmr open for around 9 months and closed it now because we want to start again all with 5.5 server+clients and I am tired to go on with this terrible performance problem and ibm cannot reproduce this ... maybe they don't have those fast Solaris-Server (to run the tsm-clients) where those things happens ? Currently we are using 5.3 server and 5.4 clients regards Rainer kiz - Abt. Infrastruktur Universitaet Ulm Zitat von Lance Nakata <[EMAIL PROTECTED]>: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
