TSM upgrade v5 -- v6 database storage question
Hello All, Thanks for your help! Upgrading a client on Windows 2003 TSM v5.5.3 to Windows 2008 TSM 6.1.3. I am planning the storage and was wondering if it is worth splitting the database between multiple file systems. The storage they have for the database is FCAL on an IBM DS4800. The client's current database is 65GB and will probably reduce to 55GB after the upgrade when we purge some old data. I was going to do the following e:\ database directory f:\ active log directory g:\ archive log directory. I could do this e:\ database directory f:\ database directory g:\ database directory h:\ active log directory i:\ archive log directory. The storage will be all be RAIDed on the DS4800 so I am wondering just how much if any performance gains I will see if I split the database up into more file systems. I would also like to solicit any opinions on the storage configuration (i.e. - RAID?, placement of logs, etc) Thanks, Nicholas
Re: TSM upgrade v5 -- v6 database storage question
Easy answer . . . it depends . . . Here are some questions/comments in no particular order: Are you on an array today? Is the array busy and loaded down? Does it have multiple raidsets? What kind of drives does it have (sata, fc10k, fc15k)? I'm not a windows admin - would the drive letters be separate luns? If separate luns, would you put them on separate raidsets? If multiple luns but all on the same raidset, then you are basically gaining a cmd queue for each lun. If separate luns and you can put them on separate raidsets, then you are getting many more HDD's working for you. Are you disk I/O bound now? If not, then you probably won't see much difference on matter what you do. The big advantage of the array is I/O spread across multiple/many spindles and write-back cache. If you were using a unix system, I'd say to allocate one lun per raidset, bring them into a volume group, and create filesystems striped across the luns. That's how we do everything. rick Nicholas Rodolfich nrodolf...@cmaon To THEWEB.COM ADSM-L@VM.MARIST.EDU Sent by: ADSM:cc Dist Stor Manager Subject ads...@vm.marist TSM upgrade v5 -- v6 database .EDU storage question 02/18/2010 02:39 PM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU Hello All, Thanks for your help! Upgrading a client on Windows 2003 TSM v5.5.3 to Windows 2008 TSM 6.1.3. I am planning the storage and was wondering if it is worth splitting the database between multiple file systems. The storage they have for the database is FCAL on an IBM DS4800. The client's current database is 65GB and will probably reduce to 55GB after the upgrade when we purge some old data. I was going to do the following e:\ database directory f:\ active log directory g:\ archive log directory. I could do this e:\ database directory f:\ database directory g:\ database directory h:\ active log directory i:\ archive log directory. The storage will be all be RAIDed on the DS4800 so I am wondering just how much if any performance gains I will see if I split the database up into more file systems. I would also like to solicit any opinions on the storage configuration (i.e. - RAID?, placement of logs, etc) Thanks, Nicholas - 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.
Re: TSM upgrade v5 -- v6 database storage question
Just one point to add to that - with the DS4x00 series storage arrays you only have one preferred controller active at a time per LUN - so if you split the db into two LUNs you have the option to have each LUN running across a separate controller, with I/O performance gains as a result. If you'd even notice the difference is another matter ;) - Richard Rhodes rrho...@firstenergycorp.com wrote: From: Richard Rhodes rrho...@firstenergycorp.com To: ADSM-L@VM.MARIST.EDU Sent: Friday, 19 February, 2010 9:28:45 AM (GMT+1200) Auto-Detected Subject: Re: [ADSM-L] TSM upgrade v5 -- v6 database storage question Easy answer . . . it depends . . . Here are some questions/comments in no particular order: Are you on an array today? Is the array busy and loaded down? Does it have multiple raidsets? What kind of drives does it have (sata, fc10k, fc15k)? I'm not a windows admin - would the drive letters be separate luns? If separate luns, would you put them on separate raidsets? If multiple luns but all on the same raidset, then you are basically gaining a cmd queue for each lun. If separate luns and you can put them on separate raidsets, then you are getting many more HDD's working for you. Are you disk I/O bound now? If not, then you probably won't see much difference on matter what you do. The big advantage of the array is I/O spread across multiple/many spindles and write-back cache. If you were using a unix system, I'd say to allocate one lun per raidset, bring them into a volume group, and create filesystems striped across the luns. That's how we do everything. rick Nicholas Rodolfich nrodolf...@cmaon To THEWEB.COM ADSM-L@VM.MARIST.EDU Sent by: ADSM: cc Dist Stor Manager Subject ads...@vm.marist TSM upgrade v5 -- v6 database .EDU storage question 02/18/2010 02:39 PM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU Hello All, Thanks for your help! Upgrading a client on Windows 2003 TSM v5.5.3 to Windows 2008 TSM 6.1.3. I am planning the storage and was wondering if it is worth splitting the database between multiple file systems. The storage they have for the database is FCAL on an IBM DS4800. The client's current database is 65GB and will probably reduce to 55GB after the upgrade when we purge some old data. I was going to do the following e:\ database directory f:\ active log directory g:\ archive log directory. I could do this e:\ database directory f:\ database directory g:\ database directory h:\ active log directory i:\ archive log directory. The storage will be all be RAIDed on the DS4800 so I am wondering just how much if any performance gains I will see if I split the database up into more file systems. I would also like to solicit any opinions on the storage configuration (i.e. - RAID?, placement of logs, etc) Thanks, Nicholas - 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.
TSM upgrade PLAN
Hello, I have TSM Server version 5.2.3.4 running on AIX 5.2. I want to upgrade to the latest version Supported by AIX 5.2 (TSM 5.4). Can you help me identify an upgrade plan approach (including intermedium releases) to reach the latest TSM version 5.4? Thank you for your help Best Regards Tiago This e-mail and any attachments may contain confidential or privileged information. Any unauthorised copying, use or distribution of this information is strictly prohibited.
Re: TSM upgrade PLAN
Take a look at the installation guide manual for TSM 5.4, in particular the section on upgrading the server. -- Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of BOTELHO, TIAGO MARIA Sent: Wednesday, October 15, 2008 10:06 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM upgrade PLAN Hello, I have TSM Server version 5.2.3.4 running on AIX 5.2. I want to upgrade to the latest version Supported by AIX 5.2 (TSM 5.4). Can you help me identify an upgrade plan approach (including intermedium releases) to reach the latest TSM version 5.4? Thank you for your help Best Regards Tiago This e-mail and any attachments may contain confidential or privileged information. Any unauthorised copying, use or distribution of this information is strictly prohibited.
Re: TSM upgrade to 5.5.1
Hi guys!
I decided to open a PMR for the TSMOR bug and support told me there already is
an open APAR for this problem:
APAR= IC57290 SER= ANR2906E UNEXPECTED SQL LITERAL TOKEN - 'RUS' ERROR FROM
OPERATIONAL REPORTING
ERROR DESCRIPTION:
The following select statement is issued for Operational Reporting:
07/09/2008 10:52:27 ANR2017I Administrator ADMIN issued command: select
option_value as LANG from options where UPPER(option_value) in
('CHS','ZH_CN','CHT','ZH_TW','DEU','DE_DE','AMENG','EN_US','ENG','ESP','ES_ES','FRA','FR_FR','ITA','IT_IT','JPN','JA_JP','KOR','KO_KR','PTB','PT_
BR')'RUS','RU_RU') (SESSION: 31)
Invalid command syntax of the select statement results in the following error
message:
07/09/2008 10:52:27 ANR2906E Unexpected SQL literal token - 'RUS'.
(SESSION: 31)
This problem was introduced in the 5.5.1 server code level.
Platforms affected: 5.5.1
Initial Impact: Medium
Additional Keywords: or o/r op report
LOCAL FIX:
The problem can be circumvented by stopping the TSMReptSvc service and exiting
the management console (mmc), then replacing the 5.5.1 tsmrept.exe with the the
one from the 550GA install package and restarting the service. The management
console can be started and the report refreshed to verify the problem has been
resolved.
The 550GA tsmrept.exe may be in the
C:\tsm_images\5.5.0.0-TIV-TSMSRV-Windows\TSM32\server\program
files\Tivoli\TSM\console directory unless the directory was deleted after the
GA install.
It's a pitty that I could not find this APAR through the IBM website. It could
have saved me opening a PMR...
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Phillip Burgess
Sent: donderdag 17 juli 2008 16:58
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM upgrade to 5.5.1
Try running Ops reporting on your test server ;)
It fails immediately when you run any report, due to a spelling mistake in the
language query !
Other than that we have been running it for two days without any problem on
Windows.
Phil
From: Björn Rackoll [mailto:backup AT RRZ.UNI-HAMBURG DOT DE]
Sent: Thu 17/07/2008 15:02
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM upgrade to 5.5.1
Hi,
currently we have TSM 5.3.4.2 running on AIX 5.3 (and an IBM 3494 tape library
with eight 3592 drives, Atape 10.7.3.0) and are planning to upgrade to 5.5.1.0
soon. I've already tested this upgrade on my test machine, and it worked fine.
This absence of any problem made me even a bit suspicious. :-)
My questions:
- Which kind of tests would you recommend performing before you'd declare a new
TSM version 'ready for production'? I've read Technote
1196013 and the relevant section in ADSM.QuickFacts. Performing a simple backup
and restore from different clients worked fine, LAN-free is not used.
- Do you know of any pitfalls in 5.5.1.0 or should it be safe to use on the
server?
Regards,
--
Bjoern Rackoll
University of Hamburg
Regionales Rechenzentrum
Zentrale Dienste
Schlueterstr. 70
20146 Hamburg
Tel.: +49 (0)40 42838 - 63 11
Fax: +49 (0)40 42838 - 62 70
E-Mail: backup AT rrz.uni-hamburg DOT de
**
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
**
FW: [ADSM-L] TSM upgrade to 5.5.1
I am trying to install the downlevel console on the windows TSM SERVER host. The error message I receive is: The Tivoli Storage Manager Console can not be installed with the Tivoli Storage Manager Server. Remove the TSM Server and try again. Am I doing something wrong? Do I need to poke around some more? I don't see any way to de-couple the installation of the console from the server or just remove the 5.5.1.0 console. Both are on a test box. Worst come to worst, I'll create a VM to run the down-level console to run the Op Rept against the TSM test server. Wanting to test some tweaking of the report (and not on a production TSM server). Thanks Bill! thanks! lisa -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bill Boyer Sent: Friday, July 18, 2008 6:23 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM upgrade to 5.5.1 Sure you can. Just download the TSMCON package from the Windows server maintenance directory on the FTP server. Just needs a Winders box. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Laughlin, Lisa Sent: Friday, July 18, 2008 4:29 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM upgrade to 5.5.1 Unless you are actually running a TSM server on windows, and you can't install the console separately thanks! lisa -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Phillip Burgess Sent: Friday, July 18, 2008 7:35 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM upgrade to 5.5.1 If you use TSM operational reporting, then you need to install an older version of the TSM Management console such as 5.5.0.3, otherwise it will fail to generate any reports. I would not consider this a major bug, more of an annoyance. Phil From: Björn Rackoll [mailto:[EMAIL PROTECTED] Sent: Fri 18/07/2008 12:28 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM upgrade to 5.5.1 Hi Phil, Try running Ops reporting on your test server ;) how exactly (e.g., using which command) do you do that? How severe would you consider that problem? Regards, -- Bjoern Rackoll University of Hamburg Regionales Rechenzentrum Zentrale Dienste Schlueterstr. 70 20146 Hamburg Tel.: +49 (0)40 42838 - 63 11 Fax: +49 (0)40 42838 - 62 70 E-Mail: [EMAIL PROTECTED]
Re: TSM upgrade to 5.5.1
Sure you can. Just download the TSMCON package from the Windows server maintenance directory on the FTP server. Just needs a Winders box. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Laughlin, Lisa Sent: Friday, July 18, 2008 4:29 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM upgrade to 5.5.1 Unless you are actually running a TSM server on windows, and you can't install the console separately thanks! lisa -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Phillip Burgess Sent: Friday, July 18, 2008 7:35 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM upgrade to 5.5.1 If you use TSM operational reporting, then you need to install an older version of the TSM Management console such as 5.5.0.3, otherwise it will fail to generate any reports. I would not consider this a major bug, more of an annoyance. Phil From: Björn Rackoll [mailto:[EMAIL PROTECTED] Sent: Fri 18/07/2008 12:28 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM upgrade to 5.5.1 Hi Phil, Try running Ops reporting on your test server ;) how exactly (e.g., using which command) do you do that? How severe would you consider that problem? Regards, -- Bjoern Rackoll University of Hamburg Regionales Rechenzentrum Zentrale Dienste Schlueterstr. 70 20146 Hamburg Tel.: +49 (0)40 42838 - 63 11 Fax: +49 (0)40 42838 - 62 70 E-Mail: [EMAIL PROTECTED]
Re: TSM upgrade to 5.5.1
Hi, I have been using 5.5.0.0 (I know base level not good for production) and have just gone to 5.5.1 . No problems to date. In fact it seems more stable and faster at daily tasks. The upgrade process is amazingly fast and efficient. Simple test were backup and restore of each client, TDP, Exchange etc. Environment = AIX on P570 LPAR, EMC SAN, TS3310 Libr 108 Slots, 4 LTO3 Drives. Good Luck Regards Adrian Compton Aspen Pharmacare Port Elizabeth tel: +2741 4072855 Fax: +2741 453 7452 Cell: +27823204495 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Björn Rackoll Sent: 17 July 2008 16:03 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM upgrade to 5.5.1 Hi, currently we have TSM 5.3.4.2 running on AIX 5.3 (and an IBM 3494 tape library with eight 3592 drives, Atape 10.7.3.0) and are planning to upgrade to 5.5.1.0 soon. I've already tested this upgrade on my test machine, and it worked fine. This absence of any problem made me even a bit suspicious. :-) My questions: - Which kind of tests would you recommend performing before you'd declare a new TSM version 'ready for production'? I've read Technote 1196013 and the relevant section in ADSM.QuickFacts. Performing a simple backup and restore from different clients worked fine, LAN-free is not used. - Do you know of any pitfalls in 5.5.1.0 or should it be safe to use on the server? Regards, -- Bjoern Rackoll University of Hamburg Regionales Rechenzentrum Zentrale Dienste Schlueterstr. 70 20146 Hamburg Tel.: +49 (0)40 42838 - 63 11 Fax: +49 (0)40 42838 - 62 70 E-Mail: [EMAIL PROTECTED]
Re: TSM upgrade to 5.5.1
Hi Phil! Same here! It seems to be a bug in TSMOR 5.5.1. I didn't feel like reporting it to IBM (I know, I know, not very helpfull of me) so I went back to the 5.4 version. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Phillip Burgess Sent: donderdag 17 juli 2008 16:58 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM upgrade to 5.5.1 Try running Ops reporting on your test server ;) It fails immediately when you run any report, due to a spelling mistake in the language query ! Other than that we have been running it for two days without any problem on Windows. Phil From: Björn Rackoll [mailto:[EMAIL PROTECTED] Sent: Thu 17/07/2008 15:02 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM upgrade to 5.5.1 Hi, currently we have TSM 5.3.4.2 running on AIX 5.3 (and an IBM 3494 tape library with eight 3592 drives, Atape 10.7.3.0) and are planning to upgrade to 5.5.1.0 soon. I've already tested this upgrade on my test machine, and it worked fine. This absence of any problem made me even a bit suspicious. :-) My questions: - Which kind of tests would you recommend performing before you'd declare a new TSM version 'ready for production'? I've read Technote 1196013 and the relevant section in ADSM.QuickFacts. Performing a simple backup and restore from different clients worked fine, LAN-free is not used. - Do you know of any pitfalls in 5.5.1.0 or should it be safe to use on the server? Regards, -- Bjoern Rackoll University of Hamburg Regionales Rechenzentrum Zentrale Dienste Schlueterstr. 70 20146 Hamburg Tel.: +49 (0)40 42838 - 63 11 Fax: +49 (0)40 42838 - 62 70 E-Mail: [EMAIL PROTECTED] ** 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: TSM upgrade to 5.5.1
Hi Phil, Try running Ops reporting on your test server ;) how exactly (e.g., using which command) do you do that? How severe would you consider that problem? Regards, -- Bjoern Rackoll University of Hamburg Regionales Rechenzentrum Zentrale Dienste Schlueterstr. 70 20146 Hamburg Tel.: +49 (0)40 42838 - 63 11 Fax: +49 (0)40 42838 - 62 70 E-Mail: [EMAIL PROTECTED]
Re: TSM upgrade to 5.5.1
If you use TSM operational reporting, then you need to install an older version of the TSM Management console such as 5.5.0.3, otherwise it will fail to generate any reports. I would not consider this a major bug, more of an annoyance. Phil From: Björn Rackoll [mailto:[EMAIL PROTECTED] Sent: Fri 18/07/2008 12:28 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM upgrade to 5.5.1 Hi Phil, Try running Ops reporting on your test server ;) how exactly (e.g., using which command) do you do that? How severe would you consider that problem? Regards, -- Bjoern Rackoll University of Hamburg Regionales Rechenzentrum Zentrale Dienste Schlueterstr. 70 20146 Hamburg Tel.: +49 (0)40 42838 - 63 11 Fax: +49 (0)40 42838 - 62 70 E-Mail: [EMAIL PROTECTED]
Re: TSM upgrade to 5.5.1
Unless you are actually running a TSM server on windows, and you can't install the console separately thanks! lisa -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Phillip Burgess Sent: Friday, July 18, 2008 7:35 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM upgrade to 5.5.1 If you use TSM operational reporting, then you need to install an older version of the TSM Management console such as 5.5.0.3, otherwise it will fail to generate any reports. I would not consider this a major bug, more of an annoyance. Phil From: Björn Rackoll [mailto:[EMAIL PROTECTED] Sent: Fri 18/07/2008 12:28 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM upgrade to 5.5.1 Hi Phil, Try running Ops reporting on your test server ;) how exactly (e.g., using which command) do you do that? How severe would you consider that problem? Regards, -- Bjoern Rackoll University of Hamburg Regionales Rechenzentrum Zentrale Dienste Schlueterstr. 70 20146 Hamburg Tel.: +49 (0)40 42838 - 63 11 Fax: +49 (0)40 42838 - 62 70 E-Mail: [EMAIL PROTECTED]
TSM upgrade to 5.5.1
Hi, currently we have TSM 5.3.4.2 running on AIX 5.3 (and an IBM 3494 tape library with eight 3592 drives, Atape 10.7.3.0) and are planning to upgrade to 5.5.1.0 soon. I've already tested this upgrade on my test machine, and it worked fine. This absence of any problem made me even a bit suspicious. :-) My questions: - Which kind of tests would you recommend performing before you'd declare a new TSM version 'ready for production'? I've read Technote 1196013 and the relevant section in ADSM.QuickFacts. Performing a simple backup and restore from different clients worked fine, LAN-free is not used. - Do you know of any pitfalls in 5.5.1.0 or should it be safe to use on the server? Regards, -- Bjoern Rackoll University of Hamburg Regionales Rechenzentrum Zentrale Dienste Schlueterstr. 70 20146 Hamburg Tel.: +49 (0)40 42838 - 63 11 Fax: +49 (0)40 42838 - 62 70 E-Mail: [EMAIL PROTECTED]
Re: TSM upgrade to 5.5.1
For our last upgrade to 5.4 we ran expiration on the test upgrade and a few backups and restores without giving access to the real data. Once upgraded we ran a backup, restore with fresh data and a restore with upgraded data. Our last upgrade we ran into a problem during reclaim (fixed with a patch), but we have not figured out a way to test that without endangering the data. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Björn Rackoll Sent: Thursday, July 17, 2008 9:03 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM upgrade to 5.5.1 Hi, currently we have TSM 5.3.4.2 running on AIX 5.3 (and an IBM 3494 tape library with eight 3592 drives, Atape 10.7.3.0) and are planning to upgrade to 5.5.1.0 soon. I've already tested this upgrade on my test machine, and it worked fine. This absence of any problem made me even a bit suspicious. :-) My questions: - Which kind of tests would you recommend performing before you'd declare a new TSM version 'ready for production'? I've read Technote 1196013 and the relevant section in ADSM.QuickFacts. Performing a simple backup and restore from different clients worked fine, LAN-free is not used. - Do you know of any pitfalls in 5.5.1.0 or should it be safe to use on the server? Regards, -- Bjoern Rackoll University of Hamburg Regionales Rechenzentrum Zentrale Dienste Schlueterstr. 70 20146 Hamburg Tel.: +49 (0)40 42838 - 63 11 Fax: +49 (0)40 42838 - 62 70 E-Mail: [EMAIL PROTECTED] This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: TSM upgrade to 5.5.1
Try running Ops reporting on your test server ;) It fails immediately when you run any report, due to a spelling mistake in the language query ! Other than that we have been running it for two days without any problem on Windows. Phil From: Björn Rackoll [mailto:[EMAIL PROTECTED] Sent: Thu 17/07/2008 15:02 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM upgrade to 5.5.1 Hi, currently we have TSM 5.3.4.2 running on AIX 5.3 (and an IBM 3494 tape library with eight 3592 drives, Atape 10.7.3.0) and are planning to upgrade to 5.5.1.0 soon. I've already tested this upgrade on my test machine, and it worked fine. This absence of any problem made me even a bit suspicious. :-) My questions: - Which kind of tests would you recommend performing before you'd declare a new TSM version 'ready for production'? I've read Technote 1196013 and the relevant section in ADSM.QuickFacts. Performing a simple backup and restore from different clients worked fine, LAN-free is not used. - Do you know of any pitfalls in 5.5.1.0 or should it be safe to use on the server? Regards, -- Bjoern Rackoll University of Hamburg Regionales Rechenzentrum Zentrale Dienste Schlueterstr. 70 20146 Hamburg Tel.: +49 (0)40 42838 - 63 11 Fax: +49 (0)40 42838 - 62 70 E-Mail: [EMAIL PROTECTED]
Re: TSM upgrade to 5.5.1
Same here with the spelling mistake. I installed TSM Console 5.5.0.3 and it got rid of the errors from the bad SQL query. ftp://ftp.software.ibm.com/storage/t...ON-Windows.exe *** Gregory Lynch Lead Programmer Analyst IT Infrastructure/Systems Administration Stony Brook University Medical Center HSC Level 3, Room 121 ZIP 8037 Phone: 631-444-9783 [EMAIL PROTECTED] This e- mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by e-mail and destroy all copies of the original. Phillip Burgess [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 07/17/2008 11:03 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM upgrade to 5.5.1 Try running Ops reporting on your test server ;) It fails immediately when you run any report, due to a spelling mistake in the language query ! Other than that we have been running it for two days without any problem on Windows. Phil From: Björn Rackoll [mailto:[EMAIL PROTECTED] Sent: Thu 17/07/2008 15:02 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM upgrade to 5.5.1 Hi, currently we have TSM 5.3.4.2 running on AIX 5.3 (and an IBM 3494 tape library with eight 3592 drives, Atape 10.7.3.0) and are planning to upgrade to 5.5.1.0 soon. I've already tested this upgrade on my test machine, and it worked fine. This absence of any problem made me even a bit suspicious. :-) My questions: - Which kind of tests would you recommend performing before you'd declare a new TSM version 'ready for production'? I've read Technote 1196013 and the relevant section in ADSM.QuickFacts. Performing a simple backup and restore from different clients worked fine, LAN-free is not used. - Do you know of any pitfalls in 5.5.1.0 or should it be safe to use on the server? Regards, -- Bjoern Rackoll University of Hamburg Regionales Rechenzentrum Zentrale Dienste Schlueterstr. 70 20146 Hamburg Tel.: +49 (0)40 42838 - 63 11 Fax: +49 (0)40 42838 - 62 70 E-Mail: [EMAIL PROTECTED]
Re: TSM Upgrade to version 5.4
Dirk, We are running TSM 5.4.1.2 on 4 AIX (5.3 ML5) servers for a month without any problems. Regards, Kurt -Oorspronkelijk bericht- Van: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Namens Dirk Kastens Verzonden: vrijdag 9 november 2007 8:59 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: Re: [ADSM-L] TSM Upgrade to version 5.4 Hi, Andy Huebner wrote: We are about to upgrade TSM from 5.2.2.4 to a version of 5.4 on AIX 5.3. Is there a stable recommended version? Maybe 5.4.1.2? We are running TSM 5.4.1.2 on AIX 5.3 for a few weeks now without any problems. -- Regards, Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470 *** Disclaimer *** Vlaamse Radio- en Televisieomroep Auguste Reyerslaan 52, 1043 Brussel nv van publiek recht BTW BE 0244.142.664 RPR Brussel http://www.vrt.be/disclaimer
AW: [ADSM-L] TSM Upgrade to version 5.4
Hi Andi, We are using TSM 5.4 since Version 5.4.0.2. Running on AIX 5300-06-03-0732. We came from TSM 5.3.5.2 - Easy migration - just use smitty update_all :-) But we decided to use the Active Data Pool feature. - Well this was a big mistake - we had serveral server crashes, audits (downtime nearly 12hours), defective offsite space reclamations and so on .. Now we have Version 5.4.1.2 and most of the problems are fixed - thanks to the folks at tivoli_support :-). At the moment the Active Data Pool works great - running on an IBM DS6000 nearly 11TB - great stuff - doing tapeless restores :-) I love this .. but I wish it wouldn´t be such a mess implementing this feature. Stefan Lehmann Sozialversicherungsträger für den Gartenbau - GB-IT, Security - Frankfurter Straße 126 34121 Kassel 0561 - 9282540 / 0160 - 7753976 -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Dirk Kastens Gesendet: Freitag, 9. November 2007 08:59 An: ADSM-L@VM.MARIST.EDU Betreff: Re: [ADSM-L] TSM Upgrade to version 5.4 Hi, Andy Huebner wrote: We are about to upgrade TSM from 5.2.2.4 to a version of 5.4 on AIX 5.3. Is there a stable recommended version? Maybe 5.4.1.2? We are running TSM 5.4.1.2 on AIX 5.3 for a few weeks now without any problems. -- Regards, Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470
Re: TSM Upgrade to version 5.4
Not that I am aware of. Whenever clients terminate unexpectedly, we get these error messages, so you might want to watch for/ignore them for now: 11/8/2007 11:40:41 PM ANR2706E cssess.c(1673) Scheduler database query failed: 2. 11/8/2007 11:40:41 PM ANRD smexec.c(3017): ThreadId Error 1 occurred reporting an abnormal termination code. 11/8/2007 11:40:41 PM ANR0481W Session 75363 for node SLIGO.VCU.EDU (SUN SOLARIS) terminated - client did not respond within 6000 seconds. Andy Huebner [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 04:54 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 Has this problem caused any issues with your server? Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Thursday, November 08, 2007 2:48 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Upgrade to version 5.4 This one: PK54980: ERROR ANR2706E AND EXCESSIVE ANRD MESSAGES WERE LOGGED IN ACTIVITY LOG AFTER A SCHEDULED CLIENT SESSION WAS TERMINATED. http://www-1.ibm.com/support/docview.wss?rs=663context=SSGSG7dc=DB550; uid=swg1PK54980loc=en_UScs=UTF-8lang=enrss=ct663tivoli I thought it interesting that under TSM Versions Affected:, it includes the as-of-yet-unreleased 5.4.2 Andy Huebner [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 03:37 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 What problem did you find? Is there a known defect list somewhere? Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Thursday, November 08, 2007 12:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Upgrade to version 5.4 Well, I wouldn't go that far. I just upgraded my 5.3.x server to 5.4.1.2 and immediately found a problem that was introduced in 5.4/5.4.1 and won't be fixed until 5.4.2. YMMV Michael Green [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 01:09 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 As always, the latest is the greatest. On 11/8/07, Andy Huebner [EMAIL PROTECTED] wrote: We are about to upgrade TSM from 5.2.2.4 to a version of 5.4 on AIX 5.3. Is there a stable recommended version? Maybe 5.4.1.2? Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. -- Warm regards, Michael Green This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: TSM Upgrade to version 5.4
As always, the latest is the greatest. On 11/8/07, Andy Huebner [EMAIL PROTECTED] wrote: We are about to upgrade TSM from 5.2.2.4 to a version of 5.4 on AIX 5.3. Is there a stable recommended version? Maybe 5.4.1.2? Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. -- Warm regards, Michael Green
Re: TSM Upgrade to version 5.4
Well, I wouldn't go that far. I just upgraded my 5.3.x server to 5.4.1.2 and immediately found a problem that was introduced in 5.4/5.4.1 and won't be fixed until 5.4.2. YMMV Michael Green [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 01:09 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 As always, the latest is the greatest. On 11/8/07, Andy Huebner [EMAIL PROTECTED] wrote: We are about to upgrade TSM from 5.2.2.4 to a version of 5.4 on AIX 5.3. Is there a stable recommended version? Maybe 5.4.1.2? Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. -- Warm regards, Michael Green
Re: TSM Upgrade to version 5.4
Rule of thumb - Always stay 1 version behind the latest and pay special attention to the release notes to the newer version and see if that applies to your environment or not. If useful then attempt to upgrade, otherwise stay where you are at until all the bugs are fixed. Kamran -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Thursday, November 08, 2007 1:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Upgrade to version 5.4 Well, I wouldn't go that far. I just upgraded my 5.3.x server to 5.4.1.2 and immediately found a problem that was introduced in 5.4/5.4.1 and won't be fixed until 5.4.2. YMMV Michael Green [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 01:09 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 As always, the latest is the greatest. On 11/8/07, Andy Huebner [EMAIL PROTECTED] wrote: We are about to upgrade TSM from 5.2.2.4 to a version of 5.4 on AIX 5.3. Is there a stable recommended version? Maybe 5.4.1.2? Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. -- Warm regards, Michael Green
Re: TSM Upgrade to version 5.4
Tell me that I am a MF'er does not mean what I immediately think of. Usually you call another person that type of name. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Thursday, November 08, 2007 12:16 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Upgrade to version 5.4 I am a MF'er and fully realize this (we always stayed 3-6 months behind current PTF levels) In my situation, I was addressing a problem that was supposedly addressed in 5.4.1.2 or I wouldn't have gone that far uplevel. Fortunately, the new problem is somewhat cosmetic/low-key. Kamran Rao [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 01:31 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 Rule of thumb - Always stay 1 version behind the latest and pay special attention to the release notes to the newer version and see if that applies to your environment or not. If useful then attempt to upgrade, otherwise stay where you are at until all the bugs are fixed. Kamran -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Thursday, November 08, 2007 1:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Upgrade to version 5.4 Well, I wouldn't go that far. I just upgraded my 5.3.x server to 5.4.1.2 and immediately found a problem that was introduced in 5.4/5.4.1 and won't be fixed until 5.4.2. YMMV Michael Green [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 01:09 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 As always, the latest is the greatest. On 11/8/07, Andy Huebner [EMAIL PROTECTED] wrote: We are about to upgrade TSM from 5.2.2.4 to a version of 5.4 on AIX 5.3. Is there a stable recommended version? Maybe 5.4.1.2? Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. -- Warm regards, Michael Green
Re: TSM Upgrade to version 5.4
I am a MF'er and fully realize this (we always stayed 3-6 months behind current PTF levels) In my situation, I was addressing a problem that was supposedly addressed in 5.4.1.2 or I wouldn't have gone that far uplevel. Fortunately, the new problem is somewhat cosmetic/low-key. Kamran Rao [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 01:31 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 Rule of thumb - Always stay 1 version behind the latest and pay special attention to the release notes to the newer version and see if that applies to your environment or not. If useful then attempt to upgrade, otherwise stay where you are at until all the bugs are fixed. Kamran -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Thursday, November 08, 2007 1:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Upgrade to version 5.4 Well, I wouldn't go that far. I just upgraded my 5.3.x server to 5.4.1.2 and immediately found a problem that was introduced in 5.4/5.4.1 and won't be fixed until 5.4.2. YMMV Michael Green [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 01:09 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 As always, the latest is the greatest. On 11/8/07, Andy Huebner [EMAIL PROTECTED] wrote: We are about to upgrade TSM from 5.2.2.4 to a version of 5.4 on AIX 5.3. Is there a stable recommended version? Maybe 5.4.1.2? Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. -- Warm regards, Michael Green
Re: TSM Upgrade to version 5.4
This one: PK54980: ERROR ANR2706E AND EXCESSIVE ANRD MESSAGES WERE LOGGED IN ACTIVITY LOG AFTER A SCHEDULED CLIENT SESSION WAS TERMINATED. http://www-1.ibm.com/support/docview.wss?rs=663context=SSGSG7dc=DB550uid=swg1PK54980loc=en_UScs=UTF-8lang=enrss=ct663tivoli I thought it interesting that under TSM Versions Affected:, it includes the as-of-yet-unreleased 5.4.2 Andy Huebner [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 03:37 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 What problem did you find? Is there a known defect list somewhere? Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Thursday, November 08, 2007 12:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Upgrade to version 5.4 Well, I wouldn't go that far. I just upgraded my 5.3.x server to 5.4.1.2 and immediately found a problem that was introduced in 5.4/5.4.1 and won't be fixed until 5.4.2. YMMV Michael Green [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 01:09 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 As always, the latest is the greatest. On 11/8/07, Andy Huebner [EMAIL PROTECTED] wrote: We are about to upgrade TSM from 5.2.2.4 to a version of 5.4 on AIX 5.3. Is there a stable recommended version? Maybe 5.4.1.2? Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. -- Warm regards, Michael Green This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: TSM Upgrade to version 5.4
I figured there were enough old timers on this list to figure out I was/am a M(ain) F(ramer) Ben Bullock [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 02:34 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 Tell me that I am a MF'er does not mean what I immediately think of. Usually you call another person that type of name. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Thursday, November 08, 2007 12:16 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Upgrade to version 5.4 I am a MF'er and fully realize this (we always stayed 3-6 months behind current PTF levels) In my situation, I was addressing a problem that was supposedly addressed in 5.4.1.2 or I wouldn't have gone that far uplevel. Fortunately, the new problem is somewhat cosmetic/low-key. Kamran Rao [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 01:31 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 Rule of thumb - Always stay 1 version behind the latest and pay special attention to the release notes to the newer version and see if that applies to your environment or not. If useful then attempt to upgrade, otherwise stay where you are at until all the bugs are fixed. Kamran -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Thursday, November 08, 2007 1:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Upgrade to version 5.4 Well, I wouldn't go that far. I just upgraded my 5.3.x server to 5.4.1.2 and immediately found a problem that was introduced in 5.4/5.4.1 and won't be fixed until 5.4.2. YMMV Michael Green [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 01:09 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 As always, the latest is the greatest. On 11/8/07, Andy Huebner [EMAIL PROTECTED] wrote: We are about to upgrade TSM from 5.2.2.4 to a version of 5.4 on AIX 5.3. Is there a stable recommended version? Maybe 5.4.1.2? Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. -- Warm regards, Michael Green
Re: TSM Upgrade to version 5.4
What problem did you find? Is there a known defect list somewhere? Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Thursday, November 08, 2007 12:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Upgrade to version 5.4 Well, I wouldn't go that far. I just upgraded my 5.3.x server to 5.4.1.2 and immediately found a problem that was introduced in 5.4/5.4.1 and won't be fixed until 5.4.2. YMMV Michael Green [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 01:09 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 As always, the latest is the greatest. On 11/8/07, Andy Huebner [EMAIL PROTECTED] wrote: We are about to upgrade TSM from 5.2.2.4 to a version of 5.4 on AIX 5.3. Is there a stable recommended version? Maybe 5.4.1.2? Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. -- Warm regards, Michael Green This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: TSM Upgrade to version 5.4
Ahh, thanks for the clarification. My bad for dropping down into the gutter. :-) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Thursday, November 08, 2007 1:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Upgrade to version 5.4 I figured there were enough old timers on this list to figure out I was/am a M(ain) F(ramer) Ben Bullock [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 02:34 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 Tell me that I am a MF'er does not mean what I immediately think of. Usually you call another person that type of name. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Thursday, November 08, 2007 12:16 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Upgrade to version 5.4 I am a MF'er and fully realize this (we always stayed 3-6 months behind current PTF levels) In my situation, I was addressing a problem that was supposedly addressed in 5.4.1.2 or I wouldn't have gone that far uplevel. Fortunately, the new problem is somewhat cosmetic/low-key. Kamran Rao [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 01:31 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 Rule of thumb - Always stay 1 version behind the latest and pay special attention to the release notes to the newer version and see if that applies to your environment or not. If useful then attempt to upgrade, otherwise stay where you are at until all the bugs are fixed. Kamran -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Thursday, November 08, 2007 1:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Upgrade to version 5.4 Well, I wouldn't go that far. I just upgraded my 5.3.x server to 5.4.1.2 and immediately found a problem that was introduced in 5.4/5.4.1 and won't be fixed until 5.4.2. YMMV Michael Green [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 01:09 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 As always, the latest is the greatest. On 11/8/07, Andy Huebner [EMAIL PROTECTED] wrote: We are about to upgrade TSM from 5.2.2.4 to a version of 5.4 on AIX 5.3. Is there a stable recommended version? Maybe 5.4.1.2? Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. -- Warm regards, Michael Green
Re: TSM Upgrade to version 5.4
I guess in that case it applies either way... Kelly J. Lipp VP Manufacturing CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ben Bullock Sent: Thursday, November 08, 2007 1:37 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Upgrade to version 5.4 Ahh, thanks for the clarification. My bad for dropping down into the gutter. :-) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Thursday, November 08, 2007 1:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Upgrade to version 5.4 I figured there were enough old timers on this list to figure out I was/am a M(ain) F(ramer) Ben Bullock [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 02:34 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 Tell me that I am a MF'er does not mean what I immediately think of. Usually you call another person that type of name. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Thursday, November 08, 2007 12:16 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Upgrade to version 5.4 I am a MF'er and fully realize this (we always stayed 3-6 months behind current PTF levels) In my situation, I was addressing a problem that was supposedly addressed in 5.4.1.2 or I wouldn't have gone that far uplevel. Fortunately, the new problem is somewhat cosmetic/low-key. Kamran Rao [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 01:31 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 Rule of thumb - Always stay 1 version behind the latest and pay special attention to the release notes to the newer version and see if that applies to your environment or not. If useful then attempt to upgrade, otherwise stay where you are at until all the bugs are fixed. Kamran -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Thursday, November 08, 2007 1:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Upgrade to version 5.4 Well, I wouldn't go that far. I just upgraded my 5.3.x server to 5.4.1.2 and immediately found a problem that was introduced in 5.4/5.4.1 and won't be fixed until 5.4.2. YMMV Michael Green [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 01:09 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 As always, the latest is the greatest. On 11/8/07, Andy Huebner [EMAIL PROTECTED] wrote: We are about to upgrade TSM from 5.2.2.4 to a version of 5.4 on AIX 5.3. Is there a stable recommended version? Maybe 5.4.1.2? Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. -- Warm regards, Michael Green
Re: TSM Upgrade to version 5.4
Has this problem caused any issues with your server? Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Thursday, November 08, 2007 2:48 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Upgrade to version 5.4 This one: PK54980: ERROR ANR2706E AND EXCESSIVE ANRD MESSAGES WERE LOGGED IN ACTIVITY LOG AFTER A SCHEDULED CLIENT SESSION WAS TERMINATED. http://www-1.ibm.com/support/docview.wss?rs=663context=SSGSG7dc=DB550; uid=swg1PK54980loc=en_UScs=UTF-8lang=enrss=ct663tivoli I thought it interesting that under TSM Versions Affected:, it includes the as-of-yet-unreleased 5.4.2 Andy Huebner [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 03:37 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 What problem did you find? Is there a known defect list somewhere? Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Thursday, November 08, 2007 12:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Upgrade to version 5.4 Well, I wouldn't go that far. I just upgraded my 5.3.x server to 5.4.1.2 and immediately found a problem that was introduced in 5.4/5.4.1 and won't be fixed until 5.4.2. YMMV Michael Green [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 11/08/2007 01:09 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade to version 5.4 As always, the latest is the greatest. On 11/8/07, Andy Huebner [EMAIL PROTECTED] wrote: We are about to upgrade TSM from 5.2.2.4 to a version of 5.4 on AIX 5.3. Is there a stable recommended version? Maybe 5.4.1.2? Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. -- Warm regards, Michael Green This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: TSM Upgrade to version 5.4
Hi, Andy Huebner wrote: We are about to upgrade TSM from 5.2.2.4 to a version of 5.4 on AIX 5.3. Is there a stable recommended version? Maybe 5.4.1.2? We are running TSM 5.4.1.2 on AIX 5.3 for a few weeks now without any problems. -- Regards, Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470
Re: TSM Upgrade to V5.3.4.2
Um. It's not a patch in the sense that it has an APAR number, it's a patch in the sense that it isn't in a formal install package. Go to the FTP site and look in the TOOLS directory: ftp://ftp.software.ibm.com/storage/tivoli-storage-management/tools/ Select either WINDOWS or UNIX depending on where your TSM server runs. Download the files and read the README very CAREFULLY, there are several steps. After you copy the files, you shut down your server and enter a dsmserv runfile command to load the files, then bring your TSM server back up. It's in the instructions. I've installed the patch many times on both Windows and AIX, never had a problem. Happy TSM-ing! From: ADSM: Dist Stor Manager on behalf of Lamb, Charles P. Sent: Fri 5/25/2007 3:25 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Upgrade to V5.3.4.2 Our consultant recommended that we update to V5.4.3.2 for now and in the spring of '08, update to V5.4.x.x which will allow V5.4.x.x to mature more. We have loaded the TSM command line interface V5.4.0.4 on some PCs which has help our TSM operational personnel since they perform a lot of command line functions without having to use the ISC V6.0.1.1 media package software. I did not know there was an APAR to allow the old web GUI to work with V5.3/V5.4. What is the APAR number?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Friday, May 25, 2007 2:06 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Upgrade to V5.3.4.2 My biggest problem with the 5.3.4.2 ISC was the java-sometimes-pop-up window for the command line function; it didn't process output from scripts and command line the same way as the old admin GUI. I'm curious as to why you stopped with 5.3.4.2 instead of 5.4; the ISC 5.4 command-line window seems much better; queries and scripts come back pretty consistently the same as the old Admin GUI window. In the meantime, install the patch that lets you use the old web GUI with 5.3. (Doesn't work with IE7, but works fine with older IE and Firefox). Naturally it doesn't have any of the new function in it, but the old stuff works fine. And it works with 5.4. W From: ADSM: Dist Stor Manager on behalf of Lamb, Charles P. Sent: Wed 5/23/2007 4:07 PM To: ADSM-L@VM.MARIST.EDU Subject: TSM Upgrade to V5.3.4.2 We just upgraded from TSM V5.2.7.3 to V5.3.4.2. The TSM ISC software needs some work ( our e-mail will not work with the words I wanted to use). We installed the ISC version from the TSM V5.4 media pack which IBM sent me. Any word on updates to ISC software?? I am using command line to complete our daily TSM work since the ISC does not have the q ac function which the old java web software had (search on both txt and message). A lot of re-training for us since everything is moved around in the ISC software.
Re: TSM Upgrade to V5.3.4.2
Our consultant recommended that we update to V5.4.3.2 for now and in the spring of '08, update to V5.4.x.x which will allow V5.4.x.x to mature more. We have loaded the TSM command line interface V5.4.0.4 on some PCs which has help our TSM operational personnel since they perform a lot of command line functions without having to use the ISC V6.0.1.1 media package software. I did not know there was an APAR to allow the old web GUI to work with V5.3/V5.4. What is the APAR number?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Friday, May 25, 2007 2:06 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Upgrade to V5.3.4.2 My biggest problem with the 5.3.4.2 ISC was the java-sometimes-pop-up window for the command line function; it didn't process output from scripts and command line the same way as the old admin GUI. I'm curious as to why you stopped with 5.3.4.2 instead of 5.4; the ISC 5.4 command-line window seems much better; queries and scripts come back pretty consistently the same as the old Admin GUI window. In the meantime, install the patch that lets you use the old web GUI with 5.3. (Doesn't work with IE7, but works fine with older IE and Firefox). Naturally it doesn't have any of the new function in it, but the old stuff works fine. And it works with 5.4. W From: ADSM: Dist Stor Manager on behalf of Lamb, Charles P. Sent: Wed 5/23/2007 4:07 PM To: ADSM-L@VM.MARIST.EDU Subject: TSM Upgrade to V5.3.4.2 We just upgraded from TSM V5.2.7.3 to V5.3.4.2. The TSM ISC software needs some work ( our e-mail will not work with the words I wanted to use). We installed the ISC version from the TSM V5.4 media pack which IBM sent me. Any word on updates to ISC software?? I am using command line to complete our daily TSM work since the ISC does not have the q ac function which the old java web software had (search on both txt and message). A lot of re-training for us since everything is moved around in the ISC software.
Re: TSM Upgrade to V5.3.4.2
My biggest problem with the 5.3.4.2 ISC was the java-sometimes-pop-up window for the command line function; it didn't process output from scripts and command line the same way as the old admin GUI. I'm curious as to why you stopped with 5.3.4.2 instead of 5.4; the ISC 5.4 command-line window seems much better; queries and scripts come back pretty consistently the same as the old Admin GUI window. In the meantime, install the patch that lets you use the old web GUI with 5.3. (Doesn't work with IE7, but works fine with older IE and Firefox). Naturally it doesn't have any of the new function in it, but the old stuff works fine. And it works with 5.4. W From: ADSM: Dist Stor Manager on behalf of Lamb, Charles P. Sent: Wed 5/23/2007 4:07 PM To: ADSM-L@VM.MARIST.EDU Subject: TSM Upgrade to V5.3.4.2 We just upgraded from TSM V5.2.7.3 to V5.3.4.2. The TSM ISC software needs some work ( our e-mail will not work with the words I wanted to use). We installed the ISC version from the TSM V5.4 media pack which IBM sent me. Any word on updates to ISC software?? I am using command line to complete our daily TSM work since the ISC does not have the q ac function which the old java web software had (search on both txt and message). A lot of re-training for us since everything is moved around in the ISC software.
TSM Upgrade to V5.3.4.2
We just upgraded from TSM V5.2.7.3 to V5.3.4.2. The TSM ISC software needs some work ( our e-mail will not work with the words I wanted to use). We installed the ISC version from the TSM V5.4 media pack which IBM sent me. Any word on updates to ISC software?? I am using command line to complete our daily TSM work since the ISC does not have the q ac function which the old java web software had (search on both txt and message). A lot of re-training for us since everything is moved around in the ISC software.
Re: Antwort: [ADSM-L] TSM upgrade path Virus checked
Hi Dierk, I did'nt know there was a TSM 5.3.4.2 or 5.3.5 APAR. I checked the link below and couldn't find those. Is there another link? Tim ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/server/AIX/ Dierk Harbort wrote: Hello Nicholas, we went from 5.2.4 up to 5.3.3 on Linux, directly. No problems with server or nodes. For the moment there are APARS (see Tivoli APAR notification page ), they recommend to use 5.3.4.2, better 5.3.5. So you may look for that version on AIX. Regards, Dierk RODOLFICH, NICHOLAS NICHOLAS.RODOLFI An [EMAIL PROTECTED] ADSM-L@VM.MARIST.EDU Gesendet von: Kopie ADSM: Dist Stor ManagerThema [EMAIL PROTECTED] [ADSM-L] TSM upgrade path Virus .EDU checked 18.01.2007 16:53 Bitte antworten an ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU Hi Everyone, Thanks for your help!! One of our AIX TSM servers is running TSM 5.2.7. We had issues upgrading from 5.1.9 to a 5.2.x release but we got it going so I have left it alone for a couple of months so it could stabilize. We had to go through a couple of intermediary steps to get to 5.2.7. I now need to upgrade the system to a 5.3.x level. Does anyone know if there is a direct upgrade path from 5.2.7 to 5.3.x and if so what version I need to go to? Any gremlins or pains would be appreciated.. Thanks!! Regards, Nicholas Rodolfich POOLCORP Desk: (985)801-3038 Cell: (228)223-6777 mailto:[EMAIL PROTECTED] This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
Re: Antwort: [ADSM-L] TSM upgrade path Virus checked
I couldn't find any of these versions, either. Even checked patches and Passport.. Timothy Hughes [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 01/19/2007 10:48 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] Antwort: [ADSM-L] TSM upgrade path Virus checked Hi Dierk, I did'nt know there was a TSM 5.3.4.2 or 5.3.5 APAR. I checked the link below and couldn't find those. Is there another link? Tim ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/server/AIX/ Dierk Harbort wrote: Hello Nicholas, we went from 5.2.4 up to 5.3.3 on Linux, directly. No problems with server or nodes. For the moment there are APARS (see Tivoli APAR notification page ), they recommend to use 5.3.4.2, better 5.3.5. So you may look for that version on AIX. Regards, Dierk RODOLFICH, NICHOLAS NICHOLAS.RODOLFI An [EMAIL PROTECTED] ADSM-L@VM.MARIST.EDU Gesendet von: Kopie ADSM: Dist Stor Manager Thema [EMAIL PROTECTED] [ADSM-L] TSM upgrade path Virus .EDU checked 18.01.2007 16:53 Bitte antworten an ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU Hi Everyone, Thanks for your help!! One of our AIX TSM servers is running TSM 5.2.7. We had issues upgrading from 5.1.9 to a 5.2.x release but we got it going so I have left it alone for a couple of months so it could stabilize. We had to go through a couple of intermediary steps to get to 5.2.7. I now need to upgrade the system to a 5.3.x level. Does anyone know if there is a direct upgrade path from 5.2.7 to 5.3.x and if so what version I need to go to? Any gremlins or pains would be appreciated.. Thanks!! Regards, Nicholas Rodolfich POOLCORP Desk: (985)801-3038 Cell: (228)223-6777 mailto:[EMAIL PROTECTED] This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
TSM upgrade path
Hi Everyone, Thanks for your help!! One of our AIX TSM servers is running TSM 5.2.7. We had issues upgrading from 5.1.9 to a 5.2.x release but we got it going so I have left it alone for a couple of months so it could stabilize. We had to go through a couple of intermediary steps to get to 5.2.7. I now need to upgrade the system to a 5.3.x level. Does anyone know if there is a direct upgrade path from 5.2.7 to 5.3.x and if so what version I need to go to? Any gremlins or pains would be appreciated.. Thanks!! Regards, Nicholas Rodolfich POOLCORP Desk: (985)801-3038 Cell: (228)223-6777 mailto:[EMAIL PROTECTED] This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
Antwort: [ADSM-L] TSM upgrade path Virus checked
Hello Nicholas, we went from 5.2.4 up to 5.3.3 on Linux, directly. No problems with server or nodes. For the moment there are APARS (see Tivoli APAR notification page ), they recommend to use 5.3.4.2, better 5.3.5. So you may look for that version on AIX. Regards, Dierk RODOLFICH, NICHOLAS NICHOLAS.RODOLFI An [EMAIL PROTECTED] ADSM-L@VM.MARIST.EDU Gesendet von: Kopie ADSM: Dist Stor ManagerThema [EMAIL PROTECTED] [ADSM-L] TSM upgrade path Virus .EDU checked 18.01.2007 16:53 Bitte antworten an ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU Hi Everyone, Thanks for your help!! One of our AIX TSM servers is running TSM 5.2.7. We had issues upgrading from 5.1.9 to a 5.2.x release but we got it going so I have left it alone for a couple of months so it could stabilize. We had to go through a couple of intermediary steps to get to 5.2.7. I now need to upgrade the system to a 5.3.x level. Does anyone know if there is a direct upgrade path from 5.2.7 to 5.3.x and if so what version I need to go to? Any gremlins or pains would be appreciated.. Thanks!! Regards, Nicholas Rodolfich POOLCORP Desk: (985)801-3038 Cell: (228)223-6777 mailto:[EMAIL PROTECTED] This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
Re: TSM Upgrade from 5.1.6 to 5.3
Rich - I'm running TSM 5.1.5 BAclients on AIX 4.3.3 to our AIX TSM Server 5.3.1.0. It's been running without fail for about the last 8 months. This is definitely NOT a supported or certified configuration. On the other hand it works. We ended up with this configuration after upgrading our W2K/W2K3 nodes to TSM 5.3.x and our AIX TSM server to 5.3.x and our AIX nodes to TSM 5.2.x. We couldn't update several AIX boxes from 4.3.3 so we just left them alone and they happily kept right on doing backups and the occasional restore. ltp Kauffman, Tom [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 01/16/2006 10:57 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM Upgrade from 5.1.6 to 5.3 Rich -- FWIW, I'm currently running TSM 5.1.6.3 on AIX 5.3 64-bit with no apparent problems. We went from AIX 5.1 to AIX 5.3 in August. I'm in the process of working out a simplified test environment for TSM 5.3, with plans to upgrade next week if all goes well. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Mochnaczewski Sent: Monday, January 16, 2006 1:47 PM To: ADSM-L@VM.MARIST.EDU Subject: TSM Upgrade from 5.1.6 to 5.3 Hi Everybody, I'm currently planning an upgrade of TSM 5.1.6 on AIX 4.3.3 to TSM 5.3 on AIX 5.2 . Since this will be an inplace upgrade on the same server, is TSM 5.1.6 supported on AIX 5.2 ? I know that IBM does not support 5.1.6 , but I have a very tight upgrade window and need to do the upgrade in stages for both the OS and TSM version over the course of a few Sundays as I do not see going from 5.1.6/4.3.3 to 5.3/5.3 in on shot. i.e. 1) First Sunday : upgrade OS from 4.3.3 to 5.2 2) Following Sunday : Upgrade TSM 5.1.6 to 5.2 3) Following Sunday : Upgrade TSM 5.2 to 5.3 Rich
TSM Upgrade from 5.1.6 to 5.3
Hi Everybody, I'm currently planning an upgrade of TSM 5.1.6 on AIX 4.3.3 to TSM 5.3 on AIX 5.2 . Since this will be an inplace upgrade on the same server, is TSM 5.1.6 supported on AIX 5.2 ? I know that IBM does not support 5.1.6 , but I have a very tight upgrade window and need to do the upgrade in stages for both the OS and TSM version over the course of a few Sundays as I do not see going from 5.1.6/4.3.3 to 5.3/5.3 in on shot. i.e. 1) First Sunday : upgrade OS from 4.3.3 to 5.2 2) Following Sunday : Upgrade TSM 5.1.6 to 5.2 3) Following Sunday : Upgrade TSM 5.2 to 5.3 Rich
Re: TSM Upgrade from 5.1.6 to 5.3
Rich -- FWIW, I'm currently running TSM 5.1.6.3 on AIX 5.3 64-bit with no apparent problems. We went from AIX 5.1 to AIX 5.3 in August. I'm in the process of working out a simplified test environment for TSM 5.3, with plans to upgrade next week if all goes well. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Mochnaczewski Sent: Monday, January 16, 2006 1:47 PM To: ADSM-L@VM.MARIST.EDU Subject: TSM Upgrade from 5.1.6 to 5.3 Hi Everybody, I'm currently planning an upgrade of TSM 5.1.6 on AIX 4.3.3 to TSM 5.3 on AIX 5.2 . Since this will be an inplace upgrade on the same server, is TSM 5.1.6 supported on AIX 5.2 ? I know that IBM does not support 5.1.6 , but I have a very tight upgrade window and need to do the upgrade in stages for both the OS and TSM version over the course of a few Sundays as I do not see going from 5.1.6/4.3.3 to 5.3/5.3 in on shot. i.e. 1) First Sunday : upgrade OS from 4.3.3 to 5.2 2) Following Sunday : Upgrade TSM 5.1.6 to 5.2 3) Following Sunday : Upgrade TSM 5.2 to 5.3 Rich
Re: TSM Upgrade from 5.1.6 to 5.3
On Jan 16, 2006, at 1:46 PM, Richard Mochnaczewski wrote: ...is TSM 5.1.6 supported on AIX 5.2... That's easily looked up via the TSM Support Page, http://www.ibm.com/software/sysmgmt/products/support/ IBMTivoliStorageManager.html under Server Requirements.
Re: TSM Upgrade from 5.1.6 to 5.3
We are currently running TSM 5.1.6.5 on AIX 5.2 and it works fine. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] On Mon, 16 Jan 2006, Richard Mochnaczewski wrote: Hi Everybody, I'm currently planning an upgrade of TSM 5.1.6 on AIX 4.3.3 to TSM 5.3 on AIX 5.2 . Since this will be an inplace upgrade on the same server, is TSM 5.1.6 supported on AIX 5.2 ? I know that IBM does not support 5.1.6 , but I have a very tight upgrade window and need to do the upgrade in stages for both the OS and TSM version over the course of a few Sundays as I do not see going from 5.1.6/4.3.3 to 5.3/5.3 in on shot. i.e. 1) First Sunday : upgrade OS from 4.3.3 to 5.2 2) Following Sunday : Upgrade TSM 5.1.6 to 5.2 3) Following Sunday : Upgrade TSM 5.2 to 5.3 Rich
Solaris TSM Upgrade
Afternoon all Currently investigating upgrading from TSM5.1 to 5.3.x, O/S Solaris 5.9. I have searched around the ftp site though having problems locating the 5.3.x server software can anyone point me in the right direction please? Regards Mark Scott
Re: Solaris TSM Upgrade
Hi Scott! Since TSM 5.3 requires a new license, you cannot download the base code from the FTP server. If your company is are a Passport Advantage member, you can download the base code from there. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Scott, Mark William [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 13, 2005 10:16 To: ADSM-L@VM.MARIST.EDU Subject: Solaris TSM Upgrade Afternoon all Currently investigating upgrading from TSM5.1 to 5.3.x, O/S Solaris 5.9. I have searched around the ftp site though having problems locating the 5.3.x server software can anyone point me in the right direction please? Regards Mark Scott ** 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. **
TSM Upgrade
Afternoon all Currently researching to upgrade from TSM 5.1 to 5.3, O/S Solaris 5.9, Sun L180 re-badged Stortek library including a replication at a DR site were we run a hourly copy. Primary lto tape to disk, disk to lto tape. Searching through adsm.org etc does anyone know of any issues? Look forward to you responses Regards Mark
Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1
Hi Richard! Thank you very much for this link! According to this article I do have a disk performance problem. One should be able to expire more than a 1000 objects per second... Indeed, during expiration disk utilization is way over 20% during expiration, so I guess I should spread my database across more disks. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Richard Sims [mailto:[EMAIL PROTECTED] Sent: Friday, March 26, 2004 15:55 To: [EMAIL PROTECTED] Subject: Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1 Just because I'm currently trying to boost expiration processing: I see your database is rather large, how long did it take you to expire those 23194393 objects? I really tried almost everything, from moving to 15k speed disks, multiple database volumes, moving to RAW's, the best I have seen in my environment is 60 objects per second. ... In the context of this discussion, the following doc makes some interesting observations on disk performance and expectations: http://www.ibm.com/support/docview.wss?uid=swg21141810 Richard Simshttp://people.bu.edu/rbs ** 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. **
Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1
Hi Luke! Just because I'm currently trying to boost expiration processing: I see your database is rather large, how long did it take you to expire those 23194393 objects? I really tried almost everything, from moving to 15k speed disks, multiple database volumes, moving to RAW's, the best I have seen in my environment is 60 objects per second. I posted a question some time ago (2002) where I requested for other people's performances, Tom Kauffman was the winner at that time with a dazzling 3112 objects per second! Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Luke Dahl [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 21:39 To: [EMAIL PROTECTED] Subject: Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1 Hi Mark, Output from q db f=d: Available Space (MB): 118,780 Assigned Capacity (MB): 70,000 Maximum Extension (MB): 48,780 Maximum Reduction (MB): 15,924 Page Size (bytes): 4,096 Total Usable Pages: 17,920,000 Used Pages: 11,215,255 Pct Util: 62.6 Max. Pct Util: 77.3 Physical Volumes: 1 Buffer Pool Pages: 32,768 Total Buffer Requests: 2,151,221,843 Cache Hit Pct.: 99.04 Cache Wait Pct.: 0.00 Backup in Progress?: No Type of Backup In Progress: Incrementals Since Last Full: 0 Changed Since Last Backup (MB): 2,785.80 Percentage Changed: 6.36 Last Complete Backup Date/Time: 03/24/04 17:33:13 This is the standard amount of expiration we see: 03/14/04 17:27:07 ANR0812I Inventory file expiration process 1692 completed: examined 23194393 objects, deleting 1690917 backup objec cts, 0 archive objects, 0 DB backup volumes, and 0 recov very plan files. 0 errors were encountered. This is currently running: Process Process Description Status s Number - 26 Expiration Examined 22853888 objects, deleting 20518954 bac ckup objects, 0 archive objects, 0 DB backup vo olumes, 0 recovery plan files; 1 errors encount tered. I don't think the policies were correctly expiring data prior to the upgrade. We've had numerous nodes that seemed to be storing much more than their policy dictated. We tried to force expiration on the files and it didn't seem to make much of a difference. Unfortunately we've been tweaking policies and trying to force a lot of data to drop off prior to the upgrade so I can't point to any particular reason why expiration is now expiring so much data. You can see the db size has dropped as well due to the expiration - and we performed an unload/reload less than a month ago prior to the upgrade. Being the db volume is one volume it could be disk contention, but it's a raw volume fiber attached (Sun T-3's). Luke Stapleton, Mark wrote: From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Luke Dahl We upgraded our TSM Server (Solaris 9) from 5.1.6.4 to 5.2.2.1 last week. Prior to the upgrade our expiration usually lasted about 24 hours (53Gb database). It would generally post results like this: examined 16446439 objects, deleting 59582 backup objects Our 3494 library showed est. capacity of 60Tb and approximately 88 pct. util. What is your db's cache hit ratio? 24 hours for a 53GB database is manifestly too long. It should get through expiration in 2-3 hours. Give us the output from Q DB F=D. Any idea why expiration wasn't running properly prior to the upgrade? Data integrity looks good but we've just cleared out loads of space. I don't recall a known bug in expiration processing in 5.1.6.4 but may have missed something. Thanks for your thoughts and input. How, exactly, did you clear out loads of space? -- Mark Stapleton ** 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. **
Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1
I have 4 rather large tsm servers, db over 30 gb. 2 are AIX, 2 are sun. The performance on the 2 aix boxes is similar. One server is very old, installed in 97, db is 60 db, and goes through 12 million objects, deleting between 300,00 and 1 million objects. 3000 objects/sec examined, but between 70 and 100 deleted. Expiration lasts between 60 and 90 minutes. The other aix server is brand new. Db is 40 gb, moslty du to 2 imap servers whose backups are kept 180 days (OUCH!!). Expiration goes through 150,000 objects, deleting 100,000. 200 objects examined/sec, 150 deleted. The old server is a f80, the new one a p615, soon to be a p630. As for the SUN servers, performance is nowhere near as good. I can't get more than 40 objects/second, examined or deleted. I moved the database on raw volumes, didn't help much. I can,T seem to get these servers to perform well. The 2 instances are on a 480 with 2 cpu's. Disks are the same as the AIX Guillaume Gilbert Backup Administrator CGI - ITM (514) 415-3000 x5091 [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Loon, E.J. van - SPLXM Sent: Friday, March 26, 2004 8:23 AM To: [EMAIL PROTECTED] Subject: Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1 Hi Luke! Just because I'm currently trying to boost expiration processing: I see your database is rather large, how long did it take you to expire those 23194393 objects? I really tried almost everything, from moving to 15k speed disks, multiple database volumes, moving to RAW's, the best I have seen in my environment is 60 objects per second. I posted a question some time ago (2002) where I requested for other people's performances, Tom Kauffman was the winner at that time with a dazzling 3112 objects per second! Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Luke Dahl [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 21:39 To: [EMAIL PROTECTED] Subject: Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1 Hi Mark, Output from q db f=d: Available Space (MB): 118,780 Assigned Capacity (MB): 70,000 Maximum Extension (MB): 48,780 Maximum Reduction (MB): 15,924 Page Size (bytes): 4,096 Total Usable Pages: 17,920,000 Used Pages: 11,215,255 Pct Util: 62.6 Max. Pct Util: 77.3 Physical Volumes: 1 Buffer Pool Pages: 32,768 Total Buffer Requests: 2,151,221,843 Cache Hit Pct.: 99.04 Cache Wait Pct.: 0.00 Backup in Progress?: No Type of Backup In Progress: Incrementals Since Last Full: 0 Changed Since Last Backup (MB): 2,785.80 Percentage Changed: 6.36 Last Complete Backup Date/Time: 03/24/04 17:33:13 This is the standard amount of expiration we see: 03/14/04 17:27:07 ANR0812I Inventory file expiration process 1692 completed: examined 23194393 objects, deleting 1690917 backup objec cts, 0 archive objects, 0 DB backup volumes, and 0 recov very plan files. 0 errors were encountered. This is currently running: Process Process Description Status s Number - 26 Expiration Examined 22853888 objects, deleting 20518954 bac ckup objects, 0 archive objects, 0 DB backup vo olumes, 0 recovery plan files; 1 errors encount tered. I don't think the policies were correctly expiring data prior to the upgrade. We've had numerous nodes that seemed to be storing much more than their policy dictated. We tried to force expiration on the files and it didn't seem to make much of a difference. Unfortunately we've been tweaking policies and trying to force a lot of data to drop off prior to the upgrade so I can't point to any particular reason why expiration is now expiring so much data. You can see the db size has dropped as well due to the expiration - and we performed an unload/reload less than a month ago prior to the upgrade. Being the db volume is one volume it could be disk contention, but it's a raw volume fiber attached (Sun T-3's). Luke Stapleton, Mark wrote: From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Luke Dahl We upgraded our TSM Server (Solaris 9) from 5.1.6.4 to 5.2.2.1 last week. Prior to the upgrade our expiration usually lasted about 24 hours (53Gb database). It would generally post results like this: examined 16446439 objects, deleting 59582 backup objects Our 3494 library showed est. capacity of 60Tb and approximately 88 pct. util. What is your db's
Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1
Sent this too fast... Must have hit the a wrong key... Not enough coffee yet I have 4 rather large tsm servers, db over 30 gb. 2 are AIX, 2 are sun. The performance on the 2 aix boxes is similar. One server is very old, installed in 97, db is 60 db, and goes through 12 million objects, deleting between 300,000 and 1 million objects. 3000 objects/sec examined, but between 70 and 100 deleted. Expiration lasts between 60 and 90 minutes. The other aix server is brand new. Db is 40 gb, moslty du to 2 imap servers whose backups are kept 180 days (OUCH!!). Expiration goes through 150,000 objects, deleting 100,000. 200 objects examined/sec, 150 deleted. The old server is a f80, the new one a p615, soon to be a p630. As for the SUN servers, performance is nowhere near as good. I can't get more than 40 objects/second, examined or deleted. I moved the database on raw volumes, didn't help much. I can't seem to get these servers to perform well. The 2 instances are on a 480 with 2 cpu's. Disks are the same as the AIX servers (HDS 9960). Is anyone getting good expiration performance on SUN servers. If so, how are you setup? Guillaume Gilbert Backup Administrator CGI - ITM (514) 415-3000 x5091 [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Loon, E.J. van - SPLXM Sent: Friday, March 26, 2004 8:23 AM To: [EMAIL PROTECTED] Subject: Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1 Hi Luke! Just because I'm currently trying to boost expiration processing: I see your database is rather large, how long did it take you to expire those 23194393 objects? I really tried almost everything, from moving to 15k speed disks, multiple database volumes, moving to RAW's, the best I have seen in my environment is 60 objects per second. I posted a question some time ago (2002) where I requested for other people's performances, Tom Kauffman was the winner at that time with a dazzling 3112 objects per second! Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Luke Dahl [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 21:39 To: [EMAIL PROTECTED] Subject: Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1 Hi Mark, Output from q db f=d: Available Space (MB): 118,780 Assigned Capacity (MB): 70,000 Maximum Extension (MB): 48,780 Maximum Reduction (MB): 15,924 Page Size (bytes): 4,096 Total Usable Pages: 17,920,000 Used Pages: 11,215,255 Pct Util: 62.6 Max. Pct Util: 77.3 Physical Volumes: 1 Buffer Pool Pages: 32,768 Total Buffer Requests: 2,151,221,843 Cache Hit Pct.: 99.04 Cache Wait Pct.: 0.00 Backup in Progress?: No Type of Backup In Progress: Incrementals Since Last Full: 0 Changed Since Last Backup (MB): 2,785.80 Percentage Changed: 6.36 Last Complete Backup Date/Time: 03/24/04 17:33:13 This is the standard amount of expiration we see: 03/14/04 17:27:07 ANR0812I Inventory file expiration process 1692 completed: examined 23194393 objects, deleting 1690917 backup objec cts, 0 archive objects, 0 DB backup volumes, and 0 recov very plan files. 0 errors were encountered. This is currently running: Process Process Description Status s Number - 26 Expiration Examined 22853888 objects, deleting 20518954 bac ckup objects, 0 archive objects, 0 DB backup vo olumes, 0 recovery plan files; 1 errors encount tered. I don't think the policies were correctly expiring data prior to the upgrade. We've had numerous nodes that seemed to be storing much more than their policy dictated. We tried to force expiration on the files and it didn't seem to make much of a difference. Unfortunately we've been tweaking policies and trying to force a lot of data to drop off prior to the upgrade so I can't point to any particular reason why expiration is now expiring so much data. You can see the db size has dropped as well due to the expiration - and we performed an unload/reload less than a month ago prior to the upgrade. Being the db volume is one volume it could be disk contention, but it's a raw volume fiber attached (Sun T-3's). Luke Stapleton, Mark wrote: From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Luke Dahl We upgraded our TSM Server (Solaris 9) from 5.1.6.4 to 5.2.2.1 last week. Prior to the upgrade our expiration usually lasted about 24 hours (53Gb database). It would generally post
Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1
Hi Eric, From our activity log: 03/20/04 06:00:07 ANR0811I Inventory client file expiration started as proc cess 26. (SESSION: 5656, PROCESS: 26) 03/25/04 17:24:44 ANR0812I Inventory file expiration process 26 completed: examined 23979559 objects, deleting 21479290 backup obj jects, 0 archive objects, 0 DB backup volumes, and 0 rec covery plan files. 1 errors were encountered. (SESSION: 5656, PROCESS: 26) 03/25/04 17:24:44 ANR0987I Process 26 for EXPIRE INVENTORY running in the B BACKGROUND processed 21479290 items with a completion st tate of FAILURE at 17:24:44. (SESSION: 5656, PROCESS: 26) We've seen much better *overall* performance after moving to raw volumes, but nowhere near what we saw on two very old AIX boxes. We're running a Sun 420R with three cpu's. Load averages nightly peak around 20. We're moving to two Sun V480's with two cpu's to start. We haven't run expiration yet again but I'm hoping it doesn't take nearly as long. I'm still confused as to why after the upgrade we're seeing this. If it's significantly different the next time around I'll report to the list with my findings. Good luck! Luke Loon, E.J. van - SPLXM wrote: Hi Luke! Just because I'm currently trying to boost expiration processing: I see your database is rather large, how long did it take you to expire those 23194393 objects? I really tried almost everything, from moving to 15k speed disks, multiple database volumes, moving to RAW's, the best I have seen in my environment is 60 objects per second. I posted a question some time ago (2002) where I requested for other people's performances, Tom Kauffman was the winner at that time with a dazzling 3112 objects per second! Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Luke Dahl [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 21:39 To: [EMAIL PROTECTED] Subject: Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1 Hi Mark, Output from q db f=d: Available Space (MB): 118,780 Assigned Capacity (MB): 70,000 Maximum Extension (MB): 48,780 Maximum Reduction (MB): 15,924 Page Size (bytes): 4,096 Total Usable Pages: 17,920,000 Used Pages: 11,215,255 Pct Util: 62.6 Max. Pct Util: 77.3 Physical Volumes: 1 Buffer Pool Pages: 32,768 Total Buffer Requests: 2,151,221,843 Cache Hit Pct.: 99.04 Cache Wait Pct.: 0.00 Backup in Progress?: No Type of Backup In Progress: Incrementals Since Last Full: 0 Changed Since Last Backup (MB): 2,785.80 Percentage Changed: 6.36 Last Complete Backup Date/Time: 03/24/04 17:33:13 This is the standard amount of expiration we see: 03/14/04 17:27:07 ANR0812I Inventory file expiration process 1692 completed: examined 23194393 objects, deleting 1690917 backup objec cts, 0 archive objects, 0 DB backup volumes, and 0 recov very plan files. 0 errors were encountered. This is currently running: Process Process Description Status s Number - 26 Expiration Examined 22853888 objects, deleting 20518954 bac ckup objects, 0 archive objects, 0 DB backup vo olumes, 0 recovery plan files; 1 errors encount tered. I don't think the policies were correctly expiring data prior to the upgrade. We've had numerous nodes that seemed to be storing much more than their policy dictated. We tried to force expiration on the files and it didn't seem to make much of a difference. Unfortunately we've been tweaking policies and trying to force a lot of data to drop off prior to the upgrade so I can't point to any particular reason why expiration is now expiring so much data. You can see the db size has dropped as well due to the expiration - and we performed an unload/reload less than a month ago prior to the upgrade. Being the db volume is one volume it could be disk contention, but it's a raw volume fiber attached (Sun T-3's). Luke Stapleton, Mark wrote: From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Luke Dahl We upgraded our TSM Server (Solaris 9) from 5.1.6.4 to 5.2.2.1 last week. Prior to the upgrade our expiration usually lasted about 24 hours (53Gb database). It would generally post results like this: examined 16446439 objects, deleting 59582 backup objects Our 3494 library showed est. capacity of 60Tb and approximately 88 pct. util. What
Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1
Just because I'm currently trying to boost expiration processing: I see your database is rather large, how long did it take you to expire those 23194393 objects? I really tried almost everything, from moving to 15k speed disks, multiple database volumes, moving to RAW's, the best I have seen in my environment is 60 objects per second. ... In the context of this discussion, the following doc makes some interesting observations on disk performance and expectations: http://www.ibm.com/support/docview.wss?uid=swg21141810 Richard Simshttp://people.bu.edu/rbs
Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1
Although your cache hit pct is great, the most obvious thing I see is that you just have ONE physical volume for this size DB! Spreading this size DB out over multiple volumes will probably increase your performance. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] [EMAIL PROTECTED] 03/25/04 03:38PM Hi Mark, Output from q db f=d: Available Space (MB): 118,780 Assigned Capacity (MB): 70,000 Maximum Extension (MB): 48,780 Maximum Reduction (MB): 15,924 Page Size (bytes): 4,096 Total Usable Pages: 17,920,000 Used Pages: 11,215,255 Pct Util: 62.6 Max. Pct Util: 77.3 Physical Volumes: 1 Buffer Pool Pages: 32,768 Total Buffer Requests: 2,151,221,843 Cache Hit Pct.: 99.04 Cache Wait Pct.: 0.00 Backup in Progress?: No Type of Backup In Progress: Incrementals Since Last Full: 0 Changed Since Last Backup (MB): 2,785.80 Percentage Changed: 6.36 Last Complete Backup Date/Time: 03/24/04 17:33:13 This is the standard amount of expiration we see: 03/14/04 17:27:07 ANR0812I Inventory file expiration process 1692 completed: examined 23194393 objects, deleting 1690917 backup objec cts, 0 archive objects, 0 DB backup volumes, and 0 recov very plan files. 0 errors were encountered. This is currently running: Process Process Description Status s Number - 26 Expiration Examined 22853888 objects, deleting 20518954 bac ckup objects, 0 archive objects, 0 DB backup vo olumes, 0 recovery plan files; 1 errors encount tered. I don't think the policies were correctly expiring data prior to the upgrade. We've had numerous nodes that seemed to be storing much more than their policy dictated. We tried to force expiration on the files and it didn't seem to make much of a difference. Unfortunately we've been tweaking policies and trying to force a lot of data to drop off prior to the upgrade so I can't point to any particular reason why expiration is now expiring so much data. You can see the db size has dropped as well due to the expiration - and we performed an unload/reload less than a month ago prior to the upgrade. Being the db volume is one volume it could be disk contention, but it's a raw volume fiber attached (Sun T-3's). Luke Stapleton, Mark wrote: From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Luke Dahl We upgraded our TSM Server (Solaris 9) from 5.1.6.4 to 5.2.2.1 last week. Prior to the upgrade our expiration usually lasted about 24 hours (53Gb database). It would generally post results like this: examined 16446439 objects, deleting 59582 backup objects Our 3494 library showed est. capacity of 60Tb and approximately 88 pct. util. What is your db's cache hit ratio? 24 hours for a 53GB database is manifestly too long. It should get through expiration in 2-3 hours. Give us the output from Q DB F=D. Any idea why expiration wasn't running properly prior to the upgrade? Data integrity looks good but we've just cleared out loads of space. I don't recall a known bug in expiration processing in 5.1.6.4 but may have missed something. Thanks for your thoughts and input. How, exactly, did you clear out loads of space? -- Mark Stapleton ## 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. ##
Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1
Hi All, We upgraded our TSM Server (Solaris 9) from 5.1.6.4 to 5.2.2.1 last week. Prior to the upgrade our expiration usually lasted about 24 hours (53Gb database). It would generally post results like this: examined 16446439 objects, deleting 59582 backup objects Our 3494 library showed est. capacity of 60Tb and approximately 88 pct. util. After the upgrade expiration has been running for nearly three days, is still running, and output from q pro: Examined 22715496 objects, deleting 20413162 bacckup objects Our library now shows: Storage PoDevice ClEstimated Pct Pct ool Name lass NameCapacity Util Mig TAPEPOOL 3590 60,367,55122.293.5 Any idea why expiration wasn't running properly prior to the upgrade? Data integrity looks good but we've just cleared out loads of space. I don't recall a known bug in expiration processing in 5.1.6.4 but may have missed something. Thanks for your thoughts and input. Luke Dahl NASA - Jet Propulsion Laboratory 818-354-7117
Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Luke Dahl We upgraded our TSM Server (Solaris 9) from 5.1.6.4 to 5.2.2.1 last week. Prior to the upgrade our expiration usually lasted about 24 hours (53Gb database). It would generally post results like this: examined 16446439 objects, deleting 59582 backup objects Our 3494 library showed est. capacity of 60Tb and approximately 88 pct. util. What is your db's cache hit ratio? 24 hours for a 53GB database is manifestly too long. It should get through expiration in 2-3 hours. Give us the output from Q DB F=D. Any idea why expiration wasn't running properly prior to the upgrade? Data integrity looks good but we've just cleared out loads of space. I don't recall a known bug in expiration processing in 5.1.6.4 but may have missed something. Thanks for your thoughts and input. How, exactly, did you clear out loads of space? -- Mark Stapleton
Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1
Hi Mark, Output from q db f=d: Available Space (MB): 118,780 Assigned Capacity (MB): 70,000 Maximum Extension (MB): 48,780 Maximum Reduction (MB): 15,924 Page Size (bytes): 4,096 Total Usable Pages: 17,920,000 Used Pages: 11,215,255 Pct Util: 62.6 Max. Pct Util: 77.3 Physical Volumes: 1 Buffer Pool Pages: 32,768 Total Buffer Requests: 2,151,221,843 Cache Hit Pct.: 99.04 Cache Wait Pct.: 0.00 Backup in Progress?: No Type of Backup In Progress: Incrementals Since Last Full: 0 Changed Since Last Backup (MB): 2,785.80 Percentage Changed: 6.36 Last Complete Backup Date/Time: 03/24/04 17:33:13 This is the standard amount of expiration we see: 03/14/04 17:27:07 ANR0812I Inventory file expiration process 1692 completed: examined 23194393 objects, deleting 1690917 backup objec cts, 0 archive objects, 0 DB backup volumes, and 0 recov very plan files. 0 errors were encountered. This is currently running: Process Process Description Status s Number - 26 Expiration Examined 22853888 objects, deleting 20518954 bac ckup objects, 0 archive objects, 0 DB backup vo olumes, 0 recovery plan files; 1 errors encount tered. I don't think the policies were correctly expiring data prior to the upgrade. We've had numerous nodes that seemed to be storing much more than their policy dictated. We tried to force expiration on the files and it didn't seem to make much of a difference. Unfortunately we've been tweaking policies and trying to force a lot of data to drop off prior to the upgrade so I can't point to any particular reason why expiration is now expiring so much data. You can see the db size has dropped as well due to the expiration - and we performed an unload/reload less than a month ago prior to the upgrade. Being the db volume is one volume it could be disk contention, but it's a raw volume fiber attached (Sun T-3's). Luke Stapleton, Mark wrote: From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Luke Dahl We upgraded our TSM Server (Solaris 9) from 5.1.6.4 to 5.2.2.1 last week. Prior to the upgrade our expiration usually lasted about 24 hours (53Gb database). It would generally post results like this: examined 16446439 objects, deleting 59582 backup objects Our 3494 library showed est. capacity of 60Tb and approximately 88 pct. util. What is your db's cache hit ratio? 24 hours for a 53GB database is manifestly too long. It should get through expiration in 2-3 hours. Give us the output from Q DB F=D. Any idea why expiration wasn't running properly prior to the upgrade? Data integrity looks good but we've just cleared out loads of space. I don't recall a known bug in expiration processing in 5.1.6.4 but may have missed something. Thanks for your thoughts and input. How, exactly, did you clear out loads of space? -- Mark Stapleton
TSM Upgrade to 5.2 from TSM 4.2 on an AIX 5.1 Server
Hello, I try to get these info from IBM but they say they could not help me unless I run into problems while doing it. Could you help? Are they any documents in how to install TSM 5.1.7.3? We have window clients. Do I install TSM 5.1 base and then apply maintenances? environment: AIX 5.1 TSM 4.2.1.9 server IBM H50 359x Library 4 3590 tape drives Also in my case with a cloned rootvg, could I do the db backup as follows: backup db type=full devclass=3590 backup devconfig filename=devconfig.date backup volhistory filename=volhistory.date Where do I get the backup tape volser, from the activity log? How do I eject this backup tape from the library? We have 349x library and drives. And if I need to back out from the migration, could I just do a restore of this backup tape by issuing: dsmserv restore db volumes=volser(from the backup) devclass=3590 commit=yes I need to write up a plan for our migration. Please advise. Thanks, Helen Tam
Re: TSM Upgrade to 5.2 from TSM 4.2 on an AIX 5.1 Server
We recently went from 4.1.6 to 5.1.7. The readme in 5.1.7 stated there were significant upgrade db perf in 5.1.7 and if you are upgrading from 4.x go to 5.1.7 then install lic from 5.1.x base. This worked really well for us, your other procedures are good as well. (Backup db etc) -Original Message- From: Helen Tam [mailto:[EMAIL PROTECTED] Sent: Thursday, December 18, 2003 1:15 PM To: [EMAIL PROTECTED] Subject: TSM Upgrade to 5.2 from TSM 4.2 on an AIX 5.1 Server Hello, I try to get these info from IBM but they say they could not help me unless I run into problems while doing it. Could you help? Are they any documents in how to install TSM 5.1.7.3? We have window clients. Do I install TSM 5.1 base and then apply maintenances? environment: AIX 5.1 TSM 4.2.1.9 server IBM H50 359x Library 4 3590 tape drives Also in my case with a cloned rootvg, could I do the db backup as follows: backup db type=full devclass=3590 backup devconfig filename=devconfig.date backup volhistory filename=volhistory.date Where do I get the backup tape volser, from the activity log? How do I eject this backup tape from the library? We have 349x library and drives. And if I need to back out from the migration, could I just do a restore of this backup tape by issuing: dsmserv restore db volumes=volser(from the backup) devclass=3590 commit=yes I need to write up a plan for our migration. Please advise. Thanks, Helen Tam
Re: TSM Upgrade to 5.2 from TSM 4.2 on an AIX 5.1 Server
Disregard. .. last note... just noticed you were going to 5.2... Doh -Original Message- From: Helen Tam [mailto:[EMAIL PROTECTED] Sent: Thursday, December 18, 2003 1:15 PM To: [EMAIL PROTECTED] Subject: TSM Upgrade to 5.2 from TSM 4.2 on an AIX 5.1 Server Hello, I try to get these info from IBM but they say they could not help me unless I run into problems while doing it. Could you help? Are they any documents in how to install TSM 5.1.7.3? We have window clients. Do I install TSM 5.1 base and then apply maintenances? environment: AIX 5.1 TSM 4.2.1.9 server IBM H50 359x Library 4 3590 tape drives Also in my case with a cloned rootvg, could I do the db backup as follows: backup db type=full devclass=3590 backup devconfig filename=devconfig.date backup volhistory filename=volhistory.date Where do I get the backup tape volser, from the activity log? How do I eject this backup tape from the library? We have 349x library and drives. And if I need to back out from the migration, could I just do a restore of this backup tape by issuing: dsmserv restore db volumes=volser(from the backup) devclass=3590 commit=yes I need to write up a plan for our migration. Please advise. Thanks, Helen Tam
Re: TSM Upgrade to 5.2 from TSM 4.2 on an AIX 5.1 Server
Charles, Your comment is good because IBM recommends us to go to AIX 5.1.7 first because of the window clients. We have a small number of window clients, less than 10. Have you ever done a restore of the TSM database? I like to have this info in case I have to back out the migration. I was told that IBM no longer support upgrade questions. The service ended this October. Any notes from your upgrade would be appreciated. Thanks, Helen At 01:15 PM 12/18/2003 -0600, you wrote: We recently went from 4.1.6 to 5.1.7. The readme in 5.1.7 stated there were significant upgrade db perf in 5.1.7 and if you are upgrading from 4.x go to 5.1.7 then install lic from 5.1.x base. This worked really well for us, your other procedures are good as well. (Backup db etc) -Original Message- From: Helen Tam [mailto:[EMAIL PROTECTED] Sent: Thursday, December 18, 2003 1:15 PM To: [EMAIL PROTECTED] Subject: TSM Upgrade to 5.2 from TSM 4.2 on an AIX 5.1 Server Hello, I try to get these info from IBM but they say they could not help me unless I run into problems while doing it. Could you help? Are they any documents in how to install TSM 5.1.7.3? We have window clients. Do I install TSM 5.1 base and then apply maintenances? environment: AIX 5.1 TSM 4.2.1.9 server IBM H50 359x Library 4 3590 tape drives Also in my case with a cloned rootvg, could I do the db backup as follows: backup db type=full devclass=3590 backup devconfig filename=devconfig.date backup volhistory filename=volhistory.date Where do I get the backup tape volser, from the activity log? How do I eject this backup tape from the library? We have 349x library and drives. And if I need to back out from the migration, could I just do a restore of this backup tape by issuing: dsmserv restore db volumes=volser(from the backup) devclass=3590 commit=yes I need to write up a plan for our migration. Please advise. Thanks, Helen Tam
tsm upgrade
getting ready to upgrade tsm server on zos 1.4 to 5.2.0.0 from 5.1.6.2 does anyone know if my os/390 linux clients 5.1.5.5 will run with 5.1.6.2?
Re: tsm upgrade
object ( ) where is the object id. These messages can be ignored. (APAR IC37589 will resolve this in V5.2.2 although once this thread runs to completion APAR IC37589 will no longer be needed.) In both of the above cases, a background thread runs after the server is upgraded to remove extraneous database entries after the conversion to new tables takes place. This background thread has been updated to remove the extraneous database searching which should result in the background thread completing more quickly. This thread will be restarted each time the server is started until the process runs to completion. Conclusion: The TSM database change in TSM V5.2 is necessary to improve the production capability and support for grouped files. The recommendations listed above should be followed to eliminate all possible invalid or incomplete grouped file entries prior to upgrading to V5.2 and to avoid performance degradation after upgrading to V5.2. Additional Information: Flash 10210 described the original problem which resulted in the creation of CLEANUP BACKUPGROUPS. If you would like additional information regarding the original problem, refer to FLASH #10210 on http://www-3.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManag er.html O/S: OS/400; AIX; HP-UX; Linux; Solaris; Windows; OS/390; z/OS Keywords: system objects, upgrade, migration, performance, cleanup BACKUPGROUPS -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Hubble, Frank Sent: Tuesday, December 09, 2003 2:03 PM To: [EMAIL PROTECTED] Subject: tsm upgrade getting ready to upgrade tsm server on zos 1.4 to 5.2.0.0 from 5.1.6.2 does anyone know if my os/390 linux clients 5.1.5.5 will run with 5.1.6.2?
TSM Upgrade and TDP compactability
Hello We are upgrading our TSM to 5.2 and we currently run SQL TDP 2.2..1.* and I was wondering if there are any compatibility issues??? Thanks Mike
Re: TSM Upgrade and TDP compactability
Mike, This should work... but be aware that Data Protection for SQL 2.2.1 is an unsupported version of the product. You should obtain the latest version, 5.2.1. You can go here to get the 5.2.1 version: Site: ftp.software.ibm.com Dir: /storage/tivoli-storage-management/maintenance/tivoli-data-protection/ntsql/v521/ 5.2.1 will install and run with the PAID license from the 2.2.1 product. Thanks, Del We are upgrading our TSM to 5.2 and we currently run SQL TDP 2.2..1.* and I was wondering if there are any compatibility issues???
TSM Upgrade 4.1.6 to 5.1.7.0 Experience
Just wanted to pass along a great experience with doing a TSM Upgrade! ENV RS/6000 H80 (4x8) AIX 4.3.3 TSM 4.1.6 TSM DB 100GB Just by chance we read the readme for 5.1.7. It stated Customers migrating from a prior release of Tivoli Storage Manager MUST 1. First download and install 5.1.7.0 (Not 5.1.0.0 or 5.1.5.0) 2. Then install license enablement and license certificates from your product CD. So we took this route and the whole process too 4hrs instead of 8-10 from a similar env we upgraded from 4.1.6 to 5.1.5 Big time saver!
Re: TSM Upgrade from 4.1 to 5.x questions
inline: graycol.gifinline: ecblank.gifinline: pic27429.gif
Re: TSM Upgrade from 4.1 to 5.x questions
Are there any issues with upgrading from TSM Server V4.1.2 to version 5.1.x? Or do we have to upgrade to 4.2.x first? Also, what is the best version to upgrade to? 5.1.5, 5.1.6.2 or something else? We are running on AIX 4.3.3 ML 10. Thanks in advance! Steven A. Conko Senior Unix Systems Administrator ADT Security Services, Inc.
Re: TSM Upgrade from 4.1 to 5.x questions
We went straight from 4.1.2 to 5.1.5 with no stop at 4.2.x and few if any problems. We were at AIX 4.3.3 ML 9 -Original Message- From: Conko, Steven [mailto:[EMAIL PROTECTED] Sent: Thursday, March 27, 2003 10:08 AM To: [EMAIL PROTECTED] Subject: Re: TSM Upgrade from 4.1 to 5.x questions Are there any issues with upgrading from TSM Server V4.1.2 to version 5.1.x? Or do we have to upgrade to 4.2.x first? Also, what is the best version to upgrade to? 5.1.5, 5.1.6.2 or something else? We are running on AIX 4.3.3 ML 10. Thanks in advance! Steven A. Conko Senior Unix Systems Administrator ADT Security Services, Inc.
Re: TSM Upgrade from 4.1 to 5.x questions
Steven, We just upgraded a few weeks ago (AIX 4.3.3) and we were told by support, to go from 4.2.1 to 5.1.0 to 5.1.5. Make sure you do not start the server until you've completed installing 5.1.5. You will have to reset your license file(s) as well. Marco Spagnuolo System Administrator University of Windsor (IT Services) 401 Sunset Windsor, Ontario N9B 3P4 (519) 253-4232 Ext. 2769 Email: [EMAIL PROTECTED] Conko, Steven [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent by: ADSM: cc: Dist StorSubject: Re: TSM Upgrade from 4.1 to 5.x questions Manager [EMAIL PROTECTED] .edu 03/27/2003 11:07 AM Please respond to ADSM: Dist Stor Manager Are there any issues with upgrading from TSM Server V4.1.2 to version 5.1.x? Or do we have to upgrade to 4.2.x first? Also, what is the best version to upgrade to? 5.1.5, 5.1.6.2 or something else? We are running on AIX 4.3.3 ML 10. Thanks in advance! Steven A. Conko Senior Unix Systems Administrator ADT Security Services, Inc.
Re: TSM Upgrade from 4.1 to 5.x questions
I'll throw in our experience if it helps anyone. We just upgraded from 4.2.0 to 5.1.6.1 on W2K. We were using subfile backups at 4.2.0 and these were not expiring properly. This was fixed at 5.1.5.x when I did a test migration to it. When doing a test migration to 5.1.6.1 we found that there was a problem trying to recover any subfile backups - client got an error (Error 8 getting backup row for object XXX). The process we followed which seems to have worked was: Upgrade to 4.2.3.3 - run expiration twice (cleans up sub file backups). Upgrade to 5.1.0.0 Upgrade to 5.1.1.0 Upgrade to 5.1.6.2 Redo licences at 5.1.6.1. Not sure if we needed to go to 5.1.0.0 and 5.1.1.0 before 5.1.6.1 (couldn't we just install 5.1.6.1 then install licences from a 5.1.5 base version?) but this was according to the readmes. Tim Rushforth City of Winnipeg -Original Message- From: Marco Spagnuolo [mailto:[EMAIL PROTECTED] Sent: Thursday, March 27, 2003 10:43 AM To: [EMAIL PROTECTED] Subject: Re: TSM Upgrade from 4.1 to 5.x questions Steven, We just upgraded a few weeks ago (AIX 4.3.3) and we were told by support, to go from 4.2.1 to 5.1.0 to 5.1.5. Make sure you do not start the server until you've completed installing 5.1.5. You will have to reset your license file(s) as well. Marco Spagnuolo System Administrator University of Windsor (IT Services) 401 Sunset Windsor, Ontario N9B 3P4 (519) 253-4232 Ext. 2769 Email: [EMAIL PROTECTED]
Re: TSM Upgrade from 4.1 to 5.x questions
We got bit by the Systemobject expiration problem and when I went from 4.2.1 to 5.1.0.0 it failed. TSM server wouldn't even start. Gave me ANR messages about unable to convert objects. I had to D/R my system back to 4.2.1, upgraded to 4.2.3.3 and ran the CLEANUP BACKUPGROUPS. Took 14-hours, but freed up almost 34% in my database. Then I went to 5.1.0.0 and applied the latest patch. I'm now up to 5.1.6.3 with the only problem being the formatting of the Q PROCESS output with the ~'s and no line-feeds. I would say if you aren't backing up any Win2k servers, you could go straight up to 5.1.x. Bill Boyer I haven't lost my mind -- it's backed up on tape somewhere. - ??? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Rushforth, Tim Sent: Thursday, March 27, 2003 12:06 PM To: [EMAIL PROTECTED] Subject: Re: TSM Upgrade from 4.1 to 5.x questions I'll throw in our experience if it helps anyone. We just upgraded from 4.2.0 to 5.1.6.1 on W2K. We were using subfile backups at 4.2.0 and these were not expiring properly. This was fixed at 5.1.5.x when I did a test migration to it. When doing a test migration to 5.1.6.1 we found that there was a problem trying to recover any subfile backups - client got an error (Error 8 getting backup row for object XXX). The process we followed which seems to have worked was: Upgrade to 4.2.3.3 - run expiration twice (cleans up sub file backups). Upgrade to 5.1.0.0 Upgrade to 5.1.1.0 Upgrade to 5.1.6.2 Redo licences at 5.1.6.1. Not sure if we needed to go to 5.1.0.0 and 5.1.1.0 before 5.1.6.1 (couldn't we just install 5.1.6.1 then install licences from a 5.1.5 base version?) but this was according to the readmes. Tim Rushforth City of Winnipeg -Original Message- From: Marco Spagnuolo [mailto:[EMAIL PROTECTED] Sent: Thursday, March 27, 2003 10:43 AM To: [EMAIL PROTECTED] Subject: Re: TSM Upgrade from 4.1 to 5.x questions Steven, We just upgraded a few weeks ago (AIX 4.3.3) and we were told by support, to go from 4.2.1 to 5.1.0 to 5.1.5. Make sure you do not start the server until you've completed installing 5.1.5. You will have to reset your license file(s) as well. Marco Spagnuolo System Administrator University of Windsor (IT Services) 401 Sunset Windsor, Ontario N9B 3P4 (519) 253-4232 Ext. 2769 Email: [EMAIL PROTECTED]
Re: TSM Upgrade from 4.1 to 5.x questions
We have upgraded TSM server code from 3.7, 4.1, and 4.2 to 5.1.0 with no problems. Then it would let us go to 5.1.3. You do have to redefine your licenses. Linda Seeba Phone: (314) 234-5190 I/T Specialist - Sr Fax: (314) 232-4581 IBM Global Services E-Mail:[EMAIL PROTECTED] Marco Spagnuolo [EMAIL PROTECTED]@VM.MARIST.EDU on 03/27/2003 10:43:06 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: TSM Upgrade from 4.1 to 5.x questions Steven, We just upgraded a few weeks ago (AIX 4.3.3) and we were told by support, to go from 4.2.1 to 5.1.0 to 5.1.5. Make sure you do not start the server until you've completed installing 5.1.5. You will have to reset your license file(s) as well. Marco Spagnuolo System Administrator University of Windsor (IT Services) 401 Sunset Windsor, Ontario N9B 3P4 (519) 253-4232 Ext. 2769 Email: [EMAIL PROTECTED] Conko, Steven [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent by: ADSM: cc: Dist StorSubject: Re: TSM Upgrade from 4.1 to 5.x questions Manager [EMAIL PROTECTED] .edu 03/27/2003 11:07 AM Please respond to ADSM: Dist Stor Manager Are there any issues with upgrading from TSM Server V4.1.2 to version 5.1.x? Or do we have to upgrade to 4.2.x first? Also, what is the best version to upgrade to? 5.1.5, 5.1.6.2 or something else? We are running on AIX 4.3.3 ML 10. Thanks in advance! Steven A. Conko Senior Unix Systems Administrator ADT Security Services, Inc.
Re: TSM Upgrade from 4.1 to 5.x questions
When everyone is mentioning redefining licenses are you referring to the client licenses defined on the TSM server? If so, does anyone know if this is done on all TSM server platforms? I am upgrading from 4.1.5 to 5.1.6 this weekend and the TSM server is on OS/390 2.10. Thanks! Joni Moyer Systems Programmer [EMAIL PROTECTED] (717)975-8338 Linda Seeba [EMAIL PROTECTED] To: [EMAIL PROTECTED] COM cc: Sent by: Subject: Re: TSM Upgrade from 4.1 to 5.x questions ADSM: Dist Stor Manager [EMAIL PROTECTED] IST.EDU 03/27/2003 12:12 PM Please respond to ADSM: Dist Stor Manager We have upgraded TSM server code from 3.7, 4.1, and 4.2 to 5.1.0 with no problems. Then it would let us go to 5.1.3. You do have to redefine your licenses. Linda Seeba Phone: (314) 234-5190 I/T Specialist - Sr Fax: (314) 232-4581 IBM Global Services E-Mail:[EMAIL PROTECTED] Marco Spagnuolo [EMAIL PROTECTED]@VM.MARIST.EDU on 03/27/2003 10:43:06 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: TSM Upgrade from 4.1 to 5.x questions Steven, We just upgraded a few weeks ago (AIX 4.3.3) and we were told by support, to go from 4.2.1 to 5.1.0 to 5.1.5. Make sure you do not start the server until you've completed installing 5.1.5. You will have to reset your license file(s) as well. Marco Spagnuolo System Administrator University of Windsor (IT Services) 401 Sunset Windsor, Ontario N9B 3P4 (519) 253-4232 Ext. 2769 Email: [EMAIL PROTECTED] Conko, Steven [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent by: ADSM: cc: Dist StorSubject: Re: TSM Upgrade from 4.1 to 5.x questions Manager [EMAIL PROTECTED] .edu 03/27/2003 11:07 AM Please respond to ADSM: Dist Stor Manager Are there any issues with upgrading from TSM Server V4.1.2 to version 5.1.x? Or do we have to upgrade to 4.2.x first? Also, what is the best version to upgrade to? 5.1.5, 5.1.6.2 or something else? We are running on AIX 4.3.3 ML 10. Thanks in advance! Steven A. Conko Senior Unix Systems Administrator ADT Security Services, Inc.
Re: TSM Upgrade from 4.1 to 5.x questions
Look for the //OPT DD card. The number of licenses is specified in an options file on the 390. -Original Message- From: Joni Moyer [mailto:[EMAIL PROTECTED] Sent: Thursday, March 27, 2003 11:25 AM To: [EMAIL PROTECTED] Subject: Re: TSM Upgrade from 4.1 to 5.x questions When everyone is mentioning redefining licenses are you referring to the client licenses defined on the TSM server? If so, does anyone know if this is done on all TSM server platforms? I am upgrading from 4.1.5 to 5.1.6 this weekend and the TSM server is on OS/390 2.10. Thanks! Joni Moyer Systems Programmer [EMAIL PROTECTED] (717)975-8338 Linda Seeba [EMAIL PROTECTED] To: [EMAIL PROTECTED] COM cc: Sent by: Subject: Re: TSM Upgrade from 4.1 to 5.x questions ADSM: Dist Stor Manager [EMAIL PROTECTED] IST.EDU 03/27/2003 12:12 PM Please respond to ADSM: Dist Stor Manager We have upgraded TSM server code from 3.7, 4.1, and 4.2 to 5.1.0 with no problems. Then it would let us go to 5.1.3. You do have to redefine your licenses. Linda Seeba Phone: (314) 234-5190 I/T Specialist - Sr Fax: (314) 232-4581 IBM Global Services E-Mail:[EMAIL PROTECTED] Marco Spagnuolo [EMAIL PROTECTED]@VM.MARIST.EDU on 03/27/2003 10:43:06 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: TSM Upgrade from 4.1 to 5.x questions Steven, We just upgraded a few weeks ago (AIX 4.3.3) and we were told by support, to go from 4.2.1 to 5.1.0 to 5.1.5. Make sure you do not start the server until you've completed installing 5.1.5. You will have to reset your license file(s) as well. Marco Spagnuolo System Administrator University of Windsor (IT Services) 401 Sunset Windsor, Ontario N9B 3P4 (519) 253-4232 Ext. 2769 Email: [EMAIL PROTECTED] Conko, Steven [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent by: ADSM: cc: Dist StorSubject: Re: TSM Upgrade from 4.1 to 5.x questions Manager [EMAIL PROTECTED] .edu 03/27/2003 11:07 AM Please respond to ADSM: Dist Stor Manager Are there any issues with upgrading from TSM Server V4.1.2 to version 5.1.x? Or do we have to upgrade to 4.2.x first? Also, what is the best version to upgrade to? 5.1.5, 5.1.6.2 or something else? We are running on AIX 4.3.3 ML 10. Thanks in advance! Steven A. Conko Senior Unix Systems Administrator ADT Security Services, Inc.
Re: TSM Upgrade from 4.1 to 5.x questions
On Thu, Mar 27, 2003 at 12:14:29PM -0500, Bill Boyer wrote: the latest patch. I'm now up to 5.1.6.3 with the only problem being the formatting of the Q PROCESS output with the ~'s and no line-feeds. Yes, that happens here too, both with 5.1.6.2 and 5.1.6.3 (AIX 433 ML 10). The filesets were installed with the correct option (Install and Update from ALL available software). It's not everywhere that linefeeds are missing, and it's only a very minor cosmetic problem. -- Jurjen Oskam PGP Key available at http://www.stupendous.org/
Re: TSM Upgrade frequency
Todd, For the original question: up to now majority of our customers have Storage Agent nodes and we have no problems with upgrades. Mostly these are AIX servers (Windows ones are smaller and go over LAN) and life with AIX is very easy. You can perform upgrade during the day without *any* significant impact: 1. set enablelanfree=no for those nodes making hourly backups. Usually we use dsmcad thus are not forced to restart the scheduler or touch anything than dsm.sys 2. stop all storage agents 3. upgrade/patch the server 4. upgrade one-by-one the storage agents and re-enable lan-free (I personally prefer to send logs and other hourly stuff to diskpool over LAN thus impact is nearly nill) Upgrade of Storage Agent without upgrading the device driver *does not* require restart. Even if you need to upgrade the TSM driver it is possible driver-upgrade to be done during the night and the storage agent upgrade to be performed the day after. As for the Eliza's remark - many patches, especially in server/storage agent have to be done on both sides. Therefore both server and storage agent must be at the same patch level (i.e. all four numbers must match). Is is clearly indicated in many server and storage agent readmes. For the upgrade I would recommend 4.2.1.15 (and seeing other's posts on the list I am not alone). v5.1.1.6 was not bad and going there without stepping any v4.2.2.x or previous 5.1.0.y/5.1.1.z versions will avoid system object-problem. Zlatko Krastev IT Consultant P.S. I posted this three days ago but did not saw it coming through. If some of you got it please excuse the repost. Eliza Lau [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 19.02.2003 17:50 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: TSM Upgrade frequency Todd, From talking to a TSM Level 2 consultant, only the first 3 numbers of a release have to match between the server and the storage agent. If all your storage agents are at 4.2.1.7, upgrading the server to 4.2.1.9 should be ok. Eliza Lau Virginia Tech Computing Center For you folks that patch your TSM server frequently (like the individual from Oxford University who upgraded from some version to 5.1.6.0 on Feb3, then to 5.1.6.1 on Feb7, and now planning to upgrade to 5.1.6.2 within a couple weeks), how many of you have Storage Agent nodes? I am still on 4.2.1.7 simply because of the Storage Agent issue. We have a problem with TSM server crashes that is supposed to be fixed in 4.2.1.9+, but I find it hard to justify upgrading to 4.2.1.9+ when I know I will have to upgrade to 5.x soon after. According to the documentation I have read, the TSM Server version and the Storage Agent version must be at the same level. We have several Storage Agent nodes, and all of them are considered 24x7 servers, mission critical. It is like pulling teeth to get downtime for any one of them just for normal OS or Application type maint. I dread the time where I have to take them all down at once. Even more so, I dread having to take all of them down at the same time several times a month just to keep updating TSM Storage Agent versions because the TSM Server needed a patch. How do you folks with several mission critical, 24x7 servers go about doing TSM Server upgrades and TSM Storage Agent upgrades? Especially considering that TSM Server outages are best done during the day when no backups are occurring, and TSM Client Node outages are done during the night to reduce impact on the users of those Client Nodes.
Re: TSM Upgrade frequency: SAN upgrade 4.2.1.7 to 4.2.1.9
I cannot remember now, but I believe this is one upgrade that absolutely required both to go at the same time. I am thinking it is 4.2.1.8 that required all to be updated. Prior to 4.2.2.0 they did not check the patch level, but since it caused so much grief for support it is now enforced. Believe me I know. Level 2 sent me 4.2.2.13 with a patch on top to run on my server and my SAs were at 4.2.2.12, every one of the puked and had to be recycled after reverting back to 4.2.2.12. They have a real nice message that comes out now to tell you they are not at the same level. Paul D. Seay, Jr. Technical Specialist Northrop Grumman Information Technology 757-688-8180 -Original Message- From: Eliza Lau [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 19, 2003 10:51 AM To: [EMAIL PROTECTED] Subject: Re: TSM Upgrade frequency Todd, From talking to a TSM Level 2 consultant, only the first 3 numbers of a release have to match between the server and the storage agent. If all your storage agents are at 4.2.1.7, upgrading the server to 4.2.1.9 should be ok. Eliza Lau Virginia Tech Computing Center For you folks that patch your TSM server frequently (like the individual from Oxford University who upgraded from some version to 5.1.6.0 on Feb3, then to 5.1.6.1 on Feb7, and now planning to upgrade to 5.1.6.2 within a couple weeks), how many of you have Storage Agent nodes? I am still on 4.2.1.7 simply because of the Storage Agent issue. We have a problem with TSM server crashes that is supposed to be fixed in 4.2.1.9+, but I find it hard to justify upgrading to 4.2.1.9+ when I know I will have to upgrade to 5.x soon after. According to the documentation I have read, the TSM Server version and the Storage Agent version must be at the same level. We have several Storage Agent nodes, and all of them are considered 24x7 servers, mission critical. It is like pulling teeth to get downtime for any one of them just for normal OS or Application type maint. I dread the time where I have to take them all down at once. Even more so, I dread having to take all of them down at the same time several times a month just to keep updating TSM Storage Agent versions because the TSM Server needed a patch. How do you folks with several mission critical, 24x7 servers go about doing TSM Server upgrades and TSM Storage Agent upgrades? Especially considering that TSM Server outages are best done during the day when no backups are occurring, and TSM Client Node outages are done during the night to reduce impact on the users of those Client Nodes.
Re: TSM Upgrade frequency
Todd, From talking to a TSM Level 2 consultant, only the first 3 numbers of a release have to match between the server and the storage agent. If all your storage agents are at 4.2.1.7, upgrading the server to 4.2.1.9 should be ok. Eliza Lau Virginia Tech Computing Center For you folks that patch your TSM server frequently (like the individual from Oxford University who upgraded from some version to 5.1.6.0 on Feb3, then to 5.1.6.1 on Feb7, and now planning to upgrade to 5.1.6.2 within a couple weeks), how many of you have Storage Agent nodes? I am still on 4.2.1.7 simply because of the Storage Agent issue. We have a problem with TSM server crashes that is supposed to be fixed in 4.2.1.9+, but I find it hard to justify upgrading to 4.2.1.9+ when I know I will have to upgrade to 5.x soon after. According to the documentation I have read, the TSM Server version and the Storage Agent version must be at the same level. We have several Storage Agent nodes, and all of them are considered 24x7 servers, mission critical. It is like pulling teeth to get downtime for any one of them just for normal OS or Application type maint. I dread the time where I have to take them all down at once. Even more so, I dread having to take all of them down at the same time several times a month just to keep updating TSM Storage Agent versions because the TSM Server needed a patch. How do you folks with several mission critical, 24x7 servers go about doing TSM Server upgrades and TSM Storage Agent upgrades? Especially considering that TSM Server outages are best done during the day when no backups are occurring, and TSM Client Node outages are done during the night to reduce impact on the users of those Client Nodes.
Re: TSM Upgrade frequency
Hmm. That's interesting, because I've seen several of the TSM server patch readme's specifically stating that the storage agent must be the same patch level. For example, the AIX 5.1.5.1 and 5.1.5.2 readme's say, patch level 5.1.5.1 (and 2) also effects Storage Agent for AIX. If you use it, you can obtain the associated install package from Can we get someone from Tivoli to weigh in? Maybe some patch levels effect the Storage Agent, and some patch levels don't? Alex Paschal Freightliner, LLC (503) 745-6850 -Original Message- From: Eliza Lau [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 19, 2003 7:51 AM To: [EMAIL PROTECTED] Subject: Re: TSM Upgrade frequency Todd, From talking to a TSM Level 2 consultant, only the first 3 numbers of a release have to match between the server and the storage agent. If all your storage agents are at 4.2.1.7, upgrading the server to 4.2.1.9 should be ok. Eliza Lau Virginia Tech Computing Center For you folks that patch your TSM server frequently (like the individual from Oxford University who upgraded from some version to 5.1.6.0 on Feb3, then to 5.1.6.1 on Feb7, and now planning to upgrade to 5.1.6.2 within a couple weeks), how many of you have Storage Agent nodes? I am still on 4.2.1.7 simply because of the Storage Agent issue. We have a problem with TSM server crashes that is supposed to be fixed in 4.2.1.9+, but I find it hard to justify upgrading to 4.2.1.9+ when I know I will have to upgrade to 5.x soon after. According to the documentation I have read, the TSM Server version and the Storage Agent version must be at the same level. We have several Storage Agent nodes, and all of them are considered 24x7 servers, mission critical. It is like pulling teeth to get downtime for any one of them just for normal OS or Application type maint. I dread the time where I have to take them all down at once. Even more so, I dread having to take all of them down at the same time several times a month just to keep updating TSM Storage Agent versions because the TSM Server needed a patch. How do you folks with several mission critical, 24x7 servers go about doing TSM Server upgrades and TSM Storage Agent upgrades? Especially considering that TSM Server outages are best done during the day when no backups are occurring, and TSM Client Node outages are done during the night to reduce impact on the users of those Client Nodes.
AW: TSM Upgrade frequency
Hello Todd we have the same problem and open a requestby ibm. the reason for the requirement in time is that the server and sta are talking over database-records (segments) (like db-io over TCP/IP) ! In time we have 16 W2K STA and 8 STA at HP and that is not the end ... Helge van de Kraan IS-Rechnersysteme Volkswagen AG Brieffach 1883 38436 Wolfsburg Telefon +49 (5361)9-73711 Telefax +49 (5361)9-29289 http://www.volkswagen.de -Ursprüngliche Nachricht- Von: Todd Lundstedt [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 18. Februar 2003 17:47 An: [EMAIL PROTECTED] Betreff: TSM Upgrade frequency For you folks that patch your TSM server frequently (like the individual from Oxford University who upgraded from some version to 5.1.6.0 on Feb3, then to 5.1.6.1 on Feb7, and now planning to upgrade to 5.1.6.2 within a couple weeks), how many of you have Storage Agent nodes? I am still on 4.2.1.7 simply because of the Storage Agent issue. We have a problem with TSM server crashes that is supposed to be fixed in 4.2.1.9+, but I find it hard to justify upgrading to 4.2.1.9+ when I know I will have to upgrade to 5.x soon after. According to the documentation I have read, the TSM Server version and the Storage Agent version must be at the same level. We have several Storage Agent nodes, and all of them are considered 24x7 servers, mission critical. It is like pulling teeth to get downtime for any one of them just for normal OS or Application type maint. I dread the time where I have to take them all down at once. Even more so, I dread having to take all of them down at the same time several times a month just to keep updating TSM Storage Agent versions because the TSM Server needed a patch. How do you folks with several mission critical, 24x7 servers go about doing TSM Server upgrades and TSM Storage Agent upgrades? Especially considering that TSM Server outages are best done during the day when no backups are occurring, and TSM Client Node outages are done during the night to reduce impact on the users of those Client Nodes.
Re: TSM Upgrade frequency: Storage Agent Requirement
Not Quite! This used to be true before 4.2.2.0, not any longer. They must match right down to the patch level. I was bitten by 4.2.2.12 and 4.2.2.13. However, TSM Development is promising to make this issue go away. Hopefully, in V5.2. You will have to upgrade all at once then, probably, but after that we pray not. Paul D. Seay, Jr. Technical Specialist Northrop Grumman Information Technology 757-688-8180 -Original Message- From: Eliza Lau [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 19, 2003 10:51 AM To: [EMAIL PROTECTED] Subject: Re: TSM Upgrade frequency Todd, From talking to a TSM Level 2 consultant, only the first 3 numbers of a release have to match between the server and the storage agent. If all your storage agents are at 4.2.1.7, upgrading the server to 4.2.1.9 should be ok. Eliza Lau Virginia Tech Computing Center For you folks that patch your TSM server frequently (like the individual from Oxford University who upgraded from some version to 5.1.6.0 on Feb3, then to 5.1.6.1 on Feb7, and now planning to upgrade to 5.1.6.2 within a couple weeks), how many of you have Storage Agent nodes? I am still on 4.2.1.7 simply because of the Storage Agent issue. We have a problem with TSM server crashes that is supposed to be fixed in 4.2.1.9+, but I find it hard to justify upgrading to 4.2.1.9+ when I know I will have to upgrade to 5.x soon after. According to the documentation I have read, the TSM Server version and the Storage Agent version must be at the same level. We have several Storage Agent nodes, and all of them are considered 24x7 servers, mission critical. It is like pulling teeth to get downtime for any one of them just for normal OS or Application type maint. I dread the time where I have to take them all down at once. Even more so, I dread having to take all of them down at the same time several times a month just to keep updating TSM Storage Agent versions because the TSM Server needed a patch. How do you folks with several mission critical, 24x7 servers go about doing TSM Server upgrades and TSM Storage Agent upgrades? Especially considering that TSM Server outages are best done during the day when no backups are occurring, and TSM Client Node outages are done during the night to reduce impact on the users of those Client Nodes.
TSM Upgrade frequency
For you folks that patch your TSM server frequently (like the individual from Oxford University who upgraded from some version to 5.1.6.0 on Feb3, then to 5.1.6.1 on Feb7, and now planning to upgrade to 5.1.6.2 within a couple weeks), how many of you have Storage Agent nodes? I am still on 4.2.1.7 simply because of the Storage Agent issue. We have a problem with TSM server crashes that is supposed to be fixed in 4.2.1.9+, but I find it hard to justify upgrading to 4.2.1.9+ when I know I will have to upgrade to 5.x soon after. According to the documentation I have read, the TSM Server version and the Storage Agent version must be at the same level. We have several Storage Agent nodes, and all of them are considered 24x7 servers, mission critical. It is like pulling teeth to get downtime for any one of them just for normal OS or Application type maint. I dread the time where I have to take them all down at once. Even more so, I dread having to take all of them down at the same time several times a month just to keep updating TSM Storage Agent versions because the TSM Server needed a patch. How do you folks with several mission critical, 24x7 servers go about doing TSM Server upgrades and TSM Storage Agent upgrades? Especially considering that TSM Server outages are best done during the day when no backups are occurring, and TSM Client Node outages are done during the night to reduce impact on the users of those Client Nodes.
TSM Upgrade 4.2.2.3 ---- 5.1.X -- HELP!
Hi, I've seen several of your posts regarding your experiences with upgrading your TSM server from 4.X to 5.X. We attempted this upgrade a few weeks back, not knowing at the time about the SYSTEM OBJECT problem, and after several hours aborted the upgrade and restored from backup. We are at 4.2.2.3, and we have about 200 Win2K clients, a 32GB TSM database (54% of which is SYSTEM OBJECTS!!). We've been retaining 60 versions of the SYSTEM OBJECT files / server, so we are going to have some major problems obviously. We did not realize the err of our ways as far as retention until we ran into the upgrade problems. We were totally blindsided by this, as it seems you and so many others have been as well. IBM has recommended the following: 1. Upgrade to 4.2.2.12, so we have the CLEANUP BACKUPGROUP utility, and the SYSTEM OBJECTS will begin to expire properly. 2. Change our retention policy on the SYSTEM OBJECT stuff gradually. 55days, 50 days, 45 days, on down to 5 days. I'm assuming the gradual stepdown is because of the time required to expire? 3. Run the CLEANUP BACKUPGROUP utility. It will take several days? I've heard you can start it after daily processing, kill the process when its time for backups to begin, and start it up again the next day. So on and so on until its finished. Have you had experience with that? 4. After the cleanup, upgrade to 5.1.X, during which the upgrade db will run. I have been told that the upgrade db could take days! Your experience? During this time, no backups/restores can be performed, correct? Bottom line, I'm getting different answers from IBM support, from our IBM reseller, from the newsgroups, etc. I am desperate for some feedback from someone who has actually made it to the other side. I'm going to have to give this another go very soon and I'm not at all looking forward to it. ANY experiences or suggestions you can share are GREATLY appreciated!! Thank you so much, Kevin This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865) 374-4900 or notify us by E-mail at [EMAIL PROTECTED]
Re: TSM Upgrade 4.2.2.3 ---- 5.1.X -- HELP!
Bottom line, I'm getting different answers from IBM support, from our IBM reseller, from the newsgroups, etc. I am desperate for some feedback from someone who has actually made it to the other side. I'm going to have to give this another go very soon and I'm not at all looking forward to it. ANY experiences or suggestions you can share are GREATLY appreciated!! As I mentioned, we made it just last week from 4.1.3 to 5.1.1.6 (direct). It only took us 18 hours, of which 13-14 hours was doing the deletion of SYSTEM OBJECTS, per this list. When we finally did CLEANUP BACKUPGROUPS on the new 5.1.1.6 system, it only took 30 seconds. We have about 100 Windows servers (though less than half are Win2K) and a 16 GB TSM database. It's possible that if we didn't do the SYSTEM OBJECT deletions, it may have taken the same time, or even less for all we know. But I'm just happy it was under a day, and we are fine on the new server (other than Informix db-level backup :(. johnn
Re: TSM upgrade from 3.7 to 5.1
I have an upgrade doc for my HP system you are welcome to have if you want? I just upgraded from 3.7 to 4.2.2.5 on HP-UX 11.0. I know there are some subtle differences. Bill -Original Message- From: Ganu Sachin, IBM [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 24, 2002 3:11 AM To: [EMAIL PROTECTED] Subject: Re: TSM upgrade from 3.7 to 5.1 It is AIX 4.3.3 -Original Message- From: Joshua Bassi [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 24, 2002 10:13 AM To: [EMAIL PROTECTED] Subject:Re: TSM upgrade from 3.7 to 5.1 Sachin, What platform are you on? The upgrade procedure varies based upon the operating system the TSM server is running on. Please provide the OS version and release for us to assist you with the installation further. Also, you should have received a Quick Start guide with your TSM upgrade. Installation info can also be found there. It can also be downloaded at the TSM web site www.tivoli.com/tsm. -- Joshua S. Bassi IBM Certified - AIX 4/5L, SAN, Shark Tivoli Certified Consultant - ADSM/TSM eServer Systems Expert -pSeries HACMP AIX, HACMP, Storage, TSM Consultant Cell (831) 595-3962 [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of Ganu Sachin, IBM Sent: Monday, September 23, 2002 8:20 PM To: [EMAIL PROTECTED] Subject: TSM upgrade from 3.7 to 5.1 Hi I am planning to upgrade my TSM from 3.7 to 5.1 . Can someone help me out for the procedure ? Will it overwrite my existing TSM db ? Regards Sachin Ganu
Re: TSM upgrade from 3.7 to 5.1
It is AIX 4.3.3 -Original Message- From: Joshua Bassi [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 24, 2002 10:13 AM To: [EMAIL PROTECTED] Subject:Re: TSM upgrade from 3.7 to 5.1 Sachin, What platform are you on? The upgrade procedure varies based upon the operating system the TSM server is running on. Please provide the OS version and release for us to assist you with the installation further. Also, you should have received a Quick Start guide with your TSM upgrade. Installation info can also be found there. It can also be downloaded at the TSM web site www.tivoli.com/tsm. -- Joshua S. Bassi IBM Certified - AIX 4/5L, SAN, Shark Tivoli Certified Consultant - ADSM/TSM eServer Systems Expert -pSeries HACMP AIX, HACMP, Storage, TSM Consultant Cell (831) 595-3962 [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of Ganu Sachin, IBM Sent: Monday, September 23, 2002 8:20 PM To: [EMAIL PROTECTED] Subject: TSM upgrade from 3.7 to 5.1 Hi I am planning to upgrade my TSM from 3.7 to 5.1 . Can someone help me out for the procedure ? Will it overwrite my existing TSM db ? Regards Sachin Ganu
TSM upgrade from 3.7 to 5.1
Hi I am planning to upgrade my TSM from 3.7 to 5.1 . Can someone help me out for the procedure ? Will it overwrite my existing TSM db ? Regards Sachin Ganu
Re: TSM upgrade from 3.7 to 5.1
Sachin, What platform are you on? The upgrade procedure varies based upon the operating system the TSM server is running on. Please provide the OS version and release for us to assist you with the installation further. Also, you should have received a Quick Start guide with your TSM upgrade. Installation info can also be found there. It can also be downloaded at the TSM web site www.tivoli.com/tsm. -- Joshua S. Bassi IBM Certified - AIX 4/5L, SAN, Shark Tivoli Certified Consultant - ADSM/TSM eServer Systems Expert -pSeries HACMP AIX, HACMP, Storage, TSM Consultant Cell (831) 595-3962 [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of Ganu Sachin, IBM Sent: Monday, September 23, 2002 8:20 PM To: [EMAIL PROTECTED] Subject: TSM upgrade from 3.7 to 5.1 Hi I am planning to upgrade my TSM from 3.7 to 5.1 . Can someone help me out for the procedure ? Will it overwrite my existing TSM db ? Regards Sachin Ganu
Re: TSM upgrade
I suggest you install the TSM-4.1 (not 5.1), restore the db from old TSM server as part of the migration; that way, (a) you preserve all the old backups (without need to export/import), and (b) you get the added space/performance on Win2K that you currently lack on the old, NT box. After successful migration to the new TSM server box, upgrade to 5.1.1.5 (or later)... read the README docs (server first, then clients later is only *one* way to do it) about all the migration considerations. In this case, you *may* be required to audit the db before upgrade will be allowed to proceed. Don France Technical Architect -- Tivoli Certified Consultant Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390 San Jose, Ca (408) 257-3037 mailto:[EMAIL PROTECTED] Professional Association of Contract Employees (P.A.C.E. -- www.pacepros.com) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Mario Behring Sent: Monday, August 19, 2002 7:49 AM To: [EMAIL PROTECTED] Subject: TSM upgrade Hi list, I have to upgrade my TSM Server and clients from 4.1 to 5.1. The new server, TSM 5.1, will be running on a different machine under Windows 2000 Server. The old one is now running on a Windows NT Server system. My storage unit is a IBM 3590 tape library (SCSI connected). The TSM 4.1 database is 17GB in size and the Recovery Log is 2GB. Do you guys have any tips on how should I do this ?? I mean, which is the best and more secure way to do it. I4ve heard that I cannot simply backup the TSM 4.1 database and restore it on the TSM 5.1 Server. And I can4t install TSM 5.1 over 4.1 because the old server is well old and there is no space left on the disks. Any help will be apreciated. Thanks. Mario Behring __ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com
TSM Upgrade
Current system: R40 AIX 4.3.3 ML8 TSM 4.1.5 New system: M80 AIX 5L Will I need a specific ML? TSM 5.1x. Current Plan: 1. Load AIX 5L on new server 2. Install TSM 4.1.5. 3. Restore DB onto new server. 4. Upgrade TSM to 5.1.x Any suggestions would be greatly appreciated!! --- Bruce Kamp Network Analyst II Memorial Healthcare System E: [EMAIL PROTECTED] P: (954) 987-2020 x4597 F: (954) 985-1404
Re: TSM Upgrade from 4.2 to 5.1
Hi Lindy, I have just upgraded a 4.1.x server to 5.1.1.1, without problems. If you check the readme, that comes on the v. 5.1 CD, it says howto do the upgrade from 4.2 to 5.1. It also tells you about known issues for upgrading a server. I'm sorry I don't have the answer here, but it would be easier to look at the file. rgds. Geirr G. Halvorsen -Original Message- From: Crawford, Lindy [mailto:[EMAIL PROTECTED]] Sent: 16. august 2002 14:45 To: [EMAIL PROTECTED] Subject: TSM Upgrade from 4.2 to 5.1 Hi TSMers Please help mehow can I upgrade from 4.2 to 5.1. Where do I start... And if I ran the tsm 5.1 setup, and I went to run server initialization instead of tsmfixup..how can I track back or fix the problemthanks Lindy Crawford Business Solutions: IT BoE Corporate * +27-31-3642185 +27-31-3642946 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] WARNING: Any unauthorised use or interception of this email is illegal. If this email is not intended for you, you may not copy, distribute nor disclose the contents to anyone. Save for bona fide company matters, BoE Ltd does not accept any responsibility for the opinions expressed in this email. For further details please see: http://www.boe.co.za/emaildisclaimer.htm
TSM upgrade
Hi list, I have to upgrade my TSM Server and clients from 4.1 to 5.1. The new server, TSM 5.1, will be running on a different machine under Windows 2000 Server. The old one is now running on a Windows NT Server system. My storage unit is a IBM 3590 tape library (SCSI connected). The TSM 4.1 database is 17GB in size and the Recovery Log is 2GB. Do you guys have any tips on how should I do this ?? I mean, which is the best and more secure way to do it. I4ve heard that I cannot simply backup the TSM 4.1 database and restore it on the TSM 5.1 Server. And I can4t install TSM 5.1 over 4.1 because the old server is well old and there is no space left on the disks. Any help will be apreciated. Thanks. Mario Behring __ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com
TSM Upgrade from 4.2 to 5.1
Hi TSMers Please help mehow can I upgrade from 4.2 to 5.1. Where do I start... And if I ran the tsm 5.1 setup, and I went to run server initialization instead of tsmfixup..how can I track back or fix the problemthanks Lindy Crawford Business Solutions: IT BoE Corporate * +27-31-3642185 +27-31-3642946 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] WARNING: Any unauthorised use or interception of this email is illegal. If this email is not intended for you, you may not copy, distribute nor disclose the contents to anyone. Save for bona fide company matters, BoE Ltd does not accept any responsibility for the opinions expressed in this email. For further details please see: http://www.boe.co.za/emaildisclaimer.htm
Re: Is TSM upgrade from V4 to V5 free?
Advice your customer to visit http://www.tivoli.com/support/maintenance. From there he/she can order to receive the new version (if is not already). To complete the form the username/password for the secure part of the site are necessary (same ID which is to be used for support - searching through knowledge base, opening of PMRs, etc.). When form is filled it is checked by IBM/Tivoli and if the customer is eligible mediadocs are shipped. I had even a case where customer administrator filled the form, got the package and later the scheduled shipment arrived so he got two copies. 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:Is TSM upgrade from V4 to V5 free? Hi TSM'rs Am I correct in believing that if a customer purchased TSM 4.2.1 two months ago and they now want to upgrade to Version 5, that it is free? I was told this by one of our distributors who said the upgrade is free if done within 12 months of purchase. Is this correct? Rgds John
Is TSM upgrade from V4 to V5 free?
Hi TSM'rs Am I correct in believing that if a customer purchased TSM 4.2.1 two months ago and they now want to upgrade to Version 5, that it is free? I was told this by one of our distributors who said the upgrade is free if done within 12 months of purchase. Is this correct? Rgds John
Re: Is TSM upgrade from V4 to V5 free?
Yes, if you are on maintenance. Paul D. Seay, Jr. Technical Specialist Naptheon, INC 757-688-8180 -Original Message- From: rs6000 [mailto:[EMAIL PROTECTED]] Sent: Monday, June 24, 2002 3:43 PM To: [EMAIL PROTECTED] Subject: Is TSM upgrade from V4 to V5 free? Hi TSM'rs Am I correct in believing that if a customer purchased TSM 4.2.1 two months ago and they now want to upgrade to Version 5, that it is free? I was told this by one of our distributors who said the upgrade is free if done within 12 months of purchase. Is this correct? Rgds John
Re: Is TSM upgrade from V4 to V5 free?
Sorry, did not read all of your message. It should be in your case because by default you are under maintenance for 1 year when you purchase the product. Talk to your supplier. Paul D. Seay, Jr. Technical Specialist Naptheon, INC 757-688-8180 -Original Message- From: rs6000 [mailto:[EMAIL PROTECTED]] Sent: Monday, June 24, 2002 3:43 PM To: [EMAIL PROTECTED] Subject: Is TSM upgrade from V4 to V5 free? Hi TSM'rs Am I correct in believing that if a customer purchased TSM 4.2.1 two months ago and they now want to upgrade to Version 5, that it is free? I was told this by one of our distributors who said the upgrade is free if done within 12 months of purchase. Is this correct? Rgds John
Impact of TSM upgrade to 4.2 on Fibre channel Protocol
Hi guys I am upgrading my TSM server from version 3.7.4 to 4.2.1.13. 2 Questions 1. What should be the upgrade path 3.7.4 --- 4.2 4.2.1.0 4.2.1.13 Is it right ?? 2. The install mentions that all FCP ( fibre channel protocol definitions will be lost and have to be re - installed ). I have got some FCP Disk drives and Fibre channel adapters attached to my tsm server . Please advise Regards Chandra Subash Unix/ Oracle Database Administrator Teletech International 154 Pacific Highway, St Leonards NSW 2065 Tel 02 -99301569 Sydney, Australia E-mail [EMAIL PROTECTED] This email is confidential and intended for the addressee(s) only. If you are not an addressee please promptly notify the sender and delete the message; do not use the content in any other way.
