Ibm tivoli storage resource manager a practical introduction sg246886
Upcoming SlideShare
Loading in...5
×
 

Ibm tivoli storage resource manager a practical introduction sg246886

on

  • 1,327 views

 

Statistics

Views

Total Views
1,327
Views on SlideShare
1,327
Embed Views
0

Actions

Likes
0
Downloads
7
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Ibm tivoli storage resource manager a practical introduction sg246886 Ibm tivoli storage resource manager a practical introduction sg246886 Document Transcript

    • Front coverIBM Tivoli StorageResource Manager:A Practical IntroductionTake control of storage resources inyour enterpriseReceive early alerts of storageproblemsNew! ESS reporting and Tivoliintegration Charlotte Brooks Michel Baus Michael Benanti Ivo Gomilsek Urs Moseribm.com/redbooks
    • International Technical Support OrganizationIBM Tivoli Storage Resource Manager: A PracticalIntroductionAugust 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 StorageResource Manager for Databases (product number 5698-SRD), IBM Tivoli Storage Resource Manager forChargeback (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 ScheduleContract 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxixPart 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Part 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 . . . . . . . 62Part 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 . . . . . . . . . . . . . . . . 137iv 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Part 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 . . . . . . . 408vi 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487Part 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509viii 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109x IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 4-60 Licensing Novell NetWare Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1104-61 Licenses for Tivoli Storage Resource Manager for NAS . . . . . . . . . . . . . . . . . . . . . 1104-62 NAS devices logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114-63 Login definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114-64 Licenses for Tivoli Storage Resource Manager for Databases . . . . . . . . . . . . . . . . 1124-65 RDBMS Logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1134-66 Defining RDBMS Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1134-67 Alert Disposition screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144-68 Log File Retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1154-69 Filters for Quota Email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1164-70 Agent selection for NAS and NDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1174-71 Defining the NAS Agent for Scan/Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1184-72 Defining the Novell NetWare Agent for Scan/Probe . . . . . . . . . . . . . . . . . . . . . . . . 1184-73 History Aggregator definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194-74 NetWare Tree Login Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194-75 Novell Tree Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204-76 History retention: Tivoli Storage Resource Manager . . . . . . . . . . . . . . . . . . . . . . . . 1204-77 Removed Resource Retention: Tivoli Storage Resource Manager . . . . . . . . . . . . . 1214-78 History retention: Tivoli Storage Resource Manager for Databases . . . . . . . . . . . . 1224-79 Removed Resource Retention: Tivoli Storage Resource Manager for Databases . 1234-80 Cluster installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1244-81 Cluster Wizard Welcome panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1254-82 HCL requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1254-83 Node selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1264-84 Cluster name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1264-85 Cluster user ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1274-86 Shared disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1274-87 Quorum disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284-88 Network setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284-89 Private network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1294-90 Public network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1294-91 Network priority for internal cluster communication . . . . . . . . . . . . . . . . . . . . . . . . . 1304-92 Cluster IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1314-93 Joining the cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1314-94 Joining cluster name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1324-95 Account for running the service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1324-96 Running cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1334-97 DB2 clustered instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1354-98 Database on first node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1364-99 Service mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1364-100 Database on second node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1374-101 Password change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1394-102 Resource dependences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1404-103 Server service name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1404-104 Agent service name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1414-105 Cluster view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1414-106 Starting Oracle Database Configuration Assistant. . . . . . . . . . . . . . . . . . . . . . . . . . 1424-107 Selecting the database name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1434-108 Database connection information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1434-109 Database information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1444-110 Setting services to manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1444-111 CIM/OM for ESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1464-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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190xii IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 5-41 Alert - SNMP trap sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1905-42 Alert - Logged alerts sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1915-43 Alert - Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1915-44 Alerts - Windows Event viewer sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1925-45 Alerts - Mail sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1925-46 OS Alerting tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1935-47 Filesystem alert creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1945-48 Computer alerts - Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1955-49 Computer alerts - RAM decreased script parameters . . . . . . . . . . . . . . . . . . . . . . . 1965-50 Computer alerts - Disk not found script parameters . . . . . . . . . . . . . . . . . . . . . . . . 1965-51 Computer alerts - Computers tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1965-52 Filesystem Alerts - Alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1975-53 Filesystem alert - Freespace default mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1985-54 Alerts log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1995-55 Detailed Alert information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2005-56 Filesystem Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2015-57 Filesystem tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2025-58 Extension tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2025-59 LUN provisioning tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2045-60 When to Enforce Policy tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2055-61 Alert tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2065-62 Save filesystem changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2075-63 Selected filesystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2085-64 Extension parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2085-65 Alert definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2095-66 Rule for /opt extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2095-67 Successful extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2105-68 Extension log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2105-69 /essfs1 filesystem expansion definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2125-70 Extension parameters for /essfs1 FS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2125-71 Provisioning parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2135-72 Filesystem extension on /essfs1 filesystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2145-73 LUN provisioning for /essfs1 filesystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2165-74 ESS LUNs for filesystem expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2175-75 Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2185-76 User Network Quotas - Users tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2195-77 Profile with user summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2205-78 User Network Quotas - Filesystem tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2205-79 User Network Quotas - Alert tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2215-80 Computer Quota - Alerts log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2225-81 Filesystem Quota - Alerts log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2235-82 Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2245-83 Constraint - File Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2255-84 Constraint - Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2255-85 Constraints - Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2265-86 Constraints - File filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2275-87 Constraints - File filter changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2275-88 Constraints - Alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2285-89 Constraints - Script parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2285-90 Scheduled actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2295-91 Scheduled action - Script options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2305-92 Databases - Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2315-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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 282xiv IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 6-47 Create database Quota - Users tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2836-48 Create database Quota - Instances tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2836-49 Create a database Quota - When to Run tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2846-50 Create a database Quota - Alert tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2846-51 Create a database Quota - Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2856-52 Run the database Quota . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2856-53 DB Quota violation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2866-54 Database Quota violation report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2866-55 Backup Reporting options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2876-56 Files most at risk report - selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2886-57 Modified Files not backed up selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2896-58 Modified Files not backed up chart overall view . . . . . . . . . . . . . . . . . . . . . . . . . . . 2896-59 Files need backed up chart in detail view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2906-60 Files not backed up bar chart detail view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2906-61 Backup storage requirements per filesystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2916-62 Backup storage requirement per computer and per filesystem . . . . . . . . . . . . . . . . 2926-63 Incremental reporting per Node and Filesystem based on files. . . . . . . . . . . . . . . . 2936-64 Incremental Range Size select By Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2946-65 Incremental Range Sizes Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2956-66 Tivoli Storage Manager preference settings for archive attribute . . . . . . . . . . . . . . 2966-67 ESS Reporting capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2976-68 ESS reporting lab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2986-69 Creating ESS probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2996-70 ESS - When to probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2996-71 ESS - Alert tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3006-72 ESS - probe job status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3016-73 Probe job log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3016-74 Asset by storage subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3026-75 ESS disk group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3026-76 Disks in volume spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3036-77 Disk and LUN association with volume space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3046-78 Hot spare LUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3056-79 ESS all disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3066-80 ESS all LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3076-81 By Computer - Relate Computer to . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3086-82 By Computer - storage subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3086-83 By Computer - LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3096-84 By Computer - disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3096-85 By filesystem/logical volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3106-86 By filesystem/logical volumes - storage subsystem. . . . . . . . . . . . . . . . . . . . . . . . . 3106-87 By filesystem/logical volume - LUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3116-88 By filesystem/logical volume - Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3116-89 By Storage Subsytems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3126-90 By Storage subsystem - Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3126-91 By storage subsystem - filesystem/logical volume. . . . . . . . . . . . . . . . . . . . . . . . . . 3136-92 By LUNs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3136-93 By LUN - computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3146-94 By LUNS - filesystem/logical volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3146-95 Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3156-96 Disks - computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3156-97 Disks - filesystem/logical volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3166-98 ESS relation to computer selected by disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3176-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 . . . . . . . . . . . . . . . . . . . . . 351xvi IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 6-153 Create a Batch Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3526-154 Create a Batch Report - report selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3526-155 Create a Batch Report - selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3536-156 Create a Batch Report - options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3546-157 Create a Batch Report - when to report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3556-158 Create a Batch Report - saving the report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3566-159 Create a database Batch Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3576-160 Create a database Batch Report - Report tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3576-161 Create a database Batch Report - Options tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3586-162 Create a database Batch Report - When to Report tab . . . . . . . . . . . . . . . . . . . . . . 3596-163 Create a database Batch Report - save definition . . . . . . . . . . . . . . . . . . . . . . . . . . 3596-164 Monitored Tables by RDBMS Type batch report output . . . . . . . . . . . . . . . . . . . . . 3606-165 Batch Reports listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3616-166 MS Word created Web page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3626-167 Setting up a Virtual Directory within IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3636-168 Reports available from a Web browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3646-169 Chargeback parameter definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3656-170 Create the Chargeback Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3667-1 Tivoli Storage Resource Manager components. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3707-2 Tivoli Storage Resource Manager integration with Tivoli Storage Manager . . . . . . 3717-3 Backup environment tor Tivoli Storage Resource Manager . . . . . . . . . . . . . . . . . . 3737-4 Procedures used to backup Tivoli Storage Resource Manager. . . . . . . . . . . . . . . . 3797-5 Tivoli Storage Resource Manager restore procedures . . . . . . . . . . . . . . . . . . . . . . 3877-6 Agent is connected to the server after restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3897-7 IBM Tivoli Storage Manager restore interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3917-8 Restore completed successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3917-9 Agents successfully reconnected after restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3927-10 Server running again after database restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3957-11 Tivoli Storage Resource Manager Server Disaster Recovery procedures . . . . . . . 3967-12 Full system restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3977-13 Full system restore result. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3977-14 System Objects restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3987-15 System Objects restore results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3987-16 IBM Tivoli SRM interface after DR restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4007-17 DB2 Database maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4017-18 SQL-Server database backup start using the GUI. . . . . . . . . . . . . . . . . . . . . . . . . . 4057-19 SQL-Server database backup end using the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . 4057-20 SQL Server database restore started using the GUI . . . . . . . . . . . . . . . . . . . . . . . . 4067-21 SQL Server database restore finished using the GUI . . . . . . . . . . . . . . . . . . . . . . . 4078-1 TEC architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4138-2 Tivoli Lab environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4148-3 Active Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4158-4 Import Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4158-5 Import Class Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4168-6 Compile Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4178-7 Load Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4178-8 Restart TEC Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4188-9 TEC Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4198-10 TEC Console Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4198-11 Create Event Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4208-12 Create Filter in Event Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4208-13 Event Group Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4218-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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460xviii IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 10-3 Managed Resources for Inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46010-4 Policy Region Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46110-5 Profile Manager Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46110-6 Inventory Profile Global Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46210-7 Inventory Profile PC Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46310-8 Inventory Profile UNIX Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46410-9 Distribute Inventory Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46510-10 Distribute Inventory Profile dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46610-11 Distribution Status Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46710-12 Create Query Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46710-13 Edit Inventory Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46810-14 Output for IBM Tivoli Storage Resource Manager Query . . . . . . . . . . . . . . . . . . . . 46910-15 Output for IBM Query. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46910-16 Software Package Editor with new package ITSRM-Agent . . . . . . . . . . . . . . . . . . . 47010-17 Properties dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47110-18 Agent installation directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47110-19 Add an execute program action to the package . . . . . . . . . . . . . . . . . . . . . . . . . . . 47210-20 Install dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47210-21 Advanced tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47310-22 Remove dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47410-23 Advanced properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47510-24 Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47610-25 Add Directory dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47710-26 Descend Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47710-27 Ready-to-build software package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47810-28 Policy Region with Profile Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47810-29 Create Software Package Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47910-30 Profile Manager with Profiles and Subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47910-31 Import Software Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48010-32 Import and build a software package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48110-33 Install a software package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48210-34 Install Software Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48310-35 Remove a Software Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48411-1 IBM Tivoli Monitoring architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48611-2 Policy Region tonga-region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48711-3 Profile Manager PM_DM_ITSANM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48811-4 Create Monitoring Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48811-5 Add Parametric Services Model to Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48911-6 Edit Resource Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49011-7 Parameters of Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49111-8 Indications and actions of resource models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49211-9 TEC forwarding of events from Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49211-10 Profilemanager for Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49311-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
    • NoticesThis 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. Consultyour local IBM representative for information on the products and services currently available in your area. Anyreference 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 notinfringe any IBM intellectual property right may be used instead. However, it is the users responsibility toevaluate 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. Thefurnishing of this document does not give you any license to these patents. You can send license inquiries, inwriting, 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 areinconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "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 ofexpress 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 madeto the information herein; these changes will be incorporated in new editions of the publication. IBM may makeimprovements and/or changes in the product(s) and/or the program(s) described in this publication at any timewithout notice.Any references in this information to non-IBM Web sites are provided for convenience only and do not in anymanner serve as an endorsement of those Web sites. The materials at those Web sites are not part of thematerials 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 incurringany obligation to you.Information concerning non-IBM products was obtained from the suppliers of those products, their publishedannouncements or other publicly available sources. IBM has not tested those products and cannot confirm theaccuracy of performance, compatibility or any other claims related to non-IBM products. Questions on thecapabilities 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 themas 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 businessenterprise is entirely coincidental.COPYRIGHT LICENSE:This information contains sample application programs in source language, which illustrates programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programs inany form without payment to IBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operating platform for which the sampleprograms 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, anddistribute these sample programs in any form without payment to IBM for the purposes of developing, using,marketing, or distributing application programs conforming to IBMs application programming interfaces.© Copyright IBM Corp. 2003. All rights reserved. xxiii
    • TrademarksThe 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 UnitedStates, other countries, or both.Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in theUnited 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 ElectronicTransaction 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 redbookThis redbook was produced by a team of specialists from around the world working at the InternationalTechnical 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 Tivolixxvi 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 SloveniaBecome 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. Youll team with IBM technical professionals, Business Partners and/or customers. Your efforts will help increase product acceptance and customer satisfaction. As a bonus, youll 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-6099xxviii 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 1Part 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.© Copyright IBM Corp. 2003. All rights reserved. 3
    • 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 definitions1.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 companys business data. Computers and storage are now mission-critical.4 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Today, you need to manage storage to stay in business. You cannot manage what you cannotmeasure, and Storage Resource Management is a key tool for measuring and managingstorage resources.Open environments today are larger and the systems are much more heterogeneous than inthe 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 storage1.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.6 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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/redbooksFigure 1-3 Infrastructure growth issuesServer growthMajor companies have hundreds of large UNIX servers, and sometimes thousands ofMicrosoft Windows servers. They are deploying more servers every quarter, and most largecompanies have a large variety of different hardware and software platforms (often not bydesign) rather than standardizing on particular configurations.Staffing growthWhile we know that storage and data are growing rapidly, support staff numbers are not. Thisonly exacerbates the problem. An average corporate server may be supporting in the order of3 TB of data in the coming years, yet it is estimated that a typical systems administrator canmanage 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 andpowerful applications will be required to support this environment.Storage data growthAlthough 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 as150 TB of data to store installed within the next two years. Total storage reserves of 150 TB tohandle the growth in storage with storage is being consolidated into SANs (Storage AreaNetworks). However, SANs do not solve the underlying problems of mismanaged data and itsexplosive growth. SANs concentrate the storage, the data, and the problems, and emphasizethe need for management. Chapter 1. Introduction to Storage Resource Management 7
    • 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.8 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • If storage is growing at 100%, and companies are using only 25% or 50% of what they buy tohold real data, then companies are buying storage they do not need, because they cannotmanage 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 UNIXenvironment) show how the numbers can add up.Example 1-1 Storage costs in NT environmentA utility company in the Northeast has 150 NT servers with internal disk, with an averageof 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 lessexpensive than adding disks to a partially populated server, the client bought 6 disks perserver 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). Whiletrue, 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 ofprotection).2. 15 cents per MB is close enough to the cost of enterprise disk to justify investigatingstorage consolidation.Example 1-2 Same examples, using enterprise storageWe re-calculated the same example using enterprise storage.Typical efficiency (space used/space available) in enterprise FC SAN Storage is less than50%. (It is more that the rate for internal storage because more attention is paid toexpensive 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 Chapter 1. Introduction to Storage Resource Management 9
    • 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.10 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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/redbooksFigure 1-5 Predicted savings from managed storage versus unmanaged storageOne key piece of information is shown in Figure 1-4. By using SRM software to improve ourutilization, then, using existing storage, we can absorb 27 months of growth in the Windowsexample, or seven months of growth in the enterprise storage example - this represents asignificant cost benefit. Chapter 1. Introduction to Storage Resource Management 11
    • 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 cant manage it." Nick Allen, Vice President, Research Director, Gartner "Its not important how much storage you have, its how much managed storage you have. If you dont know what youve 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.12 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Looking forwardBased on various studies of estimated system and data growth, we proposed the followingprojection of the number of filesystems and amounts of storage that would have to bemanaged 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/redbooksFigure 1-7 Scope of the problem - total storage, total number of filesystemsIn this projection we used 100 GB for the size of the average UNIX host today, 25 GB for theaverage Windows host, and 150 TB of storage as a target for the total storage in the averagelarge company. We also made some assumptions as to the number of filesystems perUNIX/Windows host. We believe that this is a quite conservative projection. If you use largernumbers, then the numbers are even more daunting. Nonetheless, the projection illustratesthe point: by 2004, an average large company will be managing: 7,500 filesystems 150TBs of storage 3,750 serversHow 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 Chapter 1. Introduction to Storage Resource Management 13
    • 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 recovery14 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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). Chapter 1. Introduction to Storage Resource Management 15
    • 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 solutions1.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:16 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 standardsToday, there are at least 10 organizations involved in creating standards for storage, storagemanagement, SAN management, and interpretability. Figure 1-10 shows the keyorganizations involved in developing and promoting standards relating to storage, storagemanagement, and SAN management, and the relevant standards for which they areresponsible. 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 participationFigure 1-10 Storage standards organizations and their standardsKey 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) SpecificationCIM/WEB management modelCIM was developed as part of the Web-Based Enterprise Management (WBEM) initiative bythe Desktop Management Task Force (DMTF) to simplify management of distributed systems. Chapter 1. Introduction to Storage Resource Management 17
    • 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.18 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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/redbooksFigure 1-12 SMI SpecificationThe idea behind SMIS is to standardize the management interfaces so that managementapplications can utilize these and provide cross device management. This means that anewly 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 Chapter 1. Introduction to Storage Resource Management 19
    • 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 to20 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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.org1.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 Chapter 1. Introduction to Storage Resource Management 21
    • 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.22 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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© Copyright IBM Corp. 2003. All rights reserved. 23
    • 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 browser24 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 network2.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 IBM Tivoli Storage Resource Manager Express Edition 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 IBM Tivoli Storage Resource Manager 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 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 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.26 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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/redbooksFigure 2-3 Components of Tivoli Storage Resource ManagerTivoli Storage Resource Manager ServerThe 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 provisioningAn RDBMS (either locally or remote) manages the repository of data collected from theAgents, and the reporting and monitoring capabilities defined by the users.WWW ServerThe Web Server is optional, and handles communications to allow remote Web access to theServer. 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 managedsystem, and forwards it to the Manager to be stored in the database repository, and acted on Chapter 2. Introduction to IBM Tivoli Storage Resource Manager 27
    • 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.28 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 above2.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 Alerts2.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. Chapter 2. Introduction to IBM Tivoli Storage Resource Manager 29
    • 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 long30 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 2. Introduction to IBM Tivoli Storage Resource Manager 31
    • 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 functions2.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.32 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 2-5 Agent summaryFigure 2-6 shows the Tivoli Storage Resource Manager dashboard. This is the defaultright-hand pane display when you start Tivoli Storage Resource Manager and shows a quicksummary of the overall health of the storage environment. It can quickly show you potentialproblem areas for further investigation. Chapter 2. Introduction to IBM Tivoli Storage Resource Manager 33
    • 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.34 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 2. Introduction to IBM Tivoli Storage Resource Manager 35
    • 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.36 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 2. Introduction to IBM Tivoli Storage Resource Manager 37
    • 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 a38 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • lower-level report, where the administrator has focussed on a particular Agent, BANDA, tolook at a particular disk on a particular controller.Figure 2-11 Asset Report - BANDA assetsReports can be produced either system-wide or grouped into views, such as by computer, orOS 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 thatbusiness and technology administrators can manage an enterprise infrastructure. Or, you cansummarize information from a specific server - the flexibility and choice of configuration isentirely up to the administrator.You can report as at a point in time, or produce a historical report, showing storage growthtrends over time. Tivoli Storage Resource Manager reporting lets you track actual demand fordisk 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 ofthe number of files on the C drive on the Agent WISLA. Chapter 2. Introduction to IBM Tivoli Storage Resource Manager 39
    • 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 (defining40 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 Web2.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. Chapter 2. Introduction to IBM Tivoli Storage Resource Manager 41
    • 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.42 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Example 2-1 Chargeback Report based on disk usage by userTivoli SRM for ChargeBack page 1User Usage Invoice 24-Sep-02Administrator.hb Name SPACE COST (MB) 0.1042/MB 100 5 0.52 group total 5 0.52Tivoli SRM for ChargeBack page 2User Usage Invoice 24-Sep-02Tivoli.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 Chapter 2. Introduction to IBM Tivoli Storage Resource Manager 43
    • group total 46,008 4,793.97 Tivoli SRM for ChargeBack page 3 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 Manager44 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Part 2Part 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.© Copyright IBM Corp. 2003. All rights reserved. 45
    • 46 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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.© Copyright IBM Corp. 2003. All rights reserved. 47
    • 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.48 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Tivoli Storage Resource Manager Server 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.50 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 3. Deployment architecture 51
    • 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.52 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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: Chapter 3. Deployment architecture 53
    • 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.54 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 3. Deployment architecture 55
    • 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) Tivoli SRM Agent installed 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.56 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 Chapter 3. Deployment architecture 57
    • 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 Tivoli SRM Agent installed 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.58 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 3. Deployment architecture 59
    • 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.60 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 3. Deployment architecture 61
    • 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.62 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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/redbooksFigure 3-13 AIX cluster setupIn this installation, the IBM Tivoli Storage Resource Manager program files are installed onthe shared storage, so they are accessible from both servers. With such installation we alsomaintain the consistency of the configuration. Doing this automatically maintains theconsistency of the configuration. The database repository is installed on a Windows 2000server running IBM DB2 UDB Version 7.2. Chapter 3. Deployment architecture 63
    • 64 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Part 3Part 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.© Copyright IBM Corp. 2003. All rights reserved. 65
    • 66 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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.© Copyright IBM Corp. 2003. All rights reserved. 67
    • 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 platforms4.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.68 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 repository4.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 Server4.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.24.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.70 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 4. IBM Tivoli Storage Resource Manager installation 71
    • 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 service72 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • The installation program will create a system user ID which will be used for running the TivoliStorage Resource Manager Server service. Click OK to display the database selectionscreen, as in Figure 4-9.Figure 4-9 Selecting the database for the repositoryThe installation program will query the DB2 installation for existing databases and displaythem. 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 underDatabase Alias field. You also need to provide the database user name and password underConnection information. Because the manager is accessing the database using JDBC youneed 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 RepositoryCreation Parameters screen shown in Figure 4-10. Chapter 4. IBM Tivoli Storage Resource Manager installation 73
    • 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.74 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • After supplying all the necessary parameters click Next and you will see the parameterscreen similar to Figure 4-11.Figure 4-11 Server setupIn 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 screenshown in Figure 4-12. Chapter 4. IBM Tivoli Storage Resource Manager installation 75
    • 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.76 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 4-13 Space requirementsIn this screen you can choose the installation path for the Server code. Here you can also seethe required space for the installation, which can help you to select a directory location. If thedestination directory does not exist, you will be prompted for creation of it, after you clickNext. Finally, you will see the installation summary screen in Figure 4-14.Figure 4-14 Before copying filesAt this stage you can still decide to go back and change settings if necessary. Click Next tostart copying files.If you installed the Tivoli Storage Resource Manager repository in a DB2 UDB database, theCreate Service Account window is shown in Figure 4-15. The Tivoli Storage ResourceManager creates a new Service account and the Agent will use it when running probes andscans against DB2 databases on the current machine. Chapter 4. IBM Tivoli Storage Resource Manager installation 77
    • 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.78 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 4-17 Selecting Microsoft SQL ServerSelect MS SQL Server and click Next to continue. Figure 4-18 displays.Figure 4-18 Microsoft SQL-Server parametersType 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). Chapter 4. IBM Tivoli Storage Resource Manager installation 79
    • 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.80 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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). Chapter 4. IBM Tivoli Storage Resource Manager installation 81
    • 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).82 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 4-24 Defining the directory for Web access files5. 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 directory6. 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. Chapter 4. IBM Tivoli Storage Resource Manager installation 83
    • 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.84 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 4-28 Main administration GUI screenSetting the default Web pageYou can also set the default Web page for the directory where the Web files for Tivoli StorageResource Manager are located. This means you need only to type in the directory name asthe 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. Chapter 4. IBM Tivoli Storage Resource Manager installation 85
    • Figure 4-29 Opening properties for the tsrm Web directory The Properties page displays, shown in Figure 4-30. Figure 4-30 Tsrm properties86 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 4. IBM Tivoli Storage Resource Manager installation 87
    • 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.88 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 4. IBM Tivoli Storage Resource Manager installation 89
    • Figure 4-35 Agent install selection Select An Agent on this machine and click Next. You will see the Parameters screen, as shown in Figure 4-36. 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).90 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 theconnection to the Server. The Space Requirements screen will display, as shown inFigure 4-37.Figure 4-37 Space requirementsHere you can see the required space for installation and specify the installation directory. Ifthe directory does not exists you need to confirm its creation. Click Next, then confirm thesettings on the next screen. Select Next to start copying files. After the installation iscomplete, the Agent will automatically start.If you are installing on an Agent with a NetWare client, you will be prompted to create a localaccount for the Agent (as shown in Figure 4-38) before the Agent is started after installation.Figure 4-38 Novell logon ID creationThis account can only be created if you are logged into the Novell NDS with sufficientprivilege.UNIX AgentInstall the UNIX Agent by running ./setup.sh from the appropriate directory. Our example isa Linux Agent. If you execute the script without parameters, the help is displayed as shown inExample 4-1. Chapter 4. IBM Tivoli Storage Resource Manager installation 91
    • 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...92 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 4. IBM Tivoli Storage Resource Manager installation 93
    • 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.94 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 4-41 DB2 admin user ID and password4. 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 allthe Agents.If for any reason you need to force an upgrade of the Agents with the same version currentlyavailable, you need to create an empty file with the name UPGRADE_AGENTS in the Serverinstallation directory. For example, in Windows C:Program FilesTivoliTRSM This will forcean upgrade. Chapter 4. IBM Tivoli Storage Resource Manager installation 95
    • 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.96 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 4-44 Schedule agent upgradeUnder Options, (Figure 4-45) you can force a reinstall if the Agent is already on this level.Figure 4-45 Force upgrade on Agent Chapter 4. IBM Tivoli Storage Resource Manager installation 97
    • 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=298 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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). Chapter 4. IBM Tivoli Storage Resource Manager installation 99
    • 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 Systems100 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 4. IBM Tivoli Storage Resource Manager installation 101
    • 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:102 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 process4.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. Chapter 4. IBM Tivoli Storage Resource Manager installation 103
    • 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.104 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 4-53 Agent Details viewHere you can see details about the Agent (name of the Agent and Host, date and time when itwas started, uptime, disk space allocated to virtual memory size - VM, manufacturer and OSof the Agent system, number of jobs scheduled to run on the Agent). The Jobs screen isshown in Figure 4-54. Chapter 4. IBM Tivoli Storage Resource Manager installation 105
    • 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.106 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 4. IBM Tivoli Storage Resource Manager installation 107
    • 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.108 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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) toperform 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. Chapter 4. IBM Tivoli Storage Resource Manager installation 109
    • 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.110 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 4. IBM Tivoli Storage Resource Manager installation 111
    • 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.112 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 Chapter 4. IBM Tivoli Storage Resource Manager installation 113
    • 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)114 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 RetentionThis option defines how long to keep the log files, as shown in Figure 4-68.Figure 4-68 Log File RetentionThe 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. Chapter 4. IBM Tivoli Storage Resource Manager installation 115
    • 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 shown in Figure 4-70.116 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 4-70 Agent selection for NAS and NDSThe following information is displayed: Licensed NetWare servers NetWare volumes discovered by discovery jobs Discovered NAS filesystemsThis information is gathered during the discovery process on the Agents accessing NASdevices and Novell NetWare servers.The Agent systems with access to the NAS or NetWare volumes and filesystems will bedisplayed 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) andclick Set agent per row or Set agents for all selected rows. You will see the window shownin Figure 4-71 for NAS Agents, or the window shown in Figure 4-72 for the Novell NetWareAgents. Chapter 4. IBM Tivoli Storage Resource Manager installation 117
    • 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.118 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 4-73 History Aggregator definitionsTwo 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 SRMUnder IBM Tivoli SRM settings you can do the following:NetWare Tree LoginsAssign the login ID and password for each Novell Directory Services (NDS) tree discoveredby Tivoli Storage Resource Manager Agents. The screen is shown in Figure 4-74.Figure 4-74 NetWare Tree Login AdministrationSelect the desired Tree Name and click Edit, as shown in Figure 4-75. Chapter 4. IBM Tivoli Storage Resource Manager installation 119
    • 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 Manager120 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • The retention period is specified individually for the following data types: Directories Filesystems Pings Computer uptime DisksSelecting No History turns off history keeping.Removed Resource RetentionThis panel (Figure 4-77) specifies how long to keep information that is related to entities thathave been removed or deleted from an Agent.Figure 4-77 Removed Resource Retention: Tivoli Storage Resource ManagerYou can define how long to retain information for these removed entities: Directories Filesystems DisksConfiguration: IBM Tivoli SRM for DatabasesUnder the IBM Tivoli SRM for Databases settings, you can do the following:Resource History RetentionThis panel (Figure 4-78) defines the period for which collected historical data on databaseswill be kept. Chapter 4. IBM Tivoli Storage Resource Manager installation 121
    • 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.122 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 Tables4.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 Chapter 4. IBM Tivoli Storage Resource Manager installation 123
    • 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 (Windows 2000 Adv. Server) 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 (Windows 2000 Adv. Server) MSCS IBM DB2 7.2 fp 7 IBM Tivoli SRM 1.1 ibm.com/redbooks Figure 4-80 Cluster installation4.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.124 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 panel9. Click Next. The Hardware Configuration screen displays (Figure 4-82).Figure 4-82 HCL requirements10.Accept the HCL (Hardware Compatibility List) requirements. Figure 4-83 displays. Chapter 4. IBM Tivoli Storage Resource Manager installation 125
    • 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).126 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 4-85 Cluster user ID13.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 disks14.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. Chapter 4. IBM Tivoli Storage Resource Manager installation 127
    • 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.128 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 4-89 Private network17.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 Chapter 4. IBM Tivoli Storage Resource Manager installation 129
    • 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.130 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 4-92 Cluster IP address20.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 Chapter 4. IBM Tivoli Storage Resource Manager installation 131
    • 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.132 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 Chapter 4. IBM Tivoli Storage Resource Manager installation 133
    • 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.134 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 4. IBM Tivoli Storage Resource Manager installation 135
    • 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.136 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 4. IBM Tivoli Storage Resource Manager installation 137
    • 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 the138 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 4. IBM Tivoli Storage Resource Manager installation 139
    • 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.140 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • The service name used for this resource is TrelliSrv1 as shown in Figure 4-104.Figure 4-104 Agent service name5. 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. Chapter 4. IBM Tivoli Storage Resource Manager installation 141
    • 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: http://otn.oracle.com/software/tech/java/sqlj_jdbc/content.html 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.142 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 4-107 Selecting the database name3. 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 information5. Complete the connection information as shown, and click Next. Figure 4-109 displays. Chapter 4. IBM Tivoli Storage Resource Manager installation 143
    • 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.144 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 4. IBM Tivoli Storage Resource Manager installation 145
    • 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.146 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • CIM/OM Server supported platforms Windows 2000 AIX Linux ibm.com/redbooksFigure 4-112 CIM/OM server supported platformsTo 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 communicationIn 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=D400Pre-installation taskBefore 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 installedusing the command shown in Example 4-6.Example 4-6 Checking ESS CLI installationC:>esscli -u storwatch -p specialist -s 172.31.1.1 list serverTue 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 1C:>You should see your ESS listed, as in the example. If not, reinstall the CLI package. Chapter 4. IBM Tivoli Storage Resource Manager installation 147
    • 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.148 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 4-114 Installation directory3. Choose the installation directory and click Next. The installation summary screen (Figure 4-115) displays.Figure 4-115 Installation size4. Click Install to start copying files. After this is complete you will see a successful completion message. Click Finish to end the installation process. Chapter 4. IBM Tivoli Storage Resource Manager installation 149
    • 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>150 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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/OMAt the time of writing there was a fix Version 1.1.0.2 available for CIM/OM. It is recommendedto install this fix, which can be downloaded from:http://www-1.ibm.com/support/search.wss?rs=586&q=ssg1*&tc=STHUUM&dc=D400To install the update, do the following:1. Stop the CIM/OM related services: – Service Location Protocol (SLP) – IBM CIM Object Manager2. 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 screen3. Click Next to start the installation; it will check the current and new version, as shown in Figure 4-117. Chapter 4. IBM Tivoli Storage Resource Manager installation 151
    • 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.152 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 4. IBM Tivoli Storage Resource Manager installation 153
    • 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.154 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • – 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 discovery4. 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. Chapter 4. IBM Tivoli Storage Resource Manager installation 155
    • 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.156 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 4. IBM Tivoli Storage Resource Manager installation 157
    • 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.158 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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© Copyright IBM Corp. 2003. All rights reserved. 159
    • 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.160 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 5-2 OS Monitoring treeExcept for Discovery, you can create multiple definitions for each of those monitoring featuresof Tivoli Storage Resource Manager. To create a new definition, right-click on the feature andselect New <feature>. Figure 5-3 shows how to create a new Scan job.Figure 5-3 New Scan job creationOnce saved, any definition within Tivoli Storage Resource Manager can be updated byright-clicking on the object and selecting Edit. This will put you in Edit mode. Save yourchanges 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.162 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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/redbooksFigure 5-5 Tivoli Storage Resource Manager GroupsComputer GroupsComputer Groups allow you to target management jobs on specific computers based on yourown 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 serverIn order to target specific servers for monitoring based on OS and/or database type, we willdefine these four groups: Windows Systems UNIX System Windows DB Systems NAS DevicesTo create the first group, expand Groups -> Computer, right-click Computer and select NewComputer Group. Our first group will contain all UNIX systems as shown in Figure 5-6. Toadd or remove a host from the group, highlight it in either the Available or Current Selectionspanel and use the arrow buttons. You can also enter a meaningful description in the field. Chapter 5. Operations: Policy, Quotas, and Alerts 163
    • 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.164 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 GroupsFilesystem Groups are used to associate together filesystems from different computers thathave some commonality. You can then use this group definition to focus the Scan and theAlert processes to those filesystems.To create a Filesystem Group, you have to select explicitly each filesystem for each computeryou 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 theFilesystem Group definition screen. Chapter 5. Operations: Policy, Quotas, and Alerts 165
    • 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.166 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 5-10 Directory group definitionThe 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 directorydepending on the view you select.We will define one Directory Group with /tmp for all computers, and another with the Oraclelog 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). Chapter 5. Operations: Policy, Quotas, and Alerts 167
    • 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.168 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 5-13 Final Directories Group definitionUser GroupsYou can define Groups made up of selected user IDs. These groupings will enable you toeasily define and focus storage management rules such as scanning and Constraints on thedefined 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. Chapter 5. Operations: Policy, Quotas, and Alerts 169
    • 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.170 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 GroupsYou can define Groups consisting of operating system user groups such as Administrators forWindows or adm for UNIX. To define a Group consisting of user groups, select OS UserGroup 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. Chapter 5. Operations: Policy, Quotas, and Alerts 171
    • 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.172 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 5-17 Discovery When to Run optionsAlert tabThe second tab, Alert, enables you to be notified when a new computer is discovered. See5.2, “OS Alerts” on page 189 for more details on the Alerting process.Options tabThe third tab, Options (Figure 5-18) sets the discovery runtime properties.Figure 5-18 Discovery job optionsUncheck the Skip Workstations field if you want to discover the Windows workstationsreported by the Windows Domain Controller. Chapter 5. Operations: Policy, Quotas, and Alerts 173
    • 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.174 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 5-20 Ping job configuration - ComputersWhen to Ping tabThe tab, When to PING, sets the frequency used for checking. We selected a frequency of 10minutes as shown in Figure 5-21.Figure 5-21 Ping job configuration - When to PingOptions tabOn the Options tab, you specify how often the Ping statistics are saved in the databaserepository. By default, Tivoli Storage Resource Manager keeps its Ping statistics in memoryfor one hour before flushing them to the database and calculating an average availability. Youcan 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) Chapter 5. Operations: Policy, Quotas, and Alerts 175
    • 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 it176 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 5. Operations: Policy, Quotas, and Alerts 177
    • 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.178 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 tabThis 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 theProbe job at a time where all the production data you want to monitor is available to thesystem.Alert tabAs 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 Chapter 5. Operations: Policy, Quotas, and Alerts 179
    • 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 files180 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 OwnerThose default profiles, when set in a Scan job, gather data needed for all the default TivoliStorage Resource Manager reports.As an example, we will define an additional Profile to limit a Scan job to the 500 largestPostscript or PDF files unused in the last six months. We also want to keep weekly statisticsat a filesystem and directory level for two weeks.Statistics tabOn 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 filesThe Statistics tab is used to specify the type of data that is gathered, and has a directimpact on the type of reports that will be available. In our specific case, the Scan associatedwith this profile will not create data for reports based on user IDs and users groups. Neitherwill it create data for reports on directory size. Chapter 5. Operations: Policy, Quotas, and Alerts 181
    • 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.182 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 5-30 New Profile - File filterWith the New Condition menu, you can create a single filter on the files while the NewGroup 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 LengthWe want to select files that meet our conditions: (name is *.ps or name is *.pdf) andunused 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. Chapter 5. Operations: Policy, Quotas, and Alerts 183
    • 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.184 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 save5.1.7 Scans We explain in Figure 5-36 the main objectives of the Scan jobs. Chapter 5. Operations: Policy, Quotas, and Alerts 185
    • 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.186 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 5-37 New Scan configuration - Filesystem tabDirectory Groups tabUse this tab to extend the scope of the Scan and also summarize data for the selecteddirectories. Only directories in the previously selected filesystems will be scanned.Profiles tabAs explained in 5.1.6, “Profiles” on page 180, the Profiles are used to select the files that arescanned for information gathering. A Scan job scans and gathers data only for files that arescoped 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 filesystemand directory level. Chapter 5. Operations: Policy, Quotas, and Alerts 187
    • . 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.188 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 - Dir if in specified FS x x x x FS x x Dir if in specified FS 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. Chapter 5. Operations: Policy, Quotas, and Alerts 189
    • 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.190 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 sampleFigure 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. Chapter 5. Operations: Policy, Quotas, and Alerts 191
    • 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 sample5.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.192 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 5-46 OS Alerting treeExcept for the Alert Log, you can create multiple definitions for each of those Alert features ofTivoli Storage Resource Manager. To create a new definition, right-click on the feature andselect New <feature>. Figure 5-47 shows how to create a new Filesystem Alert. Chapter 5. Operations: Policy, Quotas, and Alerts 193
    • Figure 5-47 Filesystem alert creation5.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.194 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 5-48 Computer alerts - AlertsAlerts tabThe 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. Chapter 5. Operations: Policy, Quotas, and Alerts 195
    • 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 tab196 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 5. Operations: Policy, Quotas, and Alerts 197
    • Figure 5-53 Filesystem alert - Freespace default mail5.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.198 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 5-54 Alerts logThere are eight different views. Each of them will show only the Alerts related to the selectedview 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 fieldWhen you click on the icon on the left of a listed Alert, you will see detailed information on theselected Alert as shown in Figure 5-55. Chapter 5. Operations: Policy, Quotas, and Alerts 199
    • Figure 5-55 Detailed Alert information5.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 resources5.3.1 Filesystem extension and LUN provisioning The main functions of Filesystem Extension are shown in Figure 5-56.200 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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/redbooksFigure 5-56 Filesystem ExtensionWe use filesystem extension policy to automatically extend filesystems when utilizationreaches a specified threshold. We can also enable LUN provisioning to extend filesystemswithin an ESS.To setup filesystem extension policy, select IBM Tivoli SRM -> Policy Management ->Filesystem Extension. Right click on Filesystem Extension and select Create FilesystemExtension Rules. The screen in Figure 5-57 displays. Chapter 5. Operations: Policy, Quotas, and Alerts 201
    • 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:202 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 withthe Add or Make Freespace under Amount to Extend. If you enter a maximum capacity for afilesystem in the Filesystem Maximum Capacity field, if a filesystem reaches the specifiedsize, the filesystem will be removed from the policy and an Alert will be triggered.Condition for Filesystem ExtensionThe 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 ModeEnable Do Not Extend Filesystems - Log Only when you want the policy to log thefilesystem extension. The extension actions that would have taken place are written to the logfile, but no extension takes place.In the Provisioning tab (Figure 5-59) we define LUN provision parameters. Note that LUNprovisioning is available at the time of writing for filesystems on an ESS only. Chapter 5. Operations: Policy, Quotas, and Alerts 203
    • 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.204 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 5-60 When to Enforce Policy tabThe options are:Enforce Policy after every Probe or Scan automatically enforces the policy after everyProbe or Scan job. The policy will stay in effect until you either change this setting or disablethe 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/PMThe Alert tab (Figure 5-61) can define an Alert that will be triggered by the filesystemextension job. Chapter 5. Operations: Policy, Quotas, and Alerts 205
    • 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.206 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 5-62 Save filesystem changesThe 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 currentfilesystem contents are shown in Example 5-3.Example 5-3 Status of the filesystems before expansion# df -kFilesystem 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 - IBMTivoli SRM -> Policy Management -> Filesystem Extension. Right click on FilesystemExtension and select Create Filesystem Extension Rules. We selected the /opt filesystemas shown in Figure 5-63. Chapter 5. Operations: Policy, Quotas, and Alerts 207
    • 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.208 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 5-65 Alert definitionAfter all the data is entered we save the rule, calling it opt extension. The new definition isnow shown in the menu tree as in Figure 5-66.Figure 5-66 Rule for /opt extensionWe now execute the rule by right clicking on it and selecting Run Now. In Figure 5-67 you cansee the successful extension of the /opt filesystem. Chapter 5. Operations: Policy, Quotas, and Alerts 209
    • 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 Filesystem 1024-blocks Free %Used Iused %Iused Mounted on /dev/hd4 32768 17468 47% 1594 10% / /dev/hd2 1277952 339100 74% 29164 10% /usr /dev/hd9var 49152 40180 19% 468 4% /var210 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • /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 filesystemsize 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 ESSLUN. Example 5-5 shows the volume group definition.Example 5-5 essvg1 volume group definition# lsdev -Cc diskhdisk0 Available 10-80-00-4,0 16 Bit SCSI Disk Drivehdisk1 Available 1P-18-01 IBM FC 2105F20hdisk2 Available 1P-18-01 IBM FC 2105F20vpath0 Available Data Path Optimizer Pseudo Device Driver# lsvpcfgvpath0 (Avail pv essvg1) 30918921 = hdisk1 (Avail ) hdisk2 (Avail )#The volume group is defined on the vpath0 device which represents an ESS LUN with serialnumber 30918921. The vpath device is used as we have two paths to the physical LUN. Seethe 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 inExample 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 lv00LOGICAL VOLUME: lv00 VOLUME GROUP: essvg1LV IDENTIFIER: 0041f12b00004c00000000f5a9cf986f.1 PERMISSION: read/writeVG STATE: active/complete LV STATE: opened/syncdTYPE: jfs WRITE VERIFY: offMAX LPs: 512 PP SIZE: 64 megabyte(s)COPIES: 1 SCHED POLICY: parallelLPs: 96 PPs: 96STALE PPs: 0 BB POLICY: relocatableINTER-POLICY: minimum RELOCATABLE: yesINTRA-POLICY: middle UPPER BOUND: 32MOUNT POINT: /essfs1 LABEL: /essfs1MIRROR WRITE CONSISTENCY: on/ACTIVEEACH 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 thefilesystem in rootvg (no LUN provisioning)” on page 207. Chapter 5. Operations: Policy, Quotas, and Alerts 211
    • 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).212 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 5-71 Provisioning parametersWe defined to model the LUNs on LUNs which are already in the volume group, and to createthem anywhere in the ESS.In When to Enforce Policy we specified Enforce policy: Now, this means that the policy willbe 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 extensionaction 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 -kFilesystem 1024-blocks Free %Used Iused %Iused Mounted on/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 wassuccessfully completed, extending /essfs1 by 2GB. Chapter 5. Operations: Policy, Quotas, and Alerts 213
    • 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 Filesystem 1024-blocks Free %Used Iused %Iused Mounted on /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 Filesystem 1024-blocks Free %Used Iused %Iused Mounted on /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% /opt214 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • /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 theexisting LUN for the essvg1 volume group was 8GB, as shown with the command lspvvpath0 in Example 5-10.Example 5-10 vpath0 LUN size# lspv vpath0PHYSICAL VOLUME: vpath0 VOLUME GROUP: essvg1PV IDENTIFIER: 0041f12ba9cf89ec VG IDENTIFIER 0041f12b00004c00000000f5a9cf986fPV STATE: activeSTALE PARTITIONS: 0 ALLOCATABLE: yesPP SIZE: 64 megabyte(s) LOGICAL VOLUMES: 2TOTAL PPs: 126 (8064 megabytes) VG DESCRIPTORS: 2FREE PPs: 20 (1280 megabytes) HOT SPARE: noUSED PPs: 106 (6784 megabytes)FREE DISTRIBUTION: 00..00..00..00..20USED DISTRIBUTION: 26..25..25..25..05#As the /essfs1 free space is still below 75% we ran the rule again and the filesystem wasexpanded again. The result can be seen in Example 5-11.Example 5-11 /essfs1 after third expansion# df -kFilesystem 1024-blocks Free %Used Iused %Iused Mounted on/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. Chapter 5. Operations: Policy, Quotas, and Alerts 215
    • 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 vpath0 (Avail pv essvg1) 30918921 = hdisk1 (Avail ) hdisk2 (Avail ) vpath1 (Avail pv essvg1) 20018921 = hdisk3 (Avail ) hdisk4 (Avail ) # 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 #216 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 5. Operations: Policy, Quotas, and Alerts 217
    • 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 Actions triggered through standard Alerting mechanism when 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.218 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Use IBM Tivoli SRM -> Policy Management -> Quotas -> User -> Network, right-click andselect New Quota to create a new Quota. The right pane displays the Quota configurationscreen with four tabs.Users tabFigure 5-76 shows the Users tab for Network Quotas.Figure 5-76 User Network Quotas - Users tabFrom the Available column, select any user ID or OS User Group you want to monitor forspace 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 Profileyou want to use from the pull-down. The default Profile Summary by Owner collectsinformation about all files and summarizes them on the user level. The ALLGIFFILES profilecollects information about GIF files and creates a summary at a user level as displayed inFigure 5-77. This (non-default) profile was created using the process shown in 5.1.6,“Profiles” on page 180. Chapter 5. Operations: Policy, Quotas, and Alerts 219
    • 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.220 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • When to checkThe Quota management is based on the output of the Scan jobs. Therefore, each Quotadefinition 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 tabOn the Alert tab, specify the Quota limit in: KB, MB or GB, and the action to run when theQuota is exceeded.Figure 5-79 User Network Quotas - Alert tabYou can choose from the standard Alerts type available with Tivoli Storage ResourceManager. Each Alert will be fired once for each user exceeding their Quota. We have selectedto run a script that we wrote, QUOTAUSERNET.BAT, listed in Example 5-14.Example 5-14 QUOTAUSERNET.BAT scriptecho NETWORK quota exceeded - %1 %2 uses %3 - Limit set to %4 >>quotausernet.txtExample 5-15 shows the output file created by QUOTAUSERNET.BAT.Example 5-15 Content of quotausernet.txtNETWORK quota exceeded - user root uses 8.22GB - Limit set to 5.0GBNETWORK quota exceeded - user Administrators@BUILTIN uses 9.61GB - Limit set to 5.0GBThe Alert has fired for user root and Administrators. This clearly shows that administrativeusers such as root and Administrators should not normally be included in standard Quotasmonitoring. Chapter 5. Operations: Policy, Quotas, and Alerts 221
    • 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.222 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 5. Operations: Policy, Quotas, and Alerts 223
    • 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 Actions triggered through standard Alerting mechanism when 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).224 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 5-83 Constraint - File TypesUse the buttons on the top of the screen, to allow or forbid files depending on their name. Theleft column shows some default file patterns, or you can use the bottom field to create yourown pattern. Click >> to add your pattern to the allowed/forbidden files.Users tabThe Users tab (figured in Figure 5-84) is used to allow or restrict the selected users in theConstraint.Figure 5-84 Constraint - Users Chapter 5. Operations: Policy, Quotas, and Alerts 225
    • 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.226 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • Figure 5-86 Constraints - File filterWe changed the file filter to a more appropriate one by changing the OR operator to AND.Figure 5-87 Constraints - File filter changedAlert tabAfter selecting the files, you may want to generate an Alert only if the total used spacemeeting the Constraint conditions exceeds a predefined limit. Use the Alert tab to specifythe triggering condition and action. Chapter 5. Operations: Policy, Quotas, and Alerts 227
    • 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 parameters228 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 5. Operations: Policy, Quotas, and Alerts 229
    • 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.230 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 Tree5.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. Chapter 5. Operations: Policy, Quotas, and Alerts 231
    • 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.232 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 Chapter 5. Operations: Policy, Quotas, and Alerts 233
    • 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.234 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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. Chapter 5. Operations: Policy, Quotas, and Alerts 235
    • 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 filesTivolitsmbaclient236 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • @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 output5.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. Chapter 5. Operations: Policy, Quotas, and Alerts 237
    • 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 Display starting messages 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 Perform basic checks on db type and directory238 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • REM ---------------------------------------------if not %3 == "MicroSoft SQL/Server" GOTO NOTSQLREM Execute backup commandREM ----------------------CD C:Program FilesMicrosoft SQL ServerMSSQLBackupecho Current Log backupsecho -------------------dir %1_Tlog*cd ..binn@echo onsqlmaint -D %1 -BkUpLog -BkUpMedia DISK -UseDefDirif not %errorlevel% == 0 GOTO SQLERROR@echo offecho New Log backupsecho ---------------cd ..Backupdir %1_Tlog*echo SQLBKPLOG.BAT ended successfully ...exit 0:NOTSQLecho Error - Not MSSQL databaseexit 4:SQLERRORecho Error while running SQLMAINT commandexit 4Example 5-18 shows the output of the Alert log.Example 5-18 Alert log output09-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% ofits 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 ServerMSSQLBACKUP09/18/2002 02:28p 82,432 northwind_tlog_200209181428.BAK09/18/2002 02:47p 345,600 northwind_tlog_200209181447.BAK09/18/2002 03:21p 82,432 Northwind_tlog_200209181521.BAK09/18/2002 03:24p 15,872 Northwind_tlog_200209181524.BAK09/18/2002 03:28p 15,872 Northwind_tlog_200209181528.BAK09/18/2002 03:29p 15,872 Northwind_tlog_200209181529.BAK09/18/2002 04:25p 82,432 Northwind_tlog_200209181625.BAK09/18/2002 04:26p 15,872 Northwind_tlog_200209181626.BAK 8 File(s) 656,384 bytes 0 Dir(s) 10,313,953,280 bytes freeC:Program FilesMicrosoft SQL ServerMSSQLBinn>sqlmaint -D Northwind -BkUpLog -BkUpMediaDISK -UseDefDir Chapter 5. Operations: Policy, Quotas, and Alerts 239
    • 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 09/18/2002 02:28p 82,432 northwind_tlog_200209181428.BAK 09/18/2002 02:47p 345,600 northwind_tlog_200209181447.BAK 09/18/2002 03:21p 82,432 Northwind_tlog_200209181521.BAK 09/18/2002 03:24p 15,872 Northwind_tlog_200209181524.BAK 09/18/2002 03:28p 15,872 Northwind_tlog_200209181528.BAK 09/18/2002 03:29p 15,872 Northwind_tlog_200209181529.BAK 09/18/2002 04:25p 82,432 Northwind_tlog_200209181625.BAK 09/18/2002 04:26p 15,872 Northwind_tlog_200209181626.BAK 09/18/2002 04:36p 15,872 Northwind_tlog_200209181636.BAK 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 = 05.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 x5.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.240 IBM Tivoli Storage Resource Manager: A Practical Introduction
    • 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 resources5.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 Chapter 5. Operations: Policy, Quotas, and Alerts 241
    • 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