I have not seen a response to this question, and I have a similar
situation. We had noticed that our filespaces for our Oracle DB backups
keep growing in leaps and bounds, and it finally became clear that they
were growing faster than would be expected in consideration of the
number of databases we have added. Upon investigation I have found that
there is an enormous amount of space being used by backups that should
have expired, however I cannot delete the entire filespace because that
would also eliminate the valid backups.
I have found that there seems to be two separate issues at play. One is
that upon installing a new version of SQL Backtrack the Oracle admin
that handles those profiles used the wrong management class, leaving the
backups in limbo on TSM. They have expired from the SQL Backtrack
catalog and marked inactive, however, they will never be removed from
TSM in their current state. I cannot bind them to the appropriate
management class via the usual methods. The other issue is that we seem
to have some stragglers from 2001 and 2002, that should have expired,
but are still hanging around for some reason.
The only way I have found in the documentation to remove these items is
by deleting the object by object number from the database. Can anyone
tell me if this is the only way to clean up these items, and if that
will in fact work to remove them from the tapepool storage?
TSM for AIX 5.2.0
TSM for SUN/Solaris 4.2.1
SQL Backtrack 3.0, 4.0.10
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Sent: Friday, April 16, 2004 1:47 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Delete obsolete directories only?
TSM Server 220.127.116.11 on AIX; TSM Client 18.104.22.168 on Windows 2000
I have a situation where over time, the location of data on our network
has moved from server to server. In many cases we moved the identity of
the first server to the second server, but the data paths were not
duplicated exactly. For example,
where "current_root_path" and "old_root_path" are peers under the same
Because the "old_root_path" became invalid on the first backup of the
new server, all the data under it was marked inactive by TSM. No
Once the RetOnly duration elapsed, all the FILES were purged from that
path. Again, no problem there.
But the directories were retained, probably because they were bound to
"no limit" permanent management classes prior to our implementing DIRMC
controls. Meaning those directories will live for the duration of the
server's identity or our TSM system, whichever ends first.
Those duplicate paths confuse our Help Desk. I would like to delete
just the contents under "old_root_path" since there are no files under
that path. But because both root paths are under the same filespace, I
can't delete the filespace. I turned on the permission "node can delete
backups" but that still didn't let me kill that directory tree.
So, is there a way to kill the directory tree under "old_root_path"
other than killing the entire filespace?