Backing Up Oracle - Computing at Cornell

Once the object is sent to the TSM server, you can verify which management
class was used by performing an SQL query of the archive or backup TSM
internal database table.
4.5.4 Life cycle of TSM data objects
Backup data objects and archive data objects are managed differently. We
will use the term life cycle to describe how these data objects exist on TSM
storage from initial creation to when they are purged.
4.5.4.1 Life cycle of archive data objects
An archive object exists in two states, current and expired, before being
purged from the TSM server. Figure 9 shows the three steps involved in the
life cycle of an archive data object.
Step 1: A copy of the client data is sent to the TSM server as an archive
object. Upon initial creation the archive object is in a current state.
Step 2: It remains in a current state until the TSM client program deletes the
archive object manually, or the archive object exceeds its retention setting. At
this point the archive object changes state from current to expired.
Step 3: The archive object remains in the expired state until expiration
processing runs on the TSM server. This process is invoked by a TSM
administrator with the expire inventory command. When expiration
processing encounters an archive object in the expired state, it purges that
object from the TSM database and frees up the storage space where the
archive object resided.
Figure 9. Archive object life cycle
44 Backing Up Oracle using Tivoli Storage Management