ces also.
Leigh
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Cowen
Sent: 25 January 2006 19:48
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM Database Size Growing Since Upgrading to
5.2.4.5
Graph your occupancy (num_files) by domain for
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
---Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Cowen
Sent: 25 January 2006 19:48
To: ADSM-L@VM.MARIST.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
, 2006 2:39 PM
To: ADSM-L@VM.MARIST.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
Good question, I didn't think of that one. It does appear that
expiration is working (at least it says it is working - it is expiring
objects, and a fairly normal amount).
David Longo wrote:
Have your Expirations been running successfully?
David Longo
[EMAIL PROTECTED] 01/25/06 2:05 PM >>
clude 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:
I've noticed similar symptoms.
Ice just been chalking it up to more use.
-Original Message-
From: ADSM: Dist Stor Manager
To: ADSM-L@VM.MARIST.EDU
Sent: Wed Jan 25 13:05:12 2006
Subject: TSM Database Size Growing Since Upgrading to 5.2.4.5
On November 11th, we upgraded our
Have your Expirations been running successfully?
David Longo
>>> [EMAIL PROTECTED] 01/25/06 2:05 PM >>>
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
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
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.
10 matches
Mail list logo
