TSM database size growth

frankantony

ADSM.ORG Member
Joined
May 15, 2011
Messages
50
Reaction score
0
Points
0
Hi All,

We have 45 nodes configured to one TSM server. But the database growth is growing rapidly. It reached 470 GB now. I can see expiration is completing fine everyday.Please advise how to control TSM database growth. How can we check which node is using more database.

Server version:6.3.0.0



Thanks,
Frank
 
DB growth depends on a lot of factors:

1. Backing up millions of files? The more files the bigger the DB gets.
2. Retention period - the longer, the larger your DB will be.

I am not sure if there was an issue with TSM 6.3 on the DB. Search IBM's website. Personally, I don't use base versions.
 
Hi Frank,

The number of nodes backed up is not really relevant when it comes to database size, however number of objects backed up, number of versions retained, number of days retained can play a big role.

In the manual, you can find a few methods to estimate the database size, you can use that to see if it matches what you see:
http://www-01.ibm.com/support/knowl....srv.install.doc/t_srv_inst_db_space-aix.html

You can use these 2 queries to see how many backup and archive objects you have:
Code:
select state,count(*) as "no. of objects" from backups group by state
select count(*) as "no. of objects" from archives

In addition to the space used by the objects, there's also other factors that affect growth like if reorgs are running on tables and indices, if deduplication and replication are enabled, those all have an impact. Here's some good reading on database growth: http://www-01.ibm.com/support/docview.wss?uid=swg21452146

Marc...
 
Back
Top