Spirit Software Solutions - TSM Administration and Reporting made easy
Spirit Software Solutions
  • DownloadDownload Products
  • PurchasePurchase Products
  • ProductsOur Products
    • SP Studio
    • TSM Studio Server
  • SupportProduct Support
    • Open a case
    • Helpful TSM SQL Commands
    • Knowledge Base
    • Known Issues
    • Pre Release
    • TSM Studio Documentation
  • ResellersResell TSM Studio
  • Contact UsGet in Touch With Us
Expiration

Expiring old backup and archive data from TSM is controlled by the EXPINTERVAL in your dsmserv.opt file.

EXPINTERVAL=24  specifies to run the expire process every 24 hours.

EXPINTERVAL=0 disables automatic expiration.

Removing old data from TSM can be run manually using the expire inventory command. Data is expired using the “Management Class” definitions that you have set on your files or if none are defined then the defaults for the policy set are used.  ( I will discuss policy sets in an upcoming article )

In version 5 expiration can only be run system wide, in version 6 you can run the expire inventory command on individual nodes, this is useful when changing management classes on individual nodes.

I recommend that you set the EXPINTERVAL to 0 so that you can control at what time this process runs and the setup an admin schedule to run the expire inventory command

Posted in: TSM

  • RSS IBM TSM Notifications

    • Terms of Use
    • IT43823: DOCUMENTATION FOR THE UPDATE STATUSTHRESHOLD IS MISLEADING.
    • IT43779: TIER STORAGE POOL SUMMARY PROCESS HANGS WITH WORKER PROCESS SHOWING ZERO FILES/BYTES PROCESSED.
    • IT43750: REMOVE REPLNODE IN MULTI-TARGET REPLICATION ENVIRONMENT CAN SET NODE REPLICATION STATE TO NONE
    • IT43630: VERSION 8.1.X API FUNCTION DSMUPDATEFS() PERFORMANCE IS DEGRADEDCOMPARED TO PREVIOUS API VERSIONS
    • IT43739: ANR4560E MAY OCCUR ON COMBINATIONS DOCUMENTED AS COMPATIBLE.
© 2014-2023 Spirit Software Solutions
  • Download
  • Purchase
  • Products
  • Support
  • Resellers
  • Contact Us