Re: System Objects and Cleanup Backupgroups
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
Re: System Objects and Cleanup Backupgroups
> 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? There is a less draconian version of this strategy that some sites have used successfully. Execute 'rename filespace' commands for the system objects. Subsequent backups will create new system object file spaces without the pathalogical behavior. After a few days the renamed filespaces can be deleted. If you needed to restore from a renamed filespace you could change it back to its original name. Even 'delete filespace' commands for the number of objects you mention are going to be a major undertaking. It may take you as much as several months to get rid of all the files. Be careful about running too many 'delete filespace' commands concurrently. I have never had occasion to delete a system object filespace, but my experience with other types of filespaces has been that anything beyond two concurrent 'delete filespace' processes is counterproductive.
Re: System Objects and Cleanup Backupgroups
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
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
Re: System Objects and Cleanup Backupgroups
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
Re: System Objects and Cleanup Backupgroups
Another dumb question...what is "Orphaned system objects" Regards Niklas Lunström Swedbank -Original Message- From: Hart, Charles [mailto:[EMAIL PROTECTED]] Sent: den 13 februari 2003 15:31 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
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
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
