I would add to that list, 
"Restoring the DB in a DR situation" cannot be accomplished in a
realistic amount of time.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Talafous, John
Sent: Tuesday, October 25, 2005 1:57 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: How big of a TSM DB is too big?


The basic symptom that your TSM Database is too big is when Inventory
Expiration, Tape reclamation and DB backup cannot be accomplished in a
realistic amount of time. If these processes are running fine you have
passed health check #1. However, be aware that there are limitations on
any DB size.  

At 150GB (or sooner) I would start thinking about another TSM instance.

fous

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Dearman, Richard
Sent: Tuesday, October 25, 2005 1:45 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] How big of a TSM DB is too big?

My TSM database is currently 150GB and I am wondering if I should start
thinking about a second server.  Other than the DB being so large
nothing else is wrong.

 

Thanks


**************************EMAIL DISCLAIMER***************************

This email and any files transmitted with it may be confidential and are
intended solely for the use of the individual or entity to whom they are
addressed.  If you are not the intended recipient or the individual
responsible for delivering the e-mail to the intended recipient, any
disclosure, copying, distribution or any action taken or omitted to be
taken in reliance on it, is strictly prohibited.  If you have received
this e-mail in error, please delete it and notify the sender or contact
Health Information Management 312.413.4947.