PROTECTED] En nombre de
Richard Rhodes
Enviado el: Viernes, 05 de Diciembre de 2008 18:25
Para: ADSM-L@VM.MARIST.EDU
Asunto: Re: [ADSM-L] Database size, Split to multiple instances or wait for
version 6.1
We recently had a meeting with IBM where they told us that v6.1 will be
announced at some big IBM
I heard December 8th was going to be the GA release of this.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Rhodes
Sent: Friday, December 05, 2008 3:25 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Database size, Split to multiple
Subject
.EDU> Re: Database size, Split to
multiple instances or wait for
version 6.1
12/05/2008 01:24
PM
Please respond to
No, DS4500. We got off of SSA years ago. The 15K made a huge difference
for us.
At 01:10 PM 12/5/2008, Allen S. Rout wrote:
>> On Thu, 4 Dec 2008 18:50:23 -0500, Paul Zarnowski <[EMAIL PROTECTED]> said:
> We also have 15K rpm 36GB drives, in two mirrored RAID5,7 sets (TSM
> mirroring).
Is t
d.
Jeremy
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Paul Zarnowski
Sent: Thursday, December 04, 2008 5:50 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Database size, Split to multiple instances or wait
for version 6.1
Interesting.. we have
Is this true in regards to TSM V6.1? Also Is it due out in Jan-Feb?
The biggest single change will the conversion of the database to DB2, or
UDB as it is often called these days. This will be a packaged DB2
version that will not need any maintenance by your DBAs. The DB2
database will permit the
>> On Thu, 4 Dec 2008 18:50:23 -0500, Paul Zarnowski <[EMAIL PROTECTED]> said:
> We also have 15K rpm 36GB drives, in two mirrored RAID5,7 sets (TSM
> mirroring).
Is that SSA? I thought you were still on that.
- Allen S. Rout
On Dec 4, 2008, at 18:53 , Zoltan Forray/AC/VCU wrote:
Are you mis-reading/writing that info?350GB takes 1-hour to
expire and
about the same to backup??
My 190GB DB used to take 48+ hours to run expire (350M objects) and
2-hours for a full backups! With recent cleanup/load balancing by
mov
, since those are the only
two I know that can go this fast
Regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of
Conradt, Jeremy
Sent: donderdag 4 december 2008 17:19
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Database size, Split to
y, December 04, 2008 10:45 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Database size, Split to multiple instances or wait
for version 6.1
Ok, 350GB tsm db backing up in 1 hour? How did you get it that fast?
Regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL
Regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of
Conradt, Jeremy
Sent: donderdag 4 december 2008 17:19
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Database size, Split to multiple instances or wait for
version 6.1
Expiration takes about 1 hour
DSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Bos, Karel
Sent: Thursday, December 04, 2008 10:45 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Database size, Split to multiple instances or wait
for version 6.1
Ok, 350GB tsm db backing up in 1 hour? How did you get it that f
t 1 hour 15 minutes.
>
> Thanks,
> Jeremy
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
> Wanda Prather
> Sent: Wednesday, December 03, 2008 7:01 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Database size, S
-hours.
"Conradt, Jeremy" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
12/04/2008 11:28 AM
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: [ADSM-L] Database size, Split to multiple instances or wait for
version 6.1
Ok, 350GB tsm db backing up in 1 hour? How did you get it that fast?
Regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Conradt, Jeremy
Sent: donderdag 4 december 2008 17:19
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Database size, Split
] Database size, Split to multiple instances or wait
for version 6.1
How long does it take you now to do Expiration and DB backup?
On Wed, Dec 3, 2008 at 4:24 PM, Conradt, Jeremy <
[EMAIL PROTECTED]> wrote:
> I have a TSM server currently running version 5.3.5 on Windows 2003
> that we pla
We exported from a SUN E4800 to an IBM p570, both having 8 LTO3 drives
attached, while both were still fully functioning as fileservers and
backup servers. We moved around 2TB/24 hours, took several(5-6 maybe)
months to move 250+TB. We did not tune everything for absolute speed.
--Bill
From: A
How long does it take you now to do Expiration and DB backup?
On Wed, Dec 3, 2008 at 4:24 PM, Conradt, Jeremy <
[EMAIL PROTECTED]> wrote:
> I have a TSM server currently running version 5.3.5 on Windows 2003 that
> we plan to upgrade soon.
> The problem I have is our database has grown to 350 G
One thing to consider is that migrating that large of a database to TSM 6.1
(DB2) may take a loong time. We have a large, old, database as well, and I
am concerned about the amount of time it will take. Time will tell. But
having smaller databases will definitely shorten the migration time for
I have a TSM server currently running version 5.3.5 on Windows 2003 that
we plan to upgrade soon.
The problem I have is our database has grown to 350 GB.
The question I have is will version 6.1 of TSM be better capable of
maintaining a database this size and much larger or should I break it
apa
Hi All,
Thank you all for your input on this.
As the Buffer Pool Cache Hit % and expiration all under control, I feel
comfortable to grow the Database size above 80GB. But, bearing in mind
that some day I may need to run database reorganization, I will prefer
keeping the size under 120GB
straining. :-D (72 GB)
Hope This helps.
See Ya'
Howard
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
> Of Patel, Ankur
> Sent: Thursday, August 28, 2008 8:44 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] T
Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Pahari, Dinesh P
Sent: Friday, 29 August 2008 11:37 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM database size?
Hi All,
I have got a TSM server with the 80GB database size. It is already
utilized above 80%. Could someone please let me know, what
s however a rounded figure.The actual maximum
>> size of the database is 543184 MB, which equates to about 530.5 GB.
>>
>>
>>
>>
>> Regards,
>>
>>
>>
>> Ankur Patel
>> TSM Administrator
>>
>>
>> -Original Messag
>
>
> Regards,
>
>
>
> Ankur Patel
> TSM Administrator
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
> Pahari, Dinesh P
> Sent: Friday, 29 August 2008 11:37 AM
> To: ADSM-L@VM.MARIST.EDU
: Friday, 29 August 2008 11:37 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM database size?
Hi All,
I have got a TSM server with the 80GB database size. It is already
utilized above 80%. Could someone please let me know, what is the exact
recommended database size by IBM? Any links with such i
Hi All,
I have got a TSM server with the 80GB database size. It is already
utilized above 80%. Could someone please let me know, what is the exact
recommended database size by IBM? Any links with such information would
be good.
Kind Regards,
Dinesh Pahari
the setup of a 10 Gb Ethernet network.
Orville L. Lantto
From: ADSM: Dist Stor Manager on behalf of Tom Melton
Sent: Wed 9/5/2007 12:48
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM Database Size
I have done a few searches, but have not found anything
>> On Wed, 5 Sep 2007 13:48:34 -0400, Tom Melton <[EMAIL PROTECTED]> said:
> IBM P650 Server 8-way 16 GB
> AIX 5.3
> TSM 5.2.2
> 2 fibre channel paths to disk
> 4 fibre paths to 8 - 3592 tape drives
> 2 scsi paths to 6 - 3590 tape drives
> 60 GB database size
I have done a few searches, but have not found anything conclusive. I
am interested in finding database/performance size limits, not maximum
database size.
My TSM system is on AIX configured as follows:
IBM P650 Server 8-way 16 GB
AIX 5.3
TSM 5.2.2
2 fibre channel paths to disk
4 fibre paths to
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
To: ADSM-L@VM.MARIST.EDU
Sent: Thu Jan 26 03:20:26 2006
Subject: Re: TSM Database Size Growing
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.
Luke wrote, in part..
> Is there a way to identify how the addition of a node affects the
> TSM database size? I can capture the number of files and the amount of
> data that each additional node adds to the TSM server, but what I'm
> really looking for is a way to separate
PROTECTED]
Luke Dahl <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 07/16/2001 06:01:29 PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Database S
Hello Again,
Is there a way to identify how the addition of a node affects the
TSM database size? I can capture the number of files and the amount of
data that each additional node adds to the TSM server, but what I'm
really looking for is a way to separate how a particular node affect
25 AM
To: [EMAIL PROTECTED]
Subject:Re: TSM Database Size
>Is there a preferred db volume size for TSM for optimal
performance.
Richard - Not really. Optimal performance derives from spreading
the
I/O load over multiple db volumes (mult
>Is there a preferred db volume size for TSM for optimal performance.
Richard - Not really. Optimal performance derives from spreading the
I/O load over multiple db volumes (multiple TSM threads)
and multiple real I/O paths - as well as keeping as much as possible
in real memory. Many
Is there a preferred db volume size for TSM for optimal performance. I am
currently making my database volumes in 2GB increments my database is 20GB
in total.
Thanks
***EMAIL DISCLAIMER**
This e-mail and any files transmitted with it may be confid
6,924 0 4,096 4,503,552 1,519,259 33.7
33.8
-Original Message-
From: Marco Supino [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 16, 2001 6:55 AM
To: [EMAIL PROTECTED]
Subject: Database Size
Hello.
I would like to know from some of you what is the Database size, and how
many
Hello.
I would like to know from some of you what is the Database size, and how
many pages does it contain ? i want to see if my Database is not normal
by size.
Thanks.
Marco.
begin:vcard
n:Supino;Marco
tel;cell:972-54-983653
tel;fax:972-9-9509118
tel;work:972-9-9708721
x-mozilla-html:FALSE
Steffan,
A full db backup takes about 8 hours. I have a 9672-ra6 processor (80 mips),
escon channels to 9840 stk drives. The db is on an STK SVA disk subsystem.
I tested a restore when the db was 80 GB, going to another empty instance
of tsm. It took about 24 hrs. which includes anrfmt jobs o
Bill,
how quickly does your 121GB db backup & restore? How long does reclamation
run?
Steffan
At 12:52 PM 4/3/2001 -0400, you wrote:
>David - I am running tsm 3.7.4 on os/390 r6. I do have a much bigger
>database.
>It has continued to perform well. Here is a 'q bd' --
>adsm> q db f=d
>
>
iginal Message-
>From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
>Bill Colwell
>Sent: Tuesday, April 03, 2001 10:53 AM
>To: [EMAIL PROTECTED]
>Subject: Re: ADSM concern on Database size.
>David - I am running tsm 3.7.4 on os/390 r6. I do have
: [EMAIL PROTECTED]
Subject: Re: ADSM concern on Database size.
David - I am running tsm 3.7.4 on os/390 r6. I do have a much bigger
database.
It has continued to perform well. Here is a 'q bd' --
adsm> q db f=d
Available Space (MB): 121,888
Assigned Capacity
David - I am running tsm 3.7.4 on os/390 r6. I do have a much bigger database.
It has continued to perform well. Here is a 'q bd' --
adsm> q db f=d
Available Space (MB): 121,888
Assigned Capacity (MB): 121,888
Maximum Extension (MB): 0
Maximum Reduction (MB):
age d'origine-
> De : David Browne. [mailto:[EMAIL PROTECTED]]
> Envoyé : mardi 3 avril 2001 17:14
> À : [EMAIL PROTECTED]
> Objet : ADSM concern on Database size.
>
>
> One of our ADSM databases runs on OS/390 2.10 and is 44GB.
> Does anybody have a recommend
One of our ADSM databases runs on OS/390 2.10 and is 44GB.
Does anybody have a recommendation for how big you should let the database
get?
Does anyone have one on OS/390 that's much bigger?
Is there a limit on the size?
I'm concerned about the length of time it would take to recover.
Are there
There really is no practical limit to the size of the DB. However you
will want to take into consideration things like DB backup times, and the
times needed to perform a recovery incase of an error or failure of the
server platform. Also there is the old sang "Don't put all your eggs in
one bask
All,
I'm running TSM 3.1.2.22. Will be upgrading to 3.7 soon. The question
is.
Our TSM database is currently allocated at 41gb. The percent utilized is
60%.
We will be adding many new nodes in the near future. As many as 6000
over the next few months. I know adding these node will increase the
s
Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Backup aaccount
Sent: Friday, October 13, 2000 6:18 AM
To: [EMAIL PROTECTED]
Subject: TSM Database Size
We are currently expereincing some slowdown on our nightly backups.
Here is my envronment:
Windows NT Server 4
>We are currently expereincing some slowdown on our nightly backups.
Well, you're quoting an effect and then immediately looking at your
database. Anyone running a server system, for any kind of service,
needs to be routinely running operating system performance monitoring
and tracking utilities
We are currently expereincing some slowdown on our nightly backups.
Here is my envronment:
Windows NT Server 4.0
Compaq Proliant Quad Xeon 450 512 MB RAM
TSM 3.7.3.6
150 GB Hard Disk Array
4 drive AIT-2 ADIC Scalar 1000
Our Current DB is 40% of 30GB.
We backup roughly 120 GB each night from abou
Toni Banire <[EMAIL PROTECTED]> wrote, in part..
> I am trying to work out the size of a TSM database ...
...
> versions kept = 130
...
Just because 130 versions can be kept, doesn't mean 130 versions of
all files *will* be kept, just that if you "expire inventory" now and again,
a maximum of 130
>The admin guide for ADSM says add 50% to the initial size of the database
>with TSM 3.7 it says to add 135% to the initial size
The ADSM 3.1 Admin Guide says "Overhead could increase the required space
up to an additional 25%". (page 351)
The TSM 4.1 Admin Guide says "Overhead could require up
For starters, 130 is a LOT of versions to keep.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Toni Banire
Sent: Tuesday, September 05, 2000 11:33 AM
To: [EMAIL PROTECTED]
Subject: Database size query
Just to make sure i'm on the right tra
The admin guide for ADSM says add 50% to the initial size of the database
with TSM 3.7 it says to add 135% to the initial size
Has anyone noticed this, does this seem right
Toni
Just to make sure i'm on the right track
I am trying to work out the size of a TSM database according to the TSM concepts
guide which is the total no. of files being backed up * versions kept * 600B
*135% (for overhead and growth).
No of files = 234333
versions kept = 130
234333*130 = 304632
65 matches
Mail list logo
