Hi *,
Does anyone know what the maximum size database is for TSM 5.4 and TSM 5.5 ? We
were told by IBM when we were at TSM 5.3 that 120Gb was the limit and was
wondering what the limit is for 5.4 and 5.5.
Currently running TSM 5.4.3.0 on AIX 5.3 TL 9.
Rich
I believe the limit is somewhere around 600GB or so.
I have TSM 5.5 on AIX and my DB is 200GB, it was on 5.4 also.
David Longo
Richard Mochnaczewski richard.mochnaczew...@standardlife.ca 11/10/2009
11:34 AM
Hi *,
Does anyone know what the maximum size database is for TSM 5.4 and TSM 5.5 ?
-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM DB Size
Hi *,
Does anyone know what the maximum size database is for TSM 5.4 and TSM 5.5 ? We
were told by IBM when we were at TSM 5.3 that 120Gb was the limit and was
wondering what the limit is for 5.4 and 5.5.
Currently running TSM 5.4.3.0 on AIX 5.3 TL
91.1
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Richard Mochnaczewski
Sent: Tuesday, November 10, 2009 11:35 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM DB Size
Hi *,
Does anyone know what the maximum size database is for TSM
The Admin Guide manual says that the maximum size for the db is 530 GB.
] TSM DB Size
We have DB's over 190 Gb in 5.5, on AIX servers:
TSM_Server CAP_GB MAX_EXT_GB PCT_UTIL MAX_UTIL
--- --- --
AIXPRODXYZ 191.95 0.00 89.4 89.4
AIXPRODDMZ 219.76 4.17
] On Behalf Of
Richard Sims
Sent: Tuesday, November 10, 2009 9:47 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM DB Size
The Admin Guide manual says that the maximum size for the db is 530 GB.
We had a health check done by IBM when we were at TSM 5.3 and were told
they don't recommend a DB size higher than 120Gb for performance and
restore purposes.
Rich
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Kelly Lipp
Sent: Tuesday
On Nov 10, 2009, at 11:48 AM, Kelly Lipp wrote:
I stand corrected, as usual, by Richard! 500, 530, big diff.
Nope... by IBM - a much higher authority! ;-)
Note that the SHow LVMFA command will also reveal the maximum size
(see the reported Maximum possible DB LP Table size.)
R.
11:51 AM
Please respond to
ADSM-L@VM.MARIST.EDU
To
ADSM-L
cc
Subject
Re: [ADSM-L] TSM DB Size
We had a health check done by IBM when we were at TSM 5.3 and were told
they don't recommend a DB size higher than 120Gb for performance and
restore purposes.
Rich
-Original Message
-5424 / Toll Free: (866) 796-9226
Cell: (314) 750-8721
Original Message
Subject: Re: [ADSM-L] TSM DB Size
From: Richard Mochnaczewski richard.mochnaczew...@standardlife.ca
Date: Tue, November 10, 2009 10:51 am
To: ADSM-L@VM.MARIST.EDU
We had a health check done by IBM when we
STORServer solves your data backup challenges.
Once and for all.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Shawn
Drew
Sent: Tuesday, November 10, 2009 10:10 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM DB Size
100-120GB was the IBM
On 10 nov 2009, at 19:03, Kelly Lipp wrote:
And most importantly, if you get a room full of TSM gurus, IBM types
and folks like us, nobody will really agree on a hard number.
there is a hard number 530 :) Now as for recommendations
that's a totally different story.
What I have seen
data backup challenges.
Once and for all.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On
Behalf Of Shawn Drew
Sent: Tuesday, November 10, 2009 10:10 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM DB Size
100-120GB was the IBM recommended limit
Dear Duane,
we currently face the same problem, as we had to expand one of our
databases beyond the limit we had set and cannot shrink it now. Short of
taking the System offline for dump and load of the database, we are going
to restore the database to another TSM instance and do the dump and
Good Day all,
About a month ago, I was prepping to split a TSM DB because it was growing out
of control after the addition of a number of remote imaging sites. After much
review I was able to find failures in the expiration process. I tracked it down
to a single client and after a call to IBM
Shawn Drew
Internet
duane.o...@qg.com
Sent by: ADSM-L@VM.MARIST.EDU
07/01/2009 03:31 PM
Please respond to
ADSM-L@VM.MARIST.EDU
To
ADSM-L
cc
Subject
[ADSM-L] DB size and expiration
Good Day all,
About a month ago, I was prepping to split a TSM DB because it was growing
out
Manager [mailto:ads...@vm.marist.edu] On Behalf Of Ochs,
Duane
Sent: Wednesday, July 01, 2009 2:31 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] DB size and expiration
Good Day all,
About a month ago, I was prepping to split a TSM DB because it was growing out
of control after the addition of a number
Have DB with size of 31,440 MB. Attempting to
load a copy of the database on my recovery
system. DB is 53% full.
Available Assigned Maximum MaximumPage Total Used
Pct Max.
Space Capacity Extension ReductionSizeUsable Pages Util
Pct
(MB) (MB)
The answer is yes, the exact why however, will have to be answered by someone
else. I believe it has to do with the DB design and TSM will only recognize
the actual last recorded DB size, not the last utilized size.
Ryan Miller
Storage Solutions Engineer
MSI Systems Integrators
2600 Westown
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777
[EMAIL PROTECTED]
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Tim Brown
Sent: Wednesday, December 12, 2007 12:48 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] DB size for recovery
Wiadomosc przeskanowana programem antywirusowym. Nie znaleziono wirusow /
This message was anti-virus scanned. No viruses were found.
Hi
I have problem with DB size. Now it's 114 GB (with 18 Windows Server
clients). My policy parameters are:
Version Data Exist: Nolimit
Version Data Deleted
Hi,
You have to go into unloading and reloading the database.
Regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Szymon Kacprzak
Sent: donderdag 19 oktober 2006 10:18
To: ADSM-L@VM.MARIST.EDU
Subject: DB size problem
Wiadomosc
On Oct 19, 2006, at 4:17 AM, Szymon Kacprzak wrote:
I have problem with DB size. Now it's 114 GB (with 18 Windows Server
clients). My policy parameters are:
Version Data Exist: Nolimit
Version Data Deleted: Nolimit
Retain Extra Ver.: 7
Retain Only Ver.: 7
Your backup retentions are tiny, so
Hi,
Can any one suggest what should be a recovery log and db size for the
135TB backup with retention of 90 days?
Regards
Pranav Parikh
Branch Manager - Customer Service
Ontrack Solutions Pvt. Ltd.
Baroda
TeleFax: 91-265-2324730/2324731
Visit Us: www.ontrackin.com
Hi,
Can any one suggest what should be a recovery log and db size for the
135TB backup with retention of 90 days?
I think this depends on the number of files and the number of backup copies.
--
Regards,
Dirk Kastens
Universitaet Osnabrueck, Rechenzentrum (Computer Center)
Albrechtstr. 28
: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Pranav Parikh
Sent: Thursday, 16 March, 2006 11:21
To: ADSM-L@VM.MARIST.EDU
Subject: TSM DB SIZE
Hi,
Can any one suggest what should be a recovery log and db size for the
135TB backup with retention of 90 days?
Regards
Pranav Parikh
Thanks Arnaud.
Regards
Pranav
PAC Brion Arnaud [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
03/16/2006 04:41 PM
Please respond to ADSM: Dist Stor Manager
To: ADSM-L@VM.MARIST.EDU
cc:
Subject:Re: [ADSM-L] TSM DB SIZE
Pranav
I currently have a 60GB TSM database mirrored for a total of 120GB (also
including Recovery logs 5 GB each 10GB total). I have heard that this is
big for 1 Server and would like to ask if other TSMers split their Servers
and what is the rule of thumb. It took 8 hours to restore DB at DR vs the
4
From: William Rosette [mailto:[EMAIL PROTECTED]]
I currently have a 60GB TSM database mirrored for a total of
120GB (also including Recovery logs 5 GB each 10GB total). I
have heard that this is big for 1 Server and would like to
ask if other TSMers split their Servers and what is the
Hi all,
Ive problems with dumpdb and loaddb
I have so many dbvol and so many log vol and wanted to make it to be only
one dbvol and one logvol
My dbsize is 3304M which actually use only 67.1% of it
My logsize is 824 which also use less
Ive create newdbvol 3500M and logvol 1200M
Got error as
Consolidation
on 2 of our servers.
During this consolidation effort I had noticed that
our DB size has grown
from a concerning value of 64.7% to an alarming
72.5% over a period of about
1 week.
Granted I understand that during the reorg that
there are going to be
multiple files and directories
Recently we have gone through a Server Consolidation
on 2 of our servers.
During this consolidation effort I had noticed that
our DB size has grown
from a concerning value of 64.7% to an alarming
72.5% over a period of about
1 week.
Have you taken into account your backup copy group
Hello All,
Recently we have gone through a Server Consolidation on 2 of our servers.
During this consolidation effort I had noticed that our DB size has grown
from a concerning value of 64.7% to an alarming 72.5% over a period of about
1 week.
Granted I understand that during the reorg
Hello all,
I have TSM 4.1 for OS/390. I have allocated 3000 cylinders, roughly a
volume, for the TSM database and currently I am at 90% utilization with a
few large client nodes left to get the initial backup. I am considering
using BMC's Data Accelerator/Compression or would it be better to just
PROTECTED]
-Original Message-
From: Coles, Peter [mailto:[EMAIL PROTECTED]]
Sent: 11 January 2001 16:01
To: [EMAIL PROTECTED]
Subject: TSM 4.1 for OS/390 DB size
Sensitivity: Private
Hello all,
I have TSM 4.1 for OS/390. I have allocated 3000 cylinders, roughly a
volume, for the TSM database
PROTECTED]
Internet: http://www.abraxas.ch
-Ursprngliche Nachricht-
Von: Coles, Peter [mailto:[EMAIL PROTECTED]]
Gesendet am: Donnerstag, 11. Januar 2001 17:01
An: [EMAIL PROTECTED]
Betreff: TSM 4.1 for OS/390 DB size
Vertraulichkeit: Privat
37 matches
Mail list logo
