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
>