Hello Richard,

Our DR scenario and load balancing method is to "just" swing the lun's
between servers and start the TSM Instance.

You need to be sure that the passwd and groups files are the same, so the
permissions doesn't change. Also /etc/services is needed for some special
listening ports.
sqllib/db2nodes.cfg  contains the hostname, so you need to update this file
with the new hostname.

If you want (mail me directly for it)  I can share our "start-script" where
we set several things correct every time we boot the TSM Instance.

Regards,
Maurice van 't Loo



2016-05-06 18:55 GMT+02:00 Rhodes, Richard L. <rrhodes AT firstenergycorp DOT 
com>:

> Hello,
>
> Current:  TSM v6.3.5 on AIX 6100-09
> New:      TSM v6.3.5 on AIX 7something
>
> Well, it's time to rollover our TSM AIX servers.  We're purchases new
> pSeries chassis that are getting lpar'ed up to replace the existing systems.
>
> New lpars will be AIX v7.
> All storage is SAN based on either IBM or EMC storage arrays.
> All TSM/DB2 pieces/parts are on separate luns from AIX/rootvg.
>   In rootvg lun:
>      Whatever TSM/DB2 puts in /opt, /var/, /usr
>      (tsm client stuff is in here)
>   In non-rootvg luns:
>      db2 vols
>      db2 log vols (active/mirror/archive)
>      db2 sqllib dir
>      tsm stuff (dsmserv.opt, volhist, etc)
>      tsm disk pools
>
> We would like to
>   - setup new/clean lpars with AIX v7 on the new chassis
>   - install TSM/DB2 binaries
>   - SWING THE non-rootvg luns from the old lpar to the new lpar
>   - bring up TSM . . .
> Is it really that easy????
>
>
> PROBLEM - I can't find anything on how to swing a DB2 database from one
> AIX lpar to a new/clean lpar.  We're a Oracle shop - no one knows DB2
> around here.
>
>
> Q)  Has anyone done a TSM storage swing like this?
>
>
> We are planning a TSM v7.1 upgrade.  We may need to do this to get to AIX
> v7.  I have to check this out.
>
> Thanks
>
> Rick
>
>
>
>
>
> -----------------------------------------
>
> The information contained in this message is intended only for the
> personal and confidential use of the recipient(s) named above. If the
> reader of this message is not the intended recipient or an agent
> responsible for delivering it to the intended recipient, you are hereby
> notified that you have received this document in error and that any review,
> dissemination, distribution, or copying of this message is strictly
> prohibited. If you have received this communication in error, please notify
> us immediately, and delete the original message.
>