Upgrade Considerations for TSM V6 IBM Advanced Technical Support Randy Larson

Transcription

IBM Advanced Technical Support
Upgrade Considerations for
TSM V6
Randy Larson
[email protected]
© 2009 IBM Corporation
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
Page 2
Topics
 The Basics
 Preparation
 Upgrade Considerations
– Upgrade complicating factors
– Example upgrade
 Scripting Considerations
Page 3
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 !!
Page 4
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
Page 5
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
Page 6
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
Page 7
Upgrade Utility

Upgrade utility is a separate install package
–
Can coexist with existing TSM versions
–
Must use currently supported version of TSM
 Upgrade process:
1. Upgrades existing DB to V5.5.x
2. Extracts from existing V5.5.x database
3. Inserts into DB2 using TSM server (not the utility itself)

Page 8
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
New DB Backup Process

Utilizes existing DB2 to TSM implementation
– Built into DB2, no separate product

Setup (documented in Installation Guide)
1. Install 64bit API (installed with server install)
2. Configure environment variables
3. Update configuration files (AIX example)
•
•
•
Dsm.sys
/home/tsminst1/sqllib/userprofile
tsmdbmgr.opt
4. Set password (must be “TSMDBMGR”)
•
/home/tsminst1/sqllib/adsm/dsmapipw
5. Logoff/Logon and restart TSM to pick up new environment
6. Configure device class (instance owner needs write access)
7. Issue TSM commands:
•
•
Page 9
SET DBRECOVERY devclass
BACKUP DB DEVC=devclass TYPE=full
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
Page 10
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
Page 11
Preparation - Estimating Disk Requirements
Item
Type
Same system
Media
Same system
Network
New system
Media
New system
Network
Active Log
Disk
2GB (Min)
2GB (Min)
2GB (Min)
2GB (Min)
Log Mirror
Disk
Log Size
Log Size
Log Size
Log Size
Archive Log (1)
Disk
Log Size +
Log Size +
Log Size +
Log Size +
V5 DB
Disk
Current DB
Current DB
0
0
V5 Rcvylog
Disk
Current Log
Current Log
0
0
DB2 DB (2)
Disk
DB Util%
+ 50%
DB Util%
+ 50%
DB Util%
+ 50%
DB Util%
+ 50%
DB Backup (2)
Seq Media
DB Util%
DB Util%
DB Util%
DB Util%
Extract(2)
Seq Media
DB Util%
0
DB Util%
0
Total Disk
Disk
Total Seq
Seq Media
Note 1: Archive log is a function of daily activity
Note 2: V6 DB, DBB, and Extract are a function of current DB utilization
Page 12
Preparation – Sample for 100GB database 80% Utilized
Same system
Media
Same system
Network
New system
Media
New system
Network
Disk
2GB
2GB
2GB
2GB
Log Mirror
Disk
0
0
0
0
Archive Log
Disk
80GB
80GB
80GB
80GB
V5 DB
Disk
100GB
100GB
0
0
V5 Rcvylog
Disk
13GB
13GB
0
0
DB2 DB
Disk
145GB
145GB
145GB
145GB
DB Backup
Seq Media
200GB
200GB
120GB
120GB
Extract
Seq Media
80GB
0
80GB
0
Total Disk
Disk
340GB
340GB
227GB
227GB
Total Seq
Seq Media
280GB
200GB
200GB
120GB
Item
Type
Active Log
Page 13
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
Page 14
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
Page 15
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
Page 16
– 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
Upgrade Planning - Options
Extract to Media
Extract to Network

Two step process:
Extract then Insert


Fall back is re-install

Same System 
Duplicate DB space
required
 Duplicate DB space
required

New System
Fall back is re-install
Sequential media
space required

Two step process:
extract then insert

 V5.5.2 server can
restart after extract
completes
 Requires network
bandwidth
 Sequential media
space required
Page 17
One step process:
Extract and Insert
One step process:
Extract and insert
 V5.5.2 server can restart
after extract completes
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
Page 18
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
Page 19
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
 Synchronize database contents if necessary
Page 20
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
 Synchronize database contents if necessary
Page 21
Complicating Factors
 Multiple TSM instances on single OS
 Library Manager configurations
 LANFree configurations
 New host system
 24X7 Availability Requirements
Page 22
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
Page 23
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 ?
Page 24
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 ?
Page 25
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 ?
Page 26
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
Page 27
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
Page 28
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
Page 29
Example: Starting Configuration
OS2
OS1
LIBR CLIENT 1
LIBR MGR
Server to Server
V5
V5
LIBR CLIENT 2
Server to Server
V5
SAN Paths
Storage Agents
Shared Library
Page 30
Example Upgrade Scenario – Library Manager
!! This is not the only way to upgrade !!
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
4. Upgrade Libr Mgr to New TSM in place
 Small DB, should be fairly easy and fast
Page 31
Example: Library Manager Upgraded
OS1
OS2
OS3
LIBR CLIENT 1
LIBR CLIENT 2
LIBR MGR
Server to Server
Server to Server
V5
New
Paths
V5
Upgraded
Storage Agents
Shared Library
Page 32
Example Upgrade Scenario – Library Client 1
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 Client1

Page 33
Rename new Libr Client1 to Libr Client3
Example Upgrade Scenario – Library Client 1 ...
4. Update Connectivity

Add Libr Mgr Paths for Libr Client 3

Update Libr Client 3 connections

Validate configuration / paths / connectivity
5. Define connectivity between Libr Client 1 and Libr
Client 3
6. Update B/A client connectivity

Either update clients or update TSM Server and host OS
7. Export / Import from Libr Client 1 to Libr Client 3
using date/time
8. Shutdown Libr Client 1
Page 34
Example: Library Client 1 Upgraded
OS2
OS3
LIBR CLIENT 3
LIBR MGR
Server to Server
LIBR CLIENT 2
Server to Server
V5
New
New
Paths
Upgraded
Storage Agents
Shared Library
Page 35
Example Upgrade Scenario – Library Client 2
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
Page 36
Example: Library Client 2 Upgraded
OS2
OS3
LIBR CLIENT 3
LIBR MGR
Server to Server
New
LIBR CLIENT 2
Server to Server
New
New
Paths
Upgraded
Storage Agents
Shared Library
Page 37
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
Page 38
SQL Syntax enforcement examples
1. 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')
2. 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
Page 39
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
Page 40
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“
Page 41
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
Page 42

Upgrade Considerations for TSM V6 IBM Advanced Technical Support Randy Larson

Transcription

Similar documents

Stephan Peinkofer

Hardware Support

How to upgrade manually To InteleViewer V 4.3.4

} ERP TRANSFORMATION FOR EFFICIENCY, EFFECTIVENESS AND GROWTH CHANGING MARKET DYNAMICS TRANSFORMATION APPROACH

Business Partner Sessions & Reception 27 October 2014

A3RMT - IBM Joint Brochure - A3 Remote Monitoring Technologies

2015 tsm program

Dianne Fodell Charlotte Informatics Talent Panel

Ponani Gopalakrishnan. Ponani Gopalakrishnan.

IBM loves data!