The reason for moving to only one instance, is the management question. Managing two instances is twice the work than managing only one instance. Also, the process for stgpool backup and migration is two processes instead of one.
Another reason is that the customer wants to consolidate the libraries, running the primary tape pool in the STK9310, and holding the copypool in the 3494 library. This means will have to move the primary data from the 3494 any way.
The database isn't that large, about 18GB on the first server, and 20GB on the second server.
This platform has been running for 4 years, without an unload, so my guess is that the database will shrink with about 25-40% if an unload is done. In this case, the database will become managable.
However, moving both instances to the new server(HACMP P-Series 660 fail-over cluster) is a backup plan. This will mean that will have to change TCPPorts on about 200 clients.
Then, after moving both instances, will start doing export node, until one of the instances no longer have any clients. When that happens, we can remove that instance, and only have one instance. This is a time consuming way of doing it.
Moving all data is not an option, as this would take 1-2 weeks to complete.
-----------------------------------
Daniel Sparrman
Exist i Stockholm AB
Propellervägen 6B
183 62 HÄGERNÄS
Växel: 08 - 754 98 00
Mobil: 070 - 399 27 51
-----"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote: -----
To: ADSM-L AT VM.MARIST DOT EDU
From: Zlatko Krastev <acit AT ATTGLOBAL DOT NET>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Date: 04/25/2002 10:39PM
Subject: Re: Consolidating TSM servers.
Daniel,
is there any specific reason not to consolidate using two TSM server
instances within one very powerful box.
From what I've learned from this list others are splitting a server when
database becomes too large for performance and manageability reasons. You
can still use same STK silo or 3494 from both instances.
How large are the databases if they hold metadata for those 31TB? Have you
evaluated the possibility so consolidated instance to become too huge and
for any reasons you to be forced to split it?
The simple question to not so simple answer - AFAIK you cannot import
only the database and use the volumes. The complex answer - have you
evaluated any other options or you are forced to go that way?
Zlatko Krastev
IT Consultant
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Consolidating TSM servers.
Hi
Anybody out there know if it's possible to do a export server, without
having to export all filedata, and then do a import and use the existing
tapes.
We have one STK 9310 and one IBM 3494. Each TSM server has a copypool and
a primary tape pool in the different libraries. All equipment is SAN
connected, so if I could first do a DB backup/restore to the new machine
of one of the TSM servers, and then export everything except for the file
data from the second TSM server to the new machine, it would be perfect.
Doing a export server filedata=all, would create about 1500 new tapes,
according to a export server preview=yes (about 31TB of data) and this
would probbaly not work at all.
So, anybody done this before?
Best Regards
Daniel Sparrman
-----------------------------------
Daniel Sparrman
Exist i Stockholm AB
Propellervägen 6B
183 62 HÄGERNÄS
Växel: 08 - 754 98 00
Mobil: 070 - 399 27 51
