upgrade TSM client
Hi, What is the proper way to upgrade TSM clients (TSM 3.7.x and TSM 4.1.x clients on Windows and TSM 4.1.x client on HPUX) 1. Just install the new client over the old version 2. Uninstall first the old client. What about the client config files (dsm.opt, inclexcl files and dsm.sys). Remain they intact or copy them first to another location. And what about the TSM client schedular service: just stop it or should it be uninstalled first prior to the uninstall of the BA client). Install now the new version. And if necessary copy the config files again and start the schedular again. Test the connectivity by launching the BA GUI. And the same question for the TDP's of MS SQL and the TDP for Informix on HPUX. The upgrade process for the server is well discussed in the installation guide, but I don't find this information for the B/A client. Thanks, Kurt
Re: upgrade TSM client
Best way (especially for Wintel machines) is to use TSM to remove old scheduler, then uninstall TSM, then install new TSM and setup new scheduler. Config files like dsm.opt, dsm.sys and incl/excl files are not deleted by uninstalling. (They weren't installed by the install process, so it doesn't know about them.) If you have some really special config in them, you might make a copy to be safe. I suspect that HPUX , would be like AIX in that just doing an upgrade would work o.k. David Longo >>> [EMAIL PROTECTED] 11/28/02 03:21AM >>> Hi, What is the proper way to upgrade TSM clients (TSM 3.7.x and TSM 4.1.x clients on Windows and TSM 4.1.x client on HPUX) 1. Just install the new client over the old version 2. Uninstall first the old client. What about the client config files (dsm.opt, inclexcl files and dsm.sys). Remain they intact or copy them first to another location. And what about the TSM client schedular service: just stop it or should it be uninstalled first prior to the uninstall of the BA client). Install now the new version. And if necessary copy the config files again and start the schedular again. Test the connectivity by launching the BA GUI. And the same question for the TDP's of MS SQL and the TDP for Informix on HPUX. The upgrade process for the server is well discussed in the installation guide, but I don't find this information for the B/A client. Thanks, Kurt "MMS " made the following annotations on 11/28/2002 10:47:44 AM -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ==
Re: upgrade TSM client
Kurt, TDP for SQL upgrades after version 2.2.0 will install over the top of each other. The same is true for TDP for Exchange. The BA client is like that for most platforms, in some cases, there may be a situation that causes you to uninstall the previous version first... but in all cases your dsm.opt and/or other config files should be preserved. Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] - Never cut what can be untied. - Commit yourself to constant improvement. > That is the proper way to upgrade TSM clients (TSM 3.7.x and TSM 4.1.x clients > on Windows and TSM 4.1.x client on HPUX) > > 1. Just install the new client over the old version > > 2. Uninstall first the old client. What about the client config files (dsm.opt, inclexcl files and > dsm.sys). Remain they intact or copy them first to another location. And what about the TSM client > schedular service: just stop it or should it be uninstalled first prior to the uninstall of the BA > client). Install now the new version. And if necessary copy the config files again and start the > schedular again. Test the connectivity by launching the BA GUI. > And the same question for the TDP's of MS SQL and the TDP for Informix on HPUX. > The upgrade process for the server is well discussed in the installation guide, but I don't find this > information for the B/A client.
Performance drop after upgrade TSM client to 5.3.5.3?
Hello, Is there anyone else who is experiencing a performace drop in backups after upgrading Windows 2003 TSM clients 5.3.4.0 to 5.3.5.3, or similar? The clients are outside a firewall with sessioninitiation set to serveronly. TSM server is 5.3.4.0, AIX. Any suggestions are helpfull. Thanks Henrik ANS8000I Server command: 'select char(START_TIME,19) "START_TIME ",char(END_TIME,19) "END_TIME", char(ACTIVITY,8) "ACTIVITY",char(ENTITY,8) "ENTITY",dec(EXAMINED,8,0) "EXAMINED",dec(AFFECTED,8,0) "AFFECTED", dec(BYTES,12,0) "BYTES",dec(IDLE,5) "IDLE",dec(MEDIAW,6,0) "MEDIAW",dec(PROCESSES,2,0) "Pr",COMM_WAIT, dec((cast(BYTES as decimal(18,0)) / cast((END_TIME-START_TIME)seconds as decimal(18,0))),18,6) "Bytes recv/second" from summary where ACTIVITY='BACKUP' and START_TIME>'2007-11-12' and START_TIME<>END_TIME and ENTITY in ( 'server25', 'server39') order by ENTITY,"START_TIME "' START_TIME END_TIME ACTIVITY ENTITY EXAMINED AFFECTED BYTESIDLE MEDIAW Pr COMM_WAITBytes recv/second --- -- -- -- --- --- 2007-11-12 03:08:14 2007-11-12 04:00:02 BACKUP server25 104555 45744813837371 44012062 14418866.592985 2007-11-13 03:01:54 2007-11-13 04:27:26 BACKUP server25 104582 57842513859455 43014412 8284072.380163 2007-11-14 03:00:31 2007-11-14 04:15:01 BACKUP server25 108349 332442498231685 46014201 9507434.381431 2007-11-15 03:01:09 2007-11-15 04:04:16 BACKUP server25 107538 56641725324409 40013020 11018041.829680 2007-11-16 03:02:10 2007-11-16 04:21:17 BACKUP server25 107634 60642076850875 48014313 8863882.636401 2007-11-17 03:05:23 2007-11-17 03:50:33 BACKUP server25 107685 45341662549923 50011756 15373634.657933 2007-11-18 03:08:16 2007-11-18 04:12:56 BACKUP server25 107593 51141965600974 52012818 10815876.539690 2007-11-19 03:07:25 2007-11-19 03:58:04 BACKUP server25 107594 40641538988194 36012139 13668637.115498 2007-11-20 03:08:07 2007-11-20 05:01:02 BACKUP server25 107672 58442311579480 42015803 6245251.583763 2007-11-21 03:11:08 2007-11-21 05:53:16 BACKUP server25 473 6 2837282117 1029721291661.401829 2007-11-21 08:08:15 2007-11-21 12:36:00 BACKUP server25 42 3 5667957305 202 16056352814.024587 2007-11-21 14:24:43 2007-11-21 18:08:36 BACKUP server25 44 2 5679106791 102 13415422772.782773 2007-11-22 03:05:45 2007-11-22 05:55:35 BACKUP server25 46 5 2837394092 202 10157278448.880471 2007-11-23 03:08:11 2007-11-23 05:49:33 BACKUP server25 44 1 2836050165 1029677292919.868312 2007-11-12 03:08:13 2007-11-12 03:28:58 BACKUP server39 63516 21813052749690 201 912 10484136.297188 2007-11-13 03:01:52 2007-11-13 04:10:22 BACKUP server39 63548 26334999310053 7013640 8515647.214841 2007-11-14 03:00:28 2007-11-14 03:29:30 BACKUP server39 63559 28013573380597 5011686 7791837.311710 2007-11-15 03:01:08 2007-11-15 03:55:13 BACKUP server39 63572 29237014741964 16012713 11406700.142989 2007-11-16 03:02:07 2007-11-16 04:06:04 BACKUP server39 63525 24133990745518 3013674 8858677.487099 2007-11-17 03:05:21 2007-11-17 03:19:52 BACKUP server39 63593 38110405144243 901 625 11946204.641791 2007-11-18 03:08:14 2007-11-18 04:02:07 BACKUP server39 63529 24033570527003 51012388 10383707.702752 2007-11-19 03:07:23 2007-11-19 03:48:08 BACKUP server39 63564 23933592519157 13011906 13739271.638854 2007-11-20 03:08:05 2007-11-20 05:01:33 BACKUP server39 63585 28343151257159 3015897 6338316.268948 2007-11-21 03:08:55 2007-11-21 10:01:44 BACKUP server39 65882 6464 8648367439 3701 24173 349160.944688 2007-11-21 10:17:20 2007-11-21 12:45:36 BACKUP server39 37 2 2950425196 2028893331657.508543
Don't upgrade TSM client to 7.1.8 on a 6.3 server!
Hi guys, I just found out the hard way and I would like to share this knowledge before anyone else running this (unsupported) server level runs into the same issue: do NOT upgrade the TSM client to 7.1.8 on a 6.3 server. This client contains a GSKit version (8.0.50.78) which is not compatible with the 6.3 server. As soon as you upgrade the client, you will not be able to back up the TSM database (ANR4588E A database backup configuration might be incorrect) and as soon as you stop your server, you won't be able to start it anymore (ANR1820E The server could not connect to the database manager by using TCP/IP port). After downgrading to the GSKit that comes with the 7.1.6.x clients (8.0.50.66) everything is working again. So, now it's logged on the internet. :) Kind regards, Eric van Loon Air France/KLM Storage Engineering For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286
Re: Don't upgrade TSM client to 7.1.8 on a 6.3 server!
Hi Eric, The same wil happen for every server, on any platform, for version under 7.1.7.300 if you install a 7.1.8 or 8.1.2 client. Look at this : "Interim fix 7.1.7.300 was released to provide compatibility with a future release of the Global Security Kit (GSKit)." No other APAR fixed with this Interim Fix http://www-01.ibm.com/support/docview.wss?uid=swg21995379 -- Best regards / Cordialement / مع تحياتي Erwann SIMON - Mail original - De: "Eric van Loon (ITOPT3) - KLM" À: ADSM-L@VM.MARIST.EDU Envoyé: Mardi 20 Février 2018 14:29:21 Objet: [ADSM-L] Don't upgrade TSM client to 7.1.8 on a 6.3 server! Hi guys, I just found out the hard way and I would like to share this knowledge before anyone else running this (unsupported) server level runs into the same issue: do NOT upgrade the TSM client to 7.1.8 on a 6.3 server. This client contains a GSKit version (8.0.50.78) which is not compatible with the 6.3 server. As soon as you upgrade the client, you will not be able to back up the TSM database (ANR4588E A database backup configuration might be incorrect) and as soon as you stop your server, you won't be able to start it anymore (ANR1820E The server could not connect to the database manager by using TCP/IP port). After downgrading to the GSKit that comes with the 7.1.6.x clients (8.0.50.66) everything is working again. So, now it's logged on the internet. :) Kind regards, Eric van Loon Air France/KLM Storage Engineering For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286
