dhaue
ADSM.ORG Member
Running TSM 5.3.5
I’m in the process of cleaning out large numbers of old TDP (Oracle) backups by having the DBA’s delete from RMAN and, if necessary run TDPOSYNC.
As advertised, the state for each object changes from ACTIVE_VERSION to INACTIVE_VERSION, then disappears from the database the next day when expiration processing runs (configuration is the recommended for TDPO clients with number of versions equal 0).
Finally, to my confusion and question:
Why is it that after expiration runs, I can look at the occupancy for that TDP Node (query auditoccupancy) and I don’t see any reduction in the total occupancy.
The only way I could possibly explain this behavior is if the space continues to show up in the occupancy until the associated tape goes through reclamation, but that doesn’t make any sense.
Does anyone have any thoughts?
Thanks.
I’m in the process of cleaning out large numbers of old TDP (Oracle) backups by having the DBA’s delete from RMAN and, if necessary run TDPOSYNC.
As advertised, the state for each object changes from ACTIVE_VERSION to INACTIVE_VERSION, then disappears from the database the next day when expiration processing runs (configuration is the recommended for TDPO clients with number of versions equal 0).
Finally, to my confusion and question:
Why is it that after expiration runs, I can look at the occupancy for that TDP Node (query auditoccupancy) and I don’t see any reduction in the total occupancy.
The only way I could possibly explain this behavior is if the space continues to show up in the occupancy until the associated tape goes through reclamation, but that doesn’t make any sense.
Does anyone have any thoughts?
Thanks.