My only thought is that in essence, you did a database reorg on the new
instance, and left big holes in the databae on the old instance.  When
we split databases, we had to do a reorg on the old instance to free up
the space.

Meadows, Andrew wrote:

I would have to agree there seems to be an issue. I just recently split my 
enviroment to 2 tsm servers. I have exported over 1\2 the nodes and 55 percent 
of the files to the new server. Before the split server a db size was 80 gb 91% 
full. After the split server b's db is 20 gb and like I said it has more files 
than server a.
After deleting the nodes from server a I still have 90 % of the 80 gb database 
taken up and expiration does run to completion daily.
Thoughts?

-----Original Message-----
From: ADSM: Dist Stor Manager <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU <ADSM-L AT VM.MARIST DOT EDU>
Sent: Thu Jan 26 03:20:26 2006
Subject: Re: TSM Database Size Growing Since Upgrading to 5.2.4.5

It's just a shot in the dark, but the last time this kind of thing
started happening, W2K system objects weren't being expired correctly
and it was these filespace occupancies that were clearly increasing the
db and storage. I say 'clearly', it only really became evident after 6
months.

I'm not at this level of code, so can't check and I would hope that I am
wrong and the bug hasn't been reintroduced, but it is something to look
at and check off the list as not being the problem.

May want to check W2K3 system state and system services also.


Leigh

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Cowen
Sent: 25 January 2006 19:48
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM Database Size Growing Since Upgrading to
5.2.4.5

Graph your occupancy (num_files) by domain for each server and see if it
shows uniform growth.

If not, drill down to node occupancies (num_files), and so on.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Andrew Carlson
Sent: Wednesday, January 25, 2006 2:39 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM Database Size Growing Since Upgrading to
5.2.4.5

I might have thought that too if it wasn't all 3 instances. I graphed my
database sizes back to 2004 (I have them in a mysql database), and it is
striking the growth curve since 11/12/2005.

Jack Coats wrote:

No unusual new clients being added?  Retaining more data?
Change of include/exclude files? ... Just grasping for straws...

-----Original Message-----
Subject: [ADSM-L] TSM Database Size Growing Since Upgrading to 5.2.4.5

On November 11th, we upgraded our 3 tsm instances from 5.2.1 to

5.2.4.5.  Since then, our three databases have grown at an alarming

rate.  They have grown:

56GB to 75GB (33%, 19Gb growth)
46GB to 65GB (41%, 19Gb growth)
53GB to 63GB (18%, 10Gb growth)

Anyone have problems like this?  Thanks.
Privileged and Confidential: The information contained in this e-mail

message is intended only for the personal and confidential use of the
intended recipient(s). If the reader of this message is not the intended
recipient or an agent responsible for delivering it to the intended
recipient, you are hereby notified that you have received this document
in error and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately by e-mail, and
delete the original message.

SPECIAL NOTICE


All information transmitted hereby is intended only for the use of the
addressee(s) named above and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or distribution
of confidential and privileged information is prohibited. If the reader
of this message is not the intended recipient(s) or the employee or
agent
responsible for delivering the message to the intended recipient, you
are
hereby notified that you must not read this transmission and that
disclosure,
copying, printing, distribution or use of any of the information
contained
in or attached to this transmission is STRICTLY PROHIBITED.

Anyone who receives confidential and privileged information in error
should
notify us immediately by telephone and mail the original message to us
at
the above address and destroy all copies.  To the extent any portion of
this
communication contains public information, no such restrictions apply to
that
information. (gate02)

********************************************
This message is intended only for the use of the Addressee and
may contain information that is PRIVILEGED and CONFIDENTIAL.

If you are not the intended recipient, you are hereby notified
that any dissemination of this communication is strictly prohibited.

If you have received this communication in error, please erase
all copies of the message and its attachments and notify us
immediately.

Thank you.
********************************************