Server is AIX 4.3.3 running TSM 4.2.1.7 Prior to this weekend, everything seemed to be fine on this Netware 4.11 server running B/A Client 4.1.3.0. Compression is set to ON at the Node Definition level. It was inspecting its 111K+ files and backing up between 200-1000 files a day (about 60-200MB) and completing that entire processes within 20 or 30 minutes, according to log information. Friday night, the backup didn't complete until Sunday morning, running 31+ hours, backing up 18K+ files (30GB+). Sunday night's backup was still running Monday morning when we came in. We cycled that Netware server (which killed the backup in progress). We even cycled the TSM server process and OS (as a request from TSM support regarding another issue). I took the opportunity to increase the log retention days, and turn on verbose logging. (On the sessions where the backup amounts increased, the dsmerror.log indicated several instances of session lost due to inactivity, but that is quite possible as some of the files on this server are quite large, and compression could have caused a session to time out.) Last night's backup was still running when we came in this morning. With the verbose logging, I could see what files were being backed up. I started a GUI restore session with view active/inactive set on, and navigated to some of the directories that I noticed in the logs. In all cases that I checked... 1. The entire directory and files within had been in existence since before TSM was installed on this node (Nov, 01). 2. Those files in that directory had backed up originally on day one of TSM on this node 3. Some of the files had recently been backed up again early in Feb 03, even though there was no evidence of them changing. 4. Those same files started backing up again this weekend, again, even though there was no evidence of the changing. They appear to be backing up every session, even though the session on Friday night - Sunday morning successfully completed, and they backed up then.
One more thing, we do have the NWIGNORECOMPRESSBIT flag set to YES, but that really shouldn't have mattered as many of the files that I noticed should have been Netware compressed for a very very long time, and would not have been accessed by a user. Any clues? Thanks, Todd
