Fred, According to the table at: http://www-01.ibm.com/support/docview.wss?uid=swg21302789
the TSM library master could be at 6.1, and the storage agent left behind at 5.5 or even 5.4. You are remembering outdated information, I think. So this should simplify your plans. This was very good news for us, too. We have one library master that serves 9 other TSM servers, plus 5 Lan-free agents. The thought of having to upgrade ALL of them on the same day was daunting indeed. But thankfully, we can do them in groups. Because we have as many as 4 instances on one server, we will be forced by the upgrade requirements to upgrade all of those on the same day. At least, I think that is true. When I upgraded a test server from 5.4 to 6.1 a couple weeks ago, I was told to uninstall 5.4 before installing 6.1, and that they could not exist on the same server. Am I understanding this correctly? Best Regards, John D. Schneider The Computer Coaching Community, LLC Office: (314) 635-5424 / Toll Free: (866) 796-9226 Cell: (314) 750-8721 -------- Original Message -------- Subject: [ADSM-L] 5.5 -> 6.2 From: Fred Johanson <f...@uchicago.edu> Date: Thu, March 04, 2010 4:18 pm To: ADSM-L@VM.MARIST.EDU We are making plans for the upgrade from 5.5 -> 6.2 this Spring. One, of many, thing that's causing much headscratching is consistency. I know that the Library Manager must be first. Since it has no clients, no problems with the conversion. However, the LAN-FREE storage agents, which must be at the same level as the LM, are all on our largest instance, which I'd prefer to leave till last in the conversion schedule. We think that the client level for those machines must also be at the same level as the LM. Also on that instance are the datamovers using NDMP. We're not sure if those must also be at the same level as the LM. We think the approach should be : 1. Upgrade the LM, 2. Upgrade the necessary agents and clients, and 3. Tackle a less complicated instance to convert completely. Are we thinking in the right track here? All thoughts appreciated. Another unanswered question is whether we can do the conversion directly into 6.2, or do we have to go 6.1.0 -> 6.2? If the latter, will we have to pass quickly thru 6.1.2? I hope this will be addressed in the documentation, whenever that becomes available. Fred Johanson TSM Administrator University of Chicago 773-702-8464
