7.5 TSM EXPIRE INVENTORY Process Overview

How TSM deletes old or expired backup and archive files from TSM Server storage ?

To delete the old or expired backup and archive files from the server storage, you have to run the expire inventory command. By default this process automatically runs every day, you can customize it however. Copies of files that have expired are not deleted from server storage until expiration processing occurs. Expiration is the process of identifying files for deletion because their expiration date or retention period is passed. Files that are backed up or archived are marked expired by Tivoli Storage Manager, based on the criteria that are defined in the backup or archive copy group. Expire inventory process is resource intensive and can sometimes TSM server get hangs, so you need to properly monitor and manage this expire inventory process.

The expire inventory command starts the inventory expiration process. The inventory expiration process removes client backup and archive file copies from server storage. The process is based on the policy that is specified in the backup and archive copy groups of the management classes that the files are bound to. This command can be scheduled. You can enhance the expire inventory command by using the following additional parameters: 
  • NODE
  • TYPE
Also Read: Why is it important to use DIRMC option during backups ?

Expiration processing then deletes eligible backup versions and archive file copies. Backup versions are eligible based on policy in the backup copy group, how long and how many inactive versions are kept. Archive file copies are eligible based on policy in the archive copy group, how long archived copies are kept. For example, to run manual expiration run the following command
expire inventory type=backup resource=3 duration=60

When you have the disaster recovery manager function for your Tivoli Storage Manager server, the inventory expiration process also removes eligible virtual volumes that are used by the following processes
  • Database backups of type BACKUPFULL, BACKUPINCR, and DBSNAPSHOT. The SET DRMDBBACKUPEXPIREDAYS command controls when these volumes are eligible for expiration.
  • Recovery plan files of type RPFILE and RPFSNAPSHOT. The SET DRMRPFEXPIREDAYS command controls when these volumes are eligible for expiration.
The inventory expiration process that runs during server initialization does not remove these virtual volumes. 

EXPINTERVAL Server option

You can run expiration processing either automatically or by command. You control automatic expiration processing by using the expiration interval option (EXPINTERVAL) in the Tivoli Storage Manager options file (dsmserv.opt).

Also Read: 8 commands to efficiently schedule TSM Expire Inventory Process

EXPINTERVAL option specifies the number of hours between automatic inventory expiration runs. Inventory expiration is resource intensive. You can set the EXPINterval to 0 and schedule expiration during slower periods.

Has a minimum value of 0, where automatic expiration does not occur and must be started with the expire inventory command. Has a maximum value of 336 hours (14 days) and has a default value of 24 hours.

Cancelling Expire Inventory process

Expiration is restartable if you cancel the process. It always starts from the beginning, based on the node name registration date if you simply cancel the process. However, if you cancel it by using the cancel expiration command, it continues from the point where it stopped. If you need to cancel inventory expiration, use the following command
cancel expiration

0 Comment to "7.5 TSM EXPIRE INVENTORY Process Overview"

Post a Comment