TSM Upgrade (HADR Configuration)

bigred

ADSM.ORG Member
Joined
Dec 3, 2012
Messages
13
Reaction score
0
Points
0
PREDATAR Control23

Hi,

We have a TSM Environment with two TSM Servers. One at production and another at the DR site, using HADR for the database. Looking to upgrade from 6.3 to 7.1.6. We know the process for doing fix-pack updates (shown below), but is this process also to be used for upgrading from 6.x to 7.x?

Applying Tivoli Storage Manager Server maintenance
  • On primary server:
  1. Shut down the Tivoli Storage Manager server. This will deactivate the database and stop DB2.
  2. Upgrade Tivoli Storage Manager to the new fix pack level using COI installation.
  3. Start the Tivoli Storage Manager server.
  4. Issue the following command to verify that HADR has resumed:
db2 -hadr -db tsmdb1



  • On standby server:
  1. Keep HADR enabled and running until the primary server is upgraded to the new level.
  2. Because the standby server does not have the Tivoli Storage Manager server running, you must deactivate and stop DB2 manually using DB2 commands:
db2 deactivate db tsmdb1
db2stop

  1. Upgrade Tivoli Storage Manager to the new fix pack level using COI installation
db2start
db2 activate db tsmdb1
db2 -hadr -db tsmdb1


Thanks in advance.
 
PREDATAR Control23

The steps to do an upgrade are the same as applying a fixpack as far as HADR is concerned.
 
PREDATAR Control23

Hi,

We have a TSM Environment with two TSM Servers. One at production and another at the DR site, using HADR for the database. Looking to upgrade from 6.3 to 7.1.6. We know the process for doing fix-pack updates (shown below), but is this process also to be used for upgrading from 6.x to 7.x?

Thanks in advance.
An upgrade from 6.x to 7.x implies a major DB2 release upgrade (9.7 to 10.5).
You cannot use the same upgrade as for fixpack, you must stop hadr on primary and standby server.
 
PREDATAR Control23

fidel:

Yes, that information you replied with, was correct. DB2 changed between versions, so the fixpack wasn't going to work.

What I did:
Halted TSM on Primary host
Stopped HADR on Primary/Secondary host
Upgraded TSM on Primary host
Started TSM on Primary host (make sure it's all good)
Halted TSM on Primary host
Upgraded TSM on Secondary host
Backed up TSMDB1 on Primary Host using db2 commands
Copied the DB2 backup from primary host to secondary host
Restored the DB2 backup onto secondary host and switch the HADR_REMOTE_HOST and HADR_LOCAL_HOST settings around on the secondary host
Started HADR between the hosts
Then started Primary TSM Server
 
PREDATAR Control23

an easy way (with a smaller downtime)
stop HADR and DB2 on standby
upgrade TSM on standby
stop TSM on primary
upgrade TSM on primary
start DB2 and HADR on standby
start DB2 and HADR on primary
start TSM on primary.
 
PREDATAR Control23

Hello,

I'm planning to upgrade TSM with HADR on cluster environment, where shared resources are IP address and small disk storage pool.

Regarding this I have some questions about upgrade on standby:
- when You performed upgrade on standby node did You move all resources from primary node to standby ?
- durring upgrade on standby did You set "Configure this instance on a secondary node of the cluster?" to YES ?

My plan for upgrade is:

stop TSM
stop HADR on both sites
upgrade primary host
start TSM on primary (see if it work correctly)
stop TSM on primary
upgrade TSM on standby
backup DB2 on primary and restore on standby
start HADR
start TSM on prmary host
 
Top