droach
ADSM.ORG Senior Member
I discovered that a lot of my Oracle and SQL servers had TDP backup "objects" stored on tape that were way past the company retention period. Some of the Oracle ones were due to the crosscheck not running properly...easy fix. Most of them seem to be due to special one-time backups and backups of long deleted databases. These objects stay "active" and are wasting tape space. I am trying to figure out how to auto-magically inactivate them.
To find these outdated object I use the following command:
and it returns object like this:
I found this command that I can schedule to run on the clients:
Before I go down this route I was curious how others are keeping their DBA's honest.
To find these outdated object I use the following command:
select cast(object_id as char(15)), node_name, HL_NAME, ll_name, backup_date, state from backups where (node_name like '%%_TDP' or node_name like '%%_SQL') and backup_date < (current_timestamp - 36 days) order by node_name,backup_date
and it returns object like this:
OBJECTID NODE_NAME HL_NAME LL_NAME BACKUP_DATE STATE
--------------- ------------------ ------------------ ------------------ ------------------ ------------------
838462739 MYSERVER9_SQL \WBS_m000\2013020- log 2013-02-02 ACTIVE_VERSION
2135702\000038F0\ 08:57:01.000000
This object is past my retention policy and should not be active. I know how to delete the object from the TSM database using the command 'delete object 0 838462739' command, and I know how to expose the 'Inactivate' tab in the TDP GUI and flag these objects as 'Inactive', but I am looking for a way to run a scheduled task on my TSM servers (or clients) that will mark any/all TDP objects inactive if they are older than my retention policy states.--------------- ------------------ ------------------ ------------------ ------------------ ------------------
838462739 MYSERVER9_SQL \WBS_m000\2013020- log 2013-02-02 ACTIVE_VERSION
2135702\000038F0\ 08:57:01.000000
I found this command that I can schedule to run on the clients:
tdpsqlc inactiv * * /olderthan=36
Before I go down this route I was curious how others are keeping their DBA's honest.
Last edited: