ADSM-L

Re: cleanup backupgroups

2002-10-14 20:55:25
Subject: Re: cleanup backupgroups
From: "Seay, Paul" <seay_pd AT NAPTHEON DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 14 Oct 2002 20:52:48 -0400
SYSTEM OBJECTS is a windows thing.  If you do not have windows clients, you
probably do not have the problem.  The release you are running 4.2.2.0 is
not a good release to be on.  I would recommend you get to 4.2.2.12 or
higher as soon as possible.  I will not say go to 4.2.3.0 because it is not
available yet and it is unproven an unknown what new undesireable features
it will introduce.  If you do have Windows clients, it is not clear if
4.2.2.0 introduced the SYSTEM OBJECTS debacle, but to be safe putting on
4.2.2.12 or higher would be a good thing.

Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180


-----Original Message-----
From: Matt Simpson [mailto:msimpson AT UKY DOT EDU]
Sent: Monday, October 14, 2002 10:53 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: cleanup backupgroups


I'm a newcomer to this list, and a newcomer to TSM. So there's a very good
chance that I'm totally confused.  I'm catching the tail end of this cleanup
backupgroups discussion, and I need some clarification.

I think I'm reading that there's a problem in 4.2.2.x versions of TSM which
causes SYSTEM OBJECTS not to expire, requiring the CLEANUP BACKUPGROUPS.
I've seen some messages that indicate the cleanup needs to run after
conversion to 5.1.

We're running TSM 4.2.2.0 on Solaris.  We hope to upgrade to 5.1 sometime,
but probably not soon.  While we're still on 4.2.2.0, do we need to do this
cleanup regularly?  We recently had a problem with TSM coming to a
screeching halt after our database got 100% full, and we're not sure why a
database that was supposedly way bigger than we would ever need has filled
up before we've even got half our backups on it.  Is it possible that this
systems objects problem is contributing to our db size problem?
--


Matt Simpson --  OS/390 Support
219 McVey Hall  -- (859) 257-2900 x300
University Of Kentucky, Lexington, KY 40506 <mailto:msimpson AT uky DOT edu>
mainframe --   An obsolete device still used by thousands of obsolete
companies serving billions of obsolete customers and making huge obsolete
profits for their obsolete shareholders.  And this year's run twice as fast
as last year's.

<Prev in Thread] Current Thread [Next in Thread>