ADSM-L

Re: [ADSM-L] V6.1 to V6.3.3 Upgrade Question

2013-05-23 02:34:23
Subject: Re: [ADSM-L] V6.1 to V6.3.3 Upgrade Question
From: Erwann Simon <erwann.simon AT FREE DOT FR>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 23 May 2013 08:32:25 +0200
Hi all,

See technote 1586232 : Restore a Server v6 database between major Versions / 
Releases
http://www-01.ibm.com/support/docview.wss?uid=swg21586232

-- 
Best regards / Cordialement / مع تحياتي
Erwann SIMON

----- Mail original -----
De: "Remco Post" <r.post AT PLCS DOT NL>
À: ADSM-L AT VM.MARIST DOT EDU
Envoyé: Jeudi 23 Mai 2013 08:10:53
Objet: Re: [ADSM-L] V6.1 to V6.3.3 Upgrade Question

Hi,

ok, there are two parts about this TSM db upgrade. One is the change in db 
schema for TSM. If and when you start a newer TSM server version using an older 
database, the schema automatically gets updated, TSM takes care of that and is 
actually what TSM always does in case of an upgrade.

In the case of a 6.1 to 6.[23] upgrade, db2 also gets upgraded from 9.5 to 9.7. 
Normally the installer performs an upgrade of the database format when you 
upgrade on the same host. Now, I'm quite sure that once you've installed TSM on 
your new host you'll be able to restore the TSM server database on that host, 
but you wind up with both the old db2 format and the old schema. You'll then 
need to start db2, but not the database and run 'db2 upgrade database ...', 
check the db2 9.7 information center for the details. You then can safely start 
TSM and TSM will take care of the rest as I said before.

Now, the big Question is.... will IBM support this? My guess is yes, because 
this is what the installer does during an upgrade. It's a shame it's not quite 
as well documented as could be, I do feel your upgrade path is quite a 
legitimate one.

(btw, I've not quite tested this on windows... and you're going from 32bit to 
64 bit at that....) Make backups (of course) before you begin and don't burn 
your ships behind you before you've verified that the new TSM server works 
after all of this.

On 23 mei 2013, at 06:59, Stefan Folkerts <stefan.folkerts AT GMAIL DOT COM> 
wrote:

> I think you are going to have to go with option 1 if you want to transfer
> the db (not export/replicatie data) because you can't restore a 6.1 TSM
> database on a TSM 6.3 software stack.
> This did work with TSM 5 where you could run an upgrade db command after
> the restore, this is no longer an option with TSM v6 I think.
> 
> I didn't check this so I might get corrected here. :-)
> 
> 
> On Wed, May 22, 2013 at 4:53 PM, white jeff <jeff.white3 AT blueyonder.co DOT 
> uk>wrote:
> 
>> Hi
>> 
>> TSM Server v6.1.5.0
>> On Windows 2008
>> 
>> I have a need to upgrade TSM to  v6.3.3
>> 
>> On the same physical host, no problem, straight forward
>> 
>> The current host is 32-bit, so we will move TSM onto a new physical host
>> with more memory and of course it will be 64-bit to support TSM v6.3. Can't
>> get away from this as the customer has already purchased the hardware.
>> 
>> My question: IBM have a documented migration path from v5 to v6, running on
>> a different physical host. There is also the v6-v6 upgrade path on the same
>> host. Have performed both without issues.
>> 
>> But are there any special requirements for v6-v6 across different hosts?
>> 
>> I was thinking either:
>> 
>> 1) Install v6.1 on the new host, then upgrade to v6.3
>> or
>> 2) Build v6.3 on the new host, then restore a v6.1 database backup down
>> onto v6.3, if that is possible. I remember doing something similar in v5,
>> where the DR server was a higher v5 than the production server. TSM warned
>> me when i restored the database, but was happy to run the restore.
>> 
>> I guess the the other thing to consider is moving the library connectivity
>> from the old to the new host.
>> 
>> Comments/Thoughts welcome
>> 

-- 
Met vriendelijke groeten/Kind Regards,

Remco Post
r.post AT plcs DOT nl
+31 6 248 21 622