Re: Consolidating TSM servers.
Hi 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.Thanks for the suggestions Best Regards Daniel Sparrman---Daniel SparrmanExist i Stockholm ABPropellervägen 6B183 62 HÄGERNÄSVäxel: 08 - 754 98 00Mobil: 070 - 399 27 51-"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote: -To: [EMAIL PROTECTED]From: Zlatko Krastev <[EMAIL PROTECTED]>Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>Date: 04/25/2002 10:39PMSubject: 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 KrastevIT ConsultantPlease respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>To: [EMAIL PROTECTED]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 SparrmanExist i Stockholm ABPropellervägen 6B183 62 HÄGERNÄSVäxel: 08 - 754 98 00Mobil: 070 - 399 27 51
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" <[EMAIL PROTECTED]> Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] 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
Re: Consolidating TSM servers.
Daniel,
No, I don't believe there is any way to accomplish your specific request. I
know of no supported method to move the file and volume metadata from one
TSM instance into another without also moving the data.
If your goal is to get to a single hardware platform, you can create a
second instance of TSM on the new machine and leave the old data on the
3494.
I expect, however, that your goal is to get all the clients into a single
instance of TSM? If so, I believe you will have to move the files.
Using the second instance will allow you to retire the old machine quickly,
if that is important. But it's pay me now or pay me later.
Bill SmoldtSSSI
STORServer, Inc.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Daniel Sparrman
Sent: Thursday, April 25, 2002 2:56 AM
To: [EMAIL PROTECTED]
Subject: Re: Consolidating TSM servers.
Hi
The problem isn't moving only one TSM server, but consolidating two TSM
servers into one.
I have no problems moving the first TSM server(ADSM1) to the new hardware.
However, I want to migrate the second TSM server(ADSM2) to the new
hardware/TSM server(TSM1). There are two choices for doing this, either
exporting all nodes using export node option. This will generate alot of
tapes, as the smallest ADSM server has 200 nodes, 1500 tapes and a total
storage of 30TB. However, I can choose not to export the copypools, which
would make it about 15TB of data and 750 tapes.
The other option is to do a export server. This command has a filedata=
feature, and what I would like to do is to do a export server
filedata=none, and then import this information into the new TSM server.
The new TSM server will have access through ACSLS/3494 CU to all existing
volumes from both old ADSM servers. Therefore, I wouldn't have to export
all the filedata, only definitions.
My question is, is it possible to do a export server filedata=none, and
then import this information into the new server, connect both the 3494
and the STK9310 to the new server, and use the old volumes that contains
data and already exists in the 3494/STK9310.
This would save me 3-4 days, because that is what it would take to move
15TB of data from the 3494 to the 9310 using import/export commands.
Or, do I have to do export/import of all filedata, because doing
filedata=none, will only import node definitions, and not storage volume
definitions?
Best Regards
Daniel Sparrman
---
Daniel Sparrman
Exist i Stockholm AB
Propellervdgen 6B
183 62 HDGERNDS
Vdxel: 08 - 754 98 00
Mobil: 070 - 399 27 51
"Don France (TSMnews)" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
2002-04-23 08:45
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: Consolidating TSM servers.
If you stay on the same platform-OS, all you need to do is shutdown (old
server) after a final DB backup, move the HW connections to the new
server, restore DB, and you're finished. Remember to copy the dsmserv.dsk
(filesystems for all TSM server files -- db, log, disk pool vols, logical
volumes, path-names), as well as volhist, devcfg and dsmserv.opt;
move/re-org filesystems *after* the move. Many other posts confirm this
approach, have personally done it on AIX since v2 days.
Regards,
Don France
Technical Architect - Tivoli Certified Consultant
Professional Association of Contract Employees (P.A.C.E.)
San Jose, CA
(408) 257-3037
[EMAIL PROTECTED]
- Original Message -
From: Daniel Sparrman
To: [EMAIL PROTECTED]
Sent: Monday, April 22, 2002 12:59 PM
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
Propellervdgen 6B
183 62 HDGERNDS
Vdxel: 08 - 754 98 00
Mobil: 070 - 399 27 51
Re: Consolidating TSM servers.
Hi
The problem isn't moving only one TSM server, but consolidating two TSM
servers into one.
I have no problems moving the first TSM server(ADSM1) to the new hardware.
However, I want to migrate the second TSM server(ADSM2) to the new
hardware/TSM server(TSM1). There are two choices for doing this, either
exporting all nodes using export node option. This will generate alot of
tapes, as the smallest ADSM server has 200 nodes, 1500 tapes and a total
storage of 30TB. However, I can choose not to export the copypools, which
would make it about 15TB of data and 750 tapes.
The other option is to do a export server. This command has a filedata=
feature, and what I would like to do is to do a export server
filedata=none, and then import this information into the new TSM server.
The new TSM server will have access through ACSLS/3494 CU to all existing
volumes from both old ADSM servers. Therefore, I wouldn't have to export
all the filedata, only definitions.
My question is, is it possible to do a export server filedata=none, and
then import this information into the new server, connect both the 3494
and the STK9310 to the new server, and use the old volumes that contains
data and already exists in the 3494/STK9310.
This would save me 3-4 days, because that is what it would take to move
15TB of data from the 3494 to the 9310 using import/export commands.
Or, do I have to do export/import of all filedata, because doing
filedata=none, will only import node definitions, and not storage volume
definitions?
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
"Don France (TSMnews)" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
2002-04-23 08:45
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: Consolidating TSM servers.
If you stay on the same platform-OS, all you need to do is shutdown (old
server) after a final DB backup, move the HW connections to the new
server, restore DB, and you're finished. Remember to copy the dsmserv.dsk
(filesystems for all TSM server files -- db, log, disk pool vols, logical
volumes, path-names), as well as volhist, devcfg and dsmserv.opt;
move/re-org filesystems *after* the move. Many other posts confirm this
approach, have personally done it on AIX since v2 days.
Regards,
Don France
Technical Architect - Tivoli Certified Consultant
Professional Association of Contract Employees (P.A.C.E.)
San Jose, CA
(408) 257-3037
[EMAIL PROTECTED]
- Original Message -
From: Daniel Sparrman
To: [EMAIL PROTECTED]
Sent: Monday, April 22, 2002 12:59 PM
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
Re: Consolidating TSM servers.
There is no way (AFAIK), to export/import the database information only, without exporting/importing the data. This is a major deficiency of TSM, which not only occurs when consolidating TSM servers, but also when consolidating TSM clients: When transfering a huge filespace from one client to another, you essentially run into the same problem, even if the TSM server remains the same. The ability to export/import the database information for - the whole TSM server - a specific client - a specific filespace of a specific node without exporting/importing the data itself, would help. Reinhard Daniel Sparrman <[EMAIL PROTECTED]> schrieb: > Hi > The problem isn't moving only one TSM server, but consolidating two TSM > servers into one. > I have no problems moving the first TSM server(ADSM1) to the new hardware. > However, I want to migrate the second TSM server(ADSM2) to the new > hardware/TSM server(TSM1). There are two choices for doing this, either > exporting all nodes using export node option. This will generate alot of > tapes, as the smallest ADSM server has 200 nodes, 1500 tapes and a total > storage of 30TB. However, I can choose not to export the copypools, which > would make it about 15TB of data and 750 tapes. > The other option is to do a export server. This command has a filedata= > feature, and what I would like to do is to do a export server > filedata=none, and then import this information into the new TSM server. > The new TSM server will have access through ACSLS/3494 CU to all existing > volumes from both old ADSM servers. Therefore, I wouldn't have to export > all the filedata, only definitions. > My question is, is it possible to do a export server filedata=none, and > then import this information into the new server, connect both the 3494 > and the STK9310 to the new server, and use the old volumes that contains > data and already exists in the 3494/STK9310. > This would save me 3-4 days, because that is what it would take to move > 15TB of data from the 3494 to the 9310 using import/export commands. > Or, do I have to do export/import of all filedata, because doing > filedata=none, will only import node definitions, and not storage volume > definitions? > 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 > "Don France (TSMnews)" <[EMAIL PROTECTED]> > Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > 2002-04-23 08:45 > Please respond to "ADSM: Dist Stor Manager" > To: [EMAIL PROTECTED] > cc: > Subject:Re: Consolidating TSM servers. > If you stay on the same platform-OS, all you need to do is shutdown (old > server) after a final DB backup, move the HW connections to the new > server, restore DB, and you're finished. Remember to copy the dsmserv.dsk > (filesystems for all TSM server files -- db, log, disk pool vols, logical > volumes, path-names), as well as volhist, devcfg and dsmserv.opt; > move/re-org filesystems *after* the move. Many other posts confirm this > approach, have personally done it on AIX since v2 days. > Regards, > Don France > Technical Architect - Tivoli Certified Consultant > Professional Association of Contract Employees (P.A.C.E.) > San Jose, CA > (408) 257-3037 > [EMAIL PROTECTED] > - Original Message - > From: Daniel Sparrman > To: [EMAIL PROTECTED] > Sent: Monday, April 22, 2002 12:59 PM > 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 -- Reinhard MerschWestfaelische Wilhelms-Universitaet Zentrum fuer Informationsverarbeitung - ehemals Universitaetsrechenzentrum Roentgenstrasse 9-13, D-48149 Muenster, Germany Tel: +49(251)83-31583 E-Mail: [EMAIL PROTECTED] Fax: +49(251)83-31653
Re: Consolidating TSM servers.
If you stay on the same platform-OS, all you need to do is shutdown (old server) after a final DB backup, move the HW connections to the new server, restore DB, and you're finished. Remember to copy the dsmserv.dsk (filesystems for all TSM server files -- db, log, disk pool vols, logical volumes, path-names), as well as volhist, devcfg and dsmserv.opt; move/re-org filesystems *after* the move. Many other posts confirm this approach, have personally done it on AIX since v2 days. Regards, Don France Technical Architect - Tivoli Certified Consultant Professional Association of Contract Employees (P.A.C.E.) San Jose, CA (408) 257-3037 [EMAIL PROTECTED] - Original Message - From: Daniel Sparrman To: [EMAIL PROTECTED] Sent: Monday, April 22, 2002 12:59 PM 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
Re: Consolidating TSM servers.
=> On Mon, 22 Apr 2002 21:59:45 +0200, Daniel Sparrman <[EMAIL PROTECTED]> said: > From: Daniel Sparrman <[EMAIL PROTECTED]> > Subject: Consolidating TSM servers. > To: [EMAIL PROTECTED] > PEZPTlQgZmFjZT0iRGVmYXVsdCBTYW5zIFNlcmlmLCBWZXJkYW5hLCBBcmlhbCwgSGVsdmV0aWNh > LCBzYW5zLXNlcmlmIiBzaXplPTI+PERJVj5IaTwvRElWPjxESVY+Jm5ic3A7PC9ESVY+PERJVj5B > bnlib2R5IG91dCB0aGVyZSBrbm93IGlmIGl0J3MgcG9zc2libGUgdG8gZG8gYSBleHBvcnQgc2Vy > dmVyLCB3aXRob3V0IGhhdmluZyB0byBleHBvcnQgYWxsIGZpbGVkYXRhLCBhbmQgdGhlbiBkbyBh > IGltcG9ydCBhbmQgdXNlIHRoZSBleGlzdGluZyB0YXBlcy48L0RJVj48RElWPiZuYnNwOzwvRElW > PjxESVY+V2UgaGF2ZSBvbmUgU1RLIDkzMTAgYW5kIG9uZSBJQk0gMzQ5NC4gRWFjaCBUU00gc2Vy > dmVyIGhhcyBhIGNvcHlwb29sIGFuZCBhIHByaW1hcnkgdGFwZSBwb29sIGluIHRoZSBkaWZmZXJl > bnQgbGlicmFyaWVzLiBBbGwgZXF1aXBtZW50IGlzIFNBTiBjb25uZWN0ZWQsIHNvIGlmIEkgY291 > bGQgZmlyc3QgZG8gYSBEQiBiYWNrdXAvcmVzdG9yZSB0byB0aGUgbmV3IG1hY2hpbmUgb2Ygb25l > IG9mIHRoZSBUU00gc2VydmVycywgYW5kIHRoZW4gZXhwb3J0IGV2ZXJ5dGhpbmcgZXhjZXB0IGZv > ciB0aGUgZmlsZSBkYXRhIGZyb20gdGhlIHNlY29uZCBUU00gc2VydmVyIHRvIHRoZSBuZXcgbWFj > aGluZSwgaXQgd291bGQgYmUgcGVyZmVjdC48L0RJVj48RElWPiZuYnNwOzwvRElWPjxESVY+RG9p > bmcgYSBleHBvcnQgc2VydmVyIGZpbGVkYXRhPWFsbCwgd291bGQgY3JlYXRlIGFib3V0Jm5ic3A7 > MTUwMCBuZXcgdGFwZXMsIGFjY29yZGluZyB0byBhIGV4cG9ydCBzZXJ2ZXIgcHJldmlldz15ZXMg > KGFib3V0IDMxVEIgb2YgZGF0YSkgYW5kIHRoaXMgd291bGQgcHJvYmJhbHkgbm90IHdvcmsgYXQg > YWxsLjwvRElWPjxESVY+PEJSPlNvLCBhbnlib2R5IGRvbmUgdGhpcyBiZWZvcmU/PC9ESVY+PERJ > Vj4mbmJzcDs8L0RJVj48RElWPkJlc3QgUmVnYXJkczwvRElWPjxESVY+Jm5ic3A7PC9ESVY+PERJ > Vj5EYW5pZWwgU3BhcnJtYW48L0RJVj48QlI+PERJVj4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t > LS0tLS0tLS0tLTxCUj5EYW5pZWwmbmJzcDtTcGFycm1hbjxCUj5FeGlzdCZuYnNwO2kmbmJzcDtT > dG9ja2hvbG0mbmJzcDtBQjxCUj5Qcm9wZWxsZXJ25GdlbiZuYnNwOzZCPEJSPjE4MyZuYnNwOzYy > Jm5ic3A7SMRHRVJOxFM8QlI+VuR4ZWw6Jm5ic3A7MDgmbmJzcDstJm5ic3A7NzU0Jm5ic3A7OTgm > bmJzcDswMDxCUj5Nb2JpbDombmJzcDswNzAmbmJzcDstJm5ic3A7Mzk5Jm5ic3A7MjcmbmJzcDs1 > MTxCUj48L0RJVj48L0ZPTlQ+ ... You might want to consider changing your email client's settings... - Allen S. Rout
