yep tsm: MSPSTG5>help clean CLEAN Command CLEAN Command Use the CLEAN DRIVE command to clean a drive in a SCSI library for Storage Manager. CLEAN DRIVE (Clean a Drive)
tsm: MSPSTG5>help cleanup ANR2306E No help text could be found for this command/subcommand: CLEANUP. ANS8001I Return code 11. -----Original Message----- From: Kyle Payne [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 13, 2003 9:12 AM To: [EMAIL PROTECTED] Subject: Re: System Objects and Cleanup Backupgroups Did you run help clean or help cleanup? Kyle -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of Hart, Charles Sent: Thursday, February 13, 2003 8: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
