[ADSM-L] Expiration and Delete Filespace causing TSM DB to grow and crash
2010-11-23 14:36:06
Hi TSMers,
Our TSM 6.1.3.3. has a Windows 2008 (R2 64bits) client node that
contains over 14 millions files (95% being SystemState backup files) and when
either the expiration process or a delete filespace command is run against it,
TSM DB is growing at the rate of 1 gb/hour until DB2 DB gets a space exhausted
message and TSM crashes. Of course we removed that node from the daily
expiration process but we'd like to clean those entries from the DB before
doing a DB2 REORG of some Index tables that became huge over the last year. By
the way, under TSM 5.5, our TSM DB was 85gb (1 year ago) and it now reach over
400gb (more than 50% being Index table fragmentation we were told by IBM). Any
thoughts on how to get rid of those entries (Export node was not a success too
but cause no DB increase) ?
Pierre Billaudeau
Analyste en stockage
Livraison des Infrastructures Serveurs
Société des Alcools du Québec
514-254-6000 x 6559
___________________________
Information confidentielle:
Le présent message, ainsi que tout fichier qui y est joint, est envoyé à
l'intention exclusive de son ou de ses destinataires; il est de nature
confidentielle et peut constituer une information privilégiée. Nous avertissons
toute personne autre que le destinataire prévu que tout examen, réacheminement,
impression, copie, distribution ou autre utilisation de ce message et de tout
fichier qui y est joint est strictement interdit. Si vous n'êtes pas le
destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de
courriel et supprimer ce message et tout document joint de votre système.
Merci.
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [ADSM-L] Expiration and Delete Filespace causing TSM DB to grow and crash,
Billaudeau, Pierre <=
|
|
|