Just rename *.bin to *.tar and un-tar it. Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait, www.ahliunited.com.kw
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rhodes, Richard L. Sent: 30 04 2014 3:37 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Upgrading to v6 storage agent and TDPO > 1) stop TSM services; > 2) upgrade TSM Client by "smitty update_all"; Yes, this is how I upgrade in TSM v5. My confusing is that TSMv6 comes as one big package: CZG6SML_TSM_AIX_server_v6.2.1.bin (v6.2.1 base) 6.2.5.000-TIV-TSMALL-AIX.bin. (v6.2.5 upgrade) The AIX install packages are buried down in the dir structure when this is exploded. How did you run "smitty update_all"? Did you cd to the filesets in this structure? I really don't want to run the install.bin java gui to do this storage agent upgrade. Thanks! Rick asasdasdf -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Grigori Solonovitch Sent: Tuesday, April 29, 2014 11:45 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Upgrading to v6 storage agent and TDPO We have done this a year ago (5.5 --> 6.3.3.100). For Windows TSM Clients: 1) stop all TSM services; 2) run TSM Installer from new agent; 3) start TSM services; Notes: 1. Stopping TSM services is critical - reboot is required is any of the services is not stopped!!!!!! 2) There are some limitations for Windows 2003 (we are using: TSM Client 7.1 for Windows 2008/2012 and TSM Client 6.4.1 for Windows 2003, which officially is not certified, but required for TBMR 7.1). For AIX : 1) stop TSM services; 2) upgrade TSM Client by "smitty update_all"; 3) start TSM services. Notes: 1) Maximum allowed version for AIX 5.3 is 6.2 (6.2.4.4 in my case); 2) There is no limit for AIX 7.1 (7.1 in my case??); For TDP: 1) for Oracle under AIX just "smitty update_all" for selected version (7.1 in AIX 7.1); 2) for MS SQL it is much more complicated and you need to pay specific attention for each used version and selected target version; 3) for Exchange see MS SQL. I hope this information will help you at least a little bit:):) Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait, www.ahliunited.com.kw -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rhodes, Richard L. Sent: 29 04 2014 10:18 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Upgrading to v6 storage agent and TDPO We just finished our TSM v5 to TSM v6 server upgrades. I'll have to say it generally went very well. Lots of work but no real problems. Now I have to upgrade a bunch of V5 Storage Agents and TDPO setups. I looked at the upgrade guide and Storage Agent guide, but didn't find much on how to upgrade them. All the storage agents are at v551, the highest v5. Let me ask some questions . . . - Do you have to uninstall v5 before running install.bin to upgrade/install to v6? - Since it's not installing DB2, is it possible to just run a smitty install of the AIX binaries, instead of using the Java install.bin pgm? - Any other thoughts/suggestions for upgrading a Storage Agent? (Haven't looked at TDPO yet . . .) Thanks Rick ----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message. Please consider the environment before printing this Email. ________________________________ CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software. ________________________________ CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.