If you want to avoid the gamble, just RENAME the SYSTEM OBJECT filespace to something else. After the next client backup, you'll have a new, clean SYSTEM OBJECT filespace.
After a couple of days, delete the old one. Or if you have a disaster in the meantime, you can rename ithe old SYSTEM OBJECT filespace back and use it for a restore. -----Original Message----- From: Dameon White [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 13, 2003 9: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
