Re: Rolling a TSM instance to a new server/lpar

[Maurice van 't Loo]

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. :

> 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.
>

Re: Rolling a TSM instance to a new server/lpar

[Shawn DREW]

I go through this exercise when performing DR tests and we swing over the 
storage.  Here is my cheat sheet:

- create instance owner user 

db2icrt -a server -s ese -u tsminstance tsminstance
su - tsminstance

#copy/validate:
~/sqllib/usercshrc
~/sqllib/userprofile
~/.bash_profile #or whatever shell profile to source the db2 env (. 
~/sqllib/db2profile)

db2set -i tsminstance DB2CODEPAGE=819
db2 update dbm cfg using dftdbpath /instanceDIR
db2 catalog database tsmdb1
db2 list database directory

# copy/validate db backup stanza
vi /opt/tivoli/tsm/client/api/bin64/dsm.sys


This message and any attachments (the "message") is intended solely for the 
addressees and is confidential. If you receive this message in error, please 
delete it and immediately notify the sender. Any use not in accord with its 
purpose, any dissemination or disclosure, either whole or partial, is 
prohibited except formal approval. The internet can not guarantee the integrity 
of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore 
be liable for the message if modified. Please note that certain functions and 
services for BNP Paribas may be performed by BNP Paribas RCC, Inc.


Unless otherwise provided above, this message was sent by BNP Paribas, or one 
of its affiliates in Canada, having an office at 1981 McGill College Avenue, 
Montreal, QC, H3A 2W8, Canada. To the extent this message is being sent from or 
to Canada, you may unsubscribe from receiving commercial electronic messages by 
using this link: www.bnpparibas.ca/en/unsubscribe/ 
. See www.bnpparibas.ca 
 for more information on BNP Paribas, in Canada.

Re: Rolling a TSM instance to a new server/lpar

[Rhodes, Richard L.]

Thanks for the help.

I am somewhat familiar with db2ilist (and db2iset, db2idrop) from a 
"Inconsistent Home Directory" problem when we upgraded to TSM v6.   

Will have to test. . . .

Thanks!

Rick



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Michael Prix
Sent: Friday, May 06, 2016 2:52 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Rolling a TSM instance to a new server/lpar

Hello Richard,

  gererally yes, it's that easy, but some more steps:

- on the old server do a "db2ilist" and for each instance reported do a 
"db2icrt " on the new server.

- be sure to have the same TSM-Server levels on old and new server, otherwise
you have to perform a "db2iupdt " for each instance. Naturally,
you can only upgrade, and the instance has to be mounted when performing the
command.

To find the full paths to the programs mentioned is left as an exercise for
the reader.

-- 
Michael Prix On Fr, 2016-05-06 at 16:55 +, Rhodes, Richard L. wrote:
> 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.


-
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.

Re: TSM node replication sessions too few

[Patrick Miller]

It is indeed the last filespace, it's just so large at 2T.

On Sat, May 7, 2016 at 3:08 AM, Stefan Folkerts 
wrote:

> Could it be you have one object/filespace left to replicate?
> I don't think that can be done with multiple sessions.
> Normally I see the sessions go up to the max setting but then drop back
> down when there are no longer that many filespaces left to do. Often you
> will see one sessing running for the last filespace when replicating many
> nodes to start with.
>
> On Fri, May 6, 2016 at 4:51 PM, Patrick Miller  wrote:
>
> > I'm running TSM 6.3.4 and doing node replication tape to tape between
> > servers (no choice)
> >
> > I have setup maxsessions to 8 because I have several Oracle DBs that are
> > 2T.
> >
> > When replication starts it opens 8 sessions but then closes all but one.
> >
> > When initial RMAN backup is done, it uses 5 drives so I was hoping to get
> > it that way in replication as well.
> >
> > At this point, even if I could get it to run 2 sessions it would be a
> great
> > help.
> >
> > Anyone know how to force more sessions to be used?
> >
> > --
> > Thanks,
> >
> > Patrick L. Miller
> > Computer Systems Analyst II
> > Prince George's County Schools
> > 301-952-6797 pmil...@pgcps.org
> >
> >  ___  _-_
> >  \==_=_/ .---'---`---.
> >  \_ \\._./
> >\ \   /  /`-_-'
> >__,--`.`-'..'-_
> >   /  ||  *Systems*
> >`--.,-'
> >
>



--
Thanks,

Patrick L. Miller
Computer Systems Analyst II
Prince George's County Schools
301-952-6797 pmil...@pgcps.org

 ___  _-_
 \==_=_/ .---'---`---.
 \_ \\._./
   \ \   /  /`-_-'
   __,--`.`-'..'-_
  /  ||  *Systems*
   `--.,-'

Re: TSM Server 7.1.4 woes

[Schofield, Neil (Storage & Middleware, Backup & Restore)]

For info, the full text of APAR IT15117 is now available on the IBM website at
http://www.ibm.com/support/entdocview.wss?uid=swg1IT15117

I'd like to express my gratitude to Michael Prix for uncovering this issue, and 
to Andrew Raibeck for his tenacity in getting to the bottom of it.

Regards
Neil Schofield
Tivoli Storage Manager SME
Backup & Recovery | Storage & Middleware | Central Infrastructure Services | 
Infrastructure & Service Delivery | Group IT
LLOYDS BANKING GROUP




Lloyds Banking Group plc. Registered Office: The Mound, Edinburgh EH1 1YZ. 
Registered in Scotland no. SC95000. Telephone: 0131 225 4555. Lloyds Bank plc. 
Registered Office: 25 Gresham Street, London EC2V 7HN. Registered in England 
and Wales no. 2065. Telephone 0207626 1500. Bank of Scotland plc. Registered 
Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland no. SC327000. 
Telephone: 03457 801 801. Cheltenham & Gloucester plc. Registered Office: 
Barnett Way, Gloucester GL4 3RL. Registered in England and Wales 2299428. 
Telephone: 0345 603 1637

Lloyds Bank plc, Bank of Scotland plc are authorised by the Prudential 
Regulation Authority and regulated by the Financial Conduct Authority and 
Prudential Regulation Authority.

Cheltenham & Gloucester plc is authorised and regulated by the Financial 
Conduct Authority.

Halifax is a division of Bank of Scotland plc. Cheltenham & Gloucester Savings 
is a division of Lloyds Bank plc.

HBOS plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in 
Scotland no. SC218813.

This e-mail (including any attachments) is private and confidential and may 
contain privileged material. If you have received this e-mail in error, please 
notify the sender and delete it (including any attachments) immediately. You 
must not copy, distribute, disclose or use any of the information in it or any 
attachments. Telephone calls may be monitored or recorded.