I want to thank those who helped figure this out.
I now have a procedure for rolling the TSM/DB2 disks to a new LPAR.
I thought I'd share it with you. Like a lot of things, it's fairly easy once
you know how.
==============
= procedure
==============
Situation:
All disks to be swung to new lpar contain ALL of TSM/DB2 pieces/parts. This
includes: db2 filesystems, db2 logs, db2 archive logs, sqllib dir, tsm config
(dsmserv.opt, etc). What is not being swung is rootvg filesystems (/, /usr,
/var, /opt, /home). The DB2 owner's home dir is on the disks being swung.
To swing TSM instance to new lpar:
==> On New LPAR:
AIX up and running
SET AIX to use IOCP
smitty iocp
change to "enable"
REBOOT - REQUIRES REBOOT to take effect (really??)
TAPE
install Atape
zone tape drives to new lpar
cfgmgr
change rmt device names to new scheme
stage cmds to alter drive paths on library managers
ADD user/group for tsm/db2 owners
mkgroup id=1000 tsmdb2group
mkuser id=1000 pgrp=tsmdb2group home=/tsmdata/tsmX/config tsmdb2userid
set pwd to xxxxxxx (as root: passwd tsmdb2userid)
make tsmdb2userid a NON-LOGIN account
SETUP Datadomain 10g adapter and mount
(DD contains TSM/DB2 backup, file devices, TSM config files)
mkdir -p /DD/tsmX
chmod -R 755 /DD
chown tsmdb2userid:tsmdb2group /DD/tsmX
add mount to /etc/filesystems
DD: set share to mount to new lpar
mount /DD/tsmX
ADD db2 lines to /etc/services
(port number MUST be consecutive, but value doesn't matter)
DB2_tsmdb2userid 60000/tcp
DB2_tsmdb2userid_1 60001/tcp
DB2_tsmdb2userid_2 60002/tcp
DB2_tsmdb2userid_END 60003/tcp
INSTALL TSM license from base release
IMSTALL TSM at same level as old lpar
INSTALL TSM BA client
copy BA client config files from old lpar
dsm.sys, dsm.opt, inclexcl, other
ADD DB2 api stanza to /opt/tivoli/tsm/server/bin/dbbkapi/dsm.sys
(this is new in TSM v7.1)
(remove same from BA client dsm.sys)
SERVERNAME TSMDBMGR_tsmdb2userid
* ----------------------------------------------------------------------- *
* This stanza was added by the TSM Instance Configuration Utility *
* ----------------------------------------------------------------------- *
COMMMETHOD SHAREDMEM
SHMPORT 1510
NODENAME $$_TSMDBMGR_$$
ERRORLOGNAME /tsmdata/tsmX/config/tsmdbmgr.log
(^CHANGE THAT tsmX!!!)
ADD to /etc/inittab
tsm:2:once:/etc/rc.tsm # start tsm client
tsmX:2:once:/tsmdata/tsmX/config/rc.start_tsm_in_background.ksh
>/dev/console 2>&1
fmc:2:respawn:/opt/tivoli/tsm/db2/bin/db2fmcd #DB2 Fault Monitor Coordinator
(probably already there from TSM install)
FUDGE /etc/hosts
block communications to other TSM instances during testing
9.9.9.9 <aliases for all other TSM instances>
add entries to /etc/hosts on the hostname IP for this TSM instance
tsmX tsmX.<domain>.com
==> Swing storage to new lpar
OLD lpar:
backup db
stop activity
shutdown tsm
umount
varyoffvg
exportvg
rmdev hdisks
REZONE/MASK to new lpar
NEW lpar:
cfgmgr
set hdisk bits
importvg
varyonvg
mount
check mount order in /etc/filesystems
==> Fix/Config/Test #1
CHANGE/CHECK /tsmdata/tsmX/config/sqllib/db2nodes.cfg
new lpar has hostname with "-new"
change file to have new hostname
CHECK instance known to db2
/opt/tivoli/tsm/db2/instance/db2ilist
(returns nothing - this is correct!!!)
TEST db2 start:
su - tsmdb2userid
db2start
db2stop
CHECK instance known to db2
/opt/tivoli/tsm/db2/instance/db2ilist
tsmdb2userid
(returns one line with "tsmdb2userid")
TEST TSM start:
/tsmdata/tsmX/config/rc.start_tsm_in_forground.ksh
==> Rename server (UNIX team)
CHANGE server hostnames
smitty hostname
old lpar: servernameX servernameX-old
new lpar: servernameX-new servernameX
CHANGE DNS accordingly
MOVE tsmX alias to new lpar DNS entry
CHANGE /tsmdata/tsmX/config/sqllib/db2nodes.cfg
change to new server name
CHECK that /etc/hosts entry for server has hostname on it
==> Fix/Config/Test #2
TEST db2 start:
su - tsmdb2userid
db2start
db2stop
TEST TSM start:
/tsmdata/tsmX/config/rc.start_tsm_in_forground.ksh
TEST TSM db backup
UNFUDGE /etc/hosts
remove
9.9.9.9 tsm1 tsm2 tsm3 tsm4 tsm5 tsm6 tsm7 tsm8 tsm9 tsmsap1 tsmsap2
tsmlm1 tsmlm2 tsmapp
tsmX tsmX.fenetwork.COM
ON LIBRARY MANAGERS - run cmds to set drive paths to tape drives
==> START TSM
TSM start:
/tsmdata/tsmX/config/rc.start_tsm_in_background.ksh
CHECK TSM server-to-server communications
ping server tsmX
update server tsmX forcesync=yes
TEST tape mount/unmount
From: Rhodes, Richard L.
Sent: Friday, May 06, 2016 12:56 PM
To: ADSM: Dist Stor Manager <ADSM-L AT VM.MARIST DOT EDU>
Cc: Ake, Elizabeth K. <akee AT firstenergycorp DOT com>
Subject: Rolling a TSM instance to a new server/lpar
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.
|
