I think the "doc" is in the readme for the 4.2.3.x server releases. It recommends going to the latest 4.2.3.x patch to get all the fixes. I ran mine originally on a 4.2.3.2 server level and it all worked fine. Took 14-hours, but then it's a small server. We have since moved to 4.2.3.3 patch level due to a crash problem on AIX. I would recommend going to the latest 4.2.3.3 level. Don't know if it'll improve your performance, but you can cancel the process and it'll restart pretty much where it left off.
Bill Boyer "I haven't lost my mind -- it's backed up on tape somewhere." - ??? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Hart, Charles Sent: Thursday, February 13, 2003 9:31 AM To: [EMAIL PROTECTED] Subject: Re: System Objects and Cleanup Backupgroups Dumb question, what version is the CLEANUP BACKUPGROUPS in? I ask because there is no output from "h CLEAN BACKUPGROUPS" on 4.1 or 5.1.5 Thank You! -----Original Message----- From: Dameon White [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 13, 2003 8:05 AM To: [EMAIL PROTECTED] Subject: System Objects and Cleanup Backupgroups My TSM server is at 4.2.3.0 and we want to upgrade to 5.1.x of TSM. But we have over 50 million orphaned SYSTEM OBJECTS that we have been trying to delete via the CLEANUP BACKUPGROUPS command. We tried to upgrade with the orphans and after 72 hours we backed out. Now we are tryng to delete the orphans, but the problem is that we are only cleaning up 10k-25k per night. At this rate we will not be able to upgrade to 5.1.x for at least 10-15 years. Does anyone have any idea how I can get out of this situation? Can I delete the SYSTEM OBJECT filespaces all together and gamble that I won't have to restore the registry that day? Will deleting the "good" system objects help with the orphans? Thanks. Dameon