OnDemand User Group
Support Forums => MP Server => Topic started by: jsquizz on October 31, 2018, 01:32:35 PM
-
Is there any way to see when we upgraded to a certain version of TSM? Might there be anything in the CMOD system logs?
-
Snoop around for config files in /usr/tivoli/tsm/server/bin. Usually there's config changes between versions. dsmserv.opt or dsmserv.dsk are good indicators.
-JD.
-
jeff@mybox:/usr/tivoli/tsm/server/bin> ll dsmserv.opt
-rw-r--r-- 1 root system 68261 Apr 01 2013 dsmserv.opt
Good indication the upgrade was done on April 01?
-
2013 seems to be late to upgrade to software that was released in 2007... But we're talking about TSM 5.5 at the end of 2018... I'm not sure what to tell you... :D
-
you can see the time when it was upgraded with:
lslpp -h tivoli.tsm.server.com
-
Thank you Michel - I will run that command and take a peek! 8)
My situation is weird and I am not sure where to start.
In our QA environment, we are running CMOD 8.5.0.6. TSM Client 6.2, and TSM Server 7.1
I have never heard of that mixture before -- 8.5 with 7.2 TSM.
In production we are running 8.5.0.6 with TSM 5.5 (Old, I know.)
We need to get to 7.1 ASAP but is there ANY way to get there without doing three things
1) Jumping to TSM 6.2
2) Upgrading TSM
3) Keeping 8.5
I know that after 6.X there was a version of DB2 under the covers but from speaking to some folks I know, as long as the box has enough resources, we should be ok. Does anyone have feedback on this?
-
You can go from TSM 5.5 to v7.1. It's not a lot of fun, but it can be done.
I'm not sure what you mean by #2 -- since the goal here is upgrading.
As for #3... You'd have to test this combination. Everything's so out of date that you won't have a showball's chance of getting this working properly without a lot of testing on lower regions to work out the bugs.
And FYI, DB2 was bundled with TSM starting in TSM 6.1.
-JD.
-
I have done several times upgrade of TSM 5.5 to 7.1.
Thing to worry about is the outage time. Going from 5.5 to 7.1 involves database migration which takes roughly 4GB / hr (in my environments) , so if you have a tsm db of 50GB , conversion time will be 12 hrs.......
Thank you Michel - I will run that command and take a peek! 8)
My situation is weird and I am not sure where to start.
In our QA environment, we are running CMOD 8.5.0.6. TSM Client 6.2, and TSM Server 7.1
I have never heard of that mixture before -- 8.5 with 7.2 TSM.
In production we are running 8.5.0.6 with TSM 5.5 (Old, I know.)
We need to get to 7.1 ASAP but is there ANY way to get there without doing three things
1) Jumping to TSM 6.2
2) Upgrading TSM
3) Keeping 8.5
I know that after 6.X there was a version of DB2 under the covers but from speaking to some folks I know, as long as the box has enough resources, we should be ok. Does anyone have feedback on this?
-
you can see the time when it was upgraded with:
lslpp -h tivoli.tsm.server.com
Fileset Level Action Status Date Time
----------------------------------------------------------------------------
Path: /usr/lib/objrepos
tivoli.tsm.server.com
5.5.0.0 COMMIT COMPLETE 12/21/10 15:06:19
5.5.7.0 COMMIT COMPLETE 03/13/14 12:50:30
Path: /etc/objrepos
tivoli.tsm.server.com
5.5.0.0 COMMIT COMPLETE 12/21/10 15:06:22
5.5.7.0 COMMIT COMPLETE 03/13/14 12:50:30
But when I log into TSM via dsmadmc
Command Line Administrative Interface - Version 6, Release 2, Level 0.0
(c) Copyright by IBM Corporation and other(s) 1990, 2010. All Rights Reserved.
Enter your user id: admin
Enter your password:
Session established with server TSMCENT_LINUX: Linux/x86_64
Server Version 7, Release 1, Level 1.100
Server date/time: 11/05/18 14:12:04 Last access: 10/31/18 18:14:03
-
You're connecting to the wrong server. :)
Check the ars.cfg file, and find the directory where the CMOD config for TSM is, then use the correct servername with the dsmadmc parameter.
If they use TSM for enterprise backup, maybe they should have their TSM team help you out with the upgrade?
-JD.
-
You're connecting to the wrong server. :)
Check the ars.cfg file, and find the directory where the CMOD config for TSM is, then use the correct servername with the dsmadmc parameter.
If they use TSM for enterprise backup, maybe they should have their TSM team help you out with the upgrade?
-JD.
I HAD THIS HAPPEN IN PROD BEFORE! THANK YOU for reminding me!! DOH!!
-
More questions. This is a dousey.
Trying to find the correlation between the two-
Path: /usr/lib/objrepos
tivoli.tsm.server.com
5.5.0.0 COMMIT COMPLETE 12/21/10 15:06:19
5.5.7.0 COMMIT COMPLETE 03/13/14 12:50:30
Path: /etc/objrepos
tivoli.tsm.server.com
5.5.0.0 COMMIT COMPLETE 12/21/10 15:06:22
5.5.7.0 COMMIT COMPLETE 03/13/14 12:50:30
But DSMADMC -
IBM Tivoli Storage Manager
Command Line Administrative Interface - Version 6, Release 2, Level 0.0
(c) Copyright by IBM Corporation and other(s) 1990, 2010. All Rights Reserved.
Enter your user id: admin
Enter your password:
Session established with server TSMCENT_LINUX: Linux/x86_64
Server Version 7, Release 1, Level 1.100
Server date/time: 11/06/18 09:42:46 Last access: 11/05/18 20:15:59
Why does one say 5.5 and one say 6.2 client? Everything is installed on the same box ::)
-
-> I do not know the answer to this latest issue but I can make an educated guess. <-
Command Line Administrative Interface - Version 6, Release 2, Level 0.0
That looks like a subcomponent of TSM that has its own version/release/modification tracking.
Ed
-
I am just curious where this is coming from when i do the lslpp -h
Path: /usr/lib/objrepos
tivoli.tsm.server.com
5.5.0.0 COMMIT COMPLETE 12/21/10 15:06:19
5.5.7.0 COMMIT COMPLETE 03/13/14 12:50:30
if we are on 6.2
-
Client & Server are different packages. Client update was likely done to preserve compatibility with the enterprise backup server.
-JD.
-
Thanks for all your help JD.
I am just confused that when I actually login to the tsm console I see V6.2 client, 7.1 server. But when I do the lslpp -h , I see 5.5.x.
Maybe I need to ask IBM.
-
It's possible that TSM 7.1 wouldn't appear in lslpp because it wasn't installed with AIX's installp -- but IBM's new "Installation Manager".
-
It's possible that TSM 7.1 wouldn't appear in lslpp because it wasn't installed with AIX's installp -- but IBM's new "Installation Manager".
thanks again JD! always a huge help!
And by the way- You hit the nail on the head. I found a 7.1 installation document that was used, and sure enough, they used Installation Manager.
That to me means that lslpp -h is useless in my scenario.
-
There's also faint hope that you're already on v7.1?
-JD.
-
There's also faint hope that you're already on v7.1?
-JD.
This particular box is 7.1, 6.2 client.