Hi TSM'ers: The export/import option takes so long time. So I think the best option in order to manage this environment is to copy the database to the second server. Copy the configuration files and start up the second TSM server. Then, the task is to delete nodes, stgpools, and all duplicated definitions.
Best Regards Sergio Vázquez TSM Certified Consultant -----Mensaje original----- De: Daniel Sparrman [mailto:[EMAIL PROTECTED] Enviado el: jueves, 20 de noviembre de 2003 12:41 Para: [EMAIL PROTECTED] Asunto: Re: Moving from 1 server having two libraries, to two servers having each one 1 library Hi Arnaud Another way of going at it is using server-to-server export/import functionality within TSM. You can choose to export all AIX-nodes from your old server to the new server over the LAN. You could also export all schedules, domains and other information related to your AIX-nodes separatly. Best Regards Daniel Sparrman ----------------------------------- Daniel Sparrman Exist i Stockholm AB Propellervägen 6B 183 62 TÄBY Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51 PAC Brion Arnaud <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 2003-11-20 12:18 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Moving from 1 server having two libraries, to two servers having each one 1 library Hi list, Having in sight to reduce the workload on our actual TSM server which reaches it's limits, we've planned to acquire a new machine, install a new TSM server and transfer half of the clients there. Our actual setup looks like : AIX TSM server 5.1.6.2, connected to 2 3584 libraries. Our client data is actually more or less splitted on the 2 libraries : the first one mainly for AIX systems, the second one mainly for windows systems. Our future setup will look like each server will be connnected to it's own library, one group for aix clients, the other for windows clients. My question : is there a simple way to inject only part of actual tsm DB to our new server, having as a goal to transmit only windows clients information to the future server which will be attached to the library allready containing windows systems data. The only option I could see now would be to restore the whole DB to the new server, and thereafter to modify all the scripts, parameters, paths to libraries and disk pools, to delete the undesirable aix nodes from this server, and finally to rebind windows clients to the new server. Maybe some of you have a better idea, or experience to share ... Thanks in advance. Arnaud =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | Arnaud Brion, Panalpina Management Ltd., IT Group | | Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland | | Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01 | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Este mensaje de correo electrónico y sus documentos adjuntos están dirigidos EXCLUSIVAMENTE a los destinatarios especificados. La información contenida puede ser CONFIDENCIAL y/o estar LEGALMENTE PROTEGIDA y no necesariamente refleja la opinión de ENDESA. Si usted recibe este mensaje por ERROR, por favor comuníqueselo inmediatamente al remitente y ELIMÍNELO ya que usted NO ESTA AUTORIZADO al uso, revelación, distribución, impresión o copia de toda o alguna parte de la información contenida. Gracias. This e-mail message and any attached files are intended SOLELY for the addressee/s identified herein. It may contain CONFIDENTIAL and/or LEGALLY PRIVILEGED information and may not necessarily represent the opinion of ENDESA. If you receive this message in ERROR, please immediately notify the sender and DELETE it since you ARE NOT AUTHORIZED to use, disclose, distribute, print or copy all or part of the contained information. Thank you.