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 load
I am not sure shrinking the amount of disk space used by the DB will be worth
the time. TSM will use the pages in the DB, even if they are not at the end.
You will still have to add new disks at the same point in the future.
Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manage
Provide a "q db f=d" output.
Also, might want to do a "ESTimate DBREorgstats" for more information.
But yes, most likely an unloaddb, loaddb is your only option (other than
upgrading to 6.1, which is supposed to let you optimize while running)
Regards,
Shawn
_
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 Pa
Yes. Just because is probably the best answer. It has to do with the
way the db structure is laid out originally. If you were to reduce the
database on the original system before you do the backup, then you could
restore into a smaller database...
Kelly J. Lipp
VP Manufacturing & CTO
STORServ
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 o
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 prz
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
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
>> 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 cop
It depends on how much data was on the old servers and
that now appears on the consolidated server as well as
how much capacity you have assigned for your db. My
experience as a consultant in dealing with this issue
is that there is either a lot of data on the new
server or there isn't a lot of c
11 matches
Mail list logo
