Thanks for clearing that up. Can I trouble you with a couple more questions?
1) When I try to delete or rename the filespace by name most of the time I get a response that not such filespace exists. I have gotten somewhat better luck by renaming the filespace to something without spaces by using the FSID, then trying to delete the renamed space. But that doesn't always work either. 2) I frequently get lock errors trying to delete the system object file spaces. I have seen them occasionally before, but this is pretty much guaranteed to cause them, so severly that I have to cycle the TSM server to get things working again. Any suggestions how to avoid this? 03/13/03 16:09:00 ANR0538I A resource waiter has been aborted. 03/13/03 16:09:00 ANR9999D bfcreate.c(671): ThreadId<95> Error 82 getting information for object 0.102099013. 03/13/03 16:09:00 ANR9999D imutil.c(6259): ThreadId<95> Error 19 deleting dependent bitfile 0.102099013. 03/13/03 16:09:00 ANR0985I Process 59 for DELETE FILESPACE running in the BACKGROUND completed with completion state FAILURE a t 16:09:00. 03/13/03 16:09:40 ANR8810I Volume 810778 has been labeled in library ES. 03/13/03 16:10:00 ANR0538I A resource waiter has been aborted. 03/13/03 16:10:00 ANR1029W Migration process 55 terminated for storage pool AR_SHORT_DISK - lock conflict. Thanks, Kai. -----Original Message----- From: Prather, Wanda To: '[EMAIL PROTECTED]' Sent: 3/14/03 12:21 PM Subject: RE: Finding system objects to delete The SYSTEM OBJECT filespace is only created for Win2K systems, using at least the 4.1 backup client. The SYSTEM OBJECT filespace includes the registry, the COM+DB, the RSM data base, and other Win2K-only constructs. WinNT machines do back up the registry, but don't create a separate filespace, and don't have the dreaded system object bloat problem. You only have to worry about cleaning up the existing SYSTEM OBJECT filespaces. -----Original Message----- From: Kai Hintze [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 11, 2003 4:37 PM To: [EMAIL PROTECTED] Subject: Finding system objects to delete Oh wise and experienceds star-sum wizards! I crave the boon of a clarification: Summary: If I don't see a file system named SYSTEM OBJECT for a given node does that mean that we aren't backing up the system object on that box? Discussion: I want to clean up our TSM 4.2.1.6 server (AIX 4.3.3) before I migrate it to a different box (AIX 5.1.latest) and upgrade TSM to 5.reasonably_stable. Among other things, the database is getting much larger than we expected, so I suspect that I am victim of the dreaded system object bloat, given the level of TSM server I am running. I went back through the archives researching the topic "delete system object". I found several references to rename/delete the "SYSTEM OBJECT filespace". But only about 1 in 10 of our WinNT systems has a SYSTEM OBJECT filespace listed in the filespaces table. Does that mean that most of our windows servers don't back up their system object? That would be mixed news at this point, but before I can deal with it, I need to know for sure what I am dealing with. Thank you in advance for your help. - Kai.
