What are the changes in TSM new DB2 database starting from TSMv6

The Tivoli Storage Manager administrative interfaces work with the database and recovery log. The skills of a database administrator are not required to manage them. However, since starting from TSMv6, the standard database has been replaced with inbuilt DB2 database it is recommended to learn basic DB2 commands & concepts to manage the DB2 related issues if required.

TSM Database changes in TSM from v6

Tivoli Storage Manager version 6.3 is installed with the IBM DB2 database application. Users who are experienced DB2 administrators can choose to perform advanced SQL queries and use DB2 tools to monitor the database. However, do not use DB2 tools to change DB2 configuration settings from those settings that are preset by Tivoli Storage Manager. Do not alter the DB2 environment for Tivoli Storage Manager in other ways, such as with other products. The Tivoli Storage Manager Version 6.3 server was built and tested with the data definition language (DDL) and database configuration that Tivoli Storage Manager deploys.

Making changes to the DDL or database configuration without using Tivoli Storage Manager interfaces can adversely affect performance, damage or destroy the server database, or cause data to become permanently lost. Ensure that you do not do any of the following:
  • Use database tools or interfaces other than those provided or documented by Tivoli Storage Manager to change configuration settings from those that are set by Tivoli Storage Manager at installation.
  • Alter the DB2 environment in other ways. If you use database tools or interfaces other than those provided or documented by Tivoli Storage Manager, you must treat the server database as read-only.
  • Use other interfaces to make changes to the server database.
The database does not store client data; it points to the locations of the client files in the storage pools. The Tivoli Storage Manager database contains information about the Tivoli Storage Manager server. The database also contains information about the data that is managed by the Tivoli Storage Manager server. The database includes information about:
  • Client nodes and administrators
  • Policies and schedules
  • Server settings
  • Locations of client files on server storage
  • Server operations (for example, activity logs and event records)
  • Intermediate results for queries
The maximum size of the Tivoli Storage Manager database is 4 TB.

The database can be distributed across up to 128 directories. It is important that the database is placed on fast, reliable disks that are configured for random access I/O. Locating each directory on a different file system provides the best performance because the data is striped across the directories. Enable read cache for the database, and enable write cache if the disk subsystem supports it.

The database cannot be mirrored through Tivoli Storage Manager, but it can be mirrored by using hardware mirroring, such as Redundant Array of Independent Disks (RAID) 5. 

If the database is unusable, the Tivoli Storage Manager server is unavailable. You must backup the database to ensure that data that is managed by the server can be recovered. Encrypt sensitive data using the Tivoli Storage Manager client or a storage device, unless the storage media is physically secured. Security can be compromised even if data is not recovered. If a database is lost and cannot be recovered, it might be difficult or impossible to recover data that is managed by that server. Fragments of data or complete files might be read from storage pool volumes that are not encrypted. The database manager manages database volumes, and there is no need to format them. 

Advantages of the new DB2 Database Manager

Automatic backups

When the server is started for the first time, a full backup begins automatically. When the server is next started, the database manager automatically backs up the database according to the following values set by Tivoli Storage Manager:
  • The active log space used since the last backup, which triggers a full database backup
  • The active log utilization ratio, which triggers an incremental database backup
Automatic statistics collection

Automatic statistics collection helps to improve database performance by collecting up-to-date table statistics. The database manager determines which statistics need to be updated.

Automatic database reorganization

Reorganization of table data can be initiated by the server, or by DB2®. If server-initiated reorganization is enabled, based on table activity, the server analyzes selected database tables and their indexes to determine when reorganization is required. The database manager runs a reorganization while server operations continue. If reorganization by DB2 is enabled, DB2 controls the reorganization process. Reorganization by DB2 is not recommended.

Also Read: Taking TSM server DB backup when the server is down

Multiple data streams for database backup and restore

Using a single data stream to back up databases of multiple terabytes can take many hours. It can also affect the administrator’s ability to schedule database backups effectively. The time to recover the server by using a single data stream might not be enough to meet disaster recovery objectives for the server. The Tivoli Storage Manager server provides a multiple data stream capability for backups and restores.

SQL queries

The database makes more sophisticated SQL queries on the data possible. To take advantage of these functions, you must use SQL to develop new tools and create SQL statements.

Database audits

Database audits are run automatically, as needed, to ensure consistency. As data is added to the server database, the database manager checks data constraints and data types. Online integrity checks can prevent problems for which offline audits had been needed in earlier releases.

Connecting the server to the database manager with TCP/IP

The default configuration for the Tivoli Storage Manager v6 adn v7 servers is to use interprocess communications (IPC) to communicate with the database manager. With Tivoli Storage Manager V6.3, the server can also connect to the database manager by using TCP/IP.

Using TCP/IP to communicate with DB2® can greatly extend the number of concurrent connections. The TCP/IP connection is part of the default configuration. When the Tivoli Storage Manager V6.3 server is started for the first time, it inspects the current configuration of the DB2 instance. It then makes any necessary changes to ensure that both IPC and TCP/IP can be used to communicate with the database manager. Any changes are made only as needed. For example, if the TCP/IP node exists and has the correct configuration, it is not changed. If the node was cataloged but has an incorrect IP address or port, it is deleted and replaced by a node having the correct configuration.

When cataloging the remote database, the Tivoli Storage Manager server generates a unique alias name based on the name of the local database. By default, a remote database alias of TSMAL001 is created to go with the default database name of TSMDB1.  Tivoli Storage Manager disables the TCP/IP connections if it cannot find an alias in the range TSMAL001-TSMAL999 that is not already in use.

Also Read: Steps to do after successful TSM DB restore

By default, the Tivoli Storage Manager server uses IPC to establish connections for the first two connection pools, with a maximum of 480 connections for each pool. After the first 960 connections are established, the Tivoli Storage Manager server uses TCP/IP for any additional connections.

You can use the DBMTCPPORT server option to specify the port on which the TCP/IP communication driver for the database manager waits for requests for client sessions. The port number must be reserved for use by the database manager.

If Tivoli Storage Manager cannot connect to the database by using TCP/IP, it issues an error message and halts. The administrator must determine the cause of the problem and to correct it before restarting the server. The server verifies that it can connect by using TCP/IP at startup even if it is configured to initially favor IPC connections over TCP/IP connections.

0 Comment to "What are the changes in TSM new DB2 database starting from TSMv6"

Post a Comment