Documente Academic
Documente Profesional
Documente Cultură
Agenda
In this presentation we will discuss TSM 6 Planning and Performance, TSM 6.2 updates, TSM 6.2.2 and what was released in TSM 6.3
Agenda
TSM 6.1
TSM 6.1 GA 3/27/09
Scalability, Availability and Performance Server scalability upgrade TSM DB Data Deduplication
Administration and Reporting Administration Center Updates New out of the box Reporting / Monitoring
Windows platform Enhancements MS Active Directory Item Recovery Exchange Item Level Recovery
N series integration SnapMirror to Tape integration Incremental Backup File Selection enhancement for N series / NetApp Other Enhancements VCB: Full VM for Disaster Recovery MS Windows Longhorn exploitation TSM ACS XIV Support and AIX6.1 Support Instant restore for XIV for windows (for CS) FastBack Configuration wizard added into B/A Client
GA 5/8/09
Automatic threshold migration Windows Server 2008 (64-bit) support. Support for IPv6)
CPU requirements
User ID requirements Upgrade Considerations Examining database and log operations Backing up the database
TSM 6 Deployments Are Growing First TSM 6 GAd March 2009 with significant new code and functionality Early input from technical sales teams, support teams, and customers suggests:
TSM 6 adoption is growing, but slightly less than the 5.5 rate
TSM 6 field reported problems are in line with prior releases Customers are hungry for more information about the new database
whats new how to configure it
CPU requirements
User ID requirements Upgrade Considerations Examining database and log operations Backing up the database
TSM DB
Archive Log
Suggest you start with many smaller directories and make them bigger as necessary
2009 IBM Corporation 9
2011 IBM Corporation
Possible Database Layout DB2 Managed Assume you estimate 200GB for disk space
Disk 1 50GB
Disk 2 50GB
Disk 3 50GB
Disk 4 50GB
LUN 1 200GB
Disk Array
Host
DB2 Usage of Array Managed Storage DB2 has parameter to control parallel I/O
db2set i <instance> db2_parallel_io
You may need to restart the TSM server for this to take effect
The TSM Log Directories Log space is more complicated than with TSM V5
Required Log Directories
Active Log Directory
Contains all currently active transactions
If this directory gets used frequently, then archive log too small
Tune archive log to avoid using failover
Type
Disk Disk Disk Disk Disk
32GB 0 100GB 0 0
32GB 0 100GB 0 0
DB2 DB DB Backup
Extract Total Disk Total Seq
145GB 200GB
80GB 390GB 280GB
145GB 200GB
0 390GB 200GB
145GB 120GB
80GB 277GB 200GB
145GB 120GB
0 277GB 120GB
CPU requirements
User ID requirements Upgrade Considerations Examining database and log operations Backing up the database
CPU requirements
User ID requirements Upgrade Considerations Examining database and log operations Backing up the database
Multi-process Expiration
Trade-off between time and CPU
Active Log
TSM DB
TSM Server (tsmuser, root, or Administrator)
Archive Log
TSM STGPools (disk, tape) Configuration Files dsmserv.opt, trace, devconfig, volhist
24
2011 IBM Corporation
Database Manager
dsmserv
db2sysc
pts/0
db2sysc is the main database manager process db2acd is the DB2 health monitor
CPU requirements
User ID requirements Upgrade Considerations Examining database and log operations Backing up the database
References:
DB Server Upgrade Guide (SC23-9554) Storage Technical Exchange Website:
http://www-01.ibm.com/software/sysmgmt/products/support/supp_tech_exch.html
CPU requirements
User ID requirements Upgrade Considerations Examining database and log operations Backing up the database
How the logs flow Transaction starts and stops are written to active log
Once an active log file is full, it is immediately copied to an archive log directory
If the archive log directory is not writeable, it is copied to the failover archive log If the failover archive log is not writeable, it is not copied
When an active log file has no more active transactions within it, it is eligible for deletion
Cannot be deleted until it is archived
Active
Keeping the logs flowing To keep the active log from filling:
Make sure the active log is large enough to contain active txns
Watch out for slow clients pinning the log In TSM V6, there is much more log activity than in TSM V5 If your active log is too small, it will fill and the server will halt
It may take some time, but if ANY of the log directories becomes full, the server may halt
The reason for the halt will be out of active log space
2009 IBM Corporation 35
2011 IBM Corporation
CPU requirements
User ID requirements Upgrade Considerations Examining database and log operations Backing up the database
Configuring V6 for DB Backup V6 database backup uses the TSM client API
API installed automatically with V6 server
Uses a special nodename $$_TSMDBMGR_$$ for backup
Password MUST be TSMDBMGR This node is hidden and can perform only DB backup and restore
Note: Be careful when canceling sessions. It is possible to cancel the API session doing the DB Backup
V6 database backup and restore require volumehistory and devconfig files If possible, use either instance config or upgrade wizard
Set the password in TSM.PWD or registry entry Sets up dsm.opt, dsm.sys, and DB2 parameters
2009 IBM Corporation 38
2011 IBM Corporation
TSM Server
3 1 Initiate DB Backup 2 Intercept Inbound Session from DB2 3 Stream DB Backup to Sequential DataStream
4
Volhistory