Ever since I upgrade one of our busy TSM servers from 5.5.3 to 5.5.4.1, I have been having constant problems with the log being pinned and filling.
While I was able to determine and fix 2 problem nodes (long/large Oracle backup and another node that is compressing and backing up a 280GB log file, 5-times and thus running for 10-hours), I am still having problems. The log went to 90% last night. I see there is a 5.5.4.2 server patch but none of the fixes I saw addressed such issues. So, I would like to schedule a "show logpinned" command every 15-minutes and send the output somewhere so it can be emailed to me. I have never messed with server scripting so this is new territory for me. Does anyone have a script/process they can share, to deal with this? The TSM servers are RedHat Linux 5. One a related topic, I am constantly finding folks who have live/changing files being backed up multiple times (yes, I know - server owners should be more responsible for what they are backing up....), since the default is "CHANGINGRETRIES 5". I am seriously thinking of pushing "CHANGINGRETRIES 0" via CLOPTSET. Is there and real value to the default of "5"? What do folks out there set this to and why? Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services [email protected] - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
