We went from 4.2.2.2 to 4.2.2.13 (as instructed by level 2) to take advantage of an APAR fix for restoring backupsets. All seems well after we upgraded the drivers as well as the server software. We are still testing the APAR fix.
4.2.2.13 is available at ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/server/ NT/4.2.2.13/ , the AIX version is there also. Haven't tried CLEANUP BACKUPGROUPS and I make no claims to this version, only sharing my experiences. Mark B. -----Original Message----- From: Seay, Paul [mailto:[EMAIL PROTECTED]] Sent: Monday, October 07, 2002 2:37 PM To: [EMAIL PROTECTED] Subject: Re: 5.1.1.6 Upgrade (cleanup backupgroups) Not 4.2.1.12, 4.2.2.12 is stable. There is one little piece that CLEANUP BACKUPGROUPS has a problem with. They have a fix for that coming out soon. You may not hit that problem, so put in 4.2.2.12 and run the CLEANUP BACKUPGROUPS. I had to put on a special 4.2.2.13 version (not available on the FTP site). Then run it to get by the bad condition. Once that was cleaned up 4.2.2.12 cleanup backupgroups would run to FINISH also. 4.2.3.0 is imminently going to be released. However, you know they have patches that will be missing because of timing. Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -----Original Message----- From: Lisa Cabanas [mailto:[EMAIL PROTECTED]] Sent: Monday, October 07, 2002 3:13 PM To: [EMAIL PROTECTED] Subject: Re: 5.1.1.6 Upgrade (cleanup backupgroups) So, Paul, would you recommend 4.2.1.12 as stable? I am at 4.2.1.9 (on AIX) and am unable to test 5.1 at this point. 4.2.1.9 to 4.2.2.12 wouldn't seem to be that nasty of a jump. thanks lisa "Seay, Paul" <seay_pd@NAPTH To: [EMAIL PROTECTED] EON.COM> cc: Sent by: Subject: Re: 5.1.1.6 Upgrade (cleanup backupgroups) "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] IST.EDU> 10/02/2002 07:29 PM Please respond to "ADSM: Dist Stor Manager" OK, I ran cleanup backupgroups for a week and it returned 1.5M pages to my database. However, that was not continuous time. I would run it for several hours and cancel it as needed to prevent conflicts with other stuff. My experience was it literally shuts down backup stg and database backups. I have not had to halt the server to get it out of the system. If you had to halt the server, you probably have an additional problem. Note that cleanup backupgroups is also in the release that I am running 4.2.2.12. You do not have to go to 5.1.1.6 to get this fix. The system object problem occurs in 4.2 as well. The time to run the cleanup backupgroups has not specific run time. It will run as long as it needs to seconds, minutes, hours, days, weeks, years, decades, centuries. Whatever it takes. Boy is this a nasty issue. Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -----Original Message----- From: Maria Ragan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 10:59 AM To: [EMAIL PROTECTED] Subject: 5.1.1.6 Upgrade Last week we moved the TSM server from an IBM H70 running AIX 4.3.3 and TSM 4.2.2.4 to an IBM 6H1 running AIX 5.1.0.2 then upgraded to TSM 5.1.1.6. My database is about 51 gigs in size. Tivoli support told me to run "cleanup backupgroup" to cleanup orphaned records when I ran into problems with expiration. I was told other activities (such as backing up the database and client backups) could take place while the command ran. After the "cleanup backupgroup" command was running for 5 hours and a backupdb had been running for 2 hours getting a 4th of the way finished when it normally, takes 30 minutes, I halted the server to kill the cleanup command. Support tells me the cleanup command could take 2 days. They also tell me the next release (2 weeks) should include the ability to background the command and restart where you left off. Does anyone have any experience running cleanup backupgroup to validate the 2 day run time? Thank you, Maria Maria Ragan Systems Engineer Unix Systems Group Yamanouchi Consumer, Inc.
