ADSM-L

Re: [ADSM-L] TSM server upgrade from v5.5 to v6.2

2014-06-26 20:14:42
Subject: Re: [ADSM-L] TSM server upgrade from v5.5 to v6.2
From: Saravanan <evergreen.sarav AT GMAIL DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 27 Jun 2014 08:12:53 +0800
Hi Erwan,,

Thanks for the information,,, 

Haven't performed test migration but will plan before doing the actual one

Yes we have many clients in 5.1/5.2/5.3 and it stop me to go for 6.3.4

Where as I have performed 5.5.7 to 6.3.4 upgrade when we have all clients in 5.5





By Sarav
+65-82284384


> On 27 Jun, 2014, at 2:47 am, Erwann Simon <erwann.simon AT FREE DOT FR> wrote:
> 
> Hello,
> 
> You cannot export metadata only, if you want to keep your source TSM server 
> available during migration, you need to use "hybrid method" to export newa 
> data and meta-data to the new server after the migration has completed. See 
> this article :
> https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Storage%20Manager/page/Tivoli%20Storage%20Manager%20Version%206%20Hybrid%20Upgrade%20Migration%20Method
> 
> Note that migration could take much less time than you think as IBM 
> statements are generally very conservative. Has you already run a test 
> migration using the same target hardware ?
> 
> Why are you choosing 6.2 as target version ? You'd probably prefer 6.3.4+.
> 
> -- 
> Best regards / Cordialement / مع تحياتي
> Erwann SIMON
> 
> ----- Mail original -----
> De: "Saravanan" <evergreen.sarav AT GMAIL DOT COM>
> À: ADSM-L AT VM.MARIST DOT EDU
> Envoyé: Jeudi 26 Juin 2014 19:09:15
> Objet: Re: [ADSM-L] TSM server upgrade from v5.5 to v6.2
> 
> I have new hardware migration plan but has any one tried this approach
> 
> 
> Step1: Build new hardware with same hostname but temp IP address and connect 
> all the network cables ( it has backup vlan) 
> 
> Same hostname will not impact DB2 database restart 
> 
> Step 2: Take flash copy backup and mount TSM 5.5 server in the new hardware 
> 
> Step 3: upgrade 5.5 to 6.2 and it might take 50 hrs and it will not have 50 
> hrs data in the new TSM server
> 
> Step 4 : once TSM upgrade completed then swap production up address and bring 
> to production 
> 
> Old server will be available with temp IP address 
> 
> It Will take 8 hrs for this cut over 
> 
> Here is my challenge starts 
> 
> How to copy 50 hrs difference to my new database 
> 
> Is there any way to export 50 hrs of meta data ? 
> 
> 
> If it's having only 2 weeks retention then I will straight away decommission 
> hit after 2 weeks but it has daily long retention jobs 
> 
> Please feel free to comment and your help is really appreciated 
> 
> 
> By Sarav
> +65-82284384
> 
> 
>> On 27 Jun, 2014, at 12:44 am, Saravanan <evergreen.sarav AT gmail DOT com> 
>> wrote:
>> 
>> Hi, 
>> 
>> Can any body suggest the best way for TSM server migration ? 
>> 
>> Our TSM 5.5 database is 510 GB and it has lot of archive jobs( long 
>> retention )
>> 
>> We can't perform in place upgrade because we will not get downtime more than 
>> 8 hrs 
>> 
>> It has library manager to manage VTL and 3584 tape library 
>> 
>> 
>> By Sarav
>> +65-82284384
>>