Ibm tivoli storage resource manager a practical introduction sg246886

Front cover

IBM Tivoli Storage
Resource Manager:
A Practical Introduction
Take control of storage resources in
your enterprise

Receive early alerts of storage
problems

New! ESS reporting and Tivoli
integration

Charlotte Brooks
Michel Baus
Michael Benanti
Ivo Gomilsek
Urs Moser

ibm.com/redbooks

International Technical Support Organization

IBM Tivoli Storage Resource Manager: A Practical
Introduction

August 2003

SG24-6886-01

Note: Before using this information and the product it supports, read the information in “Notices” on
page xxiii.

Second Edition (August 2003)

This edition applies to IBM Tivoli Storage Resource Manager (product number 5698-SRM), IBM Tivoli Storage
Resource Manager for Databases (product number 5698-SRD), IBM Tivoli Storage Resource Manager for
Chargeback (product number 5698-SRC), and IBM Tivoli Storage Resource Manager Express Edition
(5698-SRX)

© Copyright International Business Machines Corporation 2003. All rights reserved.
Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule
Contract with IBM Corp.

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...... ....... ...... . . . . . . . xxv
The team that wrote this redbook. . . . . . . . . . . . . . . . . . . ...... ....... ...... . . . . . . xxvi
Become a published author . . . . . . . . . . . . . . . . . . . . . . . ...... ....... ...... . . . . . . xxvii
Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...... ....... ...... . . . . . .xxviii

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix
October 2003, Second Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix

Part 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 1. Introduction to Storage Resource Management . . . . . . . . . . . . . . . . . . . . . . 3
1.1 What is Storage Resource Management? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1.1 Storage Resource Management, then and now . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2 Storage management issues today. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2.1 Growth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2.2 Storage costs too much, and money is not used efficiently . . . . . . . . . . . . . . . . . . 8
1.2.3 Unmanaged storage costs too much, and the scope is large . . . . . . . . . . . . . . . . 12
1.2.4 Storage management functions defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2.5 Architecture for a suite of Storage Management solutions . . . . . . . . . . . . . . . . . . 15
1.2.6 Standards and Storage Resource Management tools . . . . . . . . . . . . . . . . . . . . . 16
1.3 Objectives of Storage Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 2. Introduction to IBM Tivoli Storage Resource Manager . . . . . . . . . . . . . . . . 23
2.1 IBM Tivoli Storage Resource Manager overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.1.1 Business purpose of Tivoli Storage Resource Manager . . . . . . . . . . . . . . . . . . . . 24
2.1.2 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.1.3 IBM Tivoli Storage Resource Manager products . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.1.4 Components of IBM Tivoli Storage Resource Manager . . . . . . . . . . . . . . . . . . . . 26
2.1.5 Supported platforms for IBM Tivoli Storage Resource Manager. . . . . . . . . . . . . . 28
2.1.6 Security considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.2 Enhancements to Tivoli Storage Resource Manager V 1.2 . . . . . . . . . . . . . . . . . . . . . 29
2.2.1 Automated filesystem extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.2.2 Enterprise Storage Server (ESS) integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.2.3 TEC integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.2.4 Cloudscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.2.5 UDB/DB2 support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.3 Justification for IBM Tivoli Storage Resource Manager . . . . . . . . . . . . . . . . . . . . . . . . 30
2.3.1 Improving storage return on investment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.4 Functions of IBM Tivoli Storage Resource Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.4.1 Basic menu displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.4.2 Discover and monitor Agents, disks, filesystems, and databases . . . . . . . . . . . . 35
2.4.3 Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.4.4 Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

© Copyright IBM Corp. 2003. All rights reserved. iii

2.4.5 Chargeback: Charging for storage usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
2.5 Chapter summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Part 2. Design considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Chapter 3. Deployment architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.1 IBM Tivoli Storage Resource Manager architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.2 IBM Tivoli Storage Resource Manager Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.2.1 Discovery of unmanaged Windows systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
3.2.2 Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.3 IBM Tivoli Storage Resource Manager Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.4 Deployment considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.4.1 Repository database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.4.2 CIM/OM server placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.4.3 NAS Agent placement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.4.4 Novell NetWare Agent placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.5 Deployment scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.5.1 Standalone Server installation with local database. . . . . . . . . . . . . . . . . . . . . . . . 59
3.5.2 Standalone Server installation with remote database . . . . . . . . . . . . . . . . . . . . . . 59
3.5.3 Standby Server installation for HA using remote database. . . . . . . . . . . . . . . . . . 60
3.5.4 Windows cluster install of IBM Tivoli Storage Resource Manager Server . . . . . . 61
3.5.5 AIX cluster installation of IBM Tivoli Storage Resource Manager Server . . . . . . . 62

Part 3. Installation and basic operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 4. IBM Tivoli Storage Resource Manager installation . . . . . . . . . . . . . . . . . . . 67
4.1 Supported operating system platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.2 Supported databases for repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.3 Tivoli Storage Resource Manager Server install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.3.1 Lab environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
4.3.2 Database creation for repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
4.3.3 Installation of the Server code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.3.4 Microsoft SQL-Server as repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4.3.5 Installing Cloudscape as a test database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4.3.6 Configuration for Web access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.3.7 Installation of the GUI code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4.3.8 Installing the Server code on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.4 Installing the Agent code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.5 Applying maintenance to Tivoli Storage Resource Manager . . . . . . . . . . . . . . . . . . . . 93
4.5.1 Planned upgrade installation for Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4.6 Basic administrative tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.6.1 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.6.2 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4.6.3 Administration: Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4.6.4 Administrative Services: Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
4.6.5 Administrative Services: Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
4.6.6 Administrative Services: Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
4.7 Microsoft Cluster installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
4.7.1 Microsoft Cluster initial setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
4.7.2 Adding shared disk resource for DB2 instance and SRM installation . . . . . . . . . 133
4.7.3 Installation of DB2 database on both nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
4.7.4 Setting up a clustered instance in DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
4.7.5 Installing IBM Tivoli Storage Resource Manager Server on both nodes. . . . . . . 135
4.7.6 Copying the repository database to the clustered instance . . . . . . . . . . . . . . . . 137

iv IBM Tivoli Storage Resource Manager: A Practical Introduction

4.7.7 Editing the Server config file to reflect the database change . . . . . . . . . . . . . . . 138
4.7.8 Creating clustered resources for the Server and Agent . . . . . . . . . . . . . . . . . . . 138
4.8 Manager HA install using remote Oracle database. . . . . . . . . . . . . . . . . . . . . . . . . . . 142
4.8.1 Testing the standby HA installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
4.9 CIM/OM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
4.9.1 What is CIM/OM? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
4.9.2 CIM/OM Server installation for ESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
4.9.3 CIM/OM configuration in IBM Tivoli Storage Resource Manager . . . . . . . . . . . . 153

Chapter 5. Operations: Policy, Quotas, and Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
5.1 OS Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
5.1.1 Navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
5.1.2 Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
5.1.3 Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5.1.4 Pings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
5.1.5 Probes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
5.1.6 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
5.1.7 Scans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
5.2 OS Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
5.2.1 Alerting navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
5.2.2 Computer Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
5.2.3 Filesystem Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
5.2.4 Directory Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
5.2.5 Alert logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
5.3 Policy management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
5.3.1 Filesystem extension and LUN provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
5.3.2 Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
5.3.3 Network Appliance Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
5.3.4 Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
5.3.5 Scheduled actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
5.4 Database monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
5.4.1 Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
5.4.2 Probes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
5.4.3 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
5.4.4 Scans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
5.5 Database Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
5.5.1 Instance Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
5.5.2 Database-Tablespace Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
5.5.3 Table Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
5.5.4 Alert log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
5.6 Databases policy management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
5.6.1 Network Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
5.6.2 Instance Quota . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
5.6.3 Database Quota . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
5.7 Database administration samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
5.7.1 Database up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
5.7.2 Database utilization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
5.7.3 Need for reorganization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Part 4. Customizing and advanced operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Chapter 6. Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
6.1 Tivoli Storage Resource Manager reporting capabilities. . . . . . . . . . . . . . . . . . . . . . . 248
6.1.1 Major reporting categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Contents v

6.2 Using the standard reporting functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
6.2.1 Asset Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
6.2.2 Storage Subsystems Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
6.2.3 Availability Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
6.2.4 Capacity Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
6.2.5 Usage Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
6.2.6 Usage Violation Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
6.2.7 Backup Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
6.3 Tivoli Storage Resource Manager ESS Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
6.3.1 ESS Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
6.4 IBM Tivoli Storage Resource Manager top 10 reports . . . . . . . . . . . . . . . . . . . . . . . . 316
6.4.1 ESS used and free storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
6.4.2 ESS attached hosts report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
6.4.3 Computer Uptime reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
6.4.4 Growth in storage used and number of files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
6.4.5 Incremental backup trends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
6.4.6 Database reports against DBMS size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
6.4.7 Database instance storage report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
6.4.8 Database reports size by instance and by computer . . . . . . . . . . . . . . . . . . . . . 329
6.4.9 Locate the LUN on which a database is allocated . . . . . . . . . . . . . . . . . . . . . . . 331
6.4.10 Finding important files on your systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
6.5 Creating customized reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
6.5.1 System Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
6.5.2 Reports owned by a specific username . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
6.5.3 Batch Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
6.6 Setting up a schedule for daily reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
6.7 Setting up a reports Web site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
6.8 Charging for storage usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

Chapter 7. Protecting and maintaining Tivoli Storage Resource Manager . . . . . . . . 369
7.1 IBM Tivoli Storage Resource Manager environment. . . . . . . . . . . . . . . . . . . . . . . . . . 370
7.1.1 IBM Tivoli Storage Resource Manager Server . . . . . . . . . . . . . . . . . . . . . . . . . . 370
7.1.2 Tivoli Storage Resource Manager Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
7.2 Integration with IBM Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
7.2.1 IBM Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
7.2.2 Setup for backing up Tivoli Storage Resource Manager. . . . . . . . . . . . . . . . . . . 372
7.2.3 Tivoli Storage Manager Server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
7.2.4 Client configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
7.2.5 Additional considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
7.3 Backup procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
7.3.1 Agent files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
7.3.2 Server files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
7.3.3 IBM Tivoli Storage Resource Manager database . . . . . . . . . . . . . . . . . . . . . . . . 382
7.4 Restore procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
7.4.1 Restore Agent files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
7.4.2 IBM Tivoli Storage Resource Manager Server files . . . . . . . . . . . . . . . . . . . . . . 390
7.4.3 Tivoli Storage Resource Manager database. . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
7.5 Disaster Recovery procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
7.5.1 Windows 2000 restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
7.5.2 ITSRMDB database restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
7.6 Database maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
7.7 IBM Tivoli Storage Resource Manager with SQL-Server . . . . . . . . . . . . . . . . . . . . . . 404
7.7.1 Using Oracle for the IBM Tivoli Storage Resource Manager database . . . . . . . 408

vi IBM Tivoli Storage Resource Manager: A Practical Introduction

Part 5. Tivoli Systems Management integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409

Chapter 8. Integration with Tivoli Enterprise Console. . . . . . . . . . . . . . . . . . . . . . . . . 411
8.1 Introduction to Tivoli Enterprise Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
8.2 Lab environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
8.3 Configuring the Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
8.4 Configuring TEC Event Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
8.5 Event format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
8.6 Tivoli Storage Resource Manager event forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . 427

Chapter 9. Integration with Tivoli Enterprise Data Warehouse . . . . . . . . . . . . . . . . . . 431
9.1 Introduction to Tivoli Enterprise Data Warehouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
9.2 Tivoli Storage Resource Manager Warehouse Pack . . . . . . . . . . . . . . . . . . . . . . . . . 433
9.3 Tivoli GUID and Data Warehouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
9.4 Configuring TEDW: Importing Warehouse Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
9.4.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
9.4.2 Installing the Warehouse Enablement Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
9.4.3 Register the Tivoli Storage Resource Manager database with ODBC . . . . . . . . 439
9.4.4 Configuring Tivoli Enterprise Data Warehouse . . . . . . . . . . . . . . . . . . . . . . . . . . 444
9.4.5 Configure ETLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
9.4.6 Verifying data in DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455

Chapter 10. Integration with Tivoli Configuration Manager . . . . . . . . . . . . . . . . . . . . 457
10.1 Introduction to IBM Tivoli Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
10.2 Inventory - determine who has got which version . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
10.2.1 Create an inventory profile in Tivoli Framework . . . . . . . . . . . . . . . . . . . . . . . . 459
10.3 Software distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
10.3.1 Build software package with Software Package Editor . . . . . . . . . . . . . . . . . . . 470
10.3.2 Create software distribution profile in Tivoli Framework . . . . . . . . . . . . . . . . . . 478

Chapter 11. Integration with Tivoli Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
11.1 Introduction to IBM Tivoli Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
11.2 Tivoli Monitoring with Tivoli Storage Resource Manager . . . . . . . . . . . . . . . . . . . . . 486
11.3 Daemons to monitor and restart actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487

Part 6. Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495

Appendix A. Example scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Tivoli Storage Resource Manager for Databases scripts . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Backup and restore scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500

Appendix B. Additional material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
Locating the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
Using the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
System requirements for downloading the Web material . . . . . . . . . . . . . . . . . . . . . . . 503
How to use the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504

Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . ...... ....... ...... ...... 507
Other resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...... ....... ...... ...... 507
Referenced Web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . ...... ....... ...... ...... 507
How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . ...... ....... ...... ...... 508
IBM Redbooks collections. . . . . . . . . . . . . . . . . . . . . . ...... ....... ...... ...... 508

Contents vii

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509

viii IBM Tivoli Storage Resource Manager: A Practical Introduction

Figures

1-1 Storage Resource Management definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1-2 Storage management issues today . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1-3 Infrastructure growth issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1-4 SRM helps you recapture dollars already spent on storage . . . . . . . . . . . . . . . . . . . 10
1-5 Predicted savings from managed storage versus unmanaged storage. . . . . . . . . . . 11
1-6 The need for storage management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1-7 Scope of the problem - total storage, total number of filesystems . . . . . . . . . . . . . . . 13
1-8 Number and cost of storage administrators needed . . . . . . . . . . . . . . . . . . . . . . . . . 14
1-9 Storage Management disciplines - architecture for a suite of solutions. . . . . . . . . . . 16
1-10 Storage standards organizations and their standards . . . . . . . . . . . . . . . . . . . . . . . . 17
1-11 SMIS/CIM/WBEM management model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1-12 SMI Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1-13 CIM Agent & CIM Object Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1-14 Objectives of Storage Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2-1 Tivoli Storage Resource Manager architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2-2 IBM Tivoli Storage Resource Manager products . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2-3 Components of Tivoli Storage Resource Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2-4 Tivoli Storage Resource Manager functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2-5 Agent summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2-6 Tivoli Storage Resource Manager - dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2-7 Availability Report - Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2-8 Asset Report of discovered disks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2-9 Asset Report of database tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2-10 Summary View - by filesystem, disk space used and disk space free. . . . . . . . . . . . 38
2-11 Asset Report - BANDA assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2-12 Historical report of filesystem utilization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2-13 SRM Reports on the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2-14 Alert Log and details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
2-15 Business benefits of Tivoli Storage Resource Manager . . . . . . . . . . . . . . . . . . . . . . 44
3-1 IBM Tivoli Storage Resource Manager architecture . . . . . . . . . . . . . . . . . . . . . . . . . 48
3-2 IBM Tivoli Storage Resource Manager Server roles . . . . . . . . . . . . . . . . . . . . . . . . . 49
3-3 Unmanaged systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3-4 SRM Agent tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3-5 CIM/OM server placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3-6 Setup of SRM Agent for NAS devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3-7 After setting 311 for NAS discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3-8 Setup of SRM Agent for NetWare systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3-9 Installation with local database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3-10 Installation with remote database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3-11 HA setup with remote database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3-12 Windows 2000 cluster setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3-13 AIX cluster setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4-1 Supported operating system platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4-2 Supported databases for repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4-3 Installation of Tivoli Storage Resource Manager Server . . . . . . . . . . . . . . . . . . . . . . 70
4-4 Initial installation screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4-5 Selecting product to install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4-6 Enter licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

© Copyright IBM Corp. 2003. All rights reserved. ix

4-7 Selecting the database engine for the repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4-8 Creating account for running the service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4-9 Selecting the database for the repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4-10 Repository parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4-11 Server setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
4-12 NAS settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4-13 Space requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4-14 Before copying files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4-15 User create for UDB account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4-16 Installation completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4-17 Selecting Microsoft SQL Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4-18 Microsoft SQL-Server parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4-19 Repository parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4-20 Cloudscape selection to install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4-21 Cloudscape warning for production use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4-22 Creating virtual Web directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4-23 Defining the alias name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4-24 Defining the directory for Web access files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4-25 Access permissions for virtual directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4-26 IBM Tivoli Storage Resource Manager main Web window . . . . . . . . . . . . . . . . . . . . 84
4-27 Granting permission for the applet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4-28 Main administration GUI screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4-29 Opening properties for the tsrm Web directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4-30 Tsrm properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4-31 Document properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4-32 Selecting GUI to install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4-33 Server name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4-34 Size and directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4-35 Agent install selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4-36 Agent parameters setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4-37 Space requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4-38 Novell logon ID creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4-39 Selecting to apply the maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4-40 Product maintenance selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4-41 DB2 admin user ID and password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4-42 Maintenance finished . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4-43 Select Agent to upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4-44 Schedule agent upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
4-45 Force upgrade on Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
4-46 Alert selection for failed Agent upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4-47 Server login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4-48 Main panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
4-49 Menus in GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4-50 Tool Bar functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
4-51 Right-click menu on Services tree components. . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
4-52 Agent General view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
4-53 Agent Details view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
4-54 Agent Jobs view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
4-55 Right-click menu on Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
4-56 Agent log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
4-57 License Keys editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
4-58 Adding new license key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
4-59 Licenses for IBM Tivoli SRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

x IBM Tivoli Storage Resource Manager: A Practical Introduction

4-60 Licensing Novell NetWare Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
4-61 Licenses for Tivoli Storage Resource Manager for NAS . . . . . . . . . . . . . . . . . . . . . 110
4-62 NAS devices logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
4-63 Login definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
4-64 Licenses for Tivoli Storage Resource Manager for Databases . . . . . . . . . . . . . . . . 112
4-65 RDBMS Logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
4-66 Defining RDBMS Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
4-67 Alert Disposition screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
4-68 Log File Retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
4-69 Filters for Quota Email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
4-70 Agent selection for NAS and NDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
4-71 Defining the NAS Agent for Scan/Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
4-72 Defining the Novell NetWare Agent for Scan/Probe . . . . . . . . . . . . . . . . . . . . . . . . 118
4-73 History Aggregator definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
4-74 NetWare Tree Login Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
4-75 Novell Tree Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
4-76 History retention: Tivoli Storage Resource Manager . . . . . . . . . . . . . . . . . . . . . . . . 120
4-77 Removed Resource Retention: Tivoli Storage Resource Manager . . . . . . . . . . . . . 121
4-78 History retention: Tivoli Storage Resource Manager for Databases . . . . . . . . . . . . 122
4-79 Removed Resource Retention: Tivoli Storage Resource Manager for Databases . 123
4-80 Cluster installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
4-81 Cluster Wizard Welcome panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
4-82 HCL requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
4-83 Node selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
4-84 Cluster name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
4-85 Cluster user ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
4-86 Shared disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
4-87 Quorum disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
4-88 Network setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
4-89 Private network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
4-90 Public network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
4-91 Network priority for internal cluster communication . . . . . . . . . . . . . . . . . . . . . . . . . 130
4-92 Cluster IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
4-93 Joining the cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
4-94 Joining cluster name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
4-95 Account for running the service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
4-96 Running cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
4-97 DB2 clustered instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
4-98 Database on first node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
4-99 Service mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
4-100 Database on second node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
4-101 Password change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
4-102 Resource dependences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
4-103 Server service name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
4-104 Agent service name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
4-105 Cluster view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
4-106 Starting Oracle Database Configuration Assistant. . . . . . . . . . . . . . . . . . . . . . . . . . 142
4-107 Selecting the database name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
4-108 Database connection information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
4-109 Database information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
4-110 Setting services to manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
4-111 CIM/OM for ESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
4-112 CIM/OM server supported platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Figures xi

4-113 ESS CIM/OM startup screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
4-114 Installation directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
4-115 Installation size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
4-116 Welcome screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
4-117 Current version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
4-118 Install size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
4-119 Installation finished . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
4-120 CIM/OM Logins in navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
4-121 Defining CIM/OM login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
4-122 Running discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
4-123 Finding CIM/OM discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
4-124 Discovery job output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
4-125 Storage Subsystem Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
5-1 Tivoli Storage Resource Manager Monitoring features . . . . . . . . . . . . . . . . . . . . . . 160
5-2 OS Monitoring tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
5-3 New Scan job creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
5-4 OS Monitoring - Jobs list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
5-5 Tivoli Storage Resource Manager Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
5-6 Computer Group definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
5-7 Save a new Computer Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
5-8 Final Computers Group definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
5-9 Filesystem Group definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
5-10 Directory group definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
5-11 Computers by directory definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
5-12 Directories by computer configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
5-13 Final Directories Group definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
5-14 List of available users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
5-15 List of available user after Scan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5-16 Discovery process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5-17 Discovery When to Run options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
5-18 Discovery job options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
5-19 Ping process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
5-20 Ping job configuration - Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
5-21 Ping job configuration - When to Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
5-22 Ping job configuration - Alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
5-23 Ping failed popup for GALLIUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
5-24 Mail message for GALLIUM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
5-25 Probe process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
5-26 New Probe configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
5-27 Probe alert - mail configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
5-28 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
5-29 New Profile - Statistics tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
5-30 New Profile - File filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
5-31 New Condition Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
5-32 New Profile - Conditions Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
5-33 New Profile - New condition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
5-34 New Profile - Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
5-35 Profile save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
5-36 Scans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
5-37 New Scan configuration - Filesystem tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
5-38 New Scan configuration - Profiles tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
5-39 New Scan - Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
5-40 Alerts mechanisms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

xii IBM Tivoli Storage Resource Manager: A Practical Introduction

5-41 Alert - SNMP trap sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
5-42 Alert - Logged alerts sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
5-43 Alert - Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
5-44 Alerts - Windows Event viewer sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
5-45 Alerts - Mail sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
5-46 OS Alerting tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
5-47 Filesystem alert creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
5-48 Computer alerts - Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
5-49 Computer alerts - RAM decreased script parameters . . . . . . . . . . . . . . . . . . . . . . . 196
5-50 Computer alerts - Disk not found script parameters . . . . . . . . . . . . . . . . . . . . . . . . 196
5-51 Computer alerts - Computers tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
5-52 Filesystem Alerts - Alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
5-53 Filesystem alert - Freespace default mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
5-54 Alerts log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
5-55 Detailed Alert information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
5-56 Filesystem Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
5-57 Filesystem tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
5-58 Extension tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
5-59 LUN provisioning tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
5-60 When to Enforce Policy tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
5-61 Alert tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
5-62 Save filesystem changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
5-63 Selected filesystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
5-64 Extension parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
5-65 Alert definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
5-66 Rule for /opt extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
5-67 Successful extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
5-68 Extension log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
5-69 /essfs1 filesystem expansion definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
5-70 Extension parameters for /essfs1 FS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
5-71 Provisioning parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
5-72 Filesystem extension on /essfs1 filesystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
5-73 LUN provisioning for /essfs1 filesystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
5-74 ESS LUNs for filesystem expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
5-75 Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
5-76 User Network Quotas - Users tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
5-77 Profile with user summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
5-78 User Network Quotas - Filesystem tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
5-79 User Network Quotas - Alert tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
5-80 Computer Quota - Alerts log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
5-81 Filesystem Quota - Alerts log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
5-82 Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
5-83 Constraint - File Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
5-84 Constraint - Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
5-85 Constraints - Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
5-86 Constraints - File filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
5-87 Constraints - File filter changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
5-88 Constraints - Alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
5-89 Constraints - Script parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
5-90 Scheduled actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
5-91 Scheduled action - Script options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
5-92 Databases - Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
5-93 Database group definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Figures xiii

5-94 Database Probe definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
5-95 Database profile definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
5-96 Database Scan definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
5-97 Instance Alert definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
5-98 Instance Alert output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
5-99 Database alert definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
5-100 Database Quota - Users tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
6-1 Reporting capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
6-2 IBM Tivoli Storage Resource Manager main screen showing reporting options . . . 249
6-3 Tivoli Storage Resource Manager standard reporting . . . . . . . . . . . . . . . . . . . . . . . 251
6-4 Tivoli Storage Resource Manager Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . 252
6-5 Reporting - Asset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
6-6 Reporting - Asset - By Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
6-7 Report - GALLIUM assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
6-8 Reporting - Assets - System-wide view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
6-9 Monitored directories report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
6-10 Northwind database asset details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
6-11 System-wide view of database assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
6-12 Create a new database table group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
6-13 Add SQL Server tables to table group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
6-14 Add Oracle tables to table group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
6-15 Tables added to table group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
6-16 Table group added to scan job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
6-17 Displaying Scan job logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
6-18 Tables by total size asset report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
6-19 Reports - Availability - Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
6-20 Reports - Availability - Computer Uptime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
6-21 Disk capacity report selection window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
6-22 Capacity report - A23BLTZM Disk 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
6-23 Database Capacity report by Computer Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
6-24 Largest tables by RDBMS type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
6-25 Monitored tables by RDBMS type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
6-26 Create a Constraint - Filesystems tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
6-27 Create a Constraint - file types tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
6-28 Edit a Constraint file filter - before change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
6-29 Edit a Constraint file filter - after change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
6-30 Create a Constraint - Options tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
6-31 Create a Constraint - Alert tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
6-32 Create a Constraint - save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
6-33 Constraint violation report selection screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
6-34 Constraint violations by computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
6-35 Graph of capacity used by Constraint violating files . . . . . . . . . . . . . . . . . . . . . . . . 275
6-36 Alert log showing Constraint violations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
6-37 Create Quota - Users tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
6-38 Create Quota - Computers tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
6-39 Create Quota - When to Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
6-40 Create Quota - Alert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
6-41 Create Quota - save. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
6-42 Run new Quota job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
6-43 Alert Log - Quota violations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
6-44 Alert Log - Quota violation detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
6-45 Quota violations by computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
6-46 Quota violation graphical breakdown by file size . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

xiv IBM Tivoli Storage Resource Manager: A Practical Introduction

6-47 Create database Quota - Users tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
6-48 Create database Quota - Instances tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
6-49 Create a database Quota - When to Run tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
6-50 Create a database Quota - Alert tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
6-51 Create a database Quota - Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
6-52 Run the database Quota . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
6-53 DB Quota violation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
6-54 Database Quota violation report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
6-55 Backup Reporting options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
6-56 Files most at risk report - selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
6-57 Modified Files not backed up selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
6-58 Modified Files not backed up chart overall view . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
6-59 Files need backed up chart in detail view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
6-60 Files not backed up bar chart detail view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
6-61 Backup storage requirements per filesystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
6-62 Backup storage requirement per computer and per filesystem . . . . . . . . . . . . . . . . 292
6-63 Incremental reporting per Node and Filesystem based on files. . . . . . . . . . . . . . . . 293
6-64 Incremental Range Size select By Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
6-65 Incremental Range Sizes Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
6-66 Tivoli Storage Manager preference settings for archive attribute . . . . . . . . . . . . . . 296
6-67 ESS Reporting capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
6-68 ESS reporting lab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
6-69 Creating ESS probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
6-70 ESS - When to probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
6-71 ESS - Alert tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
6-72 ESS - probe job status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
6-73 Probe job log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
6-74 Asset by storage subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
6-75 ESS disk group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
6-76 Disks in volume spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
6-77 Disk and LUN association with volume space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
6-78 Hot spare LUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
6-79 ESS all disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
6-80 ESS all LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
6-81 By Computer - Relate Computer to . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
6-82 By Computer - storage subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
6-83 By Computer - LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
6-84 By Computer - disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
6-85 By filesystem/logical volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
6-86 By filesystem/logical volumes - storage subsystem. . . . . . . . . . . . . . . . . . . . . . . . . 310
6-87 By filesystem/logical volume - LUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
6-88 By filesystem/logical volume - Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
6-89 By Storage Subsytems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
6-90 By Storage subsystem - Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
6-91 By storage subsystem - filesystem/logical volume. . . . . . . . . . . . . . . . . . . . . . . . . . 313
6-92 By LUNs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
6-93 By LUN - computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
6-94 By LUNS - filesystem/logical volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
6-95 Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
6-96 Disks - computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
6-97 Disks - filesystem/logical volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
6-98 ESS relation to computer selected by disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
6-99 Report for Filesystem/Logical Volumes Part 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

Figures xv

6-100 Report for Filesystem/Logical Volumes Part 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
6-101 Computer view to the filesystem with capacity and free space . . . . . . . . . . . . . . . . 318
6-102 ESS selection per computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
6-103 ESS connections to computer report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
6-104 Computer Uptime report selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
6-105 Computer Uptime report part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
6-106 Computer Uptime report graphical combined (stacked bar) . . . . . . . . . . . . . . . . . . 321
6-107 Computer Uptime report graphical (bar chart) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
6-108 Generate Full Backup Size report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
6-109 Select History chart for File count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
6-110 History chart space used by a computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
6-111 History chart: File count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
6-112 Incremental Range selection based on filespace . . . . . . . . . . . . . . . . . . . . . . . . . . 324
6-113 Summary of all filespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
6-114 Selection for Filesystem and computer to generate a graphic. . . . . . . . . . . . . . . . . 325
6-115 Bar chart for Incremental Range Size by Filesystem. . . . . . . . . . . . . . . . . . . . . . . . 326
6-116 Pie chart selected with number of files which have modified. . . . . . . . . . . . . . . . . . 326
6-117 Total Instance storage used network wide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
6-118 DBMS drill down to the computer reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
6-119 DBMS drill down to the computer result. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
6-120 DBMS report Total Instance Storage by Instance . . . . . . . . . . . . . . . . . . . . . . . . . . 329
6-121 Instance report RDBMS overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
6-122 Instance running on computer TONGA first part . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
6-123 Instance running on computer TONGA second part . . . . . . . . . . . . . . . . . . . . . . . . 330
6-124 LUN report selection for an Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
6-125 Database select File and Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
6-126 Report DB2 File in a Pie Chart for DB2 File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
6-127 LUN information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
6-128 Create Profile for own File search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
6-129 Create new Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
6-130 Create Condition add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
6-131 Saved Condition in new Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
6-132 Listed Profiles containing Search for Tivoli Storage Manager Option File. . . . . . . . 337
6-133 Add Profile to Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
6-134 Add Profiles to Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
6-135 Report with number of found Tivoli Storage Manager Option Files . . . . . . . . . . . . . 339
6-136 Create Orphaned File search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
6-137 Update the Orphaned selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
6-138 Update the selection with own data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
6-139 Enter the file search criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
6-140 File Filter selection reconfirm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
6-141 bind the Orphan search into Profiles to apply to Filesystems column . . . . . . . . . . . 342
6-142 Scan log check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
6-143 Summary report of all Tivoli Storage Manager option files . . . . . . . . . . . . . . . . . . . 343
6-144 File selection for computer BONNIE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
6-145 Report for Tivoli Storage Manager Option file searched . . . . . . . . . . . . . . . . . . . . . 344
6-146 File detail information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
6-147 My Reports - System Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
6-148 My Reports - Storage Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
6-149 Available System Reports for databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
6-150 Create My Storage Capacity report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
6-151 My Storage Report saved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
6-152 Monitored Tables by RDBMS Types customized report . . . . . . . . . . . . . . . . . . . . . 351

xvi IBM Tivoli Storage Resource Manager: A Practical Introduction

6-153 Create a Batch Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
6-154 Create a Batch Report - report selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
6-155 Create a Batch Report - selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
6-156 Create a Batch Report - options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
6-157 Create a Batch Report - when to report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
6-158 Create a Batch Report - saving the report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
6-159 Create a database Batch Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
6-160 Create a database Batch Report - Report tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
6-161 Create a database Batch Report - Options tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
6-162 Create a database Batch Report - When to Report tab . . . . . . . . . . . . . . . . . . . . . . 359
6-163 Create a database Batch Report - save definition . . . . . . . . . . . . . . . . . . . . . . . . . . 359
6-164 Monitored Tables by RDBMS Type batch report output . . . . . . . . . . . . . . . . . . . . . 360
6-165 Batch Reports listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
6-166 MS Word created Web page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
6-167 Setting up a Virtual Directory within IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
6-168 Reports available from a Web browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
6-169 Chargeback parameter definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
6-170 Create the Chargeback Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
7-1 Tivoli Storage Resource Manager components. . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
7-2 Tivoli Storage Resource Manager integration with Tivoli Storage Manager . . . . . . 371
7-3 Backup environment tor Tivoli Storage Resource Manager . . . . . . . . . . . . . . . . . . 373
7-4 Procedures used to backup Tivoli Storage Resource Manager. . . . . . . . . . . . . . . . 379
7-5 Tivoli Storage Resource Manager restore procedures . . . . . . . . . . . . . . . . . . . . . . 387
7-6 Agent is connected to the server after restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
7-7 IBM Tivoli Storage Manager restore interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
7-8 Restore completed successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
7-9 Agents successfully reconnected after restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
7-10 Server running again after database restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
7-11 Tivoli Storage Resource Manager Server Disaster Recovery procedures . . . . . . . 396
7-12 Full system restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
7-13 Full system restore result. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
7-14 System Objects restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
7-15 System Objects restore results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
7-16 IBM Tivoli SRM interface after DR restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
7-17 DB2 Database maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
7-18 SQL-Server database backup start using the GUI. . . . . . . . . . . . . . . . . . . . . . . . . . 405
7-19 SQL-Server database backup end using the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . 405
7-20 SQL Server database restore started using the GUI . . . . . . . . . . . . . . . . . . . . . . . . 406
7-21 SQL Server database restore finished using the GUI . . . . . . . . . . . . . . . . . . . . . . . 407
8-1 TEC architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
8-2 Tivoli Lab environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
8-3 Active Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
8-4 Import Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
8-5 Import Class Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
8-6 Compile Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
8-7 Load Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
8-8 Restart TEC Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
8-9 TEC Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
8-10 TEC Console Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
8-11 Create Event Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
8-12 Create Filter in Event Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
8-13 Event Group Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
8-14 Add Constraint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421

Figures xvii

8-15 Event Group Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
8-16 Assign Event Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
8-17 Assigned Event Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
8-18 Configured Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
8-19 TEC Console main screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
8-20 TEC console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
8-21 General tab of event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
8-22 Event attribute list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
8-23 Setting the TEC server properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
8-24 Enabling TEC events for the default scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
8-25 Enable TEC events for discovery of new computers . . . . . . . . . . . . . . . . . . . . . . . . 430
9-1 Tivoli Data Warehouse data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
9-2 Warehouse pack structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
9-3 Application installation only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
9-4 Verify the fully qualified hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
9-5 Enter username and password of the data warehouse database . . . . . . . . . . . . . . 437
9-6 Enter path to the Warehouse Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
9-7 Additional products installation dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
9-8 Start actual installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
9-9 Successfully finished installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
9-10 DB2 Client Configuration Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
9-11 Choose how to make a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
9-12 Choose communication protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
9-13 Enter hostname and DB2 instance port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
9-14 Name the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
9-15 Register database with ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
9-16 Test connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
9-17 Enter UID and password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
9-18 Test successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
9-19 DB2 Control Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
9-20 Data Warehouse Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
9-21 Warehouse Sources for IBM Tivoli Storage Resource Manager . . . . . . . . . . . . . . . 446
9-22 Data Source Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
9-23 BTM_ITSRM_Source Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
9-24 Target Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
9-25 Enter password for DB2 CDW target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
9-26 Subject Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
9-27 Open the Work in Progress window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
9-28 Run New Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
9-29 Selecting the steps to run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
9-30 Work in Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
9-31 Schedule Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
9-32 Schedule a Process times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
9-33 Task Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
9-34 E-mail alert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
9-35 Change mode to production. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
9-36 Scheduled process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
9-37 Run process manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
9-38 Manually run steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
9-39 COMP table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
9-40 CDW entries from Warehouse Pack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
10-1 Tivoli Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
10-2 Policy Region tonga-region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460

xviii IBM Tivoli Storage Resource Manager: A Practical Introduction

10-3 Managed Resources for Inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
10-4 Policy Region Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
10-5 Profile Manager Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
10-6 Inventory Profile Global Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
10-7 Inventory Profile PC Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
10-8 Inventory Profile UNIX Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
10-9 Distribute Inventory Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
10-10 Distribute Inventory Profile dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
10-11 Distribution Status Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
10-12 Create Query Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
10-13 Edit Inventory Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
10-14 Output for IBM Tivoli Storage Resource Manager Query . . . . . . . . . . . . . . . . . . . . 469
10-15 Output for IBM Query. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
10-16 Software Package Editor with new package ITSRM-Agent . . . . . . . . . . . . . . . . . . . 470
10-17 Properties dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
10-18 Agent installation directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
10-19 Add an execute program action to the package . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
10-20 Install dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
10-21 Advanced tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
10-22 Remove dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
10-23 Advanced properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
10-24 Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
10-25 Add Directory dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
10-26 Descend Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
10-27 Ready-to-build software package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
10-28 Policy Region with Profile Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
10-29 Create Software Package Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
10-30 Profile Manager with Profiles and Subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
10-31 Import Software Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
10-32 Import and build a software package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
10-33 Install a software package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
10-34 Install Software Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
10-35 Remove a Software Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
11-1 IBM Tivoli Monitoring architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
11-2 Policy Region tonga-region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
11-3 Profile Manager PM_DM_ITSANM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
11-4 Create Monitoring Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
11-5 Add Parametric Services Model to Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
11-6 Edit Resource Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
11-7 Parameters of Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
11-8 Indications and actions of resource models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
11-9 TEC forwarding of events from Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
11-10 Profilemanager for Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
11-11 TEC events from Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494

Figures xix

xx IBM Tivoli Storage Resource Manager: A Practical Introduction

Tables

1-1 Comparison of storage management environments, 1985 versus 2003 . . . . . . . . . . . 5
1-2 Current estimated open-systems efficiency rates of storage utilization . . . . . . . . . . . . 9
1-3 Backup and recovery summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5-1 Default profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
5-2 Profiles/Scans versus Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
5-3 Instance Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
5-4 Instance alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
5-5 Table alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

© Copyright IBM Corp. 2003. All rights reserved. xxi

xxii IBM Tivoli Storage Resource Manager: A Practical Introduction

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult
your local IBM representative for information on the products and services currently available in your area. Any
reference to an IBM product, program, or service is not intended to state or imply that only that IBM product,
program, or service may be used. Any functionally equivalent product, program, or service that does not
infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to
evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The
furnishing of this document does not give you any license to these patents. You can send license inquiries, in
writing, to:
IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such provisions are
inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of
express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made
to the information herein; these changes will be incorporated in new editions of the publication. IBM may make
improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time
without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any
manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the
materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring
any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products and cannot confirm the
accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the
capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them
as completely as possible, the examples include the names of individuals, companies, brands, and products.
All of these names are fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrates programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating platform for which the sample
programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore,
cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and
distribute these sample programs in any form without payment to IBM for the purposes of developing, using,
marketing, or distributing application programs conforming to IBM's application programming interfaces.

© Copyright IBM Corp. 2003. All rights reserved. xxiii

Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States,
other countries, or both:

ibm.com® IBM® Tivoli®
pSeries™ NetView® TotalStorage®
xSeries® Notes® TME®
AIX® OS/2® WebSphere®
Cloudscape™ OS/390® 1-2-3®
Domino™ Redbooks™ Redbooks(logo) ™
DB2® Tivoli Enterprise™ ™
Enterprise Storage Server® Tivoli Enterprise Console®

The following terms are trademarks of other companies:

ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel Corporation in the United
States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the
United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.

C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

SET, SET Secure Electronic Transaction, and the SET Logo are trademarks owned by SET Secure Electronic
Transaction LLC.

Other company, product, and service names may be trademarks or service marks of others.

xxiv IBM Tivoli Storage Resource Manager: A Practical Introduction

Preface

Storage growth continues to accelerate, and the cost of disk can approach 80% of total
system hardware costs. Yet, the storage in most businesses is typically only about 50% used.
How can you take control of your storage assets to render utilization more efficient and make
the most of your storage dollars?

IBM® Tivoli® Storage Resource Manager helps you discover, monitor, and create enterprise
policies for your filesystems and databases. You will find out where all your storage is going,
and be able to act intelligently on this information. Application availability is improved because
you will have early warnings when filesystems are running out of space. If you are thinking
about server consolidation, you can use IBM Tivoli Storage Resource Manager to help
efficiently utilize your accumulated storage resources.

This IBM Redbook shows how to install, configure, and protect the IBM Tivoli Storage
Resource Manager environment; how to create policies; how to define automated actions like
scripts or SNMP events when policies are violated; and how to produce detailed, meaningful
storage reports. This book is intended for those who want to learn more about IBM Tivoli
Storage Resource Manager and those who are about to implement it.

The second edition of this redbook is updated for IBM Tivoli Storage Resource Manager
Version 1.2 and includes information on IBM TotalStorage® Enterprise Storage System
reporting using CIM/OM, filesystem extension, as well as on how to integrate IBM Tivoli
Storage Resource Manager with other Tivoli products.

© Copyright IBM Corp. 2003. All rights reserved. xxv

The team that wrote this redbook
This redbook was produced by a team of specialists from around the world working at the International
Technical Support Organization, San Jose Center.

The team: Urs, Mike, Michel, Ivo, Charlotte

Charlotte Brooks is an IBM Certified IT Specialist and Project Leader for Tivoli Storage
Management and Open Tape Solutions at the International Technical Support Organization,
San Jose Center. She has 12 years of experience with IBM in the fields of pSeries™, AIX®,
and storage. She has written ten redbooks, and has developed and taught IBM classes on all
areas of storage management. Before joining the ITSO in 2000, she was the Technical
Support Manager for Tivoli Storage Manager in the Asia Pacific Region.

Michel Baus is an IT Architect for @sys GmbH, an IBM Business Partner in Germany. He
has eight years of experience in the areas of UNIX, Linux, Windows and Tivoli Storage and
System Management. He holds several certifications including technical, sales, and is an IBM
Tivoli Certified Instructor. He has developed and taught several storage classes for IBM
Learning Services, Germany. He was a member of the team that wrote the redbook
Managing Storage Management, SG24-6117.

Michael Benanti is an IBM Certified IT Specialist in Tivoli Software, IBM Software Group. In
his six years with IBM, he has focused on architecture, deployment, and project management
in large SAN implementations. Mike also works with the Tivoli World Wide Services Planning
Organization, developing services offerings for IBM Tivoli SAN Manager and IBM Tivoli

xxvi IBM Tivoli Storage Resource Manager: A Practical Introduction

Storage Resource Manager. He has worked in the IT field for more than 11 years, and his
areas of expertise include network and systems management disciplines using Tivoli
NetView® and data communications hardware research and development. He was an author
of the first edition of this redbook.

Ivo Gomilsek is an IT Specialist for IBM Global Services, Slovenia, supporting the Central
and Eastern European Region in architecting, deploying, and supporting SAN/storage/DR
solutions. His areas of expertise include SAN, storage, HA systems, xSeries® servers,
network operating systems (Linux, MS Windows, OS/2®), and Lotus® Domino™ servers. He
holds several certifications from various vendors (IBM, Red Hat, Microsoft). Ivo was a
member of the team that wrote the redbook Designing and Optimizing an IBM Storage Area
Network, SG24-6419, and contributed to various other redbooks on SAN, Linux/390, xSeries,
and Linux. Ivo has been with IBM for five years and was an author of the first edition of this
redbook.

Urs Moser is an Advisory IT Specialist with IBM Global Services in Switzerland. He has more
than 25 years of IT experience, including more than 13 years experience with Tivoli Storage
Manager and other storage management products. His areas of expertise include Tivoli
Storage Manager implementation projects and education at customer sites, including
mainframe environments (OS/390®, VSE, and VM) and databases. Urs was a member of the
team that wrote the redbook Using Tivoli Storage Manager to Back Up Lotus Notes,
SG24-4534.

Thanks to the following people for their contributions to this project:

The authors of the first edition of this Redbook: Michael Benanti, Hamedo Bouchmal, John
Duffy, Trevor Foley, and Ivo Gomilsek.

Maritza M. Dubec, Deanna Polm, Emma Jacobs, Will Carney
International Technical Support Organization, San Jose Center

Brian Delaire, Doug Dunham, Barry Eberly, Nancy Hobbs, Sumant Padbidri, Jason Perkins
IBM Tivoli Storage Resource Manager Development, San Jose

Greg van Hise
IBM Tivoli Storage Architecture, Tucson

Jana Jamsek, Ales Leskosek, Bojan Sojer
IBM Slovenia

Become a published author
Join us for a two- to six-week residency program! Help write an IBM Redbook dealing with
specific products or solutions, while getting hands-on experience with leading-edge
technologies. You'll team with IBM technical professionals, Business Partners and/or
customers.

Your efforts will help increase product acceptance and customer satisfaction. As a bonus,
you'll develop a network of contacts in IBM development labs, and increase your productivity
and marketability.

Find out more about the residency program, browse the residency index, and apply online at:
ibm.com/redbooks/residencies.html

Preface xxvii

Comments welcome
Your comments are important to us!

We want our Redbooks™ to be as helpful as possible. Send us your comments about this or
other Redbooks in one of the following ways:
Use the online Contact us review redbook form found at:
ibm.com/redbooks
Send your comments in an Internet note to:
redbook@us.ibm.com
Mail your comments to:
IBM Corporation, International Technical Support Organization
Dept. QXXE Building 80-E2
650 Harry Road
San Jose, California 95120-6099

xxviii IBM Tivoli Storage Resource Manager: A Practical Introduction

Summary of changes

This section describes the technical changes made in this edition of the book and in previous
editions. This edition may also include minor corrections and editorial changes that are not
identified.

Summary of changes
for SG24-6886-01
for IBM Tivoli Storage Resource Manager: A Practical Introduction
as created or updated on August 19, 2003.

October 2003, Second Edition
This revision reflects the addition, deletion, or modification of new and changed information
described below.

New information
Release of Version 1, Release 2 of IBM Tivoli Storage Resource Manager:
– Automatic file system extension
– Enterprise Storage Server® (ESS) Subsystem Reporting
– LUN Provisioning for ESS Subsystem
– Tivoli Enterprise™ Console (TEC) and other Tivoli products Integration
IBM Tivoli Storage Resource Manager Express Edition

© Copyright IBM Corp. 2003. All rights reserved. xxix

xxx IBM Tivoli Storage Resource Manager: A Practical Introduction

Part 1

Part 1 Introduction
In this part we introduce the concepts of Storage Resource Management and the benefits it
can bring to an organization. Then we overview IBM Tivoli Storage Resource Manager.

© Copyright IBM Corp. 2003. All rights reserved. 1

2 IBM Tivoli Storage Resource Manager: A Practical Introduction

1

Chapter 1. Introduction to Storage Resource
Management
Industry needs Storage Resource Management (SRM) today in open environments for the
same reasons that industry needed Storage Resource Management in the mainframe
environment in the early and mid 1980s. Businesses are generating data so fast that data
storage and data management capabilities are being overwhelmed. If these capabilities
cannot handle the growth, then at some point, the next transaction cannot be captured, and
the business will stop.

Two key problems which impact this situation are:
Storage costs are too high
Storage management costs are too high

SRM tools will help companies lower their cost of storage, and of storage management.

In this chapter, we:
Identify the business and technology considerations, which caused the development of
SRM tools in the UNIX and Windows space
Discuss SRM:
– Benefits of using SRM tools
– Functions that SRM tools should accomplish

Subsequent chapters introduce a solution for SRM - IBM Tivoli Storage Resource Manager,
and discuss deployment architectures, installation and design considerations, operations, and
maintenance.


1.1 What is Storage Resource Management?
Tivoli uses the following definition for Storage Resource Management:
“Storage Resource Management (SRM) is an active, intelligent, business-centric
management solution for storage resources across the enterprise. SRM enables
administrators to visualize their distributed storage network, establish management
policies, and report on resource utilization. Enterprise SRM must support heterogeneous
storage environments, integrate with current and future technologies, and enable policy
based automation to simplify administration. SRM is intended to reduce system costs,
improve return on investment, and reduce the risk of application downtime.”

Figure 1-1 provides some additional definitions as used by outside sources.

SRM Definitions
SRM is a collection of automated tools that enable
administrators to visualize a distributed collection of storage
resources, to make intelligent, informed decisions about the
usage of those resources"
Enterprise Storage, Storage Resource Management Update, Sep 2001

"SRM is a component of overall systems management
infrastructure that improves application availability...by
providing capacity and performance trending, storage and
SAN device configuration, and removable media
management...SRM can help synthesize a unified view of
dispersed and heterogeneous storage deployments.
Gartner Group, Storage Resource Management for Distributed Systems,

ibm.com/redbooks

Figure 1-1 Storage Resource Management definitions

1.1.1 Storage Resource Management, then and now
Storage Resource Management has existed in the mainframe world since the mid-80s,
however, the requirements have only comparatively recently been recognized in the open
(Windows and UNIX) environment. The open environment is also dramatically different from
the traditional mainframe environments of the 80s. In the first release (in 1985) of storage
management software on the mainframe, a company did not go out of business (at least in
the short-term) if their systems failed. Companies had paper systems to fall back on if
computers failed.

Today computers are typically the only vehicle for storing a company's business data.
Computers and storage are now mission-critical.


Today, you need to manage storage to stay in business. You cannot manage what you cannot
measure, and Storage Resource Management is a key tool for measuring and managing
storage resources.

Open environments today are larger and the systems are much more heterogeneous than in
the last century. Table 1-1 summarizes some of the other major differences.

Table 1-1 Comparison of storage management environments, 1985 versus 2003
Storage Management Storage Management today
in 1985

Application Server OS 1 single OS - OS390 Many different OS
Solaris
AIX
HP-UX
Windows NT, 2000,2003, XP
IRIX
Linux
and so on

Storage Networking Channel Attach Switched Fabric
FC Switches
– Brocade, McData, Inrange, 3Com,
Cisco
IP Switches
– Cisco, Nortel, Lucent, etc.

Disk Storage Few manufacturers Many Manufacturers
IBM IBM
Hitachi EMC
StorageTek Hitachi
Compaq
HP
Sun
and all the JBOD suppliers

Chapter 1. Introduction to Storage Resource Management 5

1.2 Storage management issues today

Storage Management Issues Today

Growth (both business transactions and storage
infrastructure) is overwhelming people, tools, and
processes
Unmanaged storage costs too much
Manual Storage Management costs too much

ibm.com/redbooks

Figure 1-2 Storage management issues today

Figure 1-2 summarizes current storage management issues:
Data growth
High cost of unmanaged storage
High cost of manually managing storage

1.2.1 Growth
The single biggest issue is growth. Growth is being driven by three general trends:
Business transaction volumes are growing
Businesses are now storing more information, from different formats and sources, than
ever before. These include audio, graphical, and other scanned data that previously was
stored only on film, paper, or other traditional media.
These new data types (like music, video clips, images, graphical files, etc.) require more
storage per file than older data types like flat files.

The data and storage infrastructure that support this growth is itself growing dramatically.
Storage growth rate is estimated to range from 50-125% annually, depending on the industry
or consultant report of your choice.

Rapid infrastructure growth creates a number of technology and management issues, shown
in Figure 1-3.


Infrastructure Growth Issues

Growth Vector Comment

Large companies have thousands of servers - mixture of
Server
Windows and different UNIX OS

Each corporate server may grow to 3TB data by 2004 - a
Staffing
typical open system administrator can look after 1TB

Average storage growth is 50 to 125% per year - largest
Storage
companies may see much higher rates.

ibm.com/redbooks

Figure 1-3 Infrastructure growth issues

Server growth
Major companies have hundreds of large UNIX servers, and sometimes thousands of
Microsoft Windows servers. They are deploying more servers every quarter, and most large
companies have a large variety of different hardware and software platforms (often not by
design) rather than standardizing on particular configurations.

Staffing growth
While we know that storage and data are growing rapidly, support staff numbers are not. This
only exacerbates the problem. An average corporate server may be supporting in the order of
3 TB of data in the coming years, yet it is estimated that a typical systems administrator can
manage only 1 TB. Since in today’s economic times, businesses are looking to cut costs,
most are shrinking rather than increasing their IT departments. Clearly, more intelligent and
powerful applications will be required to support this environment.

Storage data growth
Although companies are growing their data storage at around 50-125% per year on average,
larger companies may see even higher rates. A typical large company may have as much as
150 TB of data to store installed within the next two years. Total storage reserves of 150 TB to
handle the growth in storage with storage is being consolidated into SANs (Storage Area
Networks). However, SANs do not solve the underlying problems of mismanaged data and its
explosive growth. SANs concentrate the storage, the data, and the problems, and emphasize
the need for management.


1.2.2 Storage costs too much, and money is not used efficiently
Two of the principal issues driving storage management requirements are the costs and
inefficient utilization of storage.

Costs
Storage is a large portion of IT budgets. Even with disk prices dropping at 30% per year (on
average), if storage requirements grow at 100% per year, total costs spent on storage will
grow 40% year-over-year. Storage has to be managed.

The fact that storage is inefficiently used is doubly critical in today’s environment of tight
budgets:
1. Storage administrators do not have the tools to answer questions like:
– How much storage will I need next year, given my current growth rates?
– How fast are my databases growing?
– What servers are running out of storage today?
– Can I compare the forecast on demand versus capacity from last year to the actual rate
of growth that occurred this year?
2. Because they do not have the answers to these and other questions, they wind up:
– Buying storage at the last minute (paying too much money for it)
– Buying too much (better to spend too much money on storage than to not have enough
when it is urgently needed)

Storage Resource Management tools would help the storage administrator answer these
questions, and allow corporations to buy the right amount of storage at the right time.

Utilization inefficiencies
Data protection schemes (RAID, mirroring, replication, etc.) are used to protect data from disk
failures and other hardware errors. Allocating and using additional disk for data protection is a
good business decision, and is not an inefficient use of storage.

However, there are many other ways that disk is used inefficiently. Here are a few examples,
and note that if the data is mirrored or RAIDed, then the problem is accordingly multiplied.
1. With direct-attached storage (whether internal or attached to a SAN) in some cases, a
very small percentage of available storage is actually used for application data.
2. Applications are installed, but then are not used. No one tries to locate these unused files.
Application upgrades can also leave unneeded files.
3. Many files are created once, used once, and never accessed or used again; for example,
for testing purposes. This is an example of a stale or obsolete file.
4. Some files are duplicated to other directories or systems, and later the need for the
duplicate file goes away. The duplicate file is no longer needed, but it is cheaper to leave
the duplicate file where it is rather than spend the time to try to find it.
5. It is increasingly common to find music files (often illegally copied) video clips, and other
personal data items placed onto expensive corporate storage.

Current open systems storage utilization rates can range from as low as 25% (direct-attached
Windows servers) to 50-60% (SAN-attached storage). What this means is that on average, if
a company has 100 GB of storage in a filesystem, there is about 25 to 50 GB of actual
important data on that 100 GB of storage. The rest of the disk space is being wasted.


If storage is growing at 100%, and companies are using only 25% or 50% of what they buy to
hold real data, then companies are buying storage they do not need, because they cannot
manage data efficiently.

Table 1-2 Current estimated open-systems efficiency rates of storage utilization

Environment Efficiency rate (typical)

NT Direct-attached 25%

UNIX Direct-attached 50%

FC SAN-attached 70%

Example 1-1 (for a low-end NT environment) and Example 1-2 (for a high-end UNIX
environment) show how the numbers can add up.

Example 1-1 Storage costs in NT environment
A utility company in the Northeast has 150 NT servers with internal disk, with an average
of 25GB usable per NT server. Given requirements for mirroring the OS disk, a hot spare,
RAID-5 for the data, and experience that buying a server fully populated with disks is less
expensive than adding disks to a partially populated server, the client bought 6 disks per
server to get 1 disk for actual data per server. The average cost of the NT servers was
$25,000, and the 36GB disks cost $640 each (market price), with the controller costing
$1100. The client was spending about $5000 per server (disks plus controller) for storage.

The client
spent 6 x 150 x $640= $576,000 for 32TBs of raw disk
to get 1 x 150 x $640 = $96,000 for 3.75TB of disk used for storing data, or
15.4 cents per MB usable.

Vendors argue that disk costs 1.8 cents per MB ($576,000/(32.4*1000) = 1.77 cents). While
true, it is misleading. Companies buy usable disk, not raw storage.

Two comments:
1. The difference is partly the cost of unmanaged storage (and partly the cost of
protection).
2. 15 cents per MB is close enough to the cost of enterprise disk to justify investigating
storage consolidation.

Example 1-2 Same examples, using enterprise storage
We re-calculated the same example using enterprise storage.

Typical efficiency (space used/space available) in enterprise FC SAN Storage is less than
50%. (It is more that the rate for internal storage because more attention is paid to
expensive fibre channel storage.) For the purposes of this example, we are assuming a 50%
‘best case’ scenario.
To get 3.75 TB of usable disk, the customer would have to buy 7.5TB of disk from a vendor.

Using 72GB mirrored disks which cost over $15,000 each, the customer would
buy 14 disks/TB * 3.75TBs * 2 (efficiency factor) * $15,000**/disk = $1,575,000,
to get 14 * 3.75 * $15,000 = $787,500 of usable (3.75TBs) of disk, or
42 cents per MB list price usable.

** -
90% of the current list price from one well-known storage vendor for a 72GB disk


In the examples for 3.75 TB (Example 1-2) the amount of disk bought and not used for storing
original data (excluding data protection) was:
$480,000 in the NT example above (75% of storage costs)
$787,000 in the enterprise disk example (50% of storage costs)

If you extend the two examples above to 150 TB of data, then customers would spend either
$23,000,000 (for the NT example) or $63,000,000 (for the enterprise example) for storage.

Given efficiency rates on 150 TB of used disk:
75% of the $23M, or $19M, would have been wasted in the NT example
50% of the $63M, or $31.5M, would have been wasted in the enterprise disk example

These costs are the price for not managing storage well.

How much of this could be re-captured by using Storage Resource Management software?

Storage Resource Management can help storage administrators improve the efficiency of
disk utilization. It is hard to quantify exactly the efficiency rates in the UNIX/Windows space,
since use of such tools is relatively new. However, in the mainframe world with DFSMS,
efficiency rates of over 95% disk utilization are common. If in the UNIX/Windows space, we
can conservatively assume that we could achieve rates of 80%, then Figure 1-4 shows the
cost savings that might be possible in our examples above.

Potential Storage Dollars Recaptured Using SRM

NT Storage Enterprise FC Storage

Dollars of Storage Actually Used $96,000 $787,500
Original Efficiency 25% 50%
Total $ originally spent $384,000 $1,575,000
Efficiency with SRM 80% 80%
Total $ now available at this efficiency $307,200 $1,260,000
Increased Storage ($$) Can Be Used $211,200 $472,500
Months of 100% Growth Can Absorb 26 7

ibm.com/redbooks

Figure 1-4 SRM helps you recapture dollars already spent on storage

Figure 1-5 is a pictorial representation of the same information.


Increased Utilization From SRM Tools

NT Example

Enterprise Storage

0 500 1,000 1,500
'000s of $$ of Disk Used
Current
Utilization
Increased
Utilization

ibm.com/redbooks

Figure 1-5 Predicted savings from managed storage versus unmanaged storage

One key piece of information is shown in Figure 1-4. By using SRM software to improve our
utilization, then, using existing storage, we can absorb 27 months of growth in the Windows
example, or seven months of growth in the enterprise storage example - this represents a
significant cost benefit.


1.2.3 Unmanaged storage costs too much, and the scope is large

Need for Storage Management

"Most of our clients report that they can afford to
buy storage, but they can't manage it."
Nick Allen, Vice President, Research Director, Gartner

"It's not important how much storage you have,
it's how much managed storage you have. If
you don't know what you've got, how do you
know what you need?"
Michael Karp, Enterprise Management Associates

ibm.com/redbooks

Figure 1-6 The need for storage management

Today, when the user calls and says “my application ran out of disk space and just stopped!”
administrators (storage administrators, network administrators, application administrators, or
platform administrators) have to scramble to get the application running again.

Administrators have to:
Scan the filesystems for stale or duplicate files, and delete them
Look at the application to see if some data can be archived, and try to archive it
Or else, quickly order more disk for earliest delivery, paying whatever the vendor demands

Meantime, the application is down, the company is losing money, and user satisfaction is very
low. Not being able to track the space used against space available is very expensive.

Current tools and processes
The current approach to managing storage resources typically involves manual processes
and custom scripts. For every platform, there might be a custom script to list the storage
available on individual servers. The storage administrators who manage these scripts must
run them periodically, and generally do not have the time to analyze the results, and
sometimes miss critical situations.

To find the stale files, duplicate files, or inappropriate files, the storage administrator would
have to get write access to all the servers in the environment, write the custom scripts, debug
them, run them regularly and review the resulting information manually, and then try to act on
it, while trying to perform his normal duties. The scripts also have to be maintained so that
they cater for new servers, new LUNs or volumes, new filesystems, new applications, new
policies, and so on. Doing all this manually is very difficult, if not almost impossible.


Looking forward
Based on various studies of estimated system and data growth, we proposed the following
projection of the number of filesystems and amounts of storage that would have to be
managed by a typical large company in 2004.

Management Issue Projection for 2004, F500 Company

GB / Host # Hosts Tot Stg (GB) # FS / Host Tot # FS

UNIX 100 750 75,000 4 3,000

Windows 25 3000 75,000 1.5 4,500

3,750 150,000 7,500

ibm.com/redbooks

Figure 1-7 Scope of the problem - total storage, total number of filesystems

In this projection we used 100 GB for the size of the average UNIX host today, 25 GB for the
average Windows host, and 150 TB of storage as a target for the total storage in the average
large company. We also made some assumptions as to the number of filesystems per
UNIX/Windows host. We believe that this is a quite conservative projection. If you use larger
numbers, then the numbers are even more daunting. Nonetheless, the projection illustrates
the point: by 2004, an average large company will be managing:
7,500 filesystems
150TBs of storage
3,750 servers

How many people would I need to manage storage?
The answer to this question depends on the tools used to manage storage.

We have already described the tools that today’s administrators typically use:
Custom-written scripts for different operating systems
Some individual point solutions
Spreadsheets and PC databases
Visio diagrams
Manual update processes
And good memories


Doing some rough cut forecasting to figure out the number of administrators needed to
manage storage, we developed the following estimate.

Potential Number & Cost of Admins Required

# Admins Cost ($100K ea)
Based on Storage GB / Admin
UNIX 3000 25 2.5M
Windows 1000 75 7.5M
100 10.0M
Based on # Servers # Servers/Admin
UNIX 15 50 5.0M
Windows 35 86 8.6M
136 13.6M

ibm.com/redbooks

Figure 1-8 Number and cost of storage administrators needed

In trying to project the staffing cost for storage administration (and only for administering disk)
we started with Figure 1-7, made some assumptions, and looked at the numbers. We made
two different projections - one based on the number of Gigabytes of storage that an
administrator would administer with today’s tools, and one based on the number of servers
that an administrator could manage. The assumptions were conservative.

For storage, we assumed that UNIX administrators could handle 3 TB, and Windows
administrators could handle 1 TB, and that the weighted average cost of an administrator was
$100,000 per year. Adjust your own model according to your own situation, since salary costs
vary greatly among different countries and cities, as well as within industry.

Even with conservative assumptions, administering disk will cost a lot of money. These
numbers are significant, and in parallel the situation facing the IT service industry in 1985
before the introduction of storage management tools on the mainframe. After DFSMS was
introduced to the mainframe, storage administration labor costs dropped by 90%.

Fewer studies have yet been performed in the UNIX/Windows world on the impact of storage
management tools on storage administration costs. If we were to use 45% (half the savings
achieved in the mainframe world) as a working guideline for the savings, we could achieve in
the UNIX/Windows world, given the large numbers, and the figure would be substantial.

1.2.4 Storage management functions defined
So far, we have discussed only administering disk. Storage administration covers other areas
as well:
Platform administration
Backup and recovery


Business Continuance and Disaster Recovery

Platform administration
A company with hundreds of UNIX and thousands of Windows servers across different
business units has thousands of separate filesystems to administer. Managing that many
anything is difficult. A growing percentage of companies have started consolidating storage
into SANs, but they still have the same number of storage entities to manage. Filesystems are
still assigned to individual application servers, and storage on the FC storage frame is
logically segregated.

Some companies have FC storage pools, NAS storage pools, and direct-attached storage
environments. Each FC storage pool is managed by its own storage manager. Each NAS pool
has its own manager. Each small group of direct-attached servers has its own platform
administrator. These labor costs can be at the user department level, at the division IT level,
or at the corporate IT level. The costs are hard to aggregate, but are large.

Backup and recovery
Whether your backup and recovery is decentralized or centralized, the same tasks have to be
performed. These tasks are almost always performed manually.

Table 1-3 Backup and recovery summary
Tape backup architecture Tasks

Decentralized Tape drives embedded in Backup:
backup application servers Load tapes into library
or Run backup program
Small Libraries attached to Monitor job stream
backup servers that handle Fix Errors
5-10 application servers Recovery:
Extract tapes from library, send offsite
Centralized Large library handling 200-600 Recover tapes from offsite as needed
backup application servers Load those tapes into library, perform
recovery

In either case, the corporation is paying for IT professionals to manage the backup and
recovery function. Dollars are either hidden in parts of individual’s salaries across the many
different departmental budgets, or prominently displayed (i.e. a large figure) in a centralized
budget.

Business Continuance and Disaster Recovery
The Disaster Recovery and Business Continuance function continues to be prominent. This
function involves planning a recovery from a site or facility disaster, including people,
processes, facilities, and IT infrastructure. With formerly two to three people, today,
companies have staffed up this function to five to ten people who report (in many cases)
directly to the CEO.

1.2.5 Architecture for a suite of Storage Management solutions
Figure 1-9 shows the storage infrastructure functions from the low level device solutions up to
the business management level.

The current set of Tivoli solutions already provide many of the functions in the Business
Management section (that is, Systems Management, Storage Management, and Security
Management).


IBM Tivoli Storage Manager, IBM Tivoli Storage Resource Manager, and IBM Tivoli Storage
Area Network Manager provide the functionality for the middle Storage Resource
Management layer. They interoperate with and utilize the lower level Storage Infrastructure
layer applications. These are often vendor-specific solutions, such as individual Element
Managers or Replication Solutions. These also encompass some upcoming products from
IBM, such as for Virtualization.

Comprehensive Architecture for a Suite of
Storage Management Solutions
Business Processes
Business
Applications
Management
Systems Management Storage Management Security Management

Enterprise Policy Based Automation
Operations
Storage
Resource Reporting Capacity Asset Event Availability Performance
Management Monitoring

Backup & Recovery / Advanced SAN Management

Policy Based Automation
Storage
File
Infrastructure Media Element Subsystem
Systems Virtualization Replication
Volume Managers Managers Reporting
Mgrs

DAS SAN NAS TAPE
iSCSI Fibre Channel
Devices

ibm.com /redbooks

Figure 1-9 Storage Management disciplines - architecture for a suite of solutions

1.2.6 Standards and Storage Resource Management tools
For the storage users community (both vendors and buyers), standards form the basis for
compatibility and interpretability:
Standards enable buyers to pick the solutions they want to implement with the knowledge
that today’s solution will be interoperable with tomorrow’s solution, and that existing
hardware investments will be protected as the environments are extended.
For vendors, standards give the confidence that a wide market exists for their solutions,
and lower the costs of compatibility testing.

As the Storage Resource Management tools start to implement reporting based on the
storage devices themselves, not just reporting from the operating systems view, the tools
need to know how to get this data from various storage devices. In the past and often still
today, such information was only accessible through vendor APIs as there still is no
standardized way to extract data from the storage device. For example, if the Storage
Resource Management tool wants to report where in the storage array particular data is
located, it will need to communicate to the storage device through a custom API to get this
information. This approach has several drawbacks:


When the vendor changes the API, the management application has to change also.
Higher development costs, because of the diversity of storage devices.
Slow time to market in case of limited development resources.
Some storage vendors do not publish the APIs, resulting in either unsupported devices, or
need to make special arrangements with those vendors.
Management application vendor must maintain a large number of different specifications.

Standards organizations and standards
Today, there are at least 10 organizations involved in creating standards for storage, storage
management, SAN management, and interpretability. Figure 1-10 shows the key
organizations involved in developing and promoting standards relating to storage, storage
management, and SAN management, and the relevant standards for which they are
responsible.

SAN Management Standards Bodies

Marketing De-facto Standards Formal Standards

Internet Engineering Task Force (IETF)
Storage Networking Industry Association (SNIA) Formal standards for SNMP and MIBs
SAN umbrella organization
IBM participation:
Founding member American National Standards
Board, Tech Council, Project Chair Institute (ANSI)
X3T11 for FC/FICON standards
X3T10 for SCI standards
Jiro (StoreX) IBM participation
Fibre Channel Industry
Sun consortium
Association (FCIA)
Sponsors customer events
IBM participation: Board Fibre Alliance International Organization for
EMC consortium Standardization (ISO)
International standardization
SCSI Trade Association IBM Software
National Storage
Technology roadmaps development ISO Certified
Industry Consortium
IBM participation:
Pre-competitive
Member
consortium
Distributed Management
Task Force (DMTF)
Development of CIM
IBM participation

Figure 1-10 Storage standards organizations and their standards

Key standards for Storage Resource Management are:
Distributed Management Task Force (DMTF) Common Information Model (CIM)
Standards. This includes the CIM Device Model for Storage, which at the time of writing
was version 2.7.2 for the CIM schema
Storage Networking Industry Association (SNIA) Storage Management Initiative (SMI)
Specification

CIM/WEB management model
CIM was developed as part of the Web-Based Enterprise Management (WBEM) initiative by
the Desktop Management Task Force (DMTF) to simplify management of distributed systems.


It uses an object-oriented approach to describe management information, and the description
(data model) is platform- and vendor-independent. CIM profiles have already been developed
for some devices, such as Storage Subsystems, Fibre Channel switches, and NAS devices.
IBM’s intent is to support CIM-based management as and when device manufacturers deliver
CIM-based management interfaces.

CIM/WBEM technology uses a powerful human and machine readable language called the
managed object format (MOF) to precisely specify object models. Compilers can be
developed to read MOF files and automatically generate data type definitions, interface stubs,
and GUI constructs to be inserted into management applications.

SMIS object models are extensible, as explained in “SMI Specification” on page 18, enabling
easy addition of new devices and functionality to the model, and allowing vendor-unique
extensions for added-value functionality.

Figure 1-11 shows the components of the SMIS/CIM/WBEM model.

CIM/WBEM management model

Management Application

Auto-generation of Integration Infrastructure
Application and
Object Model Mapping – Vendor Unique Features
Infrastructure
Constructs
•Platform Independent
•Distributed
SMIS • Automated Discovery CIM/WBEM
Interface •Security Technology
•Locking
•Object Oriented

Device Types
Standard
Tape Library Many Other Object
Switch Array
Model per
MOF Device
MOF MOF MOF
Vendor
Unique
Function

ibm.com/redbooks

Figure 1-11 SMIS/CIM/WBEM management model

SMI Specification
SNIA has fully adopted and enhanced CIM standard for Storage Management in its SMI
Specification. The SMI Specification was launched in mid-2002 to create and develop a
universal open interface for managing storage devices including storage networks.

Figure 1-12 shows the SMIS architecture.


Architecture of SMI Specification

Graphical User Interface Management Frameworks Users

Management Tools

Storage Resource Management Container Management Data Management
Performance Volume Management File System
Capacity Planning Media Management Database Manager
Resource Allocation Other… Backup & HSM

Storage Management Interface Specification
Managed Objects
Physical Components Logical Components
Removable Media Volume
Tape Drive Clone
Disk Drive Snapshot
Robot Media Set
Enclosure Zone
Host Bus Adapter Other…
Switch

ibm.com/redbooks

Figure 1-12 SMI Specification

The idea behind SMIS is to standardize the management interfaces so that management
applications can utilize these and provide cross device management. This means that a
newly introduced device can be immediately managed as it will conform to the standards.

SMIS extends CIM/WBEM with the following:
A single management transport
Within the WBEM architecture, the CIM-XML over HTTP protocol was selected for this
transport in SMIS
A complete, unified, and rigidly specified object model.
SMIS defines “profiles” and “recipes” within the CIM that enables a management client to
reliably utilize a component vendor’s implementation of the standard such as the control of
LUNs and Zones in the context of a SAN
Consistent use of durable names
As a storage network configuration evolves and is reconfigured, key long-lived resources
like disk volumes must be uniquely and consistently identified over time
Rigorously documented client implementation considerations
SMIS provides client developers with vital information for traversing CIM classes within a
device/subsystem and between devices/subsystems such that complex storage
networking topologies can be successfully mapped and reliably controlled
An automated discovery system
SMIS compliant products when introduced in a SAN environment will automatically
announce their presence and capabilities to other constituents
Resource Locking


SMIS compliant management applications from multiple vendors can exist in the same
storage device or SAN and cooperatively share resources through a lock manager

The models and protocols in the SMIS implementation are platform-independent, enabling
application development for any platform, and enabling them to run on different platforms. The
SNIA will also provide interpretability tests which will help vendors to test their applications
and devices if they conform to the standard.

Integrating legacy devices into the CIM model
As these standards are still evolving, we cannot expect that all devices will support the native
CIM interface, and because of this, the SMIS is introducing CIM agents and CIM object
managers (CIM/OM). The agents and object managers bridge proprietary device
management to device management models and protocols used by SMIS. The agent is used
for one device and an object manager for a set of devices. This type of operation is also called
a proxy model and is shown in Figure 1-13.

Proxy model (CIM Agent/Object Manager) for
legacy devices
Lock Directory
Manager Server
Client
Directory User
SA 0…n Agent 0…n Agent 0…n

SLP
TCP/IP

CIMxml
CIM operations over http
TCP/IP

SA Service Agent (SA) SA Object Manager
Agent
Agent
0…n Device or
0…n Provider
Subsystem
1 1 0…n
Proprietary Proprietary
1 n
Embedded
Device or Model Device or
Subsystem Device
Subsystem
Proxy Model Proxy
Model

ibm.com/redbooks

Figure 1-13 CIM Agent & CIM Object Manager

The CIM Agent or CIM Object Manager (CIM/OM) will translate a proprietary management
interface to the CIM interface. An example of a CIM/OM is the IBM CIM Object Manager for
the IBM TotalStorage Enterprise Storage Server (ESS).

In the future, more and more devices will be native CIM compliant, and will therefore have a
built-in Agent as shown in the “Embedded Model” in Figure 1-13.

When widely adopted, SMIS will streamline the way that the entire storage industry deals with
management. Management application developers will no longer have to integrate
incompatible feature-poor interfaces into their products. Component developers will no longer
have to “push” their unique interface functionality to applications developers. Instead, both will
be better able to concentrate on developing features and functions that have value to


end-users. Ultimately, faced with reduced costs for management, end-users will be able to
adopt storage-networking technology faster and build larger, more powerful networks.

For more information on SMIS/CIM/WBEM, see the SNIA and DMTF Web site:
http://www.snia.org
http://www.dmtf.org

1.3 Objectives of Storage Resource Management
Customers want to achieve the following goals (shown in Figure 1-14) with Storage Resource
Management tools.

Objectives of Storage Resource Management

Lower the cost of storage acquisition

Lower the cost of storage management
use industry standards for managing storage devices (eg CIM/WBEM)
manage all storage with one application
manage across the boundaries of the physical devices

Support business requirements as seamlessly as possible
efficiently store all data
monitor and predict storage utilization
meet SLAs - keep applications running

ibm.com/redbooks

Figure 1-14 Objectives of Storage Resource Management

IBM Tivoli Storage Resource Manager is enabled for CIM/WBEM based storage management
and as more and more devices become CIM enabled, it will be ready to manage them,
enabling a single point of management control for different storage devices.

IBM Tivoli Storage Resource Manager addresses the goals identified above, and offers
storage administrators the reporting tools needed to understand:
How much space is allocated to each application server, and how much is being used?
How fast data is growing (for a server, a filesystem, a type of data, etc.)?
How much space is being wasted?
How much space is available across a business unit or the enterprise?
How the data is distributed inside storage device (as of time of writing this was only
available for IBM ESS)?
Forecast requirements
And many other issues


Summary
We have demonstrated that:
Storage and data are growing rapidly.
Storage inefficiencies are rife.
Storage costs a lot, even as the cost of storage decreases.
Storage management costs a lot.
Companies cannot continue to manage storage and data the old way (managing
individual components) and be successful. Companies must adopt new tools to manage
storage and data.

The next chapter introduces IBM Tivoli Storage Resource Manager.


2

Chapter 2. Introduction to IBM Tivoli
Storage Resource Manager
This chapter introduces and positions IBM Tivoli Storage Resource Manager - its
architecture, components, and functionality.

Tivoli Storage Resource Manager monitors storage assets, capacity, and usage across an
enterprise. Tivoli Storage Resource Manager can look at:
Storage from a host perspective: Manage all the host-attached storage, capacity and
consumption attributed to filesystems, users, directories, and files
Storage from an application perspective: Monitor and manage the storage activity inside
different database entities including instance, tablespace, and table
Storage utilization and provide chargeback information.

Tivoli Storage Resource Manager provides over 300 standardized reports (and the ability to
customize your own reports) about filesystems, databases, and storage infrastructure. These
reports provide the storage administrator information about:
Assets
Availability
Capacity
Usage
Usage violation
Backup

With this information, the storage administrator can:
Discover and monitor storage assets enterprise-wide
Report on enterprise-wide assets, files and filesystems, databases, users, and
applications
Provide alerts (set by the user) on issues such as capacity problems, policy violations, etc.
Support chargebacks by usage or capacity


2.1 IBM Tivoli Storage Resource Manager overview
This section describes the business purpose of Tivoli Storage Resource Manager, its
architectures, components, and supported platforms.

2.1.1 Business purpose of Tivoli Storage Resource Manager
The primary business purpose of Tivoli Storage Resource Manager is to help the storage
administrator keep data available to applications so the company can produce revenue.

Through monitoring and reporting, Tivoli Storage Resource Manager helps the storage
administrator prevent outages in the storage infrastructure. Armed with timely information, the
storage administrator can take action to keep storage and data available to the application.
Tivoli Storage Resource Manager also helps to make the most efficient use of storage
budgets by allowing administrators to use their existing storage more efficiently, and more
accurately predict future storage growth.

2.1.2 Architecture
Tivoli Storage Resource Manager architecture is shown in Figure 2-1.

Tivoli Storage Resource Manager Architecture

Tivoli Storage
Resource
Manager HP/ UX
Server

Web Server
Managed

Storage

Browser Repository

ibm.com/redbooks

Figure 2-1 Tivoli Storage Resource Manager architecture

The Server system manages a number of Agents, which can be servers with storage
attached, NAS systems or database application servers. Information is collected from the
Agents and stored in a database repository. The stored information can then be displayed
from a native GUI client or browser interface anywhere in the network. The GUI or browser


interface gives access to the other functions of Tivoli Storage Resource Manager, including
creating and customizing of a large number of different types of reports and setting up Alerts.

With Tivoli Storage Resource Manager you can:
Monitor virtually any host
Monitor local, SAN-attached and Network Attached Storage
From a browser anywhere on the network

2.1.3 IBM Tivoli Storage Resource Manager products
Figure 2-2 shows the products available for Storage Resource Management.

IBM Tivoli Storage Resource Manager Products
IBM Tivoli Storage Resource Manager
Monitoring and reporting for servers and their storage
Wide OS support for Agents
Includes NAS monitoring and reporting
Pre-requisite for the other products

single Server Edition

IBM Tivoli Storage Resource Manager for Databases
Monitoring and reporting for application databases
Supports UDB / DB2 , Oracle, Sybase and MS SQL Server

IBM Tivoli Storage Resource Manager for Chargeback
Collects storage usage information
Generates reports and invoices for chargeback

ibm.com/redbooks

Figure 2-2 IBM Tivoli Storage Resource Manager products

This is the basic product for the set. It is needed as a pre-requisite for the other two products.
IBM Tivoli Storage Resource Manager provides monitoring, reporting, and alerting for storage
on a wide variety of popular operating systems, including UNIX variants, Windows and
NetWare. See 2.1.5, “Supported platforms for IBM Tivoli Storage Resource Manager” on
page 28 for the complete list of currently supported platforms. IBM Tivoli Storage Resource
Manager also includes monitoring and reporting for NAS devices.

IBM Tivoli Storage Resource Manager Express Edition is for single server, single processor
configurations. It can be used for small customer accounts which have a limited number of
storage servers by installing it on each system. Tivoli Storage Resource Manager Express
Edition contains all the functionality and features of Tivoli Storage Resource Manager except
for Network Attached Storage (NAS) and Enterprise Storage Server (ESS) subsystem

Chapter 2. Introduction to IBM Tivoli Storage Resource Manager 25

reporting. Tivoli Storage Resource Express Edition supports the same server platforms as the
full product.

IBM Tivoli Storage Resource Manager for Databases is an additionally priced and orderable
product. It requires IBM Tivoli Storage Resource Manager as a pre-requisite. It provides
monitoring and reporting for application databases - showing storage utilization by these
applications, finding unused space, identifying the fastest growing databases, and many other
functions.

IBM Tivoli Storage Resource Manager for Chargeback
IBM Tivoli Storage Resource Manager for Chargeback is an additionally priced and orderable
product. It requires IBM Tivoli Storage Resource Manager as a pre-requisite. It uses the
storage usage information gathered by IBM Tivoli Storage Resource Manager and IBM Tivoli
Storage Resource Manager for Databases to generate invoices that charge back for storage
usage.

2.1.4 Components of IBM Tivoli Storage Resource Manager
All three IBM Tivoli Storage Resource Manager products use the same components -
different functions are enabled by licensing them individually. At a high level, the major
components of Tivoli Storage Resource Manager are:
Server, running on a managing server, with access to a database repository
Agents, running on one or more Managed Devices
Clients (using either a locally installed GUI, or a browser-based Web GUI) which users
and administrators use to perform storage monitoring tasks.

These components are shown in Figure 2-3 below.


Tivoli Storage Resource Manager Components

D
I C

Direct Connect
Clients SRM Server

Managed
Servers
(Agents)

WWW Server

SRM Database I DC

Repository

Web Conect
Clients

ibm.com/redbooks

Figure 2-3 Components of Tivoli Storage Resource Manager

Tivoli Storage Resource Manager Server
The Tivoli Storage Resource Manager Server:
Controls the discovery, reporting, and Alert functions
Stores all data in the central repository
Issues commands to Agents for jobs (either scheduled or ad hoc)
Receives requests from the user interface clients for information, and retrieves the
requested information from the central data repository.
Extends filesystems automatically
Reports on the IBM TotalStorage Enterprise Storage Server (ESS) and can also provide
LUN provisioning

An RDBMS (either locally or remote) manages the repository of data collected from the
Agents, and the reporting and monitoring capabilities defined by the users.

WWW Server
The Web Server is optional, and handles communications to allow remote Web access to the
Server. The WWW Server can run on the same physical server as the SRM Server.

SRM Agent (on a Managed System)
The Agent runs Probes and Scans, collects storage-related information from the managed
system, and forwards it to the Manager to be stored in the database repository, and acted on


if so defined. An Agent is required for every host system to be monitored, with the exception
of NetWare and NAS devices.

Novell NetWare and NAS devices do not currently support locally installed Agents - they are
managed through an Agent installed on a machine that uses (accesses) the NetWare or NAS
device. The Agent will discover information on the volumes or filesystems that are accessible
to the Agent’s host.

The Agents are quite lightweight. Agents listen for commands from the host, and then perform
a Probe (against the operating system), and/or a Scan (against selected filesystems). Normal
operations might see one scheduled Scan per day or week, plus various ad hoc Scans.
Chapter 5, “Operations: Policy, Quotas, and Alerts” on page 159 provides details of Scans
and Probes.

Clients (direct-connected and Web connected)
Direct-connect Clients have the GUI to the Server installed locally. They communicate directly
to the Manager to perform administration, monitoring, and reporting. The Manager retrieves
information requested by the Clients from the database repository.

Web-connect clients use the WWW Server to access the user interface through a Web
browser. The Java administrative applet is downloaded to the Web Client machine and
presents the same user interface that Direct-connect Clients see.

2.1.5 Supported platforms for IBM Tivoli Storage Resource Manager
Details of the hardware and software required to install and run Tivoli Storage Resource
Manager components are listed in the IBM Tivoli Storage Resource Manager V1.2 Installation
Guide, GC32-9066 under “System Requirements” and on the Web site:
http://www-3.ibm.com/software/tivoli/products/storage-resource-mgr/platforms.html

Server
The following platforms are supported for Tivoli Storage Resource Manager Server at the
time of writing:
Windows NT 4.0 or higher with SP4.0 or above
Windows 2000
Windows XP
Windows Server 2003
AIX 4.3.3, 5.1
HP-UX 11.0
Solaris 2.6 or 7, 8, or 9
Red Hat Linux 6.2, 7.1, 7.2 (64-bit is not supported)

The database repository can be any of:
Microsoft SQL-Server 7.0 or higher (Windows only)
Oracle 8i or higher
Sybase SQL Server (Adaptive Enterprise Server)11.9.2 or higher
IBM DB2® UDB 7.1 or higher
Cloudscape™ 5.1 or higher (provided with IBM Tivoli Storage Resource Manager)

The database repository on the server can be local for all the databases, and remote for IBM
DB2 UDB, MS SQL-Server, Sybase, and Oracle.


Agents
The following platforms are supported for Tivoli Storage Resource Manager Agents
(Managed Systems) at the time of writing:
Windows NT 4.0 or higher with SP4.0 or above
Windows 2000
Windows XP
Windows Server 2003
Windows 95/98/ME (for the client GUI only, and must be installed to a Web server)
HP-UX 11.0
Solaris 2.6 or 7, 8, or 9
Red Hat Linux 6.2, 7.1, 7.2
AIX 4.3.3, 5.1
Novell NetWare 4.0 or above
NetApp Data ONTAP

Tivoli Storage Resource Manager for Databases
Tivoli Storage Resource Manager for Databases supports the following RDBMS:
Microsoft SQL-Server 7.0 and above
Oracle 8i and above
Sybase SQL Server (Adaptive Enterprise Server) 11.9.2 and above
IBM DB2 UDB 7.1 and above

2.1.6 Security considerations
Tivoli Storage Resource Manager has two security levels: non-administrative users and
administrators:
Non-administrator users can:
– View the data collected by Tivoli Storage Resource Manager
– Create, generate, and save reports
Administrators can:
– Create, modify, and schedule Pings, Probes, and Scans
– Create, generate, and save reports
– Perform administrative tasks and customize the Tivoli Storage Resource Manager
environment
– Create Groups, Profiles, Quotas, and Constraints
– Set Alerts

2.2 Enhancements to Tivoli Storage Resource Manager V 1.2
This section describes enhancements for IBM Tivoli Storage Resource Manager Version 1.2.

2.2.1 Automated filesystem extension
Filesystem extension allows you to create additional space in the local filesystems of
managed hosts. You can extend filesystems manually, or set up a policy to do it automatically.
Policy can be configured to extend filesystems at a specified time, or when the utilization
reaches a specified threshold. Filesystem extension is supported for JFS filesystems running
on AIX 5.1 and VxFS filesystems running on Sun Solaris 2.8. See 5.3.1, “Filesystem
extension and LUN provisioning” on page 200.


2.2.2 Enterprise Storage Server (ESS) integration
ESS Subsystem Reporting gathers and reports on IBM TotalStorage Enterprise Subsystem
(ESS) devices that can be seen in the CIM/OM. IBM Tivoli Storage Resource Manager can
discover ESS subsystems, and report on them. The new subsystem reports show the
capacity, controllers, disks, and LUNs of an ESS, and their relationships to computers and
filesystems within a network. See also 6.3.1, “ESS Reporting” on page 297. ESS LUN
provisioning provides filesystem extension using the ESS Common Information Model/Object
Manager (CIM/OM) to interact with ESS subsystems. CIM/OM was introduced in “CIM/WEB
management model” on page 17. This function allows for the automatic provisioning of
Enterprise Storage Server LUNs when there is not enough space available in a volume group
to extend a filesystem. For more information on ESS LUN provisioning see 5.3.1, “Filesystem
extension and LUN provisioning” on page 200.

2.2.3 TEC integration
You can now choose to send Alerts to the Tivoli Enterprise Console ® (TEC) when they are
triggered. The TEC administrator can write correlation and automation rules to analyze IBM
Tivoli Storage Resource Manager events according to the event definitions specified in the
BAROC file (provided by IBM Tivoli Storage Resource Manager). It also performs responses
such as sending further notification, creating or updating trouble tickets, running programs,
etc. See Chapter 8., “Integration with Tivoli Enterprise Console” on page 411.

2.2.4 Cloudscape
Interbase (formerly shipped for a database repository with IBM Tivoli Storage Resource
Manager) has been replaced with IBM’s Cloudscape database for use as an IBM Tivoli
Storage Resource Manager repository. You can easily install this lightweight database and
use it for demonstration purposes, trial licenses, test environments, and so on. See the IBM
Tivoli Storage Resource Manager Installation Guide, GC32-9066, for more information about
Cloudscape support.

2.2.5 UDB/DB2 support
IBM Tivoli Storage Resource Manager for Databases now supports DB2 UDB 7.1 or higher,
including distributed DB2 databases.

2.3 Justification for IBM Tivoli Storage Resource Manager
An investment in Tivoli Storage Resource Manager is typically justified by:
Reducing costs (disk, and storage administration)
Enhancing revenue (keeping data available to applications all the time)

When you first run Tivoli Storage Resource Manager (and Tivoli Storage Resource Manager
for Databases) against your servers and disks, filesystems and databases, you find out:
What space is used on what servers and storage
What files are using that space
Which database applications have sufficient space, and which do not

Customers typically find that utilization percentage across the enterprise is low - typically less
than 50%. Therefore, generally the initial focus is on housecleaning - delete stale, old, or
inappropriate files. After housecleaning, storage utilization should now have reached even
lower levels - maybe 40% this time. After completing this step, you can continue to more long


term goals such as planning for future growth and storage purchases, and implementing
appropriate policies and reporting to ensure storage use remains efficient.

2.3.1 Improving storage return on investment
Tivoli Storage Resource Manager can improve the storage return on investment by:
Delaying purchases of disk - After performing housecleaning, you can satisfy the demand
for more storage from existing (now freed-up) disk. Depending on your particular situation,
you may not need to buy more disk for 6 to 24 months.
Lowering the storage growth rate - Because you now are monitoring and keeping better
control of your storage according to policies in place, it should grow at a lower rate than
before.
Lowering disk costs - With Tivoli Storage Resource Manager, you will know what the real
quarter-to-quarter growth rates actually are, instead of approximating (best-effort basis)
once per year. You can project your annual demand with a good degree of accuracy, and
can negotiate an annual contract with periodic deliveries, at a price lower than you would
have paid for periodic emergency purchases.
Lowering storage management costs - The manual effort is greatly reduced as most
functions, such as gathering the information and analyzing it, are automated. Automated
Alerts can be set up so the administrator only needs to get involved in exception
conditions.

Enhancing revenue
Before using Tivoli Storage Resource Manager to manage your storage, it was difficult to get
advance warning of out-of-space conditions on critical application servers. If an application
did run out of storage on a server, it would typically just stop. This means revenue generated
from that application or the service provided by it also stopped, and this incurred a high cost
to fix it, as fixing unplanned outages fast is usually expensive.

With Tivoli Storage Resource Manager, applications will not run out of storage. You will know
when they need more storage, and can get it at a reasonable cost before an outage occurs.
You will avoid the loss of revenue and services, plus the additional costs associated with
unplanned outages.

2.4 Functions of IBM Tivoli Storage Resource Manager
Tivoli Storage Resource Manager performs the functions shown in Figure 2-4. These
functions are overviewed in the rest of this chapter and explored in detail in the rest of the
book. Tivoli Storage Resource Manager is designed to be easy to use, quick to install, with
flexible and powerful configuration.


IBM Tivoli Storage Resource Manager Functions
Automatically discover and monitor disks, partitions, shared
directories, and servers

Reporting to track asset usage and availability
physical inventory - disks, partitions, servers
logical inventory - filesystems & files, databases & tables
forecasting demand versus capacity
standardized and customized reports, on-demand and batched
various user-defined levels of grouping
from summary level down to individual file or userID granularity

Alerts - execute scripts, email, SNMP traps, event log

Quotas

Chargeback
ibm.com/redbooks

Figure 2-4 Tivoli Storage Resource Manager functions

2.4.1 Basic menu displays
Figure 2-5 shows the main menu for IBM Tivoli Storage Resource Manager. You can see that
the Agents configured show under the Agents entry. The green dot shows that the Agent is
communicating with the Server. The red crossed circle indicates that CLYDE is down. The red
triangle next to the Agent SUSE82-1 indicates that the Agent on that system is not reachable.
The red crossed square next to the Agent BANDA indicates that it was connected, but
currently there is an update for Tivoli Storage Resource Manager agent running. This display
thus shows a quick summary of the state of each Agent.


Figure 2-5 Agent summary

Figure 2-6 shows the Tivoli Storage Resource Manager dashboard. This is the default
right-hand pane display when you start Tivoli Storage Resource Manager and shows a quick
summary of the overall health of the storage environment. It can quickly show you potential
problem areas for further investigation.


Figure 2-6 Tivoli Storage Resource Manager - dashboard

The dashboard contains four viewable areas, which cycle among seven pre-defined panels.
To cycle, use the Cycle Panels button. Use the Refresh button to update the display.

Enterprise-wide summary
The Enterprise-wide Summary panel shows statistics accumulated from all the Agents. The
statistics are:
Total filesystem capacity available
Total filesystem capacity used
Total filesystem free capacity
Total allocated and unallocated disk space
Total disk space unallocated to filesystems
Total number of monitored servers
Total number of unmonitored servers
Total number of users
Total number of disks
Total number of filesystems
Total number of directories
Total number of files

Filesystem Used Space
This panel displays a pie chart showing the distribution of used and free space in all
filesystems. Different chart types can be selected here. This provides a quick snapshot of
your filesystem space utilization efficiency.


Users Consuming the Most Space
By default this panel displays a bar chart (different chart types can be selected) of the users
who are using the largest amount of filesystem space.

Monitored Server Summary
This panel shows a table of total disk filesystem capacity for the monitored servers sorted by
OS type.

Filesystems with Least Free Space Percentage
This panel shows a table of the most full filesystems, including the percent of space free, the
total filesystem capacity, and the filesystem mount point.

Users Consuming the Most Space Report
This panel shows the same information as the Users Consuming the Most Space panel, but in
a table format.

Alerts Pending
This panel shows active Alerts that have been triggered but are still pending.

2.4.2 Discover and monitor Agents, disks, filesystems, and databases
Tivoli Storage Resource Manager uses three methods to discover information about the
assets in the storage environment: Pings, Probes, and Scans. These are typically set up to
run automatically as scheduled tasks. You can define different Ping, Probe, and Scan jobs to
run against different Agents or groups of Agents (for example, to run a regular Probe of all
Windows systems) according to your particular requirements.

Pings
A Ping is a standard ICMP Ping which checks registered Agents for availability. If an Agent
does not respond to a Ping (or a pre-defined number of Pings) you can set up an Alert to take
some action. The actions could be one, any, or all of:
SNMP trap
Notification at login
Entry in the Windows event log
Run a script
Send e-mail to a specified user(s)

Pings are used to generate Availability Reports, which lists the percentage of times a
computer has responded to the Ping. An example of an Availability Report for Ping is shown
in Figure 2-7. Availability Reports are discussed in detail in 6.2.3, “Availability Reporting” on
page 262.


Figure 2-7 Availability Report - Ping

Probes
Probes are used to gather information about the assets and system resources of monitored
servers, such as processor count and speed, memory size, disk count and size, filesystems,
etc. If Tivoli Storage Resource Manager for Databases is licensed, then Probes also gather
information about the files, instances, logs, and objects that makeup the monitored
databases. The data collected by the Probe process is used in the Assets Reports described
in 6.2.1, “Asset Reporting” on page 252.

Figure 2-8 shows an Asset report for detected disks.

Figure 2-8 Asset Report of discovered disks

Figure 2-9 shows an Asset Report for detected database tablespaces.


Figure 2-9 Asset Report of database tablespaces

Scans
The Scan process is used to gather statistics about usage and trends of the server storage. If
Tivoli Storage Resource Manager for Databases is licensed, then Scans also gather
information about the storage usage and trends within the monitored databases. Data
collected by the Scan jobs are tailored by Profiles. Results of Scan jobs are stored in the
enterprise repository. This data supplies the data for the Capacity, Usage, Usage Violations,
and Backup Reporting functions. These reports can be scheduled to run regularly, or they can
be run ad hoc by the administrator.

Profiles limit the scanning according to the parameters specified in the Profile. Profiles are
used in Scan jobs to specify what file patterns will be scanned, what attributes will be
gathered, what summary view will be available in reports and the retention period for the
statistics. Tivoli Storage Resource Manager supplies a number of default Profiles which can
be used, or additional Profiles can be defined. Table 5-1 on page 180 shows the default
Profiles provided. Some of these include:
Largest files - Gathers statistics on the largest files
Largest directories - Gathers statistics on the largest directories
Most at risk - Gathers statistics on the files that have been modified the longest time ago
and have not been backed up since modified (Windows Agents only)

Figure 2-10 shows a sample of a report produced from data collected in Scans.


Figure 2-10 Summary View - by filesystem, disk space used and disk space free

This report shows a list of the filesystems on each Agent, the amount of space used in each,
expressed in bytes and as a percentage, the amount of free space, and the total capacity
available in the filesystem.

2.4.3 Reporting
Reporting in Tivoli Storage Resource Manager is very rich, with over 300 pre-defined views,
and the capability to customize those standard views, save the custom report, and add it to
your menu for scheduled or ad hoc reports. You can also create your own individual reports
according to particular needs and set them to run as needed, or in batch (regularly). Reports
can be produced in table format or a variety of charting (graph) views. You can export reports
to CSV or HTML formats for external usage.

Reports are generated against data already in the repository. A common practice is to
schedule Scans and Probes just before running reports.

Reporting can be done at almost any level in the system, from the enterprise down to a
specific entity and any level in between. Figure 2-6 on page 34 shows a high-level summary
report. Or, you can drill down to something very specific. Figure 2-11 is an example of a


lower-level report, where the administrator has focussed on a particular Agent, BANDA, to
look at a particular disk on a particular controller.

Figure 2-11 Asset Report - BANDA assets

Reports can be produced either system-wide or grouped into views, such as by computer, or
OS type.

Restriction: Currently, there is a maximum of 32,767 (216 -1) rows per report. Therefore,
you cannot produce a report Tivoli Storage Resource Manager to list all the .HTM files in a
directory containing a million files. However, you can (and it would be more productive to
do so) produce a report of the 20 largest files in the directory, or the 20 oldest files, for
example.

Tivoli Storage Resource Manager allows you to group information about similar entities (disk,
filesystems, etc.) from different servers or business units into a summary report, so that
business and technology administrators can manage an enterprise infrastructure. Or, you can
summarize information from a specific server - the flexibility and choice of configuration is
entirely up to the administrator.

You can report as at a point in time, or produce a historical report, showing storage growth
trends over time. Tivoli Storage Resource Manager reporting lets you track actual demand for
disk over time, and then use this information to forecast future demand for the next quarter,
two quarters, year, etc. Figure 2-12 is an example of a historical report, showing a graph of
the number of files on the C drive on the Agent WISLA.


Figure 2-12 Historical report of filesystem utilization

Tivoli Storage Resource Manager has three basic types of reports:
Computers and filesystems
Databases (if the module is licensed)
Chargeback (if the module is licensed)

Reporting categories
Major reporting categories for filesystems and databases are:
Assets Reporting uses the data collected Probes to build a hardware inventory of the
storage assets. You can then navigate through a hierarchical view of the assets by drilling
down through computers, controllers, disks, filesystems, directories, and exports. For
database reporting, information on instances, databases, tables, and data files is
presented for reporting.
Storage Subsystems Reporting provides information shows storage capacity at a
computer, filesystem, storage subsystem, LUN, and disk level. These reports also enable
you to view the relationships among the components of a storage subsystem. Storage
Subsystem Reporting is available at the time of writing for the IBM TotalStorage Enterprise
Storage Server (ESS)
Availability Reporting shows responses to Ping jobs, as well as computer uptime.
Capacity Reporting shows how much storage capacity is installed, how much of the
installed capacity is being used, and how much is available for future growth. Reporting is
done by disk and filesystem, and for databases, by database.
Usage Reporting shows the usage and growth of storage consumption, grouped by
filesystem, and computers, individual users, or enterprise-wide.
Usage Violation Reporting shows violations to the corporate storage usage policies, as
defined through Tivoli Storage Resource Manager. Violations are either of Quota (defining


how much storage a user or group of users is allowed) or Constraint (defining which file
types, owners and file sizes are allowed on a computer or storage entity). You can define
what action should be taken when a violation is detected - for example, SNMP trap, e-mail,
or running a user-written script.
Backup Reporting identifies files which are at risk because they have not been backed up.

Reporting on the Web
It is easy to customize Tivoli Storage Resource Manager to set up a reports Web site, so that
anyone in the organization can view selected reports through their browser. Section 6.7,
“Setting up a reports Web site” on page 361 explains how to do this. Figure 2-13 shows an
example of a simple Web site to view Storage Resource Management reports.

Figure 2-13 SRM Reports on the Web

2.4.4 Alerts
An Alert defines an action to be performed if a particular event occurs or condition is found.
Alerts can be set on physical objects (computers and disks) or a logical objects (filesystems,
directories, users, databases, and OS user groups). Alerts can tell you, for instance, if a disk
has a lot of recent defects, or if a filesystem or database is approaching capacity.

Alerts on computers and disks come from the output of Probe jobs and are generated for
each object that meets the triggering condition. If you have specified a triggered action
(running a script, sending an e-mail, etc.) then that action will happen if the condition is met.

Alerts on filesystems, directories, users, and OS user groups come from the combined output
of a Probe and a Scan. Again, if you have specified an action, that action will be performed if
the condition is met.


An Alert will register in the Alert log, plus you can also define one, some or all of the following
actions to be performed in addition:
Send an e-mail indicating the nature of the Alert.
Run a specific script with relevant parameters supplied from the content of the Alert.
Make an entry into the Windows event log.
Pop up next time the user logs in to Tivoli Storage Resource Manager.
Send an SNMP trap.
Log a TEC event

Figure 2-14 shows the Alert Log. The entries Alert Log, All, Computer, and Filesystem are in
red, signifying that an Alert threshold has been reached. Drilling down on Computer, you can
see the details of the Alert. We can see it was caused by the system VMWARE2KSRV1 being
unreachable.

Figure 2-14 Alert Log and details

Refer to 5.2, “OS Alerts” on page 189 for details on alerts.

2.4.5 Chargeback: Charging for storage usage
Through the optional Tivoli Storage Resource Manager for Chargeback product, Tivoli
Storage Resource Manager provides the ability to produce Chargeback information for
storage usage. The following items can have charges allocated against them:
Operating system storage by user
Operating system disk capacity by computer
Storage usage by database user
Total size by database tablespace

Tivoli Storage Resource Manager can directly produce an invoice or create a file in CIMS
format. CIMS is a set of resource accounting tools that allow you to track, manage, allocate,
and charge for IT resources and costs. For more information on CIMS see the Web site:
http://www.cims.com.

Chargeback is a very powerful tool for raising the awareness within the organization of the
cost of storage, and the need to have the appropriate tools and processes in place to manage
storage effectively and efficiently.

Example 2-1 shows a Chargeback Report based on disk usage by user.


Example 2-1 Chargeback Report based on disk usage by user
Tivoli SRM for ChargeBack page 1
User Usage Invoice 24-Sep-02

Administrator.hb

Name SPACE COST
(MB) 0.1042/MB

100 5 0.52

group total 5 0.52


Tivoli.Default User Group

Name SPACE COST
(MB) 0.1042/MB

[Supervisor] 524 54.60
1009 0 0.00
101 4 0.42
1010 1 0.10
1012 1 0.10
1084 1 0.10
111 1 0.10
1414 24 2.50
202 0 0.00
240 1 0.10
50 1 0.10
5115 10 1.04
8482 7 0.73
9727 0 0.00
adm 3 0.31
admin 523 54.50
Administrators 37,687 3,926.99
backup 27 2.81
bin 1,173 122.23
cbres 1 0.10
daemon 1 0.10
guest 1 0.10
imnadm 2 0.21
invscout 1 0.10
itso_hb 134 13.96
itso_usr 1 0.10
IUSR_LOCHNESS 1 0.10
IWAM_LOCHNESS 1 0.10
lotti 7 0.73
lp 1 0.10
nobody 1 0.10
oracle 5 0.52
root 5,857 610.30
sys 1 0.10
SYSTEM 3 0.31
uucp 2 0.21


group total 46,008 4,793.97

Run Summary 24-Sep-02

User Usage Invoice 46,013 MB 4,794.49

run total 4,794

Refer to 6.8, “Charging for storage usage” on page 364 for more details on Chargebacks.

2.5 Chapter summary
In this chapter we introduced Tivoli Storage Resource Manager, whose primary business
purpose is to keep the storage infrastructure running to assist revenue-generating activities.

Tivoli Storage Resource Manager
Business Benefits:
Improve Storage ROI
Reduce Storage Administration Costs
Help Improve Revenue by Reducing the Risks of Application Downtime

ibm.com/redbooks

Figure 2-15 Business benefits of Tivoli Storage Resource Manager


Part 2

Part 2 Design
considerations
In this part we present some things to consider when designing an IBM Tivoli Storage
Resource Manager solution, specifically covering some deployment scenarios. We present
the basic architecture and describe how higher availability can be implemented.


3

Chapter 3. Deployment architecture
In this chapter we will describe considerations for the deployment architecture of the IBM
Tivoli Storage Resource Manager in the enterprise. We will discuss the design strategies and
implementation infrastructure. An overview of the number of Agents and Agent placement will
be covered along with various deployment scenarios.


3.1 IBM Tivoli Storage Resource Manager architecture
Figure 3-1 shows the IBM Tivoli Storage Resource Manager architecture.

Tivoli Storage Resource Manager Architecture

D
I C

Direct-connect
Clients SRM Server

10 10 10 %
%% Managed
10 % 10 % Servers
10 % 10 %
10 10 10 %
%%

Scheduled Batch
Reports WWW Server

SRM Database I DC

Repository

Web Connect
Clients

ibm.com/redbooks

Figure 3-1 IBM Tivoli Storage Resource Manager architecture

Tivoli Storage Resource Manager consists of the following components:
Server acts as the center for all management operations. All requests from clients are
sent to the SRM server, and the server then retrieves data from the repository and returns
it to the client. With this data, users can construct and display the reports. The Server also
directs the Agent activity through its job scheduling component.
Database Repository is used to store the collected data from the Agents.
WWW Server is optional, and provides communications for remote Web access to the
Server. The WWW Server can run on the same physical system as the Tivoli Storage
Resource Manager Server.
Managed Systems run the Tivoli Storage Resource Manager Agent code, which is used
to gather the information about the managed server, its storage, and managed
applications.
Direct-connect Clients have the GUI to the Server installed locally. They communicate
directly with the Server to perform administration, monitoring, and reporting.
Scheduled Batch Reports are jobs which prepare reports based on collected data from
the Managed Systems, which are scheduled to run automatically. The reports will be
generated using the data residing in the database.


Web Connect Clients use the WWW Server to access the GUI through a Web browser.
The Java administrative applet is downloaded to the Web Client machine and presents the
same user interface as for the Direct Connect Clients.

3.2 IBM Tivoli Storage Resource Manager Server
The Server component is the main part of IBM Tivoli Storage Resource Manager. The Server
is responsible for the following roles as shown in Figure 3-2.


Server roles
Monitoring
Discovery
Probes
Pings
Scans
Policy Management
Quotas
Constrains
Scheduled Actions (SCRIPTS)
Alerts
Alerts (SCRIPTS)

ibm.com/redbooks

Figure 3-2 IBM Tivoli Storage Resource Manager Server roles

Monitoring
– Discovery - The Server searches the network to discover machines which do not have
Agent code installed (that is, not yet being monitored by IBM Tivoli Storage Resource
Manager). It will add them to the Unmanaged list (shown in Figure 3-3 on page 51) so
they can be potentially managed later. Only Windows systems in the same domain as
the IBM Tivoli Storage Resource Manager Server will be discovered.
– Probes - The Server will collect the inventory of storage assets of Managed Systems
(computers, controllers, disk driver, filesystems, logical units, etc.) and store it in the
database repository.
– Pings - The Server checks the availability of the Managed Systems by issuing TCP/IP
ping commands to the system. This function is not available for NAS devices and
NetWare servers.
– Scans - The Server Scans the Managed Systems to gather information on usage and
consumption.

Chapter 3. Deployment architecture 49

Policy Management
– Quotas - The Quota check is performed based on the results of the Scans. Quotas
define the consumption level for filesystems, computers, and network. Quotas can be
run from the GUI, or they can be scheduled to run automatically. The data used for
Quota checking resides in the database. To achieve the most accurate Quota checking,
you need to schedule the Scan job before performing Quota check.
– Constraints - During a Scan, the Server will also perform a Constraint check on the
results. Constraints can be used to define what are acceptable and unacceptable file
types, file sizes, and file owners on Managed Systems.
– Scheduled Actions - You can schedule execution of a script against Managed Systems.
The script can be use any kind of command-shell, batch programming language of
third party tool, which can be invoked through a command line interface and is valid for
execution on the Agent.
Alerts
– Alerts - After a Scan the Server will issue Alerts related to the Alert Threshold defined.

The Server roles described above are covered in more detail in Chapter 5, “Operations:
Policy, Quotas, and Alerts” on page 159.

All Storage Resource Management operations are controlled from the Server side. The
Server communicates with the Agents (Managed Systems) when it is performing those tasks.
No managed tasks are performed on the Agent itself. The Agent is just performing the Scans
and script execution on behalf of the Server. Also, all the communication with the database is
done on the Server side for performance reasons. The data is transmitted from the Agent to
the Server and the Server then stores it in the database repository. With such an approach,
there is no need for any database connectivity software on the Agents. Also, since the
Direct-connect Clients and Web Connect Clients for reporting request data through the
Server, rather than directly from the database, they also do not require any database
connectivity software installed.

As everything is controlled and run from the Server side, reliability and availability is a key
consideration for the system which is running the IBM Tivoli Storage Resource Manager
Server.

3.2.1 Discovery of unmanaged Windows systems
After the Tivoli Storage Resource Manager Server is installed it will try to find any unmanaged
Windows systems. In the process of discovery, one of the Agents installed in each Windows
domain or workgroup will identify other Windows systems. This data will be then transferred to
the Tivoli Storage Resource Manager Server, which will then query each system to determine
if they have Tivoli Storage Resource Manager Agent installed. If the system does not have the
Agent installed it will appear in the Unmanaged Systems list. To access this list, select IBM
Tivoli SRM -> Reporting -> Asset -> System-wide as shown in Figure 3-3.


Figure 3-3 Unmanaged systems

When you install the Tivoli Storage Resource Manager Server in a new environment, an
Agent is automatically installed on the same system as the Server. In this case after the initial
discovery job, all the Windows systems from the domain or workgroup of the Server system
will be displayed under Unmanaged Computers.

3.2.2 Scripts
Scripts are executed as a result of either of the following events:
Scheduled actions - Batch Reports
Alerts - An Alert can trigger an action, which can be a script

How are scripts run?
During the installation process of the Server and Agents, the scripts directory under the
installation directory is created. The default directory is:
Windows: Program directoryTivoliTSRM
UNIX: /opt/Tivoli/TSRM or /usr/Tivoli/TSRM

The following steps explain how scripts are run when they are triggered:
The Server looks in its local scripts directory.
If the script with the required name is in that directory, the Server will load the script, and
send it to the Agent where it is designated to run.
The Agent receives the script, saves it into a temporary file, and runs it.
After the script is finished, the temporary file on the Agent is deleted.


Note: When running a script against a NAS device or Novell NetWare servers, the
script is run on the Agent assigned to the filesystem where the triggered condition
occurred.

There are two possible scenarios where the script may not run from the Server:
The script already exists on the Agent. In this case the Agent will run the local script
directly instead. The Agent is always checked first to see if it has a local copy, before
running it from the Server.
You did not check the Agent may run scripts sent by server option during the
installation process as described in 4.3.3, “Installation of the Server code” on page 71:
Without this option set, Agents will not receive scripts from the server for execution.

Note: The advantage of setting the policy that Agents may run scripts from the Server is
that you can then install and maintain only one repository for all scripts. This can ease
the management of the scripts and it will also give you consistency.

3.3 IBM Tivoli Storage Resource Manager Agent
The Tivoli Storage Resource Manager Agent is responsible for the following tasks as shown
in Figure 3-4.

Tivoli Storage Resource Manager Agent

Agent types
StorageAgent for OS (includes NAS)
StorageAgent for Databases
StorageAgent for Chargeback

Agent roles
Executing Probes and Scans on behalf of the SRM server
Executing scripts in case of
Scheduled Actions
Alerts

ibm.com/redbooks

Figure 3-4 SRM Agent tasks

The Agent code is required on every system you want to manage. As the Agents
communicate through TCP/IP, the Managed System needs IP connectivity to the Server.


The product uses the same code base for all three Agent types (OS, Database, and
Chargeback). Each of the Agents is activated by the licenses installed with the Manager code.

There are two exceptions on Agent placement:
NAS devices - The monitoring of NAS devices is done through the systems using NAS
attached storage. Depending on the protocol used for filesystem access, those systems
can be either Windows or UNIX based systems.

Tip: It is recommended that you divide NAS exported filesystems among the Managed
Systems, which access the NAS device. This means that the workload of scanning and
probing is shared among the Agents.

Novell NetWare servers - For retrieving the storage information from the servers and
volumes within NDS trees, you must install the Agent code on a Windows system where a
Novell NetWare client is already located. The Agent code uses native NetWare calls from
these systems. The requirements for a Windows Agent to scan NetWare systems are:
– Running Windows 2000 or Windows NT 4 SP4 and above
– Installed a NetWare Client
– Has access to the Novell NetWare servers and volumes within your environment. This
means that you must have a user ID with the correct access level to be able to perform
queries into the NDS trees.

3.4 Deployment considerations
In this section we will outline some considerations for deploying Tivoli Storage Resource
Manager installations. As Tivoli Storage Resource Manager supports various platforms for
the Server and Agent installations, the choice of Server platform will usually reflect the
platforms used in your environment. From the generally available information, and from our
experience in the lab installations, Tivoli Storage Resource Manager can coexist with virtually
any other server software.

A single Server instance can theoretically support more than 1000 Agents. Of course, the
load on the Server side will increase with the number of jobs defined. The load of the jobs on
the Server and Agents depends of the job definition. For example, a Scan which will look for
all files will run much longer, and be more CPU-intensive easier than a Scan which will look
for only particular file types.

The Agent should be installed on every system you want to manage. For managing NAS
devices and Novell NetWare servers, you need to install Agents on the systems using the
NAS and NetWare filesystems, as described in 3.3, “IBM Tivoli Storage Resource Manager
Agent” on page 52.

3.4.1 Repository database
All the configuration data and the data collected from Agent Scans is stored in the database
repository. By using this approach, all the data can be off-loaded to a separate database
server, since Tivoli Storage Resource Manager can use either a locally installed database or
a remote database repository. In the current edition of Tivoli Storage Resource Manager, the
repository can be local or remote using any of Microsoft SQL-Server, Oracle, and Sybase
SQL, or IBM DB2 UDB. The size of the database will vary upon the number of actions you are
taking in your Storage Resource Management environment. The size of the database will
depend on the following parameters:


The amount of historical data you keep
The number of scanned files on each Managed System - for each scanned file, if a file
meets a Constraint criteria, a corresponding entry will be saved in the database.
The type of jobs (for example, different type of Scans and Constraints) you are performing
The number of systems you want to manage - i.e. Agents.

Tip: If possible, it is recommended that you use a separate system for the database
repository.

3.4.2 CIM/OM server placement
IBM Tivoli Storage Resource Manager provides a filesystem extension feature that can be
used to automatically increase filesystem capacity for managed hosts when utilization
reaches a specified level. This function allows for the automatic provisioning of Enterprise
Storage Server LUNs when there is not enough space available in a volume group to extend
a filesystem.

Filesystem extension uses the ESS Common Information Model/Object Manager (CIM/OM)
to interact with ESS subsystems. See “SMI Specification” on page 18 for more information on
CIM/OM. The IBM Tivoli Storage Resource Manager server communicates with the CIM/OM
server over an IP network using the HTTPS protocol. CIM/OMs installed on the same network
subnet as the IBM Tivoli Storage Resource Manager server can be automatically discovered.
The Service Location Protocol (SLP) is used to discover CIM/OMs.
For information about supported versions of the CIM/OM, see the IBM Tivoli Storage
Resource Manager Support Website at:
http://www-3.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageResourceManager.html

Restriction: Automatic discovery is not supported for CIM/OMs installed on Sun Solaris or
HP-UX.

In our lab setup (Figure 3-5), the CIM/OM server is installed on a host called W2KADVTSM,
which talks to the ESS (ESSF20) through Ethernet. The IBM Tivoli Storage Resource
Manager server (W2KADVTSRM) makes an HTTPS connection over the network directly to
the CIM/OM server. Neither the IBM Tivoli Storage Resource Manager server, nor the
CIM/OM server need to be connected through Fibre Channel to the ESS.


Win2k Srv sp3
CIM/OM server
w2kadvtsm
172.31.1.135

43p
AIX 5.1 ML 4 ESSF20
ITSRM Agent 172.31.1.1
tsmsrv43p
172.31.1.155 2109

Win2k Srv sp3
ITSRM Server
w2kadvtsrm
172.31.1.133

Intranet

Figure 3-5 CIM/OM server placement

If you just want ESS LUN reporting, then you do not need agents on the machines connected
to the ESS through Fibre Channel. For additional information (filesystems, devices, etc.) and
filesystem-extension and LUN provisioning, there must be an agent on the hosts connected to
the ESS.

3.4.3 NAS Agent placement
In Figure 3-6 we show an example of two Managed Systems, one on UNIX and one on
Windows using filesystems from a NAS device.


IBM Tivoli SRM Agent setup for NAS devicess
UNIX system
NFS imported network drive(s)

Tivoli SRM Agent installed

I DC
IP
NFS

IP
Tivoli SRM Server
CIFS

NAS Device
CIFS exported network drives
NFS exported network drives

Windows sytem
CIFS imported network drive(s)


ibm.com/redbooks

Figure 3-6 Setup of SRM Agent for NAS devices

In this example we also divided the workload of scanning the NAS device over the two
systems. Depending on the size of the NAS filesystems, it is recommended to spread the
scanning workload among the systems running the Agent code.

NAS discovery
After you complete the installation of the Agents for the systems accessing the NAS devices,
initial discovery will be performed. The discovery job is sent to every managed UNIX Agent
and to one managed Windows Agent in each Windows domain:
Windows - The Agent responsible for the discovery will issue an SNMP query to all the
Windows systems and NAS devices in the domain. If the Vendor Identification Number
matches a number defined in the file confignas.config in the installation directory, the
system will be considered as a NAS device. In Example 3-1 you can see the nas.config file
from our lab installation.

Example 3-1 nas.config file
36 Digital Equipment Corporation
311 Microsoft
789 Network Appliance
1139 EMC Corporation
4693 Maxtor
6411 Quantum/SNAP

After the initial Agent installation the entry for Microsoft is not present. We added the entry
to recognize the IBM NAS 200 device in our lab.


Note: IBM NAS 200 is a Windows OS powered NAS device.

The 311 entry is the generic identification number for Windows systems so all Windows
machines will be discovered. You can later limit the login to the NAS devices (as shown in
Figure 3-7) selecting only the NAS device(s) you want to manage, and leave all the others
unselected. After discovering the NAS devices, the Agent will perform a login into each
device. By default, the password supplied during installation will be used. If the NAS
device requires a different password you can supply this password for each filesystem
separately as shown in “Configuration: General settings” on page 108.

Attention: If you decide to put the 311 entry in nas.config file, all Windows based
systems with SNMP enabled will be recognized as Other NAS devices, as shown in
Figure 3-7. This means that any Windows systems without installed Agents will no
longer show up under unmanaged devices. This could cause potential for a confusing
situation as you may think that all Windows based systems are managed, since they do
not appear in the unmanaged list.

Figure 3-7 After setting 311 for NAS discovery

Tip: Because of the mentioned reasons, if your Windows powered NAS device allows
installation of third party products, we recommend that you install the Agent on the
device itself.

UNIX - All the Managed Systems that have filesystems mounted from other machines will
be used for discovering the NAS devices. The Agent uses the mount table (on Solaris,
auto-mount config files are also used) for the imported mounts. After this, it will perform an
SNMP query, and if the identification number returned is listed in the file nas.config, the


device will be qualified as a NAS device. The NAS discovery process in UNIX will not
perform any logins into the NAS device.

Note: If the NAS device does not report back on the SNMP query, it will appear in the
Unmanaged Computers Report.

3.4.4 Novell NetWare Agent placement
Figure 3-8 shows Windows systems with the Novell NetWare client installed, accessing two
Novell NetWare servers.

IBM Tivoli SRM Agent setup for Novell servers
Windows sytem
with installed Novell NetWare client
and acces to the NDS data

Tivoli SRM Agent installed IDC

IPX/
SPX

IP
I DC

Novell NetWare
running version 4.0 or above

IP
Tivoli SRM Server
IDC

IPX/
SPX

Windows sytem
with installed Novell NetWare client
and acces to the NDS data
Novell NetWare
running version 4.0 or above

ibm.com/redbooks

Figure 3-8 Setup of SRM Agent for NetWare systems

In this example, the data for the Novell NetWare server is extracted using Novell NDS
information. More than one NetWare server can be monitored from a single Managed System
with the Agent installed.

Attention: The system which will manage Novell Servers should have a user ID with
sufficient rights to perform queries to the NDS trees.

Novell NetWare discovery
The Novell NetWare servers are discovered from the Agents, which are installed on the
Windows system with the Novell NetWare client installed.


3.5 Deployment scenarios
In this section we will discuss several possible deployment scenarios.

3.5.1 Standalone Server installation with local database
The Tivoli Storage Resource Manager Server can be installed on a single system using a
local database. In this scenario, the Tivoli Storage Resource Manager Server and database
are resident on the same physical system. You can see this installation type in Figure 3-9.

IBM Tivoli SRM - Installation with local database

IDC

Direct Connect
Clients SRM Server

10 10 10 %
%% Managed
10 % 10 % Server
10 % 10 %
10 10 10 %
%%

Scheduled Batch
Reports WWW Server

SRM Database IDC

Repository

Web Conect
Clients

ibm.com/redbooks

Figure 3-9 Installation with local database

This type of installation can have certain scalability limitations as you need to take care of the
database growth and maintenance. This type of installation is available on all supported Tivoli
Storage Resource Manager Server platforms, providing the database product itself is
supported on that operating system. For example, Microsoft SQL-Server is only available for
Windows systems.

In our lab we performed this type of installation using a Windows 2000 Server system with
IBM DB2 Version 7.2 as the underlying database. The details of the installation are covered in
Chapter 4, “IBM Tivoli Storage Resource Manager installation” on page 67.

3.5.2 Standalone Server installation with remote database
In such a setup, the IBM Tivoli Storage Resource Manager server is installed on a supported
Server platform, accessing a remote database repository. In this case you can use different
platforms for the Server and the database. You can see this installation in Figure 3-10.


IBM Tivoli SRM - Installation with remote database
SRM Server

I DC

Direct Connect
Clients

10 10 10 %
%% Managed
10 % 10 % Server
10 % 10 %
10 10 10 %
%%

WWW Server
Scheduled Batch
Reports

Database
server I DC

SRM Database
Web Conect
Repository
Clients

Remote
Database

ibm.com/redbooks

Figure 3-10 Installation with remote database

As the majority of enterprise database implementations are based on centralized
management, this setup allows Tivoli Storage Resource Manager to also participate in this
architecture by using a database on the centralized server. In this case, the management of
the database will be done by the DBAs.

3.5.3 Standby Server installation for HA using remote database
A standalone installation with a remote database can give us a certain level of high
availability. Typically, enterprise database servers are already protected using high availability
(HA) solutions, so we therefore only need to protect the Tivoli Storage Resource Manager
Server itself. One possibility would be to have a standby server (for example, a testing server)
which can be enabled in the event of a Tivoli Storage Resource Manager Server failure. This
setup is shown in Figure 3-11.


IBM Tivoli SRM - possible HA setup
Tivoli SRM Server

D
I C

IDC

D
I C

Database Server
with Tivoli SRM Database

Standby Tivoli SRM Server

ibm.com/redbooks

Figure 3-11 HA setup with remote database

The standby Server has to be installed with the same settings as the primary one, and it
needs to have access to the same database. Also, whenever you make changes to the
primary Server you need to make the same changes to the secondary Server.

In the event of a primary Server failure, you would only need to change the DNS record so
that the standby Server IP address will be resolved when Agents perform queries to the Tivoli
Storage Resource Manager Server.

In our lab environment we performed an installation using Oracle 8.1.7 on Windows 2000
Server to use as a database repository. We installed the Tivoli Storage Resource Manager
Server on another two Windows 2000 server systems. The details of installation are covered
in 4.8, “Manager HA install using remote Oracle database” on page 142.

3.5.4 Windows cluster install of IBM Tivoli Storage Resource Manager Server
In this case, the Tivoli Storage Resource Manager Server is installed on two Microsoft
Windows Server systems set up in a Microsoft Cluster Services (MSCS) environment. The
systems will use SAN attached storage for the shared disk resources. The database
repository will reside on a separate server. The setup is shown in Figure 3-12.


Windows Clustered IBM Tivoli SRM Server
Primary Tivoli SRM Server
(Windows 2000 Adv. Server) Tivoli SRM Agents

I DC

IP
D
I C

IP

FC IP

IP
Database Server
with Tivoli SRM Database D
I C

(Windows 2000 Server)
Heartbeat IP

IP

SAN
FC
FC

Standby Tivoli SRM Server
(Windows 2000 Adv. Server)

FAStT 700
ibm.com/redbooks

Figure 3-12 Windows 2000 cluster setup

In this installation, the IBM Tivoli Storage Resource Manager program files are installed on a
directory on the shared storage so that they can be reachable from both servers. Doing this
automatically maintains the consistency of the configuration.

In our lab environment we performed this installation using a remote database repository on
Oracle 8.1.7 on Windows 2000. We installed IBM Tivoli Storage Resource Manager Server
on cluster of two Windows 2000 Advanced Server systems. The details of the installation are
given in 4.7, “Microsoft Cluster installation” on page 123.

3.5.5 AIX cluster installation of IBM Tivoli Storage Resource Manager Server
In this case the installation of the IBM Tivoli Storage Resource Manager server will be
performed on two AIX server systems set up in an IBM HACMP environment. Both systems
will have the Tivoli Storage Resource Manager Server installed and they will use SAN
attached storage for the shared disk resources. The database repository will reside on a
separate server. The setup is shown in Figure 3-13.


AIX clustered IBM Tivoli SRM Server
Primary IT SRM Server
(AIX 4.3.3 ML10) IT SRM Agents

IDC

IP IDC

IP

FC IP

IP
Database Server
with ITSRM Database IDC

(Windows 2000 Server)
Heartbeat IP

IP

SAN
FC
FC

Standby IT SRM Server
(AIX 4.3.3 ML10)

FAStT 700

ibm.com/redbooks

Figure 3-13 AIX cluster setup

In this installation, the IBM Tivoli Storage Resource Manager program files are installed on
the shared storage, so they are accessible from both servers. With such installation we also
maintain the consistency of the configuration. Doing this automatically maintains the
consistency of the configuration. The database repository is installed on a Windows 2000
server running IBM DB2 UDB Version 7.2.


Part 3

Part 3 Installation and
basic operations
This part discusses how to install IBM Tivoli Storage Resource Manager Server, Agent, and
Client in a number of configurations, including the basic operations of the product, as well as
the setup for high availability.


4

Chapter 4. IBM Tivoli Storage Resource
Manager installation
This chapter provides information about installing IBM Tivoli Storage Resource Manager in
various environments. We will discuss supported platforms, supported databases for the
repository, and supported databases for database monitoring. We will outline the whole
installation process up to the first startup of the application. We will also cover the CIM/OM
functionality that supports ESS reporting.


4.1 Supported operating system platforms
As IBM Tivoli Storage Resource Manager is a Java-based application, it can run under a
number of operating systems. On Figure 4.1, you can see the list of supported platforms for
the Server and Agent applications, valid at the time of writing. The first list shows OS for
which both the Server and Agent code is available. The second lists shows OS where only an
Agent is available.

Tivoli Storage Resource Manager platforms
Supported Server & Agent platforms
Windows NT 4.0 SP4 or above
Windows 2000
Windows XP
Windows Server 2003
HP-UX 11.0
Solaris 2.6, 7, 8 or 9
Red Hat Linux 6.2,7.1,7.2
AIX 4.3.3, AIX V5.1
Supported Agent platforms
Novell Netware 4.0 or above
NetApp Data ONTAP

ibm.com/redbooks

Figure 4-1 Supported operating system platforms

4.2 Supported databases for repository
Figure 4-2 shows the supported databases which can be used as the repository for Tivoli
Storage Resource Manager data. If you already have any of these installed in your enterprise,
you can use an existing database server.


Tivoli Storage Resource Manager supported
repository databases
Supported databases for repository
Microsoft SQL Server 7.0 and above
Oracle 8i or higher
Sybase12.5 or higher
IBM UDB 7.1 or higher
Cloudscape (included - not recommended for production use)

ibm.com/redbooks

Figure 4-2 Supported databases for repository

4.3 Tivoli Storage Resource Manager Server install
In this section we will outline the installation process for the Tivoli Storage Resource Manager
Server. You can see the main installation steps in Figure 4-3. Note that in all the installation
screens, logging messages are displayed at the bottom of each panel. These are not
displayed in the screen captures in this chapter.

Chapter 4. IBM Tivoli Storage Resource Manager installation 69

Tivoli Storage Resource Manager Server install

Installation
Database creation
Manager and Agent install
Configure the web access for Manager application
Start the Manager application

ibm.com/redbooks

Figure 4-3 Installation of Tivoli Storage Resource Manager Server

4.3.1 Lab environment
In our environment we used the following software setup:
Windows 2000 Server with Service Pack
IBM DB2 7.2 with Fix Pack 8
IBM Tivoli Storage Resource Manager Version 1.2

4.3.2 Database creation for repository
Before installing the Tivoli Storage Resource Manager Server, you need to create the
database for the data collected by the Server. You can either use a local database residing on
the same system as the Server itself, or a remote database residing on a different system.
These databases can be used remotely at the time of writing:
Oracle
Microsoft SQL-Server
Sybase
IBM DB2 UDB

A DB2 database can be created using DB2 Control Center or by using command line tools.
We used the DB2 Control Center wizard to create the database, and accepted defaults for the
configuration settings. In our case we created a database called ITSRMDB for this
environment.

For the database which will be used as the repository, you also need to provide the JDBC
driver. Tivoli Storage Resource Manager uses the JDBC protocol to access the database.


4.3.3 Installation of the Server code
To install the Server code in the Windows environment, run SETUP.EXE from the Windows
directory on the Tivoli Storage Resource Manager CD. Figure 4-4 shows the initial screen.

Figure 4-4 Initial installation screen

As this is a new install, the only possible selection is to install the IBM Tivoli SRM code. Click
Next to continue and the license agreement displays. Accept the license agreement and click
Next to continue. On the next window click Yes to confirm. You then select the components to
install, as shown in Figure 4-5.

Figure 4-5 Selecting product to install

As we are installing the Server code, we selected The Tivoli SRM Server and an Agent on
this machine.

Note: Whenever you install the Server code, the Agent code is also installed.


After clicking Next, the license key screen in Figure 4-6 appears.

Figure 4-6 Enter licenses

Enter in the supplied licenses, depending on what you have bought for your organization.
Click Next to continue, and the database selection screen in Figure 4-7 displays.

Figure 4-7 Selecting the database engine for the repository

Select the database server which is available. In our setup, we used DB2 UDB as the
database repository.

After selecting the database repository click Next; you will see the service account screen
shown in Figure 4-8.

Figure 4-8 Creating account for running the service


The installation program will create a system user ID which will be used for running the Tivoli
Storage Resource Manager Server service. Click OK to display the database selection
screen, as in Figure 4-9.

Figure 4-9 Selecting the database for the repository

The installation program will query the DB2 installation for existing databases and display
them. If the database you created for Tivoli Storage Resource Manager repository is listed,
you can select it by clicking on the name. Otherwise, you can type in the name under
Database Alias field. You also need to provide the database user name and password under
Connection information. Because the manager is accessing the database using JDBC you
need to specify the path to the JDBC driver in the JDBC driver.

Tip: JDBC is usually provided from the database vendor.

The JDBC driver for IBM DB2 is installed automatically with the database product itself.

Note: The setup for the other database engines will be slightly different, but you will still be
asked for the same type of information - that is, database name, user ID, and JDBC driver.

After providing all the necessary information, click Next and you will see the Repository
Creation Parameters screen shown in Figure 4-10.


Figure 4-10 Repository parameters

On this screen you can specify the database schema and tablespace name.

Tip: We recommend that you accept the defaults for these two fields. Alternatively, you can
also use the naming convention that is used in your enterprise.

If you are using DB2 as the repository, you can also choose how you will manage the
database space:
System Managed (SMS)
This option indicates that the space is managed by the OS. In this case you specify the
Container Directory, which is then managed by the system, and can grow as large as the
free space on the filesystem.

Tip: If you do not have in house database skills the System Managed approach is
recommended.

Database managed (DMS)
This option means that the space is managed by the database. In this case you need to
specify the Container Directory, Container File and Size fields. Container file
specifies a filename for the repository, and Size is the predefined space for that file. You
can later change this by using the ALTER TABLESPACE command.

Tip: We recommended that you use meaningful names for Container Directory and
Container Filer at installation. This can help you in case you need to find the container
file.

The setup for other types of databases is similar. An example using Oracle is in step 9.,
“Install the Tivoli Storage Resource Manager Server on the primary server using the same
parameters as on the standby server.’’ on page 145. An example using MS SQL-Server is in
4.3.4, “Microsoft SQL-Server as repository’’ on page 78.


After supplying all the necessary parameters click Next and you will see the parameter
screen similar to Figure 4-11.

Figure 4-11 Server setup

In this screen you need to provide the following information:
Server name: The installation program will already display the host name of the computer
that you are installing on.
Server port: The port on which the Server listens for the Agent requests.
Agent port: The port on which the Agent listens for the requests.

Note: The ports 2078 and 2077 are registered with IANA (Internet Assigned Numbers
Authority), so we recommend you use them, unless they are already in use in your
network, you can change them. If you change them on the Manager installation, you
also need to change them on each host Agent installation.

The Agent port defined here is used for the local Agent which is installed along with the
Server installation. The port which is defined is registered in the database, and because of
that, each individual Agent could possibly use a different port (however, this is not
recommended).
Agent should perform a SCAN when first brought up: With this option on, the host
Agent will perform an initial scan after installation.
Agent may run scripts sent by server (in addition to local scripts): If this option is
selected, host Agents will accept scripts sent from the Manager, otherwise, they will only
run locally stored scripts. You can get more information about scripts in 3.2.2, “Scripts’’ on
page 51.
Administrators Group: This is the name of the administrators users group. The default
value is Administrators, and can be changed if required for your organization. The
security roles are described in 4.6.1, “Security’’ on page 98.

After supplying all the needed information, click Next. You will see the NAS Discovery screen


Figure 4-12 NAS settings

In this screen you define parameters which are used for NAS discovery:
User Name - User name to login to Windows NAS devices
Password - Password for Windows NAS devices

Tip: If you use different user names on different NAS devices you can later specify a
different user name and password combination for each device.

SNMP Communities - The manager uses SNMP communities to query and identify NAS
filers (for example Network Appliance NAS devices). If you do not specify the community
name, the public community is used.

The NAS discovery process is explained in “NAS discovery” on page 56.

After specifying the required parameters click Next - you will see the Space Requirements
screen as in Figure 4-13.


Figure 4-13 Space requirements

In this screen you can choose the installation path for the Server code. Here you can also see
the required space for the installation, which can help you to select a directory location. If the
destination directory does not exist, you will be prompted for creation of it, after you click
Next. Finally, you will see the installation summary screen in Figure 4-14.

Figure 4-14 Before copying files

At this stage you can still decide to go back and change settings if necessary. Click Next to
start copying files.

If you installed the Tivoli Storage Resource Manager repository in a DB2 UDB database, the
Create Service Account window is shown in Figure 4-15. The Tivoli Storage Resource
Manager creates a new Service account and the Agent will use it when running probes and
scans against DB2 databases on the current machine.


Figure 4-15 User create for UDB account

Click Yes to create the Service account and to continue with copying the files.

After the copying is complete, you should see the messages shown in Figure 4-16.

Figure 4-16 Installation completed

In this case, after installation a Probe was executed. This happened because we enabled the
installation option Agent should perform a SCAN when first brought up.

4.3.4 Microsoft SQL-Server as repository
This section shows installing using MS SQL-Server as the repository.

If you select MS SQL-Server as the database repository during the installation process, you
will see a screen like Figure 4-17.


Figure 4-17 Selecting Microsoft SQL Server

Select MS SQL Server and click Next to continue. Figure 4-18 displays.

Figure 4-18 Microsoft SQL-Server parameters

Type in the required parameters:
Host - The system with Microsoft SQL-Server installed
Port - The port number. The default number 1433 is selected by default
SQL Server DBA user - The database administrator user ID
Password - The password for database administrator user ID
JDBC driver - The path to the JDBC driver. You can find information how to obtain
Microsoft SQL driver in “Configuration: General settings” on page 108.

Click Next and the Repository Creation Parameters screen displays (Figure 4-19).


Figure 4-19 Repository parameters

Here you specify the name and location of the database components. Click Next and the
installation process continues as in Figure 4-11 on page 75.

4.3.5 Installing Cloudscape as a test database
This section shows installing using the Cloudscape database as a repository. The
Cloudscape database is recommended for test and demonstration purposes only (not
production) as it is limited on performance. The Cloudscape product provides a complete
Java-based database.

If you select Cloudscape as the database repository when installing, you will see the screen
like Figure 4-20.

Figure 4-20 Cloudscape selection to install

Click Next and the installation process will continue. The pop-up warning in Figure 4-21
advises you not to use the database in a production environment.


Figure 4-21 Cloudscape warning for production use.

Click OK and the installation process continues as from Figure 4-11 on page 75.

4.3.6 Configuration for Web access
The client GUI for management and data collection is automatically installed with the Server
code. With this GUI, you can perform all the Storage Resource Management operations from
the Server system.

You can also access the Server system over the network and perform administration tasks
from a remote workstation. The remote administration console is a Java based applet, which
can be run locally or remotely by downloading it from the Web server.

Remote administration can be done in two ways:
Installing the administration GUI on remote workstations as per the instructions in 4.3.7,
“Installation of the GUI code’’ on page 87
Setting up the Web access for remote workstations

In our example we set up remote Web access using Microsoft IIS (Internet Information
Server) which is built into Windows 2000. We did the following:
1. Select Start -> Administrative Tools -> Internet Information Services.
2. Right-click Default Web Site and select New -> Virtual Directory (Figure 4-22).


Figure 4-22 Creating virtual Web directory

3. The Virtual Directory Creation Wizard displays. Click Next to display the Virtual
Directory Alias screen (Figure 4-23).

Figure 4-23 Defining the alias name

4. Enter an alias name which will be used as the access point for Web access (tsrm in our
example). Next, the Web Site Content Directory screen displays (Figure 4-24).


Figure 4-24 Defining the directory for Web access files

5. Specify the directory where the Web access files for Tivoli Storage Resource Manager are
located. They will be in the GUI directory under the installation directory, C:Program
FilesTivoliTSRMgui in our example. Click Next and the Access Permissions screen
(shown in Figure 4-25) displays.

Figure 4-25 Access permissions for virtual directory

6. In this dialog you can set up access permissions for the files in the virtual Web directory.

Tip: It is recommended that you use default values.

Click Next and Finish to complete the setup.


Now you can run the administrative interface remotely by pointing your Web browser to the
URL http://<hostname>/tsrm/TivoliSRM.html, as shown in Figure 4-26.

Figure 4-26 IBM Tivoli Storage Resource Manager main Web window

The applet is downloaded to your system and you need to grant the access (Figure 4-27).

Figure 4-27 Granting permission for the applet

After granting the session, you will see the administrator GUI main screen as in Figure 4-28.


Figure 4-28 Main administration GUI screen

Setting the default Web page
You can also set the default Web page for the directory where the Web files for Tivoli Storage
Resource Manager are located. This means you need only to type in the directory name as
the http address to access the IBM Tivoli Storage Resource Manager over a Web connection,
in our example http://lochness/tsrm/ To do this with IIS, from the IIS administrative panel,
right-click in the definition of the previously created Web directory as shown in Figure 4-29.


Figure 4-29 Opening properties for the tsrm Web directory

The Properties page displays, shown in Figure 4-30.

Figure 4-30 Tsrm properties


Click the Documents tab as shown in Figure 4-31.

Figure 4-31 Document properties

Click Add and add the TivoliSRM.html document. Click OK to save the changes.

Now you can access the Tivoli Storage Resource Manager Server over Web simply by typing
in the address of the Web directory: http://lochness/tsrm/

Congratulations! You have just installed, configured, and started Tivoli Storage Resource
Manager.

4.3.7 Installation of the GUI code
The GUI code is the same as that used for browser remote access as described in 4.3.6,
“Configuration for Web access’’ on page 81. For a Windows installation, run SETUP.EXE from
the Windows directory on the install CD. The main installation screen displays (Figure 4-4 on
page 71).

Click Next to continue. Accept the license terms, click Next to continue, and you will see the
installation selection screen in Figure 4-32.


Figure 4-32 Selecting GUI to install

As we are installing the GUI, select The GUI for reporting and click Next. The Parameters
screen displays, as shown in Figure 4-33.

Figure 4-33 Server name

Enter the Server hostname or IP address and the Server port (as shown in Figure 4-11 on
page 75). Click Next - you will see the Space Requirements screen, as shown in Figure 4-34.


Figure 4-34 Size and directory

Here you can see the size of installed code and selected installation directory. We
recommend you keep the default settings. Click Next to complete the installation.

4.3.8 Installing the Server code on UNIX
To install the Server code on UNIX, run ./setup.sh -g from the appropriate directory on the
CD. For example, for Linux, run the script from the Linux directory. The installation GUI is the
same as in Windows, described in 4.3.3, “Installation of the Server code’’ on page 71.

4.4 Installing the Agent code
This section covers installing the Tivoli Storage Resource Manager Agents.

Windows Agent
To install the Agent code for Windows, run SETUP.EXE from the Windows directory on the Tivoli
Storage Resource Manager CD. The initial screen displays, as in Figure 4-4 on page 71.

Click Next and accept the license. You will see the installation selection screen shown in
Figure 4-35.


Figure 4-35 Agent install selection

Select An Agent on this machine and click Next. You will see the Parameters screen, as

Figure 4-36 Agent parameters setup

The Server Port should match the entry from the Server installation - 2078 in our case, as
shown in Figure 4-11 on page 75, or the Agent will not be able to connect to the Server. The
Server Name should be the hostname (or IP address) of the Tivoli Storage Resource Manager
Server. The Agent Port can be any free port on the Agent system. You should use the same
port for all Agents as this helps simplify management.

If you do not want to automatically perform a Scan after the Agent is installed, deselect the
option Agent should perform a SCAN when first brought up (gathers default
statistics).

If for some reason you do not want to allow Agents to accept scripts from the server, deselect
Agent may run scripts sent by server (in addition to local scripts).


Tip: You can change how the Agent will handle scripts later by editing the config file and
restarting the Agent.

After supplying all the parameters click Next. The installation program will check the
connection to the Server. The Space Requirements screen will display, as shown in
Figure 4-37.

Figure 4-37 Space requirements

Here you can see the required space for installation and specify the installation directory. If
the directory does not exists you need to confirm its creation. Click Next, then confirm the
settings on the next screen. Select Next to start copying files. After the installation is
complete, the Agent will automatically start.

If you are installing on an Agent with a NetWare client, you will be prompted to create a local
account for the Agent (as shown in Figure 4-38) before the Agent is started after installation.

Figure 4-38 Novell logon ID creation

This account can only be created if you are logged into the Novell NDS with sufficient
privilege.

UNIX Agent
Install the UNIX Agent by running ./setup.sh from the appropriate directory. Our example is
a Linux Agent. If you execute the script without parameters, the help is displayed as shown in
Example 4-1.


Example 4-1 Running UNIX Agent installation script
Linux-1:/tmp/SRM/linux # ./setup.sh
To run the GUI install:
setup.sh -g

To run a quick (agent-only) install:
setup.sh -s <server-host> [-d <dest-dir>] [-p <server-port>]
[-q <agent-port>] [-x] [-n] [-l [o][r]]
<dest-dir> defaults to /usr/Tivoli/TSRM or /opt/Tivoli/TSRM
<server-port> defaults to 2078
<agent-port> defaults to 2077
-x prevents agent from running scripts sent from server
-n prevents agent from running initial scan
-l identifies the products that will be licensed on this agent
Valid product codes are: o - Tivoli SRM
r - Tivoli SRM for Databases
Linux-1:/tmp/SRM/linux # ./setup.sh -s bonnie -d /opt/tivoli/TSRM -p 2078 -q 2077 -l o

There are two ways to install a UNIX Agent:
Graphical - using ./setup.sh -g The installation procedure is the same as for the
Windows Agent, shown in “Windows Agent” on page 89.
Text (quick) mode - using ./setup.sh and specifying parameters on the command line

To install the Agent using the quick method, you need to supply the following parameters:
-s servername - The Server name or IP address
-d directory - The installation directory. The usual installation places are in /opt and /usr.
Specify the full path, for example /opt/tivoli/ITSRM.
-p serverport - The Server port
-q agentport - The Agent port

Note: The d, p, and q parameters can be omitted, if so, these defaults will be used:
d - /opt/tivoli/TSRM or /usr/tivoli/TSRM, depending on the platform
p - 2078
q - 2077

-l products - The products which you want to be active on this Agent:
– o - Base component
– r - Oracle Agent
– m - Microsoft SQL-Server Agent
– s - Sybase Agent

In our example we executed the following command:

./setup.sh -s bonnie -d /opt/tivoli/TSRM -p 2078 -q 2077 -l

During installation you will see messages similar to those shown in Example 4-2.

Example 4-2 Installation of the UNIX Agent
Linux-1:/tmp/SRM/linux # ./setup.sh -s bonnie -d /opt/tivoli/TSRM -p 2078 -q 2077 -l o
06-09 10:44:04 INS0000I: IBM Tivoli SRM Install
06-09 10:44:05 INS0058I: Port 2077 for the Agent is available
06-09 10:44:05 INS0105I: Transmitting agent licensing data to server...


06-09 10:44:05 INS1020I: Creating directory /opt/tivoli/TSRM
06-09 10:44:05 INS1020I: Creating directory /etc/Tivoli/TSRM
06-09 10:44:05 INS1020I: Creating directory /etc/Tivoli/TSRM/lock
06-09 10:44:05 INS1020I: Creating directory /opt/tivoli/TSRM/scripts
06-09 10:44:05 INS1020I: Creating directory /opt/tivoli/TSRM/config/
06-09 10:44:05 INS2092I: /opt/tivoli/TSRM/config/agent.config config file created.
06-09 10:44:05 INS2092I: /opt/tivoli/TSRM/config/../PROBE_ME config file created.
06-09 10:44:05 INS1020I: Creating directory /opt/tivoli/TSRM/java
06-09 10:44:07 INS1020I: Creating directory /opt/tivoli/TSRM/log
06-09 10:44:07 INS1020I: Creating directory /opt/tivoli/TSRM/agent
06-09 10:44:07 INS1020I: Creating directory /opt/tivoli/TSRM/install
06-09 10:44:07 INS2089I: IBM Tivoli SRM Agent startup scripts created
06-09 10:44:11 INS1070I: IBM Tivoli SRM Agent started
06-09 10:44:11 INS1077I: Waiting for agent...
06-09 10:44:16 INS1075I: Agent registered.
06-09 10:44:17 INS1078I: Waiting for Probe to complete...
06-09 10:44:25 INS1079I: Computer probed.
Linux-1:/tmp/SRM/linux #

For a Linux Agent, the installation process will create an auto-start entry in /etc/init.d and link
to this entry in runlevel 3 and 5. Other UNIX variants will create a similar entry in the
appropriate file to enable automatic start of the Agent on system start.

If for some reason, the Agent no longer appears in the Agent list, or it is marked as
Unreachable, and the network connection is working, you can force the registration process
by creating an empty file called PROBE_ME in the Agent installation directory. For example, on
Windows use C:Program FilesTivoliTSRMPROBE_ME. If the Agent showed as
Unreachable, you should first delete it from the Agent list.

Note: If you delete or reregister an Agent you will lose all historical data for this Agent.

4.5 Applying maintenance to Tivoli Storage Resource Manager
In the current release of the product, you apply maintenance by running the installation
program. Follow these steps to apply maintenance:
1. On the welcome screen (Figure 4-39) select Apply maintenance to IBM Tivoli SRM.


Figure 4-39 Selecting to apply the maintenance

2. Click Next, you will see the maintenance selection screen similar to Figure 4-40.

Figure 4-40 Product maintenance selection

3. In this case, we are upgrading the Server. Select The IBM Tivoli SRM Server and all of
its Agents and click Next.
If the Server being upgraded uses IBM DB2 as the repository database, you will see the
screen shown in Figure 4-41; otherwise, you will go directly to the confirmation screen in
the next step.


Figure 4-41 DB2 admin user ID and password

4. Here you have to enter the DB2 administrator user ID and password. Click Next and you
will see the confirmation screen. Click Next to start the maintenance.
5. After all the upgraded files are copied, the summary screen (Figure 4-42) displays.

Figure 4-42 Maintenance finished

Check for errors and click Done to finish the maintenance process.

After performing maintenance on the Server system, the Server will automatically upgrade all
the Agents.

If for any reason you need to force an upgrade of the Agents with the same version currently
available, you need to create an empty file with the name UPGRADE_AGENTS in the Server
installation directory. For example, in Windows C:Program FilesTivoliTRSM This will force
an upgrade.


Maintenance can also be performed separately for the Agent and GUI installation by selecting
the other options on Figure 4-40.

4.5.1 Planned upgrade installation for Agents
IBM Tivoli Storage Resource Manager Version 1.2 can now update agents connected to the
Server. You can define a job for these actions, as shown in Figure 4-43. We selected the
Agent on BANDA to upgrade by highlighting it and clicking the circled arrow button.

Figure 4-43 Select Agent to upgrade

You can also choose a time to perform the upgrade (When to Upgrade tab in Figure 4-44). We
chose to perform the upgrade immediately.


Figure 4-44 Schedule agent upgrade

Under Options, (Figure 4-45) you can force a reinstall if the Agent is already on this level.

Figure 4-45 Force upgrade on Agent


On the Alert tab, you can define actions in the event of an error. We selected to send an event
to the TEC console by checking TEC Event.

Figure 4-46 Alert selection for failed Agent upgrade.

After saving the job, the scheduler will run it at the selected time (immediately in this case).
Each Agent will be stopped, upgraded, and restarted.

4.6 Basic administrative tasks
This section describes some basic administrative tasks for Tivoli Storage Resource Manager.

4.6.1 Security
To log in to the Tivoli Storage Resource Manager Server, you can use any local user ID on the
Server system. During installation you can specify the administration group (shown in
Figure 4-11 on page 75). The members of this group will be able to perform all tasks using the
GUI interface. We recommend creating a special group for Tivoli Storage Resource Manager
administrators. The group name can be changed after installation by editing the server.config
in the config directory and restarting the Server services. An example of the file is shown in
Example 4-3.

Example 4-3 Tivoli Storage Resource Manager server.config file
[controller]
name="palau"
port=2078
maxConnections=500
routerThreads=1
serviceThreads=2


agentErrorLimit=3
adminGroup="Administrators"
commEncrypted=0
[logging]
logsKept=5
messagesPerLog=100000
[repository]
driver=oracle.jdbc.driver.OracleDriver
url="jdbc:oracle:thin:@gallium:1521:ITSRMREM"
user=TivoliSRM
connectionPool=10
[service]
name=TStorm.server.svp.GuiSvp
[service]
name=TStorm.server.svp.AgentSvp
[service]
name=scheduler.Scheduler

The line you need to change is adminGroup="Administrators"

All other local users on the system can log in to the Server, but only with read-only access to
administrative tasks.

Windows domain users can also access the Server, provided they are members of local
groups.

4.6.2 Administration
When you start the Tivoli Storage Resource Manager GUI either locally or using the Web
browser, you will see the logon window as shown in Figure 4-47.

Figure 4-47 Server login

Enter the user ID and password and click OK. You will see the main screen (Figure 4-48).


Figure 4-48 Main panel

As shown on the left side, the interface uses a tree-oriented navigation. Under the IBM Tivoli
SRM entry are four main sections:
Administrative Services - Here you can administer the Tivoli Storage Resource Manager
Server. We will cover these operations in this section.
IBM Tivoli SRM - Here you can manage and report on Agent systems. More information
on reporting is in Chapter 6, “Reporting” on page 247.
IBM Tivoli SRM for Databases - Here you can manage and report on database
applications on Agent systems. More information on database reporting is in Chapter 6,
“Reporting” on page 247.
IBM Tivoli SRM for Chargeback- Here you perform charge back functions. More
information on charge back is given Chapter 6, “Reporting” on page 247.

Tip: You can expand or collapse a tree or sub tree by clicking on the circle on the left
side of the tree name as highlighted in red in Figure 4-48.

In the following sections we will explain the functions found under Administrative Services.
More detailed information is in the manual IBM Tivoli Storage Resource Manager
Configuration and Getting Started Guide, SC32-9067.

The sub trees available in the Administrative Services are:
Services, to view and control various services that run on the Server
Agents, to view and control various Agent components on the Managed Systems


Configuration, to customize operational characteristics of IBM Tivoli Storage Resource
Manager. The settings are stored in the repository database and control operations for all
users.

Note: The options defined in Configuration under Administrative Services are
different from the User Preferences accessible from the main menu (Preferences ->
Edit General...). User Preferences are stored for each user separately and apply only
to the logged in user, whereas the options under Configuration apply globally to all
users.

4.6.3 Administration: Navigation
From anywhere in the navigation tree, you can access the menu entries and tool bar icons.

Menus
The menus are at the top of the screen, as in Figure 4-49.

Figure 4-49 Menus in GUI

The following menus and submenus are available:
File
– Save - Save the changes to the current object.
– Save as - Save current object under different name.
– Export data - Export data to other formats.
– Close - Close the current window.
– Print - Print current data in the content pane; you can also save as a PDF or HTML file.
– Print Tree - Print the expanded contents of the functions tree or save as a PDF or
HTML file.
– Refresh Alerts - Refresh the Alerts from repository.
– Exit - End the session.
View
– Tree - Remove and add the tree display to the screen.
– Current Page in Tree - Display the highlighted node on the tree that was responsible for
displaying the data on the content pane.
Connection
– New Connection - Create a new connection to the Tivoli Storage Resource Manager
Server.
Preferences
– Look and Feel - change between Windows, CDE/Motif or Metal interface.
– Edit General
• Panel Retention - Number of windows which can be accessed in the history
• On login - If and how to show active Alerts when you log in
• Initial Reporting Tab to Display - What tab will be displayed when you first generate
and view a report.
• Advanced Options - The unit of measurement used in reports.


Window
– Close all Windows without changes - Close windows having no updates.
– Show dashboard - Shown the dashboard
– Show Window List - Shows window list, each name has the icon indicating:
• Green circle - No changes were made.
• Red circle - Changes were made, but not saved yet.
• Green arrow - Current window displayed, no changes made.
• Red arrow - Current windows displayed, changes were made, but not saved.
Help
– Help Directory - Online help system
– Help for Displayed Panel - Help for the current window
– About - About the product

Tool Bar
The Tivoli Storage Resource Manager Tool Bar is shown in Figure 4-50.

Back Forward Save Print Cancel Edit Stop Current
Session Server Request

Figure 4-50 Tool Bar functions

The available functions are:
Back - Go to previous open window.
Forward - Go to next open window.
Save - Save current edited object.
Print - Print the currently displayed data.
Cancel Edit Session - Cancel the changes in the current window.
Stop Current Server Request - This button becomes red when the Server is processing
a request, and allows the action to be cancelled.

Tip: Do not forget to save changes made to an object. The interface will warn you if you
try to close a window with unsaved data.

4.6.4 Administrative Services: Services
Expanding the Services tree gives the following components:
Server, information about the IBM Tivoli Storage Resource Manager Server
Scheduler, information about the Scheduler component
TivoliSRM-Agent, about the Agent component
TivoliSRM-GUI, information about the GUI component

Each component indicates its status by color:


Green - Active session that is operating normally.
Red - Session that is currently not active.

If you right-click a service component you will get the menu shown in Figure 4-51.

Figure 4-51 Right-click menu on Services tree components

Except for Broadcast, which is only available on the Server node, all other options are
available on all nodes:
View Log - View log of the component
Broadcast - Inform Agents on Server location
Shutdown - Shut down the component:
– Normal - Clean shutdown, allowing all processing to finish
– Immediate - Quick shutdown
– Abort - Shut down and stop whatever is in process

4.6.5 Administrative Services: Agents
Expanding Agents under Administrative Services, shows all the registered Agents. Three
Agents are shown in Figure 4-48 on page 100:

Each Agent indicates its status by color:
Green - Active session that is operating normally.
Red - Session that is currently not active.
Yellow - Agent is unreachable and not responding to the Server.
Light Gray - Agent is active but needs to be upgraded. The Server will not receive any
information until the Agent is upgraded.

When you click on a particular Agent, you will see the screen similar to Figure 4-52.


Figure 4-52 Agent General view

This shows general information about the Agent (status, port, address, last update, time zone,
connection errors).The Details screen is shown in Figure 4-53.


Figure 4-53 Agent Details view

Here you can see details about the Agent (name of the Agent and Host, date and time when it
was started, uptime, disk space allocated to virtual memory size - VM, manufacturer and OS
of the Agent system, number of jobs scheduled to run on the Agent). The Jobs screen is


Figure 4-54 Agent Jobs view

This views shows information about any jobs currently running on the Agent. The example
shows that the Scan job is running.

If you right-click the Agent you will get the menu shown in Figure 4-55.

Figure 4-55 Right-click menu on Agent

You can perform the following actions:
View Log - View the log of the Agent as shown in Figure 4-56.


Figure 4-56 Agent log

Read Config - Agent will re-read the config file.
Check - Check the Agent. If the Agent needs to be upgraded, clicking this button will
automatically install the required upgrades.
Shutdown - Shut down the component:
– Normal - Clean shutdown, letting all processing to finish
– Immediate - Quick shutdown
– Abort - Shut down and stop whatever is in process
Disable - Disable the Agent. The Agent will still listen for connections, but will not execute
any tasks except re-enabling the Agent.
Delete - Erase the Agent from the Server repository and stop the Agent service. You can
re-enable the Agent by re-starting the Agent service. The Agent will appear as a new
install.

Attention: By deleting the Agent you will lose all (including historical) data about it from
the repository.

4.6.6 Administrative Services: Configuration
The configuration tree provides control of the operational characteristics of Tivoli Storage
Resource Manager. All these settings are stored in the database repository and are
applicable for all users. After expanding the tree as shown in Figure 4-48 on page 100, you
will see these sub trees:
General - Define general configuration settings for the Server.
IBM Tivoli SRM - Customize the settings for IBM Tivoli Storage Resource Manager main
component.


IBM Tivoli SRM for Databases - Customize the settings for Tivoli Storage Resource
Manager for Databases.

Configuration: General settings
Under general settings you can do the following:

License Keys
This option is for administering Tivoli Storage Resource Manager license keys. Clicking
License Keys shows a screen like Figure 4-57. In Tivoli Storage Resource Manager V1.2,
the license model has been simplified to only three license types.

Figure 4-57 License Keys editor

Licensing requirements are explained in the manual IBM Tivoli Storage Resource Manager
Configuration and Getting Started Guide, SC32-9067. Here we will focus on the operations
around the licenses. A new license can be added by clicking Add, and entering the
appropriate license key as shown in Figure 4-58.

Figure 4-58 Adding new license key

To change a license, select the product name and click Edit; Figure 4-58 displays for you to
enter the new license.


Licenses can be deleted by selecting the product name and clicking Delete.

Click the icon on the left side of a particular product name (as circled in Figure 4-57) to
perform other specific licensing actions:
IBM Tivoli SRM
The licensing screen for Tivoli Storage Resource Manager is shown in Figure 4-59.

Figure 4-59 Licenses for IBM Tivoli SRM

You can see the systems with installed Agents, which are licensed to use the product. To
select an Agent, click in the square in the Licensed column as shown in Figure 4-59.
If you will scan Novell NetWare servers, they have to be licensed as shown in Figure 4-60.


Figure 4-60 Licensing Novell NetWare Agent

To license a discovered NAS system, select it as shown in Figure 4-61.

Figure 4-61 Licenses for Tivoli Storage Resource Manager for NAS

All the NAS devices are displayed, and you can select those which are to be licensed. The
Filer Logins tab is shown in Figure 4-62.


Figure 4-62 NAS devices logins

Here you can update the default login and password for NAS devices, which were defined
during installation (Figure 4-12 on page 76). Also, you can define a specific login for each
NAS device by selecting the row or rows, and clicking Set login per row or Set login for
all selected rows. The window for entering the login and password looks similar to
Figure 4-63.

Figure 4-63 Login definition

Here you enter the specific login ID and password for the NAS appliance.
IBM Tivoli SRM for Databases
The licensing process for all database components (MS SQL-Server, Oracle, Sybase,
UDB) is similar. Our example shows the setup for MS SQL-Server. After opening you
will see a screen similar to Figure 4-64.


Figure 4-64 Licenses for Tivoli Storage Resource Manager for Databases

From the list of Agents, select those with SQL-Server databases installed, which you want
to monitor, as shown for CLYDE in Figure 4-64. To successfully scan the database, you
have to provide a login name and password for each instance. This can be done in the
RDBMS Logins tab as in Figure 4-65.


Figure 4-65 RDBMS Logins

You can define a new RDBMS login by clicking Add New as shown in Figure 4-66.

Figure 4-66 Defining RDBMS Login

Enter the necessary data:
– Instance - The name of the instance
– User - Login ID for the instance
– Password - Password for the instance
– Port - Port where database is listening
– JDBC Driver - Path to the JDBC driver for the database


Tip: A free JDBC driver for Microsoft SQL-Server can be downloaded from:
http://msdn.microsoft.com/library/default.asp?url=/downloads/list/sqlserver.asp

Commercial drivers are also available for SQL-Server. An example is from Altanav Inc.,
which is available at:
http://www.atinav.com/products/aveconnect/MSSQLserver/aveconnect2.htm

A free copy of JDBC for Oracle is provided with the installation package, or it can be
downloaded from:
http://otn.oracle.com/software/tech/java/sqlj_jdbc/content.html

A free copy of JDBC for Sybase can be downloaded from:
http://www.sybase.com/products/middleware/jconnectforjdbc

Alert Disposition
This option defines how the Alerts are generated when a corresponding event is discovered.
This screen is shown in Figure 4-67.

Figure 4-67 Alert Disposition screen

You can specify these parameters:
SNMP
– Community - The name of the SNMP community for sending traps
– Host - The system (event manager) which will receive the traps
– Port - The port on which traps will be sent (the standard port is 162)


TEC
– TEC Server for sending traps to. The system (TEC) which will receive the traps
– TEC Port, which traps will be sent (the standard port is 5529)
E-mail
– Mail Server - The mail server which will be used for sending the e-mail.
– Mail Port - The port used for sending the mail to the mail server.
– Default Domain - Default domain to be used for sending the e-mail.
– Return To - The return address for undeliverable e-mail.
– Reply To - The address to use when will replying to an Alert-triggered e-mail.
Alert Log Disposition
– Delete Alert Log Records older than how long the Alert Log files will be kept.

Log-File Retention
This option defines how long to keep the log files, as shown in Figure 4-68.

Figure 4-68 Log File Retention

The possible parameters are:
Keep at most n runs of each schedule - The numbers of runs you want to keep for each
scheduled job.
Keep at most n day’s worth of log-files, regardless of schedule - The number of days
you want to keep the log files. Every log file older that this will be deleted.
Quota Email Address Rules - Here you specify the rules for generating the e-mail
address of Quota violators based on login name, first name, and/or last name as they are
registered within the OS. The Quota Email Address Rules screen is shown in Figure 4-69.


Figure 4-69 Filters for Quota Email

Depending on the OS, Tivoli Storage Resource Manager obtains the user names from:
Windows 2000 - Full name field, from LDAP
Windows NT - Full name field, from domain-level security database
NetWare - Surname and Given name fields, from LDAP
UNIX - User description from the password file

The name is stored in the repository database and then specific algorithms are used to
extract the names for building e-mail address rules. In the example shown in Figure 4-69, the
last name plus the first character of the first name will be used to create the name. When
e-mail is sent the default domain defined in Alert Disposition (see “Alert Disposition” on
page 114) will be appended.

More explanation on setting up the rules is in the manual IBM Tivoli Storage Resource
Manager Configuration and Getting Started Guide, SC32-9067.

Scan/Probe Agent Administration
Here you assign the Agents which will perform scanning and probing of NAS filesystems and
the volumes and filesystems of an NDS tree. The Scan/Probe Agent Administration screen is


Figure 4-70 Agent selection for NAS and NDS

The following information is displayed:
Licensed NetWare servers
NetWare volumes discovered by discovery jobs
Discovered NAS filesystems

This information is gathered during the discovery process on the Agents accessing NAS
devices and Novell NetWare servers.

The Agent systems with access to the NAS or NetWare volumes and filesystems will be
displayed here along with information on which volume or filesystem(s) they are using.

Important: If the discovery jobs are not run against NDS trees and NAS devices, the
volumes and filesystems will not be displayed.

To change the Agent that will scan the volume and filesystem, select the desired row(s) and
click Set agent per row or Set agents for all selected rows. You will see the window shown
in Figure 4-71 for NAS Agents, or the window shown in Figure 4-72 for the Novell NetWare
Agents.


Figure 4-71 Defining the NAS Agent for Scan/Probe

Figure 4-72 Defining the Novell NetWare Agent for Scan/Probe

In this window you specify which Agent will scan the selected volume or filesystem.

History Aggregator
This option specifies when to run the History Aggregation job as shown in Figure 4-73. This
job runs within the Tivoli Storage Resource Manager Server and aggregates information in
the repository for reporting purposes.


Figure 4-73 History Aggregator definitions

Two options can be set:
When to Run - The time and date to run the job
Alert - Actions to perform if the job fails. More information on Alerts is in 5.2, “OS Alerts’’
on page 189.

Configuration: IBM Tivoli SRM
Under IBM Tivoli SRM settings you can do the following:

NetWare Tree Logins
Assign the login ID and password for each Novell Directory Services (NDS) tree discovered
by Tivoli Storage Resource Manager Agents. The screen is shown in Figure 4-74.

Figure 4-74 NetWare Tree Login Administration

Select the desired Tree Name and click Edit, as shown in Figure 4-75.


Figure 4-75 Novell Tree Login

Specify the login ID and the password for the NDS tree.

Tip: The login ID must be specified with the full context name.

Tivoli Storage Resource Manager uses this login ID to access the NDS trees and gather
information about the NetWare servers and volumes in those trees.

Important: The assigned login ID must have permission to enumerate the volumes within
the NetWare servers on that tree.

Resource History Retention
This panel (Figure 4-76) defines the period that collected historical data will be kept.

Figure 4-76 History retention: Tivoli Storage Resource Manager


The retention period is specified individually for the following data types:
Directories
Filesystems
Pings
Computer uptime
Disks

Selecting No History turns off history keeping.

Removed Resource Retention
This panel (Figure 4-77) specifies how long to keep information that is related to entities that
have been removed or deleted from an Agent.

Figure 4-77 Removed Resource Retention: Tivoli Storage Resource Manager

You can define how long to retain information for these removed entities:
Directories
Filesystems
Disks

Configuration: IBM Tivoli SRM for Databases
Under the IBM Tivoli SRM for Databases settings, you can do the following:

Resource History Retention
This panel (Figure 4-78) defines the period for which collected historical data on databases
will be kept.


Figure 4-78 History retention: Tivoli Storage Resource Manager for Databases

Here you define the retention period for the following data:
Database-Tablespaces
Tables

Clicking No History turns off history keeping.

Removed Resource Retention
This panel (Figure 4-79) specifies how long to keep information that is related to entities that
have been removed or deleted from an Agent.


Figure 4-79 Removed Resource Retention: Tivoli Storage Resource Manager for Databases

You can define how long to retain information on these removed entities:
Databases-Tablespaces
Tables

4.7 Microsoft Cluster installation
In this section we will outline how to install Tivoli Storage Resource Manager in a Microsoft
Cluster (MSCS) environment using IBM DB2 as a local repository for the database. We will
provide step by step instructions to:
Install and configure Microsoft Cluster server on clustered systems
Install and configure DB2 on clustered systems
Install and configure the Tivoli Storage Resource Manager Server on clustered systems

Our environment uses the following setup:
Two Windows 2000 Advanced servers with Fix Pack 2 installed, members of the same
domain. The primary system is DIOMEDE, with SENEGAL as the other cluster member.

Important: The clustered systems must be members of the same domain. They can
also be domain controllers.

One Fibre Channel HBA in each of the systems attached to the SAN
IBM FAStT Storage system with two 10GB LUNs FC-attached to the hosts. The LUNs
were configured to be seen by both systems. The first LUN was used as the quorum disk
and the second LUN was used as the data disk for DB2 and Tivoli Storage Resource
Manager.
IBM DB2 UDB Version 7.2 Service Pack 7


IBM Tivoli Storage Resource Manager Version 1.1

The environment is shown in Figure 4-80.

Tivoli Storage Resource Manager MSCS install
Primary Server DIOMEDE
MSCS
IBM DB2 7.2 fp 7
IBM Tivoli SRM 1.1 IT SRM Agents

IP IDC

FC

FC
SAN IP

IDC

Heartbeat IP
LUN0 - Disk E:
Data (Quorum)

FAStT 700 IP
LUN1 - Disk F:
Data (DB2 & ITSRM)

FC

Standby Server SENEGAL
MSCS
IBM DB2 7.2 fp 7
IBM Tivoli SRM 1.1

ibm.com/redbooks

Figure 4-80 Cluster installation

4.7.1 Microsoft Cluster initial setup
We followed these steps to implement the Tivoli Storage Resource Manager cluster:
1. Install Windows 2000 Advanced server on both systems.
2. Prepare two shared LUNs on storage accessible from both systems.
3. Check both systems can see the disks. Make sure that the disks are Basic type.
4. Create the partitions, format the disks using NTFS filesystem, and assign drive letters to
both disks. In our example the first disk was E: and the second disk was F:.
5. Check that the disks are visible from the second system with the same drive letters. If the
disks cannot be seen, restart the system.
6. Each system requires two network adapters. We recommend that one from each system
is connected through a dedicated link, for example, with an Ethernet crossover cable.
These adapters will be used for the heartbeat. Both adapters must use static IP
addresses.

Tip: We recommend using private subnet addresses for the heartbeat adapters.

7. Obtain two additional IP addresses, to be used for the cluster setup.


8. Start the cluster installation and configuration on the first node, in our example DIOMEDE,
by accessing Add/Remove Windows Components in Control Panel -> Add/Remove
Programs. Select Cluster Service and click Next. Figure 4-81 displays the Configuration
Wizard.

Figure 4-81 Cluster Wizard Welcome panel

9. Click Next. The Hardware Configuration screen displays (Figure 4-82).

Figure 4-82 HCL requirements

10.Accept the HCL (Hardware Compatibility List) requirements. Figure 4-83 displays.


Figure 4-83 Node selection

11.As we are installing on the first node, select The first node in the cluster. You will see the
Cluster Name screen, shown in Figure 4-84.

Figure 4-84 Cluster name

12.Enter the cluster name, in our example ITSOSRMCL, and click Next. The Account Selection
screen displays (Figure 4-85).


Figure 4-85 Cluster user ID

13.Enter the user ID and password that will be used by the Cluster service. This account must
be a domain account. Click Next. The Managed Disks screen displays (Figure 4-86).

Figure 4-86 Shared disks

14.Select the shared disks to be used for the cluster. You need to select at least one for the
Quorum disk. You can add more shared disks later. In our example, we chose Disk E: for
the Quorum disk. Next, the Cluster File Storage window displays, as shown in Figure 4-87.


Figure 4-87 Quorum disk

15.Select which shared disk will be used for Quorum, Disk E: in our example. Click Next to
display the Configure Cluster Networks screen, as in Figure 4-88.

Figure 4-88 Network setup

16.The next screens define the networks to be used in the cluster setup. First is the Network
Connections screen, shown in Figure 4-89.


Figure 4-89 Private network

17.In this panel you select roles for each network defined on the systems. At least two
networks are required, they can have the following roles:
– Client access - The network will be used for client access.
– Internal cluster communication only - The network will be used for cluster heartbeat.
– All communications - The network will be used for both communication methods
mentioned above.
In our example we selected our Local Area Connection network for Internal cluster
communication only.
Figure 4-90 shows our second Network configuration.

Figure 4-90 Public network


18.In this window we selected to use Local Area Connection 2 for All communications

Tip: We recommend defining the All communications mode for the second adapter if
you have only two network adapters in the system.

After completing the network connection setup, click Next to continue to the Internal
Cluster Communication screen shown in Figure 4-91.

Figure 4-91 Network priority for internal cluster communication

19.If more than one network was defined for cluster communication, the priority order for
them must be specified. In our example, we specified one network for private
communication and another network for all communications, therefore, we will define the
private network as the top priority network used for inter-cluster communication. If this
network fails, the all communications network will be used for inter-cluster communication
as well as client access.
The Cluster IP address screen comes next, shown in Figure 4-92.


Figure 4-92 Cluster IP address

20.Here you define the Cluster IP Address to be used by clients to access cluster resources.
If additional networks were defined for public or all communications access, you need to
also specify the network to which this address will be bound. In our example we used the
Local Area Connection 2 network.
After defining the address click Next to continue, and Finish to end the installation and
configuration on the first node.
21.Start the cluster installation and configuration on the second node, (SENEGAL in our
example) by accessing Add/Remove Windows Components in Control Panel ->
Add/Remove Programs, and selecting Cluster Service. The first windows shown are
identical to those for the primary cluster node (Figure 4-81 on page 125, and Figure 4-82
on page 125). Continue to the Create or Join a Cluster screen, shown in Figure 4-93.

Figure 4-93 Joining the cluster


22.As we are joining the existing cluster, select The second or next node in the cluster.
Next, specify the cluster name (Figure 4-94).

Figure 4-94 Joining cluster name

23.Enter the name of the cluster you created on the first node (in step 12 on page 126) and
supply the same user ID, password, and domain of the account you will use to connect to
the cluster (in step 13 on page 127). Click Next. Figure 4-95 displays.

Figure 4-95 Account for running the service

24.Specify the password for the domain account which will be used to run the cluster service
on this node. Click Next and then Finish to complete the installation and configuration of
the cluster.


25.Check if the cluster service is running by starting Cluster administration from
Administrative Tools. If the cluster is running all the nodes (DIOMEDE and SENEGAL in
our example) should be up and all resources should be online as shown in Figure 4-96.

Figure 4-96 Running cluster

Tip: If you installed the cluster from media at a lower Service Pack level than the installed
one, you should reapply the latest Service Pack on both nodes before continuing.

4.7.2 Adding shared disk resource for DB2 instance and SRM installation
In our setup, we use a local DB2 database for the Tivoli Storage Resource Manager
repository. To enable this for clustering, we need to provide a clustered instance for this
database, which requires definition of an additional shared disk resource. We have already
defined Disk F: to our cluster as shown in Figure 4-96 on page 133, as a member of the
Cluster group, but it will be later moved to a new cluster group used for the Tivoli Storage
Resource Manager Server cluster.

4.7.3 Installation of DB2 database on both nodes
To cluster the DB2 instance we need to install DB2 on both nodes. The application should be
installed on a local drive, in our example drive C:.

Before installing, create a user ID that will be used to install DB2 (db2admin in our example).
This user ID should be a member of the Windows DomainAdmins group. To start the
installation, log on using this newly created user ID.

When installing DB2, you only need to select the DB2 Enterprise Edition component. You
can then accept all defaults - the only thing you need to change is to select Do not install the
OLAP Starter Kit. After installation, restart the system and apply the appropriate Fix Pack.

In our installation we used IBM DB2 Enterprise Edition 7.2 with Fix Pack 7.

4.7.4 Setting up a clustered instance in DB2
To have a clustered database we need to create a clustered instance. The DB2 installation
provides the db2mscs utility, which automatically changes the existing instance to a clustered


instance, and also creates a new cluster group and all needed resources. Follow these steps
to create the clustered instance:
1. Log on to the system which currently owns the shared disk for the DB2 instance, in our
example Disk F:, with the user ID you created for DB2 installation.
2. Create a new instance, in our example ITSRM, using the following command:
db2icrt ITSRM
3. In the DB2 installation directory create a file DB2MSCS.CFG file with the following entries:
– DB2_INSTANCE - The instance to be clustered
– CLUSTER_NAME - The cluster in which this instance will be clustered
– GROUP_NAME - The cluster group for this instance. We recommend not using the
default Cluster Group here.
– IP_NAME - The IP address to be used for accessing this instance
– IP_ADDRESS - The fixed IP address to be used for accessing this instance
– IP_SUBNET - The subnet mask for IP_ADDRESS
– IP_NETWORK - The network to be used for accessing the instance. Usually this is
either the public or all communications network.
– NETNAME_NAME - The network name to be used to access this instance
– NETNAME_VALUE - The value for the network name to be used for accessing the
instance.
– NETNAME_DEPENDENCY - The IP address on which the network name will need to
be available before. In our case this should be the IP address defined in this
configuration file.
– DISK_NAME - The shared disk to be used for this instance. This resource must exist,
and should not be the quorum disk. The instance directory will be copied to this
resource.
– INSTPROF_DISK - If you specified more then one DISK_NAME, which will be moved
into the instance cluster group, you can specify which disk will be used for the instance
specified in the DB2_INSTANCE parameter.
You can see the configuration file we created in Example 4-4.

Example 4-4 DB2MSCS.CFG file for ITSRM instance
DB2_INSTANCE=ITSRM
CLUSTER_NAME=ITSOSRMCL
GROUP_NAME=SRMCluster
IP_NAME=SRMCluster IP Address
IP_ADDRESS=9.1.38.73
IP_SUBNET=255.255.254.0
IP_NETWORK=Local Area Connection 2
NETNAME_NAME=SRMCluster Network Name
NETNAME_VALUE=CLUSTER2
NETNAME_DEPENDENCY=SRMCluster IP Address
DISK_NAME=Disk F:
INSTPROF_DISK=Disk F:

4. Run the following command to cluster the instance you created in step 2:
db2mscs -f:DB2MSCS.CFG
The command will define all the necessary cluster objects and copy the database instance
files to the clustered disk.


5. After the command successfully finishes, the new cluster group with the name defined in
the configuration file will appear in the cluster definition, as seen in Figure 4-97.

Figure 4-97 DB2 clustered instance

6. Verify that all resources in the new cluster group, in our example SRMCluster, are online.
You can verify the database instance by accessing it in the DB2 Control Center and
creating a sample database. You can also try to failover the resource group and see if the
instance is available.
When you have verified that the clustered instance is working and is capable of failover,
continue with the next installation steps.

4.7.5 Installing IBM Tivoli Storage Resource Manager Server on both nodes
In our example we installed the Tivoli Storage Resource Manager Server on the same disk as
the DB2 clustered instance, Disk F:.

Follow these steps to install Tivoli Storage Resource Manager Server on both nodes:
1. Log on to the first node (DIOMEDE) as the Domain Administrator.
2. If required, fail over the DB2 instance cluster group, in our example SRMCluster, to the
first node in the cluster. This is necessary for our configuration as the DB2 instance is
installed on Disk F: in this group and this disk is required to install the Tivoli Storage
Resource Manager Server on it.
3. Create the database in a non-clustered local instance. We created ITSRMDBD in the DB2
instance as shown in Figure 4-98.


Figure 4-98 Database on first node

4. Install Tivoli Storage Resource Manager Server following the instructions in 4.3.3,
“Installation of the Server code’’ on page 71, using the database created in step 3 as the
repository, in our example ITSRMDBD. Use the cluster NETNAME_VALUE, in our
example cluster2, for the server name (Example 4-4 on page 134). We installed in the
directory F:TivoliTSRM.
5. After installation, stop the services for Server and Agent, and change them to manual
startup mode as shown in Figure 4-99.

Figure 4-99 Service mode

6. Rename the installation directory. In our example we renamed it to F:TivoliTSRMD.


7. During the installation, the TSRMsrv1 Domain account is created. This account has to be
deleted before installing on the second node.
8. Failover the DB2 instance cluster group, in our example SRMCluster, to the second node
in the cluster. This is necessary as we will install Tivoli Storage Resource Manager on this
drive.
9. Log on to the second node as the Domain Administrator.
10.Create the database in a non clustered local instance. In our example we created
ITSRMDBS in the DB2 instance as shown in Figure 4-100.

Figure 4-100 Database on second node

11.Install Tivoli Storage Resource Manager Server following the instructions in 4.3.3,
“Installation of the Server code’’ on page 71, using the database created in step 10 as the
repository, in our example ITSRMDBS. Use the cluster NETNAME_VALUE, in our
example cluster2, for server name. In our example we installed in the directory
F:TivoliTSRM.
12.After installation, stop the services for Server and Agent, and change them to manual
startup mode as shown in Figure 4-99.

4.7.6 Copying the repository database to the clustered instance
To copy the database from the local instance to the clustered instance, do the following on the
second node with the clustered instance cluster group, (SRMCluster), active on this node:
1. Define the clustered instance, in our example ITSRM, in DB2 Control Center as shown in
Figure 4-100.
2. Make a backup of the local database used for the Tivoli Storage Resource Manager
Server, in our example ITSRMDBS, using the database backup tool from DB2 Control
Center.
3. Restore the database into the clustered instance using a different name; in our example
we used SRMDBCL, using the database restore tool from DB2 Control Center.
4. Failover the clustered instance to the first node.


5. Define the clustered instance, in our example ITSRM, in DB2 Control Center as shown in
Figure 4-98 on page 136.
6. Define the restored database, in our example SRMDBCL, in DB2 Control Center as shown
in Figure 4-98 on page 136. Check if the database can be accessed normally.

Continue with the setup when you have verified that the database in the clustered instance
can be accessed from both cluster nodes.

4.7.7 Editing the Server config file to reflect the database change
As we will be using a database in a clustered instance, the Tivoli Storage Resource Manager
Server configuration file (server.config in the config directory) needs to be changed to point to
this database. Example 4-5 shows the config file we used.

Example 4-5 Server config file
[controller]
name="cluster2"
port=2078
maxConnections=500
routerThreads=1
serviceThreads=2
agentErrorLimit=3
adminGroup="Administrators"
commEncrypted=0
[logging]
logsKept=5
messagesPerLog=100000
[repository]
driver=COM.ibm.db2.jdbc.app.DB2Driver
url="jdbc:db2:SRMDBCL"
user=TivoliSRM
connectionPool=10
[service]
name=TStorm.server.svp.GuiSvp
[service]
name=TStorm.server.svp.AgentSvp
[service]
name=scheduler.Scheduler

As you can see we changed the database URL to url=”jdbc:db2:SRMDBCL” to reflect that the
repository database was moved to the clustered instance.

4.7.8 Creating clustered resources for the Server and Agent
Now we are ready to set up the Tivoli Storage Resource Manager Server and Agent as
clustered resources so they will be able to failover.

Follow these steps to define the resources for operating in a clustered environment:
1. Change the password of the TSRMsrv1 domain account to a new value. The password is
randomly generated by the initial install program, and it is used to run the Tivoli Storage
Resource Manager service. Since we need to synchronize this password on both systems,
we must manually reset it.
2. Edit the logon properties for the Tivoli Storage Resource Manager Server service on both
cluster nodes to reflect the password changes. Right-click on the service entry in the


Services applet and select Properties. You should see the window as shown in
Figure 4-101.

Figure 4-101 Password change

Select the Log On tab and enter the new password.

Attention: If you do not change the password on both nodes, the service will fail to
start.

3. Using Cluster Administration, define a new Generic Service resource for the Tivoli
Storage Resource Manager Server in the clustered instance group, in our example
SRMCluster group. When creating the resource you should define it to be dependent on
the following resources:
– The disk where you installed the Server
– The clustered database instance
– The clustered IP address
– The clustered Network Name
You can see these values in our example in Figure 4-102.


Figure 4-102 Resource dependences

The service name used for this resource is TrelliSrv1 as shown in Figure 4-103.

Figure 4-103 Server service name

Also check Use Network Name for computer name, so that the Network Name defined
for this cluster group will be associated with this resource.
4. Using Cluster Administration define a new Generic Service resource for the Tivoli
Storage Resource Manager Agent in the clustered instance group, in our example
SRMCluster group. When creating the resource you should define it to be dependent on
the following resources:
– The disk where you installed the Server
– The clustered database instance
– The clustered IP address
– The clustered Network Name
You can see these values in our example in Figure 4-102.


The service name used for this resource is TrelliSrv1 as shown in Figure 4-104.

Figure 4-104 Agent service name

5. After creating both resources, bring them online, as in Figure 4-105.

Figure 4-105 Cluster view

If all resources are online your Tivoli Storage Resource Manager Server cluster
implementation is ready to use.

Note: When installing the Agents point them to the name which resolves into the cluster IP
address, in our example SRMCluster IP Address as shown in Figure 4-105.


4.8 Manager HA install using remote Oracle database
This section shows how to install Tivoli Storage Resource Manager using a remote Oracle
database. Enterprise database servers are usually already clustered for HA (high availability),
so we will not discuss that further here. We will only focus on protecting the application server
itself. We will set up a primary Tivoli Storage Resource Manager Server using a remote
Oracle database. We will then have a standby Server which can be manually switched over in
the event of failure of the primary. Note this scenario does not use automatic failover.

For this installation we used Oracle 8.1.7 running on a Windows 2000 server as the
repository. Before installing, you need to install a JDBC driver for the database. This driver
can be downloaded from the following Web site:

or located in the Oracle installation directory:
[install drive]:OracleOra81jdbclib

Put the JDBC drivers on the local drive of the systems where the Tivoli Storage Resource
Manager Server will be installed.

Our configuration will use the environment shown in Figure 3-11 on page 61. To set this up:
1. Create the repository database on the Oracle database server.
Our database server was installed in the system GALLIUM, and created using the Oracle
Database Configuration Assistant (Figure 4-106).

Figure 4-106 Starting Oracle Database Configuration Assistant

2. Select Create a database and click Next. On the next screen select Typical and click
Next. Select Create new database files and click Next. For the primary type of database
usage, select Multipurpose and click Next. You can accept the default value for
Concurrently connected users, (in our example, 15) and click Next. On the screen
where you can select options to use with the database, you should deselect all options
and then click Next. A screen similar to Figure 4-107 will display.


Figure 4-107 Selecting the database name

3. Here you define the database name, in our example ITSRMREM. The Assistant will
automatically define the SID for the database, and in our example we accepted the default
value ITSRMREM. After specifying the name click Next. In the next window, select No
don’t register the database and click Next. In the window asking when to create the
database select Create Database Now and click Finish. The assistant will create the
database.
4. Install the Tivoli Storage Resource Manager Server on the standby server using this
database, following the instructions in 4.3.3, “Installation of the Server code’’ on page 71.
In the step for database selection, choose Oracle. The screen shown in Figure 4-108
displays.

Figure 4-108 Database connection information

5. Complete the connection information as shown, and click Next. Figure 4-109 displays.


Figure 4-109 Database information

6. Click Next and continue the installation process as described in 4.3.3, “Installation of the
Server code’’ on page 71.
7. Stop the Tivoli Storage Resource Manager Server service and set the startup type to
manual, using the Services applet under Administrative tools (Figure 4-110).

Figure 4-110 Setting services to manual

8. Clear the repository database, using the Oracle database tools. Delete and recreate the
database with the same name as when you created it (ITSRMREM in our example). This
is required because the installation program tries to create the repository in the database
and if the repository already exists, the installation will fail.


9. Install the Tivoli Storage Resource Manager Server on the primary server using the same
parameters as on the standby server.

Note: If you are using this scenario for HA, you need to maintain two directories inside
the Tivoli Storage Resource Manager installation directory in a consistent state. These
directories are:
config - for the configuration files. After installation or changes on the primary server,
you need to copy those two files to the standby server:
– repository
– nas.config
scripts - for scripts. If you use server distribution to the Agents for the scripts, all
scripts must be copied on both servers.

4.8.1 Testing the standby HA installation
To test the scenario, we simulated a primary server failure. We then did the following:
In the DNS server we changed the settings so that the name of the primary server pointed
to the standby server IP address.
Started the Tivoli Storage Resource Manager Server services on the standby server.

After starting the services, the standby server connects to the remote database repository
using the same settings as the primary server. As all the information except scripts and basic
configuration options are in the database, the operations can resume.

Tip: For the best results you should keep the clocks of the primary and standby servers
synchronized.

Note: The local Agent installed on the primary server will not appear. Also, all tasks related
to that Agent will fail as the name of the standby server Agent is not the same as for the
primary server.

4.9 CIM/OM
This section describes how CIM/OM works, how to install and configure the CIM/ON server,
and how to configure Tivoli Storage Resource Manager to login into the CIM/OM server.

4.9.1 What is CIM/OM?
The Common Information Model (CIM) agent consists of the CIM Object Manager (CIM/OM),
the Service Location Protocol (SLP), and the device provider. A device can be a storage
server such as an IBM TotalStorage Enterprise Storage Server (ESS). The CIM agent
registers itself with SLP to enable discovery by the Client application. The SLP is a directory
service called by a client application to locate the CIM Object Manager. The client application
and the CIM/OM communicate through CIM Messages. The CIM/OM and device provider
communicate through method calls made from the CIM/OM to the provider. The device
provider communicates with the device through proprietary calls. Figure 4-111 shows the
ESS CIM/OM implementation.


CIM/OM ESS implementation
Client
Application

ITSRM

SLP
CIM M essag es
en cod ed w ith in XM L

CIM /O M

Meth od calls m ade from
CIMO M to Pro vid er

Device Provider

Prop rietary calls

Device
or
ESS

ibm.com/redbooks

Figure 4-111 CIM/OM for ESS

IBM Tivoli Storage Resource Manager supports reporting from CIM compliant devices. At the
present time, the only tested device is the ESS using its CIM/OM server. IBM Tivoli Storage
Resource Manager gathers and reports on ESS devices defined in the CIM/OM server. It
uses Probe jobs to collect information about the defined ESS devices and uses the reporting
facilities to view that information.

4.9.2 CIM/OM Server installation for ESS
The supported platforms for the CIM/OM server are shown in Figure 4-112.


CIM/OM Server supported platforms

Windows 2000
AIX
Linux

ibm.com/redbooks

Figure 4-112 CIM/OM server supported platforms

To install and configure the ESS CIM/OM server you need:
ESS 2.1.1.135 or later for model F20 and 2.1.1.136 or later for model 800
Command line Interface (CLI) Version 2.1.1.8 or later
TCP/IP communication

In our example we installed the CIM/OM server V1.1.0.1 on Windows 2000 Advanced Server.
The CIM/OM software can be downloaded from the Web site:

http://www-1.ibm.com/support/search.wss?rs=586&q=ssg1*&tc=STHUUM&dc=D400

Pre-installation task
Before installing the CIM/OM server, the ESS CLI has to be installed and configured correctly.
In our example we used ESS CLI Version 2.1.1.8. Verify the ESS CLI is correctly installed
using the command shown in Example 4-6.

Example 4-6 Checking ESS CLI installation
C:>esscli -u storwatch -p specialist -s 172.31.1.1 list server
Tue Jun 10 23:10:15 CEST 2003 IBM ESSCLI 2.1.0.8

Server Model Mfg WWN CodeEC Cache NVS Racks
---------- ----- --- ---------------- --------- ----- ----- -----
2105.18921 F20 075 5005076300C08781 2.1.1.269 8GB 384MB 1
C:>

You should see your ESS listed, as in the example. If not, reinstall the CLI package.


CIM/OM installation
After verifying the ESS CLI, we installed and configured CIM/OM server:
1. From the CIM/OM CD, or downloaded image, run launchpad.bat Figure 4-113 displays.

Figure 4-113 ESS CIM/OM startup screen

2. Click on Installation wizard - you will see a Welcome screen. Click Next to display the
License agreement. Click Next to accept it, and the directory selection screen
(Figure 4-114) displays.


Figure 4-114 Installation directory

3. Choose the installation directory and click Next. The installation summary screen
(Figure 4-115) displays.

Figure 4-115 Installation size

4. Click Install to start copying files. After this is complete you will see a successful
completion message. Click Finish to end the installation process.


Post-installation
The installation process creates two system services:
Service Location Protocol (SLP)
IBM CIM Object Manager

After installation, verify the two services are running, as they are essential to provide the
CIM/OM interface to the managed ESS devices.

CIM/OM configuration
Now you need to configure the CIM/OM to actually access the ESS and start providing this
information to the CIM enabled management application.
1. Define the users who will access the CIM/OM interface to gather data. Open a command
prompt with Start -> Programs -> IBM TotalStorage CIM Agent for ESS -> Configure
CIMOM Users. Use the adduser command as in Example 4-7.

Example 4-7 Adding CIM/OM users
Application setuser started in interactive mode
To terminate the application enter: exit
To get a help message enter: help
>>> adduser itsrm itsrm
An entry for user itsrm successfully added
>>>

In our example we defined user itsrm, with password itsrm. The exit command closes
the window.
2. Define the ESSs which will be controlled by the CIM/OM server. Open a command prompt
with Start -> Programs -> IBM TotalStorage CIM Agent for ESS -> Enable ESS
Communication. Use the address command (Example 4-8) to define a managed ESS.

Example 4-8 Defining ESSes to be managed by CIM/OM
Application setdevice started in interactive mode
To terminate the application enter: exit
To get a help message enter: help
>>> address 172.31.1.1 storwatch specialist
An ess provider entry for IP 172.31.1.1 successfully added
>>>

3. After applying these definitions, we recommend rebooting the CIM/OM server.
4. To check that the setup is correct, run the verifyconfig command in the CIM/OM
installation directory as shown in Example 4-9.

Example 4-9 Verifying ESS CIM/OM configuration
C:Program FilesIBMcimagent>verifyconfig -u itsrm -p itsrm
Verifying configuration of ESS CIM Agent...
Communicating with SLP to find WBEM services...
1 WBEM services found
host=w2kadvtsm, port=5989
Connecting to ESS CIM Agent, host=w2kadvtsm, port=5989
Found 1 IBMTSESS_StorageSystem instances
Verification Successful

C:Program FilesIBMcimagent>


Your Managed Systems should be listed as IBMTSESS_StorageSystem. If not, re-check
all the setup steps.

Tip: If the verification still fails, try restarting both the CIM/OM services before re-verifying.

Upgrading CIM/OM
At the time of writing there was a fix Version 1.1.0.2 available for CIM/OM. It is recommended
to install this fix, which can be downloaded from:

http://www-1.ibm.com/support/search.wss?rs=586&q=ssg1*&tc=STHUUM&dc=D400

To install the update, do the following:
1. Stop the CIM/OM related services:
– Service Location Protocol (SLP)
– IBM CIM Object Manager
2. Unpack the fix file to a temporary directory, and run the cimagentfix.cmd to start the
update. You will see a screen similar to Figure 4-116.

Figure 4-116 Welcome screen

3. Click Next to start the installation; it will check the current and new version, as shown in
Figure 4-117.


Figure 4-117 Current version

4. Click Next to continue; the installation confirmation screen displays (Figure 4-118),
including the location and file size.

Figure 4-118 Install size

5. Click Install to begin copying files. When done, you will see the screen in Figure 4-119.


Figure 4-119 Installation finished

6. Click Finish to end the installation process.

After the upgrade, check if the CIM/OM related services are running, and verify the
configuration as shown in Example 4-9 on page 150.

CIM/OM security
By default CIM/OM server uses secure communication with certificates. The certificate
created during installation is in the file truststore in the installation directory. You can create
new certificates with the command mkcertificate The new certificate will also be stored in
the truststore file.

IBM Tivoli Storage Resource Manager supports secure communication with CIM/OM. If you
are using an application which does not support the secure protocol, the CIM/OM server can
be configured to run in insecure mode. Follow the instructions in Common Information Model
Agent Installation and Configuration Guide for the IBM Enterprise Storage Server,
GC35-0485.

Your CIM/OM server for IBM ESS is now ready to do some serious reporting.

4.9.3 CIM/OM configuration in IBM Tivoli Storage Resource Manager
Before using the storage subsystem reports with IBM Tivoli Storage Resource Manager, you
need to register the CIM/OM server as follows:
1. Navigate to CIM/OM Logins node in the navigation tree as shown in Figure 4-120.


Figure 4-120 CIM/OM Logins in navigation tree

2. To create a new CIM/OM login definition, click Create. Figure 4-121 displays.

Figure 4-121 Defining CIM/OM login

The following fields have to be populated:
– Host Name - fully resolvable name of the CIM/OM server - in our example w2kadvtsm.

– Port - the CIM/OM CP/IP port. The CIM/OM server for ESS uses port 5989 for secure
communication port and 5988 for insecure communication. In our example we used
port 5989.


– Protocol - The ESS CIM/OM server can use either https or http for the protocol. In our
example we used the secure protocol https.
– User Name - the user name which is defined in the CIM/OM server. In our example we
used itsrm (step 1 on page 150).
– Password - the corresponding password for the user name.
– Certificate File - the certificate file which was created on the CIM/OM server.

Tip: The truststore file has to be copied from the CIM/OM server to the machine
where IBM Tivoli Storage Resource Manager server is installed. If both are running
on the same machine, you can use the original location.

After entering all the required data, click Save to store the information into the repository
database. The defined CIM/OM login will appear similar to Figure 4-120.
Once you have defined the CIM/OM login(s) you can edit or delete them using the Edit
and Delete buttons.
3. Before you can start collecting data for CIM/OM managed ESSs, you need to discover
them. The discovery is done using the CIM/OM login information by the Agent on the IBM
Tivoli Storage Resource Manager Server. Select Discovery under Monitoring in the IBM
Tivoli SRM Tree. Right-click the Discovery tree and select Run Now as shown in
Figure 4-122.

Figure 4-122 Running discovery

4. Once discovery is complete, you should see two entries from the Agent installed on the
IBM Tivoli Storage Resource Manager Server. If you scroll the status window correctly you
can distinguish which was the CIM/OM discovery as shown in Figure 4-123.


Figure 4-123 Finding CIM/OM discovery

The Log File Name for the CIM/OM will include cimom_discovery in the name, thus
identifying it as the discovered CIM/OM. To see if the discovery was successful, display
the job output information by double clicking the spy glass symbol circled in Figure 4-123.
The output is shown in Figure 4-124.


Figure 4-124 Discovery job output

Our output shows that the ESS subsystem (2105.18921, where 18921 is the ESS serial
number) was discovered and configured. You can also see that CIM/OM data was queried
from the host w2kadvtsm which is the CIM/OM server.
5. Once the ESS is discovered, it can be configured for monitoring. Navigate to CIM/OM
Storage Subsystem Administration in the Navigation Tree as shown in Figure 4-125.

Figure 4-125 Storage Subsystem Administration

All discovered ESS’s will be displayed. To enable reporting on particular ESS, check the
Monitored square as shown in Figure 4-125.


You can also set an alias, which will be then used in reports, by selecting the ESS entry
and clicking on Set disk alias. In our example we specified ESSF20 as an alias.
We give details of ESS subsystem reporting in 6.3, “Tivoli Storage Resource Manager
ESS Reporting’’ on page 297.


5

Chapter 5. Operations: Policy, Quotas, and
Alerts
In this chapter we describe how to setup the Tivoli Storage Resource Manager functions
related to monitoring, alerting, and policy management of your storage environment. We will
discuss the following:
Discovery
Probes for asset reporting
Pings for availability reporting
Scans for capacity and usage reporting
Policy Management including ESS LUN provisioning


5.1 OS Monitoring

Tivoli Storage Resource Manager Monitoring
Scheduled and ad hoc data collection
Discovery
Probes for asset reporting
Pings for availability reporting
Scans for capacity and usage reporting
Policy Management
ESS LUN provisioning

ibm.com/redbooks

Figure 5-1 Tivoli Storage Resource Manager Monitoring features

The Monitoring features of Tivoli Storage Resource Manager enable you to run regularly
scheduled or on-the-flight data collection jobs. These jobs gather statistics about the storage
assets and their availability and their usage within your enterprise, and make the collected
data available for reporting.

We will now give a quick overview of the monitoring jobs, and explain how they work through
practical examples.

Reporting on the collected data is explained in Chapter 6, “Reporting” on page 247.

5.1.1 Navigation tree
Figure 5-2 shows the complete navigation tree for OS Monitoring which includes Groups,
Discovery, Pings, Probes, Scans, and Profiles.


Figure 5-2 OS Monitoring tree

Except for Discovery, you can create multiple definitions for each of those monitoring features
of Tivoli Storage Resource Manager. To create a new definition, right-click on the feature and
select New <feature>. Figure 5-3 shows how to create a new Scan job.

Figure 5-3 New Scan job creation

Once saved, any definition within Tivoli Storage Resource Manager can be updated by
right-clicking on the object and selecting Edit. This will put you in Edit mode. Save your
changes by clicking the floppy disk icon in the top menu bar.

Chapter 5. Operations: Policy, Quotas, and Alerts 161

Discovery, Pings, Probes, and Scan menus contain jobs that can run on a scheduled basis or
ad hoc. To execute a job immediately, right-click the job then select Run now (see
Figure 5-4). Each execution of a job creates a time-stamped output that can be displayed by
expanding the tree under the job.

Figure 5-4 OS Monitoring - Jobs list

The color of the job output represents the job status:
Green - Successful run
Brown - Warnings occurred during the run
Red - Errors occurred during the run
Blue - Running jobs

To view the output of a job, double click the job.

Groups and Profiles are definitions that may be used by other jobs - they do not produce an
output in themselves.

As shown in Figure 5-4, all objects created within Tivoli Storage Resource Manager are
prefixed with the user ID of the creator. Default definitions, created during product installation,
are prefixed with Tivoli.Default.

Groups, Discovery, Probes, Scans, and Profiles are explained in the following sections.

5.1.2 Groups
Before defining monitoring and management jobs, it may be useful to group your resources
so that you can limit the scope of monitoring or data collection.

Figure 5-5 shows the groups you can create with Tivoli Storage Resource Manager.


Tivoli Storage Resource Manager Groups
Used for targeted monitoring and policy management

Allows grouping by
Computers
Filesystems
Directories
User ids
OS user groups

ibm.com/redbooks

Figure 5-5 Tivoli Storage Resource Manager Groups

Computer Groups
Computer Groups allow you to target management jobs on specific computers based on your
own criteria. Some criteria you might consider for grouping computers are platform type,
application type, database type, and environment type (for example, test or production).

Our lab environment contains:
UNIX servers
Windows 2000 servers
MS SQL-Server databases
Oracle databases
NAS200 server

In order to target specific servers for monitoring based on OS and/or database type, we will
define these four groups:
Windows Systems
UNIX System
Windows DB Systems
NAS Devices

To create the first group, expand Groups -> Computer, right-click Computer and select New
Computer Group. Our first group will contain all UNIX systems as shown in Figure 5-6. To
add or remove a host from the group, highlight it in either the Available or Current Selections
panel and use the arrow buttons. You can also enter a meaningful description in the field.


Figure 5-6 Computer Group definition

To save the new Group, click the floppy disk icon in the menu bar, and enter the Group name
in the confirmation box shown in Figure 5-7.

Figure 5-7 Save a new Computer Group

We created the other groups using the same process, and named them Windows Systems,
Windows DB Systems, and NAS Devices.

Important: To avoid redundant data collection, a computer can belong to only one Group
at a time. If you add a system which is already in a Group, to a second Group, it will
automatically be removed from the first Group.

Figure 5-8 shows the final Group configuration, with the members of the Windows Systems
group.


Figure 5-8 Final Computers Group definitions

Note: The default group Tivoli.DefaultComputerGroup contains all servers that have been
discovered, but not yet assigned to a Group.

Filesystem Groups
Filesystem Groups are used to associate together filesystems from different computers that
have some commonality. You can then use this group definition to focus the Scan and the
Alert processes to those filesystems.

To create a Filesystem Group, you have to select explicitly each filesystem for each computer
you want to include in the group. There is no way to do a grouped selection, e.g. / (root)
filesystem for all UNIX servers or C: for all Windows platforms. Figure 5-9 shows the
Filesystem Group definition screen.


Figure 5-9 Filesystem Group definition

Note: As for computers, a filesystem can belong to only one Group.

Directory GROUPS
Use Directory Groups to group together directories to which you want to apply the same
storage management rules.

Figure 5-10 shows the Directory Group definition screen.


Figure 5-10 Directory group definition

The Directory Group definition has two views for directory selection:
Use directories by computer to specify several directories for one computer.
Use computers by directory to specify one directory for several computers.

The button on the bottom of the screen toggles between New computer and New directory
depending on the view you select.

We will define one Directory Group with /tmp for all computers, and another with the Oracle
log directory for a specific computer (DIOMEDE). To define the first Group:
1. Select computers by directory.
2. Click on New directory.
3. Enter /tmp in the Directory field and select All computers (see Figure 5-11).


Figure 5-11 Computers by directory definition

4. Click on OK and save the group as /tmp.

For the second group:
1. Select directories by computer.
2. Click New computer.
3. Select diomede from the pull-down Computer field (see Figure 5-12).
4. Enter C:oracleoradataitsrmarchive in the Directories field (see Figure 5-12)

Figure 5-12 Directories by computer configuration

5. Click Add, then OK.
6. Save the group as OracleArchive.

Figure 5-13 shows our final Groups configuration and details of the OracleArchive Group.


Figure 5-13 Final Directories Group definition

User Groups
You can define Groups made up of selected user IDs. These groupings will enable you to
easily define and focus storage management rules such as scanning and Constraints on the
defined IDs.

Note: You can include in a User Group only user IDs defined on the discovered hosts,
which have files belonging to them.

Figure 5-14 shows the list of available users at a specific point in time.


Figure 5-14 List of available users

As shown in Example 5-1, we added a new user on the Agent DIOMEDE and created some
files for the user. We than ran a new Scan.

Example 5-1 Create user and files

root@brazil> mkgroup -'A' itso_grp
root@brazil> mkuser pgrp=itso_grp home=/home/itso_usr itso_usr
root@brazil> chown itso_usr:itso_grp /home/itso_usr
root@brazil> su - itso_usr
$ pwd
/home/itso_usr
$ echo "hello" > myfile
$ ls -l myfile
-rw-r--r-- 1 itso_usr itso_grp 6 Sep 13 11:46 myfile

Now, Figure 5-15 shows that this user ID (itso_usr) is listed in the Available user’s list.


Figure 5-15 List of available user after Scan

Note: As for computers, a user can be defined in only one Group.

OS User Group Groups
You can define Groups consisting of operating system user groups such as Administrators for
Windows or adm for UNIX. To define a Group consisting of user groups, select OS User
Group from the Groups entry on the left hand panel.

Note: As for users, an OS User Group will be added to the list of available Groups only
when a Scan job finds at least one file owned by a user belonging to that Group.

Note: As for users, an OS User Group can belong to only one Group at a time.


5.1.3 Discovery
The discovery process is used to discover new computers within your enterprise that have not
yet been monitored by Tivoli Storage Resource Manager, as shown in Figure 5-16.

Tivoli Storage Resource Manager Discovery process
The Discovery process will discover
Windows servers in the same domain
NAS filers
NetWare servers

ibm.com/redbooks

Figure 5-16 Discovery process

The discovery process will:
Request a list of Windows systems from the Windows Domain Controller
Contact, through SNMP, all NAS filers and check if they are registered in the nas.config file
Discover all NetWare servers in the NetWare trees reported by Agents
Search UNIX Agents’ mount tables, looking for remote filesystems and discover NAS filers

More details of NAS and NetWare discovery are given in “NAS discovery” on page 56, and in
“Novell NetWare discovery” on page 58.

Use IBM Tivoli SRM -> Monitoring -> Discovery to change the settings of the Discovery
job. The following options are available.

When to run tab
The initial tab When to Run, (Figure 5-17) is used to modify the scheduling settings. You can
specify to execute the discovery:
Now - Run once when the job is saved.
Once - at a specified time in the future
Repeatedly - Choose the frequency in minutes, hours, days, weeks, or months. You can
limit the run to specific days of the week.


Figure 5-17 Discovery When to Run options

Alert tab
The second tab, Alert, enables you to be notified when a new computer is discovered. See
5.2, “OS Alerts” on page 189 for more details on the Alerting process.

Options tab
The third tab, Options (Figure 5-18) sets the discovery runtime properties.

Figure 5-18 Discovery job options

Uncheck the Skip Workstations field if you want to discover the Windows workstations
reported by the Windows Domain Controller.


5.1.4 Pings
Figure 5-19 summarizes the Ping process.

Tivoli Storage Resource Manager Ping process
The Ping process will
launch TCP/IP pings against monitored computers
generate statistics on computer Availability in the central repository
generate an Alert if the process fails because of an unavailable host

ibm.com/redbooks

Figure 5-19 Ping process

Pings gather statistics about the availability of monitored servers. The scheduled job will Ping
your servers and consider them active if it gets an answer. This is purely ICMP-protocol
based - there is no measurement of individual application availability. When you create a new
Ping job, you can set the following options.

Computers tab
Figure 5-20 shows the Computers tab, which is used to limit the scope of the computers that
are to be Pinged.


Figure 5-20 Ping job configuration - Computers

When to Ping tab
The tab, When to PING, sets the frequency used for checking. We selected a frequency of 10
minutes as shown in Figure 5-21.

Figure 5-21 Ping job configuration - When to Ping

Options tab
On the Options tab, you specify how often the Ping statistics are saved in the database
repository. By default, Tivoli Storage Resource Manager keeps its Ping statistics in memory
for one hour before flushing them to the database and calculating an average availability. You
can change the flushing interval to another time amount, or a number of Pings (for example,
to calculate availability after every 10 Pings). The system availability is calculated as:
(Count of successful pings) / (Count of pings)


A lower interval can increase database size, but gives you more accuracy on the availability
history.

We selected to save to the database at each Ping, which means we will have an availability of
100% or of 0%, but we have a more granular view of the availability of our servers.

Alerts tab
The Alerts tab (shown in Figure 5-22) is used to generate Alerts for each host that is
unavailable. Alert mechanisms are explained in more detail in 5.2, “OS Alerts” on page 189.

You can choose any Alert type from the following:
SNMP trap to send a trap to the Event manager defined in Administrative services —>
Configuration —> General —> Alert Disposition
Login Notification to direct the Alert to the specified user in the Alert Log (see 5.2, “OS
Alerts” on page 189)
Windows Event Log to generate an event to the Windows event log
Run Script to run a script on the specified server
Email to send a mail to the specified user through the Mail server defined in
Administrative services -> Configuration -> General -> Alert Disposition

Figure 5-22 Ping job configuration - Alert

We selected to:
Send e-mail to two users
Run a script that will send popup messages to selected administrators. The script is listed
in Example 5-2. Optimally, you would send an event to a central console such as the Tivoli
Enterprise Console. Note that certain parameters are passed to the script - more
information is given in “Alerts tab” on page 195.

Example 5-2 Script PINGFAILED.BAT
net send /DOMAIN:a23blvag Computer %1 did not respond to last %2 ping(s). Please check it


We then saved the Ping job as PingHosts, and tested it by right-clicking and selecting Run
now. As the hosts GALLIUM and CRETE did not respond, we received:
One popup for GALLIUM (Figure 5-23)

Figure 5-23 Ping failed popup for GALLIUM

A similar popup for CRETE
One e-mail for GALLIUM (Figure 5-24)

Figure 5-24 Mail message for GALLIUM

A similar e-mail for CRETE

More details about the related reporting features of Tivoli Storage Resource Manager are in
6.2.3, “Availability Reporting” on page 262.

5.1.5 Probes
Figure 5-25 summarizes the Probe process.


Tivoli Storage Resource Manager Probe process
The Probe process will
gather Assets data on monitored computers
Memory
Processors
Hard disks
Filesystems
store data in the central repository
generate an Alert if the process fails

ibm.com/redbooks

Figure 5-25 Probe process

The Probe process gathers data about the assets and system resources of Agents such as:
Memory size
Processor count and speed
Hard disks
Filesystems

The data collected by the Probe process is used by the Assets Reports described in 6.2.1,
“Asset Reporting” on page 252.

Computers tab
Figure 5-26 shows that we included the Tivoli.Default Computer Group in the Probe so that all
computers, including those not yet assigned to an existing Group, will be Probed. We saved
the Probe as ProbeHosts.


Figure 5-26 New Probe configuration

Important: Only the filesystems that have been returned by a Probe job will be available
for further use by Scan, Alerts, and policy management within Tivoli Storage Resource
Manager.

When to Probe tab
This tab has the same configuration as for the Ping process.

We set up a weekly Probe to run on Sunday for all computers. We recommend running the
Probe job at a time where all the production data you want to monitor is available to the
system.

Alert tab
As this is not a business-critical process, we asked to be alerted by mail for any failed Probe.
Figure 5-27 shows the default mail text configuration for a Probe failure.

Figure 5-27 Probe alert - mail configuration


5.1.6 Profiles
The main functionality of Profiles is explained in Figure 5-28.

Tivoli Storage Resource Manager Profiles
Profiles are used
in Scan jobs
to limit files to be scanned
to specify files attibutes to be scanned
to select the summary view
directories and filesystems
user ids
OS user groups
to set statistics retention period

Tivoli Storage Resource Manager provides default profiles that
provide data for all the default reports

ibm.com/redbooks

Figure 5-28 Profiles

Profiles are used in Scan jobs to specify:
The pattern of files to be scanned
The attributes of files to be gathered
The summary view that will be available in reports
The statistics retention period

Specifying correct profiles avoids gathering unneeded information that may lead to space
problems within the Tivoli Storage Resource Manager repository. However, you will not be
able to report on or check Quotas on files that are not used by the Profile.

Tivoli Storage Resource Manager comes with several default profiles, (shown in Table 5-1)
prefixed with Tivoli.Default, which can be reused in any Scan jobs you define.

Table 5-1 Default profiles

Default profile name Description

BY_ACCESS Gathers statistics by length of time since last access of files

BY_CREATION Gathers statistics by length of time since creation of files

BY_MOD_NOT_BACKED_UP Gathers statistics by length of time since last modification (only for
files not backed up since modification). Windows only

BY_MODIFICATION Gathers statistics by length of time since last modification of files


Default profile name Description

LARGEST_DIRECTORIES Gathers statistics on the n largest directories. (20 is the default
amount.)

LARGEST_FILES Gathers statistics on the n largest files. (20 is the default amount.)

LARGEST_ORPHANS Gathers statistics on the n largest orphan files. (20 is the default
amount.)

MOST_AT_RISK Gathers statistics on the n files that have been modified the longest
time ago and have not yet been backed up since they were
modified. Windows only. (20 is the default amount.)

OLDEST_ORPHANS Gathers statistics on the n oldest orphan files. (20 is the default
amount.)

SIZE_DISTRIBUTION Gathers information on the size distribution of files

MOST_OBSOLETE_FILES Gathers statistics on the n “most obsolete” files (i.e., files that have
not been accessed or modified for the longest period of time). (20
is the default amount.)

SUMMARY_BY_FILESYSTEM Summarizes space usage by Filesystem or Directory
/DIRECTORY

SUMMARY_BY_GROUP Summarizes space usage by OS Group

SUMMARY_BY_OWNER Summarizes space usage by Owner

Those default profiles, when set in a Scan job, gather data needed for all the default Tivoli
Storage Resource Manager reports.

As an example, we will define an additional Profile to limit a Scan job to the 500 largest
Postscript or PDF files unused in the last six months. We also want to keep weekly statistics
at a filesystem and directory level for two weeks.

Statistics tab
On the Statistics tab (shown in Figure 5-29), we specified:
Retain filesystem summary for two weeks
Gather data based on creation data
Select the 500 largest files

The Statistics tab is used to specify the type of data that is gathered, and has a direct
impact on the type of reports that will be available. In our specific case, the Scan associated
with this profile will not create data for reports based on user IDs and users groups. Neither
will it create data for reports on directory size.


Figure 5-29 New Profile - Statistics tab

The Summarize space usage by section of the Statistics tab specifies how the space usage
data must be summarized. If no summary level is checked, the data will not be summarized,
and therefore will not be available for reporting in the corresponding level of Usage Reporting
section of Tivoli Storage Resource Manager.

In our particular case, because we select to summarize by filesystem and directory, we will
see space used by PDF and Postscript files at those levels, providing we set up the Scan
profile correctly. See 5.1.7, “Scans” on page 185 for information on this. We will not see which
users or groups have allocated those PDF and Postscript files.

Restriction: For Windows servers, users and groups statistics will not be created for FAT
filesystems.

The Accumulate history section sets the retention period of the collected data. In this case,
we will see a weekly summary for the last two weeks.

The Gather statistics by length of time since section sets the base date used to calculate the
file load. It determines if data will be gathered and summarized for the IBM Tivoli SRM ->
Reporting -> Usage -> Files reporting view.

The Gather information on the section sets the amount of files to retrieve for each of the
report views available under IBM Tivoli SRM -> Reporting -> Usage -> Access Load.

Files filter tab
The Files filter tab is used to limit the scope of files that are returned by the Scan job. To
create a selection, right-click on the All files selected context-menu option as shown in
Figure 5-30.


Figure 5-30 New Profile - File filter

With the New Condition menu, you can create a single filter on the files while the New
Group enables you to combine several conditions with:
All of The file is selected if all conditions are met (AND)
Any of The file is selected if at least one condition is met (OR)
None of The file is NOT selected if at least one condition is met (NOT OR)
Not all of The file is selected if none of the conditions are met (NOT AND)

The Condition Group can contain individual conditions or other condition groups.

Each individual condition will filter files based on one of the listed items:
Name
Last access time
Last modified
Creation time
Owner user ID
Owner group
Windows files attributes
Size
Type
Length

We want to select files that meet our conditions: (name is *.ps or name is *.pdf) and
unused since six months. The AND between our two conditions will be translated to All of,
while the OR within our first condition will be translated to Any of.

On the screen shown in Figure 5-30, we selected New Group. From the popup screen,
Figure 5-31, we selected All of and clicked OK.


Figure 5-31 New Condition Group

Now, within our All of group we will create one dependant Any of group using the same
sequence. The result is shown in Figure 5-32.

Figure 5-32 New Profile - Conditions Groups

Now, we create individual conditions within each group by right-clicking on New Condition on
the group where the conditions must be created. Figure 5-33 shows the creation of our first
condition for the Any of group. We enter in our file specifications (*.ps and *.pdf) here.

Figure 5-33 New Profile - New condition

We repeated the operation for the second condition (All of). The final result is shown in
Figure 5-34.


Figure 5-34 New Profile - Conditions

The bottom of the right pane shows the textual form of the created condition. You can see that
it corresponds to our initial condition. We saved the profile as PS_PDF_FILES (Figure 5-35).

Figure 5-35 Profile save

5.1.7 Scans
We explain in Figure 5-36 the main objectives of the Scan jobs.


Tivoli Storage Resource Manager Scan process
The Scan process is used
to gather data about files
to summarize Usage statistics

as specified in the associated profiles

Mandatory for Quotas and Constraints management

ibm.com/redbooks

Figure 5-36 Scans

The Scan process gathers statistics about the usage and trends of the server storage. Scan
jobs results are stored in the repository and supply the data necessary for the Capacity,
Usage, Usage Violations, and Backup Reporting facilities. To create a new scan job, IBM
Tivoli SRM -> Monitoring -> Scans, right-click and select New scan. The scope of each
Scan job is set by five different tabs on the right pane.

Filesystems tab
You can specify a specific filesystem for one computer, a filesystem Group (see “Filesystem
Groups” on page 165) or all filesystems for a specific computer. Only the filesystems you
have selected will be scanned. Figure 5-37 shows how to configure the Scan to gather data
on all our servers.

Note: Only filesystems found by the Probe process will be available for Scan.


Figure 5-37 New Scan configuration - Filesystem tab

Directory Groups tab
Use this tab to extend the scope of the Scan and also summarize data for the selected
directories. Only directories in the previously selected filesystems will be scanned.

Profiles tab
As explained in 5.1.6, “Profiles” on page 180, the Profiles are used to select the files that are
scanned for information gathering. A Scan job scans and gathers data only for files that are
scoped by selected Profiles. You can specify Profiles at two levels:
Filesystems: All selected filesystems will be scanned and data summarized for each
filesystem.
Directory: All selected directories (if included in the filesystem) will be scanned and data
summarized for each directory.

Figure 5-38 shows how to configure a Scan to have data summarized at both the filesystem
and directory level.


.

Figure 5-38 New Scan configuration - Profiles tab

When to Scan tab
As for the Probe and Ping jobs, the scheduling of the job is specified on the When to Scan tab.

Alert tab
You can be alerted through mail, script, Windows Event Log, SNMP trap, or Login notification
if the Scan job fails. The Scan job may fail if an Agent is unreachable.

Click on the floppy icon to save your new Scan job, shown in Figure 5-39.

Figure 5-39 New Scan - Save

Putting it all together
Table 5-2 summarizes the reports views for filesystems and directories that will be available
depending on the settings of the Profiles and the Scan jobs. We assume the Profiles have
been defined with the Summarize space by Filesystem/Directory option. Note that in order
to get reports by filesystem or directory, you need to select either or both in the Scan Profile.


Table 5-2 Profiles/Scans versus Reports
Scan Jobs settings Available reports

Filesystem Directory Filesystem Directory What is scanned By Filesystem By Directory
/Computer profile profile Reports Reports

x - - - FS - -

x x - - FS - -
Dir if in specified FS

x x x - FS x -

x x x x FS x x

x x x FS x
Dir scanned if in
specified FS

x - x x FS x -

x - - x FS - -

5.2 OS Alerts
Tivoli Storage Resource Manager enables you to define Alerts on computers, filesystems,
and directories. Once the Alerts are defined, it will monitor the results of the Probe and Scan
jobs, and will trigger an Alert when the threshold or the condition is met.

Tivoli Storage Resource Manager provides a number options for Alert mechanisms from
which you can choose depending on the severity you assign to the Alert.

Figure 5-40 shows the Alert mechanisms provided by Tivoli Storage Resource Manager.


Tivoli Storage Resource Manager Alert mechanisms
Triggers on
Computers
Filesystems
Directories

Alert mechanisms
SNMP traps
TEC events
Tivoli SRM GUI alerts
Windows Event Logger
Scripts
Email

ibm.com/redbooks

Figure 5-40 Alerts mechanisms

Depending on the severity of the triggered event or the functions available in your
environment, you may want to be alerted with:
An SNMP trap to an event manager. Figure 5-41 shows a Filesystem space low Alert as
displayed in our SNMP application, IBM Tivoli NetView. Defining the event manager is
explained in “Alert Disposition” on page 114.

Figure 5-41 Alert - SNMP trap sample

A TEC event. See Chapter 5., “Operations: Policy, Quotas, and Alerts” on page 159.


An entry in the Alert Log (see Figure 5-42). You can configure Tivoli Storage Resource
Manager, so that the Alert Log will be automatically displayed when you log on to the GUI
by using Preferences -> Edit General (see Figure 5-43).

Figure 5-42 Alert - Logged alerts sample

Figure 5-43 Alert - Preferences

An entry in the Windows Event log, as shown in Figure 5-44. This is useful for lower
severity alerts or when you are monitoring your Windows event logs with an automated
tool such as IBM Tivoli Distributed Monitoring.


Figure 5-44 Alerts - Windows Event viewer sample

Running a specified script - The script runs on the specified computer with the authority of
the Agent (root or Administrator). See 5.3.5, “Scheduled actions” on page 229 for special
considerations with scripts execution.
An e-mail - Tivoli Storage Resource Manager must be configured with a valid SMTP
server and port as explained in “Alert Disposition” on page 114. Figure 5-45 shows an
example of e-mail notification.

Figure 5-45 Alerts - Mail sample

5.2.1 Alerting navigation tree
Figure 5-46 shows the complete navigation tree for OS Alerting which includes Computer
Alerts, Filesystem Alerts, Directory Alerts, and Alert Log.


Figure 5-46 OS Alerting tree

Except for the Alert Log, you can create multiple definitions for each of those Alert features of
Tivoli Storage Resource Manager. To create a new definition, right-click on the feature and
select New <feature>. Figure 5-47 shows how to create a new Filesystem Alert.


Figure 5-47 Filesystem alert creation

5.2.2 Computer Alerts
Computer Alerts act on the output of Probe jobs (see 5.1.5, “Probes” on page 177) and
generate an Alert for each computer that meets the triggering condition. Figure 5-48 shows
the configuration screen for a Computer Alert.


Figure 5-48 Computer alerts - Alerts

Alerts tab
The Alerts tab contains two parts:
Triggering condition to specify the computer component you want to be monitored. You
can monitor a computer for:
– RAM increased
– RAM decreased
– Virtual Memory increased
– Virtual Memory decreased
– New disk detected
– Disk not found
– New disk defect found
– Total disk defects exceed. You will have to specify a threshold.
– Disk failure predicted
– New filesystem detected
Information about disk failures is gathered through commands against disks with the
following exceptions:
– IDE disks do support only Disk failure predicted queries
– AIX SCSI disks do not support failures and predicted failures queries
Triggered action where you specify the action that must be executed. Available actions are
described in Figure 5-40. If you choose to run a script, it will receive several positional
parameters that depends on the triggering condition. The parameters display on the
Specify Script panel, which is accessed by checking Run Script and clicking the Define
button.

Figure 5-49 shows the parameters passed to the script for a RAM decreased condition.


Figure 5-49 Computer alerts - RAM decreased script parameters

Figure 5-50 shows the parameters passed to the script for a Disk not found condition.

Figure 5-50 Computer alerts - Disk not found script parameters

Computers tab
This limits the Alert process to specific computers or computer Groups (Figure 5-51).

Figure 5-51 Computer alerts - Computers tab


5.2.3 Filesystem Alerts
Filesystem Alerts will act on the output of Probe and Scan jobs and generate an Alert for each
filesystem that meets the specified threshold. Figure 5-52 shows the configuration screen for
a Filesystem Alert.

Figure 5-52 Filesystem Alerts - Alert

Alerts tab
As for Computer Alerts, the Alerts tab contains two parts. In the Triggering condition section
you can specify to be alerted if a:
Filesystem is not found, which means the filesystem was not mounted during the most
recent Probe or Scan.
Filesystem is reconfigured.
Filesystem free space is less than a threshold specified in percent, KB, MB, or GB.
Free UNIX filesystem inode count is less than a threshold (either percent or inodes count).

You can choose to run a script (click the Define button next to Run Script), or you can also
change the content of the default generated mail by clicking on Edit Email. You will see a
popup with the default mail skeleton which is editable. Figure 5-53 shows the default e-mail
message.


Figure 5-53 Filesystem alert - Freespace default mail

5.2.4 Directory Alerts
Directory Alerts will act on the output of Scan jobs.

Alerts tab
Directory Alerts configuration is similar to Filesystem alerts. The supported triggers are:
Directory not found
Directory consumes more than the specified threshold set in percent, KB, MB or GB.

Directories tab
Since Probe jobs do not report on directories and Scan jobs report only on directories. if a
directory Profile has been assigned (See “Putting it all together” on page 188) you can only
choose to be alerted for any directory that has already been included in a Scan and actually
scanned.

5.2.5 Alert logs
The IBM Tivoli SRM -> Alerting -> Alert log menu (Figure 5-54) lists all Alerts that have
been generated.


Figure 5-54 Alerts log

There are eight different views. Each of them will show only the Alerts related to the selected
view except:
All view - Shows all Alerts
Alerts Directed to <logged user> - Shows all Alerts where the current logged user has
been specified in the Login notification field

When you click on the icon on the left of a listed Alert, you will see detailed information on the
selected Alert as shown in Figure 5-55.


Figure 5-55 Detailed Alert information

5.3 Policy management
The Policy Management functions of Tivoli Storage Resource Manager enable you to:
Define a filesystem extension policy can be used to automatically increase filesystem
capacity for managed hosts when utilization reaches a specified level. The LUN
provisioning option can be enabled to extend filesystems within an ESS.
Define space limits (Quotas) on storage resources used by user IDs and user groups. This
limits can be set at a network (whole environment) at a computer and at a filesystem level.
To define space limits (Quotas) on NAS resources used by user IDs and user groups
To perform checks (Constraints) on specific files owned by the users and perform any
action on those files
To schedule scripts against your storage resources

5.3.1 Filesystem extension and LUN provisioning
The main functions of Filesystem Extension are shown in Figure 5-56.


Tivoli Storage Resource Manager Filesystem Extension

Automates filesystem extension

Supported platforms
AIX using JFS
SUN using VxFS

Support for automatic LUN provisioning with IBM ESS Storage
Subsystem

Actions triggered through standard Alerting mechanism when
a filesystem is performed

ibm.com/redbooks

Figure 5-56 Filesystem Extension

We use filesystem extension policy to automatically extend filesystems when utilization
reaches a specified threshold. We can also enable LUN provisioning to extend filesystems
within an ESS.

To setup filesystem extension policy, select IBM Tivoli SRM -> Policy Management ->
Filesystem Extension. Right click on Filesystem Extension and select Create Filesystem
Extension Rules. The screen in Figure 5-57 displays.


Figure 5-57 Filesystem tab

In the Filesystems tab, select the filesystems which will use filesystem extension policy by
moving them to the Current Selections panel. In Figure 5-57 we selected the /opt filesystem.

Note the Enabled checkbox - the default is to check it, meaning the rule will be active. If you
uncheck the box, it will toggle to Disabled - you can still save the rule, but the job will not run.

To specify the extension parameters, select the Extension tab (Figure 5-58).

Figure 5-58 Extension tab

This tab specifies how a filesystem will be extended. Here are the fields.

Amount to Extend
We have the following options:


Add - the amount of space used for extension in MB or GB, or as a percentage of
filesystem capacity.
Make Freespace - the amount of freespace that will be maintained in the filesystems by
this policy. If freespace falls below the amount that is specified, the difference will be
added. Freespace can be specified in MB or GB increments, or by a percentage of
filesystem capacity.
Make Capacity - the total capacity that will be maintained in the selected filesystems. If
the capacity falls below the amount specified, the difference will be added.

Limit Maximum Filesystem Capacity?
When this option is enabled, the Filesystem Maximum Capacity is used in conjunction with
the Add or Make Freespace under Amount to Extend. If you enter a maximum capacity for a
filesystem in the Filesystem Maximum Capacity field, if a filesystem reaches the specified
size, the filesystem will be removed from the policy and an Alert will be triggered.

Condition for Filesystem Extension
The options are:
Extend filesystems regardless of remaining freespace - the filesystem will be
expanded regardless of the available free space.
Extend filesystems when freespace is less than - defines the threshold for the
freespace which will be used to trigger the filesystem expansion. If freespace falls below
this value, the policy will be executed. Freespace can be specified in MB or GB
increments, or by a percentage of filesystem capacity.

Note: If you select Make Capacity under Amount to Extend, the Extend filesystems
when freespace is less than option is not available.

Use LOG ONLY Mode
Enable Do Not Extend Filesystems - Log Only when you want the policy to log the
filesystem extension. The extension actions that would have taken place are written to the log
file, but no extension takes place.

In the Provisioning tab (Figure 5-59) we define LUN provision parameters. Note that LUN
provisioning is available at the time of writing for filesystems on an ESS only.


Figure 5-59 LUN provisioning tab

LUN Provisioning is an optional feature for filesystem extension. When the Enable
Automatic LUN Provisioning is selected, LUN provisioning is enabled.

In the Create LUNs that are at least field, you can specify a minimum size for new LUNs. If
you select this option, LUNs of at least the size specified will be created. If no size is
specified, then the Amount to Extend option specified for the filesystem (in “Amount to
Extend” on page 202) will be used. For more information on LUN provisioning, see IBM Tivoli
Storage Resource Manager 1.2 User’s Guide.

The Model for New LUNs feature means that new LUNs will be created similar to existing
LUNs in your setup. At least one ESS LUN must be currently assigned to the Tivoli Storage
Resource Manager Agent associated with the filesystem you want to extend. There are two
options for LUN modeling:
Model new LUNs on others in the volume group of the filesystem being extended -
provisioned LUNS are modeled on existing LUNs in the extended filesystem’s volume
group.
Model new LUNs on others on the same host as the filesystem being extended -
provisioned LUNS are modeled on existing LUNs in the extended filesystem’s volume
group. If the corresponding LUN model cannot satisfy the requirements. it will look for
other LUNs on the same host.

The LUN Source option defines the location of the new LUN in the ESS, and has two options:
Same Storage Pool - provisioned LUNs will be created using space in an existing Storage
Pool. In ESS terminology this is called the Logical Sub System or LSS.
Same Storage Subsystem - provisioned LUNs can be created in any Storage Pool or
ESS LSS.

The When to Enforce Policy tab (Figure 5-60) specifies when to apply the filesystem
extension policy to the selected filesystems.


Figure 5-60 When to Enforce Policy tab

The options are:

Enforce Policy after every Probe or Scan automatically enforces the policy after every
Probe or Scan job. The policy will stay in effect until you either change this setting or disable
the policy.

Enforce Policy Now enforces the policy immediately for a single instance.

Enforce Policy Once at enforces the policy once at the specified time, specifying the month,
day, year, hour, minute, and AM/PM

The Alert tab (Figure 5-61) can define an Alert that will be triggered by the filesystem
extension job.


Figure 5-61 Alert tab

Currently the only available condition is A filesystem extension action started
automatically.

Refer to “Alerts tab” on page 176 for an explanation of the definitions.

Important: After making configuration changes to any of the above filesystem extension
options, you must save the policy, as shown in Figure 5-62. If you selected Enforce Policy
Now, the policy will be executed after saving.


Figure 5-62 Save filesystem changes

The following sections show examples of the filesystem expansion function.

Expanding the filesystem in rootvg (no LUN provisioning)
This example shows expanding the /opt filesystem in the root volume group. The current
filesystem contents are shown in Example 5-3.

Example 5-3 Status of the filesystems before expansion
# df -k
Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
/dev/hd4 32768 17468 47% 1594 10% /
/dev/hd2 1277952 339112 74% 29161 10% /usr
/dev/hd9var 49152 40184 19% 468 4% /var
/dev/hd3 344064 167648 52% 7018 9% /tmp
/dev/hd1 16384 15820 4% 18 1% /home
/proc - - - - - /proc
/dev/hd10opt 65536 55904 15% 387 3% /opt
/dev/lv00 524288 63472 88% 38169 30% /essfs1
#

/opt has 64 MB and 15% used space. We created a new Filesystem Expansion rule - IBM
Tivoli SRM -> Policy Management -> Filesystem Extension. Right click on Filesystem
Extension and select Create Filesystem Extension Rules. We selected the /opt filesystem
as shown in Figure 5-63.


Figure 5-63 Selected filesystem

In the Extension tab we specified the following values as shown in Figure 5-64:
Extend the filesystem by 64MB
Extend filesystem regardless of remaining freespace

Figure 5-64 Extension parameters

We do not need to define anything in the Provisioning tab as the rootvg is not on an ESS. In
When to Enforce Policy we specified Enforce policy: Now, this means that the policy will be
executed only once.

Under Alert, we chose to send an SNMP trap and TEC event when a filesystem extension
action was triggered as shown in Figure 5-65.


Figure 5-65 Alert definition

After all the data is entered we save the rule, calling it opt extension. The new definition is
now shown in the menu tree as in Figure 5-66.

Figure 5-66 Rule for /opt extension

We now execute the rule by right clicking on it and selecting Run Now. In Figure 5-67 you can
see the successful extension of the /opt filesystem.


Figure 5-67 Successful extension

By clicking on the spyglass, you can examine the log of the action, as shown in Figure 5-68.

Figure 5-68 Extension log file

In Example 5-4 we show the filesystem information after expansion.

Example 5-4 Status of the FSes after expansion
# df -k
/dev/hd4 32768 17468 47% 1594 10% /
/dev/hd2 1277952 339100 74% 29164 10% /usr
/dev/hd9var 49152 40180 19% 468 4% /var


/dev/hd3 344064 167648 52% 7018 9% /tmp
/dev/hd1 16384 15820 4% 18 1% /home
/proc - - - - - /proc
/dev/hd10opt 262144 246248 7% 387 1% /opt
/dev/lv00 2686976 2158280 20% 38169 6% /essfs1
#

As you can see from Figure 5-68 the policy was executed three times so the new filesystem
size should be 64 MB (original size) + 3 x 64 MB (the increment defined in extension policy) =
256 MB and this is the size which is displayed in Example 5-4.

Expanding the filesystem in volume group on ESS (LUN provisioning)
For this example we used a filesystem defined on a volume group, essvg1 using an ESS
LUN. Example 5-5 shows the volume group definition.

Example 5-5 essvg1 volume group definition
# lsdev -Cc disk
hdisk0 Available 10-80-00-4,0 16 Bit SCSI Disk Drive
hdisk1 Available 1P-18-01 IBM FC 2105F20
hdisk2 Available 1P-18-01 IBM FC 2105F20
vpath0 Available Data Path Optimizer Pseudo Device Driver
# lsvpcfg
vpath0 (Avail pv essvg1) 30918921 = hdisk1 (Avail ) hdisk2 (Avail )
#

The volume group is defined on the vpath0 device which represents an ESS LUN with serial
number 30918921. The vpath device is used as we have two paths to the physical LUN. See
the Subsystem Device Driver documentation for explanation of vpath device functionality.

The filesystem is mounted on /essfs1 and is defined on logical volume /dev/lv00 as shown in
Example 5-4. The command lslv lv00 shows the information about the logical volume,
including its containing volume group. See Example 5-6.

Example 5-6 Logical volume information for /dev/lv00
# lslv lv00
LOGICAL VOLUME: lv00 VOLUME GROUP: essvg1
LV IDENTIFIER: 0041f12b00004c00000000f5a9cf986f.1 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: jfs WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 64 megabyte(s)
COPIES: 1 SCHED POLICY: parallel
LPs: 96 PPs: 96
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 32
MOUNT POINT: /essfs1 LABEL: /essfs1
MIRROR WRITE CONSISTENCY: on/ACTIVE
EACH LP COPY ON A SEPARATE PV ?: yes
#

In Example 5-4 you can see the current /essfs1 filesystem size which is 2.56GB.

We will now define the Filesystem Expansion Rule following the steps in “Expanding the
filesystem in rootvg (no LUN provisioning)” on page 207.


We selected /essfs1 as the filesystem for expansion as shown in Figure 5-69.

Figure 5-69 /essfs1 filesystem expansion definition

The Extension parameters are shown in Figure 5-70.

Figure 5-70 Extension parameters for /essfs1 FS

We defined to add 2GB on each expansion, which will trigger when the filesystem has less
than 75% free space.

As the volume group is on an ESS, we defined Provisioning parameters (Figure 5-71).


Figure 5-71 Provisioning parameters

We defined to model the LUNs on LUNs which are already in the volume group, and to create
them anywhere in the ESS.

In When to Enforce Policy we specified Enforce policy: Now, this means that the policy will
be executed only once or when we will manually run it.

In the Alert tab we defined to send an SNMP trap and TEC event when a filesystem extension
action was triggered.

We saved the rule and called it essfs1 extension.

Now we create some data to fill the disk. Example 5-7 shows /essfs1 at 80% utilization.

Example 5-7 essfs1 filled up
# df -k
/dev/hd4 32768 17468 47% 1594 10% /
/dev/hd2 1277952 339100 74% 29164 10% /usr
/dev/hd9var 49152 40180 19% 468 4% /var
/dev/hd3 344064 167648 52% 7018 9% /tmp
/dev/hd1 16384 15820 4% 18 1% /home
/proc - - - - - /proc
/dev/hd10opt 262144 246248 7% 387 1% /opt
/dev/lv00 2686976 556704 80% 38171 6% /essfs1
#

Now we run the filesystem extension policy. Figure 5-72 shows the filesystem extension was
successfully completed, extending /essfs1 by 2GB.


Figure 5-72 Filesystem extension on /essfs1 filesystem

The df -k output also shows the difference as in Example 5-8. The new size is 4.56GB.

Example 5-8 /essfs1 filesystem after expansion
# df -k
/dev/hd4 32768 17468 47% 1594 10% /
/dev/hd2 1277952 339100 74% 29164 10% /usr
/dev/hd9var 49152 40180 19% 468 4% /var
/dev/hd3 344064 167648 52% 7018 9% /tmp
/dev/hd1 16384 15820 4% 18 1% /home
/proc - - - - - /proc
/dev/hd10opt 262144 246248 7% 387 1% /opt
/dev/lv00 4784128 2588024 46% 38171 4% /essfs1
#

As the /essfs1 free space is still below 75%, we ran the rule again and the filesystem was
expanded again. The result can be seen in Example 5-9.

Example 5-9 /essfs1 after second expansion
# df -k
/dev/hd4 32768 17468 47% 1594 10% /
/dev/hd2 1277952 339100 74% 29164 10% /usr
/dev/hd9var 49152 40180 19% 468 4% /var
/dev/hd3 344064 167648 52% 7018 9% /tmp
/dev/hd1 16384 15820 4% 18 1% /home
/proc - - - - - /proc
/dev/hd10opt 262144 246248 7% 387 1% /opt


/dev/lv00 6881280 4619352 33% 38171 3% /essfs1
#

The new size is 6.56GB. Until now, the filesystem expansion did not require a new LUN as the
existing LUN for the essvg1 volume group was 8GB, as shown with the command lspv
vpath0 in Example 5-10.

Example 5-10 vpath0 LUN size
# lspv vpath0
PHYSICAL VOLUME: vpath0 VOLUME GROUP: essvg1
PV IDENTIFIER: 0041f12ba9cf89ec VG IDENTIFIER 0041f12b00004c00000000f5a9cf986f
PV STATE: active
STALE PARTITIONS: 0 ALLOCATABLE: yes
PP SIZE: 64 megabyte(s) LOGICAL VOLUMES: 2
TOTAL PPs: 126 (8064 megabytes) VG DESCRIPTORS: 2
FREE PPs: 20 (1280 megabytes) HOT SPARE: no
USED PPs: 106 (6784 megabytes)
FREE DISTRIBUTION: 00..00..00..00..20
USED DISTRIBUTION: 26..25..25..25..05
#

As the /essfs1 free space is still below 75% we ran the rule again and the filesystem was
expanded again. The result can be seen in Example 5-11.

Example 5-11 /essfs1 after third expansion
# df -k
/dev/hd4 32768 17460 47% 1601 10% /
/dev/hd2 1277952 339084 74% 29166 10% /usr
/dev/hd9var 49152 40072 19% 468 4% /var
/dev/hd3 344064 167648 52% 7018 9% /tmp
/dev/hd1 16384 15820 4% 18 1% /home
/proc - - - - - /proc
/dev/hd10opt 262144 246248 7% 387 1% /opt
/dev/lv00 8978432 6650672 26% 38171 2% /essfs1
#

The partial log file for the third expansion is shown in Figure 5-73.


Figure 5-73 LUN provisioning for /essfs1 filesystem

As shown in the log, a new LUN of 2GB was required to accommodate another filesystem
expansion. After the provisioning the ESS LUN, it was added to the essvg1 volume group and
the filesystem was expanded as shown in Example 5-11 on page 215.

The lsvpcfg command shows the new LUN in the essvg1 volume group (Example 5-12).

Example 5-12 New LUN in essvg1 volume group
# lsvpcfg
#

the lspv vpath1 command shows the physical attributes of the new LUN (Example 5-13).

Example 5-13 New LUN attributes
# lspv vpath1
PHYSICAL VOLUME: vpath1 VOLUME GROUP: essvg1
PV IDENTIFIER: 0041f12bc3650604 VG IDENTIFIER 0041f12b00004c00000000f5a9cf986f
PV STATE: active
STALE PARTITIONS: 0 ALLOCATABLE: yes
PP SIZE: 64 megabyte(s) LOGICAL VOLUMES: 1
TOTAL PPs: 32 (2048 megabytes) VG DESCRIPTORS: 1
FREE PPs: 20 (1280 megabytes) HOT SPARE: no
USED PPs: 12 (768 megabytes)
FREE DISTRIBUTION: 07..00..00..06..07
USED DISTRIBUTION: 00..06..06..00..00
#


The size of the newly created LUN was as specified in the filesystem expansion rule. Even
though we selected to model LUNs after existing LUNs in the volume group, the size was
defined by the filesystem expansion as it is not part of the modeling algorithm.

Tip: If you wish to maintain the same LUN size in the volume group, it is recommended to
match the filesystem expansion size to the size of the LUNs used in volume group.

From the new LUN serial number 20018921 as shown in Example 5-12 we can see that it was
created in a different Storage Pool or LSS inside the ESS. The original LUN was in LSS 0x13
(as identified by serial number which starts with 3xx) and the new one is in LSS 0x12 (as
identified by serial number starting with 2xx). The reason for the new LUN being created in
another LSS is that the original LSS is full, therefore there is no space for new LUNs. We
selected the option to create new LUNs anywhere in the ESS in our expansion rule. You can
see the physical representation of LUNs from the ESS Specialist in Figure 5-74.

LSS 0x12

LSS 0x12 LSS 0x13

Figure 5-74 ESS LUNs for filesystem expansion

On this screen, the selected icon with label 43P_0 represents the host definition in the ESS
for the server which was used in the LUN provisioning example in this section.

5.3.2 Quotas
The main functionality of Quotas are displayed in Figure 5-75.


Tivoli Storage Resource Manager User Quotas
Help monitor space used by users and user groups

Quotas can be set for
the whole network
specific computers
specific filesystems

a quota is exceeded

ibm.com/redbooks

Figure 5-75 Quotas

Quotas can be set at either a user or at an OS User Group level. For the OS User Group level,
this could be either an OS User Group, (see “OS User Group Groups” on page 171), or a
standard OS group (such as system on UNIX, or Administrators on Windows). The User
Quotas trigger an action when one of the monitored users has reached the limit while the OS
User group Quotas trigger the action when the sum of space used by all users of monitored
groups has reached the limit. The Quotas definition mechanism is the same for both except
for:
The menu tree to use:
– IBM Tivoli SRM -> Policy Management -> Quotas -> User
– IBM Tivoli SRM -> Policy Management -> Quotas -> OS User group
The monitored elements you can specify:
– User and user groups for User Quotas
– OS User Group and OS User Group Groups for OS User Group Quota

We will show how to configure User Quotas. User Group Quotas are configured similarly.

Note that the Quota enforcement is soft - that is, users are not automatically prevented from
exceeding their defined Quota, but the defined actions will trigger if that happens. There are
three sub-entries for Quotas: Network Quotas, Computer Quotas, and Filesystem Quotas

Network Quotas
A Network Quota defines the maximum cumulated space a user can occupy on all the
scanned servers. An Alert will be triggered for each user that exceeds the limit specified in the
Quota definition.


Use IBM Tivoli SRM -> Policy Management -> Quotas -> User -> Network, right-click and
select New Quota to create a new Quota. The right pane displays the Quota configuration
screen with four tabs.

Users tab
Figure 5-76 shows the Users tab for Network Quotas.

Figure 5-76 User Network Quotas - Users tab

From the Available column, select any user ID or OS User Group you want to monitor for
space usage.

The Profile pull-down menu is used to specify the file types that will be subject to the Quota.
The list will display all Profiles that create summaries by user (by file owner). Select the Profile
you want to use from the pull-down. The default Profile Summary by Owner collects
information about all files and summarizes them on the user level. The ALLGIFFILES profile
collects information about GIF files and creates a summary at a user level as displayed in
Figure 5-77. This (non-default) profile was created using the process shown in 5.1.6,
“Profiles” on page 180.


Figure 5-77 Profile with user summary

Using this profile option, we can define general Quotas for all files and more restrictive
Quotas for some multimedia files such as GIF and MP3.

Filesystem tab
On the Filesystem tab shown Figure 5-78, select the filesystems or computers you want to be
included in the space usage for Quota management.

Figure 5-78 User Network Quotas - Filesystem tab

In this configuration, for each user, his cumulated space usage on all servers will be
calculated and checked against the Quota limit.


When to check
The Quota management is based on the output of the Scan jobs. Therefore, each Quota
definition must be scheduled to run after the Scan jobs that collect the adequate information.

The When to CHECK tab is standard, and allows you to define a one off or a recurring job.

Alert tab
On the Alert tab, specify the Quota limit in: KB, MB or GB, and the action to run when the
Quota is exceeded.

Figure 5-79 User Network Quotas - Alert tab

You can choose from the standard Alerts type available with Tivoli Storage Resource
Manager. Each Alert will be fired once for each user exceeding their Quota. We have selected
to run a script that we wrote, QUOTAUSERNET.BAT, listed in Example 5-14.

Example 5-14 QUOTAUSERNET.BAT script
echo NETWORK quota exceeded - %1 %2 uses %3 - Limit set to %4 >>quotausernet.txt

Example 5-15 shows the output file created by QUOTAUSERNET.BAT.

Example 5-15 Content of quotausernet.txt
NETWORK quota exceeded - user root uses 8.22GB - Limit set to 5.0GB
NETWORK quota exceeded - user Administrators@BUILTIN uses 9.61GB - Limit set to 5.0GB

The Alert has fired for user root and Administrators. This clearly shows that administrative
users such as root and Administrators should not normally be included in standard Quotas
monitoring.


Computer Quotas
Computer Quotas enable you to fire Alerts when a user exceeds their space Quota on a
specific computer. Multiple Alerts are generated if a user violates the Quota on separate
computers as shown in Figure 5-80.

Figure 5-80 Computer Quota - Alerts log

Here, we received an Alert that the root user exceeded the Quota on the computers CRETE,
SOL-E, BRAZIL, and EASTER. Another Alert was generated for user itso_hb, because it
exceeded the Quota on the system BRAZIL.

Filesystem Quotas
A Filesystem Quota defines a space usage limit at the filesystem level. An Alert will be fired
for each filesystem where a user exceeds the limit specified in the Quota definition.

Use IBM Tivoli SRM -> Policy Management -> Quotas -> User -> Filesystem, right-click,
and select New quota to create a new Quota. After setting up and running a Quota for
selected filesystems, we received the following entries in the Alert History, shown in
Figure 5-81.


Figure 5-81 Filesystem Quota - Alerts log

We see that four Alerts have been fired for CRETE:
User bin on /usr
User root on /
User root on /tmp
User root on /user

We also see down to the filesystem level on BRAZIL for the user itso_hb, who generated an
Alert in “Computer Quotas” on page 222.

5.3.3 Network Appliance Quotas
Using IBM Tivoli SRM -> Policy Management -> Network Appliance Quotas ->
Schedules, you can compare the space used by users against Quotas defined inside
Network Appliance filers, using the appropriate software, and raise an Alert whenever a user
is close to reaching the NetApp Quota.

When you run a Network Appliance Quota job, the NetApp Quota definitions will be imported
into Tivoli Storage Resource Manager for read-only purposes.

Note: Network Appliance Quotas jobs must be scheduled after the Scan jobs, since they
use the statistics gathered by the latest Scan to trigger any NetApp Quota violation.

With IBM Tivoli SRM -> Policy Management -> Network Appliance Quotas -> Imported
User Quotas and Imported OS User Group Quotas, you can view the definitions of the
Quotas defined on your NetApp filers.


5.3.4 Constraints
The main features of Constraints are displayed in Figure 5-75.

Tivoli Storage Resource Manager Constraints
Reports and triggers actions based on specific files which use
too much space on monitored servers

Files can be selected based on
server and filesystem
name pattern (eg: *.mp3, *.avi)
owner
age
size
attributes

total space used by files exceeds a threshold

ibm.com/redbooks

Figure 5-82 Constraints

Constraints are used to generate Alerts when files matching specified criteria are consuming
too much space on the monitored servers.

Constraints provide a deeper level of Storage Resource Management. Quotas will allow
reporting on users who have exceeded their space limitations. With Constraints, we can get
more detailed information to specify limits on particular file types or other attributes, such as
owner, age, and so on. The output of a Constraint when applied to a Scan will return a list of
the files that are consuming too much space.

Note: Unlike Quotas, Constraints are automatically checked during Scan jobs and do not
need to be scheduled. Also, the Scan does not need to be associated with Profiles that will
cause data to be stored for reporting.

Filesystems tab
This Filesystems tab helps you to select the computers and filesystems you want to be
checked for the current Constraint. The selection method for computers and filesystems is the
same as for Scan jobs (see 5.1.7, “Scans” on page 185).

File Types tab
On the File Types tab, you can explicitly allow or disallow certain file patterns (Figure 5-83).


Figure 5-83 Constraint - File Types

Use the buttons on the top of the screen, to allow or forbid files depending on their name. The
left column shows some default file patterns, or you can use the bottom field to create your
own pattern. Click >> to add your pattern to the allowed/forbidden files.

Users tab
The Users tab (figured in Figure 5-84) is used to allow or restrict the selected users in the
Constraint.

Figure 5-84 Constraint - Users


Important: The file condition is logically ORed with the User condition. A file will be
selected for Constraint processing if it meets at least one of the conditions.

Options tab
The Options tab provides additional conditions for file selection, and limits the number of
selected files to store in the central repository.

Once again, the conditions added in the tab will be logically ORed with the previous set in the
File Types and Users tab.

The bottom part of the tab, shown in Figure 5-85, contains the textual form of the Condition,
taking into account all the entries made in the Filesystems, File Types, Users and Options
tabs.

Figure 5-85 Constraints - Options

You can change this condition or add additional conditions, by using the Edit Filter button. It
displays the file filter popup (Figure 5-86) to change, add, and remove conditions or
conditions groups as previously explained in 5.1.6, “Profiles” on page 180.


Figure 5-86 Constraints - File filter

We changed the file filter to a more appropriate one by changing the OR operator to AND.

Figure 5-87 Constraints - File filter changed

Alert tab
After selecting the files, you may want to generate an Alert only if the total used space
meeting the Constraint conditions exceeds a predefined limit. Use the Alert tab to specify
the triggering condition and action.


Figure 5-88 Constraints - Alert

In our Constraint definition, a script is triggered for each filesystem where the selected files
exceed one Gigabyte. We select the script by checking the Run Script option and selecting
Define ... as shown in Figure 5-89. The script will be passed several parameters including a
path to a file that contains the list of files meeting the Constraint. You can use this list to
execute any action including delete or archive commands.

Figure 5-89 Constraints - Script parameters


Our example uses a sample script (tsm_arch_del.vbs) which is shipped with Tivoli Storage
Resource Manager, which archives all the files in the produced list to a Tivoli Storage
Manager server, and then deletes them from local storage. This script is installed with the
Tivoli Storage Resource Manager server, and stored in the scripts subdirectory of the server
installation. It can be edited or customized if required - we recommend that you save the
original files first. Versions for Windows (tsm_arch_del.vbs) and UNIX (tsm_arch_del) are
provided. If you will run this Constraint on a UNIX agent, then PERL is required to be installed
on the agent. A Tivoli Storage Manager server must be available and configured for this script
to work. For more information on the sample scripts, see Appendix A of the IBM Tivoli Storage
Resource Manager User’s Guide, SC32-9069.

5.3.5 Scheduled actions
Figure 5-90 shows the main functionality of Scheduled actions.

Tivoli Storage Resource Manager Scheduled actions
Scheduling tool

Allow automated script execution
on selected computers
on selected computer groups

Alert raised when a script fails

ibm.com/redbooks

Figure 5-90 Scheduled actions

Tivoli Storage Resource Manager comes with an integrated tool to schedule script execution
on any of the Agents. If a script fails due to an unreachable Agent, the standard Alert
processes can be used. To create a Scheduled action, select Scheduled Actions -> Scripts,
and right-click on New Script.

Computers tab
On the Computers tab, select the computers or computer groups to execute the script.

Script Options tab
From the pull-down field, select a script that exists on the server. You can also enter the name
of a script not yet existing on the server or that only resides on the Agents.


See 3.2.2, “Scripts” on page 51 for an explanation of server/Agent scripts execution rules.

The Script options tab is shown in Figure 5-91.

Figure 5-91 Scheduled action - Script options

The Script Name pull-down field lists all files (including non-script files) in the servers’ script
directory.

Attention: For Windows Agents, the script must have an extension that has an associated
script engine on the computer running the script (for example: .BAT, .CMD, or .VBS).

For UNIX Agents:
The extension is removed from the specified script name
The path to the shell (for example, /bin/bsh, /bin/ksh) must be specified in the first line of
the script
If the script is located in a Windows Tivoli Storage Resource Manager Server scripts
directory, the script must have been created on a UNIX platform, and then transferred in
binary mode to the Server or you can use UNIX OS tools such as dos2unix to convert
the scripts. This will ensure that the CR/LF characters are correctly inserted for
execution under UNIX.

When to Run tab
As for other Tivoli Storage Resource Manager jobs, you can choose to run a script once or
repeatedly at a predefined interval.

Alerts tab
With the Alert tab you can choose to be notified when a script fails due to an unreachable
Agent or a script not found condition. The standard Alert Mechanism described in 5.2, “OS
Alerts” on page 189 is used.

5.4 Database monitoring
The Monitoring functions of Tivoli Storage Resource Manager are extended to databases
when the license key for Tivoli Storage Resource Manager for Databases is enabled.
Currently, MS SQL-Server, Oracle, DB2, and Sybase are supported.


We will now review the Groups, Probes, Scans, and Profiles definitions for Tivoli Storage
Resource Manager for Databases, and show the main differences compared to the core Tivoli
Storage Resource Manager monitoring functions.

Figure 5-92 shows the navigation tree for Tivoli Storage Resource Manager for Databases.

Figure 5-92 Databases - Navigation Tree

5.4.1 Groups
To get targeted monitoring of your database assets, you can create Groups consisting of:
Computers
Databases-Tablespaces
Tables
Users

Computer Groups
All databases residing on the selected computers will be probed, scanned, and managed for
Quotas.

The groups you have created using Tivoli Storage Resource Manager remain available for
Tivoli Storage Resource Manager for Databases. If you create a new Group, the computers
you put in it will be removed from the Group they currently belong to.

To create a Computer Group, use IBM Tivoli SRM for Databases -> Monitoring -> Groups
-> Computer, right-click, and select New Group.

“Computer Groups” on page 163 gives more information on creating Computer Groups.

Databases-Tablespaces Groups
Creating Groups with specific databases and tablespaces may be useful for applying identical
management rules for databases with the same functional role within your enterprise.


An example could be to create a group with all the SQL-Server system databases, as you will
probably apply the same rules for space and alerting on those databases. This is shown in
Figure 5-93.

Figure 5-93 Database group definition

Table Groups
You can use Table Groups to create Groups of the same set of tables for selected or all
database instances.

You can use two different views to create a table group:
Tables by instance selects several tables for one instance.
Instances by table selects several instances for one table.

You can combine both views as each entry you add will be added to the group.

User Groups
As for core Tivoli Storage Resource Manager, you can put user IDs in groups. The user
groups you create will be available for the whole Tivoli Storage Resource Manager product
set.

Tip: The Oracle and MS SQL-Server user IDs (SYSTEM, sa, ...) are also included in the
available users list after the first database Probe.

5.4.2 Probes
The Probe process is used to gather data about the files, instances, logs, and objects that
make up monitored databases. The results of Probe jobs are stored in the repository and are
used to supply the data necessary for Asset Reporting.

Use IBM Tivoli SRM for Databases -> Monitoring -> Probe, right-click, and select New
probe to define a new Probe job. In the Instance tab of the Probe configuration, you can
select specific instances, computers, and computer groups.


Figure 5-94 Database Probe definition

The Computers list contains only computers that have been licensed for Tivoli Storage
Resource Manager for Databases. The product licensing procedure is described in “License
Keys” on page 108.

5.4.3 Profiles
As for Tivoli Storage Resource Manager, Profiles in Tivoli Storage Resource Manager for
Databases are used to determine the databases attributes that are to be scanned. They also
determine the summary level and retention time to keep in the repository.

Use IBM Tivoli SRM for Databases - Monitoring - Profile, right-click, and select New
profile to define a new profile. Figure 5-95 shows the Profile definition screen.

Figure 5-95 Database profile definition


You can choose to gather data on tables size, database extents, or database free space and
summarize the results at the database or user level.

5.4.4 Scans
Scan jobs in Tivoli Storage Resource Manager for Databases collect statistics about the
storage usage and trends within your databases. The gathered data is used as input to the
usage reporting and Quota analysis.

Defining a Scan job requires defining:
The database, computer, and instances to Scan
The tables to monitor for detailed information such as size, used space, indexes, rows
count
The profile that will determine the data that is gathered and the report views that will be
made available by the Scan
The job scheduling frequency
Oracle-only additional options to gather information about pages allocated to a segment
that has enough free space for additional rows
The alerting mechanism to use should the Scan fail

All this information is set through the Scan definition screen that contains one tab for each
previously listed item. To define a new Scan, select IBM Tivoli SRM for Databases ->
Monitoring -> Scan, right-click and select New scan as in Figure 5-96.

Figure 5-96 Database Scan definition

Note: If you request detailed scanning of tables, the tables will only be scanned if their
respective databases have also been selected for scanning.


5.5 Database Alerts
Tivoli Storage Resource Manager for Databases enables you to define Alerts on instances,
databases, and tables. The Probe and Scan jobs output are processed and compared to the
defined alerts. If a threshold is reached, an Alert will be triggered.

Tivoli Storage Resource Manage for Databases uses the standard Alert mechanisms
described in 5.2, “OS Alerts” on page 189.

5.5.1 Instance Alerts
IBM Tivoli SRM for Databases -> Alerting -> Instance Alerts, right-click and select New
alert lets you define some alerts as shown in Table 5-3. Those Alerts are triggered during the
Probe process.

Table 5-3 Instance Alerts
Alert type Oracle Sybase MSSQL

New database discovered x x

New tablespace discovered x

Archive log contains more than X units x

New device discovered x

Device dropped x

Device free space greater than X units x

Device free space less than X units x

An interesting Alert is the Archive log contains more than for Oracle, since the Oracle
application can hang if there is no more space available for its archive log. This Alert can be
used to monitor the space used by in this specific directory and trigger a script that will
archive the files to an external manager such as Tivoli Storage Manager once the predefined
threshold is reached. Here is the procedure:
1. We defined an Instance Alert and selected the Archive log contains more than
condition. We also specified that the script ARCHORA.BAT must be executed when the
Alert is fired. Note the parameters passed to the script.


Figure 5-97 Instance Alert definition

2. As the archive command must run on the server where Oracle resides, we set Triggering
Computer in the Where to run pull-down field. This does not means that the script must be
physically copied on the monitored server.
3. On the Instance tab, we selected our Oracle server (GALLIUM) and we saved the Alert as
ArchiveOracleLog.

Example 5-16 shows a sample script which we have written, ARCHORA.BAT, which will
archive the Oracle logs to a Tivoli Storage Manager server, and then delete them after
archive. It assumes you already have a Tivoli Storage Manager Server and client defined and
configured for your environment. Note this is a sample only, and should be customized and
tested for your environment.

Example 5-16 ARCHORA.BAT - Archive to TSM script
@ECHO OFF
REM Display starting messages
REM -------------------------
echo ARCHORA.BAT starting ...
echo on server %2
echo to archive %3 logs for instance %4
echo Directory to process : %1
echo Expecting %5 files to be archived for a total size of %6

REM Perform basic checks on db type and directory
REM ---------------------------------------------
if not %3 == Oracle GOTO NOTORACLE
if not exist %1 GOTO DIRNOTEXIST

REM Execute archive TSM command
REM ---------------------------
set logfile=ARCHORA.LOG
CD C:Program filesTivolitsmbaclient


@echo on
dir %1ARC*.*
dsmc archive %1ARC*.* -subdir=no -delete -descr="%2 %3 %4 ArchiveLogs" -verbose
@echo off
if not %errorlevel% == 0 GOTO DSMCERROR

@echo on
dir %1ARC*.*
echo ARCHORA.BAT ended successfully ...
exit 0

:NOTORACLE
echo Error - Not Oracle database
exit 4
:DIRNOTEXIST
echo Error - Directory does not exist
exit 4
:DSMCERROR
echo Error while running DSMC command
dir %1ARC*.*
type dsmerror.log

When the Probe job is run against the GALLIUM server, an Alert is fired. You can see its
output in Figure 5-98.

Figure 5-98 Instance Alert output

5.5.2 Database-Tablespace Alerts
To define a Database-Tablespace Alert, select IBM Tivoli SRM for Databases -> Alerting ->
Database-Tablespace Alerts, right-click, and select New alert. You can define various
monitoring options on your databases as shown in Table 5-3. Those Alerts are triggered
during the Probe process.


Table 5-4 Instance alerts
Alert type Oracle Sybase MSSQL

Database/Tablespace freespace lower than x x x

Database/Tablespace offline x x x

Database/Tablespace dropped x x x

Freespace fragmented in more than n extents x

Largest free extent lower than x

Database Log freespace lower than x x

Last dump time previous to n days x

To avoid a Log Full condition, we will define an Alert to monitor log usage on our MS
SQL-Server database. When the log reaches 70% utilization, the Alert will trigger and
perform a backup of the transaction log.

Figure 5-99 Database alert definition

The script specified is SQLBKPLOG.BAT, listed in Example 5-17.

Example 5-17 MSSQL Log backup utility
@ECHO OFF
REM -------------------------
echo SQLBKPLOG.BAT starting ...
echo on server %2
echo Transaction log of %3 database %4/%1 reaches %7 of its capacity
echo Performing transaction log backup



REM ---------------------------------------------
if not %3 == "MicroSoft SQL/Server" GOTO NOTSQL

REM Execute backup command
REM ----------------------
CD C:Program FilesMicrosoft SQL ServerMSSQLBackup
echo Current Log backups
echo -------------------
dir %1_Tlog*
cd ..binn
@echo on
sqlmaint -D %1 -BkUpLog -BkUpMedia DISK -UseDefDir
if not %errorlevel% == 0 GOTO SQLERROR
@echo off
echo New Log backups
echo ---------------
cd ..Backup
dir %1_Tlog*
echo SQLBKPLOG.BAT ended successfully ...
exit 0

:NOTSQL
echo Error - Not MSSQL database
exit 4
:SQLERROR
echo Error while running SQLMAINT command
exit 4

Example 5-18 shows the output of the Alert log.

Example 5-18 Alert log output
09-18 16:36:25 AGT0133I: Running Command:
BKPSQLLOG.BAT Northwind gallium "MicroSoft SQL/Server" gallium 525.0KB 80% 51.27%
--------------------- BEGIN OUTPUT ---------------------
SQLBKPLOG.BAT starting ...
on server gallium
Transaction log of "MicroSoft SQL/Server" database gallium/Northwind reaches 51.27% of
its capacity
Performing transaction log backup
Current Log backups
-------------------
Volume in drive C has no label.
Volume Serial Number is 3C32-1025

Directory of C:Program FilesMicrosoft SQL ServerMSSQLBACKUP

09/18/2002 02:28p 82,432 northwind_tlog_200209181428.BAK
09/18/2002 03:21p 82,432 Northwind_tlog_200209181521.BAK
8 File(s) 656,384 bytes
0 Dir(s) 10,313,953,280 bytes free

C:Program FilesMicrosoft SQL ServerMSSQLBinn>sqlmaint -D Northwind -BkUpLog -BkUpMedia
DISK -UseDefDir


C:Program FilesMicrosoft SQL ServerMSSQLBinn>if not 0 == 0 GOTO SQLERROR
New Log backups
---------------
Volume in drive C has no label.
Volume Serial Number is 3C32-1025

Directory of C:Program FilesMicrosoft SQL ServerMSSQLBACKUP

9 File(s) 672,256 bytes
0 Dir(s) 10,313,867,264 bytes free
SQLBKPLOG.BAT ended successfully ...
---------------------- END OUTPUT ----------------------
09-18 16:36:26 AGT0131I: Exit Status = 0

5.5.3 Table Alerts
To define a new Table Alert, use IBM Tivoli SRM for Databases -> Alerting -> Table Alerts,
right-click, and select New alert. With this option you can set up monitoring on database
tables. The Alerts that can be triggered for a table are shown below. Those Alerts are
triggered during the Scan processes and only if the Scan includes a Table Group.

Table 5-5 Table alerts
Alert type Oracle Sybase MsSQL

Total Table Size Greater Than x x x

Table Dropped x x x

(Max Extents - Allocated) < x
Segment Has More Than x

Chained Row Count Greater Than x

Empty Used Segment Space Exceeds x

Forwarded Row Count Greater Than x

5.5.4 Alert log
The IBM Tivoli SRM for Database - Alerting - Alert log menu lists all Alerts that have been
fired by the Probe jobs, the Scan jobs, the defined Alerts, and the violated Quotas.

Tip: Please refer to 5.2.5, “Alert logs” on page 198 for more information about using the
Alert log tree.


5.6 Databases policy management
The Policy Management functions of Tivoli Storage Resource Manager for Databases enable
you to:
Define space limits (Quotas) on database space used by tables owners. Those limits can
be set at a network (whole environment), at an instance or at a database level.
Schedule scripts against your database resources

5.6.1 Network Quotas
A Network Quota will define the maximum cumulated space a user can occupy on all the
scanned databases. An Alert will be fired for each user that exceeds the limit specified in the
Quota definition.

We used IBM Tivoli SRM for Databases - Policy Management - Quotas - Network,
right-click and select New quota to create a new Quota. The right pane will switch to a Quota
configuration screen with four tabs.

Users tab
On the Users tab, specify the database users you want to be monitored for Quotas. You can
also select a profile in the Profile pull-down field on the top right of the tab. In this field, you
can select any Profile that stores summary data on a user level. The Quota will only be fired
for databases that have been scanned using this Profile.

Figure 5-100 Database Quota - Users tab

Database-Tablespace tab
Use this tab to restrict Quota checking to certain databases. You can choose several
databases or computers. If you choose a computer, all the databases running on it will be
included for Quota management.

When to run tab
As for Tivoli Storage Resource Manager, you can select the time to run from:
Immediate


Once at a schedule date and time
Repetitive at predefined intervals

Alert tab
On the Alert tab you can specify the space limit allowed for each user and the action to run. If
no action is selected, the Quota violation will only be logged in the Alert log.

5.6.2 Instance Quota
The Instance Quota mechanism is similar to the Network Quota, except that it is set at the
instance level. Whenever a user reaches the Quota on one instance, an Alert will be fired.

5.6.3 Database Quota
With Database Quota, the Quota is set at the database level. Each monitored user will be
reported back as soon as he reaches the limit on at least one of the monitored database.

5.7 Database administration samples
We now list some typical checks done regularly by Oracle database administrators and show
how they can be automated using Tivoli Storage Resource Manager for Databases.

5.7.1 Database up
Tivoli Storage Resource Manager for Databases can be used to test for database availability
using Probe and Scan jobs since they will fail and trigger an Alert if either the database or the
listener is not available. Since those jobs use system resources to execute, you may instead
choose scheduled scripts to test for database availability.

Due to limited scheduling options and the need for user-written scripts, we recommend using
dedicated monitoring products such as Tivoli Monitoring for Databases.

5.7.2 Database utilization
There are a number of different levels where system utilization can be monitored and checked
in a database environment.

Tablespace space usage
This is a standard Alert provided by Tivoli Storage Resource Manager for Databases. This
Alert will be triggered by the Probe jobs.

Archive log directory space usage
This is a standard alert provided by Tivoli Storage Resource Manager for Databases. This
Alert will be triggered by the Probe jobs as shown in 5.5.1, “Instance Alerts” on page 235.

Maximum extents used
Your application may become unavailable if a table reaches its maximum allowed number of
extents. This is an indicator that can be monitored using the (Max Events - Allocated Extents)
< Table Alert.


5.7.3 Need for reorganization
To ensure good application performance, it is important to be notified promptly if a database
reorganization is required.

Count of Used table extents
You can monitor for table reorganization need using the table Alert trigger Segment has more
than n extents.

Count of chained rows
Chained rows can have an impact on database access performance. This issue can be
monitored using the Chained Row Count Greater than table Alert trigger.

Count of Used table extents
You can monitor the need for table reorganization using the table Alert trigger Segment has
more than n extents.

Freelist count
You cannot monitor the count of freelists in an Oracle table using Tivoli Storage Resource
Manager for Databases.


Part 4

Part 4 Customizing and
advanced operations

This book part gives detailed procedures for using the reporting facilities of IBM Tivoli Storage
Resource Manager, plus information on backing up, restoring, and maintaining your IBM
Tivoli Storage Resource Manager environment.


6

Chapter 6. Reporting
This chapter discusses the following:
An overview of IBM Tivoli Storage Resource Manager’s reporting options
Using the supplied report definitions
Enterprise Storage Subsystem (ESS) reporting
– Prerequisite checking
– Creating a Probe
– Asset Reports
• By Storage Subsystems
– Storage Subsystem Reports
• Computer Views
• Storage Subsystem Views
Backup Reporting
Suggested list of Top 10 Reports
Customizing standard reports and saving the changes for later use
Setting up processes for generating daily reports


6.1 Tivoli Storage Resource Manager reporting capabilities

Tivoli Storage Resource Manager Reporting Capabilities

Powerful and flexible
Over 300 predefined views
Commonly used report criteria can be save for reuse
Reports can be scheduled to run regularly

Reporting categories
Asset
Storage Subsystems
Availability
Capacity
Usage
Usage Violations
Backup

Chargeback
ibm.com/redbooks

Figure 6-1 Reporting capabilities

The reporting capabilities of Tivoli Storage Resource Manager are very rich, with over 300
predefined views. You can see the data from a very high-level; for example, the total amount
of free space available over the enterprise; or from a low-level, for example, the amount of
free space available on a particular volume or a table in a database.

The data can be displayed in tabular or graphical format, or can be exported as HTML,
Comma Separated Variable (CSV), or formatted report files.

The reporting function uses the data stored in the Tivoli Storage Resource Manager
repository. Therefore, in order for reporting to be accurate in terms of using current data,
regular discovery, Ping, Probe, and Scan jobs must be scheduled. These jobs are discussed
in 5.1, “OS Monitoring” on page 160.

Figure 6-2 shows the Tivoli Storage Resource Manager main screen with the reporting
options highlighted.

The Reporting sections are used for interactive reporting. They can be used to answer ad hoc
questions such as, “How much free space is available on my UNIX systems?” Typically, you
will start looking at data at a high-level and drill down to find specific detail. Much of the
information can also be displayed in graphical form as well as in the default table form.

The My Reports sections give you access to predefined reports. Some of these reports are
pre-defined by Tivoli Storage Resource Manager, others can be created by individual users


saving reporting criteria in the Reporting options. You can also set up Batch Reports to create
reports automatically on a schedule.

My Reports will be covered in more detail in 6.5, “Creating customized reports” on page 345,
and 6.6, “Setting up a schedule for daily reports” on page 360.

The additional product, Tivoli Storage Resource Manager for Chargeback produces storage
usage Chargeback data, as described in 6.8, “Charging for storage usage” on page 364.

Predefined reports provided by
Tivoli Storage Resource
Manager
Reports customized and saved
by user db2admin

Schedule reports to run in
batch mode

Interactive reporting options

Database reporting options

Figure 6-2 IBM Tivoli Storage Resource Manager main screen showing reporting options

6.1.1 Major reporting categories
Tivoli Storage Resource Manager collects data for reporting purposes in seven major
categories. These will be covered in the following sections. Within each major category there
are a number of sub-categories.

Most categories are available for both operating system level reporting and database
reporting. However, a few are for operating system reporting only. The description of each
category specifies which applies, and in the more detailed following sections for each
category, we present the capabilities separately for both Tivoli Storage Resource Manager
and Tivoli Storage Resource Manager for Database as appropriate.

Chapter 6. Reporting 249

Asset Reporting
Asset data is collected by Probe processes and reports on physical components such as
systems, disk drives, and controllers. Currently, Asset Reporting down to the disk level is only
available for locally attached devices. Asset Reporting is available for both operating system
and database reporting.

Storage Subsystems Reporting
Storage Subsystem data is collected by Probe processes. It provides a mechanism for viewing
storage capacity at a computer, filesystem, storage subsystem, LUN, and disk level. These
reports also enable you to view the relationships among the components of a storage
subsystem. Storage Subsystem reporting is currently only available for IBM TotalStorage
Enterprise Storage Servers (ESS). Storage Subsystems Reporting is available for operating
system only.

Availability Reporting
Availability data is collected by Ping processes and allows you to report on the availability of
your storage resources and computer systems. Availability Reporting is provided for operating
system reporting only.

Capacity Reporting
Capacity Reporting shows how much storage you have and how much of it is being used. You
can report at anywhere from an entire network level down to an individual filesystem.
Capacity Reporting is provided for both operating system and database reporting.

Usage Reporting
Usage Reporting goes down a level from Capacity Reporting. It is concerned not so much
with how much space is in use, but rather with how the space is actually being used for. For
example, you can create a report that shows usage by user, or a wasted space report. You
define what wasted space means, but it could be for example files of a particular type or files
within a certain directory, which are more than 30 days old. Usage Reporting is provided for
both operating system and database reporting.

Usage Violation Reporting
Usage Violation Reporting allows you to set up rules for the type and/or amount of data that
can be stored, and then report on exceptions to those rules. For example, you could have a
rule that says that MP3 and AVI files are not allowed to be stored on file servers. You can also
set Quotas for how much space an individual user can consume. Not that usage violations
are only softly enforced - IBM Tivoli Storage Resource Manager will not enforce the rules in
real time, but will generate an exception report after the fact. Usage Violation Reporting is
provided for both operating system and database reporting.

Backup Reporting
Backup Reporting identifies files that have not been backed up. Backup Reporting is provided
for operating system reporting only.


6.2 Using the standard reporting functions

Tivoli Storage Resource Manager: Standard Reporting

Predefined reports or views of the data

Available for both operating system and database reporting

Can report at a high level or drill down for specific detail

ibm.com/redbooks

Figure 6-3 Tivoli Storage Resource Manager standard reporting

This section discusses Tivoli Storage Resource Manager’s standard reporting capabilities.
Customized reporting is covered in 6.5, “Creating customized reports” on page 345.

This section is not intended to cover exhaustively all of the reporting options available, as
these are very numerous, and are covered in detail in the Reporting section of the manual
IBM Tivoli Storage Resource Manager V1.1 Reference Guide SC32-9069. Instead, this
section provides a basic overview of Tivoli Storage Resource Manager reporting, with some
examples of what types of reports can be produced, and additional information on some of
the less straightforward reporting options.

To demonstrate the reporting capabilities of Tivoli Storage Resource Manager, we installed
the Server code on a Windows 2000 system called LOCHNESS, and deployed these Agents:
A Windows NT workstation called A23BLTZM
AIX systems called BRAZIL and CRETE
An HP-UX system called EASTER
A Solaris system called SOL-E
Windows 2000 servers called GALLIUM, LEAD and VMWAREW2KSR1.
LOCHNESS is also an Agent as well as being the Server.

The host GALLIUM has both Microsoft SQL-Server and Oracle database installed to
demonstrate database reporting. The Agent on LOCHNESS also provides data for a NAS
device call NAS200. The Agent on VMWAREW2KSRV1 also provides data for a NetWare
server called ITSOSJNW6.

The lab setup is shown in Figure 6-4.


Tivoli Storage Resource Manager: Lab Environment

ITSRM
Scan
ITSRM
Database

A23BLTZM
WNT LOCHNESS
ITSRM W2K
Agent & ITSRM
GUI Server

Ethernet

NetWare VMWAREW2KSRV1 SOL-E GALLIUM CRETE BRAZIL IBM
EASTER
W2K (Vmware) Solaris W2K AIX AIX NAS200
HP-UX
ITSRM ITSRM ITSRM ITSRM ITSRM
ITSRM
Agent Agent Agent Agent Agent
Agent

ITSRM
Scan
ibm.com/redbooks
VMWAREW2KSRV1
W2K (Vmware)
ITSRM
A t
Figure 6-4 Tivoli Storage Resource Manager Lab Environment

6.2.1 Asset Reporting
Asset Reporting provides configuration information for the Tivoli Storage Resource Manager
Agents. The information available includes typical asset details such as disk system name
and disk capacities, but provides a large amount of additional detail.

Figure 6-5 shows the major subtypes within Asset Reporting. Note that unlike the other
reporting categories where most of the drill-down functions are chosen from the right-hand
panel, in Asset Reporting the drill-down functions are mostly available on the left-hand pane.


Figure 6-5 Reporting - Asset

By Computer view
Click By Computer to see a list of all of the monitored systems (Figure 6-6.)

Figure 6-6 Reporting - Asset - By Computer

From there we can drill down on the assets associated with each system. We will take a look
at node GALLIUM. In Figure 6-7 we have shown most of the items for GALLIUM expanded,
with the details for Disk 0 displayed in the right-hand bottom pane.


You will see a detailed level of information, both in terms of the type of objects for which data
is collected (for example, Exports/Sshares), and the specific detail for a given device.

Figure 6-7 Report - GALLIUM assets

By OS Type view
This view of the Asset data provides the same information as the By Computer view, with the
difference that the Agent systems are displayed sorted by operating system platform.

System-wide view
The System-wide view however does provide additional capability, as it can give a
System-wide view rather than a node-by-node view of some of the data. A graphical view of
some of the data is also available. Figure 6-8 shows the options available from the
System-wide view and in the main panel, the report of all exports/shares available.


Figure 6-8 Reporting - Assets - System-wide view

Each of the options available under the System-wide view are self explanatory with the
possible exception of Monitored Directories. Tivoli Storage Resource Manager can monitor
utilization at a directory level as well as a device or filesystem level. However, by default,
directory level monitoring is disabled.

To enable directory monitoring, define a Directory Group by selecting Tivoli Storage
Resource Manager -> Monitoring -> Groups -> Directory, right-click Directory and choose
New Directory Group. The process of setting up Directory Groups is discussed in more
detail in 5.1.2, “Groups” on page 162. Once the Directory Group is created it must be
assigned to a Scan job, and that job must be run on the systems where the directories to be
monitored exist.

By setting up a monitored directory you will get additional information for that directory. Note
that the information collected includes any subdirectories. Information collected about the
directory tree includes the number of files, number of subdirectories, total space used, and
average file size. This can be graphed over time to determine space usage patterns.

Figure 6-9 shows the directories that we are monitoring.


Figure 6-9 Monitored directories report

Asset Reporting for databases is similar to that for filesystems; however, filesystem entities
like controllers, disks, filesystems, and shares are replaced with database instances,
databases, tables, and data files.

Very specific information regarding an individual database is available as shown in
Figure 6-10 for the database Northwind on node GALLIUM. Or you can see rollup information
for all databases on a given system (using the System-wide view) as shown in Figure 6-11.


Figure 6-10 Northwind database asset details

Figure 6-11 System-wide view of database assets

All of the database Asset Reporting options are quite straightforward with the exception of
one. In order to receive table level asset information, one or more Table Groups needs to be


defined. This is a similar process to that for Directory Groups as described in “System-wide
view” on page 254.

You would not typically include all database tables within Table Groups, but perhaps either
critical or rapidly growing tables. We will set up two groups, one for each database type.

To set up a Table Group, Tivoli Storage Resource Manager for Databases -> Monitoring
-> Groups -> Table, right-click Table and choose New Table Group (Figure 6-12).

Figure 6-12 Create a new database table group

We have entered a description of GALLIUM Table Group. Now we click New Instance to
enter the details of the database and tables that we want to monitor. From the drop down box,
we select the database instance, in this case the SQL-Server instance on GALLIUM. We then
enter three tables in turn. For each table, we entered the database name (Northwind ), the
creator name (dbo) and a table name. After entering the values, click Add to enter more
tables or finish. We entered the table names of Customers, Employees and Suppliers, as
shown in Figure 6-13. Once all of the tables have been entered click OK.

Figure 6-13 Add SQL Server tables to table group


We then entered details for a single table called DR$OBJECT for the Oracle database ITSRM

Figure 6-14 Add Oracle tables to table group

Now we return to the Create Table Group panel, and we see in Figure 6-15 the information
about the newly entered tables.

Figure 6-15 Tables added to table group

Now we chose File -> Save and when prompted, we entered the Table Group name of
GALLIUM Table Group.

In order for the information for our tables to be collected, the Table Group needs to be
assigned to a Scan job. We will assign it to the default database scan job called Tivoli.Default
DB Scan by choosing IBM Tivoli SRM for Databases -> Monitoring -> Scans ->
Tivoli.Default DB Scan. The definition for this scan job is shown in Figure 6-16 and in
particular we see the Table Groups tab. Our new Table Group is shown initially in the left hand
pane. We moved it to the right hand pane by selecting it and clicking >>. We then save the
updates to the Scan job by choosing File -> Save (or with the floppy disk icon from the tool


bar). Finally, we can execute the Scan job by right-clicking it and choosing Run Now.
Figure 6-16 shows the Scan job definition after the Table Group had been assigned to it.

Figure 6-16 Table group added to scan job

Example 6-1 on page 261 is an extract from the Scan job log showing that the table
information is now being collected. You can view the Scan job log through the Tivoli Storage
Resource Manager GUI by first expanding the particular Scan job definition. A list of Scan
execution reports will be shown; select the one of interest. You may need to right-click on the
Scan job definition and choose Refresh. The list of Scan executions for the Tivoli.Default DB
Scan is shown in Figure 6-17.

Figure 6-17 Displaying Scan job logs

Once you have the actual job chosen you can click the detail icon for the system that you are
interested in to display the job log. The actual file specification of the log file on the Agent


system will be displayed at the top of the output when viewed through the GUI. Example 6-1
shows the actual file output.

Example 6-1 Database scan job showing table monitoring
09-19 18:01:01 DBA0036I: The following databases-tablespaces will be scanned:
MS SQLServer gallium/gallium Databases:
master
model
msdb
Northwind
pubs
tempdb
Oracle itsrm Tablespaces:
ITSRM.DRSYS
ITSRM.INDX
ITSRM.RBS
ITSRM.SYSTEM
ITSRM.TEMP
ITSRM.TOOLS
ITSRM.USERS
09-19 18:01:01 DBA0041I: Monitored Tables:
.CTXSYS.DR$OBJECT
Northwind.dbo.Employees
Northwind.dbo.Customers
Northwind.dbo.Suppliers

Finally, we can produce table level asset reports by choosing for example, IBM Tivoli SRM
for Databases -> Reporting -> Asset-> System-wide-> All DBMSs -> Tables -> By Total
Size. This is shown in Figure 6-18.

Figure 6-18 Tables by total size asset report


6.2.2 Storage Subsystems Reporting
Storage Subsystems Reporting is covered in detail in 6.3, “Tivoli Storage Resource Manager
ESS Reporting” on page 297.

6.2.3 Availability Reporting
Availability Reporting is quite simple. Two different sets of numbers are reported - Ping and
Computer Uptime. Ping is only concerned with whether or not the system is up and
responding to the ICMP requires - it does not care whether the Tivoli Storage Resource
Manager Agent is running or not. Ping results are collected by a Ping job, so this must be
scheduled to run on a regular basis. See 5.1.4, “Pings” on page 174.

Computer Uptime detects whether or not the Tivoli Storage Resource Manager Agent is
running. Computer Uptime statistics are gathered by a Probe job so this must be scheduled to
run on a regular basis. See 5.1.5, “Probes” on page 177.

Figure 6-19 shows the Ping report for our Tivoli Storage Resource Manager environment, and
Figure 6-20 shows the Computer Uptime report. To generate these reports, we had to select
the computers of interest and select Generate Report.

Figure 6-19 Reports - Availability - Ping


Figure 6-20 Reports - Availability - Computer Uptime

6.2.4 Capacity Reporting
Capacity Reporting shows how much storage capacity is installed, and of that capacity, how
much is being used and how much is available for future growth.

There are four capacity report views within Tivoli Storage Resource Manager:
Disk Capacity
Filesystem Capacity
Filesystem Used Space
Filesystem Free Space

However, in reality there are really only two views, or perhaps three. The Filesystem Capacity
and Filesystem Used Space views are nearly identical - the only differences being in the
order of the columns and the row sort order.

And there is relatively little difference between these two views and the Filesystem Free
Space view. The Filesystem Capacity and Filesystem Used Space views report on used
space, so include columns like percent used space whereas Filesystem Free Space includes
columns like percent free space. All other data is identical.

Therefore, there are really only two views: a Disk Capacity view and a Filesystem Capacity
view.

The Disk Capacity view provides information about physical or logical disk devices and what
proportion of them has been allocated. Figure 6-21 shows the Disk Capacity by Disk selection
window.


Figure 6-21 Disk capacity report selection window

Often there is a one-to-one relationship between devices and filesystems, particularly on
Windows systems. One of our Windows systems, A23BLTZM, has a single physical disk
which has two partitions. We will select that system to report on by choosing Clear All,
clicking the check box beside the system name, and then choosing Generate Report. This
system has only one disk (Disk 0) which is displayed on the next screen, so we clicked the
detail icon and the report in Figure 6-22 is produced. Note the two partitions show at the
bottom of the right-hand pane.


Figure 6-22 Capacity report - A23BLTZM Disk 0

Capacity Reporting for databases is very straightforward. You can report on:
All databases of any type
All databases of a given type on a particular system or group of systems
On a specific database

Example 6-23 shows a Capacity Report by Computer Group. We actually have databases in
just one Computer Group, WindowsDBServers. We then drilled down to see all systems within
the WindowsDBServers group, then specifically to node GALLIUM, so that we could see all
databases on GALLIUM.


Figure 6-23 Database Capacity report by Computer Group

6.2.5 Usage Reporting
The reporting categories covered so far have been mostly concerned with reporting at the
system or device level. Usage Reporting goes down one more step to report at a level lower
than the filesystem. You can produce reports that answer questions such as:
How old is my data? When was it created, last accessed, or modified?
What are my largest files? What are my largest directories?
Do I have any orphan files?

With Usage Reporting, you will be able to:
Identify orphan files and either update their ownership or delete them to free up space
Identify the largest files and determine whether they are needed or whether parts of the
data could be archived
Identify obsolete files so that they can be either deleted or archived

There are a few restrictions on Usage Reporting:
In order to report by directory or by Directory Group you will need to set them up in IBM
Tivoli SRM -> Monitoring -> Groups -> Directory
UNIX systems do not record file create dates, so no reporting by creation time is available
for these systems.

Like database Asset Reporting, all of the database Usage Reporting options are quite
straightforward with the exception of table level reporting.

From a usage perspective there are two types of table report available:
Largest tables
Monitored tables


We can report on database largest tables by choosing for example, Tivoli Storage Resource
Manager for Databases-> Reporting -> Usage -> All DBMSs -> Tables -> Largest Tables
-> By RDBMS Type. This report is shown in Figure 6-24.

Figure 6-24 Largest tables by RDBMS type

A Monitored Tables by RDBMS Type report is shown in Figure 6-25. In this case, only tables
which are part of a Table Group, which is included in a Scan job will be reported on.


Figure 6-25 Monitored tables by RDBMS type

6.2.6 Usage Violation Reporting
Usage Violation Reporting enforces Tivoli Storage Resource Manager Constraints and
Quotas. A Constraint is a limit, by file name syntax, on the type of data that can be stored on
a system. A Quota is a storage usage limit placed on a user or operating system User Group,
and can be defined at the network, computer, or filesystem level. Constraints and Quotas
were described in 5.3, “Policy management” on page 200. It is important to remember that
Quotas and Constraints are not hard limits - users will not be stopped from working if a Quota
or Constraint is violated, but this event will trigger an exception, which will be reported.

IBM Tivoli Storage Resource Manager Constraint Violation Reporting
There are a number of predefined Constraints in Tivoli Storage Resource Manager. Before
we produce a Constraint violation report, we need to set up a new Constraint called forbidden
files. Setting up Constraints was described in 5.3.4, “Constraints” on page 224.

First navigate Tivoli Storage Resource Manager -> Policy Management -> Constraints.
Existing Constraints will be listed. Right-click Constraints and choose New Constraint. On
the Filesystems tab we entered a description of forbidden files, chose Computer Groups,
then selected db2admin.Windows Systems and clicked >>. The completed Filesystems tab
is shown in Figure 6-26.


Figure 6-26 Create a Constraint - Filesystems tab

We then need to specify in the File Types tab, what a forbidden file is. You can define the
criteria as either inclusive or exclusive; that is, you can specify just those files types that will
violate the Constraint, or you can specify that all files will violate the Constraint except those
specified. There are a number of predefined file types included; you can also chose additional
files by entering appropriate values in the “Or enter a pattern field” at the bottom of the
form. We have chosen MP3 and AVI files. The completed File Types tab is shown in
Figure 6-27.


Figure 6-27 Create a Constraint - file types tab

The Users tab is very similar to the File Types tab - you can specify which users should be
included or excluded from the selection criteria. We have taken the default, which is to include
all users.

In the Options tab, we nominate a maximum number of rows to be returned. We can also
apply some more specific selection criteria here such as only including files that are larger
than a defined size. Note, however that these criteria are added to the file list. For example, if
we specified here that we only wanted to include files greater than 1 MB, the search criteria
would be changed to ((NAME matches any of ('*.AVI', '*.mp3') AND TYPE <> DIRECTORY)
OR SIZE > 1 MB). So the returned list of files would be any file greater than 1 MB in size plus
any *.MP3 or *.AVI files.

If you wish to change the selection criteria so that instead you select any *.MP3 or *.AVI files
that are larger than 1 MB, you can enter 1 MB against the bigger than option, and then click
the Edit Filter button shown in Figure 6-30. You will then see the file filter as shown in
Figure 6-28. To add the size criteria to the file type criteria, click on the Size > 1MB entry and
drag it up to the All of tag. The changed filter is shown in Figure 6-29. You can also see the
Boolean expression for the filter has changed to reflect this condition.


Figure 6-28 Edit a Constraint file filter - before change

Figure 6-29 Edit a Constraint file filter - after change

In this case we did not want to apply a size criteria, so we left the Option tab entries at their
defaults as shown in Figure 6-30.


Figure 6-30 Create a Constraint - Options tab

Finally, we can specify that we want an Alert generated if a triggering condition is met. The
only choice here is to specify a maximum amount of space consumed by the files that meet
our selection criteria. We left all of the Alert tab options at their defaults other than specifying
an upper limit of 100 MB for files that have met our selection criteria. The Alert tab is shown in
Figure 6-31. Alerting is covered in more detail in 5.2, “OS Alerts” on page 189.

We then clicked the Save button and entered a name of Forbidden Files as shown in
Figure 6-32.


Figure 6-31 Create a Constraint - Alert tab

Figure 6-32 Create a Constraint - save


Before we can report against the Constraint, we need to ensure that a Scan job has been run
to collect the appropriate information.

Once the Scan has completed successfully, you can go ahead and produce Constraint
Violation Reports. Note that you cannot produce a report of violations of a particular
Constraint - the report will include entries for any Constraint violation. However, once the
report is generated, you can drill down into specific Constraint violations.

We produced the report by choosing Tivoli Storage Resource Manager -> Reporting ->
Usage Violations -> Constraint Violation -> By Computer. You will see a screen like
Figure 6-33 where you can select a subset of the clients if appropriate - after selecting, click
Generate Report.

Figure 6-33 Constraint violation report selection screen

You will then see a list of all of those instances of Constraint violations as shown in
Figure 6-34.

The report shows multiple types of Constraints. Some of these Constraints were predefined
(Orphaned File Constraint and Obsolete File Constraint) and others (ALLFILES and forbidden
files) we defined. An orphaned file is any file that does not have an owner. This allows you to
easily identify files that belonged to users who have left your organization or have had an
incorrect ownership set.


Figure 6-34 Constraint violations by computer

From there you can drill down on a specific Constraint, then filesystems within the Constraint,
and finally to a list of files that violated the Constraint on that filesystem by selecting the
magnifying glass icon next to the entry of interest. Or, as shown in Figure 6-35, by clicking the
pie chart icon next to the entry for forbidden files, you can produce a graph indicating what
proportion of capacity is being utilized by files violating the Constraint. Position the cursor
over any segment of the pie chart to show the percentage and number of bytes consumed by
that segment. We can see that 13% or 7.7 Gigabytes of capacity is being consumed by files
violating the forbidden files Constraint on this filesystem.

Figure 6-35 Graph of capacity used by Constraint violating files


Constraint violations are also written to the Tivoli Storage Resource Manager Alert Log.
Figure 6-36 shows the same list of violations as if you had produced a Constraint Violations
by computer report.

Figure 6-36 Alert log showing Constraint violations

Quota Violation Reporting
The process of producing a Quota violation report is very similar to producing a Constraint
violation report, but with some key differences.

One difference between Quotas and Constraints is the process of collecting data. For
Constraints, the data is collected as part of a standard Scan job in a similar way to adding an
additional Profile to a Scan. Quota data collections are performed in a separately scheduled
job. So, when you set up a Quota you need to specify scheduling parameters.

We set up a Quota rule called Big Windows Users by choosing Tivoli Storage Resource
Manager -> Policy Management -> Quotas -> Users -> Computer, right-clicking Computer
and selecting New Quota. On the Users screen we entered a description of Big Windows
Users and then selected User Groups and then Tivoli.Default User Group as show in
Figure 6-37.


Figure 6-37 Create Quota - Users tab

On the Computers tab we chose our Windows group: db2admin.Windows Systems
(Figure 6-38).

Figure 6-38 Create Quota - Computers tab


We when had to specify when and how often we wanted the Quota job to run. We chose to
run the job weekly under the When to CHECK tab as shown in Figure 6-39.

Figure 6-39 Create Quota - When to Check

On the Alert tab, shown in Figure 6-40, we accepted all of the defaults other than to specify
the limit under User Consumes More Than, in this case, 1 GB.

No Alerts will be generated other than to log any exceptions in the Tivoli Storage Resource
Manager Alert Log.


Figure 6-40 Create Quota - Alert

Finally, we save the Quota definition, calling it Big Windows Users as shown in Figure 6-41.

Figure 6-41 Create Quota - save


The new Quota now appears under IBM Tivoli SRM -> Policy Management -> Quotas ->
Users > Computer as db2admin.Big Windows Users (where db2admin is our Tivoli Storage
Resource Manager username). We right-clicked the Quota and chose Run Now as in
Figure 6-42.

Figure 6-42 Run new Quota job

This job will collect data related to the Quota, and add any Quota Violations to the Alert Log

Figure 6-43 Alert Log - Quota violations


We then drilled down on one of the Alerts to see the details (Figure 6-44).

Figure 6-44 Alert Log - Quota violation detail

And finally we can create a Quota Violation report by choosing IBM Tivoli SRM -> Reporting
-> Usage Violations -> Quota Violations -> Computer Quotas -> By Computer. The
high-level report is shown in Figure 6-45.

Figure 6-45 Quota violations by computer

We can then drill down further for additional detail or to produce a graphical representation of
the data behind the violation. The graph in Figure 6-46 shows a breakdown of the users’ data
by file size.


Figure 6-46 Quota violation graphical breakdown by file size

Filesystem Usage Violation Reporting includes both Quota and Constraint violations.
However, for databases, only Quota violations are available.

You can place a Quota on users, user groups, or all users and you can limit the Quota by
computer, computer group, database instance, database tablespace group or tablespace.

We will set up an Instance Quota that limits any individual user to 100 MB of space per
instance for any database on any server in the db2admin.WindowsDBServers computer
group.

To do this, navigate to IBM Tivoli SRM for Databases -> Policy Management -> Quotas ->
Instance. Right-click Instance and choose New Quota. Figure 6-47 shows the Quota
definition screen. We entered a description of Big DB Users and selected the Tivoli.Default
User Group by expanding User Groups, clicking Tivoli.Default User Group, and then
clicking >>.


Figure 6-47 Create database Quota - Users tab

On the Instances tab, expand Computer Groups, select db2admin.WindowsDBServers
and then click >> to add it to the Current Selections as shown in Figure 6-48.

Figure 6-48 Create database Quota - Instances tab

On the When to Run tab shown in Figure 6-49, we chose to run the Quota job weekly and
nominated a time of day for the job to run. Other values were left at the defaults.


Figure 6-49 Create a database Quota - When to Run tab

On the Alert tab (shown in Figure 6-50) we specified the actual Quota that we wanted
enforced, which was a 100 MB per user Quota. Other values were left as defaults.

Figure 6-50 Create a database Quota - Alert tab

We saved the new Quota definition with a name of Big DB Users as shown Figure 6-51.


Figure 6-51 Create a database Quota - Save

We now run the Quota by right-clicking it and choosing Run Now as seen in Figure 6-52.

Figure 6-52 Run the database Quota

To check if any user has violated the Quota, navigate IBM Tivoli SRM for Databases ->
Alerting -> Alert Log -> All DBMSs -> All. We see one violation as shown in Figure 6-53.


Figure 6-53 DB Quota violation

We can also now run a database Quota violation report by choosing IBM Tivoli SRM for
Databases -> Reporting -> Usage Violations -> Quota Violations -> All Quotas -> By
User Quota. This report can be seen in Figure 6-54.

Figure 6-54 Database Quota violation report


6.2.7 Backup Reporting
Backup Reporting is designed to do two things: It can alert you to situations where files have
been modified but not backed up, and it can provide data on the volume of data that will be
backed up. Figure 6-55 shows the options that are available for Backup Reporting.

Figure 6-55 Backup Reporting options

Most at Risk Files
Tivoli Storage Resource Manager defines most at risk files as those that are least-recently
modified, but have not been backed up.

There are some points worth noting about this report:
Since the report relies on the archive bit being set to determine whether the file has
changed, this report will only work on Windows systems as UNIX systems have no
equivalent to the archive bit
When using most backup products, once a file has been backed up the archive bit is
cleared. Before Version 5.2, IBM Tivoli Storage Manager did not do this, therefore if this
level of Tivoli Storage Manager was used, this report would list files that actually may have
been backed up. IBM Tivoli Storage Manager Version 5.2 has the ability to reset the
Windows archive bit after a successful backup of a file. See “Backup reporting for Tivoli
Storage Manager V5.2” on page 295 for more information on the reset archive bit available
for the Tivoli Storage Manager Windows client.

By default, information on only 20 files will be returned. Figure 6-56 shows the selection
screen for the report. You will notice that the report uses the Profile Tivoli.Most at Risk. It is in
this Profile that the 20 file limit is set, although the value can be changed. You can override
the value on the selection screen, but you can only reduce the value here, not increase it.

By updating the Profile you can also exclude files from the report. By default, any file in the
WINNTsystem* directory tree on any device will be excluded. You can add entries to the
exclusion list if appropriate. Ideally, the exclusion list should be the same as that in your
backup product.


Figure 6-56 Files most at risk report - selection

Modified Files Not Backed up
The report provides an aging analysis of your data that has been modified but not backed up.
It will show what proportion of the data has been modified within the past 24 hours, between
one and seven days, between one week and one month, and so on. Figure 6-57 shows the
selection taken in our Windows environment. Like the Most at Risk Files report, this report
also relies on the archive bit, so check to see if your backup application uses this.


Figure 6-57 Modified Files not backed up selection

To view the report, click Generate report. We choose to view it as a graphic by then clicking
on the pie icon and selecting Chart: Space Distribution for All. This is shown in Figure 6-58.
This chart tells you the amount of space consumed by files have not been backed up since
the last backup was run for this server.

Figure 6-58 Modified Files not backed up chart overall view


We can also select Chart: Count Distribution for All as shown in Figure 6-59 to show the
number of files in each category.

Figure 6-59 Files need backed up chart in detail view

The different charts can be viewed in different ways. To select another type of chart, right-click
in the chart area and select another type - e.g. bar chart, as shown in Figure 6-60.

Figure 6-60 Files not backed up bar chart detail view


Backup Storage Requirements Reporting
This option allows you determine how much data would be backed up if you were to perform
either a full or an incremental backup. The Full Backup Size option can be used regardless of
the OS type and the backup application in use.

In Figure 6-61, the report is run against Windows systems by filesystem.

Figure 6-61 Backup storage requirements per filesystem

The selection can also run by computer, as shown in Figure 6-62.


Figure 6-62 Backup storage requirement per computer and per filesystem

The Incremental Backup Size option makes use of the archive bit, so it can only be used on
Windows systems, and if Tivoli Storage Manager is the backup application, the
resetarchiveattribute option must be used (for Version 5.2). A sample report is shown in
Figure 6-63.


Figure 6-63 Incremental reporting per Node and Filesystem based on files

The third report type here is Incremental Range Sizes Reporting. This does not rely on the
archive bit (instead, it uses the modification date) so is more generically applicable. It is
possible to show through the use of this report the actual difference between a traditional
weekly full/daily incremental backup process versus Tivoli Storage Manager’s progressive
incremental approach. To generate this report, select Backup -> Backup Storage
Requirements -> Incremental Range Size -> By Computer as shown in Figure 6-64.


Figure 6-64 Incremental Range Size select By Computer

After you select the Computers of interest, click Generate Report. Figure 6-65 shows the
output from this report, with the amount of data changed for different time ranges. Note that
the values are cumulative, so for each time range; the values shown include the smaller time
periods.

If we take the results for system BONNIE as an example, it shows that 390 files (1.02% of all
files) and 41.66 MB (1.82% of total storage) changed within the previous 24 hours and 2831
files (7.45% of all files) and 2.33 GB (53.42% of total storage) changed within the last week.

Using the report for IBM Tivoli Storage Manager planning
Tivoli Storage Manager’s progressive incremental capability avoids the necessity of
performing regular full backups by keeping a record in its own relational database of what files
have been backed up, and then only backing up those files that have changed.

A typical metric when doing Tivoli Storage Manager planning is to estimate the amount of
data that changes each day in a file server environment as typically about 5-10%. With Tivoli
Storage Resource Manager, we can replace this estimate with actual numbers.

The 1.02% change rate here is outside the typical range because the system is in a lab
environment, and is not performing production work. But, to demonstrate the calculations we
will use those figures.


If we assume that 1.02% is the average for each day, that gives a weekly change rate of
7.14%. Seven times the daily rate of change will almost always be greater than the reported
weekly change rate as some files will be updated on multiple days throughout the week.

With Tivoli Storage Manager’s progressive incremental approach in this example we will only
backup approximately 291.62 MB (7 * 41.66 GB) per week compared to 4738 MB (4.38 GB *
1024 = 4485 MB + (6 * 41.66 MB)) for a traditional weekly full plus daily incremental
approach.

Figure 6-65 Incremental Range Sizes Report

Backup reporting for Tivoli Storage Manager V5.2
With IBM Tivoli Storage Manager Version 5.2 and IBM Tivoli Storage Resource Manager
V1.2, we have now the possibility to get more accurate statistics than in previous IBM Tivoli
Storage Resource Manager Versions.

To set this up we use a new option, resetarchiveattribute, in the DSM.OPT file for Windows
clients, as shown in Example 6-2. The use of this option determines whether Tivoli Storage
Manager resets the Windows archive attribute on files that have been successfully backed up
to a Tivoli Storage Manager server. Tivoli Storage Manager will also reset the archive attribute
during incremental backups if it is determined that there is already an active object on the
Tivoli Storage Manager server. The resetarchiveattribute option is useful in conjunction
with applications, such as IBM Tivoli Storage Resource Manager, as a simple way to report
on the backup status of files.

The Windows archive attribute is used to indicate that a file has changed since the last
backup. If it has been set to OFF, the Windows operating system will turn the attribute back to
ON after the file has been modified. Tivoli Storage Manager does not use the Windows archive


attribute to determine if a file is a candidate for incremental backup, (it uses its own algorithms
to determine this) but only for the purposes of reporting.

Example 6-2 Tivoli Storage Manager Option RESETARCHIVEATTRIBUTE
*********************************************************************
* Tivoli Storage Manager LOCHNESS
*
* Sample dsm.opt for the Microsoft Windows Backup-Archive Client
*********************************************************************
.
.
RESETARCHIVEATTRIBUTE YES
.

You can also use the Tivoli Storage Manager Preferences editor, as shown in Figure 6-66 to
set the Reset archive attribute. In any case, you need to start the Tivoli Storage Manager
client (including the Windows Scheduler Service) to make the changes active.

Figure 6-66 Tivoli Storage Manager preference settings for archive attribute

The next Tivoli Storage Resource Manager Scan will then be able to identify files backed up
with Tivoli Storage Manager, and include them in reporting functions.


6.3 Tivoli Storage Resource Manager ESS Reporting

IBM Tivoli Storage Resource Manager ESS Reporting

New Reporting Features
Capacity
Controllers
Disks and LUNs within an ESS

Reporting Categories
Asset Reporting
By Storage Subsystem
Disk Groups...Volume Spaces... Disk ... LUNs.
Storage Subsystem
Computer Views
By computer... By File Systems/Logical Volumes.
Storage Subsystem Views...By Storage Subsystem... By LUN... By Disk.

ibm.com/redbooks

Figure 6-67 ESS Reporting capabilities

The reporting capabilities in Tivoli Storage Resource Manager are expanded in Version 1.2 to
include Enterprise Storage Subsystem (ESS) reporting. IBM Tivoli Storage Resource
Manager uses Probe jobs to collect information about the ESS. We can then use the
reporting facility to view that information. The new subsystem reports show the capacity,
controllers, disks, and LUNs of an ESS and their relationships to computers and filesystems
within a network. Figure 6-67 summarizes the functionality.

6.3.1 ESS Reporting
For this section we discuss ESS asset and storage subsystem reporting, making refererences
to the ESS lab environment in Figure 6-68 below. Note that the host which accesses the ESS
had a Tivoli Storage Resource Manager Agent installed. This provides the fullest combination
of reporting ability for the ESS. If an ESS-attached host does not have a Tivoli Storage
Resource Manager Agent installed, items such as filesystem, logical volume, and device
logical names will not be displayed.


Win2k Srv sp3
CIM/OM server
w2kadvtsm
172.31.1.135

43p
AIX 5.1 ML 4 ESSF20
ITSRM Agent 172.31.1.1
tsmsrv43p
172.31.1.155 2109

Win2k Srv sp3
ITSRM Server
w2kadvtsrm
172.31.1.133

Intranet

Figure 6-68 ESS reporting lab

Prerequisites to ESS reporting
Before doing ESS reporting with Tivoli Storage Resource Manager, the following are required:
CIM/OM server successfully installed.
IBM Tivoli Storage Resource Manager successfully logs into CIM/OM server.
IBM Tivoli Storage Resource Manager successfully runs a discovery and probes the ESS.

Important: Refer to 4.9, “CIM/OM” on page 145 for additional details on confirming
these prerequisites.

The IBM Tivoli Storage Resource Manager will run a discovery to locate the CIM/OM server
in our environment, which in turn discovers the ESSs. See 4.9.3, “CIM/OM configuration in
IBM Tivoli Storage Resource Manager” on page 153.

Creating the ESS Probe
IBM Tivoli Storage Resource Manager will then run a Probe to query the discovered ESS.
The Probe collects detailed statistics about the storage assets in our enterprise, such as
computers, storage subsystems, disk controllers, hard disks, and filesystems.

Next, we show how to create a Probe for an ESS-F20. Select Probe -> Select new probe,
then under the Computers tab, choose Storage Subsystems. See Figure 6-69.


Figure 6-69 Creating ESS probe

On the When to PROBE tab, we selected PROBE Now because we need to populate the
backend repository. See Figure 6-70.

Figure 6-70 ESS - When to probe


Next is the Alert tab, shown in Figure 6-71. This defines the type of notification for a Probe.

Figure 6-71 ESS - Alert tab

After all parameters are defined, save the Probe definition. At this point the Probe is
submitted and will run immediately.

Note: For additional information on creating Probes, see 5.1.5, “Probes” on page 177.

There are several ways to check the status of the Probe job. First, we can check the color of
the Probe job entry in the navigation tree, then in the content panel. There are two colors that
represent job status. They are:
GREEN - Job successfully complete with no errors
RED - Job completed with errors

The status of the Probe job is displayed in text and in color, as shown in Figure 6-72, after
selecting the Probe job output in the navigation tree. The job at 8:44 am is in green, indicating
success. The job at 6:32 pm is in red, indicating errors.


Figure 6-72 ESS - probe job status

We open the Probe job by selecting it and double clicking on the spy glass icon next to the
job in the content window. We see the contents of the job, including detailed information on
the status, as in Figure 6-73. Here, we have selected the successful Probe on June 9 at 8:44.

Figure 6-73 Probe job log

Asset Reports - By Storage Subsystem
With Asset reporting by storage subsystem, you can view the centralized asset repository that
IBM Tivoli Storage Resource Manager constructs during a Probe. The Probe itemizes the
information about computers, disks, controllers, and filesystems, and builds a hardware
inventory of ESS assets. With the backend repository now populated with ESS-F20 asset
information, we will show how to view reports to display the storage resources.

We choose Reporting -> Asset -> By Storage Subsystem -> ESSF20. This report provides
specific resource information of the ESS and allows us to view storage capacity by a
computer, filesystem, storage subsystem, LUN, and disk level. We can also view the
relationships between the components of a storage subsystem. Notice that the navigation
tree is hierarchical, and shows ESSF20 as active (green). See Figure 6-74.


Figure 6-74 Asset by storage subsystem

We drill down to the Disk Groups. The disk group contains information related to the ESS, as
well as the volume spaces and disks associated with those Disk Groups. Expanding the Disk
Group node, a list of all Disk Groups on the ESS displays (Figure 6-75).

Figure 6-75 ESS disk group

Continuing, we expand the disk group DG1 to view the disks and volume spaces within it. We
open Volume Space VS3, which shows the disks and LUNs associated with it. The Disks
subsection shows the individual disks associated with the Volume Space (see Figure 6-76).


Figure 6-76 Disks in volume spaces

Notice the LUNs subsection for disk DD0105 (Figure 6-77). This shows the LUN to disk
relationship. The LUNs shown here are just a subset of all the LUNs. You can see that the
LUN is spread across all the displayed disks in the content window.


Figure 6-77 Disk and LUN association with volume space

Figure 6-78 shows the discovery of a disk with no LUN associations. This is known as a hot
spare. It can be used when one of the other seven disks in the disk group fails.


Figure 6-78 Hot spare LUN

We now show a high level view of all disks in ESSF20. There are 32 disks in the ESS, as
shown in Figure 6-74 on page 302 in the Number of Disks field. Figure 6-79 shows a partial
listing of the disks.


Figure 6-79 ESS all disks

We can also display a report of all the LUNs in the ESS. This report provides the physical disk
association with each LUN. We have a total of 56 LUNs in the ESSF20 as shown in
Figure 6-74 on page 302 (number of LUNS). A partial listing is shown in Figure 6-80.


Figure 6-80 ESS all LUNs

Storage Subsystem Reporting
We now open Reporting -> Storage subsystems. Storage Subsystems Reporting allows
viewing storage capacity at a computer, filesystem, storage subsystem, LUN, and disk level.

By Computer
We drill down Computers Views -> By Computer. The report displays the association of
filesystems to the storage subsystem, LUNS, and disks on ESSF20. These reports are useful
for relating computers and filesystems to different storage subsystem components. There are
three options available in the Relate Computers to: pull down, as shown in Figure 6-81.


Figure 6-81 By Computer - Relate Computer to

We select Storage Subsystems from the pull down, select the desired computer and click
Generate. Figure 6-82 shows that the generated report TSMSRV43P uses 9.24 GB in the
ESS.

Figure 6-82 By Computer - storage subsystem

Returning to the selection screen tab (Figure 6-81) we select LUNs. We choose the same
host, and click Generate. Figure 6-83 shows the generated report; the relationship between
TSMSRV43P and its assigned LUNs. TSMSRV43P has one LUN created on the ESS.


Figure 6-83 By Computer - LUNs

Finally, from the Selection tab (Figure 6-81), we select Disks, our host TSMSRV43P, and click
Generate. Figure 6-84 shows the report: the ESS disks assigned to the LUN on the host.

Figure 6-84 By Computer - disk

By Filesystem/Logical Volume
We will now drill to Computer Views -> By Filesystem/Logical Volume. The report displays
the association of filesystems to the storage subsystem, LUNS, and disks on ESSF20. These
reports are useful for relating computers and filesystems to different storage subsystem
components. There are three options available in the Relate Filesystem/Logical Volumes
to pull down, shown in Figure 6-85.


Figure 6-85 By filesystem/logical volume

Select Storage Subsystem, the host (TSMSRV43P), and click Generate. Figure 6-86 shows
the filesystems on the host, which are located on the ESS.

Figure 6-86 By filesystem/logical volumes - storage subsystem

From the Selection tab (Figure 6-85) we now choose LUNs, the host (TSMSRV43P), and
click Generate. Figure 6-87 shows the LUN location of each filesystem on the host.


Figure 6-87 By filesystem/logical volume - LUN

From the Selection tab (Figure 6-85) we now choose Disks, the host (TSMSRV43P), and
click Generate. Figure 6-88 shows which disks are comprising each filesystem and logical
volume.

Figure 6-88 By filesystem/logical volume - Disk

By Storage Subsystem
We will now drill down Storage Subsystem Views -> By Storage Subsystem. These
reports display the relationships of the ESS components (storage subsystems, LUNs, and
disks) to the computers and filesystems and logical volumes. There are two options available
in the Relate Storage Subsystems to: the pull down, shown in Figure 6-89.


Figure 6-89 By Storage Subsytems

Select Computers from the pull down, the subsystem ESSF20, and click Generate.
Figure 6-90 shows the space used by each host on the storage subsystem.

Figure 6-90 By Storage subsystem - Computer

Now, select Filesystem/logical Volumes from Figure 6-89, the ESSF20 subsystem, and
click Generate. Figure 6-91 shows each host’s filesystems and logical volumes, with their
capacity and free space.


Figure 6-91 By storage subsystem - filesystem/logical volume

By LUN
Continuing, we drill down Storage Subsystem Views -> By LUNs, (Figure 6-92).

Figure 6-92 By LUNs

Select Computer from the Relate LUNs to: pull down, select the subsystem (ESSF20) with
the associated disks (default is all), and click Generate Report. Figure 6-93 shows the LUNs


assigned to each host, with the host’s logical name for the LUN (/dev/hdisk1 in this case).

Figure 6-93 By LUN - computer

Now select Filesystem/Logical Volumes from the Relate LUNS to pull down, the ESSF20
subsystem with associated logical disks (default is all), and click. Next, we clicked Generate
Report. Figure 6-93 shows the relationships between the LUNs, computers, and
filesystems/logical volumes, including free space and host device logical names.

Figure 6-94 By LUNS - filesystem/logical volumes

Disks
Now we drill to Storage Subsystem Views -> Disks. There are two options available in the
Relate Disks to: pull down, shown in Figure 6-95.


Figure 6-95 Disks

Select Computer from the pull down, the ESSF20 subsystem with related disks (default is
all), and click Generate Report. Figure 6-96 shows the relationships of the disks to the hosts.

Figure 6-96 Disks - computer

Now select Filesystem/Logical Volumes from the pull down (Figure 6-95), the ESSF20
subsystem with related disks (default is all), and click Generate Report. Figure 6-97 shows
the relationship between the ESS disks and the filesystems and logical volumes.


Figure 6-97 Disks - filesystem/logical volumes

Note: For demonstration purposes, we have reduced some of the fields in the reports.

6.4 IBM Tivoli Storage Resource Manager top 10 reports
After analyzing typical customer scenarios, we have compiled the following list of “Top 10
reports” which we recommend running regularly for best practices:
ESS used and free storage
ESS attached hosts report
Computer Uptime
Growth in storage used and number of files
Incremental backup trends
Database reports against DBMS size
Database Instance storage report
Database reports size by instance and by computer
Locate the LUN on which a database is allocated
Finding important files on your systems

6.4.1 ESS used and free storage
This report shows the free and used storage on an ESS system. To generate this filesystem
logical view report, navigate IBM Tivoli SRM -> Reporting -> Storage Subsystem ->
Computer Views -> By Filesystem/Logical Volumes. Select the computers to report on,
and select Disks from the pull-down Relate Filesystems/Logical Volumes To as in
Figure 6-98.


Figure 6-98 ESS relation to computer selected by disk

Click Generate Report. The report is shown in Figure 6-99. Various columns are displayed:
Storage Subsystem
Storage Subsystem Type
Manufacturer
Model
Serial Number
Computer
Filesystem/Logical Volume Path
Capacity
Free Space
Physical Allocation

Figure 6-99 Report for Filesystem/Logical Volumes Part 1

Figure 6-100 shows the right hand columns of the same report.


Figure 6-100 Report for Filesystem/Logical Volumes Part 2

This report provides quick answers to how much space on the ESS is allocated to each
filesystem.

Select LUNs this time from the pull-down in Figure 6-98. The report in Figure 6-101 shows
the LUN to host mapping for the ESS, which filesystem is associated with each LUN, and the
free space.

Figure 6-101 Computer view to the filesystem with capacity and free space

6.4.2 ESS attached hosts report
This report shows which systems are using storage on an ESS. This is useful when ESS
maintenance is applied so that the administrators of affected systems can be informed.

To generate this report, select IBM Tivoli SRM -> Reporting -> Storage Subsystem ->
Computer Views -> By Computer tree. We have selected all computers as in Figure 6-102.


Figure 6-102 ESS selection per computer

Click the Generate Report field - the report is shown in Figure 6-103.

Figure 6-103 ESS connections to computer report

Note you can sort the report on a different column heading by clicking on it. The current sort
field is indicated by the small pointer next to the field name. Clicking again in the same
column reverses the sort order.

6.4.3 Computer Uptime reporting
Uptime is an important IT metric in the enterprise. To generate a Computer Uptime report,
select IBM Tivoli SRM -> Reporting -> Availability -> Computer Uptime -> by Computer.
Select the computers of interest, and a date range (optional), and click Generate Report, as


Figure 6-104 Computer Uptime report selection

For each computer, percent availability, number of reboots, total down time, and average
downtime is given, as in Figure 6-105 shows the selection. The default sort order is by
descending Total Down Time.

Figure 6-105 Computer Uptime report part 1

You can also display this information graphically, by selecting the pie chart icon at the top of
the report, as shown in Figure 6-106.


Figure 6-106 Computer Uptime report graphical combined (stacked bar)

Figure 6-107 shows an unstacked bar chart of the same information (right-click and select
Bar Chart).

Figure 6-107 Computer Uptime report graphical (bar chart)

6.4.4 Growth in storage used and number of files
The Backup Reporting features of Tivoli Storage Resource Manager also give a convenient
way to track the total storage used by files in each computer, as well as the number of files
stored. It can be presented graphically, to show historical numbers and future trends. This
information helps you plan future storage requirements, be alerted to potential problems, and
also (if using a traditional full and incremental backup product), plan your backup server
storage requirements, since this report shows the size of a full backup on each computer.
Select IBM Tivoli SRM -> Reporting -> Backup -> Backup Storage Requirements -> Full
Backups Size -> by Computer. We used the Profile: Tivoli.Summary By


Filesystem/Directory and selected all computers, as in Figure 6-108. Click Generate Report.

Figure 6-108 Generate Full Backup Size report

Figure 6-109 shows the total disk space used by all the files, and the number of files on each
computer. The top column shows the totals for all Agents.

Figure 6-109 Select History chart for File count

To drill down, select all the computers (using the Shift key) so they are highlighted, then click
on the pie icon, and select History Chart: Space Usage for Selected. The generated report
(Figure 6-110), shows how the total full backup size has fluctuated, and is predicted to
change in the future (dotted lines - to disable this, click Hide Trends).


Figure 6-110 History chart space used by a computer

To display the file count graph, select History Chart: File count from the pie icon in
Figure 6-109. The output report is shown in Figure 6-111, which shows trends in the number
of files on each computer.

Figure 6-111 History chart: File count


These reports will help you find potential problems (e.g. a computer system that shows an
unexpected sudden upward or downward spike) and also predicts disk and backup
requirements for the future.

6.4.5 Incremental backup trends
This report shows the rate of modification of files, which is very useful for incremental backup
planning.

Select IBM Tivoli SRM -> Reporting -> Backup -> Backup Storage Requirements ->
Incremental Range Size -> by Filesystem. Select Profile: Tivoli.by Modification as shown
in Figure 6-112.

Figure 6-112 Incremental Range selection based on filespace

The generated report shows all the filesystems on the selected computers as in Figure 6-113.


Figure 6-113 Summary of all filespace

The third column shows the total number and total size of files (for all the systems, then
broken down by filesystem). Then there are “Last Modified” columns for one day, one week,
one month, two months, three, six, nine, and one year selections. Each of these gives the
number and size of the modified files.

To generate charts, highlight all the systems, and click the pie icon. Select Chart: Count
Distribution for Selected, as shown in Figure 6-114.

Figure 6-114 Selection for Filesystem and computer to generate a graphic

The chart is shown in Figure 6-115. Note that when your cursor passes over a bar, a pop-up
shows the number of files associated with that bar.


Figure 6-115 Bar chart for Incremental Range Size by Filesystem

You can display other filesystems using the Next 2 and Prev 2 buttons. Change the chart
format by right-clicking and selecting a different layout. Figure 6-116 is a pie chart of the same
data. The pop-ups work here also as circled.

Figure 6-116 Pie chart selected with number of files which have modified


With these reports you can track and forecast your backups. You can also display backup
behavior for the last one, three, nine, or 12 months.

6.4.6 Database reports against DBMS size
This report shows an enterprise wide view of storage usage by all RDBMS. Select IBM Tivoli
SRM for Databases -> Reporting -> Capacity -> All DBMSs -> Total Instance Storage ->
Network-wide and click Generate Report.
Figure 6-117 shows a sample output.

Figure 6-117 Total Instance storage used network wide

This is a quick overview database space consumption across the network. To drill down on a
particular RDBMS type, select the appropriate magnifying glass icon as in Figure 6-118.

Figure 6-118 DBMS drill down to the computer reports

The report (Figure 6-119) displays.


Figure 6-119 DBMS drill down to the computer result

It shows the following fields for each Agent running DB2:
Computer name
Total size
Container capacity
Container free space
Log file space
Tablespace count
Container count
Log file count

6.4.7 Database instance storage report
This report shows storage utilization by database instance. Go to IBM Tivoli SRM for
Databases -> Reporting -> Capacity -> UDB -> Total Instance Storage -> by Instance,


select the computer(s) of interest, and click Generate Report. Figure 6-118 shows the result.

Figure 6-120 DBMS report Total Instance Storage by Instance

Note you could select any RDBMS which is installed in your network.

The report shows the following information for each Agent with DB2, plus a total (summary):
Computer name
RDBMS instance
Total size
Container Capacity
Container free space
Log file capacity
Tablespace count
Container count
Log file count

6.4.8 Database reports size by instance and by computer
The next report is based on the previous report (database Instance storage report), but in
more detail. From the report in Figure 6-120, click the magnifying glass next to a computer of
interest. Then do a further drill down on the generated report as in Figure 6-121.


Figure 6-121 Instance report RDBMS overview

Select the computer again, and click the magnifying glass. The report shows the entire DB2
environment running on computer TONGA. We have 3 DB2 UDB databases, shown in
Figure 6-122 and Figure 6-123.

Figure 6-122 Instance running on computer TONGA first part

Scroll to the right side of the panel.

Figure 6-123 Instance running on computer TONGA second part

Here we can see which databases are running in ARCHIVELOG mode.


6.4.9 Locate the LUN on which a database is allocated
This report shows you which disk or LUN is used by a database. Go to IBM Tivoli SRM for
Databases -> Reporting -> Capacity -> UDB -> Total Instance Storage -> by Instance,
select the Agent(s) of interest, then click Generate Report. Figure 6-124 shows the result.

Figure 6-124 LUN report selection for an Database

Select an Agent, and click the magnifying glass to drill down. Figure 6-125 displays.

The report shows the following columns:
File Type
Path
File Size
Free Space
Auto Extend of an File


Figure 6-125 Database select File and Path

Select now a particular data file, and click the magnifying glass. The generated pie chart is
shown in Figure 6-126. We can see this data file is allocated on the C: drive.

Figure 6-126 Report DB2 File in a Pie Chart for DB2 File

Click the View Logical Volume button at the bottom to display the LUN report (Figure 6-127).


Figure 6-127 LUN information

Using this procedure, we can find the LUNs where all the database data files are stored. This
information is useful for a variety of purposes, e.g. for performance planning, availability
planning, and assessing the impact of a LUN failure.

6.4.10 Finding important files on your systems
This report generates a search for specific files over all computers managed by an IBM Tivoli

As an example, we will look for the IBM Tivoli Storage Manager server and client options files.
We have chosen this search for all machines because it will return a relatively small number
of results; however, any search criteria could be used.

The task requires a number of steps:
1. Define new Profile
2. Bind new Profile into a Scan
3. Generate a Report with your Profile
4. Define new Constraint
5. Bind new Constraint into your Scan
6. Generate a Report to find defined Constraint
1. Define the new Profile
First create the Profile - IBM Tivoli SRM -> Monitoring -> Profiles, right-click, and select
Create Profile. Fill out the description field accordingly, and check the Summarize space
usage by, Accumulate history, and Gather information on the fields as desired. In the
bottom half click size distribution of files, as shown in Figure 6-128.


Figure 6-128 Create Profile for own File search

Now select the File Filter tab. Click in the All files selected area and right-click to create
a new condition, as shown in Figure 6-129.

Figure 6-129 Create new Condition


Enter the desired file pattern into the Match field, and click Add to bring the condition to
the display window below, as in Figure 6-130. You can select from different conditions like:
– Matches any of
– Matches none of
– Matches
– Does not match
When you have finished the condition, click OK. In our case we are matching Tivoli
Storage Manager option files.

Figure 6-130 Create Condition add

Figure 6-131 shows our newly created Condition.


Figure 6-131 Saved Condition in new Profile

Now save the new Profile with an appropriate name, (in this instance, Search for TSM
Options Files). The saved Profile now appears in the Profiles list, see Figure 6-132.

Tip: We recommend choosing meaningful Profile names, which reflect the content or
function of the profile.


Figure 6-132 Listed Profiles containing Search for Tivoli Storage Manager Option File

2. Bind new Profile into a Scan
First, create a new Scan - IBM Tivoli SRM -> Monitoring -> Scans. We chose
Tivoli.Default Scan as shown in Figure 6-133. Fill in a description for this Scan and select
the Filesystems and Computers on which the Scan will run.


Figure 6-133 Add Profile to Scan

On the Profiles tab, select the newly created Profile and add it to the Profiles to apply to
Filesystems column, as shown in Figure 6-134.

Figure 6-134 Add Profiles to Scan


Now select the schedule time when the schedule should run, save the Scan, then check
the result.
3. Generate Report with your Profile
To view the results, select IBM Tivoli SRM -> Reporting -> Usage -> File Size
Distribution -> by Filesystem. Select all filesystems, select the Profile: administrator.
Search for Tivoli Storage Manager Option Files and click Generate Report. The report
contains all the option files discovered by the Scan as in Figure 6-135.

Figure 6-135 Report with number of found Tivoli Storage Manager Option Files

Note that on BONNIE’s C drive we found 13 files.
4. Define new Constraint
We would like to know where specifically these files are located. To set up this search,
select IBM Tivoli SRM -> Policy Management -> Constraints -> Tivoli.Orphaned File
Constraint, as shown in Figure 6-136. Enter a description, and select the Filesystem
Groups and Computers where you want to locate the files.


Figure 6-136 Create Orphaned File search

Select the Options tab, then select Edit Filter as shown in Figure 6-137.

Figure 6-137 Update the Orphaned selection

On the Edit Filter pop-up, double click the ATTRIBUTES Filter. Here we will replace the
ORPHANED condition with our own filter, since we want to actually search for Tivoli
Storage Manager option files, not orphaned files (Figure 6-138).


Figure 6-138 Update the selection with own data

Use the Del button to delete the ORPHANED condition, then select NAME from the
Attributes pull-down, and the Add button to add another Attributes condition. We will
specify to search for Tivoli Storage Manager option files (including with an .smp extension
for sample files), as in Figure 6-139.

Figure 6-139 Enter the file search criteria

After each file pattern entry, click Add to save it. When all search arguments are entered,
click OK to save the search. The selection is now complete as in Figure 6-139.


Figure 6-140 File Filter selection reconfirm

Click OK again. Save the search with a new description and name (File -> Save As), so
that you do not overwrite the original Tivoli.Orphaned File Constraint. We called the
search “TSM Option File search.”
Now we have to embed the new Constraint into our Scan.
5. Bind the new Constraint into your Scan
To create or add this entry, go to IBM Tivoli SRM -> Monitoring -> Scans ->
Tivoli.Default.Scan. In the Profiles tab, add administrator.TSM Opt File search to the
right hand panel as in Figure 6-141. This will bind the Tivoli Storage Manager Option file
search to the filesystem search.

Figure 6-141 bind the Orphan search into Profiles to apply to Filesystems column

Finally, save and run the Scan. Check the Scan Job log for correct execution, as shown in
Figure 6-142.


Figure 6-142 Scan log check

6. Generate Report to find defined Constraint
Now look for the results of the file name search. Select IBM Tivoli SRM -> Reporting ->
Usage Violations -> Constraint Violations -> By Computer, select all computers and
generate the report. The report will present a summary as in Figure 6-143.

Figure 6-143 Summary report of all Tivoli Storage Manager option files


To drill down, click the magnifying glass on BONNIE as in Figure 6-144. This shows all the
filesystems on BONNIE where matching files were found.

Figure 6-144 File selection for computer BONNIE

Click the magnifying class on a filesystem (e.g. C drive). This will show all the files found
which matched the pattern, as in Figure 6-145. Note there are 13 files reported, which
matches the summary view given in Figure 6-135 on page 339.

Figure 6-145 Report for Tivoli Storage Manager Option file searched


You can also drill down to individual files, for detailed information as in Figure 6-146.

Figure 6-146 File detail information

6.5 Creating customized reports
Customized Reporting within Tivoli Storage Resource Manager is done through the My
Reports option, which is available for both Tivoli Storage Resource Manager and Tivoli
Storage Resource Manager for Databases.

There are three main options available within My Reports:
System Reports
Reports owned by username
Batch Reports

System Reports, while included here in the customized reporting section, is in fact not
customizable currently. We will still discuss it in this section as it is part of the My Reports
group.

Reports owned by username’s Reports, where username is the currently logged in Tivoli
Storage Resource Manager username, are modified versions of standard reports from the
Reporting option. You will only see reports here that you have modified and saved.

Batch Reports are reports that are typically set up to run on a schedule, although they can be
run interactively. The key difference between Batch Reports and other reporting options is
that with Batch Reports, the output will always be written to an output file rather than
displayed on the screen.

6.5.1 System Reports
These reports can, at this point in time at least, only be run as is. You cannot modify the
parameters in any way, nor can you add additional reports to the list.


These reports provide the same information than is available from running reports from the
Reporting option. The intent of these reports is to provide frequently needed information,
which can be provided quickly and repetitively without having to reenter parameters.

Figure 6-147 shows the available System Reports for Tivoli Storage Resource Manager.

Figure 6-147 My Reports - System Reports

Figure 6-148 shows the output from running the Storage Capacity system report. We could
have generated exactly the same output by selecting IBM Tivoli SRM -> Reporting ->
Capacity -> Disk Capacity -> By Computer -> Generate Report. Obviously, selecting IBM
Tivoli SRM -> My Reports -> Storage Capacity is a lot simpler.


Figure 6-148 My Reports - Storage Capacity

The System Reports available for Tivoli Storage Resource Manager for Databases are shown
in Figure 6-149. While there are quite a few reports available, they fall into three main
categories:
Database storage by database
Database storage by user
Database freespace

The only report that does not fall into one of those categories is a usage violation report.

Figure 6-149 shows the output from the All Dbms - User Database Space Usage report. We
are not so much interested in the report contents as such here, but rather in the fact that when
the report was run it produced a report for all users. You can go back to the selection tab and
select specific users if required. This capability exists for all of the System Reports.


Figure 6-149 Available System Reports for databases

6.5.2 Reports owned by a specific username
In concept this option is very similar to System Reports. You can include here those reports
that you need to run regularly, consistently and easily. The difference, compared to System
Reports, is that you get to decide what reports are included and what they look like.

However, it is important to remember that you will only see those reports that have been
created by the currently logged in Tivoli Storage Resource Manager username.

We will define a report here for db2admin, the username that we are currently logged in as.

We will create a report that is exactly the same as the Storage Capacity system report as
shown in Figure 6-148. In practice this is not something you would normally do as a report
already exists. However, this will demonstrate more clearly how the options relate to each
other.

We select IBM Tivoli SRM -> Reporting -> Capacity -> Disk Capacity -> By Computer ->
Generate Report. Once the report is produced, we save the report definition, using the name
My Storage Capacity. This is shown in Figure 6-150.


Figure 6-150 Create My Storage Capacity report

Once the report is saved you will see it available under username’s Reports for db2admin as

There are a few features of saved reports worth mentioning here. Firstly, characteristics such
as sort order are not saved with the report definition; however, selection criteria are saved.
Secondly, you can override the selection criteria when running your report. By default the
objects selected at the time of the save only will be reported. However, you can use the
Selection tab when running the saved report to include or exclude objects from the report. If
you change selection criteria you can resave the report, or save it under another name to
update the definition or create a new definition respectively.


Figure 6-151 My Storage Report saved

Database Reports created for specific users, in this case db2admin, are set up the same as in
Tivoli Storage Resource Manager.

We will show one brief example here. We will take one of the reports that we created earlier in
our discussion on Reporting (in this case Figure 6-25 on page 268) the Monitored Tables by
RDBMS Type report and set it up to be able to run more easily.

First we run the report by choosing IBM Tivoli SRM for Databases -> Reporting -> Usage
-> All DBMSs -> Tables -> Monitored Tables -> By RDBMS Type. We then saved the report
definition, naming it Monitored Tables by RDBMS Type. This is shown in Figure 6-152.


Figure 6-152 Monitored Tables by RDBMS Types customized report

The report is more easily run now by choosing IBM Tivoli SRM for Databases -> My
Reports -> username’s Reports -> Monitored Tables by RDBMS Type.

6.5.3 Batch Reports
In this section we will show how we set up some Batch Reports. All of the reports were set up
in the same way so we will use only one as an example. The process is the same whether the
report is for Tivoli Storage Resource Manager or Tivoli Storage Resource Manager for
Databases.

To set up a new report right-click on Batch Reports and select New Batch Report. You will
then see the screen shown in Figure 6-153.


Figure 6-153 Create a Batch Report

Now, it is a simply a matter of specifying what has to be reported, plus when and what the
output should be. In this case we are going to create a system uptime report. As shown in
Figure 6-154, we entered our report description of System Uptime and have then selected
Availability ->Computer Uptime ->By Computer and clicked >>. Our selection is then
moved into the right hand panel, Current Selections.

Figure 6-154 Create a Batch Report - report selection

We then selected the Selection tab, which is shown in Figure 6-155. Here we are able to
select a subset of available data by either reporting for a specified time range or a subset of
available systems. We took the defaults here.


Figure 6-155 Create a Batch Report - selection

On the Options tab, we specified that the report should be executed and generated on the
Agent called LOCHNESS, which is our Tivoli Storage Resource Manager server. We selected
HTML for Report Type Specification and then changed the rules for the naming of the
output file under Output File Specification.

By default the name will be {Report creator}.{Report name}.{Report run number}. In this
case we do not really care who created the report and having a variable like report run
number, which changes every time a new version of the report is created and makes it difficult
to access the file from a static Web page. So we changed the report name to be {Report
name}.html.

The report will be created in <install-directory>Tivoli Storage Resource ManagerlogTivoli
Storage Resource Manager-agent-namereports on the Agent system where the report job is
executed. There is no ability to override the directory name. For example, c:program
filestivolitsrmloglochnessreports on our Windows 2000 Tivoli Storage Resource Manager
server LOCHNESS or /usr/tivoli/tsrm/log/brazil/reports on our AIX Tivoli Storage Resource
Manager Agent BRAZIL.

The Option tab is shown in Figure 6-156.

Note here that it possible to run a script after the report is created to perform some type of
post-processing. For example, you might need to copy the output file to another system if your
Web server is on a system that is not running an Tivoli Storage Resource Manager Agent.


Figure 6-156 Create a Batch Report - options

On the When to REPORT tab we specified when the report should be generated. We chose
REPORT Repeatedly and then selected a time early in the morning (3:15 AM) and specified
that the report should be generated every day. This is shown in Figure 6-157.


Figure 6-157 Create a Batch Report - when to report

We left the Alert tab options as default, but it is possible to generate an Alert through several
mechanisms including e-mail, an SNMP trap, or the Windows event log should the generation
of the report fail.

Finally, we saved the report, calling it System Uptime, as shown in Figure 6-158.


Figure 6-158 Create a Batch Report - saving the report

We will use the same example here as we used in 6.5.2, “Reports owned by a specific
username” on page 348, that is a Monitored Tables by RDBMS Type, but here we will save it
in HTML format.

We choose IBM Tivoli SRM for Databases -> My Reports -> Batch Reports, right-click
Batch Reports and select New Batch Report as shown in Figure 6-159.


Figure 6-159 Create a database Batch Report

Figure 6-160 shows the Report tab. We expanded in turn Usage -> All DBMSs -> Tables ->
Monitored Tables -> By RDBMS Type and clicked >>. We also entered a Description of
Monitored Tables by RDBMS Type.

Figure 6-160 Create a database Batch Report - Report tab

We accepted the defaults on the Selection tab, which is to report on all RDBMS types and
then went to the Options tab, shown in Figure 6-161. We set the Agent computer, which will
run the report to GALLIUM.

Note that the system that you run the report on must be licensed for each type of database
that you are reporting on. If we were to run the report on LOCHNESS, the Tivoli Storage


Resource Manager server system, we would need to have the Tivoli Storage Resource
Manager for Databases licences for Oracle and SQL-Server licences loaded there even
though LOCHNESS does not run these databases.

We also set the report type to HTML and changed the output file name to be {Report
name}.html. This is shown in Figure 6-161.

Figure 6-161 Create a database Batch Report - Options tab

On the When to Report tab, shown in Figure 6-162, we chose REPORT Repeatedly and set
a start time.


Figure 6-162 Create a database Batch Report - When to Report tab

We did not change anything in the Alert tab. We saved the definition with the name Monitored
Tables by RDBMS Type as shown in Figure 6-163.

Figure 6-163 Create a database Batch Report - save definition

We can now run the report by choosing IBM Tivoli SRM -> My Reports-> Batch Reports
and then right-clicking on db2admin.Monitored Tables by RDBMS Type and choosing Run
Now.

Figure 6-164 shows the output from the report execution.


Figure 6-164 Monitored Tables by RDBMS Type batch report output

6.6 Setting up a schedule for daily reports
Tivoli Storage Resource Manager can produce reports according to a schedule. In our lab
environment, we set up a number of Batch Reports as shown in Figure 6-165. Note that the
name of each of the reports is prefixed by db2admin. This is the Windows username that we
used to log into Tivoli Storage Resource Manager. Even though the reports were created by a
particular user, other Tivoli Storage Resource Manager administrative users still have access
to the reports (Tivoli Storage Resource Manager non-administrative users can only look at
the results).

It is possible to generate output from Batch Reports in various formats including HTML,CSV,
(comma separated values) and formatted reports. For all of the reports that we set up, we
specified HTML as the output type, and also set them to run on a daily schedule. That way it
is very easy to use a browser to quickly look at the state of the organization’s storage. It also
means that anyone can look at the reported data through their browser, without having
access to, or indeed, knowing how to use Tivoli Storage Resource Manager. Obviously, if
unrestricted access to this data was not desirable some sort of password based security
could be included within the Web page.

Currently, all of the HTML output from Batch Reports is in table format - graphs cannot be
produced. There is also no ability to affect the layout of the reports in terms of sort order,
nominating the columns to be displayed or the column size. Using the interactive reporting
capability of the product does allow graphs to be produced and gives you some additional
capability in determining what the output looks like. To go further than that you can export to a
CSV file, and then use a tool such as Lotus 1-2-3® or Microsoft Excel to manipulate the
output.

The next section shows how to develop the Web site.


Figure 6-165 Batch Reports listing

6.7 Setting up a reports Web site
Since Tivoli Storage Resource Manager can easily generate reports in HTML format, it is a
logical extension to set up a Web site where the reports can be easily viewed.

Since Tivoli Storage Resource Manager itself is easy to install and use, we likewise took a
fairly simplistic view to creating the Web site. We used the Microsoft Word Web Page Wizard
to create the basic layout of the page as shown in Figure 6-166.

The main page has two frames. In the left hand frame we have created links to each of the
report files. The right hand frame is where the reports are displayed.

As additional Batch Reports are needed, it is a relatively simple process of editing the HTML
source and including another hot link.

Obviously, this could be made more sophisticated. An example would be to have the browser
list all HTML files within the report directory.


Figure 6-166 MS Word created Web page

We then used the Virtual Directory Creation Wizard within Microsoft Internet Information
Server (IIS) to set up access to the reports as shown in Figure 6-167.


Figure 6-167 Setting up a Virtual Directory within IIS

We could then access the reports through a Web browser as shown in Figure 6-168.


Figure 6-168 Reports available from a Web browser

6.8 Charging for storage usage
Through the optional IBM Tivoli Storage Resource Manager for Chargeback product, IBM
Tivoli Storage Resource Manager provides the ability to produce Chargeback information for
storage usage. The following items can have charges allocated against them:
Operating system storage by user
Operating system disk capacity by computer
Storage usage by database user
Total size by database-tablespace

For each of the Chargeback by user options, a Profile needs to be specified. Profiles are
covered in 5.1.6, “Profiles” on page 180.

IBM Tivoli Storage Resource Manager can directly produce an invoice or create a file in CIMS
format. CIMS is a set of resource accounting tools that allow you to track, manage, allocate,
and charge for IT resources and costs. For more information on CIMS see:
http://www.cims.com.

Figure 6-169 shows the Parameter Definition screen. The costs allocated here do not
represent any real environment, but represent an example, based on these assumptions:
Disk hardware costs, including controllers and switches. is $0.50 per MB
Hardware costs are only 20% of the total cost over the life of the storage = $2.50 /MB
On average only 50% of the capacity is used = $5.00 /MB used
The expected life of the storage is 4 years - $5.00 /48 = 0.1042 /MB /month


The figures used are for monthly Chargeback
Chargeback is for cost recovery only, no profit

Figure 6-169 Chargeback parameter definition

In this example we have chosen to perform Chargeback by computer. It is possible to
separately charge for database usage and use a different rate from the computer rate. To do
this you would need to set up a Profile that excluded the database data, otherwise, it would be
counted twice.

Chargeback is useful, even if you do not actually collect revenue from your users for the
resources consumes. It is a very powerful tool for raising the awareness within the
organization of the cost of storage, and the need to have the appropriate tools and processes
in place to manage storage effectively and efficiently.

Figure 6-170 shows the Chargeback Report being created. Currently, it is not possible to have
the Chargeback Report created automatically (that is, scheduled).


Figure 6-170 Create the Chargeback Report

Example 6-3 shows the Chargeback Report that was produced.

Example 6-3 Chargeback Report

Administrator.hb

Name SPACE COST
(MB) 0.1042/MB

100 5 0.52

group total 5 0.52


Tivoli.Default User Group

Name SPACE COST
(MB) 0.1042/MB

[Supervisor] 524 54.60
1009 0 0.00
101 4 0.42
1010 1 0.10
1012 1 0.10
1084 1 0.10
111 1 0.10
1414 24 2.50
202 0 0.00
240 1 0.10
50 1 0.10
5115 10 1.04
8482 7 0.73
9727 0 0.00
adm 3 0.31
admin 523 54.50
Administrators 37,687 3,926.99


backup 27 2.81
bin 1,173 122.23
cbres 1 0.10
daemon 1 0.10
guest 1 0.10
imnadm 2 0.21
invscout 1 0.10
itso_hb 134 13.96
itso_usr 1 0.10
IUSR_LOCHNESS 1 0.10
IWAM_LOCHNESS 1 0.10
lotti 7 0.73
lp 1 0.10
nobody 1 0.10
oracle 5 0.52
root 5,857 610.30
sys 1 0.10
SYSTEM 3 0.31
uucp 2 0.21

group total 46,008 4,793.97

Run Summary 24-Sep-02

User Usage Invoice 46,013 MB 4,794.49

run total 4,794

Example 6-4 shows the Chargeback Report in CIMS format.

Example 6-4 Chargeback Report in CIMS format
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Administrator,hb,100,1,4230
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User
Group,[Supervisor],1,536328
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,1009,1,0
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,adm,1,2820
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,admin,1,535384
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User
Group,Administrators,1,38591436
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,backup,1,27102
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,bin,1,1200421
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,cbres,1,2
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,daemon,1,413
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,guest,1,1
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,imnadm,1,1257


TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,invscout,1,1
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,itso_hb,1,137157
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,itso_usr,1,2
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,IUSR_LOCHNESS,1,3
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,IWAM_LOCHNESS,1,5
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,lotti,1,6497
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,lp,1,339
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,nobody,1,2
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,oracle,1,4389
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,root,1,5996617
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,sys,1,26
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,SYSTEM,1,2092
TSAOU1,20020924,20020924,13:25:00,13:25:59,,3,Tivoli,Default User Group,uucp,1,1185


7

Chapter 7. Protecting and maintaining Tivoli
Storage Resource Manager
This chapter discusses backup and restore strategies to protect the IBM Tivoli Storage
Resource Manager environment. While there are many different backup products available,
we will focus on IBM Tivoli Storage Manager. We assume that you have knowledge of IBM
Tivoli Storage Manager, which can be obtained from the following Redbooks:
IBM Tivoli Storage Management Concepts, SG24-4877
IBM Tivoli Storage Manager Implementation Guide, SG24-5416
Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment, SG24-6141
Backing Up DB2 Using Tivoli Storage Manager, SG24-6147
Using Data Protection for Microsoft SQL Server, SG24-6148

We will discuss backup scenarios using both IBM DB2 UDB and Microsoft SQL-Server. Note
that the database included as standard with Tivoli Storage Resource Manager, Cloudscape,
is not recommended for a production environment, hence we do not discuss its backup here.


7.1 IBM Tivoli Storage Resource Manager environment

Tivoli Storage Resource Manager Components

A repository - can be DB2/UDB, Oracle, Sybase or MS SQL-Server
Cloudscape not recommended for production use
Configuration, log and report files

Tivoli Storage Resource Manager Agent
Configuration, log and report files

ibm.com/redbooks

Figure 7-1 Tivoli Storage Resource Manager components

Tivoli Storage Resource Manager relies on two main components: a Server and one or more
Agents. Each of them stores configuration data in text files and/or in databases. We describe
now each component and explain where they store their configuration information.

7.1.1 IBM Tivoli Storage Resource Manager Server
The Tivoli Storage Resource Manager Server stores its configuration:
In flat files in the directories (for Windows platforms - similar for UNIX):
– Program Filestivolitsrmconfig
– Program Filestivolitsrmscripts
In a DB2, SQL-Server, Oracle, Sybase, or Cloudscape database

The configuration files contain information including the TCP/IP ports to be used by the
Server and Agents, database name, and username.

The Tivoli Storage Resource Manager database contains information about the configured
Agents, policies, schedules, and the actual storage resource data.

Our Tivoli Storage Resource Manager database is called ITSRMDB.


7.1.2 Tivoli Storage Resource Manager Agents
All Agents store their configuration in flat files located in the directory Program
Filestivolitsrmconfig.

7.2 Integration with IBM Tivoli Storage Manager

Integration with Tivoli Storage Manager
Tivoli Storage
Resource Manager

TSM
config B/A
files client

DB
utility
or
TSM
for
Database DB TSM API

TSM storage pools

ibm.com/redbooks

Figure 7-2 Tivoli Storage Resource Manager integration with Tivoli Storage Manager

The IBM Tivoli Storage Resource Manager Web site is:
http://www-3.ibm.com/software/tivoli/products/storage-resource-mgr/

7.2.1 IBM Tivoli Storage Manager
IBM Tivoli Storage Manager is an enterprise-wide storage management application for the
network. It provides automated storage management services (including backup and restore,
archive and retrieve, hierarchical space management and Disaster Recovery) to multi-vendor
workstations, personal computers, mobile laptops, and servers of all sizes and operating
systems, which are connected through WAN, LAN, and SAN. IBM Tivoli Storage Manager
includes these components:
Server - The repository for all backups and maintains the backup policies and schedules
Clients - Backup data to the Tivoli Storage Manager Server
API - Available to allow other applications to interface to Tivoli Storage Manager

Chapter 7. Protecting and maintaining Tivoli Storage Resource Manager 371

The IBM Tivoli Storage Manager solution set also includes the following optional products:
IBM Tivoli Storage Manager for Databases
IBM Tivoli Storage Manager for ERP
IBM Tivoli Storage Manager for Application Servers
IBM Tivoli Storage Manager for Mail
IBM Tivoli Space Manager (HSM client)

Each of these products provide the interface between the IBM Tivoli Storage Manager API
and an application or database API.

The Tivoli Storage Manager Web site is:
http://www-3.ibm.com/software/tivoli/products/storage-mgr/

IBM DB2/UDB databases can be backed up to IBM Tivoli Storage Manager as DB2/UDB has
built in IBM Tivoli Storage Manager API support.

Normal flat files (configuration, log and report files) on the Tivoli Storage Resource Manager
Server can be backed up using the IBM Tivoli Storage Manager Backup/Archive client.

Therefore, the two client types (Backup/Archive client for flat files, API client for DB2 backup)
work together to provide full data protection for your Tivoli Storage Resource Manager
environment.

The DB2/UDB API client and the IBM Tivoli Storage Manager Backup/Archive client can run
simultaneously on the same DB2 server, however, they are totally separate clients as far as
the Tivoli Storage Manager server is concerned and we will configure them separately.

7.2.2 Setup for backing up Tivoli Storage Resource Manager
We will use the following environment for backing up our Tivoli Storage Resource Manager
Server to a Tivoli Storage Manager Server:
Tivoli Storage Manager Server for AIX, V5.2.0.0, running on BANDA
Tivoli Storage Manager Backup/Archive client for Windows 2000, V5.2.0.0 running on the
Tivoli Storage Resource Manager Server BONNIE
Tivoli Storage Manager DB2/UDB API client for Windows 2000, V5.2.0.0 running on the
Tivoli Storage Resource Manager Server BONNIE
Tivoli Storage Manager Backup/Archive client for LINUX, V5.2.0.0 running on the Tivoli
Storage Resource Manager Agent SUSE82-1.


Backup environment for Tivoli Storage Resource Manager

Ethernet

Tivoli SRM Agent
Tivoli SRM Server TSM Client 5.2.0.0
TSM Server 5.2.0.0 DB2 V7.1
TSM Client 5.2.0.0
TSM API 5.2.0.0
SuSE82-1
TSM Client 5.2.0.0
BANDA BONNIE
AIX 5.1.0 ML4 Windows2000 SP3

ibm.com/redbooks
© 2002 IBM Corporation

Figure 7-3 Backup environment tor Tivoli Storage Resource Manager

The summary of the setup steps is:
1. Configure the Tivoli Storage Manager Server to receive backups from the Tivoli Storage
Resource Manager Server.
2. Configure the DB2/UDB API and Tivoli Storage Manager Backup/Archive clients on the
Tivoli Storage Resource Manager Server.

7.2.3 Tivoli Storage Manager Server configuration
We assume that:
The Tivoli Storage Manager Server is installed and configured with sufficient storage.
The Tivoli Storage Manager Backup/Archive and API code is installed on the Tivoli
Appropriate backup policies (policy domain, management classes, copy groups) for
non-DB2 backups (that is, flat files) have been implemented. You should be doing OS-level
backups of the Windows 2000 Server, which runs the Tivoli Storage Resource Manager
code.

We need to specify a management class and copy group within a policy domain for DB2
backups. We recommend defining a separate policy domain for the DB2 backups. We will
define a domain called DB2_DOMAIN and register the nodename assigned to the DB2
backup client (in our case, BONNIE_DB2) to it.

DB2 places special requirements on the management class. Each DB2 database backup is
stored as a unique object in the Tivoli Storage Manager Server, by specifying a time stamp as


part of the low-level qualifier (LL_NAME). This means that the DB2 backups must be
manually deactivated. This also means that the management class that the backup objects
are bound to should have retention settings that change the deactivated backup objects to be
expired immediately. The retention settings for a backup copy group that would provide this is
RETONLY=0 and VERDELETED=0.

Example 7-1 shows typical Tivoli Storage Manager commands to define an adequate
environment for DB2 backups. We define a policy domain, policy set, management class, and
copy groups for the DB2 environment. We activate the policy set and register our client node
to the policy domain. We are using a storage pool called BACK_LTO as the destination for our
DB2 backups.

Example 7-1 Tivoli Storage Manager setup for Tivoli Storage Resource Manager DB2 backups
DEFINE DOMAIN DB2_DOMAIN DESCRIPTION="Domain for DB2 backups" BACKRETENTION=30
ARCHRETENTION=365

DEFINE POLICYSET DB2_DOMAIN DB2_POLICY DESCRIPTION="DB2 BACKUPS Policyset"

DEFINE MGMTCLASS DB2_DOMAIN DB2_POLICY DB2_MGMTCLASS DESCRIPTION="Mgmtclass for DB2
databases" SPACEMGTECHNIQUE=NONE AUTOMIGNONUSE=0 MIGREQUIRESBKUP=YES

DEFINE COPYGROUP DB2_DOMAIN DB2_POLICY DB2_MGMTCLASS DESTINATION=BACK_LTO FREQUENCY=0
VEREXISTS=1 VERDELETED=0 RETEXTRA=0 RETONLY=0 MODE=MODIFIED SERIALIZATION=SHRSTATIC

DEFINE COPYGROUP DB2_DOMAIN DB2_POLICY DB2_MGMTCLASS TYPE=ARCHIVE DESTINATION=ARCHIVEPOOL
RETVER=NOLIMIT SERIALIZATION=SHRSTATIC

ASSIGN DEFMGMTCLASS DB2_DOMAIN DB2_POLICY DB2_MGMTCLASS

ACTIVATE POLICYSET DB2_DOMAIN DB2_POLICY

REGISTER NODE BONNIE_DB2 BONNIEDB2 DOMAIN=DB2_DOMAIN ARCHDELETE=YES BACKDELETE=YES
USERID=NONE

The following parameters for the backup copy group were set:
VEREXISTS=1 to keep only one version of the backup file as the name of each DB2
backup is unique. (There will never be a newer version of the backup image with the same
name.)
VERDELETED=0 so that if the backup file has been deleted (through db2adutl), then
Tivoli Storage Manager should not keep an inactive version of this file.
RETEXTRA=0 (the same value as RETONLY) parameter will never be used as you will
never have more than one version of the backup file. To prevent confusion set this
parameter to the same value as RETONLY.
RETONLY=0 so that when a backup image file becomes inactive it will be purged from the
Tivoli Storage Manager Server at the next expiration.

7.2.4 Client configuration
The client configuration takes place on BONNIE, the Tivoli Storage Resource Manager
Server, since this will be the Tivoli Storage Manager client. For Tivoli Storage Resource
Manager Agents, you should perform regular backups using the Tivoli Storage Manager
Backup/Archive client. No special considerations for Tivoli Storage Resource Manager should
be necessary. We will focus primarily on the setup for backing up the DB2 repository.


Tivoli Storage Manager nodenames
The Tivoli Storage Resource Manager Server will use two different Tivoli Storage Manager
client names, for DB2 and non-DB2 backups. We will assume the client named BONNIE (for
the Tivoli Storage Manager Backup/Archive client) is already defined to the STANDARD
policy domain. The client name BONNIE_DB2 will be used for DB2 backups, which was
defined to the Tivoli Storage Manager Server in Example 7-1. Figure 7-2 shows the server
QUERY NODE command to display currently configured clients.

Example 7-2 Tivoli Storage Manager clients list
tsm: BANDA>q node *bonnie*

Node Name Platform Policy Domain
Days Since Days Since Locked?
Name Last Acce- Password
ss Set
------------------------- -------- -------------- ---------- ---------- -------
BONNIE WinNT STANDARD <1 <1 No
BONNIE_DB2 WinNT DB2_DOMAIN <1 <1 No

DB2 configuration
Now, you must configure DB2 so that it uses the correct Tivoli Storage Manager node name,
password, and management class.

This can be done in two different ways. Either you define these parameters within DB2 as
shown in Example 7-4, or you can rely on information taken from the Tivoli Storage Manager
client options file, in association with the default Tivoli Storage Manager settings defined in
7.2.3, “Tivoli Storage Manager Server configuration” on page 373.

In both cases you will need to set some OS environment variables so that the Tivoli Storage
Manager API is able to find the Tivoli Storage Manager options file and knows where to write
log files. These environment variables are shown in Example 7-3.

Tip: We used a different DSM.OPT (DB2_DSM.OPT) file to save our DB2 environment. To
“inform” our DB2 environment, you have to define all the DSMI_ variables to the system. If
you should choose this simple way, you do not have to add the Tivoli Storage Manager
entries into the DB2 configuration of the database ITSRMDB as shown in Example 7-4,
TSM_MGMTCLASS, TSM_NODENAME, TSM_OWNER, TSM_PASSWORD. If you have
these entries in the DB2 configuration, you can remove them with the following commands:

update db cfg for ITSRMDB using TSM_MGMTCLASS ‘’

update db cfg for ITSRMDB using TSM_OWNER ‘’

update db cfg for ITSRMDB using TSM_NODENAME ‘’

update db cfg for ITSRMDB using TSM_PASSWORD ‘’

Otherwise, define them into the system variables as shown in Example 7-3.

Example 7-3 IBM Tivoli Storage Manager environment variables for API client
DSMI_CONFIG=c:tivolitsmapidb2_dsm.opt
DSMI_DIR=c:tivolitsmapi
DSMI_LOG=c:tivolitsmapi


There are four Tivoli Storage Manager parameters that can be defined within DB2:
Management class
Owner
Nodename
Password

Example 7-4 shows the setup of these parameters, however, our recommendation is not to
set any of these parameters, but to rely on the Tivoli Storage Manager options file and default
settings. If you rely on the Tivoli Storage Manager options file and default settings, then for the
above four settings: the management class should be the default management class for the
node, the owner is not required to be set, the nodename comes from the Tivoli Storage
Manager options file and the password, when used with the Tivoli Storage Manager options
file setting passwordaccess generate, is stored in encrypted form in the Windows registry or
in a file on UNIX platforms.

Being able to set these options within DB2 does offer some flexibility when you have multiple
databases on the one system, which has different backup requirements. For example, you
can set different management classes for each database.

Example 7-4 DB2 configuration
db2 => update db cfg for ITSRMDB using TSM_MGMTCLASS DB2_MGMTCLASS
DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
DB21026I For most configuration parameters, all applications must disconnect
from this database before the changes become effective.

db2 => update db cfg for ITSRMDB using TSM_OWNER BONNIE_DB2

db2 => update db cfg for ITSRMDB using TSM_NODENAME BONNIE_DB2

db2 => update db cfg for ITSRMDB using TSM_PASSWORD BONNIEDB2

db2 => get db cfg for ITSRMDB
.
.
.
Number of database backups to retain (NUM_DB_BACKUPS) = 12
Recovery history retention (days) (REC_HIS_RETENTN) = 366
TSM management class (TSM_MGMTCLASS) = DB2_MGMTCLASS
TSM node name (TSM_NODENAME) = BONNIE_DB2
TSM owner (TSM_OWNER) = BONNIE_DB2
TSM password (TSM_PASSWORD) = *********

db2 => quit

Now, you must configure DB2 for using online backups if you plan to run online backups of
your database. The recovery mode is set by the LOGRETAIN parameter.


Example 7-5 Configure for online backup

db2 => get db cfg for ITSRMDB
.
.
Log retain for recovery enabled (LOGRETAIN) = OFF
.
.
db2 => update db cfg for ITSRMDB using LOGRETAIN RECOVERY

db2 => quit
DB20000I The QUIT command completed successfully.

C:PROGRA~1SQLLIBBIN>db2stop force
SQL1064N DB2STOP processing was successful.

C:PROGRA~1SQLLIBBIN>db2start
SQL1063N DB2START processing was successful.

Storing the API password
Example 7-6 shows how to configure these parameters into the Tivoli Storage Manager API
client, using the dsmapipw command.

Example 7-6 Configuring DB2 backup password to Tivoli Storage Manager API client
C:Program FilesSQLLIBadsm>dsmapipw.exe

*************************************************************
* Tivoli Storage Manager *
* API Version = 5.2.0 *
*************************************************************
Enter your current password:bonniedb2
Enter your new password:bonniedb2
Enter your new password again:bonniedb2

Your new password has been accepted and updated.

Stop and re-start DB2 to allow the changes to take effect.

Example 7-7 Stop and start DB2
C:PROGRA~1SQLLIBBIN>db2stop

C:PROGRA~1SQLLIBBIN>db2start

Client option files
Now configure the Tivoli Storage Manager API client option file, dsm.opt located in
C:Tivolitsmapi so that DB2 will point to the correct Tivoli Storage Manager Server, BANDA.

Example 7-8 API dsm.opt file sample
NODENAME BONNIE_DB2
PASSWORDACCESS GENERATE


TCPSERVERADDRESS banda.almaden.ibm.com

As the DB2 database files are backed up using DB2, they must be excluded from backup by
the normal Backup/Archive client. We excluded all DB2 files except the recovery log files. You
must update the dsm.opt file located in c:tivolitsmbaclient directory.

Example 7-9 baclient dsm.opt file sample
NODENAME BONNIE
PASSWORDACCESS GENERATE
TCPSERVERADDRESS banda.almaden.ibm.com

EXCLUDE C:DB2...*
INCLUDE C:DB2...*.LOG

7.2.5 Additional considerations
The previous explanation shows you how to perform a basic configuration for Tivoli Storage
Manager, so that you can send DB2 backups directly to Tivoli Storage Manager storage.
However, you should note the following considerations:
DB2 archives are generated on local disk. They must be protected against loss through
mirroring or archival. You can also activate an exit to automatically archive DB2 logs.
Old database backups must be manually deleted from the Tivoli Storage Manager Server
once they are not needed using the db2adutl utility.
Depending on your recovery requirements, you may have to configure additional DB2
parameters (such as NUM_DB_BACKUPS and REC_HIS_RETENTN).

See the redbook Backing Up DB2 Using Tivoli Storage Manager, SG24-6147 for detailed
information on setting up DB2 backups with Tivoli Storage Manager.

7.3 Backup procedures
We describe now the procedures used to backup the major components of Tivoli Storage
Resource Manager.


Tivoli Storage Resource Manager backup procedures
Tivoli Storage Resource Manager Agents
Incremental backup of files

Incremental backup of files

Tivoli Storage Resource Manager database
Online backup

ibm.com/redbooks

Figure 7-4 Procedures used to backup Tivoli Storage Resource Manager

7.3.1 Agent files
The configuration files contain relatively static information. Therefore, we recommend using a
traditional incremental backup policy to backup the files. In addition, there will be report and
log files to be backed up. Again a traditional incremental backup method is appropriate here.
We show backup of a Linux Agent, SUSE82-1 using the Tivoli Storage Manager
Backup/Archive client in Example 7-10.


Example 7-10 Backup of Agent’s files
linux:/opt/tivoli/tsm/client/ba/bin # dsmc i /opt/

IBM Tivoli Storage Manager
Command Line Backup/Archive Client Interface - Version 5, Release 2, Level 0.0
(c) Copyright by IBM Corporation and other(s) 1990, 2003. All Rights Reserved.

Node Name: SUSE82-1
Please enter your user id <SUSE82-1>:

Please enter password for user id "SUSE82-1":

Incremental backup of volume '/opt/’
.
.
Normal File--> 668,678 /opt/tivoli/TSRM/agent/lib/ibmpkcs.jar [Sent]
Normal File--> 1,928 /opt/tivoli/TSRM/agent/lib/local_policy.jar [Sent]
Normal File--> 168 /opt/tivoli/TSRM/config/agent.config [Sent]
Normal File--> 233,710 /opt/tivoli/TSRM/install/TSRMRequest.jar [Sent]
Normal File--> 1,831,100 /opt/tivoli/TSRM/install/TSRMins.jar [Sent]
.
.
Normal File--> 7,365 /opt/tivoli/TSRM/java/lib/security/cacerts [Sent]
Normal File--> 2,224 /opt/tivoli/TSRM/java/lib/security/java.policy [Sent]
Normal File--> 4,083 /opt/tivoli/TSRM/java/lib/security/java.security [Sent]
Directory--> 720 /opt/tivoli/TSRM/log/suse82-1 [Sent]
Directory--> 48 /opt/tivoli/TSRM/log/suse82-1/restart [Sent]
Normal File--> 542 /opt/tivoli/TSRM/log/suse82-1/Tivoli.Default
Probe.0005_probe.00000362.log [Sent]
Normal File--> 1,025 /opt/tivoli/TSRM/log/suse82-1/Tivoli.Default
Scan.0009_scan.00000407.log [Sent]
Normal File--> 1,025 /opt/tivoli/TSRM/log/suse82-1/Tivoli.Default
Scan.0010_scan.00000413.log [Sent]
Normal File--> 199
/opt/tivoli/TSRM/log/suse82-1/Tivoli.Discovery.0004_discovery.00000371.log [Sent]
Normal File--> 1,930 /opt/tivoli/TSRM/log/suse82-1/agent_000001.log [Sent]
Normal File--> 163 /opt/tivoli/TSRM/log/suse82-1/agent_000002.log [Sent]
Normal File--> 1,069
.
.
Successful incremental backup of '/opt/*'

Total number of objects inspected: 20,633
Total number of objects backed up: 20,352
Total number of objects updated: 0
Total number of objects rebound: 0
Total number of objects deleted: 0
Total number of objects expired: 0
Total number of objects failed: 0
Total number of bytes transferred: 416.44 MB
Data transfer time: 20.84 sec


Network data transfer rate: 20,454.91 KB/sec
Aggregate data transfer rate: 2,280.36 KB/sec
Objects compressed by: 0%
Elapsed processing time: 00:03:07

7.3.2 Server files
We used the standard Tivoli Storage Manager Backup/Archive Windows 2000 client to
execute a daily incremental backup of all the files excluding the database. The operating
system components, such as the Windows registry, are also backed up.

Running the backup
The output of the backup procedure is shown in Example 7-11.

Example 7-11 Backup of server files
C:tivolitsmbaclient>dsmc inc

Node Name: BONNIE
Session established with server BANDA: AIX-RS/6000
Server Version 5, Release 2, Level 0.0
Server date/time: 06/11/2003 14:03:34 Last access: 06/11/2003 11:52:18

Incremental backup of volume 'BONNIEC$'

Incremental backup of volume 'BONNIEF$'

Incremental backup of volume 'SYSTEMOBJECT'
Backup System Object: 'COM+ Database'.

Backup System Object: 'Event Log'.

Backup System Object: 'System and Boot Files'.

Backup System Object: 'Registry'.

Backup System Object: 'RSM Database'.

Backup System Object: 'WMI Database'.
.
.
.
Directory--> 0 bonniec$Program FilesTivoliTSRMlog [Sent]
FilesTivoliTSRMlogScheduler_000001.log [Sent]
Normal File--> 279 bonniec$Program
FilesTivoliTSRMlogserver_000002.log [Sent]
Normal File--> 5,537 bonniec$Program


FilesTivoliTSRMlogTivoliSRM_000001.log [Sent]
Normal File--> 42 bonniec$Program FilesTivoliTSRMlogTSRMsrv1.out
[Sent]
Normal File--> 54 bonniec$Program FilesTivoliTSRMteccache [Sent]
.
.
.
Total number of objects inspected: 25,379
Total number of objects backed up: 1,933
Total number of objects updated: 1
Total number of objects rebound: 0
Total number of objects deleted: 0
Total number of objects expired: 7
Objects compressed by: 0%

7.3.3 IBM Tivoli Storage Resource Manager database
Depending on the availability you require from the Tivoli Storage Resource Manager Server,
you can choose between online and offline backups of the DB2 database. Offline backups will
require a shutdown of the DB2 database, which implies a shutdown of the Tivoli Storage
Resource Manager application. We explain here how to perform both an online and offline
backup of the Tivoli Storage Resource Manager DB2 database.

Note: Please refer to this documentation for detailed information about DB2 protection and
Tivoli Storage Manager integration:
IBM DB2 Universal Database - Administration Guide: Implementation - Version 7,
SC09-2944
IBM DB2 Universal Database - Command Reference - Version 7, SC09-2951

Offline backup
An offline backup will run only if the database is not currently in use. You must stop the
database or at least close all connections. In our case, we do not have to stop the database
since Tivoli Storage Resource Manager is the application using it. Check this using the DB2
command shown in Example 7-12. We then stopped the Tivoli Storage Resource Manager
Server - this will close all active connections to the Tivoli Storage Resource Manager
database.

Example 7-12 Active connections to IBM Tivoli SRM database
C:PROGRA~1SQLLIBBIN>db2 list applications for database itsrmdb

Auth Id Application Appl. Application Id DB # of
Name Handle Name Agents


-------- -------------- ---------- ------------------------------ -------- -----

TSRMSRV1 java.exe 21 *LOCAL.DB2.030611201922 ITSRMDB 1

C:bkupscripts>net stop "IBM Tivoli SRM Server"
The IBM Tivoli SRM Server service is stopping.
The IBM Tivoli SRM Server service was stopped successfully.

C:bkupscripts>db2 list applications for database itsrmdb
SQL1611W No data was returned by Database System Monitor. SQLSTATE=00000

You can see that after stopping the application, message SQL1611W is returned by db2 list
applications for database itsrmdb, which means that no connections are active on the
database.

The backup script, ITSRMBackupOffline (displayed in Example 7-13) performs the following
operations:
1. Stop Tivoli Storage Resource Manager application.
2. Run backup of ITSRMDB database.
3. Start Tivoli Storage Resource Manager application.

Example 7-13 ITSRMBackupOffline - offline backup script for ITSRMDB database
@ECHO ON
@REM Stop the IBM Tivoli SRM server
@REM ------------------------------
net stop "IBM Tivoli SRM Server"

@ECHO ON
@REM Get Status and check if Stopped
@REM -------------------------------
net start | findstr /i "IBM Tivoli SRM Server"
@if %errorlevel% EQU 0 GOTO BACKUPDB

:NOTSTOPPED
@ECHO ON
@REM IBM Tivoli SRM server not stopped - Backup cannot run
@REM -----------------------------------------------------
@echo "IBM Tivoli SRM Not Stopped !!!"
@echo "Backup process cancelled "
exit 1

:BACKUPDB
@ECHO ON
@REM IBM Tivoli ITSRM server is stopped - Backup can run
@REM -------------------------------------------------
@echo "Backup of ITSRMDB starting ..."
C:PROGRA~1SQLLIBBINdb2cmd.exe /c /w /i db2 backup database ITSRMDB USE TSM
@if %errorlevel% NEQ 0 echo "Backup failed - Please check error messages"


@REM Backup completed - Start IBM Tivoli SRM
@REM ---------------------------------------
:STARTITSRM
net start "IBM Tivoli SRM Server"

@ECHO ON
@REM Get Status and check if Started
@REM -------------------------------
@if %errorlevel% EQU 0 GOTO STARTOK

@REM IBM Tivoli SRM not started
@REM --------------------------
@echo "IBM Tivoli SRM Server Not Started !!!"
exit 1

@REM IBM Tivoli SRM started
@REM ----------------------
:STARTOK
@echo "IBM Tivoli SRM started successfully"

The output of the backup script execution is shown in Example 7-14.

Example 7-14 Offline backup of ITSRMDB output
C:bkupscripts>ITSRMBackupOffline.cmd

C:bkupscripts>net stop "IBM Tivoli SRM Server"

C:bkupscripts>net start | findstr /i "IBM Tivoli SRM Server"
DB2 JDBC Applet Server
DB2 License Server
DB2 Security Server
Server
VNC Server
"Backup of ITSRMDB starting ..."

C:bkupscripts>C:PROGRA~1SQLLIBBINdb2cmd.exe /c /w /i db2 backup database IT
SRMDB USE TSM

Backup successful. The timestamp for this backup image is : 20030611131856

C:bkupscripts>net start "IBM Tivoli SRM Server"
The IBM Tivoli SRM Server service is starting.
The IBM Tivoli SRM Server service was started successfully.

C:bkupscripts>net start | findstr /i "IBM Tivoli SRM Server"
DB2 JDBC Applet Server
DB2 License Server
DB2 Security Server
IBM Tivoli SRM Server
Server
VNC Server
"IBM Tivoli SRM started successfully"


C:bkupscripts>

Online backup
An online backup can run while applications are still accessing the data. DB2 will manage the
enqueue process and will use its recovery log to track all changes made to the database
while the backup is running. Your database must be configured for online backups (see
Example 7-5 on page 377). The database backup procedure, ITSRMBackupOnline, displayed
in Example 7-15, includes:
1. List current connections.
2. Run backup of ITSRMDB database.
3. List current connections.

Example 7-15 ITSRMBackupOnline script
@ECHO ON
@REM List active connections for information
@REM ---------------------------------------
db2cmd.exe /c /w /i db2 list applications for database ITSRMDB | findstr /i SQL1032N
@if %errorlevel% NEQ 0 GOTO BACKUPDB

@REM SQL1032N found - DB is not started
@REM ----------------------------------
@echo "SQL1032N return - DB2 is not active - Backup cancelled !!!"
exit 1

:BACKUPDB
@ECHO ON
@REM DB2 is active - Backup can run
@REM ------------------------------
C:PROGRA~1SQLLIBBINdb2cmd.exe /c /w /i db2 backup database ITSRMDB ONLINE USE TSM

@REM Backup completed - List connections
@REM -----------------------------------
db2cmd.exe /c /w /i db2 list applications for database ITSRMDB

The output of this script execution is shown in Example 7-16.

Example 7-16 Online Backup of ITSRMDB output
C:bkupscripts>ITSRMBackupOnline.cmd

C:bkupscripts>db2cmd.exe /c /w /i db2 list applications for database ITSRMDB
| findstr /i SQL1032N
"Backup of ITSRMDB starting ..."

C:bkupscripts>C:PROGRA~1SQLLIBBINdb2cmd.exe /c /w /i db2 backup database IT
SRMDB ONLINE USE TSM

Backup successful. The timestamp for this backup image is : 20030611132049

C:bkupscripts>db2cmd.exe /c /w /i db2 list applications for database ITSRMDB

Auth Id Application Appl. Application Id DB # of
Name Handle Name Agents


-------- -------------- ---------- ------------------------------ -------- -----

C:bkupscripts>

You can check the status of your backups using the db2adutl command, which is only valid
for backups done using Tivoli Storage Manager.

Example 7-17 db2adutl output
C:PROGRA~1SQLLIBBIN>db2adutl query database ITSRMDB

Query for database ITSRMDB

Retrieving FULL DATABASE BACKUP information.
1 Time: 20030611142057 Oldest log: S0000001.LOG Node: 0 Sessions: 1

Retrieving INCREMENTAL DATABASE BACKUP information.
No INCREMENTAL DATABASE BACKUP images found for ITSRMDB

Retrieving DELTA DATABASE BACKUP information.
No DELTA DATABASE BACKUP images found for ITSRMDB

Retrieving TABLESPACE BACKUP information.
No TABLESPACE BACKUP images found for ITSRMDB

Retrieving INCREMENTAL TABLESPACE BACKUP information.
No INCREMENTAL TABLESPACE BACKUP images found for ITSRMDB

Retrieving DELTA TABLESPACE BACKUP information.
No DELTA TABLESPACE BACKUP images found for ITSRMDB

Retrieving LOAD COPY information.
No LOAD COPY images found for ITSRMDB

Retrieving LOG ARCHIVE information.
No LOG ARCHIVE images found for ITSRMDB

We see our two latest backups with timestamps 20030611142057 and 20030611132049.


7.4 Restore procedures

Tivoli Storage Resource Manager restore procedures
Tivoli Storage Resource Manager Agents
Restore of lost files

Restore of lost files

Tivoli Storage Resource Manager database
Database restore command

ibm.com/redbooks

Figure 7-5 Tivoli Storage Resource Manager restore procedures

We describe now the procedures we have used to recover from:
A loss of major Agent files
A loss of major Manager files
A loss of the Tivoli Storage Resource Manager database

7.4.1 Restore Agent files
In this restore procedure, we have:
Stopped the Agent
Deleted some files including the Agent executable and configuration file
Tried to start the Agent, which failed
Restored all of the deleted files
Successfully started the Agent

You can see in Example 7-18, all the steps executed to destroy and recover the Agent files.

Example 7-18 Agent restore procedure output
linux:/etc/init.d # ps -ef | grep java
root 4367 4350 0 08:11 pts/0 00:10:04 /opt/tivoli/TSRM/java/bin/exe/java -cp
/opt/tivoli/TSRM/agent/lib/TSRMagt.zip:/opt/tivoli/TSRM/agent/lib/Sprinta2000.jar:/opt/tivo
li/TSRM/agent/lib/ibmjcefw.jar:/opt/tivoli/TSRM/agent/lib/TSRMRequest.jar:/opt/tivoli/TSRM/
agent/lib/ibmpkcs.jar:/opt/tivoli/TSRM/agent/lib/ibmjceprovider.jar:/opt/tivoli/TSRM/agent/


lib/US_export_policy.jar:/opt/tivoli/TSRM/agent/lib/local_policy.jar
com.tivoli.itsrm.agent.svp.Agent
.
.

linux:/etc/init.d # ./tsrmagt1 stop
linux:/etc/init.d #
linux:/etc/init.d # ps -ef | grep TSRMagt1
linux:/etc/init.d #
linux:/etc/init.d # cd /opt/tivoli/TSRM
linux:/opt/tivoli/TSRM #
linux:/opt/tivoli/TSRM # rm config/*
linux:/opt/tivoli/TSRM # rm agent/bin/linux_i386/*
linux:/opt/tivoli/TSRM # cd /etc/init.d
linux:/etc/init.d # ./tsrmagt1 start
linux:/etc/init.d # 06-11 08:49:09 GEN0198I: Agent starting
Exception in thread "main"

linux:/etc/init.d # dsmc restore /opt/tivoli/TSRM/ -subdir=yes -replace=yes

Restore function invoked.

Node Name: SUSE82-1
Session established with server BANDA: AIX-RS/6000
Server Version 5, Release 2, Level 0.0
Server date/time: 06/11/03 16:05:10 Last access: 06/11/03 16:03:04

ANS1247I Waiting for files from the server...
Restoring 176 /opt/tivoli/TSRM/agent [Done]
Restoring 80 /opt/tivoli/TSRM/config [Done]
Restoring 432 /opt/tivoli/TSRM/install [Done]
Restoring 160 /opt/tivoli/TSRM/java [Done]
Restoring 72 /opt/tivoli/TSRM/log [Done]
Restoring 48 /opt/tivoli/TSRM/scripts [Done]
Restoring 80 /opt/tivoli/TSRM/agent/bin [Done]
Restoring 112 /opt/tivoli/TSRM/agent/guid [Done]
Restoring 320 /opt/tivoli/TSRM/agent/lib [Done]
Restoring 168 /opt/tivoli/TSRM/agent/bin/linux_i386 [Done]
...
Restoring 1,025 /opt/tivoli/TSRM/log/suse82-1/Tivoli.Default
Scan.0010_scan.00000413.log [Done]
Restoring 199
/opt/tivoli/TSRM/log/suse82-1/Tivoli.Discovery.0004_discovery.00000371.log [Done]
Restoring 1,930 /opt/tivoli/TSRM/log/suse82-1/agent_000001.log [Done]
Restoring 163 /opt/tivoli/TSRM/log/suse82-1/agent_000002.log [Done]
Restoring 1,069
/opt/tivoli/TSRM/log/suse82-1/db2admin.filling_the_DB_with_scan.0011_scan.00000503.log
[Done]

Restore processing finished.


Total number of objects restored: 281

linux:/etc/init.d # ./tsrmagt1 start
linux:/etc/init.d # 06-11 09:05:31 GEN0198I: Agent starting

linux:/etc/init.d # ps -ef | grep java
.
.
root 4389 4050 0 09:11 pts/0 00:00:00 grep java

From the Tivoli Storage Resource Manager: Administrative GUI we checked to ensure that
the Agent had started successfully (IBM Tivoli SRM -> Administrative Services -> Agents),
right-click SUSE82-1 and chose Check. Figure 7-5 shows that the Agent on SUSE82-1 did
start.

Figure 7-6 Agent is connected to the server after restore


7.4.2 IBM Tivoli Storage Resource Manager Server files
Since our Tivoli Storage Resource Manager Server system also has an Agent running on it,
and the Server and Agent files are stored in the same directory structure, in this restore test
we will be recovering both the Server and Agent.

The restore procedure has the following steps:
1. Stop the Tivoli Storage Resource Manager Server and Agent.
2. Delete Tivoli Storage Resource Manager directories.
3. Try to start the Server - fails.
4. Restore all deleted directories.
5. Successfully start the Tivoli Storage Resource Manager Server and Agent.

Example 7-19 shows the Server and Agent being stopped, the files being deleted, and the
Server and Agent failing to start.

Example 7-19 Stop server and Agent and delete commands
C:Program FilesTivoliTSRM>net stop "IBM Tivoli SRM Server"

C:Program FilesTivoliTSRM>del *.* /s /q >

Deleted file - C:Program FilesTivoliTSRMautorun.inf
Deleted file - C:Program FilesTivoliTSRMibmchanges.txt
Deleted file - C:Program FilesTivoliTSRMibmchanges.zip
Deleted file - C:Program FilesTivoliTSRMINSTANCE1.DAT
Deleted file - C:Program FilesTivoliTSRMITSRM_1.2.2.07_windows.zip
Deleted file - C:Program FilesTivoliTSRMlicense_key.txt
Deleted file - C:Program FilesTivoliTSRMlicense_srm.txt
Deleted file - C:Program FilesTivoliTSRMSERVER.ID
Deleted file - C:Program FilesTivoliTSRMsetup.exe
Deleted file - C:Program FilesTivoliTSRMUPTIME.bonnie
Deleted file - C:Program FilesTivoliTSRMversion.txt
Deleted file - C:Program FilesTivoliTSRMagentbinWIN32_I386TSRMagt.dll
...
C:Program FilesTivoliTSRM>cd ..

C:Program FilesTivoli>rmdir tsrm /s
tsrm, Are you sure (Y/N)? y

C:Program FilesTivoli>net start "IBM Tivoli SRM Server"
System error 2 has occurred.

The system cannot find the file specified.

C:Program FilesTivoli>net start "IBM Tivoli SRM Agent"
System error 2 has occurred.

The system cannot find the file specified.

We launched the Tivoli Storage Manager Backup/Archive client interface and started the
restore of the deleted directories, shown in Figure 7-7.


Figure 7-7 IBM Tivoli Storage Manager restore interface

Figure 7-8 shows the successful restore of the Tivoli Storage Resource Manager files.

Figure 7-8 Restore completed successfully

We were then able to successfully restart the Server and Agent as shown in Example 7-20.


Example 7-20 Server and Agent started successfully after restore
C:Program FilesTivoli>net start "IBM Tivoli SRM Server"

C:Program FilesTivoli>net start "IBM Tivoli SRM Agent"
The IBM Tivoli SRM Agent service is starting.
The IBM Tivoli SRM Agent service was started successfully.

Figure 7-9 shows the Tivoli Storage Manager Administrative GUI, where all of the Agents
have successfully reconnected to the Server after the restore.

Figure 7-9 Agents successfully reconnected after restore

7.4.3 Tivoli Storage Resource Manager database
We will now test restoring the Tivoli Storage Resource Manager DB2 repository. In this
restore procedure, we:
Stop the Tivoli Storage Resource Manager Server
Delete all rows in the ITSRMDB tables
Restore an old ITSRMDB database backup
Reapply the log up till the delete row commands
Successfully start the server

Figure 7-21 shows stopping the Server and the SQL DELETE commands used to delete the
contents of the ITSRMDB tables.

Example 7-21 ITSRMDB corruption through DELETE commands
C:PROGRA~1SQLLIBBIN>net stop "IBM Tivoli SRM Server"



C:PROGRA~1SQLLIBBIN>cd C:bkupscripts

C:bkupscripts>db2 connect to ITSRMDB user db2admin
Enter current password for db2admin:

Database Connection Information

Database server = DB2/NT 7.2.6
SQL authorization ID = DB2ADMIN
Local database alias = ITSRMDB

C:bkupscripts>db2 "select 'DROP TABLE TIVOLISRM.'||tabname||';' from syscat.tab
les where tabschema = 'TIVOLISRM'" > drop_SRM.sql

C:bkupscripts>db2 -tf drop_SRM.sql
. .
DB20000I The SQL command completed successfully.
.
.

We then restored the database as shown in Example 7-22. We selected the most recent
backup image to restore.

Example 7-22 ITSRMDB restore procedure
C:PROGRA~1SQLLIBbin>db2adutl query db ITSRMDB



Retrieving INCREMENTAL DATABASE BACKUP information.
No INCREMENTAL DATABASE BACKUP images found for ITSRMDB

Retrieving DELTA DATABASE BACKUP information.
No DELTA DATABASE BACKUP images found for ITSRMDB

Retrieving TABLESPACE BACKUP information.
No TABLESPACE BACKUP images found for ITSRMDB

Retrieving INCREMENTAL TABLESPACE BACKUP information.
No INCREMENTAL TABLESPACE BACKUP images found for ITSRMDB

Retrieving DELTA TABLESPACE BACKUP information.
No DELTA TABLESPACE BACKUP images found for ITSRMDB


Retrieving LOAD COPY information.
No LOAD COPY images found for ITSRMDB

Retrieving LOG ARCHIVE information.
No LOG ARCHIVE images found for ITSRMDB

C:bkupscripts>db2 restore database ITSRMDB use tsm taken at 20030612104416

SQL2539W Warning! Restoring to an existing database that is the same as the ba
ckup image database. The database files will be deleted.
Do you want to continue ? (y/n) y
DB20000I The RESTORE DATABASE command completed successfully.

C:PROGRA~1SQLLIBbin>db2 rollforward db ITSRMDB to 2003-06-12-20.02.00.000000 and STOP

Rollforward Status

Input database alias = ITSRMDB
Number of nodes have returned status = 1

Node number = 0
Rollforward status = not pending
Next log file to be read =
Log files processed = S0000008.LOG - S0000011.LOG
Last committed transaction = 2003-06-12-18.03.53.000000

DB20000I The ROLLFORWARD command completed successfully.

C:PROGRA~1SQLLIBbin>net start "IBM Tivoli SRM Server"

In the ROLLFORWARD command, we specified to which point we want to restore the database.
2003-06-12-18.03.53.000000 is expressed in Coordinated Universal Time (UTC) and is the time
just before we started our SQL DROP commands.

Figure 7-10 shows that Tivoli Storage Resource Manager restarted after the database
restore.


Figure 7-10 Server running again after database restore


7.5 Disaster Recovery procedures

Tivoli Storage Resource Manager Disaster Recovery
Tivoli Storage Resource Manager server
Install basic Windows 2000 server
Install Windows Service Pack
Install Tivoli Storage Manager client
Restore of files
Restore of System Objects
Restore of ITSRMDB database
Start of application

ibm.com/redbooks

Figure 7-11 Tivoli Storage Resource Manager Server Disaster Recovery procedures

We describe now the procedures we have used to recover from a complete loss of our Tivoli

7.5.1 Windows 2000 restore
To restore our Tivoli Storage Resource Manager Server, we followed the procedure described
in Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment, SG24-6141.
We have:
1. Installed Windows 2000 on the server using BONNIE as hostname
2. Installed Windows 2000 Service Pack 3
3. Installed the Tivoli Storage Manager Backup/Archive client and configured it to use our
Tivoli Storage Manager Server located on BANDA. Example 7-23 shows the minimal
client options file required for this.

Example 7-23 Minimal dsm.opt file
tcpserveraddress banda.almaden.ibm.com
nodename bonnie

4. Restored all the files on the boot partition (disk C:) as displayed in Figure 7-13.


Figure 7-12 Full system restore

Note that after the restore of the boot partition you will be prompted that a reboot of the
system is required. Do not reboot at this time. You need to wait until after the System
Objects have been restored.

Figure 7-13 Full system restore result


5. Restore the System Objects.

Figure 7-14 System Objects restore

The restore of System Objects finished successfully as you can see in Figure 7-15.

Figure 7-15 System Objects restore results

6. Reboot the system.


At this stage, we are in the situation where all our software and configuration files have been
restored. We must now restore the ITSRMDB database to its latest available status.

7.5.2 ITSRMDB database restore
We used the procedure described in 7.3.3, “IBM Tivoli Storage Resource Manager database”
on page 382 to restore the ITSRMDB database. We were able to do a rollforward restore
since the DB2 logs were backed up to Tivoli Storage Manager before the crash. They were
restored during step 4 on page 396. Example 7-24 shows the output of the restore process.

Example 7-24 Rollforward restore of database
C:Program FilesSQLLIB>db2adutl query db ITSRMDB


.
.

C:Program FilesSQLLIB>db2 restore db ITSRMDB use TSM taken at 20030612133931
SQL2539W Warning! Restoring to an existing database that is the same as the ba
ckup image database. The database files will be deleted.
Do you want to continue ? (y/n) y

C:Program FilesSQLLIB>db2 rollforward db ITSRMDB to end of logs

Rollforward Status


Node number = 0
Rollforward status = DB working
Next log file to be read = S0000001.LOG
Log files processed = -


C:Program FilesSQLLIB>db2 rollforward db ITSRMDB stop

Rollforward Status


Node number = 0
Rollforward status = not pending
Next log file to be read =
Log files processed = -



C:PROGRA~1SQLLIBbin>net start “IBM Tivoli SRM Server”

The Tivoli Storage Resource Manager Server is now successfully restarted as shown in
Figure 7-16.

Figure 7-16 IBM Tivoli SRM interface after DR restore

Note that if your DB2 files and directories were never backed up using the standard
Backup/Archive client, your DB2 local and system directory will not be synchronized. You will
have to uncatalog the ITSRMDB database, and recreate the database during the restore as
briefly shown in Example 7-25.

Example 7-25 Database restore into

to C into ITSRMDB
SQL1005N The database alias "ITSRMDB" already exists in either the local
database directory or system database directory. SQLSTATE=00000

C:Program FilesSQLLIB>db2 uncatalog db ITSRMDB
DB20000I The UNCATALOG DATABASE command completed successfully.
DB21056W Directory changes may not be effective until the directory cache is
refreshed.


C:Program FilesSQLLIB>db2stop

C:Program FilesSQLLIB>db2start

SQL1036C An I/O error occurred while accessing the database. SQLSTATE=58030

to C into ITSRMDB

7.6 Database maintenance
As with every database, basic maintenance should be applied to the Tivoli Storage Resource
Manager repository to avoid space and performance problems.

Tivoli Storage Resource Manager: database
maintenance
Database should be checked for performance using
runstats
reorgchk
reorg table
db2rbind

ibm.com/redbooks

Figure 7-17 DB2 Database maintenance

Basic DB2 maintenance should include:
runstats to update tables statistics
reorgchk to check need for tables reorganization
reorg to rebuild unordered tables and indexes
db2rbind to rebuild packages


The runstats command is not mandatory since the statistics can be updated by the reorgchk
command. Also, you need to run a runstats command for each table while reorgchk
executes over all tables.

Example 7-26 shows the output of the reorgchk command on our ITSRMDB database.

Example 7-26 Output of reorgchk
db2 => connect to itsrmdb

Database Connection Information

Database server = DB2/NT 7.2.6
SQL authorization ID = ADMINIST...
Local database alias = ITSRMDB

db2 => reorgchk on table all

Doing RUNSTATS ....

Table statistics:

F1: 100 * OVERFLOW / CARD < 5
F2: 100 * TSIZE / ((FPAGES-1) * (TABLEPAGESIZE-76)) > 70
F3: 100 * NPAGES / FPAGES > 80

CREATOR NAME CARD OV NP FP TSIZE F1 F2 F3 REORG

--------------------------------------------------------------------------------

SYSIBM SYSATTRIBUTES - - - - - - - - ---
.
.
.
TIVOLISRM T_STAT_FILE 137397 0 4836 7808 18960786 0 60 61 -**
TIVOLISRM T_STAT_FS_HIST 944 0 15 15 51920 0 92 100 ---
TIVOLISRM T_STAT_GROUP 89 0 6 9 12371 0 38 66 -**
TIVOLISRM T_STAT_GROUP_HIST 2911 0 37 37 142639 0 98 100 ---
TIVOLISRM T_STAT_LARGE_DIR 650 0 38 64 134550 0 53 59 -**
TIVOLISRM T_STAT_PING_HIST 194 0 4 4 12028 0 99 100 ---
TIVOLISRM T_STAT_SCAN_SPOOR 2714 0 21 21 70564 0 87 100 ---
TIVOLISRM T_STAT_SEGMENT 91 0 4 22 10738 0 12 18 -**
TIVOLISRM T_STAT_SIZE_DIST 49 0 3 3 5194 0 64 100 -*-
TIVOLISRM T_STAT_SPACE_HIST 1462 0 21 21 65790 0 81 100 ---
TIVOLISRM T_STAT_SUMMARY 264 0 3 4 8712 0 72 75 --*
TIVOLISRM T_STAT_TABLE 162 0 7 32 25758 0 20 21 -**
TIVOLISRM T_STAT_TIME_DIST 124 0 7 7 18228 0 75 100 ---
TIVOLISRM T_STAT_TIME_HIST 2122 0 78 78 301324 0 97 100 ---
TIVOLISRM T_STAT_TOTALS 31 0 2 4 4247 0 35 50 -**
TIVOLISRM T_STAT_USER 291 0 13 13 43650 0 90 100 ---
.
.
.
--------------------------------------------------------------------------------

Index statistics:

F4: CLUSTERRATIO or normalized CLUSTERFACTOR > 80
F5: 100 * (KEYS * (ISIZE+8) + (CARD-KEYS) * 4) / (NLEAF * INDEXPAGESIZE) > 50
F6: (100-PCTFREE) * (INDEXPAGESIZE-96) / (ISIZE+12) ** (NLEVELS-2) * (INDEXPAGES
IZE-96) / (KEYS * (ISIZE+8) + (CARD-KEYS) * 4) < 100


CREATOR NAME CARD LEAF LVLS ISIZE KEYS F4 F5 F6 REORG
--------------------------------------------------------------------------------
.
.
.
Table: TIVOLISRM.T_STAT_FILE
TIVOLISRMT_STAT_FILE_IX 137397 313 3 9 161 99 43 124 -**
Table: TIVOLISRM.T_STAT_FS_HIST
TIVOLISRMT_STAT_FS_HIST_IX 944 5 2 5 343 31 33 52 **-
Table: TIVOLISRM.T_STAT_GROUP
TIVOLISRMT_STAT_GROUP_IX 89 2 2 12 89 100 21 202 -**
Table: TIVOLISRM.T_STAT_GROUP_HIST
TIVOLISRMT_STAT_GRP_HIST_IX 2911 16 2 13 1636 37 60 9 *--
Table: TIVOLISRM.T_STAT_LARGE_DIR
TIVOLISRMT_STAT_LDIR_IX 650 1 1 8 49 98 - - ---
Table: TIVOLISRM.T_STAT_SCAN_SPOOR
TIVOLISRMT_SCAN_SPOOR_IX1 2714 8 2 8 343 89 45 24 -*-
Table: TIVOLISRM.T_STAT_SEGMENT
TIVOLISRMT_STAT_SEG_IX 91 1 1 9 7 96 - - ---
Table: TIVOLISRM.T_STAT_SPACE_HIST
TIVOLISRMT_STAT_SP_HIST_IX 1462 6 2 9 484 25 49 29 **-
.
.
.
--------------------------------------------------------------------------------

CLUSTERRATIO or normalized CLUSTERFACTOR (F4) will indicate REORG is necessary
for indexes that are not in the same sequence as the base table. When multiple
indexes are defined on a table, one or more indexes may be flagged as needing
REORG. Specify the most important index for REORG sequencing.

The reorgchk command calculates three formulas (F1, F2, F3) for the tables and three
formulas (F4, F5, F6) for the indexes to determine if the table or index must be reorganized.
Each hyphen displayed in the REORG column indicates that the calculated results were
within the set bounds of the corresponding formula, and each asterisk indicates that the
calculated result exceeded the set bounds of its corresponding formula.

Table reorganization is suggested when the results of the calculations exceed the bounds set
by the formula.

Attention: Refer to the appropriate administration guide for your DB2 platform.

If a reorganization is recommended for a table or an index, this can only be done when no
activity is running against the database. This means that IBM Tivoli SAN Manager must be
stopped in order to reorganize the tables.

Example 7-27 shows an output of the reorg for the ITSRMDB DB2
TIVOLISRM.T_STAT_FILE table followed by a reorgchk on this table.

Example 7-27 REORGANIZE output
db2 => reorg table TIVOLISRM.T_STAT_FILE
DB20000I The REORG TABLE command completed successfully.
db2 => reorgchk on table TIVOLISRM.T_STAT_FILE

Doing RUNSTATS ....


Table statistics:

F1: 100 * OVERFLOW / CARD < 5
F2: 100 * TSIZE / ((FPAGES-1) * (TABLEPAGESIZE-76)) > 70
F3: 100 * NPAGES / FPAGES > 80

CREATOR NAME CARD OV NP FP TSIZE F1 F2 F3 REORG

--------------------------------------------------------------------------------

TIVOLISRM T_STAT_FILE 137397 0 4788 4788 18960786 0 98 100 ---

--------------------------------------------------------------------------------

Index statistics:

F4: CLUSTERRATIO or normalized CLUSTERFACTOR > 80
F5: 100 * (KEYS * (ISIZE+8) + (CARD-KEYS) * 4) / (NLEAF * INDEXPAGESIZE) > 50
F6: (100-PCTFREE) * (INDEXPAGESIZE-96) / (ISIZE+12) ** (NLEVELS-2) * (INDEXPAGES
IZE-96) / (KEYS * (ISIZE+8) + (CARD-KEYS) * 4) < 100

CREATOR NAME CARD LEAF LVLS ISIZE KEYS F4 F5 F6 REORG
--------------------------------------------------------------------------------

Table: TIVOLISRM.T_STAT_FILE
TIVOLISRMT_STAT_FILE_IX 137397 175 2 9 161 99 76 0 ---
--------------------------------------------------------------------------------

CLUSTERRATIO or normalized CLUSTERFACTOR (F4) will indicate REORG is necessary
for indexes that are not in the same sequence as the base table. When multiple
indexes are defined on a table, one or more indexes may be flagged as needing
REORG. Specify the most important index for REORG sequencing.

Important: Note that it is preferable to reorganize a table according its most used index.
Refer to the appropriate DB2 administration guide for tables and indices reorganization.

Finally, rebuild the packages (if any) that are associated with ITSRMDB using the db2rbind
command. No log file was created from our db2rbind command, which indicates that there
are currently no packages defined for our ITSRMDB database.

Example 7-28 DB2 rebind
C:PROGRA~1SQLLIBBIN>db2rbind ITSRMDB -l c:tempITSRMDB_RBIND.txt all

Rebind done successfully for database 'ITSRMDB'.

7.7 IBM Tivoli Storage Resource Manager with SQL-Server
All of the examples so far have shown DB2 as the database being used. Here we show some
examples using Microsoft SQL-Server instead. The database name is TivoliSRM.

We installed SQL Server 2000 and a new Tivoli Storage Resource Manager instance on
server GALLIUM. From an installation point of view, the process was very similar to when
DB2 was used. Other than a local Agent, this new server had no Agents, and no significant
amount of data was collected so the database was extremely small.


We used the IBM Tivoli Storage Manager for Databases product to perform the backups for
the database. Since even in a production implementation of Tivoli Storage Resource Manager
the database will be reasonably small, we came to the conclusion that it would likely not be
necessary to use the incremental backup capability of Tivoli Storage Manager for Databases,
so all of our examples are using full backups and restores.

Figure 7-18 displays using the Tivoli Storage Manager for Database GUI to start the backup,
and Figure 7-19 shows that the backup completed successfully.

Figure 7-18 SQL-Server database backup start using the GUI

Figure 7-19 SQL-Server database backup end using the GUI

In Example 7-29 we show the command line interface for Tivoli Storage Manager for
Databases being used to backup the database.


Example 7-29 SQL Server database backup using the command line
C:Program FilesTivoliTSMTDPSql>tdpsqlc backup TivoliSRM

Tivoli Storage Manager
Tivoli Data Protection for Microsoft SQL Server
Version 2, Release 2, Level 1.0
(C) Copyright IBM Corporation 1997, 2002. All rights reserved.

Starting SQL database backup...

Beginning full backup for database TivoliSRM, 1 of 1.
Full: 0 Read: 2445072 Written: 2445072 Rate: 1,582.35 Kb/Sec
Backup of TivoliSRM completed successfully.

Total SQL backups selected: 1
Total SQL backups attempted: 1
Total SQL backups completed: 1
Total SQL backups excluded: 0
Total SQL backups inactivated: 0

Throughput rate: 1,581.30 Kb/Sec
Total bytes transferred: 2,445,072
Elapsed processing time: 1.51 Secs

Figure 7-20 shows a restore of the database being started using the GUI, and Figure 7-21
shows the restore complete.

Figure 7-20 SQL Server database restore started using the GUI


Figure 7-21 SQL Server database restore finished using the GUI

And finally, Example 7-30 shows the restore being run using the command line interface.

Example 7-30 SQL Server database restore using the command line
C:Program FilesTivoliTSMTDPSql>tdpsqlc restore TivoliSRM /REPLACE

Tivoli Storage Manager
Tivoli Data Protection for Microsoft SQL Server
Version 2, Release 2, Level 1.0
(C) Copyright IBM Corporation 1997, 2002. All rights reserved.

Starting Sql database restore...

Querying Tivoli Storage Manager server for a list of database backups, please wait...

Beginning full restore of backup object TivoliSRM, 1 of 1, to database TivoliSRM
Full: 0 Read: 2443776 Written: 2443776 Rate: 1,190.27 Kb/Sec
Restore of TivoliSRM completed successfully.

Total database backups inspected: 1
Total database backups requested for restore: 1
Total database backups restored: 1
Total database skipped: 0

Throughput rate: 1,189.68 Kb/Sec
Total bytes transferred: 2,443,776
Elapsed processing time: 2.01 Secs

Both the backups and restores were quite straightforward. No special setup was required for
either Tivoli Storage Manager for Databases or Tivoli Storage Resource Manager. More
information on using Tivoli Storage Manager for Databases is available in the redbook Using
Tivoli Data Protection for Microsoft SQL Server, SG24-6148.

One small issue that we came across is that we received an error when performing the
restore when we had the SQL-Server Enterprise Console running. The error was reporting
that the restore process was unable to open the database in exclusive mode. It would appear


that this kept a connection option with the database. We shut down the Enterprise Console
and the restore completed successfully.

7.7.1 Using Oracle for the IBM Tivoli Storage Resource Manager database
We have not tested backing up and restoring an Oracle database used with Tivoli Storage
Resource Manager, however, the same principles apply as already shown for DB2 and MS
SQL-Server. If you have a Tivoli Storage Manager Server, you can use the extra product IBM
Tivoli Storage Manager for Databases to backup and restore Oracle. More information on
backing up Oracle is available in the redbook Backing Up Oracle Using Tivoli Storage
Management, SG24-6249.


Part 5

Part 5 Tivoli Systems
Management
integration
This section discusses how to integrate IBM Tivoli Storage Resource Manager with other
Tivoli Systems Management products.


8

Chapter 8. Integration with Tivoli Enterprise
Console
In this chapter, we show how you can enhance an IBM Tivoli Storage Resource Manager
installation using IBM Tivoli Enterprise Console (TEC). We assume a basic understanding of
TEC technology and the examples are based on a standard pre-existing TEC installation. To
learn more about TEC installation and procedures, see the Redbook Early Experiences with
Tivoli Enterprise Console, SG24-6015.

This chapter covers the following topics:
Introduction to Tivoli Enterprise Console (TEC)
Configuring Rule Base
Event format
Configuring TEC Event Console
Configuring IBM Tivoli Storage Resource Manager to forward events


8.1 Introduction to Tivoli Enterprise Console
The IBM Tivoli Enterprise Console (TEC) is a tool for receiving and processing formatted
events. It uses a database to store the actual events. This database is divided into two
separate tables: one to store the reception log and one to store the processed and probably
reformatted events. TEC depends on the Tivoli Enterprise Framework.

There are five processes which make up a TEC server (see Figure 8-1):
1. tec_reception - Receives events, places them in a reception buffer, and writes them into
the database using a Framework RDBMS Interface Module (RIM). After successfully
placing the event into the reception log in the database, the status of the event is WAITING.
2. tec_rule - When an event becomes WAITING, this will cause the tec_rule process to pull in
the event and place it into its Event Cache. The tec_rule process is configured using a
so-called Rule Base. This can be programmed using a Prolog based language. These
Prolog files are compiled and loaded into the tec_rule process. Based on the defined
rules, the events are treated accordingly. They can be reformatted, matched, related,
time-triggered, and actions can be executed.
3. tec_dispatch - When the tec_rule process finishes processing an event, it hands it over to
the tec_dispatch process. This process stores the events in to the database event
repository table using RIM. It then informs the tec_server process about successfully
processing the event, and if there are any tasks or actions to be executed, it informs the
tec_task process to do it.
4. tec_server - This is the master process of the TEC server. It monitors all the other
processes and stops and starts these. Additionally, it receives a PROCESSED signal from the
tec_dispatch and informs the tec_reception process to change the reception log of an
event to PROCESSED. This is stored in the database accordingly.
5. tec_task - This process executes any tasks or actions requested by the rule engine, and
optionally gives a return code back to it.


Master (tec_server) tec_task
EV
Communication
E V2
Server N R10
T

tec_reception tec_rule tec_dispatch

Reception Event
Buffer Cache

Status = PROCESSED RIM

tec_t_evt_rec_log tec_t_evt_rep
RDBMS

Figure 8-1 TEC architecture

A Rule base is divided into event class definitions, which define the attributes of an event; and
rules, which define what should be done with an event.

IBM Tivoli Storage Resource Manager ships only a class definition file (so called baroc file)
but no rule file.

Events can be received either through Tivoli Enterprise Framework mechanisms (which
requires some software to be installed on each event sender) or through a socket connection
(which only requires that events are sent according to TEC formats). IBM Tivoli Storage
Resource Manager sends its events through a socket connection directly to the TEC server.

In order to view the events and assign them to administrators to be treated, there is a Java
based program called the TEC Console. This connects to the event repository using
Framework mechanisms (RIM) and a helper process called tec_ui_server. It can be
configured to show different views for different administrators. Events can be modified
graphically.

8.2 Lab environment
The setup in our lab environment is shown in Figure 8-2.

Chapter 8. Integration with Tivoli Enterprise Console 413

Component placement

Tivoli Managed Region Server (TMR) Tivoli Enterprise Data Warehouse

DB2
Tivoli Enterprise Console
Tivoli Configuration Manager
Tivoli Monitoring

Ethernet
Tivoli Desktop
Tivoli Enterprise Console Console

Tivoli SAN Manager Agent Tivoli SAN Manager Agent
Tivoli SAN Manager Agent Win2k
Win2k AIX
Tivoli Light Client Tivoli Light Client Tivoli Light Client
Framework (LCF) Framework (LCF) Framework (LCF)

ibm.com/redbooks

Figure 8-2 Tivoli Lab environment

The machines used in the setup are:
Tonga
– Windows 2000 SP3
– Tivoli Management Framework 4.1
– Tivoli Enterprise Console 3.8 FP1
– Tivoli Configuration Manager 4.2
– Tivoli Monitoring 5.1.1 FP3
Palau
– Windows 200 SP3
– Tivoli Enterprise Data Warehouse 1.1 FP2

All the other machines in the lab are running the Tivoli Light Client Framework (LCF) code,
which is the basis for all Tivoli Management activities.

8.3 Configuring the Rule Base
In order to receive events from IBM Tivoli Storage Resource Manager in a TEC server, the
event class definitions which IBM Tivoli Storage Resource Manager uses must be imported to
the TEC server. If you do not import them, events will not show up on your TEC console and
parsing errors will appear in the TEC reception log. You can determine if your events are
received by the TEC server (but the definitions are not there) by issuing the wtdumprl
command on your TEC server. If you see any parsing errors (Example 8-1) on IBM Tivoli
Storage Resource Manager events, then you have not imported the class definitions.


Example 8-1 Output of wtdumprl when baroc has not been imported
1~3467~1~1054831782(Jun 05 09:49:42 2003)
### EVENT ###
JobFailure;adapter_host=wisla;messageID=ALR1339W;scheduleRun='9';scheduleName='T
ivoli.Default Probe';alertType='Scheduled Job Failed';scheduleType='Probe';msg='
A scheduled job has failed.';END

### END EVENT ###
PARSING FAILED

To import the event class definitions, open the Tivoli Desktop and double click the Event
Server icon. In the window (Figure 8-3) you see the defined rule bases, with the active one
highlighted by an arrow.

Figure 8-3 Active Rule Base

Choose the active rule base and right-click it. Select Import (Figure 8-4).

Figure 8-4 Import Rule Base

Select the check-box Import Class Definitions and enter the fully qualified path to the
definitions file. This file is on the IBM Tivoli Storage Resource Manager CD and is called
tivoliSRM.baroc. (Our example uses a copy of this file on disk.)


The Position to insert depends on how many events you expect to receive from IBM Tivoli
Storage Resource Manager, and on the hierarchical dependencies inside the class structure.
Since the IBM Tivoli Storage Resource Manager classes depend only on the root EVENT, you
can put it right after that event class. However, since classes are matched from the top to
bottom, put the busiest event classes higher in the hierarchy rather than the less busy
classes. For example, we put it at the very bottom, because we do not expect very many
events (Figure 8-5).

Figure 8-5 Import Class Definitions

After the class definitions are imported, we must compile the rule base to incorporate the
changes (as shown in Figure 8-6). To compile, right-click the active rule base icon and select
Compile.


Figure 8-6 Compile Rule Base

Carefully check the output for any compilation errors. If there were none, load the rule base
(Figure 8-7). You must recycle the event server whenever you make any changes to the class
definitions. If you only changed rules, then recycling the event server is not necessary.

Figure 8-7 Load Rule Base

Stop and start the Event Server by right-clicking the icon on your Tivoli Desktop (Figure 8-8).


Figure 8-8 Restart TEC Server

8.4 Configuring TEC Event Console
The TEC Event Console allows you to view the events the TEC server has received and
processed. This is an installable Java GUI to install on desktop machines. You must be
assigned as an operator to an Event Console to view events. A Console can be divided into
multiple Event Groups, which sort the events in meaningful groups. Each Event Group
contains one or more Event Filters to separate events. This example assumes you are
working with a Tivoli administrative user ID, which is authorized to do TEC configurations. In
the Console in Figure 8-9, there is an Event Group named All which shows all the events.


Figure 8-9 TEC Console

To make the changes click the Windows menu and then Configuration (Figure 8-10).

Figure 8-10 TEC Console Configuration

In the Configuration dialog there are three folders:
Event Groups
Consoles
Operators

First we have to create an Event Group to specify filters to sort out the IBM Tivoli Storage
Resource Manager events. Right-click Event Groups and select Create Event Group
(Figure 8-11).


Figure 8-11 Create Event Group

Name the Event Group (for example, ITSRM) and right-click it. Select Create Filter
(Figure 8-12).

Figure 8-12 Create Filter in Event Group

When the dialog opens up, enter a description to the filter and select Add Constraint
(Figure 8-13).


Figure 8-13 Event Group Filter

Choose Class as an Attribute and Operator In, then select SRMAlert in the Value window
(Figure 8-14).

Figure 8-14 Add Constraint

This will add a Constraint to our filter ITSRM. If you add multiple Constraints, they behave as
a boolean AND. If you add more filters to an Event Group they behave as a boolean OR. You
can test if your filter matches any events by clicking the Test SQL button on Figure 8-13. If
there are no events in the TEC repository, then you will get zero matching events. You can
view the Constraint in plain SQL by clicking the little arrow above the Help button on
Figure 8-13. It will display similar to Figure 8-15.


Figure 8-15 Event Group Filter

After creating the Event Group, we must assign it to a Console. We assume that you already
have a Console defined, so right-click it and select Assign Event Group. The menu in
Figure 8-16 appears.

Figure 8-16 Assign Event Group

Select the appropriate roles and click OK. You will see output similar to Figure 8-17.


Figure 8-17 Assigned Event Groups

Your Console should now have the ITSRM Event Group assigned to it (Figure 8-18).

Figure 8-18 Configured Console

After configuring the Event Console, you can look at the results by changing the view in the
Windows menu and choose Summary Chart View. The window that appears is the actual
event viewer, which shows all configured event groups (Figure 8-19).


Figure 8-19 TEC Console main screen

If you click the bar of a particular event group, the event viewer for this event group opens
(Figure 8-20).

In the upper window space, you can see the events which you can modify and are assigned
for you to solve. You can acknowledge, close, and run tasks, or view the details of the
selected event.

Figure 8-20 TEC console

If you select an event and click the Details button, the window in Figure 8-21 opens. It
describes in plain text the most important details of the selected event.


Figure 8-21 General tab of event

You get a complete listing of all event attributes by selecting the Attribute List tab
(Figure 8-22). There you can get additional information on where the event originated, when it
has occurred, when it has been received by the TEC server and other fields.


Figure 8-22 Event attribute list

8.5 Event format
The event classes IBM Tivoli Storage Resource Manager uses and the format of these are
described in the following paragraphs.

The possible event attributes (slots) IBM Tivoli Storage Resource Manager uses are the
following:
adaptor_host: Name of the Tivoli SRM server generating the event
hostname: Name of the alerting computer
origin: IP address of the alerting computer
source: The name of the application generating the event i.e. IBM Tivoli Storage Resource
Manager
msg: Text description which gives the summary of the event.
messageID: ID that is assigned to the associated message by the TSRM product.


Severity: severity level of the event. Possible values in order of decreasing severity are
FATAL, CRITICAL, MINOR, WARNING, HARMLESS, and UNKNOWN.
alertName: name of the triggered alert.
alertType: type of the triggered alert.
resourceName: name of the alerting resource.
resourceType: type of the alerting resource.
threshold: The alert’s triggering threshold.
currentValue: alerting resource’s current value.
previousValue: alerting resource’s previous value.
freespace: free space of the alerting resource.
violatorName: name of the over quota user or OS/Group.
violatorType: type of the storage consumer – user or OS/Group.
filerName: filer triggering the alert.
currentCapacity: current capacity of the alerting resource.
targetCapacity: target capacity of the alerting resource.
scheduleName: name of the failed job schedule.
scheduleType: type of schedule that failed.
scheduleRun: schedule run number that failed.
rdbmsName: name of the alerting RDBMS.
rdbmsType: type of RDBMS that triggered the alert.
databaseName: name of the alerting database.
segmentName: creator and name of the alerting Oracle segment.
segmentType: type of Oracle segment that triggered the alert.

The event classes IBM Tivoli Storage Resource Manager uses are:
Ram_Changed: the amount of RAM on an Agent has changed
VirtualMemory_Changed: the amount of virtual memory on an Agent has changed.
Disk_New: a new disk has been discovered on an Agent
Disk_Missing: a disk has been removed from an Agent
Disk_Failure: a managed disk has predicted that a disk failure is imminent.
Disk_Defect: a new defect has been detected on a managed disk.
Filesystem_New: a new filesystem has been discovered on a managed computer.
Filesystem _Missing: a filesystem has been removed or unmounted from an Agent
Filesystem_Reconfigured: the physical space definition of an Agent filesystem has been
reconfigured.
Filesystem _FreeSpace_Low: a managed filesystem is low on free space.
Filesystem _Inode_Low: a managed UNIX filesystem is low on free inodes.
Filesystem_Constraint_Violated: a Constraint on a managed filesystem has been violated.
Filesystem_Auto_Extend: a managed filesystem will be extended.
Filesystem_Stopped_Auto_Extend: extension of a managed filesystem is prevented.
Directory_Missing: a monitored directory has been removed from a managed computer.
Directory_Quota_Exceeded: a user or directory storage quota has been exceeded.
Computer_Offline: an Agent is offline.
Computer_Discovered: a new unmanaged computer has been discovered.
NasComputer_Discovered: a new filer has been discovered.
Filer_Missing: a filer is no longer accessible through the specified resource.
DiskArray_Missing: a disk array is no longer visible to a managed computer.
DiskArray_New: a new Disk Array has been discovered.
Job_Failure: a scheduled job has failed

8.6 Tivoli Storage Resource Manager event forwarding
After we have prepared the Tivoli Event Console Server (TEC) to receive events from IBM
Tivoli Storage Resource Manager, we must enable IBM Tivoli Storage Resource Manager


itself to forward events to TEC. Open the IBM Tivoli Storage Resource Manager Desktop and
navigate to Administrative Services -> Configuration -> Alert Disposition and enter the
hostname of your TEC server and the port (Windows 5529, UNIX 0) in the TEC section on the
right (Figure 8-23).

Figure 8-23 Setting the TEC server properties

Save your changes by clicking on the Save button under the top menu.

This configuration only defines where TEC events should be sent to - we have not yet actually
enabled any events. To enable events for a specific topic in IBM Tivoli Storage Resource
Manager, you have to select the TEC check box on every Alert properties tab that you want ti
activate. For example, if you want a TEC event sent when the Default Scan fails, navigate to
its properties page and enable it (Figure 8-24).


Figure 8-24 Enabling TEC events for the default scan

You can configure IBM Tivoli Storage Resource Manager to send a TEC event for any Alerts.
Another example is to send an event when a new computer is discovered, as shown in
Figure 8-25.


Figure 8-25 Enable TEC events for discovery of new computers


9

Chapter 9. Integration with Tivoli Enterprise
Data Warehouse
This chapter provides an overview of Tivoli Enterprise Data Warehouse and the Tivoli Storage
Resource Manager Warehouse Pack. It covers the following topics:
Introduction to Tivoli Data Warehouse
Overview of the IBM Tivoli Storage Resource Manager Warehouse Pack
Tivoli GUID and Data Warehouse
Configuring Data Warehouse - importing Warehouse Pack

You can learn about the Tivoli Enterprise Data Warehouse in the following manuals and
redbook:
Tivoli Enterprise Data Warehouse Release Notes, GI11-0857
Installing and Configuring Tivoli Enterprise Data Warehouse, GC32-0744
Enabling an Application for Tivoli Enterprise Data Warehouse, GC32-0745
Introduction to Tivoli Enterprise Data Warehouse, SG24-6607


9.1 Introduction to Tivoli Enterprise Data Warehouse
The Tivoli Enterprise Data Warehouse (TEDW) is an application used to collect and manage
data from various Tivoli and non-Tivoli system management applications. The data is
imported from the source applications, stored centrally, and further processed to fit the needs
of the end users. Figure 9-1 shows the basic components of the TEDW in the logical order of
the data flow.

Tivoli Warehouse

Control Server:
IBM DB2® Warehouse
DWC Metadata

Source Apps Tivoli Reporting Services

ITM ETL
Tivoli
Reporting
Interface
Inventory ETL
Data Marts
Data Marts
ETL Data Marts
TEC ETL Central Data
Data Marts Business Intelligence Tools
Warehouse
Data Marts
Data Marts
IBM Cognos

ETL Business
Source App Brio Objects

Figure 9-1 Tivoli Data Warehouse data flow

The first step to introducing TEDW is enabling the source applications. This means to provide
all tools and customizations necessary to import the source operational data into the central
data warehouse. All components needed for that task are collected in Warehouse Packs for
each source application.

An important part of the Warehouse Packs is the ETL programs (Extract, Transform, and
Load). ETL programs process data in three steps. First they extract the data from a data
source. Then the data is validated, transformed, aggregated, and cleansed so that it fits the
format and needs of the data target. Finally, the data is loaded into the target database.

In TEDW there are two types of ETLs. The central data warehouse ETL pulls the data from
the source applications and loads it into the central data warehouse. The central data
warehouse ETL is also known as source ETL or ETL1. The second type of ETL is the data
mart ETL.

The central data warehouse (CDW) is the database that contains all enterprise-wide
historical data (with hour as the lowest granularity). This data store is optimized for the
efficient storage of large amounts of data and has a documented format that makes the data
accessible to many analysis solutions. The database is organized in a very flexible way, and
you can store data from new applications without adding or changing tables.

The data mart ETL extracts a subset of historical data from the central data warehouse that
contains data tailored to and optimized for a specific reporting or analysis task. This subset of
data is used to create data marts. Data mart ETL is also known as target ETL or ETL2 .


A data mart satisfies the needs of a specific department, team, or customer. The format of a
data mart is specific to the reporting or analysis tool you plan to use. Each application that
provides a data mart ETL creates its data marts in the appropriate format.

TEDW provides a Report Interface (RI) that creates static two-dimensional reports of your
data using the data marts. The RI is a role-based Web interface that can be accessed with a
Web browser without any additional software installed on the client. You can also use other
tools to perform OLAP analysis, business intelligence reporting, or data mining.

The Control server is the system that contains the control database, which contains metadata
for Tivoli Enterprise Data Warehouse and from which you manage your data warehouse. The
Control server controls communication between the Control server, the central data
warehouse, the data marts, and the Report Interface.

The Control server uses the Data Warehouse Center to define the ETL processes and the
star schemas used by the data marts. You use the Data Warehouse Center to schedule,
maintain, and monitor these processes.

For more information about Tivoli Enterprise Data Warehouse, refer to Introduction to Tivoli
Enterprise Data Warehouse, SG24-6607.

9.2 Tivoli Storage Resource Manager Warehouse Pack
Tivoli Storage Resource Manager has a three-tier architecture: a user interface (UI)
component, a Server component, and an Agent component. Agents collect statistics about
accessible storage and send that information to the centralized Server. The Agent must be
installed on all of the machines where the user wants to monitor storage and storage activity.
The Server receives information from the Agent(s) and saves that information in the
Enterprise Repository (Figure 9-2).

The Tivoli Storage Resource Manager Warehouse Pack provides the steps that extract data
from the Tivoli Storage Resource Manager Enterprise Repository database. The central data
warehouse ETL transforms that data so it conforms to the central data warehouse format and
then loads it into the central data warehouse of Tivoli Enterprise Data Warehouse. Other
products, like Tivoli Service Level Advisor, pull data into data marts they provide to use with
service level agreement reports.

Collection of data from IBM Tivoli products into one central repository provides the user with
the opportunity to see trends in operation, resource usage and cross product interoperability.
Tivoli Storage Resource Manager historical data is available for use by Tivoli Service Level
Advisor (SLA) and Tivoli Storage Manager.

Consult the Tivoli Service Level Advisor documentation for information about its installation,
configuration, and use. Tivoli Enterprise Data Warehouse and IBM DB2 Data Warehouse
Center ETL processes are designed to perform data collection at least once a day.

Chapter 9. Integration with Tivoli Enterprise Data Warehouse 433

ITSRM Server DB
Server

ETL1

Central Data Warehouse

SLA ETL2

ITSRM
Client/Agent

SLA
Data marts

ITSRM
History Aggregator
panel

Figure 9-2 Warehouse pack structure

9.3 Tivoli GUID and Data Warehouse
Some Tivoli products have adopted the use of a globally unique identifier (GUID) that is
permanently assigned to computer systems running storage products. Tivoli Storage
Resource Manager Version 1.2 implements this feature as a software identifier and the GUID
package is automatically installed on the Server and Agents . The GUID allows these
products to coordinate computer system data in the central data warehouse. The GUID is
recorded as an attribute in the central data warehouse for each Tivoli Storage Resource
Manager Server and Agent when available.

A STORAGE_GUID attribute will not be available for the monitored systems until all Agents
are updated to Tivoli Storage Resource Manager Version 1.2.

Consult the Tivoli Storage Resource Manager Version 1.2 documentation for a list of
platforms that support GUID.

9.4 Configuring TEDW: Importing Warehouse Pack
In this section we will describe how to import the Tivoli Storage Resource Manager
Warehouse Pack.


9.4.1 Prerequisites
Before installing the IBM Tivoli Storage Resource Manager Warehouse Pack, you need to
install the following products and patches:
Tivoli Storage Resource Manager, Version 1.2
IBM DB2 UDB Enterprise Edition, Version 7.2 with Fix Pack 6
Tivoli Enterprise Data Warehouse required e-fixes to IBM DB2 UDB v7 Fix Pack 6
(1.1-TDW-0002)
Tivoli Enterprise Data Warehouse, Version 1.1
Tivoli Enterprise Data Warehouse 1.1 Fix Pack 2 (1.1-TDW-FP02)

You can get the TEDW Fix Packs at the Web site:
http://www.ibm.com/software/sysmgmt/products/support/TivoliDataWarehouse.html

The TEDW required fixes for DB2 are at the Web site:
http://www-1.ibm.com/support/entdocview.wss?uid=swg24001636

Refer to the manual Installing and Configuring Tivoli Enterprise Data Warehouse, GC32-0744
and the redbook Introduction to Tivoli Enterprise Data Warehouse, SG24-6607 for information
on installing TEDW. We do not provide the detailed installation steps here - simply follow the
given instructions.

9.4.2 Installing the Warehouse Enablement Pack
You will first need to download the latest Warehouse Pack from:

http://www.ibm.com/software/sysmgmt/products/support/TivoliDataWarehouse.html

Select Downloads and then Warehouse Packs. Download the Storage Resource Manager
Warehouse Pack and unzip it to a directory. We used:
C:Tivoli-SoftwarewepITSRM_WEP1.2.
1. To import the Warehouse Pack, start the setup program from the Tivoli Enterprise Data
Warehouse installation media. Click Next and on the next screen choose Application
Installation only (Figure 9-3). (Note that when you installed TEDW, the selection was
Custom/Distributed.)


Figure 9-3 Application installation only

2. Verify that the fully qualified local hostname appears on the next screen (Figure 9-4).

Figure 9-4 Verify the fully qualified hostname

3. Enter the DB2 username and password of the data warehouse database (Figure 9-5),
which you configured when installing TEDW.


Figure 9-5 Enter username and password of the data warehouse database

4. Next, you need the path to the Warehouse Pack. The directory entered should contain the
file twh_app_install_list.cfg (Figure 9-6), which was part of the zip package downloaded at
the beginning of this section.

Figure 9-6 Enter path to the Warehouse Pack

5. Choose whether to install additional Warehouse Packs (Figure 9-7) for other Tivoli
products.


Figure 9-7 Additional products installation dialog

6. Click Install to actually install the Warehouse Pack (Figure 9-8).

Figure 9-8 Start actual installation

7. Depending on what type of machine you have, this can take some time to complete. If
everything went well, the summary screen appears (Figure 9-9).


Figure 9-9 Successfully finished installation

This step imported the IBM Tivoli Storage Resource Manager Warehouse Pack into Tivoli
Enterprise Data Warehouse.

9.4.3 Register the Tivoli Storage Resource Manager database with ODBC
Next, register the IBM Tivoli Storage Resource Manager repository database with the ODBC
interface on the warehouse manager server.
1. If it is a DB2 database, as in our case, start the Client Configuration Assistant from the
DB2 Program Folder. It shows the ODBC data source that is already configured. To add
the repository DB, click Add in the upper right corner of the window (Figure 9-10).

Note: If you are running IBM Tivoli Storage Resource Manager repository on the
Cloudscape database, you cannot use the Warehouse Enablement Pack.


Figure 9-10 DB2 Client Configuration Assistant

2. There are three different ways to register a database, we chose to Manually configure a
connection to a database (Figure 9-11).

Figure 9-11 Choose how to make a connection


3. Choose the connection protocol. We used TCP/IP (Figure 9-12).

Figure 9-12 Choose communication protocol

4. Next, enter the hostname and the port that the remote DB2 instance uses (Figure 9-13).
You can determine the port by listing the /etc/services (or
%SystemRoot%system32driversetcservices on Windows) file on the Tivoli Storage
Resource Manager Server (or remote database server).


Figure 9-13 Enter hostname and DB2 instance port

5. Then, enter the database name (ITSRMDB in our example); see Figure 9-14.

Figure 9-14 Name the database


6. The last relevant screen lets you choose whether to make this database available to
ODBC or not. We accepted this value and clicked Finish (Figure 9-15).

Figure 9-15 Register database with ODBC

7. A Confirmation screen appears (Figure 9-16). Click Test Connection.

Figure 9-16 Test connection

8. Enter the database user ID and password (Figure 9-17).


Figure 9-17 Enter UID and password

9. If the connection worked, you will see the following screen (Figure 9-18).

Figure 9-18 Test successfully

9.4.4 Configuring Tivoli Enterprise Data Warehouse
After installing the enablement pack and registering the repository database as an ODBC
data source, we must configure the Tivoli Enterprise Data Warehouse to receive IBM Tivoli
Storage Resource Manager data:
1. First open the DB2 control center: Start -> Programs -> DB2 -> Control Center
(Figure 9-19).


Figure 9-19 DB2 Control Center

From the menu bar, choose Tools -> Data Warehouse Center. This is the main
application for configuring the Central Data Warehouse (CDW), the Data Marts and the
ETLs (Figure 9-20).

Figure 9-20 Data Warehouse Center

2. It consists of five different topics:
– Subject Areas - The ETLs are configured here
– Warehouse Sources - All the ODBC application data sources are in here
– Warehouse Targets - All the ODBC data targets (CDW, Marts)
– Warehouse Schemas - Contains information about data structures
– Administration - Contains information about users, etc.
Open the Warehouse Sources folder, right-click BTM_ITSRM_Source and select
Properties (Figure 9-21).


Figure 9-21 Warehouse Sources for IBM Tivoli Storage Resource Manager

3. Click the Data Source tab and enter the name for your ODBC connection in the data
source name field (Figure 9-22). The default name is TIVOLISR, which we accepted.

Figure 9-22 Data Source Properties

Enter also the appropriate user name and password (Figure 9-23) and click OK.


Figure 9-23 BTM_ITSRM_Source Properties

4. Open the Warehouse Targets folder, right-click BTM_TWH_CDW_Target and select
Properties (Figure 9-24).

Figure 9-24 Target Properties

5. Do not change the database name, just enter the password for the CDW DB2 user
(Figure 9-25). Click OK to complete.


Figure 9-25 Enter password for DB2 CDW target

9.4.5 Configure ETLs
After we have successfully configured the ODBC database connections, we opened the
Subject Area folder and selected the BTM_Tivoli_Storage_Resource_Manager folder (from
Figure 9-21 on page 446) to configure the ETLs. You will see three ETL processes:
BTM_C05_Initialize - Run this process only once as part of the installation of the
Warehouse Pack. It modifies the repository database of IBM Tivoli Storage Resource
Manager to incorporate the changes necessary to run Tivoli Data Warehouse.
BTM_C10_ETL1 - The actual ETL process that gathers the data from the IBM Tivoli
Storage Resource Manager repository database into the CDW database. This should be
run daily.
BTM_C15_Expire_Server - This process should only be run to remove all information and
statistics from the CDW.

A process can have different types of objects. The first process has only one actual
“executable” step, which you can see at the top position in the right window of Figure 9-26,
called Create Archive. These steps can have three different states:
Development - Used for modifications
Test - You can execute, but changes are rolled back after completion
Production - You can execute and changes persist, but no configurations can take place

To run the process, right-click the process and select Mode -> Production (Figure 9-26).


Figure 9-26 Subject Areas

To run the initialization process, select the Warehouse menu and select Work in Progress
(Figure 9-27).


Figure 9-27 Open the Work in Progress window

In the new window, select Work in Progress -> Run New Step (Figure 9-28).

Figure 9-28 Run New Step


A new dialog appears, listing all processes that are in the production state. Select
BTM_c05_s010_Create_Archive and click the > button in the middle of the screen. Run this
step by clicking OK (Figure 9-29).

Figure 9-29 Selecting the steps to run

In the main window, you can see the progress of the step. If it finished successfully the status
shows Successful (Figure 9-30).

Figure 9-30 Work in Progress

This created some additional configurations inside the IBM Tivoli Storage Resource Manager
repository database.

To schedule the actual ETL to extract data, right-click the BTM_C10_ETL1_Process and
select Schedule (Figure 9-31).


Figure 9-31 Schedule Process

This will open the Schedule properties. Enter suitable parameters (Figure 9-32).

Figure 9-32 Schedule a Process times


The Task Flow tab shows which steps are associated with the process. The ETL1 process
incorporates four different steps, which are run sequentially (Figure 9-33).

Figure 9-33 Task Flow

In the last tab, Notification, you can send an e-mail, if a step fails to run (Figure 9-34).

Figure 9-34 E-mail alert

The schedule is not enabled until you change the mode on the associated steps to
Production. You can select multiple steps (Figure 9-35).


Figure 9-35 Change mode to production

When you now look at the Work in Progress window, you should see the scheduled ETL
process with a status of Scheduled, Figure 9-36.

Figure 9-36 Scheduled process

This process will now run at the specified time. To run it manually, right-click the process and
select Run Now (Figure 9-37).


Figure 9-37 Run process manually

You should see the progress of each single step in the window. If everything worked well, you
should see the status as Successful for each step (Figure 9-38).

Figure 9-38 Manually run steps

This process retrieved the information from the IBM Tivoli Storage Resource Manager
repository database and loaded it into the Tivoli Enterprise Central Data Warehouse.

9.4.6 Verifying data in DB2
You can view the loaded data manually in the DB2 Control Center. Open the TWH_CDW
database, right-click the COMP table and choose sample-contents (Figure 9-39).


Figure 9-39 COMP table

Look for entries in the COMPTYP_CD row saying BTM_Server, BTM_Client or File_System.
These are entries generated by the Warehouse Pack for IBM Tivoli Storage Resource
Manager (Figure 9-40).

Figure 9-40 CDW entries from Warehouse Pack.

The structure of the Warehouse Pack generated entries is described in the PDF document
shipped in the doc directory of the Warehouse Pack. This document provides in-depth
information about the ETL process and the database structure.

The Warehouse Pack for IBM Tivoli Storage Resource Manager currently contains only the
ETL 1 process. To use the collected data, you can use Tivoli Service Level Advisor (TSLA).
The redbook Introducing IBM Tivoli Service Level Advisor, SG24-6611 explains how to
incorporate different Warehouse Pack data into the TSLA. It also explains how to extract data
and build reports with popular third-party Business Intelligence applications. Alternatively, you
can extract the data and use third party reporting tools as described in Introduction to Tivoli
Enterprise Data Warehouse, SG24-6607.

A future version of the Warehouse Pack for IBM Tivoli Storage Resource Manager will have
predefined reports and the data mart ETL 2.


10

Chapter 10. Integration with Tivoli
Configuration Manager
This chapter shows you can use IBM Tivoli Configuration Manager to distribute IBM Tivoli
Storage Resource Manager agent code.

We assume you have basic understanding of IBM Tivoli Configuration Manager and a running
installation of Tivoli Enterprise Framework V3.7.1 or 4.1 and IBM Tivoli Configuration
Manager V4.2. For more information about these products see the redbook All About IBM
Tivoli Configuration Manager V4.2, SG24-6612.

This chapter covers the following topics
Introduction to IBM Tivoli Configuration Manager
Inventory - determine who has got which version
Software Distribution - Distributing IBM Tivoli Storage Resource Manager Agents and GUI
(silent installation)


10.1 Introduction to IBM Tivoli Configuration Manager
IBM Tivoli Configuration Manager, Version 4.2, is a solution for controlling software
distribution and asset management inventory in a multiplatform environment. It focuses on
deploying and managing software in complex, distributed enterprise environments. IBM Tivoli
Configuration Manager is a key solution to rapidly and efficiently deploying complex
mission-critical or desktop productivity applications to multiple locations from a central point
and to gather and maintain the inventory information about hardware and software assets,
easily, quickly, and accurately.

Tivoli Configuration Manager consists of the following main components:
Inventory
Software Distribution

Software Distribution enables you to install, configure, and update software remotely within
your network.

Inventory enables you to gather and maintain up-to-date inventory asset management
information in a distributed environment. This helps system administrators and accounting
personnel to manage complex, distributed enterprises.

Tivoli Configuration Manager also provides the following services:
Activity Planner
Change Manager
Resource Manager
Web Interface
Enterprise Directory Query Facility

Activity Planner enables you to define a group of activities that originate from different
applications in an activity plan, submit or schedule the plan for running, and monitor the plan
while it runs.

Change Manager functions with Activity Planner to support software distribution, inventory,
and change management in large networks. It uses reference models to simplify the
management of the network environment.

You can use Resource Manager, together with Software Distribution and Inventory, to perform
the management operations for pervasive devices.

You can use the Web Interface to install and manage various Tivoli Configuration Manager
Web objects. The Web Interface has a server component that pushes software packages,
inventory profiles, and reference models from the Tivoli region to the Web Gateway where
they are stored until they are pulled by the Web Interface endpoint.

With enterprise directory integration, you can exploit organizational information that is stored
in enterprise directories in order to determine a set of targets for a software distribution or an
inventory scan. The Enterprise Directory Query Facility enables you to select a specific
directory object, or container of directory objects, as subscribers for a reference model or an
activity plan.


10.2 Inventory - determine who has got which version
In order to determine which machine in your environment has got which product installed and
which version, you can use the Inventory part of IBM Tivoli Configuration Manager. The
process to query inventory information from your nodes includes four steps:
1. Create an inventory profile in Tivoli Framework
2. Distribute profile to endpoints
3. Build a query
4. Run the query

10.2.1 Create an inventory profile in Tivoli Framework
Open the Tivoli Desktop and navigate to your Inventory Policy Region. In our environment this
is done by opening the tonga-region Policy Region (Figure 10-1).

Figure 10-1 Tivoli Desktop

We created separate Policy Regions for each Tivoli product. Double click Inventory Policy
Region (Figure 10-2).

Chapter 10. Integration with Tivoli Configuration Manager 459

Figure 10-2 Policy Region tonga-region

Make sure that the Inventory Policy Region contains the InventoryConfig resource as a
Managed Resource. To determine if it has been set, right-click the Policy Region and select
Managed Resources. The dialog in Figure 10-3 appears.

Figure 10-3 Managed Resources for Inventory

For our environment we created the default Query Libraries with the script
inventory_query.sh in the bin/generic/inv/SCRIPTS/QUERIES directory of the Tivoli
installation directory and created a Profile Manager called Inventory_default_PM.
(Figure 10-4). To create a Profile Manager select Create in the top menu and select Profile


Manager.

Figure 10-4 Policy Region Inventory

Double click the Profile Manager and the dialog in Figure 10-5 appears.

Figure 10-5 Profile Manager Inventory


Create an Inventory Profile by clicking Create in the top menu and select Profile. Enter the
name and select InventoryConfig as the Profile type. Right-click the newly created Profile
and select Edit. The screen that appears shows you the global properties of the Inventory
Profile (Figure 10-6).

Figure 10-6 Inventory Profile Global Properties

Since we want to create a software only inventory scan, you should deselect all hardware
related check boxes. The only ones we need is the PC Software section (Figure 10-7) and the
UNIX Software section (Figure 10-8).


Figure 10-7 Inventory Profile PC Software

There are two possible ways to collect software information from endpoints. One is to scan all
the files on your machine and compare them to a predefined list, thus determining an installed
product by filename and size of a significant file in the software package. IBM Tivoli Storage
Resource Manager ships these so called Inventory Signature files with the product. They can
be found in the installation directory in the TIVINV subdirectory. The signature files are zero
bytes in length and are recognized by filename (TSRM01_02.SIG for the IBM Tivoli Storage
Resource Manager - Manager Version 1.2). The signatures for IBM Tivoli Storage Resource
Manager are already incorporated in the latest inventory signature files, which you can
download from the IBM Software support Web site.

Another way to determine installed software is to query the native software repository of the
OS. This gives you very fast scans, but relies on the fact that the software has registered itself
in the OS during installation, rather than just copying files.

For IBM Tivoli Storage Resource Manager you can do both - the choice for your environment
depends on the practices of your IBM Tivoli Configuration Manager environment.

In our examples we chose to use the native software query, so we check just the Scan
Registry for Product Information boxes in the dialog (Figure 10-8), not the Scan for File
Information


Figure 10-8 Inventory Profile UNIX Software

Click OK to close the dialog and distribute the Inventory Profile to your Endpoints. Right-click
on the Profile and select Distribute (Figure 10-9).


Figure 10-9 Distribute Inventory Profile

This opens a dialog where you can choose the machines which will run the inventory scan.
After selecting, click on the Distribute & Close button (Figure 10-10).


Figure 10-10 Distribute Inventory Profile dialog

You can determine the status of the inventory scan with a tool called Distribution Status
console. If it is installed, you find it on the main screen of your Tivoli Desktop (Figure 10-1 on
page 459). Double click on the icon and a console opens (Figure 10-11).


Figure 10-11 Distribution Status Console

In the upper window, double click on the Inventory Scan distribution and in the lower window
select All Nodes. You can see which scans are successfully completed, pending, failed etc.

When the scans are all finished, you can query the collected information. There are many
standard queries, but we want to gather only the data for IBM Tivoli Storage Resource
Manager. Therefore we create a new query by selecting Create -> Query (Figure 10-12).

Figure 10-12 Create Query Library

Name the Query and select inv_query as the repository. This is the Inventory Database RIM
object. The table containing the native software information is NATIVE_SWARE_VIEW.
Select the columns you want and add a filter: Column name PACKAGE_NAME = ‘IBM Tivoli
SRM’ (Figure 10-13).


Figure 10-13 Edit Inventory Query

Click Run Query to execute the query while it is being edited. The output shows all the
installed IBM Tivoli Storage Resource Manager products including Agents, Manager and
Consoles (Figure 10-14).


Figure 10-14 Output for IBM Tivoli Storage Resource Manager Query

You can also query the Inventory database with a native DB2 client. That enables you to
connect to Business Intelligence tools or script based applications.

Play around with the queries and you will find that there is much additional information which
can be obtained from them. In combination with the hardware inventory scans, you can
determine which Fibre Channel cards are in your systems, and which firmware levels and
drivers they are using. In the following query output we queried all the IBM software which
was on the endpoints (Figure 10-15).

Figure 10-15 Output for IBM Query


10.3 Software distribution
To automatically deploy a large number of IBM Tivoli Storage Resource Manager Agents, you
can use the Software Distribution component of IBM Tivoli Configuration Manager. The
distribution process has four steps:
1. build software package with the Software Package Editor
2. create software distribution profile in Tivoli Framework
3. import and build software package
4. perform installation/uninstall tasks

10.3.1 Build software package with Software Package Editor
Before you can use the Software Package Editor you have to install it from the Configuration
Manager CD. It must be either installed on a managed node or a Tivoli endpoint so that the
software packages, once built, can be automatically fetched from the host. Figure 10-16
shows the Software Package Editor with a new package which we called ITSRM-Agent.

Figure 10-16 Software Package Editor with new package ITSRM-Agent

You can build one package for each platform or all platforms in one. The benefit of separating
the packages by operating system is that you prevent having to download all the code to all
the endpoints before installation occurs. If temporary space is an issue, you should split into
multiple packages. This in turn makes it slightly more complicated in installation tasks,
because you have to group the endpoints by operating system. We will give some simple
examples here, but if you already have a production ready installation of Configuration
Manager, then the design rules will be in place, and you should build the packages according
to them.

Right-click the package name and select Properties. The dialog in Figure 10-17 displays.
Enter the package version and a title for your package. Leave all the other parameters at their
default values.


Figure 10-17 Properties dialog

For the actual installation we use the command line procedure. First copy the installation
media to the hard drive. We only need the setup.exe and the directories install, java and
agent (Figure 10-18).

Figure 10-18 Agent installation directories

After setting the package properties, we add objects to the package. From the screen in
Figure 10-16, click the tab Execute program as shown in Figure 10-19.


Figure 10-19 Add an execute program action to the package

With this type of action you can distribute files to the endpoint, run the provided script and
delete the temporary files. During the Tivoli Storage Resource Manager installation, the setup
program ends at once and additional processes are spawned. For this reason, we cannot use
software distribution for corequisite files since these file would be deleted, when they are still
needed. Therefore, we need additional actions to distribute the installation media.

After selecting the the action, the Execute Program Properties dialog appears (Figure 10-20).

Figure 10-20 Install dialog

Enter the full path to the installation setup program. The example shows the installation of the
Windows agent. This must be the path as it appears after transferring the files to the endpoint,


which could be different from the directory structure on the node where you are building the
filepack. Do not include any arguments, then select the Advanced dialog (Figure 10-21).

Figure 10-21 Advanced tab

In the arguments field, enter the parameters for silent installation. The syntax is:
setup.exe -s servername -d installdir -p serverport -q agentport -x (no scripts from
server) -n (no initial scan)

For example, the only non-default parameters are to specify server name (WISLA) and no
initial scan of the Agent. The full installation command is:
setup.exe -s wisla -n

The Working Directory entry points to the installation directory. Optionally, you can redirect
standard out and standard error to files. Click OK to end the dialog.

This should be sufficient for the installation process. Configuration Manager can also do
deinstallation, so to configure the deinstallation process select the Remove tab from
Figure 10-20 on page 472, as shown in Figure 10-22.


Figure 10-22 Remove dialog

A single command is sufficient to remove the software. The path to the deinstallation program
is in the installation directory of the IBM Tivoli Storage Resource Manager agent. We need an
argument for the uninstallation program. To open the dialog, click Advanced (Figure 10-23).


Figure 10-23 Advanced properties

The parameters to specify are java -uq. This procedure is not documented in the manual, but
is derived from the script to remove the UNIX agents and proved to work well. Be sure to add
the working directory for the process.

We chose to make just one software package for Windows and AIX machines. To prevent
execution on an AIX machine, you can specify a condition when to run that action, using the
Condition button at the top right hand corner of Figure 10-22. Figure 10-24 displays.


Figure 10-24 Condition

Choose os_name from the list box, add an == operator, and enter Windows_NT. This will
ensure execution only on the desired platform.

Using the same procedure, we added an extra action for the AIX installation, starting from the
Execute Program Properties dialog shown in Figure 10-20 on page 472. The actions to define
are mainly the same except for the paths and the setup.aix program. Also, we added a
condition that allows execution only on AIX machines.

Since we can not download the installation media with the Execute Program action, we have
to distribute it with an extra step.

In the main screen of the Software Package editor (Figure 10-16 on page 470), choose the
Add Object tab and click the Add Directory icon. The dialog in Figure 10-25.


Figure 10-25 Add Directory dialog

To ensure all subdirectories are getting copied, choose the Advanced button on the lower left
corner, and select the Descend Directories check box (Figure 10-26).

Figure 10-26 Descend Directories

The ready-to-build software package is shown in Figure 10-27.


Figure 10-27 Ready-to-build software package

Save this package to an .sp file on your server and exit the Software Package Editor.

10.3.2 Create software distribution profile in Tivoli Framework
Open your Tivoli Desktop and navigate to the Software Distribution policy region. Make sure it
has the Software Distribution package as a managed resource in the properties menu. To
determine if it has been enabled, click on Properties -> Managed Resources and check if
the SoftwarePackage resource is on the left side. Then create a Profile Manager for use by
IBM Tivoli Storage Resource Manager packages (Figure 10-28).

Figure 10-28 Policy Region with Profile Managers

Double-click the object PM_SD_ITSRM to open the Profile Manager, and create a Profile with
the name of your file package including the version (Figure 10-29).


Figure 10-29 Create Software Package Profile

After you have created the Profile, an empty package icon appears in the Profile Manager.
Add any subscribers for the distribution of the package.

Figure 10-30 Profile Manager with Profiles and Subscribers


Next we need to import the previously defined Software package to the Profile we just
created. Right-click the Profile and choose Import (Figure 10-31).

Figure 10-31 Import Software Package

A dialog appears, where you can select the node on which you have previously created the
Package and the path to the .sp file. Checking Build, will include all the source files and
programs and actions into one single file (.spb) to be distributed to the target endpoint. Enter
the location where you want to store the .spb file. You might want to store it on your software
distribution server or on any of your software depot servers. If your are rebuilding it, check
Overwrite (Figure 10-32).


Figure 10-32 Import and build a software package

The package icon of the should now be a sealed package, ready to ship to your targets. For
installation to occur, right-click the package and choose Install (Figure 10-33).


Figure 10-33 Install a software package

The install dialog, which is shown in Figure 10-34, lets you select on which endpoints to install
the software. Our package will work on Windows and AIX servers. Additional checks can be
made, eg. whether the software is already installed or with the Change Manager feature, if
you are allowed to install the software due to licensing issues. For additional information see
the redbook All About IBM Tivoli Configuration Manager Version 4.2, SG24-6612.


Figure 10-34 Install Software Package

You can also schedule the installation and query inventory to look for hardware or software
Constraints. To ensure that every host in your environment has an IBM Tivoli Storage
Resource Manager agent, you can use the strategies described in Implementing Automated
Inventory Scanning and Software Distribution After Auto Discovery, SG24-6626, to discover
new nodes through Tivoli NetView, install an endpoint, perform an inventory query, and
automatically deploy the S agent on them.

Another method of identifying hosts to install software on, is querying an LDAP directory like
Microsoft Active Directory or IBM Directory with the Enterprise Directory Query facility. Then
you would be able to create a machine group for IBM Tivoli Storage Resource Manager, and
automatically deploy the software once a machine belongs to the group.

Configuration Manager enables you to remove the software as well. For this function,
right-click the package and select Remove (Figure 10-35).


Figure 10-35 Remove a Software Package

All the other options like verify, clean, etc., are not defined and will not work.


11

Chapter 11. Integration with Tivoli Monitoring
This chapter describes some possibilities for using IBM Tivoli Monitoring to ensure a proper
operation of the IBM Tivoli Storage Resource Manager Server. We assume basic
understanding and a fully running installation of the following products:
Tivoli Framework 3.7.1 or 4.1
IBM Tivoli Monitoring 5.1.1
IBM Tivoli Enterprise Console 3.8

The following topics are covered:
Introduction to IBM Tivoli Monitoring
Using Tivoli Monitoring to maintain ITSRM
Daemons to monitor and restart actions


11.1 Introduction to IBM Tivoli Monitoring
Figure 11-1 presents a high-level overview of the interaction between various components of
IBM Tivoli Monitoring 5.1. The IBM Tivoli Monitoring 5.1 profile contains, among other
information, a resource model. The resource model is a collection of monitors that correlate
amongst themselves before attempting to perform a notification action. The IBM Tivoli
Monitoring 5.1 profile is distributed to the endpoints to monitor one or more resources
(examples of typical resources are hard disk space, paging space, and process/service).
Based on configuration settings in the IBM Tivoli Monitoring 5.1 profile, the engine runs on the
endpoint and performs the necessary monitoring on the resources that are specified in the
distributed resource model(s). The Web Health Console obtains logged data from selected
endpoints and displays the “health” of the endpoints for their resources.

Trend Analysis
C
us
to
m
iz

Profile
e
/D

De
Ro

Data
is

fa
tr

llu
ib

ul warehouse
ut

ts
p
e

lay
sp
TMR Di Web health
console
G et D
ITM at a
Heartbeat
l
tal
Ins

Resource Endpoint Endpoint
Model Distribute NT/W2K UNIX/Linux

Design
Create ITM Engine ITM Engine

Debug
Workbench

Figure 11-1 IBM Tivoli Monitoring architecture

11.2 Tivoli Monitoring with Tivoli Storage Resource Manager
There are many possibilities to use IBM Tivoli Monitoring to help securing a productive
installation of IBM Tivoli Storage Resource Manager. The base product ships with a wealth of
predefined resource models:
Filesystems
CPU
Memory
TCP/IP
Network interface
Event log


You can use any of these to monitor basic functions of your OS. Additionally, there are
numerous modules that provide special monitoring capabilities for additional software
products. There are modules for:
DB2
WebSphere® Application Server
Oracle
Microsoft Active Directory
Apache/IIS

If you want in depth monitoring for your IBM Tivoli Storage Resource Manager DB2 instance,
you can use these additional modules.

In our examples here, we use the shipped monitor Parametric Services to watch the status of
the Windows services, which are required to run IBM Tivoli Storage Resource Manager.
Additionally, there is a default action to restart stopped services.

11.3 Daemons to monitor and restart actions
This section describes how to configure IBM Tivoli Monitoring to monitor the IBM Tivoli
Storage Resource Manager Windows services.

Open the Tivoli Desktop and navigate to your Monitoring Policy Region (Figure 11-2).

Figure 11-2 Policy Region tonga-region

Create a profile manager to contain the monitoring profiles. Select Create -> Profile
Manager and create a dataless Profile manager, called PM_DM_ITSRM in our example
(Figure 11-3).

Chapter 11. Integration with Tivoli Monitoring 487

Figure 11-3 Profile Manager PM_DM_ITSANM

Open the Profile Manager, select Create -> Profile and choose a Tmw2kProfile (which is the
Monitoring profile resource). If this entry does not show up in the list, make sure the
Tmw2kProfile is in the managed resources list of the Policy Region. Figure 11-4 shows a
Profile called P_DM_ITSRM in .

Figure 11-4 Create Monitoring Profile

Double click on the newly created profile and in the screen that appears, click Add with
Defaults. This opens a chooser window, where you can select the resource model you want
to add to your profile. In the Category list box, choose Windows and select the Parametric
Services entry (Figure 11-5).


Figure 11-5 Add Parametric Services Model to Profile

After adding the resource model, we have to edit the model to include the services we want to
monitor. For that, click Edit (Figure 11-6).


Figure 11-6 Edit Resource Models

In this window, we can adjust all attributes belonging to that resource model. To specify the
services to monitor open the Parameters window (Figure 11-7). You must enter the names of
the services exactly as they appear in the Windows Registry under
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices. The services which IBM
Tivoli Storage Area Network Manager needs to run are:
DB2
TSRMagt1
TSRMsrv1


Figure 11-7 Parameters of Resource Model

Click Apply Changes and Close to close the window, bring up the next dialog with the
Indications button. As you can see from the definitions, the default action, when a service is
stopped or failed, is to restart the service automatically. Additionally a CRITICAL TEC event is
generated (Figure 11-8).


Figure 11-8 Indications and actions of resource models

To enable the TEC events globally for this Profile and to specify to which TEC server the
events are sent, click on the Properties menu in the Profiles main window (Figure 11-4 on
page 488) and the following screen will open (Figure 11-9).

Figure 11-9 TEC forwarding of events from Monitoring


Select the Send TEC Events check box and choose the event delivery method and TEC
server. The TME® (Secure) Delivery is (in most cases) the better choice, because it caches
events if the Event Server is temporarily unavailable.

Close the windows with the OK button until you are back in the Profile Manager main window.
(Figure 11-10). Subscribe the endpoints running the IBM Tivoli Storage Resource Manager -
Manager with Profile manager -> Subscriber and distribute the Profile using Profile
Manager -> Distribute -> Distribute Now.

Figure 11-10 Profilemanager for Monitoring

You can determine if your resource models are running on a particular endpoint by issuing the
wdmlseng command at thecommand line on your Tivoli Managed Region (TMR) server.
Example 11-1 shows typical output.

Example 11-1 Determining if resource models are running
bash$ wdmlseng -e wisla
Forwarding the request to the engine...

The following profiles are running:

P_DM_Basic_Win#tonga-region
TMW_EventLog :Running


TMW_PhysicalDiskModel :Running
TMW_Services :Running
TMW_TCPIP :Running
TMW_MemoryModel :Running
TMW_Process :Running
TMW_Processor :Running
P_DM_ITSRM#tonga-region
TMW_ParamServices :Running
bash$

For demonstration purposes, we stopped the TSRMsrv1 service on our Server. After a few
seconds the following TEC events appear in the TEC console (Figure 11-11).

Figure 11-11 TEC events from Monitoring

IBM Tivoli Monitoring detected the service that has been stopped and restarted it accordingly.


Part 6

Part 6 Appendices


A

Appendix A. Example scripts
In this appendix we provide several scripts we used as examples in the main text of the
redbook. The first group of scripts shows how to use IBM Tivoli Storage Resource Manager
for Databases together with IBM Tivoli Storage Manager to manage database space. The
second group consists of backup and restore scripts for the IBM Tivoli Storage Resource
Manager repository are provided. Those scripts are intended to provide basic samples only of
the functionality described. They must be modified, customized, and tested according to the
operating system, the volume manager, the database manager, the backup software, or any
other software used in your environment.

These scripts can be downloaded as described in “Locating the Web material” on page 503.

Tivoli Storage Resource Manager for Databases scripts
Example A-1 shows the ARCHORA.bat script, which can be used to archive an Oracle
database log (using Tivoli Storage Manager) on a Windows platform.

Example: A-1 ARCHORA.bat
@ECHO OFF
REM -------------------------
echo ARCHORA.BAT starting ...
echo on server %2
echo to archive %3 logs for instance %4
echo Directory to process : %1
echo Expecting %5 files to be archived for a total size of %6

REM ---------------------------------------------
if not %3 == Oracle GOTO NOTORACLE
if not exist %1 GOTO DIRNOTEXIST

REM Execute archive TSM command
REM ---------------------------
set logfile=ARCHORA.LOG
CD C:Program filesTivolitsmbaclient


@echo on
dir %1ARC*.*
dsmc archive %1ARC*.* -subdir=no -delete -descr="%2 %3 %4 ArchiveLogs" -verbose
@echo off
if not %errorlevel% == 0 GOTO DSMCERROR

@echo on
dir %1ARC*.*
echo ARCHORA.BAT ended successfully ...
exit 0

:NOTORACLE
echo Error - Not Oracle database
exit 4
:DIRNOTEXIST
echo Error - Directory does not exist
exit 4
:DSMCERROR
echo Error while running DSMC command
dir %1ARC*.*
type dsmerror.log

Example A-2 shows the BKPSQLLOG.bat script, which can be used to backup the MSSQL
transaction log should this log reaches a high usage percentage.

Example: A-2 BKPSQLLOG.BAT script
@ECHO OFF
REM -------------------------
echo SQLBKPLOG.BAT starting ...
echo on server %2
echo Transaction log of %3 database %4/%1 reaches %7 of its capacity
echo Performing transaction log backup

REM ---------------------------------------------
if not %3 == "MicroSoft SQL/Server" GOTO NOTSQL

REM Execute backup command
REM ----------------------
CD C:Program FilesMicrosoft SQL ServerMSSQLBackup
echo Current Log backups
echo -------------------
dir %1_Tlog*
cd ..binn
@echo on
sqlmaint -D %1 -BkUpLog -BkUpMedia DISK -UseDefDir
if not %errorlevel% == 0 GOTO SQLERROR
@echo off
echo New Log backups
echo ---------------
cd ..Backup
dir %1_Tlog*
echo SQLBKPLOG.BAT ended successfully ...
exit 0

:NOTSQL
echo Error - Not MSSQL database
exit 4


:SQLERROR
echo Error while running SQLMAINT command
exit 4

Appendix A. Example scripts 499

Backup and restore scripts
Example A-3 shows the script that we used to perform an offline backup of the IBM Tivoli
Storage Resource Manager DB2 database in 7.3, “Backup procedures” on page 378.

Example: A-3 ITSRMBackupOffline script
@ECHO ON
@REM Stop the IBM Tivoli SRM server
@REM ------------------------------
net stop "IBM Tivoli SRM Server"

@ECHO ON
@REM Get Status and check if Stopped
@REM -------------------------------
@if %errorlevel% EQU 0 GOTO BACKUPDB

:NOTSTOPPED
@ECHO ON
@REM IBM Tivoli SRM server not stopped - Backup cannot run
@REM -----------------------------------------------------
@echo "IBM Tivoli SRM Not Stopped !!!"
@echo "Backup process cancelled "
exit 1

:BACKUPDB
@ECHO ON
@REM IBM Tivoli ITSRM server is stopped - Backup can run
@REM -------------------------------------------------
C:PROGRA~1SQLLIBBINdb2cmd.exe /c /w /i db2 backup database ITSRMDB USE TSM

@REM Backup completed - Start IBM Tivoli SRM
@REM ---------------------------------------
:STARTITSRM
net start "IBM Tivoli SRM Server"

@ECHO ON
@REM Get Status and check if Started
@REM -------------------------------
@if %errorlevel% EQU 0 GOTO STARTOK

@REM IBM Tivoli SRM not started
@REM --------------------------
@echo "IBM Tivoli SRM Server Not Started !!!"
exit 1

@REM IBM Tivoli SRM started
@REM ----------------------
:STARTOK
@echo "IBM Tivoli SRM started successfully"

Example A-4 shows the script that we used to an online backup of the IBM Tivoli Storage
Resource Manager DB2 database in 7.3, “Backup procedures” on page 378.


Example: A-4 ITSRMBackupOnline script
@ECHO ON
@REM List active connections for information
@REM ---------------------------------------
db2cmd.exe /c /w /i db2 list applications for database ITSRMDB | findstr /i SQL1032N
@if %errorlevel% NEQ 0 GOTO BACKUPDB

@REM SQL1032N found - DB is not started
@REM ----------------------------------
@echo "SQL1032N return - DB2 is not active - Backup cancelled !!!"
exit 1

:BACKUPDB
@ECHO ON
@REM DB2 is active - Backup can run
@REM ------------------------------
C:PROGRA~1SQLLIBBINdb2cmd.exe /c /w /i db2 backup database ITSRMDB ONLINE USE TSM

@REM Backup completed - List connections
@REM -----------------------------------
db2cmd.exe /c /w /i db2 list applications for database ITSRMDB

Appendix A. Example scripts 501

B

Appendix B. Additional material
This redbook refers to additional material that can be downloaded from the Internet as
described below.

Locating the Web material
The Web material associated with this redbook is available in softcopy on the Internet from
the IBM Redbooks Web server. Point your Web browser to:
ftp://www.redbooks.ibm.com/redbooks/SG246886

Alternatively, you can go to the IBM Redbooks Web site at:
ibm.com/redbooks

Select the Additional materials and open the directory that corresponds with the redbook
form number, SG246886.

Using the Web material
The additional Web material that accompanies this redbook includes the following file:
File name Description
SG246886.zip Zipped Sample Scripts

System requirements for downloading the Web material
The following system configuration is recommended:
Hard disk space: 1 MB
Operating system: Windows 2000
Processor: Pentium or higher
Memory: 128 MB


How to use the Web material
Create a subdirectory (folder) on your workstation, and unzip the contents of the Web
material zip file into this folder.


Abbreviations and acronyms
API Application Programming Interface NAS Network Attached Storage
CDE Common Desktop Environment NDS NetWare Directory Services
CDW Central Data Warehouse NTFS NT Filesystem
CIM Common Information Model ODBC Open Database Connectivity
CIM/OM Common Information Model Object RAID Redundant Array of Independent
Manager Disk
CR/LF Carriage Return/Line Feed RDBMS Relational Database Management
CSV Comma Separated Values Server

DBA Database Administrator RI Report Interface
DFSMS Data Facility Systems Managed RIM RDBMS Interface Module
Storage ROI Return on Investment
DMS Database Managed Storage
SAN Storage Area Network
DR Disaster Recovery
SDD Subsystem Device Driver
ESS Enterprise Storage Server
SID System Identifier
ETL Extract, Transform and Load
SLA Service Level Agreement
GUI Graphical User Interface
SLP Service Location Protocol
GUID Globally Unique Identifier
SMIS Storage Management Interface
HA High Availability or Highly Available Specification
HACMP High Availability Clustered SMS System Managed Storage
Multiprocessing
SMTP Simple Mail Transfer Protocol
HCL Hardware Compatibility List
SNMP Simple Network Management
HTML Hypertext Markup Language Protocol
IANA Internet Assigned Numbers SRM Storage Resource Management
Authority
TEC Tivoli Enterprise Console
IBM International Business Machines
TEDW Tivoli Enterprise Data Warehouse
Corporation
TSLA Tivoli Service Level Advisor
ICMP Internet Control Message Protocol
UDB Universal Database
IDE Integrated Device Electronics
URL Uniform Resource Locator
IIS Internet Information Server
VM Virtual Memory
ITSO International Technical Support
Organization WWN World-Wide Name
JDBC Java Database Connectivity WWPN World-Wide Port Name
JFS Journaled Filesystem
JVM Java Virtual Machine
LAN Local Area Network
LCF Light Client Framework
LDAP Lightweight Directory Access
Protocol
LSS Logical Sub System
LUN Logical Unit Number
MOF Managed Object Format
MSCS Microsoft Cluster Services


Related publications

IBM Redbooks
The publications listed in this section are considered particularly suitable for a more detailed
discussion of the topics covered in this redbook.

For information on ordering these publications, see “How to get IBM Redbooks” on page 508.
Tivoli Storage Management Concepts, SG24-4877
Getting Started with Tivoli Storage Manager: Implementation Guide, SG24-5416
Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment, SG24-6141
Using Data Protection for Microsoft SQL Server, SG24-6148
Backing Up Oracle Using Tivoli Storage Management, SG24-6249
Early Experiences with Tivoli Enterprise Console, SG24-6015
Introducing IBM Tivoli Service Level Advisor, SG24-6611
Introduction to Tivoli Enterprise Data Warehouse, SG24-6607
All About IBM Tivoli Configuration Manager V4.2, SG24-6612
Implementing Automated Inventory Scanning and Software Distribution After Auto
Discovery, SG24-6626

Other resources
These publications are also relevant as further information sources:
IBM Tivoli Storage Resource Manager V1.1 Configuration and Getting Started Guide,
SC32-9067
IBM Tivoli Storage Resource Manager V1.1 Installation Guide, GC32-9066
IBM Tivoli Storage Resource Manager V1.1 Reference Guide, SC32-9069
Tivoli Enterprise Data Warehouse Release Notes, GI11-0857
Installing and Configuring Tivoli Enterprise Data Warehouse, GC32-0744
Enabling an Application for Tivoli Enterprise Data Warehouse, GC32-0745

Referenced Web sites
These Web sites are also relevant as further information sources:
IBM Tivoli Storage Resource Manager home page
http://www-3.ibm.com/software/tivoli/products/storage-resource-mgr/
IBM Tivoli Storage Resource Manager supported platforms
http://www.ibm.com/software/tivoli/products/storage-resource-mgr/platforms.html
IBM Tivoli Storage Manager home page:
http://www.ibm.com/software/tivoli/products/storage-mgr/


CIMS home page
http://www.cims.com/
Perl home page
http://www.perl.org
Sybase JDBC
http://www.sybase.com/products/middleware/jconnectforjdbc
Oracle JDBC
Microsoft SQL-Server JDBC
http://msdn.microsoft.com/downloads/default.asp?URL=/downloads/sample.asp?url=/MSDN-FILE
Other Microsoft SQL-Server JDBC
http://www.atinav.com/products/aveconnect/MSSQLserver/aveconnect2.htm

How to get IBM Redbooks
You can order hardcopy Redbooks, as well as view, download, or search for Redbooks at the
following Web site:
ibm.com/redbooks

You can also download additional materials (code samples or diskette/CD-ROM images) from
that site.

IBM Redbooks collections
Redbooks are also available on CD-ROMs. Click the CD-ROMs button on the Redbooks
Web site for information about all the CD-ROMs offered, as well as updates and formats.


Index
proxy model 20
A reporting 146
Agent 50 schema 17
AIX CIM Device Model for Storage 17
clustering 62 CIM/OM 20, 30, 54, 67, 145, 298
volume group 211 certificates 153
AIX commands configuration 150
lslv 211 discovery 298
lspv 215–216 installation 148
lsvpcfg 216 registration with Tivoli Storage Resource Manager
Alert 23, 25, 27, 35, 41, 50–51, 101, 119, 173, 176, 189, 153
203, 205, 208, 227, 428–429 secure communication 153
and Tivoli Storage Resource Manager 433 security 153
API 16 services 150
applet 49, 81, 84 users 150
application availability 24, 31 CIM/OM server
archive 12 supported platforms 146
archive bit 287–288, 295 CIMOM 20
asset management 458 CIMS 42, 364
asset reporting 36, 40, 178, 250, 252, 256 CIM-XML 19
at risk files 181 class definition file 413
audio data 6 CLI 147
automount 57 client options file 396
availability reporting 35, 40, 174, 250, 262 Cloudscape 30, 80
clustered resources 138
B clustering 61–62
backup 15 Cluster Administration 140
Tivoli Storage Resource Manager 369 cluster group 134
volume calculation 294 cluster IP address 131
backup reporting 41, 250, 287, 321 cluster name 126, 132, 134
backup storage requirements 324 cluster service 132
backup storage requirements reporting 291 database clustered instance 137
baroc file 30, 413, 415 failover 135, 137
batch reporting 345, 351 HCL 125
batch reports 360 heartbeat 124
Business Continuance 3, 15 installation 124
business intelligence reporting 433 internal cluster communication 130
network connections 128
shared disk 124, 127
C user ID 127, 132
capacity reporting 40, 186, 250, 263, 265 computer uptime 262, 319
CDE 101 Constraint 50, 54, 200, 224–225, 268, 274
CDW 445 Constraint violation report 268
See central data warehouse context name 120
certificates 153 Control server 433
Chargeback 23, 26, 40, 42, 249 cross device management 19
chargeback 42, 364–365 CSV 360
CIM 17, 145 CSV output 38, 248, 360
agent 20, 145 customized reporting 345
device provider 145
discovery 145
messages 145 D
object manager 20 dashboard 33
Object Manager see CIM/OM data archiving 12
profiles 18 data growth 3, 6, 13, 21


data management 3 online backup 376, 385
data mart 433 restore 137, 392, 399
data mining 433 rollforward 394
Data Warehouse Pack 433 DB2 commands
database ALTER TABLESPACE 74
Alert 235 db2adutl 386
application servers 24 db2icrt 134
asset reporting 36, 232, 256 db2mscs 133–134
availability 242 db2rbind 404
backup expiration 373 list applications 383
batch reporting 356 reorg 403
capacity reporting 265 reorgchk 402–403
chained rows 243 ROLLFORWARD 394
chargeback 365 runstats 401
clustering 133 DB2 UDB 29, 70, 111
connectivity 50 db2adutl 378
growth 26 default profiles 180–181
instance 113 device discovery 155
Instance Alert 235 device provider 145
Instance Quota 242 DFSMS 10, 14
monitoring 230 direct-attached storage 15
policy management 241 Disaster Recovery 15, 396
port 113 discovery 49–50, 298
Quota 241–242 disk
Quota violation reporting 282 allocated space 34
recovery 387 capacity 252, 263
Scan 259 costs 8
schema 74 mirroring 8
space usage report 347 RAID 8
Storage Resource Management 26 replication 8
storage utilization 26 utilization 8, 30
system reports 347 Distribution Status console 466
Table Alert 240 DMTF 17
tablespace 74 DNS 61, 145
Tivoli Storage Resource Manager 53 dsm.opt 295
trend reporting 37 dsmapipw 377
usage reporting 266 DTMF 17
usage violation report 347 duplicate files 8, 12
used table extents 243
user specific reporting 350
utilization 242 E
database instance storage report 328 element managers 16
database LUN assignment 331 Email 35, 176, 192
database size report 329 enable TEC events 428
database storage usage 327 engine 486
DB2 28, 53, 59, 63, 70, 94, 123, 133, 230, 370, 469 Enterprise Directory Query 458, 483
administrator id 95, 133 ESS 40, 145, 147, 250
archive log 378 attached hosts report 318
backup 137, 373, 382 automatic provisioning 30
Client Configuration Assistant 439 CIM/OM 20, 30, 54, 298
cluster installation 133 CIM/OM installation 148
clustered instance 133, 137 CIM/OM supported platforms 146
clustering 133 CLI 147
connection information 73 filesystem extension 211
container directory 74 Logical Sub System 204, 217, 505
Control Center 70, 135, 137, 455 LUN provisioning 54–55, 200–201, 203, 211
database maintenance 401 LUN reporting 55
JDBC driver 73 provisioning 54
LOGRETAIN 376 reporting 297–298, 316, 318
offline backup 382 SDD 211
Specialist 217


storage subsystem reporting 54 historical reporting 39
subsystem reporting 27, 30 hot link 361
Tivoli Storage Resource Manager Probe 298 HSM. See Hierarchical Space Management
used and free storage report 316 HTML 248, 360
ESS CIM/OM 153, 155 HTML output 38, 360
add managed devices 150 HTTP 19
add users 150 HTTPS 54, 155
communication port 154
serious reporting 153
upgrading 151 I
ESS CIM/OM commands IANA 75
address 150 IBM Directory 483
adduser 150 IBM Storage Management solutions 16
mkcertificate 153 IBM Tivoli Configuration Manager see Tivoli Configuration
verifyconfig 150 Manager
Ethernet 124 IBM Tivoli Enterprise Console see TEC
ETL programs 432 IBM Tivoli Monitoring see Tivoli Monitoring
Event 418 IBM Tivoli Storage Area Network Manager. See Tivoli
event manager 190 SAN Manager
IBM Tivoli Storage Manager. See Tivoli Storage Manager
IBM Tivoli Storage Resource Manager for Chargeback.
F See Tivoli Storage Resource Manager for Chargeback
FAT 182 IBM Tivoli Storage Resource Manager for Databases.
files See Tivoli Storage Resource Manager for Databases
at risk 181 IBM Tivoli Storage Resource Manager. See Tivoli Storage
filtering 182 Resource Manager
forbidden 269 IBM TotalStorage Enterprise Storage Server see ESS
modified since backup 289–290 ICMP 35, 174, 262
most at risk 37, 287 IDE 195
obsolete 181, 274 IIS 362
orphaned 181, 274 incremental backup planning 324
statistics 37 inode 197
filesystem 13 Interbase 30
automatic extension 27 interoperability 16
extension 29 inventory 458
Quota 222 Inventory Profile 464
filesystem capacity 34, 50, 263 Inventory Signature files 463
filesystem extension 27, 29, 54, 200–201 invoices 42
Alert 205
log only 203
filesystem utiliization 201 J
filesystems Java 28, 49, 68, 80–81, 413, 418
NAS 53 JDBC 70, 73, 79, 113, 142
forecasting 21, 24, 31
free space 34–35 L
LDAP 116, 483
G lightweight 28
graphical data 6 Linux 89, 91
group 165 backup 379
growth Load 432
data 3, 6, 13, 21 logging 203
Logical Sub System 204, 505
look and feel 101
H Lotus
HACMP 62 1-2-3 360
HCL 125 LSS 217
heterogeneity 5 LUN 12, 124
Hierarchical Space Management 371 LUN modeling 204
high availability 60–62, 142 LUN provisioning 54–55, 200–201, 203, 211
historical data 54 LUN reporting 55

Index 511

M P
mainframe Parametric Services monitor 487
Storage Resource Management 4 people costs 13
manual storage management 12 PERL 229
measuring storage resources 5 Ping 35, 40, 49, 121, 174, 248, 250, 262
Microsoft platform administration 14
Excel 360 policy based automation 4
Internet Information Server 81, 362 policy management 200
Microsoft Active Directory 483 pre-defined views 38
Microsoft Cluster Services 61 Probe 27–28, 36, 38, 40–41, 49, 78, 146, 177, 186, 194,
modified since backup files 289–290 232, 248, 250, 262, 297–298
MOF 18 Profile 37, 180, 187, 219, 276, 287, 333, 364
monitoring 49, 160 profile manager 487
monitoring storage 23 profile overview 486
most at risk files 37, 287 progressive incremental backup 293
Motif 101 Prolog 412
MSCS 61, 123 provisioning 54
proxy model 20

N
NAS 24–25, 28, 49, 52–53, 55–57, 76, 172 Q
exported filesystems 53 Quorum disk 127
login id 76, 110–111 Quota 50, 115, 180, 200, 218, 250, 268
password 76 violation report 276
Quota 200
SNMP 76
Storage Resource Management 25, 116 R
native software repository 463 RDBMS 27
NDS 53, 58, 91, 116–117, 119–120 Redbooks Web site 508
NetView 190 Contact us xxviii
event forwarding to TEC 427 replication solutions 16
NetWare 28, 49, 52–53, 58, 91, 109, 117, 172 reporting 38, 48
login 119 assets 40, 250, 252
Storage Resource Management 25 availability 40, 174, 250, 262
Network Appliance backup 41, 250
quota 223 backup storage requirements 291
Network Attached Storage. See NAS backups 287
network discovery 49 batch 345, 351, 360
non-Tivoli applications 432 by userID 41, 345
NTFS 124 capacity 40, 186, 250, 263
computer uptime 319
Constraint violation 274
O customized 345
object-oriented 18 database assets 256
obsolete files 8, 181, 274 database batch 356
ODBC 439 database capacity 265
offline backup 382 database Quota violations 282
OLAP database space usage 347
analysis 433 database usage 266
online backup 385 disk capacity 263
Oracle 29, 53, 61, 70, 74, 92, 111, 142, 230, 259, 370 filesystem capacity 263
archive log 235 owned by a username 348
Database Configuration Assistant 142 Quota violation 276
JDBC driver 114, 142 saved reports 349
regular administration 242 scheduling 345, 360
SID 143 storage capacity 263, 346
orphaned files 181, 274 storage subsystems 40, 250
out-of-space condition 31 top 10 reports 316
uptime 319
usage 40, 182, 250, 266
usage violation 40, 250, 268


wasted space 250 stale files 12
Web publishing 361 standard reporting 251
Web site 41 standards organizations 17
reporting categories 249 standby server 60
Tivoli Storage Resource Manager 249 static IP address 124
reports storage
HTML output 360 administration 14
resetarchiveattribute 292, 295 asset discovery 23, 36, 49
resource accounting 364 asset reporting 178
resource model 486 capacity 7, 40, 50, 263, 346
RI 433 Chargeback 26
RIM 467 consolidation 7
ROI 31 consumption 49
Rule Base 412–413 costs 8, 22, 31
forecasting 8, 21, 24, 31
growth 6, 31, 39–40
S infrastructure 6, 24
sample script 229 inventory 49
SAN 7, 15, 61 management standards 16
Scan 27–28, 37–38, 41, 49, 53–54, 75, 90, 106, 161, monitoring 23, 25, 160
165, 180, 185–186, 198, 248, 259, 274, 276, 337 reporting 38
Scan job log 260 return on investment 31
scanned data 6 standards organizations 17
scheduled reports 249 unused space 26
scheduled tasks 35 usage trends 37, 49
scheduler 102 utilization 8, 23, 26, 30, 181
scheduling 50–51, 360 virtualization 16
scripts 12, 27, 50–51, 75 Storage Area Network. See SAN
SCSI 195 storage management
SDD 211 costs 3, 31
server growth 7 environments 5
shared storage 62–63 functions 14
SLP 54, 145 issues 6, 8
SMI 17–18 people costs 13
SMIS 20 storage management standards 16
architecture 19 storage reports 23
discovery 19 Storage Resource Management 3, 8, 10, 53
proxy model 20 definition 4
SMTP 192 justification 30
SNIA 17–18, 21 ROI 31
SNMP 35, 56–57, 76, 172, 208 storage resources
port 114 measuring 5
trap 42, 176, 190, 355 Storage Subsystems reporting 40, 250, 297
socket 413 Subsystem Device Driver 211
software deployment 458 Sybase 29, 53, 70, 92, 111, 230, 370
software distribution 470 JDBC driver 114
software distribution profile 478 system availability 49
software inventory 458 system reports 347
Solaris 57
spreadsheets 360
SQL-Server 28–29, 53, 59, 70, 74, 78, 92, 111, 230, 258, T
370, 404 Table 258–259
administrator id 79 tablespace 74
backup 404 TEC 115, 208, 213, 412, 491
Enterprise Console 407 Assign Event Group 422
restore 406 baroc file 30, 413, 415
transaction log 238 class definition file 413
SRM compile rule base 416
standards 16 Console 413
SRM. See Storage Resource Management Constraint 420
staffing growth 7 Event Console 418

Index 513

Event Filters 418 Tivoli Storage Manage
event format 426 resetarchiveattribute 292
Event Groups 418 Tivoli Storage Manager 16, 229, 235, 287, 295, 371, 433
event processing 412 API 371
events from Tivoli Storage Resource Manager 427 archive bit 287
import class definitions 414–415 backup reporting 295
load rule base 417 backup volume prediction 294
RIM 412 Backup/Archive client 374
Rule Base 412–414 client options file 295, 377, 396
stop or start event server 417 Constraint violation report 268
Test SQL 421 copy group 373
TEC commnds dsm.opt 295, 377
wtdumprl 414 management class 373
tec_dispatch 412 nodename 375
tec_reception 412 policy domain 373
tec_rule 412 progressive incremental backup 293
tec_server 412 resetarchiveattribute 295
tec_task 412 RETEXTRA 374
tec_ui_server 413 RETONLY 374
Tivoli Configuration Manager 414, 458 VERDELETED 374
create Profile Manager 460 VEREXISTS 374
Distribution Status console 466 Tivoli Storage Manager capabilities
inventory 459 Backup-Restore 251
Inventory Profile 464 Disaster preparation and recovery 399
Inventory Signature files 463 Tivoli Storage Manager commands
software distribution 470 db2adutl 378
software distribution profile 478 dsmapipw 377
Web interface 458 QUERY NODE 375
Tivoli Desktop 459, 466, 478, 487 Tivoli Storage Manager for Databases 405
Tivoli Distributed Monitoring 191 Tivoli Storage Resource Manager 16, 23, 25–26, 62,
Tivoli Enterprise Console 176 266, 274, 360, 428, 433
Tivoli Enterprise Console see TEC ad hoc jobs 162
Tivoli Enterprise Data Warehouse 414, 432–433 administration 99, 102
Administration 445 administration group 98
configuration 444 administration GUI 81
data mart 432 administrative tasks 98
database 436 Agent 24, 26–27, 32, 48, 50, 52, 91, 100, 102
ETL processes 433 Agent administration 103
ETL programs 432 Agent automatic upgrade 107
ODBC 439 Agent auto-start 93
source applications 432 Agent backup 379
Subject Areas 445 Agent configuration file 107
Warehouse Packs 432 Agent details 104
Warehouse Schemas 445 Agent health 107
Warehouse Sources 445 Agent id 91
Warehouse Targets 445 Agent installation 89, 91
Tivoli Enterprise Framework 413 Agent license 109
Tivoli Light Client Framework 414 Agent log 106
Tivoli Managed Region 493 Agent platforms 29, 68
Tivoli Management Framework 414 Agent Port 90
Tivoli Monitoring 414, 486 Agent port 75, 92, 104
Parametric Services monitor 487 Agent quick installation 92
profile manager 487 Agent restore 387
resource model 486 Agent shutdown 107
TEC events 491 Agent statistics 34
wdmlseng command 493 Agent status 32, 103
Tivoli Monitoring for Databases 242 Agent tasks 52
Tivoli NetView 190 agent upgrade 96
Tivoli SAN Manager 16 Alert 23, 25, 27, 35, 41, 50–51, 101, 119, 173, 176,
Tivoli Service Level Advisor 433 189, 203, 205, 208, 227, 272, 428–429


Alert Disposition 114, 176 database id 73
Alert log 42, 115, 176, 191, 198, 276, 278 database maintenance 401
alerting 25 database platforms 28
allocated disk space 34 database port 79
apply maintenance 93 database repository 24, 48, 50, 72–73, 78, 101, 248
architecture 24, 48 database restore 392, 399
archive bit 295 database schema 74
asset reporting 36, 40, 178, 250, 252 database selection 73
at risk files 181 database size 53
automatic filesystem extension 27, 29 database tablespace 74
automatic provisioning 30 default profiles 180–181
availability reporting 35, 174, 250, 262 default Web page 85
backup 369 define Alert 193
backup reporting 41, 250, 287, 321 deleted Agent history 121–122
backup storage requirements 291, 324 deployment architecture 47
backup volume prediction 294 deployment considerations 53
baroc file 413, 415 deployment scenarios 59
batch reports 51, 249, 345, 351, 360 destination directory 77
biggest users 35 direct-connect Client 28, 48, 50
broadcast 103 Directory Alert 198
browser interface 24, 26, 28, 49, 84 Directory Group 166, 187, 255
capacity reporting 40, 186, 250, 263 directory monitoring 255
Chargeback 40, 42 Disaster Recovery 396
chargeback 42, 364 discovery 23, 27, 35, 49–50, 56, 117, 172
CIM reporting 146 discovery scheduling 172
CIM/OM 54, 145 disk capacity 263
CIM/OM discovery 155 email notification 115, 176, 192
CIM/OM registration 153 Enterprise-wide Summary 34
CIMS 42 ESS discovery 155
class definition file 413 ESS reporting 297–298, 316, 318
Client 26, 28 ESS subsystem reporting 27, 30
Cloudscape 30, 80 event forwarding 428
clustered database 133 event forwarding to TEC 427
clustered installation 135–136 Express Edition 25
clustering 61, 123 file statistics 37, 49
co-existence 53 filer logins 110
components 26 files filter 182
Computer Alert 194 Filesystem Alert 197
Computer Group 163, 196 filesystem capacity 34, 263
Computer Quota 222 filesystem extension 54, 200–201, 211
Computer Uptime 319 filesystem extension logging 203
computer uptime 319 filesystem free space 35
configuration 101, 107, 119 Filesystem Group 165
configuration file 98, 107, 138, 145, 370 Filesystem Quota 222
connection information 73 filesystem used space 34
Constraint 50, 54, 200, 224–225, 268, 274 forbidden file 269
Constraint Violation report 274 free space 34
create Group 163 functions 31
create Probe 178 graphical reporting 275
create Quota 222 Group 162
CSV output 38, 248, 360 Group definition 167
customized reporting 345 GUI client 24, 26, 81, 99, 102
Cycle Panels 34 GUI client installation 87
dashboard 33, 102 GUID 434
data retention 120–121 help 102
database 30, 53, 67, 370 high availability 60–62
database alias 73 historical data 54
database asset reporting 256 historical reporting 39
database backup 382 History Aggregation 118
database clustering 133 HTML output 38, 248, 356, 360

Index 515

Import Class Definitions 415 products 25
install Warehouse Pack 435 Profile 37, 162, 180, 187, 219, 276, 287, 333, 364
installation 67, 143 quick installation 92
installation directory 77, 83, 89, 91–92, 136, 145 Quota 50, 115, 180, 200, 218, 250, 268
interactive reporting 248 Quota scheduling 221
interface look and feel 101 Quota violation report 276
inventory 49 read-only access 99
Inventory Signature files 463 remote access 81
invoices 42 remote administration 81
JDBC driver 73 remote database 53, 59, 70, 142, 145
job output 162 remote execution 27
job scheduling 188 report scheduling 345, 360
job status 162 reporting 23, 25, 27, 38, 48, 247
jobs 105 Reporting Tab 101
license key 72 reports on the Web 361
licensing 26, 53, 71, 89, 108 repository 24, 27–28, 48, 50, 73, 78, 101, 248
local database 59 repository database 53
log retention 115 retention period 120–121
logging 103, 106, 115 roles 49
login 98 sample script 229
logon properties 138 sample scripts 497
LUN modeling 204 saved reports 349
LUN provisioning 200–201, 203, 211 scalability 53, 59
mail port 115 Scan 27, 37–38, 41, 49, 53–54, 75, 90, 106, 161,
maintenance 93 180, 185–186, 198, 248, 274, 276, 337
Managed Devices 26 Scan job log 260
Managed Systems 48 scanned files 54
maximum report size 39 scheduled actions 229
modified since backup files 289–290 scheduled jobs 27, 35, 48, 50–51, 105, 162
monitored directories 255 scheduled reports 48, 249
monitored server summary 35 scheduler 102
monitoring 24–25, 49, 160 script 41, 50–51, 75, 176, 192, 200
monitoring services 490 script parameters 195, 228
most at risk files 37, 287 scripts 145
MSCS 123 security 98–99
My Reports 248, 345 security levels 29
NAS 25, 53, 55–57, 76, 172, 200 Server 24, 26–27, 32, 48–49, 102
NAS probe 116 Server backup 381
native client 24, 26 server configuration file 98
navigation 101 Server installation 69
NDS 116, 119 Server log 103
NetWare 53, 58, 91, 109, 172 Server name 75
NetWare login 119 Server platforms 28, 68
NetWare reporting 251 Server port 75, 88, 90, 92
Network Appliance Quota 223 Server restore 390
network discovery 49 Server shutdown 103
Network Quota 218 Server status 102
obsolete files 181, 274 server.config 138
orphaned files 181 service 73, 100, 102, 136, 138
OS User Group Group 171, 218 services monitoring 490
OS User Groups 41 shared database 62
overview 24 shared disk 124
Panel Retention 101 shutdown 103, 107
Ping 35, 40, 49, 121, 174, 248, 250, 262 SNMP 208
policy management 200 software distribution 470
ports 75, 79, 88, 90, 92 space requirements 77, 89, 91
pre-defined reports 248 standard reporting 251
Probe 27, 36, 38, 40–41, 49, 78, 146, 177, 186, 194, standby server 60
248, 250, 262, 297–298 storage inventory 49
PROBE_ME 93 storage statistics 160


Storage Subsystem Reporting 40, 250, 316, 318 Databases-Tablespaces Groups 231
summary reporting 39 Database-Tablespace Alert 237
supported platforms 28, 67 Groups 231
system availability 49 Instance Alert 235
system id 73 Instance Quota 242, 282
System Reports 345 licensing 111, 233
system-wide view 254 monitoring 230
TEC configuration 115 My Reports 345
TEC event 208, 213 Network Quota 241
TEC event format 426 policy management 241
tool bar 102, 259 Probe 232
top 10 reports 316 Profile 233
trend reporting 37 Quota 241
Triggered Action 41, 52, 190, 195 Quota violations 282
Triggering condition 195, 197 RDBMS Login 112
UNIX Agent 91 Scan 112, 234, 259
UNIX Server 89 script 241–242
unmanaged list 49 script parameters 235
unmanaged systems 50, 57 storage usage 327
unreachable 103 supported platforms 29
Unreachable Agent 93 system reports 347
upgrade agents 96 Table Alert 240
UPGRADE_AGENTS 95 Table Group 232, 240, 257–258
upgrading 93 trend reporting 37
uptime 105 usage reporting 266
uptime reporting 262, 319 User Group 232
usage reporting 40, 182, 250 user specific reports 350
usage violation reporting 250, 268 top 10 reports 316
User Group 169 transactions 6
user names 116 Transform 432
user preferences 101 trend reporting 37
user space summary 35 Triggered Action 41, 52
username reporting 41, 345 truststore 153
view log 103, 106 TSM. See Tivoli Storage Manager
Warehouse Pack 434 Types of ETLs
Warehouse Pack prerequisites 435 Central Data Warehouse 432
wasted space report 250 data mart 432
Web access 81
Web Connect Clients 49–50
Web reporting 41 U
Windows Agent 89 UNIX 57
WWW server 27, 48 automount 57
Tivoli Storage Resource Manager Express Edition 25 inode 197
Tivoli Storage Resource Manager for Chargeback 26, password file 116
42, 100, 249, 364 Storage Resource Management 4, 25
Tivoli Storage Resource Manager for Databases 36, 100 unmanaged storage 6
Alert 235 unreachable agent 93
Alert log 239–240 unused files 8
asset reporting 36, 232, 256 uptime 262, 319
availability check 242 usage reporting 40, 182, 250, 266
batch reports 356 usage violation reporting 250, 268
capacity reporting 265 user space summary 35
Computer Groups 231, 265 usiness Intelligence tools 469
configuration 108, 121 UTC 394
create Group 231 utilization 201
create Table Group 259 utilization rates 8
database instance report 328
database LUN reporting 331 V
Database Quota 242 Vendor Identification Number 56–57
database Scan 259 virtual directory 82

Index 517

virtualization 16
Visio 13
volume group 54

W
warehouse pack 432
wasted space 21
wasted space report 250
WBEM 17
wdmlseng 493
Web browser 24, 26, 49, 361
Web Health Console 486
Web reporting 41
Windows 56
archive bit 287, 292, 295
backup 381
clustering 61, 123
domain 49–50, 56
Domain Controller 172
domain users 99
event log 35, 176, 191
MSCS 123
Service Pack 133
Storage Resource Management 4, 25
workgroup 50
Windows 2000
LDAP 116
restore 396
System Objects 397–398
WWW Server 27


IBM Tivoli Storage Resource Manager:
(1.0” spine)
0.875”<->1.498”
460 <-> 788 pages

Back cover ®

IBM Tivoli Storage
Resource Manager:
Take control of Storage growth continues to accelerate, and the cost of disk can
approach 80% of total system hardware costs. Yet, the storage in
INTERNATIONAL
storage resources in
most businesses is typically only about 50% used. How can you TECHNICAL
your enterprise
take control of your storage assets to render utilization more SUPPORT
Receive early alerts of efficient, and make the most of your storage dollars? ORGANIZATION
storage problems IBM Tivoli Storage Resource Manager helps you discover,
monitor, and create enterprise policies for your filesystems and
databases. You will find out where all your storage is going, and
New! ESS reporting be able to act intelligently on this information. Application
and Tivoli integration BUILDING TECHNICAL
availability is improved because you will have early warnings INFORMATION BASED ON
when filesystems are running out of space. If you are thinking PRACTICAL EXPERIENCE
about server consolidation, you can use IBM Tivoli Storage
Resource Manager to help efficiently utilize your accumulated IBM Redbooks are developed
storage resources. by the IBM International
This IBM Redbook shows how to install, configure, and protect Technical Support
the IBM Tivoli Storage Resource Manager environment; how to Organization. Experts from
IBM, Customers and Partners
create policies; how to define automated actions like scripts or from around the world create
SNMP events when policies are violated; and how to produce timely technical information
detailed, meaningful storage reports. This book is intended for based on realistic scenarios.
those who want to learn more about IBM Tivoli Storage Resource Specific recommendations
Manager, and for those who are about to implement it. are provided to help you
implement IT solutions more
effectively in your
The second edition of this redbook is updated for IBM Tivoli environment.
Storage Resource Manager Version 1.2.

For more information:
ibm.com/redbooks

SG24-6886-01 ISBN 073849979X

Ibm tivoli storage resource manager a practical introduction sg246886

More Related Content

What's hot (16)

Viewers also liked (8)

Similar to Ibm tivoli storage resource manager a practical introduction sg246886 (20)

More from Banking at Ho Chi Minh city (20)

Recently uploaded (20)

Ibm tivoli storage resource manager a practical introduction sg246886