tsm 6.1 upgrade - ibm · pdf filetsm database upgrade planning

Tivoli Storage, IBM Software Group

© 2009 IBM Corporation

TSM 6.1 upgrade

Oliver Rautenberg



Agenda – TSM 6.1 upgrade

2

Database Upgrade Options

Upgrade scenarios– Scenario 1: Same system, media method

– Scenario 2: Same system, network method

– Scenario 3: New system, media method

– Scenario 4: New system, network method

DB2 Upgrade Process - to new or existing system?

TSM Database Upgrade Planning

DB & Log Sizing

Upgrading Library manager, Clients & Storage Agents

Preparation– Preparation - Estimating Disk Requirements

– Preparation - Sample for 100GB database 80% Utilized




3

Upgrade Utility Performance - Example

Upgrade Example– Example: Starting Configuration

– Example Upgrade Scenario - Library Manager

– Example: Library Manager Upgraded

– Example Upgrade Scenario - Library Client 1

– Example: Library Client 1 Upgraded



Estimating the DB Upgrade Time

Upgrade DB Example Times

General procedures for upgrading a server to V6.1

Example for Scenario 1: Same system, media method




4








DB & Log Sizing







5

You can upgrade the database in two ways:

Extract data from the original db to media & later load the data into the new dba) New db can be located on the same system (Scenario 1)

b) Or new db can be located on a different system (Scenario 3)

Simultaneously extract data from the original db & load the data into the new dba) New db can be located on the same system (Scenario 2)

b) Or new db can be located on a system connected via network (Scenario 4)

The original server cannot be running while the data is being extracted




6








DB & Log Sizing






Scenario 1: Same system, media method

7

TSM 6.1.0.0DB2 V9.5

2. Install TSM 6.1

4. dsmserv loadformat

5. dsmserv insertdb manifest

Extractdb/dsmserv insertdb done in separate steps

TSM 5.x

3. dsmupgrd extractdb manifest1. dsmupgrd preparedb

or

TSM Server

TSM db




8








DB & Log Sizing






Scenario 2: Same system, network method

TSM 5.xTSM 6.1.0.0

DB2 V9.5

Upgrade in place (same system), using loopback address for HLAExtractdb/dsmserv insertdb done at same time

2. Install TSM 6.1


4a. dsmserv insertdb

1. Dsmupgrd preparedb

4b. dsmupgrd extractdb

TSM Server

TSM db

NEW TSM db




10








DB & Log Sizing






Scenario 3: New system, media method

TSM 5.x TSM 6.1.0.0DB2 V9.5


3. dsmupgrd extractdb manifest

2. Install TSM 6.1



Source Server Target Server

Extractdb/dsmserv insertdb done in separate steps

TSM Server

TSM dbor

New TSM Server

TSM db




12








DB & Log Sizing






Scenario 4: New system, network method


4b. dsmupgrd extractdb2. Install TSM 6.1


4a. dsmserv insertdb

Source Server Target Server

Extractdb/dsmserv insertdb at same time

TSM 5.xTSM 6.1.0.0

DB2 V9.5

TSM Server

TSM db

New TSM Server

TSM db




14








DB & Log Sizing







15

Item Upgrade on an existing system Upgrade on a new system

System hardware

Additional resources (disk space, memory & possibly processor capacity) required

New system that meets requirements is required

–Must upgrade to a new system if the existing server is not supported for V6.1

Software SW must meet requirements for V6.1

V6.1 server cannot coexist with other versions on the same system

–If multiple V5 servers are located on a system, after the V6.1 server is installed all servers are down until the dbs can be upgraded.

SW on the new system must meet requirements for V6.1

SW on the original V5 system must meet requirements for a V5.5 server

Can stage the upgrade of multiple servers, because the V5 server program can be left on the original system

Database movement method

DB can be moved without a network connection or media

Must have either a network connection between the existing and the new systems

or a device and media available to store the extracted database

Storage devices

Existing attached devices can be used New system must have access to all storage used by the original system




16








DB & Log Sizing







17

Upgrading the contents of server database into the new database– Uses a large percentage of a system’s processor

– Requires a high amount of I/O activity

Consider testing the upgrade on non-production system– Gather info on how long the upgrade of the server database will take

– Some databases will take much longer than others to upgrade

– Gather info about the size of the new database compared to the original

If you have multiple TSM servers– Consider upgrading one server first

– Get experience with how the upgrade process will work for your data

– Use the results of the first upgrade to plan for upgrading remaining server

If you have a System Storage Archive Manager Server (data retention)– Run repair expiration command before the upgrade

– Review other specific requirements




18








DB & Log Sizing






DB & Log Sizing

19

Database space requirements– Approximately the same as the size for earlier versions of the server

– Amount of db space required depends on how much data the server is managing

Estimating recovery log requirements– Similar to previous versions of the server operating in roll-forward mode

Estimating total space requirements for the upgrade process– Some additional disk space is needed for the upgrade process

– If upgrading the server on the same system where it is currently located• Need enough space for two copies of the database during the upgrade process

Memory requirements– Memory required to run TSM 6.1 server; 4GB minimum, 8GB recommended

Use worksheet in the DB Upgrade Guide – Part of the TSM 6.1 Manuals

http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp




20








DB & Log Sizing







21

Planning for upgrading library managers and library clients– If using shared libraries, upgrade the server that is the library manager first

– Then upgrade the servers that are library clients

– The servers that are library clients must be at least version 5.x

Planning for upgrading clients– To connect to a V6.1 server, client nodes must be running 5.5 or later

Planning for upgrading storage agents– To connect to a V6.1 server, storage agents must be at version 5.5 or later




22








DB & Log Sizing






Preparation

23

Disk space planning– Upgrade process creates new database

– Determine and configure DB2 space before starting the upgrade

Time– How long can your TSM server be down ?

– Estimate the extract and insert processes

– 5GB/hr is goal for complete upgrade process• But that assumes a “normal” TSM workload• Content Manager DBs have more objects per GB, so they may be considerably slower when

using GB/hr estimate

Verify your monitoring applications support TSM V6




24








DB & Log Sizing






Preparation - Estimating Disk Requirements

25

Note 1: Archive log is a function of daily activityNote 2: V6 DB, DBB, and Extract are a function of current DB utilization




26








DB & Log Sizing






Preparation – Sample for 100GB database 80% Utilized

27




28















Upgrade Utility Performance – Example

29

System configuration– 4-way P570 LPAR with 32GB

– 4 ESS800 LUNs with dual paths for 8 database volumes

– 1 ESS800 LUN for recovery log

– TSM 5.5.2.0

40 GB database at 50% utilization– Pristine database

– dsmserv unloaddb 54 Min 38 Sec

– dsmserv loadformat 2 Min 55 Sec

– dsmserv loaddb 1 Hr 6Min 28 Sec

– dsmserv auditdb 5 Hr 40 Min 51 Sec

– Extract 9 Min 30 Sec

– dsmserv insertdb 3 Hr 8 Min




30















Upgrade Example

31

Library Sharing Environment– 2 OS Instances

– Library Manager with a shared tape library

– 2 Library Clients

LANFree– 2 Storage Agents using 1 Library Client

Preparation– Upgrade Servers and Storage Agents to minimum supported levels to work with New TSM

– Install / Upgrade OS and Hardware as appropriate

– Update SAN Zoning to include new paths




32















Example: Starting Configuration

33




34















Example Upgrade Scenario – Library Manager

35

1. Move Libr Mgr to new OS instance (OS3)– Update SAN Zoning

– Update Libr Mgr Paths

– Update Libr Client connections

– Validate configuration / paths / connectivity

2. Upgrade Libr Clients and Storage Agents to compatible levels

3. Upgrade Libr Mgr to V5.5.2– Validate configuration / paths / connectivity

4. Upgrade Libr Mgr to New TSM in place– Small DB, should be fairly easy and fast




Example: Library Manager Upgraded

36




37















Example Upgrade Scenario – Library Client 1

38

1. Build Libr Client 1 Instance on OS3

2. Upgrade Libr Client 1 using Media Method– Shutdown Libr Client 1

– Extract Database

– Start Libr Client 1

3. Create Libr Client 3 on OS3– Insert DB into Libr Client 3 (from Libr Client1 extract)

4. At this point Libr Client 3 is identical to Libr Client 1– Rename new Libr Client1 to Libr Client3



Example Upgrade Scenario – Library Client 1 …

39

5. Update Connectivity– Add Libr Mgr Paths for Libr Client 3

– Update Libr Client 3 connections


6. Define connectivity between Libr Client 1 and Libr Client 3

7. Update B/A client connectivity– Either update clients or update TSM Server and host OS

8. Export / Import from Libr Client 1 to Libr Client 3 using date/time

9. Shutdown Libr Client 1



Example: Library Client 1 Upgraded

40




41















Example Upgrade Scenario – Library Client 2

42

1. Install Upgrade utility on OS2

2. Shutdown Libr Client 2

3. Install New TSM on OS2

4. Create Libr Client 2 DB instance

5. Upgrade Libr Client 2 in place using network method

6. Start Libr Client 2

7. Validate configuration / paths / connectivity– Libr Mgr

– Storage Agents

– B/A Clients



Example: Library Client 2 Upgraded

43




44
















45

13 GB/hr for an extract to media and a reload on the same system– Network extract/reload will be marginally faster, but require more hw– The process is highly dependant on the system it runs on

• In particular the disk subsystem• Faster times are possible with high performance disks and CPUs• Conversely it can run much slower on old slow hardware




46
















47

Test Time Throughput MB/hr CPU Utilization DB disk % busy

Extract to file 00:08:11 155819 11.4 77

Extract to LTO 4 00:08:11 155819 10.8 58

Insert from file 02:27:11 8663 5.0 89

Insert from LT0 4 02:27:20 8655 5.0 89

For an extract and load from disk:Total used database space / (extractdb + insertdb elapsed time) = 30720 / ( 2:18:51 ) = 30720 / 2.314 = 13,275 MB/hr

Windows 2003 x64 enterprise edition, 16-way 2.9GHz, TSM 5.5.2 31GB, DS8100 disks for database, log, output/input files30GB allocated, 100% used

32 nodesAll data stored in random disk storage pool volumes256GB total random disk storage in 4 volumes




48
















49

1. Preparing for the upgrade

2. Installing the upgrade utilities on the original server

3. Preparing the database of a V5 server for upgrade

4. Same-system upgrade only: Uninstalling the V5 program before installing V6.1

5. Installing the V6.1 server

6. Creating the directories and the user ID for the upgraded server instance

7. Upgrading the server, using one of the following methods:a. Upgrading the server using the upgrade wizard

b. Upgrading the server manually using utilities

8. Completing the upgrade by taking important first steps:a. Verifying access to storage pools on disk

b. Starting the server instance after the upgrade

c. Registering licenses

d. Backing up the database after upgrading the server

e. Verifying the upgraded server

f. Updating automation

g. Monitoring the upgraded server




50
















51

Live Demo

Source: http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.nav.doc/t_upgrading.html

Current state: TSM Server 5.5.1.0 on Windows 2003

Preparation:

1. TSM server halt

2. Install 5.5.2 upgrade package: 5.5.2.0-TIV-TSMUPG-Windows.exe

Upgrade to 6.1:

1. dsmupgrd preparedb

"c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd" preparedb 1>>prepare.out 2>&1




52

C:\>"c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd" preparedbANR0900I Processing options file c:\program files\tivoli\tsm\server1\dsmserv.opt.ANR7800I DSMSERV generated at 12:07:33 on Mar 12 2009.

Tivoli Storage Manager for WindowsVersion 5, Release 5, Level 2.0

Licensed Materials - Property of IBM

(C) Copyright IBM Corporation 1990, 2007.All rights reserved.U.S. Government Users Restricted Rights - Use, duplication or disclosurerestricted by GSA ADP Schedule Contract with IBM Corporation.

ANR4726I The ICC support module has been loaded.ANR0990I Server restart-recovery in progress.ANR0200I Recovery log assigned capacity is 8 megabytes.ANR0201I Database assigned capacity is 12 megabytes.ANR0306I Recovery log volume mount in progress.ANR0285I Database page shadowing started using file dbpgshdw.bdt.ANR0353I Recovery log analysis pass in progress.ANR0354I Recovery log redo pass in progress.ANR0355I Recovery log undo pass in progress.ANR0352I Transaction recovery complete.ANR1635I The server machine GUID, bd.30.fa.91.2d.79.11.de.88.ba.4c.67.d8.ff.1d.4e, has initialized.ANR4726I The NAS-NDMP support module has been loaded.ANR1792W HBAAPI vendor library failed to load or is missing.ANR7808W Sun Microsystems Library Attach module libacs.dll is not available from the system.ANR1305I Disk volume D:\TSMDATA\SERVER1\DISK1.DSM varied online.ANR2718W Schedule manager disabled.ANR0129I Database upgrade completed successfully.ANR0993I Server initialization complete.ANR0916I TIVOLI STORAGE MANAGER distributed by Tivoli is now ready for use.ANR0991I Server shutdown complete.




53

1.1 Uninstall TSM 5.5.1.0 (server and license)

2. Install TSM 6.1

3. dsmupgrd extractdb




54

D:>"c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd" extractdb devclass=file manifest=.\manifest.txtANR0900I Processing options file c:\program files\tivoli\tsm\server1\dsmserv.opt.ANR7800I DSMSERV generated at 12:07:33 on Mar 12 2009.




ANR4726I The ICC support module has been loaded.ANR0990I Server restart-recovery in progress.ANR0200I Recovery log assigned capacity is 8 megabytes.ANR0201I Database assigned capacity is 12 megabytes.ANR0306I Recovery log volume mount in progress.ANR0285I Database page shadowing started using file dbpgshdw.bdt.ANR0353I Recovery log analysis pass in progress.ANR0354I Recovery log redo pass in progress.ANR0355I Recovery log undo pass in progress.ANR0352I Transaction recovery complete.ANR1635I The server machine GUID, bd.30.fa.91.2d.79.11.de.88.ba.4c.67.d8.ff.1d.4e, has initialized.ANR4726I The NAS-NDMP support module has been loaded.ANR1792W HBAAPI vendor library failed to load or is missing.ANR7808W Sun Microsystems Library Attach module libacs.dll is not available from the system.ANR1305I Disk volume D:\TSMDATA\SERVER1\DISK1.DSM varied online.ANR4029I EXTRACTDB: Database checkpoint started.ANR4030I EXTRACTDB: Database checkpoint completed.ANR0610I EXTRACTDB started by ADMINISTRATOR as process 1.ANR8340I FILE volume D:\TSMDATA\40215292.ost mounted.ANR1360I Output volume D:\TSMDATA\40215292.ost opened (sequence number 1).ANR1361I Output volume D:\TSMDATA\40215292.ost closed.ANR1380I EXTRACTDB: Output stream 1 used volume D:\TSMDATA\40215292.ost.ANR1382I EXTRACTDB: Process 1, database extract, has completed.ANR1383I EXTRACTDB: Found 118 database objects.ANR1384I EXTRACTDB: Processed 32 database objects.ANR1385I EXTRACTDB: Skipped 86 empty database objects.ANR1386I EXTRACTDB: Failed to process 0 database objects.ANR1387I EXTRACTDB: Processed 185 database records.ANR1388I EXTRACTDB: Read 37 database pages.ANR1389I EXTRACTDB: Wrote 35,326 bytes.ANR1390I EXTRACTDB: Elapsed time was 0:00:11.ANR1391I EXTRACTDB: Throughput was 0.00 megabytes per hour.




55

Log on as an administrator.

db2icrt -u db2user1 server1Enter current password for db2user1:

DB20000I The DB2ICRT command completed successfully.

Log on to the system using the user ID that owns the V6.1 server instance (instance user ID). db2user1

Copy the configuration files to the instance directory that you created for the new server

Edit the server options file

Change the default path for the database to be the drive where the instance directory for the server is located. Complete the following steps

Click Start > Programs > IBM DB2 > DB2TSM1 > Command Line Tools > Command Line Processor.

-> quit

set DB2INSTANCE=server1

db2 update dbm cfg using dftdbpath d:




56

D:\tsm\server1>"c:\Program Files\Tivoli\TSM\server\dsmserv" loadformat dbdir=d:\tsm\db001 activelogsize=2048 activelogdir=d:\tsm\log mirrorlogdir=d:\tsm\logmirror archlogdir=d:\tsm\archlogANR0900I Processing options file D:\tsm\server1\dsmserv.opt.ANR4858I Option MIRRORWRITE is no longer supported and there is no directreplacement for this capability.ANR7800I DSMSERV generated at 16:44:45 on Mar 13 2009.




ANR4726I The ICC support module has been loaded.ANR0152I Database manager successfully started.ANR0152I Database manager successfully started.ANR1380I The buffer pool monitor switch is enabled.ANR1004I Server formatting complete, database ready for loading.ANR0369I Stopping the database manager because of a server shutdown.ANR2976I Offline DB backup for database TSMDB1 started.ANR2974I Offline DB backup for database TSMDB1 completed successfully.




57


D:\Software\server>"c:\Program Files\Tivoli\TSM\server\dsmserv" insertdb manifest=.\manifest.txtANR0900I Processing options file D:\tsm\server1\dsmserv.opt.ANR4858I Option MIRRORWRITE is no longer supported and there is no directreplacement for this capability.ANR7800I DSMSERV generated at 16:44:45 on Mar 13 2009.




ANR4726I The ICC support module has been loaded.ANR0990I Server restart-recovery in progress.ANR0152I Database manager successfully started.ANR1380I The buffer pool monitor switch is enabled.ANR1636W The server machine GUID changed: old value (), new value (bd.30.fa.91-.2d.79.11.de.88.ba.4c.67.d8.ff.1d.4e).ANR7808W Sun Microsystems Library Attach module libacs.dll is not available from the system.ANR8200I TCP/IP Version 4 driver ready for connection with clients on port 1500.ANR8340I FILE volume D:\TSMDATA\40215292.ost mounted.ANR1363I Input volume D:\TSMDATA\40215292.ost opened (sequence number 1).ANR1364I Input volume D:\TSMDATA\40215292.ost closed.ANR1395I INSERTDB: Process 1, database insert, has completed.ANR1397I INSERTDB: Found 32 database objects.ANR1398I INSERTDB: Processed 32 database objects.ANR1399I INSERTDB: Failed to process 0 database objects.ANR1517I INSERTDB: Processed 185 database records.ANR1518I INSERTDB: Read 35,468 bytes.ANR1519I INSERTDB: Elapsed time was 0:00:10.ANR1445I INSERTDB: Throughput was 0.00 megabytes per hour.ANR1446I RUNSTATS: Table updating statistics started.ANR0136I Table updating statistics performed successfully for 119 of 119.ANR1528I RUNSTATS: Table updating statistics completed in 0:00:16.ANR0369I Stopping the database manager because of a server shutdown.




58

Configuring the system for database backup

1. Create the tsmdbmgr.env file in the d:\tsm\server1 directory with the following contents:

DSMI_CONFIG=d:\tsm\server1\tsmdbmgr.opt

DSMI_LOG=d:\tsm\server1

2. Set the DSMI_ api environment-variable configuration for the database instance:

a. Open a DB2 command window. One method of doing this is by going to the C:\Program Files\Tivoli\TSM\db2\bin directory, or if you installed Tivoli Storage Manager in a different location, go to the db2\bin subdirectory in your main installation directory. Then, issue this command:

db2cmd

b. Issue this command:

db2set -i server1 DB2_VENDOR_INI=d:\tsm\server1\tsmdbmgr.env




59

Configuring the system for database backup

1. Create the tsmdbmgr.env file in the d:\tsm\server1 directory with the following contents:

DSMI_CONFIG=d:\tsm\server1\tsmdbmgr.opt

DSMI_LOG=d:\tsm\server1

2. Set the DSMI_ api environment-variable configuration for the database instance:


db2cmd

b. Issue this command:

db2set -i server1 DB2_VENDOR_INI=d:\tsm\server1\tsmdbmgr.env




60

Configuring the system for database backup …

3. Create the tsmdbmgr.opt file in the d:\tsmserver1 directory with the following contents: nodename $$_TSMDBMGR_$$ commmethod tcpiptcpserveraddr localhosttcpport 1500passwordaccess generateerrorlogname d:\tsm\server1\TSMDBMGR_TSMSERVER1.log

4. Stop and start the database instance:


db2cmd

b. Set the database instance:

SET DB2INSTANCE=server1

c: Stop DB2:

db2stop




61

Configuring the system for database backup …

d. Start DB2:

db2start C:\Program Files\Tivoli\TSM\db2\BIN>db2start

SQL1063N DB2START processing was successful.

5. issue the following commands:

set DSMI_CONFIG=d:\tsm\server1\tsmdbmgr.opt

"C:\Program Files\Tivoli\TSM\server\dsmsutil UPDATEPW /NODE:$$_TSMDBMGR_$$ /PASSWORD:TSMDBMGR /VALIDATE:NO"



TSM 6.1 updgrade

62

Questions?

tsm 6.1 upgrade - ibm · pdf filetsm database upgrade planning

Documents