Expiration Process doesnt run

[Shiv0202s]

Hi All,

Expiration process doesn't run on the TSM Servers.

We have Configured Deduplication, Replication on 2 TSM servers 6.3V. The Total backedup Data is around 5TB in both the servers. So the Database size should not be more than 50GB.
But in both the TSM server the Database is around 180GB used.
Can someone suggest what needs to bo done.

 

[Shiv0202s]

Hi All,

Expiration process doesn't run on the TSM Servers.

We have Configured Deduplication, Replication on 2 TSM servers 6.3V. The Total backedup Data is around 5TB in both the servers. So the Database size should not be more than 50GB.
But in both the TSM server the Database is around 180GB used.
Can someone suggest what needs to bo done.

12/15/2014 11:00:09 ANR0984I Process 781 for EXPIRE INVENTORY started in the

BACKGROUND at 11:00:09. (SESSION: 32722, PROCESS: 781)

12/15/2014 11:00:26 ANR0987I Process 781 for EXPIRE INVENTORY running in the

BACKGROUND processed 95 items with a completion state of

SUCCESS at 11:00:26. (SESSION: 32722, PROCESS: 781)

 

[marclant]

Looks like expiration is running fine based on those messages.

A 180GB database is actually a small database if you are using dedup and replication. I've worked with a few customers that have databases greater than 1TB.

This technote (http://www-01.ibm.com/support/docview.wss?uid=swg21596944) provides a script to show you how much DB space is used for dedup. When doing dedup, there is a cost, while it takes less storage space, all the deduped chunks have to be referenced in the database, it takes a lot less space than the actual files, but it takes more space than a traditional backup.

If you also suffer from insomnia at some point, you can read this technote on database growth: http://www-304.ibm.com/support/docview.wss?uid=swg21452146

 

[marclant]

Also, since you are using dedup, I highly recommend going to 7.1.1.100 or 7.1.1.200 when it's released. There are a few APARs and enhancements at these levels that do help with the reorg portion, which has an impact on DB size.