Upgrade Considerations for TSM V6

1. Upgrade Considerations forTSM V6 Randy Larson IBM Advanced Technical Support larsonr@us.ibm.com

2. Introduction • We will not be discussing features and functions • Future sessions will cover added function • The intent here is to put into perspective the resources, time, and effort that are required to upgrade to TSM V6 using DB2 • Refer to announcement material or IBM marketing for specific details on supported environments, software levels, and new function

3. Topics • The Basics • Preparation • Upgrade Considerations • Upgrade complicating factors • Example upgrade • Scripting Considerations

4. The Basics • Major restructuring of the TSM database • Why do this ? • Current DB is reaching its limits in terms of size, performance, and function • Position for long term growth • Position for future additional function • Free TSM development resources DB maintenance • Performance goal is to provide “equivalent performance” • Compared to Version 5.5 • “Port” to DB2 has some side effects • Yes, there will be new function • Not part of this discussion • !! Not the solution to every problem !!

5. The Basics • Increase in real memory recommendations • 4X increase to accommodate DB2 • Increase in TSM DB size possible / probable • DB2 space will expand and contract based on workload • Increase in overall recovery log size • Only support for roll-forward mode • DB Upgrade process includes: • Prepare current TSM server Database • Extract all DB entries from current TSM DB • Insert all DB entries into DB2 via TSM • Time consuming upgrade when compared to previous TSM software upgrades • Fall back is re-install of previous code and DB • Potentially more complex than previously experienced • No exposure to data loss if you plan ahead

6. What you get and what you do not get • New database • DB2 is external to TSM, installed with TSM package • Must use the DB2 image that is installed with TSM • Don’t install on a system with DB2 already installed • One-to-One relationship between TSM instance and database instance • No merge of multiple TSM instances into one database • Can run multiple TSM / database instances on same OS image • No Cross platform upgrade • For instance, you cannot upgrade from TSM on Windows to TSM on AIX

7. What you get and what you do not get • Theoretical DB size will increase, BUT ... • Recommended maximum DB size will be limited initially • Plan for equivalent number of objects • New function will add to DB growth • New Recovery Log mechanism • DB2 logs may require more disk space • Size depends on activity and DB Backup frequency • Can NOT run multiple versions of TSM on same OS instance • Same restriction as prior releases

8. Upgrade Utility • Upgrade utility is a separate install package • Can coexist with existing TSM versions • Must use currently supported version of TSM • Upgrade process: • Upgrades existing DB to V5.5.x • Extracts from existing V5.5.x database • Inserts into DB2 using TSM server (not the utility itself) • Source server is down during extract process • If TSM V5.5.x, existing TSM server can restart afterwards • If prior to V5.5.x, the DB needs to be restored first

9. New DB Backup Process • Utilizes existing DB2 to TSM implementation • Built into DB2, no separate product • Setup (documented in Installation Guide) • Install 64bit API (installed with server install) • Configure environment variables • Update configuration files (AIX example) • Dsm.sys • /home/tsminst1/sqllib/userprofile • tsmdbmgr.opt • Set password (must be “TSMDBMGR”) • /home/tsminst1/sqllib/adsm/dsmapipw • Logoff/Logon and restart TSM to pick up new environment • Configure device class (instance owner needs write access) • Issue TSM commands: • SET DBRECOVERY devclass • BACKUP DB DEVC=devclass TYPE=full

10. Preparation • OS Levels • Be current – check web and documentation • TSM Levels • Recommended starting point is TSM V5.5.2 • Preparation could include: • DB unload/load might help extract process • DB audit • Consider 24X7 requirements for TSM availability • Applications such as CDP, Content Manager, and Space Manager assume TSM server is always available • Customer DBs may need to backup logs hourly

11. Preparation • 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 to 10GB/hr is current goal for 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

12. Preparation - Estimating Disk Requirements Note 1: Archive log is a function of daily activity Note 2: V6 DB, DBB, and Extract are a function of current DB utilization

13. Preparation – Sample for 100GB database 80% Utilized

14. Preparation • Picking the first TSM to upgrade • Ideal first candidate is small, stand-alone TSM • Do you use Library Sharing ? • Library Manager must be at a higher level that Library Clients • Library Clients must be at a supported level • Do you use LANFree ? • Storage Agents must be at a supported level • Test, test, test • Have a real test system • Test the upgrade process • Test upgrade with a large DB to make your own estimate of time • Test the back-out procedure • Test the upgraded database

15. Considerations Summary • Resources • DB/LOG disk requirement will grow • Recommended memory per TSM instance increases • Plan for same database I/O performance as before • Time • Estimate upgrade time and plan your TSM downtime • Integrated solutions (ex. Content Manager) • Multiple TSM instances • How many upgrades can you do in a weekend ? • IP Address concerns • Interconnectivity concerns • If upgrade in place, must upgrade all TSM instances • Consider the various upgrade options

16. Upgrade Utility Performance – One Example • 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 V5.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

17. Upgrade Planning - Options

18. Upgrade Process: Media - Same server • Install the upgrade tool • Prepare V5.5 database • Shutdown TSM V5.5 • Install New TSM Product • Prepare New TSM database • Two steps to upgrade • Extract V5.5 DB objects to media (disk or tape) • Insert DB objects from media into New TSM DB • Start New TSM • Configure TSM DB Backup and take backup

19. Upgrade Process: Network - Same server • Install upgrade tool • Prepare V5.5 database • Shutdown TSM V5.5 • Install New TSM Product • Prepare New TSM database • Single step to upgrade • Insert DB objects from network into New TSM DB • Extract V5.5 DB objects to network • Start New TSM • Configure TSM DB Backup and take backup

20. Upgrade Process: Media - New server • On V5.5 system • Install upgrade tool • Prepare V5.5 database • Shutdown TSM V5.5 • Extract V5.5 DB objects to media (disk or tape) • Restart TSM V5.5 (optional) • On New TSM system • Verify Hardware Configuration • Install New TSM Product • Prepare New TSM database • Insert DB objects from media into New TSM DB • Stop TSM V5.5 (if running) • Start New TSM • Configure TSM DB Backup and take backup • Synchronize database contents if necessary

21. Upgrade Process: Network - New server • On New TSM system • Verify Hardware Configuration • Install New TSM product • Prepare New TSM database • On V5.5 system • Install upgrade tool • Prepare V5.5 database • Shutdown TSM V5.5 • Single step to upgrade • Insert DB objects from network into New TSM server • Extract V5.5 DB objects from V5.5 server to network • TSM V5.5 can be restarted when extract portion completes • Start New TSM • Configure TSM DB Backup and take backup • Synchronize database contents if necessary

22. Complicating Factors • Multiple TSM instances on single OS • Library Manager configurations • LANFree configurations • New host system • 24X7 Availability Requirements

23. Multiple TSM instances on single OS • Only 1 version of TSM code can be installed at a time • Same as prior upgrades • If upgrade in place (either media or network) • All instances must upgraded at same time • If upgrade to new system (either media or network) • Need to update network address on clients • Need to update network address on storage agents

24. Library Manager configurations (Libr Mgr) • Library Manager must upgrade first • Library Manager moves to new server: • Move V5.5 Library Manager to new system • Update connectivity, paths, etc • Validate Library Manager configuration works with existing V5.5 code • Upgrade Library Manager to New TSM in place • Library Manager remains on existing server • What else is on that OS instance ?

25. Library Manager configurations (Libr Clients) • Library Manager must be New TSM first • If Library Client moves to new server: • Move V5.5 Library Client to new system • Update connectivity, paths, etc • Validate Library Client configuration works with existing V5.5 code • Upgrade Library Client to New TSM • If Library Client remains on existing server • What else is on that OS instance ?

26. LANFree configurations • Storage Agents need to be compatible with New TSM server • How is TSM Server being upgraded • Same or new system ? • Is this also part of a Library sharing environment ?

27. New OS Instance • IP address changes • Clients, Library sharing, Storage Agents • DNS can be helpful • Hardware changes • Disk space and connectivity • Tape and/or other device support • SAN changes • Zoning changes • LUN Masking changes

28. 24X7 Requirements • TSM V5.5 down for the extract • How will the application deal with TSM unavailability ? • Possibility: • Install V5.5 product on new system • Build V5.5 DB using database backup • Upgrade in place to New TSM • Point application to New TSM server • Synchronize application with New TSM server • Export / Import using date/time from V5.5 to New TSM server

29. Upgrade Example • 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

30. Example: Starting Configuration OS2 OS1 LIBR CLIENT 1 LIBR MGR LIBR CLIENT 2 Server to Server Server to Server V5 V5 V5 SAN Paths Storage Agents Shared Library

31. Example Upgrade Scenario – Library Manager !! This is not the only way to upgrade !! • Move Libr Mgr to new OS instance (OS3) • Update SAN Zoning • Update Libr Mgr Paths • Update Libr Client connections • Validate configuration / paths / connectivity • Upgrade Libr Clients and Storage Agents to compatible levels • Upgrade Libr Mgr to V5.5.2 • Validate configuration / paths / connectivity • Upgrade Libr Mgr to New TSM in place • Small DB, should be fairly easy and fast • Validate configuration / paths / connectivity

32. Example: Library Manager Upgraded OS2 OS1 OS3 LIBR CLIENT 1 LIBR CLIENT 2 LIBR MGR Server to Server Server to Server V5 V5 New Paths Upgraded Storage Agents Shared Library

33. Example Upgrade Scenario – Library Client 1 !! This is not the only way to upgrade !! • Build Libr Client 1 Instance on OS3 • Upgrade Libr Client 1 using Media Method • Shutdown Libr Client 1 • Extract Database • Start Libr Client 1 • Create Libr Client 3 on OS3 • Insert DB into Libr Client 3 (from Libr Client1 extract) • At this point Libr Client 3 is identical to Libr Client1 • Rename new Libr Client1 to Libr Client3

34. Example Upgrade Scenario – Library Client 1 ... !! This is not the only way to upgrade !! • Update Connectivity • Add Libr Mgr Paths for Libr Client 3 • Update Libr Client 3 connections • Validate configuration / paths / connectivity • Define connectivity between Libr Client 1 and Libr Client 3 • Update B/A client connectivity • Either update clients or update TSM Server and host OS • Export / Import from Libr Client 1 to Libr Client 3 using date/time • Shutdown Libr Client 1

35. Example: Library Client 1 Upgraded OS2 OS3 LIBR CLIENT 3 LIBR MGR LIBR CLIENT 2 Server to Server Server to Server V5 New New Paths Upgraded Storage Agents Shared Library

36. Example Upgrade Scenario – Library Client 2 !! This is not the only way to upgrade !! • Install Upgrade utility on OS2 • Shutdown Libr Client 2 • Install New TSM on OS2 • Create Libr Client 2 DB instance • Upgrade Libr Client 2 in place using network method • Start Libr Client 2 • Validate configuration / paths / connectivity • Libr Mgr • Storage Agents • B/A Clients

37. Example: Library Client 2 Upgraded OS2 OS3 LIBR CLIENT 3 LIBR MGR LIBR CLIENT 2 Server to Server Server to Server New New New Paths Upgraded Storage Agents Shared Library

38. Scripting / Reporting • SQL syntax more strictly enforced • Exceptions will be documented • Existing customer scripts and reports • New / changed commands and output • Can directly access DB2 database (read-only mode) • TSM DB2 database is exposed but not documented • Schema is proprietary and may change in the future • Check compatibility of third party reporting tools • Do they work with TSM V6

39. SQL Syntax enforcement examples • The LIKE predicate is not supported for a nested SELECT statement. For example, you receive an error if you use the LIKE predicate as in this statement: • select * from volumeusage where volume_name like (select distinct volume_name from volumeusage where node_name='node1') • Replace such usage with the = operator, as in this statement: • select * from volumeusage where volume_name=(select distinct volume_name from volumeusage where node_name='node1') • Labeled duration cannot be compared in a SELECT statement. For example, the following statement results in an SQL error: • select * from actlog where (current_time-date_time) seconds <= 60 seconds • The following statement is an example of correct usage: • select * from actlog where second(current_time-date_time) <= 60 • From Upgrade Guide, it has more for more examples

40. SQL Example • select node_name,count(*) as Number_of_Objects, sum(file_size) as Bytes_of_WKLD from contents where node_name='61SOURCE18' and filespace_id=1 and file_name like '\WKLD%' group by node_name • Performance: • TSM V5.5.2 5hr 50min 32.53sec • TSM V6.1 beta 27min 29.92sec • DB2 command line 23min 39.42sec • This is an example of a “select” command that creates temporary workspace within DB2

41. Example of how to find Centera “ClipID” through DB2 • db2 "select TSMDB1.AS_SEGMENTS.PVRPOS as ClipID from TSMDB1.AS_SEGMENTS,TSMDB1.AF_SEGMENTS where TSMDB1.AF_SEGMENTS.BFID=‘42803004’ and TSMDB1.AS_SEGMENTS.VOLID=TSMDB1.AF_SEGMENTS.VOLID and TSMDB1.AS_SEGMENTS.START=TSMDB1.AF_SEGMENTS.START" • db2 "select tsmdb1.AF_SEGMENTS.BFID as ObjID from tsmdb1.AF_SEGMENTS,tsmdb1.AS_SEGMENTS where tsmdb1.AS_SEGMENTS.PVRPOS=x'37 ... 542’ and tsmdb1.AS_SEGMENTS.VOLID=tsmdb1.AF_SEGMENTS.VOLID and tsmdb1.AS_SEGMENTS.START=tsmdb1.AF_SEGMENTS.START“

42. Summary • Major change to TSM DB • Resource intensive upgrade process • Time consuming upgrade process • Increase in memory and disk space requirements • SQL syntax considerations • Refer to announcement material (when it becomes available) for specific details on supported environments, software levels, and new function