Yes, been there done, that. It's even part of my failover setup. Essential, 
once you've mapped everything, db2icrt and set the default db path as usual 
during installation then run 'catalog db TSMDB1' to make the database known 
again to the DB2 instance.


-- 

Met vriendelijke groeten/Kind regards,

Remco Post
r.post AT plcs DOT nl
+31 6 24821622



Op 9 jan. 2013, om 16:16 heeft Bill Boyer <bjdboyer AT COMCAST DOT NET> het 
volgende geschreven:

> With V5 I was able to move TSM from one computer to another if the
> database/log files were on attached storage (SAN) as long as I mounted them
> to the same path that is in the DSMSERV.DSK file.
> 
> 
> 
> Now with TSM V6 and DB2, if all by db/log/archlog/. files are on attachned
> SAN LUN's, is it possible to install TSM on a new server, recreate the
> instance pointing to the same db/log/archlog paths and then re-attach the
> LUN's? Will the instance come up? Trying to do this without having to
> allocate additional space (short supply!) and doing a restore.
> 
> 
> 
> What happened here is that somehow most of the / root directory on the Linux
> TSM server got deleted, as well as the home/tsminst1 directory. The
> DB/LOG/ARCHLOG are all on attached Netapp LUN's and weren't affected. I was
> hoping that I could just reinstall TSM, recreate the instance pointing to
> the same locations and then map the storage.. Would the instance (and DB2)
> come up? This way they customer wouldn't have to restore from the last
> DBBackup and potentially lose data.
> 
> 
> 
> Bill Boyer
> DSS, Inc.
> (610) 927-4407
> "Enjoy life. It has an expiration date." - ??