managing storage management tivoli enterprise integration with tivoli storage manager sg246117

ibm.com/redbooks

Managing Storage ManagementTivoli Enterprise integration with Tivoli Storage Manager

Patrick RandallMichel Baus

Andrej MarencicMelinda Sangargir

Centrally manage your distributed storage management environment

Automatically react to storage events

Benefit from practical, real-life examples

http://www.redbooks.ibm.com/


Managing Storage ManagementTivoli Enterprise integration withTivoli Storage Manager

October 2000

SG24-6117-00

International Technical Support Organization

© Copyright International Business Machines Corporation 2000. All rights reserved.Note to U.S Government Users – Documentation related to restricted rights – Use, duplication or disclosure issubject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.

First Edition (October 2000)

This edition applies to Version 3.7.3 of Tivoli Storage Manager and Tivoli Management Framework3.6.3 for use with all supported operating systems.

Comments may be addressed to:IBM Corporation, International Technical Support OrganizationDept. QXXE Building 80-E2650 Harry RoadSan Jose, California 95120-6099

When you send information to IBM, you grant IBM a non-exclusive right to use or distribute theinformation in any way it believes appropriate without incurring any obligation to you.

Before using this information and the product it supports, be sure to read the general information inAppendix A, “Special notices” on page 157.

Take Note!

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiThe team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

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

Chapter 1. Introduction to Tivoli Management products . . . . . . . . . . . . 31.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2 Parts and pieces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.2.1 Tivoli Enterprise modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2.2 Tivoli Data Protection for Applications . . . . . . . . . . . . . . . . . . . . . 81.2.3 Other Tivoli modules for managing applications . . . . . . . . . . . . . 121.2.4 Tivoli Storage Manager event handling. . . . . . . . . . . . . . . . . . . . 161.2.5 Tivoli Service Desk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

1.3 System environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Part 2. Using the individual modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 2. Tivoli Framework TME 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.1 Framework architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.2 Framework desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.2.1 Desktop window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.3 Framework components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.3.1 Tivoli Management Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.3.2 Policy regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.3.3 TME administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.3.4 Profile managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.3.5 Task libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.3.6 Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.3.7 Notice groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.4 Framework configuration: examples . . . . . . . . . . . . . . . . . . . . . . . . . . 282.4.1 Defining administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.4.2 Creating tasks and jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

2.5 Hints and tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 3. Tivoli Distributed Monitoring . . . . . . . . . . . . . . . . . . . . . . . . 413.1 Tivoli Distributed Monitoring concepts . . . . . . . . . . . . . . . . . . . . . . . . 41

3.1.1 Tivoli Distributed Monitoring components . . . . . . . . . . . . . . . . . . 42

© Copyright IBM Corp. 2000 iii

3.1.2 Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443.2 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.2.1 Monitoring the status of the dsmserv daemon. . . . . . . . . . . . . . . 473.2.2 Custom script monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

3.3 Hints and tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Chapter 4. Tivoli Software Distribution . . . . . . . . . . . . . . . . . . . . . . . . . 554.1 Overview of Tivoli Software Distribution . . . . . . . . . . . . . . . . . . . . . . . 55

4.1.1 Source host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554.1.2 Target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.1.3 Repeaters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.1.4 File package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.1.5 Autopack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.3 Setting the environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

4.3.1 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.3.2 Creating packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.3.3 Distributing packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

4.4 Hints and tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Chapter 5. Tivoli Inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695.1 Tivoli Inventory concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

5.1.1 Tivoli Inventory components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705.1.2 Tivoli Inventory installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705.1.3 Tivoli Inventory scan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

5.2 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735.2.1 Inventory profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735.2.2 Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

5.3 Hints and tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Chapter 6. Tivoli Enterprise Console . . . . . . . . . . . . . . . . . . . . . . . . . . 856.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856.2 Overview of the Tivoli Enterprise Console . . . . . . . . . . . . . . . . . . . . . 86

6.2.1 Event adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 886.2.2 Event classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906.2.3 Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906.2.4 Handling of the messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

6.3 How to prepare TEC for Tivoli Storage Manager . . . . . . . . . . . . . . . . 936.3.1 Importing files for Tivoli Storage Manager. . . . . . . . . . . . . . . . . . 936.3.2 Creating event group for Tivoli Storage Manager . . . . . . . . . . . . 966.3.3 Display setting of the event console . . . . . . . . . . . . . . . . . . . . . 1006.3.4 Creating an automated task . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026.3.5 Setting the severity of TEC events . . . . . . . . . . . . . . . . . . . . . . 1066.3.6 Deleting rule sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

iv Managing Storage Management: Tivoli Enterprise Integration with Tivoli Storage Management

Chapter 7. Tivoli Plus Module for ADSM . . . . . . . . . . . . . . . . . . . . . . . 1117.1 Components of Tivoli Plus Module . . . . . . . . . . . . . . . . . . . . . . . . . . 1117.2 How it works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1127.3 Setting up the Tivoli Plus Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 1127.4 Hints and tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Chapter 8. Tivoli Data Protection for Applications . . . . . . . . . . . . . . . 1158.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1158.2 Event forwarding to Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . 1168.3 Using tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1168.4 Using Tivoli Software Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . 1178.5 Hints and tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Chapter 9. Tivoli Enterprise features of Tivoli Storage Manager . . . . 1199.1 Tivoli Storage Manager enterprise features . . . . . . . . . . . . . . . . . . . 119

9.1.1 How to set up server-to-server communication . . . . . . . . . . . . . 1219.1.2 Configuring and managing the servers . . . . . . . . . . . . . . . . . . . 1239.1.3 Storing data on another server . . . . . . . . . . . . . . . . . . . . . . . . . 1249.1.4 Managing servers from any server . . . . . . . . . . . . . . . . . . . . . . 1249.1.5 Central monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

9.2 Predefined items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1299.3 Example of event logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1299.4 Hints and tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Chapter 10. Tivoli Service Desk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13110.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13110.2 Customizing Tivoli Service Desk. . . . . . . . . . . . . . . . . . . . . . . . . . . 132

10.2.1 Editing a Tivoli Service Desk user profile . . . . . . . . . . . . . . . . 13310.2.2 Starting the Tivoli Storage Manager administrative client . . . . 13610.2.3 Migrating assets from Tivoli Inventory. . . . . . . . . . . . . . . . . . . 13710.2.4 Opening a call in Tivoli Service Desk . . . . . . . . . . . . . . . . . . . 139

10.3 Hints and tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Part 3. Putting it all together . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Chapter 11. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14311.1 Updating the Tivoli Storage Manager backup-archive client . . . . . . 14311.2 Extending the Tivoli Storage Manager recovery log . . . . . . . . . . . . 14911.3 Offline backup of the Exchange server . . . . . . . . . . . . . . . . . . . . . . 153

Appendix A. Special notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Appendix B. Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161B.1 IBM Redbooks publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

v

B.2 IBM Redbooks collections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162B.3 Tivoli publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165IBM Redbooks fax order form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

IBM Redbooks review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

vi Managing Storage Management: Tivoli Enterprise Integration with Tivoli Storage Management

Figures

1. Tivoli Enterprise Framework, its modules, and Tivoli Storage Manager . . . 42. Tivoli Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213. Tivoli desktop — example of window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234. Desktop Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245. Create Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286. Create Administrator, Set TMR Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297. Create Administrator, Set Login Names . . . . . . . . . . . . . . . . . . . . . . . . . . 308. Create Administrator, Set Resource Roles . . . . . . . . . . . . . . . . . . . . . . . . 319. Create Administrator, Set Notice Groups. . . . . . . . . . . . . . . . . . . . . . . . . . 3210. Create Administrator, administrator desktop . . . . . . . . . . . . . . . . . . . . . . . 3211. Task Library, acme_task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3312. Create Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3413. Task Library, acme_task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3514. Create Job menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3615. Schedule a job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3816. Schedule a job, Set Retry/Cancel/Restriction . . . . . . . . . . . . . . . . . . . . . . 3917. Tivoli Distributed Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4118. Interaction between Tivoli Distributed Monitoring and the TMR server . . . 4319. Profile to monitor Tivoli Storage Manager and subscribed Endpoint . . . . . 4520. Monitors inside Distributed Monitoring profile . . . . . . . . . . . . . . . . . . . . . . 4621. Monitor daemon status of Tivoli Storage Manager . . . . . . . . . . . . . . . . . . 4822. User and group ID to execute the monitors . . . . . . . . . . . . . . . . . . . . . . . . 5023. Universal numeric monitor with custom script . . . . . . . . . . . . . . . . . . . . . . 5224. Distributing a custom script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5325. Tivoli Software Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5526. Tivoli Software Distribution process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5727. Create Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5928. Autopack main menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6129. Scanning the system with Autopack Control Center . . . . . . . . . . . . . . . . . 6130. Build Autopack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6231. File Package Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6332. Unix After Distribution Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6433. Distribute File Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6634. Tivoli Inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6935. Tivoli Inventory architecture when scanning Endpoints . . . . . . . . . . . . . . . 7236. Profile manager with inventory profiles and subscribers . . . . . . . . . . . . . . 7437. Inventory profile manager and query libraries . . . . . . . . . . . . . . . . . . . . . . 7538. Inventory scan for hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7639. Inventory scan for software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7840. Storing configuration files as ASCII through inventory profile . . . . . . . . . . 79

© Copyright IBM Corp. 2000 vii

41. Sample hardware query. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8042. Custom query TSM clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8243. Query results of custom TSM client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8344. Tivoli Enterprise Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8545. Tivoli Enterprise Console event flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8646. Components of the TEC Event Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . 8847. TEC Adapter profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9048. Rule Bases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9149. Tivoli Storage Manager message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9250. Translating Tivoli Storage Manager messages into TEC Events. . . . . . . . 9351. Rule Base Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9452. Copy Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9453. Import Into Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9554. Compile Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9655. Load Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9656. Event Group Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9757. New Event Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9858. Edit Event Group Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9959. Assign Event Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10060. Event Groups display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10161. Sort Event Group Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10162. Tivoli Enterprise Console Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10363. Select Event Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10464. Summary of the Automated Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10465. Setup Automatic Task Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10566. Automated Task Execution Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10667. Tivoli Plus Module for Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . 11168. ADSMPlus for Tivoli menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11269. Set ADSM Home menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11370. Tivoli Data Protection for Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 11571. Tivoli Data Protection for MS Exchange . . . . . . . . . . . . . . . . . . . . . . . . . 11772. Tivoli Storage Manager event forwarding . . . . . . . . . . . . . . . . . . . . . . . . 12073. Server-to-server communication, enterprise administration . . . . . . . . . . 12274. Server-to-server event logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12675. Event logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12976. Tivoli Service Desk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13277. Tivoli Service Desk main window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13278. Configuration of a user profile in Tivoli Service Desk . . . . . . . . . . . . . . . 13379. Action groups in Tivoli Service Desk . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13480. System actions in Tivoli Service Desk . . . . . . . . . . . . . . . . . . . . . . . . . . . 13581. Launching administrative client from Tivoli Service Desk . . . . . . . . . . . . 13682. Tivoli Storage Manager Web administrative client. . . . . . . . . . . . . . . . . . 13683. Configuring the Tivoli Inventory database into Tivoli Service Desk . . . . . 137

viii Managing Storage Management: Tivoli Enterprise Integration with Tivoli Storage Management

84. Importing assets from Tivoli Inventory into Tivoli Service Desk. . . . . . . . 13885. Opening a call in Tivoli Service Desk. . . . . . . . . . . . . . . . . . . . . . . . . . . . 13986. Rule sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14587. New Simple Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14688. Condition in Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14789. Actions in Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14890. Extend log rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15191. Extend log arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15292. Compound Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15393. Stop_Services parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15494. Send_Event task parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

ix

x Managing Storage Management: Tivoli Enterprise Integration with Tivoli Storage Management

Preface

This IBM Redbook covers the new features of Tivoli Storage Manager, whichrelate to the Tivoli Enterprise set of products and show how these, in return,can contribute to a traditional installation of Tivoli Storage Manager.

This redbook is addressed to Tivoli Storage Manager administrators, whohave little or no knowledge of Tivoli Enterprise. However, it does not cover thebasic installation of the Tivoli Framework or its applications. This is covered inother books listed in Appendix B, “Related publications” on page 161.

We focus on Tivoli Enterprise products, such as Framework, DistributedMonitoring, Inventory, Software Distribution, and Enterprise Console. Weshow how these modules can be used to ease daily tasks, to monitorconditions, and to report these accordingly. Additionally, we explain how tocustomize Tivoli Storage Manager to collaborate with the Tivoli Enterprisemodules.

This book is divided into three parts. Part 1 contains an introduction to thedifferent Tivoli Enterprise modules and special features of Tivoli StorageManager. Part 2 covers each of the modules in depth. Part 3 describes acomplete scenario where all of the modules come together, thereforeproviding a holistic approach to an enterprise management system, includingstorage.

© Copyright IBM Corp. 2000 xi

The team that wrote this redbook

This redbook was produced by a team of specialists from around the worldworking at the International Technical Support Organization San Jose Center.

Pat Randall is a Distributed Storage Software Specialist at the InternationalTechnical Support Organization, San Jose, California. He has written elevenredbooks on ADSM and Tivoli Storage Manager, teaches IBM classesworldwide on all areas of distributed storage, and is a consultant in disasterand business recovery. Before joining the ITSO in July 1996, Patrick workedin IBM UK's Business Recovery Services as a Solutions Architect.

Michel Baus is a consultant at sys Gesellschaft fuer Client/ServerLoesungen mbH in Germany as an independent IT Integrator. He has fiveyears of experience in implementing Tivoli Storage Manager/ADSM and threeyears in designing Tivoli Enterprise based solutions. He holds a degree inSensor Systems Technology from Karlsruhe University of Applied Science,Germany. His areas of expertise include DCE/DFS, RS/6000 SP, ACSLS andSAN.

Andrej Marencic is an IT Specialist in Nibble Data Systems. He has fouryears of experience in the Technical Support and Systems Managementfields, and he teaches IBM courses. His areas of expertise include WindowsNT and UNIX operating systems, Tivoli Storage Manager/ADSM, TivoliFramework, and Tivoli Enterprise Console.

Melinda Sangardir is a UNIX IT Specialist at IBM Denmark. She has threeyears of experience in implementing and supporting Tivoli Storagemanager/ADSM and eight years experience in other IT areas. She holds abachelor’s degree in English and an EDP diploma from EDP College inDenmark. Her areas of expertise include UNIX administration, backupsystems, and Tivoli Storage Manager/ADSM.

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

Tetsuya ShiraiInternational Technical Support Organization, San Jose Center

Yvonne LyonInternational Technical Support Organization, San Jose Center

xii Managing Storage Management: Tivoli Enterprise Integration with Tivoli Storage Management

Comments welcome

Your comments are important to us!

We want our Redbooks to be as helpful as possible. Please send us yourcomments about this or other Redbooks in one of the following ways:

• Fax the evaluation form found in “IBM Redbooks review” on page 175 tothe fax number shown on the form.

• Use the online evaluation form found at ibm.com/redbooks

• Send your comments in an Internet note to [email protected]

xiii



http://www.redbooks.ibm.com/contacts.html

xiv Managing Storage Management: Tivoli Enterprise Integration with Tivoli Storage Management

Part 1. Introduction

Part 1 explains the basic functions and special features of the various Tivoliproducts and modules that are covered in this book.

© Copyright IBM Corp. 2000 1

2 Managing Storage Management: Tivoli Enterprise Integration with Tivoli Storage Management

Chapter 1. Introduction to Tivoli Management products

In this chapter, we give you an overview of the different products and Tivolimodules, which are used in the other parts of the book. We explain their basicfunctions and their special features.

1.1 Overview

In Figure 1 you can see all the products which are mentioned in the book andtheir logical connections to each other. In the upper left corner, there is theTivoli Framework underlaying most of the Tivoli modules except Tivoli ServiceDesk. In the lower part there is the Tivoli Storage Manager suite with theserver itself and the different clients and special modules. On the right sideyou can see some applications, which can be managed by TivoliManagement modules and its storage managed by the Tivoli Data Protectionmodules for Applications. By using all these products together, you will get aclosed cycle of events, management, and data flow.


Figure 1. Tivoli Enterprise Framework, its modules, and Tivoli Storage Manager

1.2 Parts and pieces

This section is divided into the Tivoli Enterprise modules, which use theFramework, the Tivoli Data Protection for Applications modules, other Tivolimodules such as the ADSMPlus module for Tivoli Storage Manager and TivoliManager for Applications, and some basics for event flow in Tivoli StorageManager itself and the Tivoli Service Desk.

1.2.1 Tivoli Enterprise modules

1.2.1.1 Tivoli FrameworkThe Tivoli Framework provides the basic system management services, suchas communications, presentation, and security, that most of the Tivoli

TivoliData

Protection forOracle

BackupArchiveClient

TivoliData

Protection forExchange

TivoliData

Protection forDomino

TivoliData

Protection forSQL

AdminClient

Oracle

SQL

RDBMS

Exchange

Domino

TivoliServiceDesk

Framework

TivoliStorageManager

Server

TivoliADSMPlus

Module

TivoliManager for

Oracle

TivoliManager for

Domino

TivoliManager for

SQL

TivoliManager forExchange

TivoliInventory

TivoliSoftware

Distribution

TivoliDistributedMonitoring

TivoliEnterpriseConsole

TivoliRDBMSInterfaceModule

TivoliService

Desk PlusModule


Management applications use, thus, ensuring consistency and integration. Atits core, the Tivoli Framework provides the facilities to transfer files andexecute commands on remote systems with built-in security and authorizationroles. The Tivoli Management applications can use these core facilities toimplement management functions, such as software distribution, resourcemonitoring, and system configuration.

Most Tivoli systems management tasks, regardless of the application orcomponent that is to be managed, may be performed by using the Tivolidesktop that provides a user interface consistent throughout managementapplications. However, you are not limited to using the Tivoli desktop, asmany jobs and tasks can also be executed using the command line interface.

1.2.1.2 Tivoli Distributed MonitoringTivoli Distributed Monitoring is an application that allows you to monitor thestatus of a wide range of geographically-dispersed platforms from differentvendors running different operating systems, including resources that are notpart of your Tivoli Environment.

A monitor is an entity that controls specific aspects of a resource (percentageof disk space, status of a print queue, database process status, load averageof a system, network collisions, and so on). Its definition contains thresholdvalues and various response actions triggered upon reaching a threshold.Tivoli Distributed Monitoring uses the concept of management by subscriptionas the other Tivoli core applications. Monitors are defined centrally indistributed monitoring profiles and then distributed and activated on the targetsystems.

Tivoli Distributed Monitoring provides your network computing environmentwith the following features:

• Centralized, synchronous (scheduled) monitoring of remote resources

• Predefined monitors for almost every resource (monitoring collections)

• Strong mechanism to generate events and alarms

• Automated decisions and actions in response to alarms or events

• Various responses (e-mail, triggering a program)

• Custom scripts for monitoring specific applications

• Full integration with the Tivoli Enterprise Console event server

• Data collection for statistical analysis and capacity planning

Chapter 1. Introduction to Tivoli Management products 5

1.2.1.3 Tivoli Software DistributionTivoli Software Distribution provides facilities for the distribution andinstallation of software to managed systems in a Tivoli environment. TivoliSoftware Distribution uses the facilities provided by the Tivoli ManagementFramework to distribute file packages in an efficient manner. Administratorsuse the profile paradigm used by most other Tivoli applications to define filepackages to be distributed. These file packages can include any files(executable programs, data files, and so on) and scripts that will be executedbefore and after the distribution for a proper installation of the files on thetarget system.

The actual distribution process can use the Multiplexed Distribution (MDist)facility of the framework to optimize the use of the network. MDist is used todefine nodes as repeaters so that they become fan-out points for thedistribution. By defining an appropriate repeater hierarchy for your networkenvironment, large file packages will only be moved once across slower links,but will still reach multiple target systems.

1.2.1.4 Tivoli InventoryOne of the challenges in a network computing environment is keeping track ofthe hardware and software installed on each machine. Tivoli Inventoryaddresses this problem by providing the means to gather hardware andsoftware information related to each system and then storing that informationin a relational database. Queries and reports can be run to display theinformation in this database.

Tivoli Inventory has three major advantages:

• It is based on the Tivoli Management Framework and therefore can betightly and automatically integrated with other Tivoli applications.

• It stores inventory information in a Relational Database ManagementSystem (RDBMS) and therefore allows any non-Tivoli applications thatcan access SQL data to share the inventory information. Moreover, itbenefits from the advanced features of an RDBMS system, such asscalability and performance.

• Tivoli Inventory has close links with other applications, such as TivoliSoftware distribution and Tivoli Service Desk.

1.2.1.5 Tivoli Enterprise ConsoleFor many companies, the computing enterprise is becoming moreheterogeneous in nature. It is supporting a wider variety of operating systemplatforms, communications methods, and a diverse set of applications anddatabases. Many computing enterprises are also becoming more distributed


both from a client/server and a geographical perspective. It follows, therefore,that the computing enterprise is becoming increasingly more demanding tomanage and control, and it is getting more difficult to attain acceptable levelsof availability. Availability or the lack of availability of the computing resourcesmay be directly related to the bottom line of a company as well as to itscompetitiveness within the industry.

The people who create and develop the variety of resources that make up acomputing environment give the resources the ability to provide statusinformation through the creation and transmission of alarms, messages,alerts, traps, and so on. These may be created in large quantities and mayflow through the network expressing significant or insignificant changes in thestatus of those resources. It is up to the system support teams andoperations staff to sort through the potentially large quantity of messages inorder to respond appropriately to a given situation.

To issue these problems, Tivoli Enterprise Console (TEC) provides acentralized point of integration and control for enterprise client/serverenvironments. It allows administrators to monitor information about theenvironments for which they are responsible.

TEC assists in maintaining high availability of the myriad of networks,systems, applications, and databases found within an enterprise. TEC helpsdetect potential problems before they cause outages. When problems aredetected, TEC may be configured to take action and intervene as defined bythe customer.

TEC can prevent administrators from being flooded with unnecessary datathat masks the real problems. For instance, it can perform automatic actionsor filter out duplicate messages. By maintaining a comprehensive history ofreported conditions, TEC allows handling only serious problem that happen ina particular time frame or in the context of other previously-received events.

Both TEC and Tivoli Distributed Monitoring (TDM) are capable of monitoringsystem resources and activities. Both have the capability to respond toevents. TEC is more powerful in that it can understand that events reportedfrom different sources are related. TEC maintains a history, whereas TDMdoes not. The administrators have more power and flexibility to respond toevents with TEC.

The scope of events which TEC can monitor is broader. However, mostenvironments use TEC and TDM. Let us distinguish each product:

• TDM is ideal for monitoring locally and for synchronous monitoring.


• TEC is for asynchronous monitoring.

• Complex and persistent or unresolved problems with TDM can beforwarded to TEC for further analysis.

1.2.2 Tivoli Data Protection for ApplicationsThe Tivoli Data Protection for Applications modules allow you to back up datain databases to a Tivoli Storage Manager server by using the module tointerface directly with the Tivoli Storage Manager API. Usually, when youback up data from the database, the format of this data may need to beconverted into files before backup; also, the database may be need to beoffline to get a consistent backup.

By using the Tivoli Storage Manager API, the underlying physical structure ofthe database (raw devices or files) is handled by the application (theapplication decides how the data is stored); so, it does not matter whetherraw devices or files are used. Also, the type of backup (for example, online,offline, incremental, or table space) is determined and controlled by theapplication. Some products, such as IBM DB/2 can write directly to the TivoliStorage Manager API without using Tivoli Data Protection modules.

1.2.2.1 Tivoli Data Protection for MS ExchangeTivoli Data Protection for Microsoft Exchange Server is an application thatallows you to perform online backups of Microsoft Exchange Serverdatabases to Tivoli Storage Manager storage. Tivoli Data Protection forMicrosoft Exchange Server is referred to as the Exchange Application Clientin this document. The Exchange Application Client helps protect and manageExchange Server data by making it easy to do the following actions:

• Perform full, copy, differential, and incremental backups of the MicrosoftExchange Directory and Information Store databases.

• Restore a full Directory or Information Store database and any number ofassociated transaction logs.

• Delete a Directory or Information Store database backup from TSMstorage.

• Back up the Exchange Server databases to any TSM server withdrag-and-drop ease.

• Set TSM options regarding connection information to TSM servers.

• Set TSM options regarding security and performance.

• Obtain online context sensitive, task, and concept help.

• View online documentation for the Exchange Application Client.


• Launch TSM and other related system applications.

• Automate scheduled backups.

• Automate deletion of old backups.

• Back up and restore a Microsoft Exchange Server Cluster running in aMicrosoft Cluster Server (MSCS) environment.

• Set up seamless failover for scheduled backups in an MSCS environment.The Exchange Application Client communicates with Tivoli StorageManager using its application program interface (API) and with anExchange Server using the Exchange API.

The Exchange Application Client must be installed on the same machine asthe Exchange Server. However, the Exchange Application Client must be ableto connect to a TSM server which can run on any supported operatingsystem. The Exchange Application Client can compress Exchange databefore sending it to the TSM server. The Exchange Application Client alsoruns in a Microsoft Cluster Server environment.

1.2.2.2 Tivoli Data Protection for MS SQLTivoli Data Protection for Microsoft SQL Server (referred to as the SQLApplication Client) is an application that allows you to perform online backupsand restores of Microsoft SQL databases to Tivoli Storage Manager storage.The SQL Application Client helps you protect and manage SQL Server databy making it easy to:

• Perform full database and transaction log (incremental) backups.

• Perform a restore of a full database and any number of associatedtransaction logs.

• Delete an SQL database backup from Tivoli Storage Manager storage.

• Back up any SQL database to any Tivoli Storage Manager server withdrag-and-drop ease.

• Set TSM connection information options to Tivoli Storage Managerservers.

• Set Tivoli Storage Manager security and performance options.

• Obtain online context-sensitive, task, and concept help.

• View online documentation for the SQL Application Client.

• Launch other Tivoli Storage Manager programs and related systemapplications.

• Automate scheduled backups.


• Automate deletion of old backups.

• Back up and restore a Microsoft SQL Server running in a Microsoft ClusterServer (MSCS) environment.

• Set up seamless failover for scheduled backups in an MSCS environment.

The SQL Application Client communicates with Tivoli Storage Manager usingits application program interface (API) and with an SQL Server using the SQLDB-Library.

The SQL Application Client must be installed on the same machine as theSQL Server, not the Tivoli Storage Manager server. However, the SQLApplication Client must be able to connect to a Tivoli Storage Manager server(version 2 or higher) running on any supported operating system platform.The Tivoli Storage Manager server does not need to be run on Windows NT.The SQL Application Client also supports operation in a Microsoft ClusterServer environment.

1.2.2.3 Tivoli Data Protection for OracleThe Oracle Backup Agent supports these databases:

• Oracle7 databases with the Enterprise Backup Utility (EBU)

• Oracle8 databases with the Recovery Manager (RMAN)

The Oracle7 EBU and Oracle8 RMAN perform backup (online and offline) andrestore (online and offline) of Oracle databases. After the Oracle7 EBU orOracle8 RMAN initiates a backup or restore, the Oracle Backup Agent acts asthe interface to Tivoli Storage Manager. The Tivoli Storage Manager serverthen applies its storage management functions to the data, which can bedone while users are working, with minimal disruption. The Oracle BackupAgent can work with any Version 3 ADSM or Version 3.7 Tivoli StorageManager server. The Oracle Backup Agent translates the Oracle7 or Oracle8API commands into Tivoli Storage Manager API calls.

1.2.2.4 Tivoli Data Protection for Lotus DominoThe Tivoli Data Protection module for Lotus Domino is a Lotus Dominoapplication that provides backup and restore of individual documents within aLotus Domino database, or an entire database with folders, documents,forms, and views. Each Lotus Domino database can consist of two types ofnotes:

• Non-data notes such as forms, folders, and views

• Data notes such as documents


A Lotus Domino database is stored on a server or client workstation as asingle structured file, usually with a .NSF file extension. Domino databasesare complex logical structures that appear to traditional storage managementtools, such as the Tivoli Storage Manager Backup-Archive Client, as singleworkstation files. It runs only at operating system level and will always backup the entire database. Whenever a single document is updated within adatabase, an incremental backup updates the entire database, because thedatabase modification timestamp has changed.

Most backup products can perform incremental backups of files, exceptDomino. The Tivoli Data Protection module incrementally backs up Dominodatabases on a document level to allow the administrator to retain a certainnumber of backup versions for each document.

The Tivoli Data Protection module for Lotus Domino application uses theLotus Domino API to communicate with the Lotus Domino databases. TheTivoli Data Protection module uses the Tivoli Storage Manager API tocommunicate with the Tivoli Storage Manager server. The Tivoli StorageManager API is configured in a way similar to the standard backup-archiveclient. It has its own dsm.opt client user options file, which contains standardoptions such as node name, connectivity options, and include-exclude filterlists. The syntax for the include-exclude list for the Lotus Domino is differentfrom the backup-archive client. It is highly recommended that you use aunique node name for the Lotus Domino Agent. Then the Tivoli StorageManager server will view the application as a separate, self-containedworkstation client.

The Lotus Domino Agent helps you protect your Lotus Domino databases byusing the backup and recovery services of Tivoli Storage Manager. Functionsare available that enable you to:

• Incrementally back up only those portions of a database that havechanged since the last back up, such as new or changed documents,forms, and views.

• Restore selected documents from a database (graphical user interfaceonly).

• Restore documents that are deleted but not yet purged from a database.

• Restore an entire Lotus Domino database.

Some of these tasks can be performed by using a graphical user interface(the Lotus Notes Workspace). Others can be accomplished through acommand-line interface.


1.2.2.5 Tivoli Data Protection for SAP R/3Tivoli Data Protection for SAP R/3 lets you manage backup storage andprocessing independently from normal SAP R/3 operations. Tivoli DataProtection for SAP R/3 and Tivoli Storage Manager provide reliable, highperformance, repeatable backup and restore processes that let systemadministrators manage large volumes of data more efficiently. Tivoli DataProtection for SAP R/3 allows system administrators to follow SAPprocedures and use the integrated SAP utilities for backup and restore. Theseutilities are SAPDBA, BRBACKUP, BRArchive and BRRestore. Other SAPfiles are backed up using Tivoli Storage Manager standard techniques for filebackup and restore, for example, incremental backup, file filtering, andpoint-in-time recovery.

1.2.3 Other Tivoli modules for managing applicationsTivoli provide modules for managing appliactions. We outline those currentlyavailable below:

1.2.3.1 ADSMPlus for Tivoli module for TSM 3.7The ADSMPlus for Tivoli module provides an integration of the TME 10 withTivoli Storage Manager software.

Note: ADSMPlus for Tivoli Version 3.7 will work only with Tivoli StorageManager (formerly known as ADSM) Version 3.7 and not with any earlierversions of ADSM.

This integration allows centralized management of the Tivoli StorageManager application across a multi-platform network. This module providesthe following features for managing the Tivoli Storage Manager application:

• Icons for launching the Tivoli Storage Manager application

• Subscription lists for clients and servers

• Monitors for TME 10 Distributed Monitoring

• Tivoli Storage Manager tasks and jobs

1.2.3.2 Tivoli Manager for MS ExchangeTivoli Manager for Exchange (Manager for Exchange) provides a centralizedsystem management tool for Microsoft Exchange servers on the Tivoliplatform. Manager for Exchange facilitates the management of MicrosoftExchange Servers on endpoints and the installation of Microsoft Exchangefile packs on clients.


Manager for Exchange can be used with the following optional products:

• Tivoli Enterprise Console (TEC):

Receives, filters, and forwards selected events to an event server forfurther processing.

• TEC event adapter for Windows NT (NT event adapter):

Converts Microsoft Exchange events to the TEC format.

• Tivoli Software Distribution:

Used to distribute and deploy software across multi-platform networks.

Manager for Exchange provides the following features to enable you toperform system management functions for Microsoft Exchange:

• Tasks to control and automate Microsoft Exchange administrativeactivities on endpoints

• A selection of monitors for key performance and availability statistics forMicrosoft Exchange Servers

• Configuration files for the NT event adapter to receive, filter, and forwardselected events to the TEC

• Automated Microsoft Exchange client distribution

• Data input to Tivoli Decision Support

1.2.3.3 Tivoli Manager for MS SQLTivoli Manager for Microsoft SQL Server complements existing Microsofttools for Microsoft SQL Server and adds features so you can manage a largenumber of database servers in a distributed environment. This productconcentrates on those tasks that can be defined and deployed by genericmethods. It reduces the complexity of managing large distributed databaseenvironments and frees database administrators (DBAs) to concentrate onthe non-generic issues associated with each of the individual servers.

This product provides the ability to manage and monitor Microsoft SQLServers by providing extensions to TME 10 Framework, DistributedMonitoring, Enterprise Console, and Global Enterprise Manager (GEM). Itincludes the MSSQLManagerTasks library and the MSSQLServer andMSSQLDatabase monitoring collections.

These tools enable you to manage distributed Microsoft SQL Servercomputing resources effectively.


Using Tivoli Manager for Microsoft SQL Server, you can do the following:

• Register the Microsoft SQL Server with Tivoli.

• Automate repetitive DBA operations across all database servers ordatabases. Tivoli tasks work on multiple servers or databases in a singleaction.

The tasks provided can:

• Ensure that optimal reading of data by monitoring and correctingfragmentation.

• Ensure that query plans are based on the correct statistics.

• Ensure space availability on log and data devices.

• Run standard maintenance commands and check for corruption.

• Check database and server configuration settings.

• Keep up-to-date recovery information.

• Back up databases and log files.

• Use the MSSQLServer and MSSQLDatabase monitoring collections forglobal database server and database availability and performancemonitoring facilities. The monitors can be configured to respondautomatically to problems. They can run tasks to perform correctiveactions.

• Alert administrators to performance problems or serious errors andfailures. Monitors can notify administrators in a number of ways. They canalso send events to the Tivoli Enterprise Console (TEC).

• Integrate with the Tivoli Storage Manager backup tool to take advantage offeatures such as secure backups and backup device management.

• Integrate with Tivoli GEM (Global Enterprise Manager) to allowbusiness-system views of managed servers and databases.

1.2.3.4 Tivoli Manager for OracleWith Tivoli Manager for Oracle - Framework, you can manage thetablespaces, datafiles, rollback segments, and redo logs in an Oracledatabase, and manage sessions and instances associated with a database.Tivoli Manager for Oracle - Framework enables you to use the other TivoliManager for Oracle products to manage your Oracle environment. Themodule consists of the following products:

• Tivoli Manager for Oracle - Framework

• Tivoli Manager for Oracle - Distributed Monitoring


• Tivoli Manager for Oracle - User Management

1.2.3.5 Tivoli Manager for Lotus DominoThe Tivoli Manager for Domino (Manager for Domino) allows the Tivoli orDomino system administrator to manage Lotus Domino within a TivoliManagement Environment (TME). That is, you can manage Domino serversfrom the same Tivoli Framework desktop where you control TivoliManagement Regions (TMRs).

• Manager for Domino Monitor Collections offer a wide range of monitoringoptions, including monitors for all statistics in the events4.nsf databasethat return numeric values. Program status monitor check the state ofDomino add-in tasks.

• Manager for Domino makes use of Tivoli Software Distribution filepackages to customize and distribute Notes client software.

• Manager for Domino uses TEC rules and classes to filter and manageDomino events. Using Event Server rule base functionality, you can modifyor extend Manager for Domino rule sets to meet your processingrequirements. You can also assign Domino events to an event group, andthen view these events on one or more Event Consoles.

1.2.3.6 Tivoli Manager for SAP R/3A typical SAP R/3 environment includes one or more R/3 systems, whereeach R/3 system consists of one database server and one or moreapplication servers. The R/3 application servers run on the UNIX andWindows NT operating systems. The database servers run on the UNIX,Windows NT, and OS/390 operating systems.

The Tivoli management environment consists of a Tivoli Management Region(TMR) server, a Tivoli Event Console (TEC) server, and multiple installationsof the Tivoli Manager for R/3 product.

Manager for R/3 operates at both the machine level and the R/3 system level.Management at the machine level is done via monitors provided with theTivoli Distributed Monitoring product. These monitors provide status on themachines and daemons.

Management at the R/3 system level is done via monitors, event adapters,and tasks provided with the Manager for R/3 product. Manager for R/3represents each R/3 system and server as a Tivoli object. Each object is aspecial type of Tivoli endpoint that enables the Manager for R/3 to distributemonitors and tasks directly to the endpoint. As with any Tivoli endpoint, you


can run a task against one or more application servers across the R/3systems that the TMR server manages.

Manager for R/3 provides two event adapters for R/3 application servers. Theevent adapters are specific to each application server. You must configureeach event adapter for each application server. R/3 application servers arethe primary resources used in managing the R/3 system. The applicationservers obtain most performance metrics. Manager for R/3 obtainsperformance information about the R/3 database server through calls madeto one of the R/3 system's application servers. This allows the Manager forR/3 to gather database information for all platforms, including DB2 onOS/390.

1.2.4 Tivoli Storage Manager event handling

1.2.4.1 Events from Tivoli Storage Manager to TECIn its current release, Tivoli Storage Manager supports the forwarding ofevents to the Tivoli Enterprise Console (TEC). This happens in the same wayas other event receivers such as activity log or console. This includes thestandard messages originating from the Tivoli Storage Manager itself and itsclients.

1.2.4.2 Events from multiple Tivoli Storage Manager servers to TECBy using the central event logging feature, which is included in the enterprisefeatures of Tivoli Storage Manager, you can use a central server to forwardthe events originating from all Tivoli Storage Manager servers in yourorganization.

1.2.4.3 Events from Tivoli Data Protection for Applications to TECAnother feature which was introduced in Version 3.7.3 is the forwarding ofevents originating from the Tivoli Data Protection for Applications modules tothe TEC server. This finally enables you to monitor all the events related toTivoli Storage Manager from all sources in your enterprise network.

1.2.5 Tivoli Service DeskService Desk is a help desk software solution whose primary goal is toimprove the efficiency and effectiveness of a corporate service and supportoperation. It is a suite of three integrated applications:

• Tivoli Problem Management: This application, which is the coreapplication of Tivoli Service Desk, addresses help desk services related touser requests for problem resolution.


• Tivoli Change Management: This application addresses the operationalchanges associated with delivering IT services.

• Tivoli Asset Management: This application addresses issues surroundingcorporate assets.

1.3 System environment

These are the products we used in our lab environment:

• Framework 3.6.3 (TMR on AIX 4.3.3 ML2)

• Tier 2 Framework for Redhat Linux 3.6.1 on Redhat Linux 6.1,including Software Distribution, Inventory, and TEC Logfile Adapter

• Distributed Monitoring 3.6.1

• Distributed Monitoring UNIX Monitors 3.6

• Distributed Monitoring Universal Monitors 3.6

• TEC 3.6.2

• TEC Adapter Configuration Facility 3.6.2

• Inventory 3.6.2

• Software Distribution 3.6

• Software Distribution Historical Database 3.6

• Service Desk 6.0 on NT 4.0 SP5 using MS SQL 7.0 SP1 for database

• Storage Manager 3.7.3

• Storage Manager Clients 3.7.2

• ADSMPlus for Tivoli, Version 3.7, Revision 0

• Data Protection for MS SQL 1.1.1 on MS SQL server 7.0 SP1

• Data Protection for MS Exchange 1.1.1.0 on MS Exchange server 5.5 SP3

• Data Protection for Oracle 1.1 on Oracle server 8.1.5

• Data Protection for Lotus Domino 1.1 on Domino server 5.0

• DB2 5.2 on AIX 4.3.3 ML2 for TEC and Inventory database


These are the machines on which we installed Tivoli Endpoints and TivoliStorage Manager Backup/Archive Clients:

• AIX 4.3.3 ML2

• Windows NT 4.0 SP5 Server /Workstation

• Windows 2000 Server

• Solaris 7

• Redhat Linux 6.1 Kernel 2.2.12-20


Part 2. Using the individual modules

Part 2 covers the Tivoli Enterprise products, plus modules, Tivoli DataProtection for different applications and Tivoli Storage Manager. We do notcover the installation, and expect that the system is already installed andrunning.

We give you a description of individual modules starting with productarchitecture, concepts, definitions of components, how they work, and, at theend, examples of how to set them up. These examples are based on ourenvironment and can be different from the system environment in yourorganization.

Setting up Tivoli Enterprise requires a basic knowledge of Tivoli products,and, therefore, this may involve your Tivoli Enterprise administrator. We alsodiscuss how to configure Tivoli Storage Manager, which requires basicknowledge of Tivoli Storage Manager administration.

This part of the book will help you to get started, and, at the end, you shouldbe able to make use of the Tivoli Enterprise features that relate to TivoliStorage Manager.


Chapter 2. Tivoli Framework TME 10

In this chapter we give you a brief description of the Tivoli ManagementEnvironment 10 (TME 10) Framework, which is the base component for theTME 10 product line. In this chapter we cover:

• Framework architecture• Framework components• Framework configuration, with examples

2.1 Framework architecture

The TME 10 Framework provides a set of services or features used by theTME 10 applications installed on the Framework. See Figure 2.

Figure 2. Tivoli Framework

ManagedNode

ManagedNode

gateway

Task LibrariesQuery LibrariesRIMEndpointManagerScheduler

tasks

communicationtasks

communication

RDBMSinterfacemodule

RDBMS

Framework

End-point

End-point

End-point

End-point

End-point


Following are some examples of the services provided by the Framework:

• Task Library — A task library through which you can create tasks andexecute them on multiple TME 10 resources.

• Scheduler — A scheduler that enables the administrator to schedule allTME 10 operations, such as execution of the tasks created in the TME 10task library.

• Relational Database Management System (RDBMS) Interface Module(RIM) — This enables some of the TME 10 applications to writeapplication specific information to a relational database.

• Query facility — This enables an administrator to search and retrieveinformation from a relational database.

The introduction of the Gateway and the Endpoints enables a TivoliEnterprise installation to be three-tiered, as shown in Figure 2 on page 21.Tivoli Management servers communicate with Managed Nodes. ManagedNodes can host a Gateway to handle communication with Endpoints.Gateway controls all the communications with and operations on TivoliEnterprise Endpoints. Using fewer Managed Nodes and more Endpointsreduces the Tivoli Management server load for the following reasons:

• There is a limitation of 200 Managed Nodes per TMR.

• Endpoints do not have a client database to synchronize with the TivoliManagement server database.

• There are fewer Managed Node databases to synchronize with the TivoliManagement server database.

2.2 Framework desktop

The TME 10 desktop is the user interface that provides access to TME 10features and components. The desktop provides a central control to manageand organize the system management tasks of all modules. The desktop isavailable for Microsoft Windows and for other platforms having the X11environment or a graphical interface installed.

There is also a command line interface (CLI) for TME 10 that enables you toenter TME 10 commands.


2.2.1 Desktop windowThe desktop window is a graphical representation of TME 10 and providesstatus information of modules, objects, and resources. Windows are used tomove or copy the resources. See Figure 3.

Figure 3. Tivoli desktop — example of window

2.2.1.1 Desktop NavigatorThe Desktop Navigator provides filtering of the resources and keywordsearch. By using Navigator, you can go directly to the resource you would liketo see without going through other intermediate resources. Navigator can beaccessed from any collection window.

For an example of the Desktop Navigator dialog, see Figure 4.

Chapter 2. Tivoli Framework TME 10 23

Figure 4. Desktop Navigator

2.2.1.2 CollectionsA collection is a container that you can create and place on your desktop. Acollection can contain shortcuts that enable you to access resources. You canpopulate a collection by moving and linking objects.

Note: You can create a collection from the desktop only.

2.3 Framework components

This section includes brief descriptions of Tivoli Management Frameworkcomponents. In addition, it guides you through examples of how to defineadministrators, tasks, and jobs, as well as how to make a profile anddistribute it to subscribers.

The basic components of TME 10 are:

• Policy regions

• Administrators

• Profiles

• Profile managers

• Task libraries


• Notice groups

• Query libraries

• Endpoint manager

• Scheduler

2.3.1 Tivoli Management RegionA Tivoli Management Region (TMR) consists of a TME 10 server and a set ofTME clients that it serves. After base installation of Framework on a system,that system becomes the TME server for the TMR. The TME serverinstallation process automatically allocates a unique 10-digit region numberthat originated from the TME license key during the installation. In addition,the administrator has to specify a region name for the initial region.

The most common types of TME clients are Managed Nodes and Endpoints:

• Managed Node

A Managed Node is a client on which the complete TME 10 Framework isinstalled. TME server can install a Managed Node remotely and add it tothe TMR. A Managed Node, which supports the majority of TME 10management applications, occupies a disk space of 200-300 MB.

• Endpoints

The Endpoints can execute methods sent to them by the Gateway, wherethey can then cache locally. Endpoints occupies a disk space of about5 MB.

2.3.2 Policy regionsA policy is a set of rules that are applied to managed resources. A specificrule in a policy is referred to as a policy method.

A policy region is a container of resources that share one or more commonpolicies. Resources belong to the policy region in which they were created ormoved to. Managed resources can be moved or linked symbolically from onepolicy region to another policy region, but you cannot copy managedresources.

2.3.3 TME administratorsAn administrator is a user that performs administration tasks inside TME 10.For example, on AIX, the root user installs TME and becomes the TMEadministrator.


Each administrator ID is associated with certain administrator “roles”. Rolesdefine administrator levels of authority. The possible authorization roles foradministrator that may be defined are:

• Super — Authority to perform any operation.

• Senior — Authority to create TME 10 resources. The senior role isrequired for configuration and policy tasks such as creating anadministrator or setting policy.

• Admin — Authority to manage and create system resources, such asassign a user item to a profile or changing the message of the day.

• User — Authority to view but not modify.

• Backup — Authority to perform TME 10 database backup.

• Restore — Authority to perform TME 10 database restore.

• Install product — Authority to install new TME management applications.

• Install-client — Authority to install new Managed Nodes within policyregions.

• Additional modules can define additional roles.

2.3.4 Profile managersA profile manager is a container that links a collection of profiles to a set ofsubscribers. Subscribers can be the following managed resources:

• Managed Nodes• Endpoints• Other profile managers

Profile managers are created within a policy region. Subscribers of theseprofiles can be from same policy region or other policy regions. An example ofthis situation could be Managed Nodes within a department or location whichare configured as subscribers to a profile manager within a policy region.Those profile managers can be subscribers to another profile manager.

2.3.4.1 ProfilesProfiles are collections of applications-specified information. A profile definesthe characteristics of the function to be performed.

For example, a software distribution defines the Courier file packageproperties. This would typically include the files to be distributed, their sourcelocations, and any pre-distribution or post-distribution functions to beperformed on the target workstation.


2.3.5 Task librariesTask libraries are collections of tasks that can be run on target nodes withinthe TMR.

2.3.5.1 TasksTasks are commands or functions that can be run on a target node orworkstation. Tasks can run on Managed Nodes, Endpoints, or a profilemanager which contains many other subscribers.

2.3.5.2 JobsJobs can be created in a task library (however, you must create a task beforeyou can create a job). A job is a task that is executed at specific managedresources. The execution information you specify when you create a jobincludes a list of task Endpoints on which the associated task will run andwhere the output will be displayed. Jobs can be run at predefined times byusing the scheduler.

2.3.6 SchedulerAn administrator may need to schedule a job to begin in a specific time framesome time in the future. The scheduler allows the administrator to schedulepreviously created jobs, as well as to do the following:

• Schedule jobs to run at specific times within a specified time frame.

• Schedule jobs to repeat a specified number of times at specified timeintervals.

• Schedule jobs to repeat indefinitely.

• Restrict scheduled jobs to run only at night, during the day, or every day,but only Monday to Friday, or on weekends.

• Schedule a job to run only once.

2.3.7 Notice groupsTME 10 management operations are logged and results are displayed as“notices”. Notices are the response mechanism for the administrators tomonitor the status of management operations. Notices are sent to applicationor operation-specific notice groups. Notice groups stores notices sorted byfunction of modules. For example an administration notice group receivesnotices from operation such as creating a new administrator.


2.4 Framework configuration: examples

In this section we show you how the Framework can be configured.

2.4.1 Defining administratorsAn existing administrator with a senior function role can define anotherTME 10 administrator. Our example is performed by a TME administrator. Youcan create a new administrator from the desktop or the command line. Here isan example using desktop.

1. Select Create Administrator from administrator icon pop-up menu todisplay the Create Administrator dialog. See Figure 5.

Figure 5. Create Administrator

2. Enter the name of the administrator (in our example, “melinda”).

3. Enter the administrator’s user login name.

4. Enter the administrator’s group name in the Group Name text field.

5. Then click on the Set TMR Roles.... button to set the function roles for theadministrator. TMR roles are roles for the whole TMR. Resource roles areroles for specific resources which are superseded by TMR. In the Set TMRRoles dialog, it is possible to select admin, senior, user and other rolesfrom the available Roles list. The combination of these roles is sufficientfor the tasks an administrator can perform. To define an administrator, you


should at least have senior role; otherwise you cannot give someone elsethe role that you do not have yourself. After selection of a series of roles,click on Set & Close to return to the Create Administrator dialog. SeeFigure 6.

Figure 6. Create Administrator, Set TMR Roles

6. Click on the Set Logins... button to define the login names under whichthe new administrator will be able to start the TME 10 desktop or issueTME commands. The login name can be one of the following forms:

- username- username@ManagedNode- NTdomain\username- NTdomain\username@ManagedNode- Kerberos-name:realm

If you want more than one login name, repeat this step for each login that youwish to add. See Figure 7. The user must exist on the Managed Nodes onwhich you are going to run the desktop or issuing the commands. For moreinformation, refer to the Framework User’s Guide, GC31-8433.


Figure 7. Create Administrator, Set Login Names

7. Click on the Set Resource Roles... button to specify individual resourceroles for the administrator “melinda”. Again, there are different rolesavailable for different resources. For example, you can choose User,admin, and Senior for the scheduler resource and repeat this function.

Click on Set & Close to return to the Create Administrator dialog. SeeFigure 8.


Figure 8. Create Administrator, Set Resource Roles

8. Click on the Set Notice Group... button to set the notice groups for thisadministrator. You can select a set of different notice groups. See Figure 9.


Figure 9. Create Administrator, Set Notice Groups

9. Click on the Create & Close button to create the administrator, “melinda”.The new administrator’s icon is displayed in the Administrators window.See Figure 10.

Figure 10. Create Administrator, administrator desktop

The preceding steps have created the administrator. This administratordesktop is now ready to start. The final step of setting up the TMEadministrator “melinda” is to add resources to its desktop. This is done by


dragging resource icons from an existing desktop and dropping them onto thenewly created administrator icon.

The new TME administrator “melinda” is now defined and ready to use.

2.4.2 Creating tasks and jobs

2.4.2.1 Create task libraryA task library enables you to create tasks and jobs that can be run on one ormore managed resources in a network. You can create multiple task librarieswithin each policy region.

Before creating the task, one or more executable files or scripts thatimplement the operation associated with the task must exist. We created atask library with the name “acme-task” within the policy region “acme-region”.A task library must be an enabled managed resource of this policy regionbefore you can create it. See Figure 11.

Figure 11. Task Library, acme_task

2.4.2.2 Creating a taskExample of creating a task named df (this task will run the df command onUNIX platform). See Figure 12.

1. Double-click on the icon of the task library. Select the Task... option fromthe task library’s Create menu to display the Create Task dialog.

2. In the Task Name field of the Create Task window, enter the name of thetask. Choose the platform on which you would like to run the task. If youhave a generic executable, for example, a shell script can be run onmultiple architectures.


Figure 12. Create Task

3. Then you choose the platform you want the task to run from the availableplatform list. Framework displays the Executable for Task dialog for thespecified platform, in which you can enter the name of the managed nodethat contains the executable for the chosen platform in the On Host textfield, and the path name in the Path to File text field — for example, “IBMRS/600 /AIX 4”, if your task is going to run at this platform.

4. In the Role Required to Execute Task list, select the administration rolerequired to start this task. For example, selecting admin will permit anyadministrator with that authority to execute the task.

5. Under Execution Privileges, in the User Name field, insert the user IDunder which the task should run on the target node. The default value forthis field is ‘*’, which specifies that the task should run under the ID of the


administrator executing the task. In our example, we chose “$root_user”as user name, and “$root_group” as group name, as a generic substitutefor administrators at different platforms.

6. Click on Create & Close button to create the task and return to the TaskLibrary window.

2.4.2.3 Create a job1. From the Task Library, in our example, “acme_task” dialog, select Job...

from the Create action bar menu. See Figure 13.

Figure 13. Task Library, acme_task

2. In the Create Job dialog, enter the Job Name “df-job’”.

3. Select the task name associated with the job from the Task Namescrolling list.

4. For execution mode choose for example, if you choose Parallel, the jobwould be run in parallel on all selected Managed Nodes, Endpoints, orprofile manager. The other possibility is Serial, so that the job will be runserially on all selected Managed Nodes, Endpoints, or profile manager.See Figure 14.


Figure 14. Create Job menu

5. For output destination, you can select Display on Desktop if you want thejob output to be displayed on the Tivoli desktop, or Save to a File if youwant the output to be saved to a file, and enter the name of the ManagedNode or Endpoints on which to save the output in the On Host text field.

6. You can run the job on one or more Managed Nodes or Endpoints byselecting them from the Available Task Endpoints list.


7. To run the job on all subscribers of a specified profile manager, choose theprofile managers from the Available Profile Managers scrolling list.

2.4.2.4 Schedule a jobTo schedule a job, do the following:

1. You can schedule a job by dragging and dropping the job icon onto thescheduler icon. The Framework then displays the Add Scheduled Jobdialog.

2. Enter the job Label in the Job Label text field.

3. Enter the scheduled date in the Schedule Job For field.

4. Enter the scheduled time in the Hour and Minute option menus. You canenter the number of times you wish the job to repeat, and the time intervalfor repeats. See Figure 15.


Figure 15. Schedule a job

5. Enter the action that should occur when the job is finished.

6. You can set Retry/Cancel/Restriction Options for the job. With the Retryoption, you can specify that a job can retried if it is unable to start at thescheduled time. With the Cancel option, you can specify that a job shouldbe cancelled if it does not start within a specified time period after itsscheduled stat time. With the Restriction option, you can restrict a job torun during the day, at night, during the week or on weekends. See Figure16.


Figure 16. Schedule a job, Set Retry/Cancel/Restriction

7. Press the Schedule Job and Close button to schedule the job and returnto the desktop.

2.5 Hints and tips

• When assigning authorization roles to an administrator, to ensure thatsenior system administrators can perform tasks at their authorization leveland below, assign these administrators all authorization roles below theircurrent level.

• For example, to ensure that an administrator with the senior role canperform all tasks at the senior level and below, assign this administratorthe senior, admin, and user roles.


Chapter 3. Tivoli Distributed Monitoring

In this chapter, we cover the concepts of Tivoli Distributed Monitoring. Wealso show you, by example, how a Tivoli Storage Manager administrator couldbenefit from using this product.

3.1 Tivoli Distributed Monitoring concepts

Figure 17 shows how Tivoli Distributed Monitoring interacts with otherFramework components. This is an application which uses Tivoli Frameworkto interact with target machines, which can be either Managed Nodes orEndpoints. It distributes monitors from the TMR server to the targets tomonitor certain conditions. Based on trigger levels, it can execute actionssuch as forwarding events to the Tivoli Enterprise Console.

Figure 17. Tivoli Distributed Monitoring

End-point

End-point

End-point

End-point

End-point


ManagedNode

ManagedNode

gateway

TivoliDistributedMonitoring

distributemonitors

send events

Framework


RDBMS

execute monitorscollect values


Before we proceed with some examples of how to use Tivoli DistributedMonitoring, we explain what components it consists of, and how they interactwith each other.

3.1.1 Tivoli Distributed Monitoring componentsTivoli Distributed Monitoring is based on the Tivoli Framework architecture. Itprovides fundamental tools for monitoring resources on the following targets:

• Managed Nodes• TMA Endpoints• Distributed Monitoring Proxies (DM proxies)

DM proxies are non-Tivoli entities that function as subscribers for TivoliDistributed Monitoring profiles. Since they are not related to Tivoli StorageManager in any way, we do not cover them in this book.

Tivoli Distributed Monitoring has two main install images:

1. Tivoli Distributed Monitoring package — This install image must beinstalled on the TMR server, the Managed Nodes that need to perform themonitoring functions and the Endpoint Gateways managing the TMAEndpoints you want to monitor. This package enables the following twofunctions:

- Distributed Monitoring engine — One process on a Managed Nodeand TMA Endpoint that controls and oversees the resources as definedin the monitors of Distributed Monitoring profiles. It determines whetherthe monitor should be triggered and runs most of the automatedresponses. The Distributed Monitoring engine runs autonomously oneach monitored system, which makes more efficient use of networkresources. The Distributed Monitoring engine performs the necessarychecks on behalf of the monitors at the specified intervals.

- Distributed Monitoring Gateway — One process on an EndpointGateway that communicates with the distributed monitoring engine onthe TMA Endpoint. It caches the collection data, forwards the events toTEC, bundles response data from Endpoints, and handles non-localresponses directly or by passing to another process.

2. Monitoring collections — Monitors are grouped into monitoringcollections. A monitoring source represents a specific aspect of a systemthat can be monitored, such as percentage of disk space used. Theintelligence (code and parameters) that actually enables the performanceof these monitoring functions has to be available (installed) before amonitor can be defined. Tivoli and Tivoli partners provide predefinedmonitoring sources that monitor common system functions.


Figure 18 shows the interaction of Distributed Monitoring modules with theTMR server and the targets.

Figure 18. Interaction between Tivoli Distributed Monitoring and the TMR server

Distributed Monitoring was designed to run independently of the oservprocess, since not all monitored computers will be running this process. Forinstance, PC Managed Nodes and TMA Endpoints do not run an oservprocess.

Chapter 3. Tivoli Distributed Monitoring 43

Since oserv implements the centralized Tivoli Framework scheduler, TivoliDistributed Monitoring uses its own distinct scheduler.

3.1.2 MonitorsMonitors are records of a Distributed Monitoring profile, thus, multiple (usuallyrelated) monitors can be handled with one profile defined centrally on theTMR server.

After distribution of the DM profiles, all the monitors’ activities are maintainedby a local Distributed Monitoring engine.

The administrator can monitor the status of monitors using an indicatorcollection. Within an indicator collection, you can assign an indicator icon to aDistributed Monitoring profile, and when any monitor of that profile detects aproblem, the gauge on the corresponding indicator icon is raised to theappropriate warning level. An indicator collection and indicators provide aneasy and centralized method of checking on all the Distributed Monitoringprofiles in a policy region. However, if you have the Tivoli Enterprise Consoleinstalled in your TMR, this is where your messages should go.

The following steps are required to create a monitor:

1. Create a Distributed Monitoring profile in a profile manager. (If you areusing Endpoints, the profile manager must be in dataless mode.)

2. Add a monitor to the Distributed Monitoring profile.

3. Choose the targets that will be monitored and subscribe them to theprofile manager that contains your monitor.

4. Send (distribute) a copy of the profile to the selected subscribers inorder to monitor a target.

3.2 Examples

We now show some examples how Tivoli Distributed Monitoring can be usedto monitor Tivoli Storage Manager servers. These examples are not acomplete solution that fits every environment. They are customized to ourgiven lab infrastructure and can be extended in any way.

Tivoli provides a variety of predefined monitors, and there are very fewconstraints for extending it to your special needs. So don’t ask what TivoliDistributed Monitoring can do, ask yourself what you need! Before configuringmonitors, you should take some notes on what you are going to monitor andwhat should happen, if these conditions are met.


The first thing to do is to create a Distributed Monitoring profile in a profilemanager. If you are using Endpoints, be sure to have dataless mode enabledon the profile manager. Also verify that the Sentry Profile is among themanaged resources of your current policy region.

In our example we use just one profile which holds multiple monitors relatedto Tivoli Storage Manager server on the AIX platform. We named the profiledm_tsm_server_aix, as seen in Figure 19.

Figure 19. Profile to monitor Tivoli Storage Manager and subscribed Endpoint


In order to distribute your profile to machines, you have to subscribe them tothe profile manager. Here, the monitored host is palana, which is our TivoliStorage Manager server on AIX.

The examples include four monitors to check the status of the Tivoli StorageManager server (Figure 20):

1. Available swap space

This monitor checks the remaining megabytes in the swap space.

2. Daemon status

This monitor looks after the dsmserv daemon. It will trigger when the TivoliStorage Manager application is down.

3. Load average

This monitor checks the load average of the server. If it is too high, youcan tell whether there are zombies or very time-consuming processes.

4. Numeric script

This is an example of a complete custom monitor. It uses a command linescript which polls certain conditions from Tivoli Storage Manageradministrative interface (dsmadmc).

Figure 20. Monitors inside Distributed Monitoring profile


We will only cover in depth the daemon status and the numeric script. Theother two are mainly the same and should only give you an idea of what elseyou can do. Again, there is almost nothing you can’t monitor, so first thinkwhat makes sense in your environment, what saves you time, and which dailytasks can be automated, and then go to implementation.

3.2.1 Monitoring the status of the dsmserv daemonOpen the desired profile. If you click the button add monitor, you will beprompted for the type of monitor you want to add. Choose Unix_Sentry andthen daemon status in order to monitor the Tivoli Storage Manager daemon.You have to fill in the name of the daemon in the field provided — in our case,dsmserv. After clicking add empty, you will see the screen shown inFigure 21.


Figure 21. Monitor daemon status of Tivoli Storage Manager

You will now have to define the trigger levels and the according responses. Ifyou are monitoring a daemon, you have only two possible conditions: up ordown.

3.2.1.1 Response levelsTivoli Distributed Monitoring provides five different levels of response:

1. Critical (trigger level can be defined)

2. Severe (trigger level can be defined)

3. Warning (trigger level can be defined)

4. Normal (if none of the above conditions are met)


5. Always (triggers every time the monitor is executed)

Additionally, you have several criteria to define these trigger levels. Thesedepend on which kind of monitor you have — for example, for daemon status,you might have the following monitor criteria:

• Is up/available

• Is down/unavailable

• Becomes unavailable

• Becomes available

We prefer the criteria becomes available and becomes unavailablebecause these only generate an event if the status is changing. So you onlyget a message once. Otherwise, every time the monitor is executed, it willgenerate a message. Imagine a condition where the monitor is executedevery minute, and the event generates an E-mail from Friday evening untilSunday morning. Your mailbox probably will not be capable of holding all themessages!

So, in our case, we chose critical when the daemon becomes unavailableand warning if it becomes available again. This will give you feedback whenthe daemon is up again. If someone has restarted the daemon, you will stillknow that is was down.

3.2.1.2 ActionsThe available actions that can be executed if a certain condition is met arelisted below:

• Send Tivoli notice: This will post a message into a notice group.

• Popup: This will create a message on the specified administratorsdesktop.

• Change icon: This will change the icon of an indicator collection.

• Tasks: Any defined Tivoli task can be executed.

• Send E-mail to: Send an e-mail to the specified address(es).

• Log to file: Writes the event into a log file on any host.

• Run program: Runs any executable on any host.

• Send enterprise console event: Generates a Tivoli Enterprise Consoleevent at a certain severity level.

Since we are having a Tivoli Enterprise Console server in our environment,this is the suggested way of treating events. On the TEC server these events


are being processed according to rules. This again can include tasks, mailsand so on. See the Tivoli Distributed Monitoring User’s Guide 3.6,GC31-8382.

3.2.1.3 SchedulingAdditionally, you have to specify the schedule of the monitor, for example,5 minutes. This can include exceptions on weekends, shift hours, and so on.See Chapter 6, “Tivoli Enterprise Console” on page 85.

3.2.1.4 User mappingTivoli provides a user mapping facility to take care of the different platformson which monitors can be run. There are variables which are mappedaccording to the platform known to the Tivoli Framework. The two predefinedmapping are:

1. $root_user

On a UNIX-platform, for example, this maps to root, and on a Windows NTplatform, it maps to Administrator.

2. $root_group

On an AIX system, for example, this maps to system, and on a WindowsNT platform, it maps to Administrative users.

With these mappings, you can select the user environment under which themonitors are executed on the targets. See Figure 22.

Figure 22. User and group ID to execute the monitors

If you need to customize or to add your own user/group mapping, you can dothis. See the Tivoli Framework 3.6 User’s Guide, GC31-8433.


3.2.2 Custom script monitorsThe next example we want to show involves reporting a certain condition via acustom script and integrating it into a Tivoli Distributed Monitoring monitor.

3.2.2.1 Defining shell scriptsIn this example, we used one of the sample scripts provided by Tivoli StorageManager. You can import these scripts to your Tivoli Storage Manager serverby running: dsmserv runfile /usr/tivoli/tsm/server/webimages/scripts.smp

This will provide you with some sample scripts which can be used to monitorspecific conditions inside your Tivoli Storage Manager.

The one we chose is q_scratch_stg, which gives back the percentage ofallowed scratch volumes used in a storage pool via an SQL select statement.It returns the value in a numeric figure, which then can be monitored bysetting triggers to the response levels in Tivoli Distributed Monitoring.

The first step consists of writing a shell script which logs in to Tivoli StorageManager server using the batch mode of the administrative command-lineinterpreter dsmadmc. For security reasons, it is suggested that you create anunprivileged operator account in your Tivoli Storage Manager for thesemonitoring issues. The script then passes the command to run the script, andthe returned value is piped through some shell commands to get only thedesired numeric figure.

#!/bin/kshdsmadmc -id=tivoli -password=tivoli "run q_scratch_stg tapepool" \| grep TAPEPOOL | tr -s " "|cut -d " " -f2

To test the script, execute it on the shell prompt first. It should look like this:

brazil:/ > ./monitor.sh1.000

3.2.2.2 Using shell scripts in a monitorNow, to import this script into Tivoli Distributed Monitoring, we add a newmonitor from the universal monitoring collection with the name Numericscript. Then you have to provide the full path for the script you created. Afteradding it, you should get a screen like the one shown in Figure 23.


Figure 23. Universal numeric monitor with custom script

3.2.2.3 Response levelsAs in the previous example, you can now set the triggers and the accordingresponse levels and actions. Note that numeric triggers have differentcomparative patterns than, for example, the daemon status monitor. You candefine the trigger levels by these criteria:

• Greater/less than

• Equal/not equal to

• Increase/decrease

• And many more


Again we encourage you to use increase/decrease instead of greater/lessthan, to keep the number of events at a lower level.

3.2.2.4 Distribution actionsIf you deploy a custom script in a monitor, this script needs to be copied to thetarget machine where the monitor is supposed to run. Tivoli provides a way todo this at the profile level. You can define distribution actions where you caneither copy file(s) and/or run program(s). In our case, we need to distributeour script to the target machines. See Figure 24.

Figure 24. Distributing a custom script

You should be aware that these files are being copied as the user nobody,group nobody. So make sure your destination directory has write access forthis user.

The less events you generate, the more you can focus on the reallyimportant ones. You shouldn’t produce as many events as you can. Theskill is to extract only the information that needs (automated) action, and toreport only the events that need attention from a human administrator. Allothers (such as informational messages) can go into the log of theapplication or the operating system, but should not go into Tivoli.

General rule for events


3.3 Hints and tips

• Having an unprivileged, operator account on Tivoli Storage Manager formonitoring purposes makes it more secure.

• With custom monitors which are using dsmadmc and select commands,you can get any information out of Tivoli Storage Manager.

• If you have Tivoli Enterprise Console, forward your events instead ofacting in TDM.

• Be careful when using automated tasks to resolve problems.

• Don’t forget to use distribution actions to distribute your custom scriptsto Endpoints or Managed Nodes.

• Scripts are being distributed under user nobody. So be sure this user canwrite to the directory of the target machine.

• Using increases/decreases beyond will generate only one event insteadof every time the monitor fires when using greater/less than.


Chapter 4. Tivoli Software Distribution

Tivoli Software Distribution is the key component used to install, configure,and update software on network systems. It can be used for distributing anddeploying software across multi-platform networks.

4.1 Overview of Tivoli Software Distribution

Tivoli Software Distribution is part of the Tivoli Framework. It uses itscomponents to distribute software and to report the results back to theFramework and other modules. The Tivoli Software Distribution module usesseveral objects for distributing software. See Figure 25.

Figure 25. Tivoli Software Distribution

4.1.1 Source hostAn object from which software is updated is called the source host. You canuse any UNIX or Windows NT Managed Node in the same managementregion, after installation of Framework and Software Distribution.

End-point

End-point

End-point

End-point

End-point

ManagedNode

ManagedNode

gateway

TivoliSoftwareDistribution

distributepackages

TivoliEnterpriseConsole RDBMS

interfacemodule

RDBMS

Framework

distribute packages


4.1.2 TargetTivoli Software Distribution supports the distribution of file packages andautopacks on Managed Nodes, PC Managed Nodes, Netware ManagedSites, and Endpoints. Endpoints are connected to an Endpoint Gateway tothe rest of the Tivoli environment. The Endpoint Gateway uses multiplexeddistribution (MDist) for distributing the software to Endpoints.

4.1.3 RepeatersA repeater is an object in Tivoli Software Distribution used for multiplexeddistribution service. The TMR server itself is, by default, the repeaterdistribution server for all hosts in the TMR. Endpoint Gateways areautomatically repeaters for their Endpoints.

For performance-effective software distribution, you need to create a repeaterhierarchy that reflects the network topology. By default, the TMR server isautomatically set as a repeater. Endpoint Gateways are also repeaters fortheir Endpoints. To minimize network and server loads, also consider puttinga Managed Node as a repeater on each side of a slow network link.

This allows you to avoid copying binaries across slow links multiple times. Ifyou are always using specific servers as source hosts, from a performancepoint of view, it is desirable to use repeaters. Also, if the repeater contains toomany clients, you need to distribute the load among multiple repeaters,according to our network topology.

4.1.4 File packageA file package is a Tivoli Software Distribution object that contain referencesto the files and directories for distributing, and rules on how to apply thesefiles and directories.

Nested file package: In a file package, you can include another file package,which creates a nested file package. You use this option for distributing filesfrom more than one source host, to run different configuration programs fordifferent parts of a single distribution, or to distribute sets of files with differentproperties. There is no limit on the number of nested file packages.

4.1.5 AutopackAutopack is a similar object as a file package. It provides a faster and easierway for creating a file package on Windows platforms. With the autopackutility, you automatically create a list of files, which needs to be distributed,and you can record registry changes, desktop icons, and profile changes.


4.2 Installation

Using Tivoli Software Distribution, first you prepare the package to bedistributed; and second, you distribute the package (possibly multiple times).For detailed steps, refer to Figure 26.

Figure 26. Tivoli Software Distribution process

The administrator transfersthe autopack file to theSource Host.

The administrator:Creates the SD profiles,identifies the targets, anddistributes the SD profilesto the targets.

The administrator createsthe autopack files on Prepmachines.

1

8

32

63

4

63

5

7

4

33

4

8

Connection to SourceHost and transfer of data

Chapter 4. Tivoli Software Distribution 57

The numbers in Figure 26 refer to the numbered steps below:

1. Depending on your requirements, you first prepare a file package or anautopack. For an autopack, we recommend that you select a machine witha clean installation of the operating system. In the picture this machinesare labeled as Prep Machines. You will be installing the Autopack ControlCenter on these machines and building an autopack of files, which mustbe included in a software distribution profile. The machine on which youbuild an autopack is not necessary a part of the Tivoli environment.

2. You now transfer the autopack files to the source host.

3. The next step is creating a software distribution profile. For this, you needa policy region which has the file package, autopack, and profile managerset as managed resources. In this policy region, you choose an existingprofile manager or are creating a new one. A profile manager is acollection of profiles and subscribers. You create an autopack or a filepackage profile and distribute the profile immediately or schedule thedistribution of profile. The profile manager can also be distributed orscheduled. The profile itself does not contain data, only references andrules for files which reside on the source host. A part of the profileproperties are actions which can be executed before or after distribution orupon a commit request. The notification options are set on that level aswell.

4. Actions before distribution are executed on the targets.

5. The Managed Node communicates directly with the source host, and thetransfer of data from the source host to the Managed Node takes place.Upon distributing, actions (if defined) are performed on the ManagedNode.

6. The Endpoint Gateway hosting the TMA Endpoint communicates directlywith the source host and the transfer of data to the Endpoint Gatewayoccurs. Then the Endpoint Gateway uses the MDist mechanism todistribute the data to its associated target TMA Endpoints. Actions upondistributing (if defined) are performed on the TMA Endpoint.

7. Acting as a resource host for the PC, the Managed Node, where the PCManaged Node object resides, communicates directly with the source hostand the transfer of data to the Managed Node takes place. Then theManaged Node uses the MDist mechanism to distribute the data to itsassociated PCs designated as targets for the software distribution. Actionsupon committing (if defined) are performed on the PC.

8. Actions upon commit (if defined) are performed on the targets.


4.3 Setting the environment

For Tivoli Software Distribution, you must first install Tivoli SoftwareDistribution Server. This package is installed on the TMR server, wheresoftware distribution profiles are defined; and on any Managed Node, whereyou will create software distribution profiles, or where you want to runsoftware distribution commands from the command line. This package mustalso be installed on any Tivoli NetWare repeater if the distribution target is aNetWare PC hosted by a NetWare Managed Site.

The Tivoli Software Distribution Gateway package contains the softwaredistribution methods and needs to be installed on all Managed Nodes thatyou will configure as Endpoint Gateways. A machine running a TivoliManagement Agent needs to communicate to its assigned Gateway in orderto download any methods necessary to execute management operations.

4.3.1 ProfilesFor distributing software, you must first create a software distribution profile,which can be a file package or an autopack profile. See Figure 27.

Figure 27. Create Profile


4.3.1.1 File package propertiesAdditionally, you must set the properties of the software distribution package.Selecting the source host and the files and directories is the first step. Thenyou select any nested file packages. These packages must exist before youcan import them to a profile. You cannot create circular nested packages.

Under the general options section, you can choose whether the distributionshould stop if an error occurs.

For transferring complete directory structures, you check Descend intodirectories. In case you do not select this option and distribute directories,an empty one is created on the target.

Append source path to remote path allows you to append completestructures from the source to the target directory. Otherwise, only files ordirectories are created in the destination directory of the target.

With Perform compression on distribution, the data is compressed on thesource host before it is transferred to the target and decompressed on target.The next option is File Mode at Destination. By default, Preserve mode ofthe source files is selected. You can override this by selecting Changemode of source files to, and writing an octal chmod number. For PCs only,valid values are 4 for read, and 6 for read and write.

In the Log Information Options section, you can choose to send informationabout software distribution to a notice group, e-mail, or to a log file. In the editmenu are platform specific options. Depending on our distribution targets, youcan set actions Before Distribution, After Distribution, Upon removal orDuring Commit. See Figure 31 on page 63.

4.3.2 Creating packagesWe show below how to create packages ready for distribution.

4.3.2.1 AutopackFor autopack, you select Prep Machine and install Autopack Control Centerfrom Tivoli Software Distribution CD. See Figure 28. In the next step youcreate a baseline snapshot of our operating system. The system is beingscanned for files, directories and registry entries. See Figure 29.


Figure 28. Autopack main menu

Then you install the software you want to include in Autopack. After softwareis installed, you start Autopack Control Center again, and choose BuildAutoPack.

Figure 29. Scanning the system with Autopack Control Center


The system is being scanned again and changes are written to a set of files inthe destination directory. You might change some values in those filesmanually, especially in the .chg file, which contains a list of changes for thisAutopack. After that, you select build Autopack to create Autopack. AutopackControl Center then creates a .pak file, which contains all binaries, directoriesand registry entries in the directory that was specified as staging directory.See Figure 30.

Figure 30. Build Autopack

The next step is creating an Autopack profile. In the previously created profilemanager under Type, you select Autopack. In options for this profile, youselect from where the Autopack file should be copied and the directory andfile name on the source host.

4.3.2.2 Linux clientFor installation of the Tivoli Storage Manager backup-archive client for Linux,you use a file package. The client software is distributed as an .rpm file. Youcreate a profile in a profile manager and under Properties select SourceHost and names of the files you want to distribute. See Figure 31.


Figure 31. File Package Properties

For installation, you can set different scenarios, for our requirements. With theLinux client, you want to distribute files to the target and execute aninstallation script. After the Backup/ Archive Client files are on the targetmachine, you execute the installation script. For the Linux platform, you selectUnix Options. In Run a Program section you select After Distribution andin After Distribution Program Options type the name of the script andselect where to get this program from. Because the .rpm format alreadyincludes the installation script, our script only needs to execute the .rpm. SeeFigure 32.

#!/bin/sh/bin/rpm -i --force /tmp/TIVsm-BA-3.7.2.0-1.i386.rpm


Figure 32. Unix After Distribution Options

In the commit stage of the software distribution is the task to create thedsm.opt and dsm.sys files for our requirements. You enter the commit scriptin the Commit Distribution Program Options section. During the upgrade ofthe clients, you can skip the commit stage, because those files already exist.

4.3.3 Distributing packagesAfter you create a file package, and set all options for all platforms, you candistribute the package. The package can be distributed directly to targets or


profile managers. Using drag and drop is the same, as is distribution of allfiles with Distribute Only options on all selected targets.

With File Package and Distribute, you open the distribution options window.Our first choice is Distribution Type, where you can choose betweenDistribution Only, Distribution & Commit, and Commit Only. The first twooptions are running together with pre-installation and post-installation scripts,while Commit Only runs only commit programs.

In the Available Subscribers section, you select the subscribers.

Under File Package Distribution Preview, you can observe the list of filesand directories that you selected to distribute. In case the source files arecorrupt or missing, they are not shown on the preview list.

For distributing files later, you can use the Tivoli Framework scheduler. SeeFigure 33.


Figure 33. Distribute File Package


4.4 Hints and tips

• If you want to browse files on Endpoint, you must first enter the Endpointname manually.

• If the Endpoint platform is Windows, then you must change the defaultbrowse path from root (/) to the drive letter you want to browse (c:/).


Chapter 5. Tivoli Inventory

In this chapter, we explain the Tivoli Inventory product in more detail. Again,we provide samples to show what can be done to help the Tivoli StorageManager administrator to get more work done in less time.

5.1 Tivoli Inventory concepts

Figure 34 shows the Tivoli Inventory as part of the Framework, interactingwith the RIM, the RDBMS, and the target machines. Inventory collectsinformation about hardware and software that can be reviewed by inventoryqueries.

Figure 34. Tivoli Inventory

In order to better understand the examples, we first cover the components ofTivoli Inventory and how they interact with each other.

End-point

End-point

End-point

End-point

End-point

ManagedNode

ManagedNode

gateway

TivoliInventory

distributeinventoryprofiles

collectinventory

data


RDBMS

Framework

distribute inventory profilescollect inventory data


5.1.1 Tivoli Inventory componentsThe Tivoli Inventory application can be viewed as having two maincomponents:

• The collection engine

• The database interface and query facility

Tivoli Inventory consists of the collection engine and some Tivoli Inventoryspecific views for the query facility. The Relational Database Interface Module(RIM) and the query facility are part of the Tivoli Framework. What we havecalled the collection engine is divided into two install images:

1. Tivoli Inventory Server Package — This package is installed on the TMRserver, where profiles are defined. These profiles contain instructions forscanning target machines. The machine where this package is installed iscalled the Tivoli Inventory Server.

2. Tivoli Inventory Gateway Package — A machine running a TivoliManagement Agent needs to communicate to its assigned Gateway inorder to download any methods necessary to execute managementoperations. The Tivoli Inventory Gateway Package contains theseinventory methods and needs to be installed on all Managed Nodes thatyou will configure as Endpoint Gateways. A scanning agent is part of thispackage and is downloaded to the TMA Endpoint when needed.

5.1.2 Tivoli Inventory installationDuring the installation of Tivoli Inventory, the following happens:

• An instance of the RIM object is created and is called inventory. Thisinstance of the RIM object defines the connection between the TivoliInventory application and the RDBMS server via an RIM host. The RIMhost is a machine where an RDBMS client is installed and which isenabled to communicate with an RDBMS server, or is the RDBMS serveritself. The RIM host must be a Managed Node in the TMR.

• The configuration repository defines all of the tables and fields wherethe inventory information is stored. The relational database containingthese tables can reside either on the same machine as the Tivoli InventoryServer or even on a machine outside the TMR, whereas the RIM hostwhere the RDBMS client is installed must be a Managed Node in the TMR.The data can be queried using the Tivoli desktop menus or the queryfacility.


Some scripts and files are also installed with Tivoli Inventory:

• Database vendor-dependent scripts to create the schema of theinventory database. The schema determines the structure of the tables ofthe inventory database.

• Inventory query scripts create queries that return general informationabout the machines in your TMR.

• Subscription query scripts to create queries that return lists of possiblesubscribers for profiles based on various scan results.

• A software signature file: A software signature is a set of informationthat defines a software package. This information is used to determinewhich software packages are installed on the machines you scan.Inventory 3.6.2 has over 10,000 software signatures available in a file.Additionally, tools are provided that allow a customer to add their ownsoftware signatures to the database.

5.1.3 Tivoli Inventory scanThe following describes a typical order of events involved in an inventoryscan. By initiating a scan, the administrator activates a scanning softwareresiding on every system from which information is to be collected. This canbe anything from a single system to every system in the enterprise.

On each scanned system, the hardware and software scanners create aDMTF-compliant, industry-standard, Management Information Format (MIF)formatted flat file containing the results of the scan. Depending on theresources which you have selected to scan, the following will happen:

Scanning TMA Endpoints ()Figure 35 illustrates the Tivoli Inventory architecture when scanningEndpoints. The scanners running on the TMA Endpoints produce MIF files.On the TMA Endpoint, the MIF files are parsed, archived, and differentiated ifthis option is selected in the scan profile. Then, the files resulting fromparsing MIF files are converted to a format that can be saved in an RDBMSdatabase and sent to the Endpoint Gateway.

The Endpoint Gateway sends these files in RDBMS format to the TMR server.These data are used to populate the configuration repository via theRelational Database Interface Module (RIM). The RIM object on the TMRserver calls the RIM host where the RDBMS client resides and the RIM hostcontacts the RDBMS server.

Chapter 5. Tivoli Inventory 71

During a scan, you can specify if you want to save configuration files such asthe autoexec.bat or /etc/hosts, or the Tivoli Storage Manager relateddsm.opt or dsm.sys. If you have chosen this option and are scanning TMAEndpoints, the configuration files copied during the scan are sent to theEndpoint Gateway, which sends them back to the TMR server. Theseconfiguration files are stored in the TMR server’s database.

Figure 35. Tivoli Inventory architecture when scanning Endpoints

Scanning the machines in your environment for the first time can betime-consuming, because data has yet to be collected. After you have done afull scan on the machines once, you can use the inventory profile that is set tocompare the results of the current scan with the results of the previous scan;so, it will occur faster.


5.2 Examples

These examples are designed to stimulate your imagination — they aren’tintended to be taken as-is. If you go through them and find yourself thinking:“I would do this in another way”, then the lesson is already learned.

5.2.1 Inventory profilesIn this section we show three examples of inventory profiles:

1. Hardware scan

2. Software scan

3. Saving of configuration files

In Figure 36 you can see a screen showing this three inventory profiles andtheir subscribers. As with other modules, you have to set subscribers to theprofiles in order to distribute them to the target machines.

There is only one default Inventory scan profile, so upon creation, a defaultone will appear. You then have to customize it to the designated function.

Inventory scans target machines in parallel, but writes the collectedinformation to the configuration repository serially; so, it is important thatthe network connectivity between the TMR, Inventory server, RIM host, andthe RDBMS is sufficient and configured for optimum operation. Also,inventory does not save the information to the configuration repository untilall targets of the distribution are scanned.

Note


Figure 36. Profile manager with inventory profiles and subscribers

5.2.1.1 Hardware scanTo create an inventory profile which scans the hardware of your machines,open the profile manager which is supposed to house your inventory profiles.If you are using Endpoints as subscribers, make sure that this profilemanager is in dataless mode, and that Inventory Profile is a managedresource of your current policy region. See Figure 37.


Figure 37. Inventory profile manager and query libraries

Create an inventory profile and open it for customizing. You will get thefollowing screen (Figure 38).


Figure 38. Inventory scan for hardware


When you are scanning only for hardware, then only the upper part of thescreen is important. Be sure that only hardware scan is selected, and thatthe appropriate MIF files are created. For more about MIF files, see the TivoliInventory Users Guide, GI10-8048.

Then save and close, and you can now distribute this inventory profile to thetarget machines. It will scan for all hardware which is known to inventory. Thisincludes processors, memory, file systems, hard disks, BIOS information, andso on. To keep up-to-date with changes made to the machines, you shouldschedule these scans with the Tivoli Framework scheduler.

5.2.1.2 Software scanIn order to create an inventory profile for scanning software, create anotherprofile called sw_scan and open it for customizing (Figure 39).

The execute on target should be software scan and read results toSoftware MIF file. The save results in database section is for incremental(update with differences) or replace all collected information. End useraccess relates to Tivoli Userlink which we don’t cover in this book. See theTivoli Inventory Users Guide, GI10-8048.

When you are not having separate inventory profiles for each platform, it isrecommended that you scan all files with all extensions. That’s becauseexecutables in UNIX platforms don’t need extensions, but on Windowsplatforms, extensions are required.

After changing the values, you can save and exit. To run the software scan,distribute the profile to the subscribers. This scan normally takes a while foreach machine to perform, and your database will be quite busy. Although thescans run parallel on all targets, the results are being written to the databaseserially after all scans have finished. So no updates are visible as long as thescan is running.


Figure 39. Inventory scan for software

5.2.1.3 Saving config files (dsm.opt/sys, recovery plan)In addition to hardware and software scans, you can save information aboutconfiguration files with Tivoli Inventory. In normal environments, this will be/etc/hosts or autoexec.bat, and so on.


However, you can also save the contents of the dsm.opt/sys file and yourTivoli Storage Manager’s recovery plan file. This is especially useful whenthese files have been altered or deleted, since you can’t access the TivoliStorage Manager server to restore them, if they don’t exist. If you choose“Store as ASCII” they will be copied to the database directory of your TMRserver ($BINDIR/inventory/objectid/...). See Figure 40.

Figure 40. Storing configuration files as ASCII through inventory profile

In order to keep track of changes to these files, you can schedule thedistribution of the scanning profiles.


5.2.2 QueriesThe previous section showed how to retrieve information into the repositorydatabase. Now, we will consider how to make use of this collected data.

Tivoli Inventory provides a wealth of predefined inventory queries to retrieveinformation from the repository. This can be machine specific or informationspecific. To issue machine specific queries, you can right-click on the targetspecifying hardware, software or generic query.

5.2.2.1 Hardware queriesSee Figure 41 for a hardware inventory of a four-way RS/6000 on AIX(partially displayed).

Figure 41. Sample hardware query

The following list provides some examples of queries that might provideuseful information regarding a Tivoli Storage Manager administrator’s clients:

• Harddisks

Size (for capacity planning).

• Logical Volumes

Size of file systems (for bare metal restore, capacity planning).

• Network cards

Full or incremental backups, additional bandwidth needed.


• Processor, memory, paging space

Determine if compression should be on or not.

5.2.2.2 Software queriesFor Tivoli Inventory to recognize which software products are installed on atarget (rather than just knowing which files are on), you have to provideSoftware Signatures. They consist of stanzas for each Software productwhich include a filename, its size, the name of the product and its version.With this unique combination, Tivoli Inventory recognizes a software productwhich then can be queried. For standard products, these signature files areprovided by Tivoli and are updated regularly. They can be downloaded fromthe Tivoli support Web site http://www.tivoli.com/support.

Note that special products (including Tivoli products), are not provided.However, if you add them manually, they are especially useful for TivoliStorage Manager administrators.

The command wfilesig is used to import software signatures into TivoliInventory. The syntax is:

wfilesig [-a|-r] [-n name -s size -d description -v version]

The parameters are -a for adding and -r for removing certain products.

Here is a sample of creating a custom signature:

wfilesig -a -n dsmc.exe -s 1036288 \-d “Tivoli Storage Manager Backup/Archive-Client Win32” -v “3.7.2”

An explanation of how to use the wfilesig command can be found by typingman wfilesig or in the Tivoli Inventory Users Guide, GI10-8048.

This will make Tivoli Inventory recognize the Tivoli Storage ManagerBackup/Archive client version 3.7.2 on the Windows platforms. With thisinformation stored in the repository database, you can create a custom queryto list all the Tivoli Storage manager clients and versions on all clientmachines. To create such a custom query, open a query library (for example,INVENTORY_QUERIES). Create a query and change it, using the values inFigure 42.


Figure 42. Custom query TSM clients

The where clause, which is hard to see in the figure, should be:SW_COMP_NAME like ‘Tivoli Storage Manager Backup/Archive-Client %’The % is the wildcard character of SQL. This will select from the tableSW_COMP_NAME all the entries that begins with the above pattern.


This will give you the client names which have the Tivoli Storage Managerbackup-archive client installed in any version on any platform.

If you run this query, you should get output similar to that shown in Figure 43.

Figure 43. Query results of custom TSM client

Then you can conveniently view the software levels of your Tivoli StorageManager Clients and decide which eventually have to be upgraded and so on.

Additionally, using the predefined software queries, you can identify the clientmachines which have special applications installed, like MS SQL orExchange, and which need special treatment to backup their data (Tivoli DataProtection).

Again, use your imagination to extend these examples to your needs in yourenvironment. Since the possibilities are so widespread, we can only makesuggestions. Tivoli Enterprise and its modules are so universal, almostanything can be realized — customizing is the key.


5.3 Hints and tips

• If you are running multiple scans on multiple machines, make sure yourdatabase log is big enough.

• Queries over multiple views or tables can take a significant amount of timeand CPU to proceed.

• If you have large fileservers, don’t scan all files. Search only specificdirectories.

• If your company is developing software, create software signatures forthese products as well.

• There are queries and signatures for fix-levels and PTFs.


Chapter 6. Tivoli Enterprise Console

This chapter explains basic Tivoli Enterprise Console components and how toset them for the Tivoli Storage Manager Enterprise environment.

6.1 Introduction

Tivoli Enterprise Console (TEC) is a management product that allows you toapply customized actions on different events from different sources, such asoperating systems, network management data, databases, or applicationsevents. In TEC, all these events from the IT environment are brought togetherin one place, which offers the administrators a centralized and filtered view ofthe enterprise-wide events. See Figure 44.

Figure 44. Tivoli Enterprise Console

End-point

End-point

End-point

End-point

End-point



ManagedNode

gateway

send events


RDBMS

TaskLibraries

actions

Framework


6.2 Overview of the Tivoli Enterprise Console

The Tivoli Enterprise Console collects, processes, and sets actions based onpredefined rules. It allows you to effectively process events in a distributedenvironment with setting the level of importance of events, filtering out lessimportant, correlations on events from other sources, setting the limits onview and action possibilities for specific administrators, and reactingautomatically, when this is needed.

The main components of Tivoli Enterprise Console are:

• Event Adapters• Event Server• Event Consoles

See Figure 45. To facilitate implementation of the Tivoli Enterprise Console,the following tools are provided:

• Tivoli Event Integration Facility (EIF) for customizing and creating newevent adapters

• Tivoli Adapter Configuration Facility (ACF) for graphical configuration anddistribution method of event adapters

Figure 45. Tivoli Enterprise Console event flow

Every system has integrated mechanisms for monitoring the state of thecomponents. Those informations are usually collected in log files, where theyare filtered by the system itself. In our schematic overview, we will call this anevent source. The filtered event source is monitored by the event adapter. In alog file scenario, the event adapter is a small portion of code running on thesystem and parsing informations out of the system or application log file.Devices incapable to host programs, like routers, have their adapters onnearby systems. Raw events collected by the event adapter are then filteredagain. With this filter you can limit the data flow through the network. Those

EventSource Filter

FormattedEvents

RawEvents Filter

Ru

les

EventConsole

ClientAdapter Formatted

Events

Event Server

ProcessedEvents

RDBMS


filtered events are formatted by the event adapter into a form, the eventserver can understand.

Filtered and formatted events are sent to the event server. When the eventserver receives events which does not fit in the correct format, they arediscarded. See Figure 45. The server reception engine is responsible forreception of events. When an event arrives, the reception engine validatesand gives a unique identifier, which is the composite of time stamp and serialnumber. If the reception engine is busy, it stores events in a reception buffer.All events are recorded in a reception log, so you can check for discardedevents. The next stop for events is the rules engine. It applies rules on events.A part of the rules engine is the rules cache. Events are temporarily stored inthe rules cache in case of correlation with other events, for updating eventvalues (called slots) or to reapply and process the rules on events again. Therules are made of a unique name, description, conditions and actions. Thereare three types of rules. Plain rules are evaluated against all incoming events,change rules for changing specific slot values and timer rules for redoanalysis. From the rules engine events are passed to the dispatch engine,which updates the event consoles. The dispatch engine also communicateswith the task engine and the event repository. The task engine executes tasksand scripts, and returns the status of actions back to the dispatcher engine.The event repository stores all processed events in its RDBMS.Synchronization of all processes is done by the master process. Events arethen displayed on the event console. See Figure 46.

Chapter 6. Tivoli Enterprise Console 87

Figure 46. Components of the TEC Event Server

Event console is the administrators interface for communication with TEC.Each of administrators have their own console. When the console is started, itdisplays two windows. The first is a collection of source groups. In the secondevent groups are displayed. For each administrator we have assigned eventgroups and upon those, event sources are displayed. With assigning of eventgroups you can set access and view priority. The event console allowsadministrators to select the events by severity and status, to sort events byparameters like date, host name severity and so on and setting the fieldswhich are displayed for each event. The administrators can use manual tasksor create automatic responses on specific events.

6.2.1 Event adaptersThe event adapter is the portion of code which runs on the client system andcaptures formats and sends the event to TEC. Already provided eventadapters are:

• AS/400 Alert adapter


• AS/400 Message adapter

• Logfile Event adapter

• Netview for OS/390 adapter

• NetView/6000 adapter

• OpenView adapter

• SNMP adapter

• Spectrum Enterprise Manager adapter

• Sun Solstice/SunNet Manager adapter

• Tandem NonStop Kernel adapter

• Windows NT Event Log adapter

The adapters can be different, but they have some common files.Communication between the adapter and TEC server is configured via theadapter configuration file (.conf). Error logging and tracing is configured withthe error file (.err). Logfile adapters are using format files (.fmt) for parsinginformations from the log files. Format files must be consistent with the eventdefinition file (.baroc). This files are provided and can be distributed as aprofile. In graphical environment you can set parameters like filters,environment or location of files. See Figure 47.


Figure 47. TEC Adapter profile

6.2.2 Event classesFormatted events are received by the event server and are checked againstthe event definition file. The type of events is defined with the event class.Events which do not match any of the event classes, are discarded by theevent server. The event class definition file contains, beside class definitionsand hierarchical structure, also slot definitions. Slots are names for possiblevalues, the adapter can receive. In the class definition, you can set defaultvalues for the slots.

6.2.3 RulesReceived events are now ready to be processed by the rules engine. Therules are grouped together in rule sets. On the server each rule set is one file(.rls). A rule base is made of multiple rule sets and class definition files.Rules, described in the rule set files, must match class definitions. The orderof loading rules is described in a file called rule_sets, and the class order inload_classes. See Figure 48.


Figure 48. Rule Bases

Rules are written in the TEC rule language and then compiled together withthe class definitions. With TEC, you can also use the graphical rule builder.After installation of the TEC server you have a Default rule base and you cancopy it into a new one, together with rule sets and class definitions. You canhave multiple rule bases, but only one can be active.

6.2.4 Handling of the messagesIn the Tivoli Storage Manager server messages are in form of three letterscalled prefix which explains source of the message followed by four numberswhich is actual message number and one letter for message type. See Figure49.


Figure 49. Tivoli Storage Manager message

With Tivoli Storage Manager server is provided class definition file with nameibmtsm.baroc. In this file type and default severity of events are defined. Forgetting the correct level of severity you must translate Tivoli Storage Managerseverity to TEC severity (Figure 50). Forwarding those messages to TEC iscontrolled by putting the information about TEC event server in opt file andenabling or disabling specific messages. For easier setting of messages youhave script called ibmtsm.mac. In this script first all messages are disabled,than enabled severity types error and severe, followed by enabling messagesfrom other severity types, which could be important for Tivoli Storagemanager administrator. In next section a series of different syntax errors aredisabled. In the end of this script is the client section. For clients info andwarning severity messages are disabled and enabled with severity error andsevere for all nodes. This is first filtering level of events. All enabledmessages are forwarded to TEC, where they are mapped into events.


Figure 50. Translating Tivoli Storage Manager messages into TEC Events

Default severity of all events which do not have value for severity inIBMBACKUP class is set by ibmtsm.baroc file on CRITICAL. For changingthat setting, you must change this file, replace existing event class definitionfile with new one, compile the rule base, import rule base and restart theevent server.

6.3 How to prepare TEC for Tivoli Storage Manager

To integrate Tivoli Storage Manager into the Tivoli Enterprise, you have toexecute a few tasks and prepare TEC for Tivoli Storage Manager.

6.3.1 Importing files for Tivoli Storage ManagerThe latest maintenance level of Tivoli Storage Manager server ships with aclass definition file and a rule set file, which need to be imported into theactive rule base. Since you can not modify the Default rule base, you create anew rule base and copy the class definition files and rule sets you need. Inthe Tivoli Desktop main window, you select event server and with a right clickselect Rule Bases. In the Event Server Rule Bases window, you then selectCreate Rule Base and type in the name and the directory of the new rulebase. See Figure 51.

ppp nnnn I

ppp nnnn E

ppp nnnn S

ppp nnnn W

INFO

WARNING

ERROR

SEVERE

UNKNOWN

HARMLESS

WARNING

MINOR

CRITICAL

FATAL

Messages Tivoli StorageManager server

Tivoli EnterpriseConsoleMessage mapping


Figure 51. Rule Base Properties

To make a copy of the Default rule base you right click on Default rule baseand select Copy, select new rule base as destination and check boxes forclass definitions and rule sets. See Figure 52.

Figure 52. Copy Rule Base

We created a new rule base with a copy of the default class definitions andrule sets. In case that you don’t want to have some of those files, you mustdelete unwanted entries from rule_sets and load_classes files, exceptroot.baroc and tec.baroc in that order, because there are slot definitions forinheriting classes. Now you can import the Tivoli Storage Manager files. Youselect Import with right click on our rule base. See Figure 53.


Figure 53. Import Into Rule Base

Into this dialog window you type the name of the file, you want to import. Inour case under rule set is ibmtsm.rls and select position of this rule set withselecting the existing rule set and Insert Before and Insert After radiobuttons. You repeat this with class definition file, which is calledibmtsm.baroc. You have to position at least after root.baroc and tec.baroc andfinish the procedure with Import & Close click. After importing of files, youhave to compile our modified rule base. With right click you select Compilefrom the menu. In dialog window you select Compile. See Figure 54.


Figure 54. Compile Rule Base

In case that event definitions and rules are inconsistent or their are syntaxerrors in files, compile will fail. The last step of import is loading the rule base.You again right click on rule base and select Load. See Figure 55.

Figure 55. Load Rule Base

In this window you have two choices. First one is Load and activate the rulebase. You must choose Load, but activate only when server restarts,because event definition files are loaded only with server restart and if youmake any change in class definitions, then you have to restart the eventserver.

6.3.2 Creating event group for Tivoli Storage ManagerFor filtering out Tivoli Storage Manager events you need to create separateevent group and assign this group to the appropriate administrators. With


right click on the event server icon you select Event Groups. In Event GroupManagement window you have list of existing event groups. See Figure 56.

Figure 56. Event Group Management

In this window you open new event group creation dialog with Event Group,New. In next dialog window you type in the name of the new event group andselect an icon. You can import new icons with Import Bitmap option. SeeFigure 57.


Figure 57. New Event Group

After you created new event group, it does not contain any filters. Filters areset for selecting type of events, you want to see in the specific event group. Toset the filters you have to select Edit and Edit Filters. In this dialog windowyou select appropriate filters. For all events which are generated by TivoliStorage Manager you click Event Class button in Filter Values section andfrom list of available event classes select IBMBACKUP. With Set Class Valueand Add Filter buttons you add this filter to event group. In case that youwant to add additional information to this event group, you can set additionalfilters or if you want to distribute information on several event groups, thenyou must replace this filter with subsided. For getting the events from onlyselected nodes you type in or select appropriate node in origin section. SeeFigure 58.


Figure 58. Edit Event Group Filters

After creating of an event group or more of them, you have to assign thisevent groups to administrator. You can assign one event group to multipleadministrators, but you must ensure that administrative rights are logicallyset. Assign is done by selecting with the right mouse button administrator’sevent console option Assign Event Groups. In this dialog window you selectevent groups for each administrator and security privileges on these groups.Event sources are selected automatically based on event groups eventclasses selection. See Figure 59.


Figure 59. Assign Event Groups

In case that you need to change event group name or to delete it, werecommend that you first unassign event group from all administrators.

6.3.3 Display setting of the event consoleAdministrator’s event console is used for displaying event to administrator andas tool for responding manually or automatically to the events. When youopen event console two windows with title TME 10 Enterprise Console areautomatically opened. One is for displaying the source groups. There areoptions to display source groups in text mode and to sort source groupsvertically. Second one displays event groups. See Figure 60. In this windowyou can choose:

• Severity Display for setting text colors, background colors and icons ordifferent severities

• Event Group Display for setting the event group icons and enable ordisable display of event group title, severity text, date and time

• Rearrange Groups for setting the order of the event and source groups

• Message Time Limits for setting time limits for displaying and keepingopen or closed messages. This dialog box enables option to view someold events

• Netview Connections to establish connection between TEC and Netviewserver and Netview maps


Figure 60. Event Groups display

When you open event group, the list of events is displayed. In View menu youhave first Sort Messages. In this dialog box you set the sort keys and order.By default the events are sorted first by status and than by severity. In the lastcolumn you select row header. You can choose any of available slots. To sortevents first by the date you must move the date in the Sort By window andshift it to the top. See Figure 61.

Figure 61. Sort Event Group Messages


With selecting Display Message Field you set the fields of events which aredisplayed out of the event slots. In the event window of the event group youhave list of events, sorted by our criteria. On the top is Update ON buttonwhich enable or disable live updating of events in that event group. Below youhave check marks for including types of events by severity and status. Statusis when event arrives open. Administrator can either acknowledge or closeevent. To acknowledge the event user privileges in that event group arerequired and for closing admin rights. When administrator acknowledge orclose the event, the administrator slot gets value of the administratorsdesktop login.

6.3.4 Creating an automated taskWith Tivoli Enterprise Console you can set task which run automatically,when the selected event is received. To create automated task, you have togo to the enterprise console events window and select Automated Task frommenu. You can select the event first and than in menu New with SelectedEvent if you already received event on which you want to react. See Figure62.


Figure 62. Tivoli Enterprise Console Events

Option without selecting the event class, prompt you for this with pop upwindow. You select event class, upon which you want to have automated task.See Figure 63.


Figure 63. Select Event Class

With Select & Close button or with New with Selected Event from mainmenu, you open Summary of the Automated Task window. Here there aretwo main windows. In the left are filters for this event and in the right windowthere is a list of the actions you have set. You can set the order of executionfor actions with buttons on the right side of the window. See Figure 64.

Figure 64. Summary of the Automated Task


With Edit Criteria button, you invoke window in which you set the filters forthis event. Filters are set on the event slot values. You select slot from theAvailable Slots and with double click or with right arrow on the top add filter.Then you select operator with pull down menu. Available options are:

• Equals

• Less than

• Less then or equal

• Greater then

• Greater then or equal

• Contain

• Does not contain

In the value field you type in the criteria value. Values from the last selectedevent are automatically fill in. With Enter or click on check mark sign you addfilter to the events automated task. After you are finished with adding thefilters, you add those filters with Set & Close button. See Figure 65.

Figure 65. Setup Automatic Task Execution


With Add Task button in Summary of the Automated Task window you openthe dialog for adding and configuring task. You must select the task first.Selection list is made of all existing task in our framework. In the left list youhave list of task libraries and with double click you fill the right window withtasks available within this task library. With selecting the task the area bellowis filled with tasks configuration parameters you have to fill in. See Figure 66.

Figure 66. Automated Task Execution Setup

With selecting where to execute the task between Execute on Event orExecute on select Managed Nodes from the pull down menu and buttonAdd or Add & Close you add task to the Summary of the Automated Taskwindow. With saving of the automated task you finish the configuring.

6.3.5 Setting the severity of TEC eventsSetting of the default severity for the event class sets severity for all events inthat event class without severity slot value. In example you will set defaultseverity of class IBMTSM_BASE_SERVER to warning andIBMTSM_BASE_CLIENT default severity which maps all client messages toharmless. You already created rule base named itso with default directory in:/usr/local/Tivoli/bin/aix4-r1/custom/TEC_CLASSES. First step is to edit the


necessary sections in ibmtsm.baroc. The sections of this file after editing willlook similar to this:

TEC_CLASS :IBMTSM_BASE_SERVER ISA IBMBACKUPDEFINES {

severity: SEVERITY, default= "WARNING";source: default = "TSM";tsm_message_severity: INTEGER;tsm_message_number: INTEGER;

sub_source: default = "TSM_SERVER";tsm_server_platform: STRING;

};ENDTEC_CLASS :

IBMTSM_BASE_CLIENT ISA IBMBACKUPDEFINES {

severity: SEVERITY, default= "HARMLESS";source: default = "TSM";tsm_message_severity: INTEGER;tsm_message_number: INTEGER;

sub_source: default = "TSM_BACKUP_ARCHIVE_CLIENT";policy_domain: STRING, default = "STANDARD";schedule_name: STRING, default = "none";session_id: INTEGER, default=0;comm_method: STRING, default = "TCP/IP";owner_name: STRING, default = "none";};

END

We changed ‘default =’ values of these sections. In our example you alreadyhave working environment with imported ibmtsm.baroc class definition file, soyou must delete existing on from the rule base:

wdelrbclass ibmtsm.baroc itso

Than you have to import new file into the rule base:

wimprbclass /usr/tivoli/tsm/server/bin/ibmtsm.baroc itso

In the next step you compile edited rule base:

wcomprules itso

Compilation of the rule base will fail with the message Compilation Failed, ifyou make any errors in syntax or in order of loaded classes. Screen outputallows you to pinpoint the error. Then load the compiled rule base:

wloadrb itso


Stop and start the event server:

wstopesvrwstartesvr

The last step is necessary, because TEC loads event classes only at serverstart. For testing purposes you can generate events on TEC to test severity ofthese events:

wpostemsg -m 'Test of severity settings' IBMTSM_BASE_SERVER TSMwpostemsg -m 'Test of severity settings' IBMTSM_BASE_CLIENT TSM

6.3.6 Deleting rule setsFor better performance during the processing of the rules and compilations ofthe rule set it is recommended that you remove all unnecessary rule set andclass definition files. First you list rule sets and class definition files in the rulebase:

wlsrbrules itsoRule Set files--------------log_default.rlssentry.rlsibmtsm.rlsdo_something.rls

This command list the rule set files in rule base. For class definition files youmust use Tivoli Desktop or list the content of the configuration file for classes.You must find out, where the configuration file of our rule base are. Commandwhich list directories of rule bases is:

wlsrb -dRule Base Name Directory-------------- -------------------------------------Default brazil:/usr/local/Tivoli/bin/aix4-r1/TME/TEC/default_rbitso brazil:/usr/local/Tivoli/bin/aix4-r1/custom

In home directory of the rule base there are three more subdirectories:

• TEC_CLASSES

• TEC_RULES

• TEC_TEMPLATES.

This directories includes classes, rules and templates for the rule base. In theTEC_CLASSES subdirectory, you can find file .load_classes. This file has the


list of the class definition files for our rule base. The list of the contents of thisfile should look like this:

brazil:/ > cat .load_classesroot.baroctec.baroctecad_logfile.baroctecad_nt.barocSentry.barocuniversal.baroctivoli.baroctecad_sd.barocibmtsm.baroc

We edited the file and removed the entries which were not needed. When youare changing the rule base, you have to take care, that class definition filesare defining all event classes which are used in rules. Also, the order of theclass definition files must be in the order which classes are built. Afterchanging the event classes or rules, you have to compile and load the rulebase. For changing the classes, starting and stoping the TEC event server isrequired.


Chapter 7. Tivoli Plus Module for ADSM

The Tivoli Plus module for ADSM is a collection of predefined tasks and jobsfor additionally managing the ADSM and Tivoli Storage Manager servers inTivoli Enterprise. See Figure 67.

7.1 Components of Tivoli Plus Module

Figure 67 shows the components of the Tivoli Plus module for ADSM.

Figure 67. Tivoli Plus Module for Tivoli Storage Manager

Tivoli Plus for ADSM creates a generic collection for managing TivoliStorage Manager servers and clients. In this collection you can find icons forlaunching servers, clients, and administrative clients. Subscription lists arepredefined for ADSM Servers, ADSM Clients, HSM Recall Servers, andHSM Space Monitor Servers. Distributed Monitoring profiles are added withmonitors for host availability, network collisions per packet, database, and logutilization percentage.

End-point

End-point

End-point

End-point

End-point


ManagedNode

gateway

Plus Module for TSM- Tasks- Jobs- Profile Managers- Indicator Collections- Monitors

Framework


The Tivoli Plus module provides tasks and jobs for backup and archiveoperations on Tivoli Storage Manager clients and for administrative clients.See Figure 68.

Figure 68. ADSMPlus for Tivoli menu

7.2 How it works

The Tivoli Plus module for ADSM extends integration between TivoliEnterprise and Tivoli Storage Manager servers and clients by adding alreadydefined organizational structure of monitors, indicator collections, tasks, andjobs. You must install this module on every node from which you want toperform TSM tasks, and on the TEC server. Nodes can be Managed Nodes orEndpoints, including TMR and TEC servers.

7.3 Setting up the Tivoli Plus Module

After installation of the Tivoli Plus Module for ADSM on all nodes, you mustfirst check and modify subscription lists in the provided profile managers.These lists must be synchronized with the Tivoli Storage Managerenvironment. These profile managers are not in dataless Endpoint mode.


The graphical environment does not allow changing of the profile managersetting, and you must use the command: wsetpm [-d | -D]. For example:

wsetpm -d @ProfileManager:”ADSM Clients”

This example sets the provided profile manager ADSM Clients in datalessmode, so you can set Endpoints as subscribers. Another option is to set othercustom-created profile managers as subscribers. The next step is setting thecorrect home setting for the server, client, and administrative client files. Thehome directory should point to the directory where binaries for specific clientsare located. See Figure 69.

Figure 69. Set ADSM Home menu

To monitor the state of the servers, you must customize distributed monitors.You check each profile manager and populate them with the monitors that youconsider useful. The Tivoli Plus module provides an additional monitor innumeric script format for database and log size. Then you set limits, severity,and response values for each of those monitors. Parameters vary, anddepend heavily on the production environment.

After setting the monitors, you need to set their schedules. Again, you mustconsider the environment, setting timers that will get meaningful results andthat will not overload systems and network connections.

The next step is distribution of the prepared monitors. For this, you can usean already-prepared profile manager called ADSM Servers. Distribution canbe scheduled or executed immediately.

The final task is to check subscribers for the jobs, especially in multiple TivoliStorage Manager server environments. There are some limitations using thePlus Module with Endpoints, especially during the installation.

Chapter 7. Tivoli Plus Module for ADSM 113

Note: The majority of the tasks in the ADSM Plus Module will be integratedinto the next server release, and the product will be discontinued.

7.4 Hints and tips

• The default path for the Tivoli Storage Manager client in Windows NT isC:\Program Files\Tivoli\TSM\baclient. Because of the fields in this path,you must use directory names without extended attributes. In this caseyou must set the path C:\Progra~1\Tivoli\TSM\baclient.

• In Set ADSM Home task for Admin Client parameter on Windows NT, thetask fails because the script expects the dsmadm.exe file, which no longerexists in the TSM administrative clients. The workaround is to create a filewith that name in the same directory as dsmadmc.exe, and set the homeparameter again. Another possibility is to modify the script(setadsmhome.sh) for setting parameters.

• You must set all parameters of Set ADSM Home task, otherwise thescripts are not executed.


Chapter 8. Tivoli Data Protection for Applications

This chapter briefly covers some possible integration scenarios with TivoliEnterprise. Although the Tivoli Data Protection for Applications modules arenot directly connected to the Framework, they are a substantial part of TivoliStorage Manager, thus necessitating their integration in system managementapplications.

Application servers are usually widespread in various departments; however,they need to be monitored and managed centrally.

8.1 Overview

Figure 70 shows the interaction of the Tivoli Data Protection for Applicationsmodules with the rest of the modules.

Figure 70. Tivoli Data Protection for Applications

ManagedNode

gateway


ManagedNode

Tivoli StorageManager

Endpoint

Application

TDP

RDBMS

events

data

tasks

events

TaskLibraries RDBMS

interfacemodule

RDBMS

Framework


8.2 Event forwarding to Tivoli Storage Manager

By doing backups and restores of your data from the applications, events arelogged against the Tivoli Storage Manager event receivers. By default, theseevents are activity log and server console. For example, by setting up theTivoli event receiver, events are forwarded to the Tivoli Enterprise Console.This includes messages from the server itself and client messages from theTivoli Data Protection modules.

The latest versions of Tivoli Storage Manager and the Tivoli Data Protectionmodules are enabled for enhanced TEC event forwarding. This means thatthere are special TEC classes for messages originating from the Tivoli DataProtection modules. When these messages arrive at the Tivoli Storagemanager, they are translated into unique TEC messages, such asTSM_TDP_EXCHANGE_ACN####.

This feature allows for faster filtering and more efficient rule generation withinthe TEC server. Additionally, individual TDP messages can be enabled ordisabled for the TEC event receiver on an individual node basis.

8.3 Using tasks

Since all the Tivoli Data Protection modules are able to use scripts forautomating backup/restore actions, they are ideal for using Tivoli tasks. If themachine where the application and its TDP module resides is a TivoliEndpoint or Managed Node, you are able to run tasks against it.

Some Tivoli managers for applications, for example, Tivoli Manager forMicrosoft SQL server, are shipping with predefined tasks to execute full orincremental backups of the application.

This enables you to respond to certain events with backup action (eventtriggered backup). For example, when you get the event indicating that themirror or the RAID array where your application data resides is degraded, youcan make a full backup of your application.

Another situation that concerns most administrators is offline backup of anapplication. You can determine if your application is down, by using TECevents, and then make your backup. After the backup is completed, which isagain determined by TEC events, you can start the application again. Anexample of this situation is provided in Part 3 of this redbook.

Tivoli Storage Manager and Tivoli Enterprise, together with Tivoli DataProtection and Tivoli Managers, enable you to automate whatever you want.


8.4 Using Tivoli Software Distribution

In order to deploy the Tivoli Data Protection for Application modules to yourclients, you can use Tivoli Software Distribution. Figure 71 shows the mainscreen of Tivoli Data Protection for MS Exchange.

Figure 71. Tivoli Data Protection for MS Exchange

As an example, we show you how to create a file package for the MSExchange TDP client.

1. Copy the files from your TDP CD onto your hard disk, for example, to adirectory like this: c:\temp\tdp_exch.

Chapter 8. Tivoli Data Protection for Applications 117

2. Create an unattended installation file. This is done by running thesetup.exe from the TDP installation path with parameter -r.

setup.exe -r

This will create a file called setup.iss in your winnt directory. Copy thisfile to c:\temp\tdp_exch.

3. Create an installation batch file called setup.bat. It should include thefollowing lines:

c:cd c:\temp\tdp_exchc:\temp\tdp_exch\setup.exe -SMS -s

4. Copy all the files and subdirectories within c:\temp\tdp_exch to your TMRserver or any Managed Node — in our example, /swd_stag/tdp_exch onthe TMR server.

5. Create a Software Distribution Profile in a profile manager (for example,tdp_exch).

6. Go to Properties of the Software Distribution Profile. Enter Source Hostand Directory and check the button Descend into Directories.

7. Edit Platform specific Options for Windows NT.

8. Point the Destination Directory Path to c:/temp.

9. In the After Distribution dialog, enter the path to the installation batch filec:/temp/tdp_exch/setup.bat.

10.Set and close. Now you are ready to distribute this software package toyour Exchange servers.

8.5 Hints and tips

• Exclude database files from normal backup (because they are alwaysopen).

• If you are involving all modules, events, and tasks, documentation iscrucial. Make diagrams, flow charts, and so on, for every event/actioncycle, and test everything thoroughly.

• Make sure that your network is stable, or better yet, fault tolerant. If theevents are not getting through, there can be no action.

• Find out from your application administrators what they want to monitor.The Tivoli Managers for Applications come with many predefinedmonitors, tasks, and possibilities for managing the application itself.


Chapter 9. Tivoli Enterprise features of Tivoli Storage Manager

Tivoli Storage Manager is an enterprise-wide product integrating highlyautomated network backups, restore, archive, storage management, anddisaster recovery. Tivoli Storage Manager is fully functional without TivoliEnterprise, but added benefits such as monitoring and software distributionare attained when Tivoli Storage Manager is integrated with Tivoli Enterpriseand other Tivoli products.

Tivoli Storage Manager integration with various Tivoli productsThe following points are the important issues that enable an organization tocustomize their solutions according to their organizational needs and growth:

• Integration with Tivoli Disaster Recovery Manager to provide intelligent,automated disaster recovery for business continuance

• Integration with Tivoli Space Manager to make the most efficient andeconomical use of distributed storage resources by migratingrarely-accessed files.

• Integration with Tivoli Decision Support for historical trending analysis.

• Integration with Tivoli Data Protection for Applications to enable backupsof major ERP applications, email, and databases.

• Integration with Tivoli Enterprise to enable additional monitoringcapabilities.

In this chapter, we cover the Enterprise features of Tivoli Storage Manager.

9.1 Tivoli Storage Manager enterprise features

The essential information about Tivoli Storage Manager enterprise isdiagrammed in Figure 72.


Figure 72. Tivoli Storage Manager event forwarding

We must emphasize that we do not cover all of the Tivoli Storage Managerconcepts in this book. In order to integrate Tivoli Storage Manager with TivoliEnterprise, and to monitor and manage the system centrally, it is necessaryto set up the following:

• Server-to-server communication

• Event server for central logging

• Forwarding of events to Tivoli Enterprise Console


Tivoli StorageManager

events

data

events Tivoli StorageManager

Backup/ArchiveClient

Operatingsystem


RDBMS

Framework


Tivoli Storage Manager provides capabilities for managing a network ofservers. Server-to-server communication is part of the base Tivoli StorageManager component that gives servers the capability to communicate witheach other. Server-to-server communication is enabled by a series ofdefinitions made on the servers.

Configuring server-to-server communications is a prerequisite for thefollowing Tivoli Storage Manager Enterprise features:

• Configuring and managing multiple servers with an enterpriseconfiguration.

• Storing data on another server using virtual volumes.

• Managing servers from any server: distributing a consistent configurationfor Tivoli Storage Manager servers through a configuration manager tomanaged servers. By having consistent configurations, you can simplifythe management of a large number of servers and clients.

• Central logging: monitoring many servers and clients from a single server.

• Enterprise logon and command routing: performing tasks on multipleservers by using command routing, enterprise logon, and enterpriseconsole.

• Enterprise event logging: sending server and client events to anotherserver for logging.

9.1.1 How to set up server-to-server communicationIn this example, we use the following terminology, as shown in Figure 73:

• Master server (ACMEMASTER) — The server on which server definitionsare created.

• Slave server (ACMESLAVE) — The server or servers defined by themaster server.

Chapter 9. Tivoli Enterprise features of Tivoli Storage Manager 121

Figure 73. Server-to-server communication, enterprise administration

Slave server setup

• Slave server definitions:

Example:set servername ACMESLAVEset serverpassword secret_pswdset crossdefine on

To check that the server definitions are correct, issue query statuscommand.

q statusServer Name: ACMESLAVEServer Low Level Address:Server URL:Crossdefine: OnServer Password set: Yes

ACMEMASTER9.1.151.61

ACMESLAVE9.1.150.113

crossdefine

9.1.150.113:1500


Master server setup

• Master server definitions:

The following four definitions on the master server are passed to the slaveserver and used by that server to perform crossdefined operation of themaster server on the slave server.

Example:

set servername ACMEMASTERset serverpassword serverpasswdset serverhladdress 9.1.151.61set serverlladdress 1500

To check that the server is defined correctly, issue the query statuscommand:

q statusServer Name: ACMEMASTERServer High Level Address: 9.1.151.61Server Low Level Address: 1500Server URL:Crossdefine:offServer Password Set: Yes

Server definitionsDefine the slave servers on the master server. This is done with thecrossdefine option set on the slave server, which allows a server definition forthe slave server on the master server, and a server definition for the masterserver on the slave server.

• Server definitions on master server — example:

define server ACMESLAVE serverpassword=secret_pswd hladdress=9.1.150.113lladdress=1500 crossdefine=yes

9.1.2 Configuring and managing the serversThe enterprise configuration functions of the Tivoli Storage Managerenterprise administration feature make it easier to consistently set up andmanage a network of Tivoli Storage Manager servers. You can set upconfigurations on one server and distribute the configurations to the otherservers. You can make changes to configurations and have the changesautomatically distributed.


To use enterprise configuration, you first select the Tivoli Storage Managerserver that is to act as the configuration manager. You may want to dedicate anew server for this purpose. At the configuration manager, you define thedetails of the server configurations that you want to distribute. For example:

• You set up backup and archive policies and client option sets.

• You designate one or more administrators to have access to the servers,and control their authority levels.

• You define the servers that you want the configuration manager to manageor communicate with, and you set up communications among the servers.

9.1.3 Storing data on another serverTivoli Storage Manager lets one server store data in and retrieve data from astorage pool of another server. This data, stored as virtual volumes, caninclude database and storage pool backups, disaster recovery plan files, anddata that is directly backed up, archived, or space managed from clientnodes. The data can also be a recovery plan file created by using TivoliDisaster Recovery Manager (DRM).

The source server (slave server) is a client of the target server (masterserver), and the data for the source server is managed only by the sourceserver. In other words, the source server controls the expiration and deletionof the files that comprise the virtual volumes on the target server. Thisfunction is available through a licensed feature, server-to-server virtualvolumes.

9.1.4 Managing servers from any serverEnterprise management allows you to manage the servers in your networkfrom many locations. For example, suppose you are an administratorresponsible for servers located in different departments within your company.The servers have some requirements in common, but also have many uniqueclient requirements. You can set up the environment as follows:

• Set up an existing or new Tivoli Storage Manager server as a configurationmanager.

• Set up communications so that commands can be sent from any server toany other server.

• Define any configuration that you want to distribute by defining policydomains, schedules, and so on, on the configuration manager.

• Associate the configuration information with profiles.

• Have the managed servers subscribe to profiles as needed.


• Activate policies and set up storage pools as needed on the managedservers.

• Set up enterprise logging by setting up one server as an event server. Theevent server can be the same server as the configuration manager or adifferent server.

After setting up in this way, you can manage the servers from any server. Youcan do any of the following tasks:

• Use Tivoli Enterprise Console to monitor all the servers in your network.

• Perform tasks on any or all servers using the Tivoli Enterprise Consoleand command routing.

• Manage the group of servers from anywhere in the network. Allow localadministrators to monitor and tune their own servers.

9.1.5 Central monitoringTivoli Storage Manager provides you with several ways to centrally monitorthe activities of a server network:

• Enterprise event logging, in which events are sent from one or more ofservers to be logged at an event server.

• Allowing designated administrators to log in to any of the servers in thenetwork with a single user ID and password.

• Routing query commands to one or more servers in the network.

Enterprise logon and command routingEnterprise logon allows administrators to seamlessly access multiple TivoliStorage Manager systems. The administrative IDs and passwords to be usedmust be the same on all servers that will be accessed. The passwordexpiration period for the servers should be set to the same value through theSET PASSEXP command.

Command routing allows an administrator to send commands from one TivoliStorage Manager server to one or more Tivoli Storage Manager servers thatthe administrator is authorized to access. The following configuration must beperformed to enable administrative command routing:

• Crossdefined server definition must exist between the server where thecommands will be issued and the server to which the commands arerouted.

• The administrative ID and password on the server issuing the commandsmust also be valid on the server where commands are to be routed.


Command syntax:

servername:administrative command

Example:

acmemaster:q db

Enterprise event loggingThis feature enables a server to route the events from a server and its clientsto another server defined as event server. Tivoli Storage Manager server andclient messages provide records of events of Tivoli Storage Manager activity,which Tivoli Storage Manager administrators can use to monitor TivoliStorage Manager. See Figure 74.

Figure 74. Server-to-server event logging

9.1.5.1 How events are routed to the master serverOne or more servers can send events to the master server for central logging.Tivoli Storage Manager provides an event receiver at the sending/slaveserver to receive the enabled events from clients and slave server and thenroutes them to the designated event server. At the event server,administrators can enable one or more receivers for the events being routedfrom slave server.

ServerMessages

EventRules

Tivoli Storage Manager(Slave)

Tivoli Storage ManagerEvent Server (Master)

ClientMessages

ServerConsole

User Exit

File

Activity Log

Tivoli EventConsole

Events EventRules


This is an example of how event logging works. The administrator at eachsending/slave server does the following:

• Identifies the event server:

define eventserver ACMEMASTER

• Enables the logging of severe, errors and warning server messages fromthe sending/slave server and also error messages from all clients to theevent server receiver:

enable events eventserver severe,error,warningenable events eventserver severe,error nodename=*

Tivoli Storage Manager installation package includes a macro ‘ibmtsm.mac’.You can modify this macro for your requirements and run it in Tivoli StorageManager to enable or disable the events you wish to monitor. The following isan example of ibmtsm.mac.

This is part of the original file ibmtsm.mac:

/* ------------------------------------------------------------------ *//* macro to enable recommended messages to Tivoli event receiver *//* TSM Server Development, 17 Dec 1999 *//* ------------------------------------------------------------------ *//* server events *//* start with no info or warning and all error and severe events *//* ------------------------------------------------------------------ */DISABLE EVENTS TIVOLI ALLENABLE EVENTS TIVOLI ERRORENABLE EVENTS TIVOLI SEVERE/* ------------------------------------------------------------------ *//* enable more important info or warning events *//* ------------------------------------------------------------------ */ENABLE EVENTS TIVOLI ANR0400 /* begin client session */ENABLE EVENTS TIVOLI ANR0403 /* end client session */ENABLE EVENTS TIVOLI ANR1400 /* mount denied - canceled */DISABLE EVENTS TIVOLI ANR0572 /* export/import syntax/value errors */DISABLE EVENTS TIVOLI ANR0574 /* export/import syntax/value errors */DISABLE EVENTS TIVOLI ANR0575 /* export/import syntax/value errors */

In the following example, we have changed the file (Tivoli is replaced witheventserver) in order to forward events to the event server.

/*------------------------------------------------------------------ *//* macro to enable recommended messages to eventserver event receiver *//* TSM Server Development, 17 Dec 1999 *//* ------------------------------------------------------------------ *//* server events */


/* start with no info or warning and all error and severe events *//* ------------------------------------------------------------------ */DISABLE EVENTS eventserver ALLENABLE EVENTS eventserver ERRORENABLE EVENTS eventserver SEVERE/* ------------------------------------------------------------------ *//* enable more important info or warning events *//* ------------------------------------------------------------------ */ENABLE EVENTS eventserver ANR0400 /* begin client session */ENABLE EVENTS eventserver ANR0403 /* end client session */ENABLE EVENTS eventserver ANR1400 /* mount denied - canceled */DISABLE EVENTS eventserver ANR0572 /* export/import syntax/value errors */DISABLE EVENTS eventserver ANR0574 /* export/import syntax/value errors */DISABLE EVENTS eventserver ANR0575 /* export/import syntax/value errors */

Logging events to Tivoli Event ConsoleTivoli Storage Manager includes the Tivoli receiver, a Tivoli EnterpriseConsole (TEC) adapter for sending Tivoli Storage Manager events to theTEC.

In the server option file (dsmserv.opt), specify the location of the host onwhich the TEC is running and begins the event logging for the Tivoli receiver.

techhostname 9.114.11.236

Begin event logging for the Tivoli receiver. You do this in one of two ways:

To begin event logging automatically at server start up, specify the followingserver option:

tecbegineventlogging yes

Or enter the following command (this is a one-time command, so werecommend taking the first choice and defining it in a server option file):

begin eventlogging tivoli

Then the administrator enables the events by issuing the ENABLE EVENTScommand for each sending server. For example, for enabling events forACMESLAVE, the administrator enters:

enable events tivoli all servername=ACMESLAVE


9.2 Predefined items

The file ibmtsm.baroc, which is distributed with the server, defines theTivoli Storage Manager event classes to the TEC.

Before the events are displayed on a TEC, you must import ibmtsm.barocinto an existing rule base or create a new rule base and activate it.

9.3 Example of event logging

In Figure 75, we show you an example of event logging for an event fromslave server to master server and then to TEC.

Figure 75. Event logging

To forward an event ANR1400 ‘mount denied/canceled’ from serverACMESLAVE to event server ACMEMASTER and then to TEC, do thefollowing:

• On server ‘ACMESLAVE’, enable the event ANR1400 by issuing followingcommand:

enable events eventserver ANR1400

• On event server ‘ACMEMASTER’, enable events receiving and forwardingto TEC by issuing the following command:

enable events tivoli ANR1400 servername=acmeslave

ServerMessages

ServerMessages

EventRules

Tivoli Storage Manager(Slave)

Tivoli Storage ManagerEvent Server (Master)

ClientMessages

ServerConsole

User Exit

File

Activity Log

Tivoli EventConsole

Events EventRules

REC


When event receiver on server ‘ACMESLAVE’ receives an event with eventnumber ANR1400, it checks it with event rules to see if this event is enabledor not. The event ANR1400 will be routed to the master server. On the masterserver Receiver Engine ‘REC’ receives the event ANR1400 and forwards theevent to TEC, where it will be handled in order the rules set for each specificevent.

Testing event loggingYou can test that the event logging is working as it should by issuing theEVGEN command.This command generates an event with the event numberspecified by you. By querying the activity log, you can see if your event isgenerated.

For example:

evgen 1400q actlogANR2017I Administrator ADMIN issued command: EVGEN 1400ANR1400W Mount request denied for volume - mount canceled.

9.4 Hints and tips

• Most of the manual checks can be automated and monitored centrally byTEC.

• Make a list of events you find useful to monitor and enable these events forevent logging. For example, check if backup is missed, event numberANR2578.


Chapter 10. Tivoli Service Desk

The Tivoli Service Desk application is designed to handle all issuesconcerning its three components throughout the enterprise. These can be ofspecial interest for a Tivoli Storage Manager administrator. Tivoli ServiceDesk can contribute especially in supporting customers, who have problemswith their installation or operation of Tivoli Storage Manager clients.

In this chapter we show how to customize Tivoli Service Desk enhancementsto integrate with Tivoli Storage Manager and other Tivoli products like TivoliInventory.

However, we do not cover the components of Tivoli Service Desk, or itsstructure. The complete suite of products is too extensive to fit in the scope ofthis redbook. Therefore, our starting point will be a complete and functionalinstallation of Tivoli Service Desk. If you need additional information on setupor structure, refer to other documentation mentioned in Appendix B, “Relatedpublications” on page 161.

10.1 Overview

Tivoli Service Desk (Figure 76) is a standalone product, because:

• It does not require any Framework components.

• In its operation, it does not require any other products.

However, it can be configured to interoperate in the following ways:

• You can start the Tivoli Storage Manager administrative Web client.

• You can gather asset information from Tivoli Inventory.

• You can generate problem records triggered by TEC events (not covered).


Figure 76. Tivoli Service Desk

10.2 Customizing Tivoli Service Desk

In order to access the features mentioned above, you must customize theTivoli Service Desk profile for your administrative user. For these examples,we use the built-in user EXAV. After logging in to Tivoli Service Desk, you willsee a window similar to the one shown in Figure 77.

Figure 77. Tivoli Service Desk main window

After a standard installation of Tivoli Service Desk, there will be no menuentries for starting the Tivoli Storage Manager administrative Web client, nor


TivoliStorage

Manager

TivoliServiceDesk

RDBMS

eventsdatamigration

TivoliInventory


RDBMS

launch web admin client

Framework


for the integration of Tivoli Inventory. In order to add these entries to themenus, the steps described in the following sections are required.

10.2.1 Editing a Tivoli Service Desk user profileIn the Edit pull-down menu, you will find the entry Profiles. This starts theprofile editor of Tivoli Service Desk. See Figure 78.

Figure 78. Configuration of a user profile in Tivoli Service Desk

You will need to choose the Profile Name you wish to edit. In our example forthe user EXAV, this would be Tivoli Service Desk Administrator. Then, inthe General tab of this screen, you must Add new action groups. Here youneed Tivoli Framework Integration and Data Utilities. After this, you mustadd the specific action to either the tool bar or the menu. For adding this to

Chapter 10. Tivoli Service Desk 133

the menus, choose the Menu Items tab and click the Menu Bar button. Thecurrent menu bar appears, and you need to insert the action where you wantit. We chose the Configuration drop-down menu.

Finally, you need to add the system actions ADSM Web Administration andTivoli Inventory Migration Utility. Choose an appropriate name to displaythe menu entries (for example, TSM Web Administration).

An action group consists of system actions. The Tivoli FrameworkIntegration action group includes the ADSM Web Administration systemaction (Figure 79).

Figure 79. Action groups in Tivoli Service Desk

As you can see in the lower end of the picture, the Tivoli FrameworkIntegration action group is defined in the file tivint. Tivoli Service Deskbuilds its components from scripts, which are parsed to binary files. Thisenables you to modify each component and customize your environment.


A system action, for example, ADSM Web Administration, calls asubfunction in the tivint file called ADSMInterface (Figure 80).

Figure 80. System actions in Tivoli Service Desk

If you want to know more about parsing scripts and customizing Tivoli ServiceDesk, see the Tivoli Service Desk Users Guide, GC31-5205.

For example, the system action ADSM Web Administration starts only theserver component on port 1580. You could add a procedure to the filetivint.kb to start the Tivoli Storage Manager Backup-Archive WebClient on port 1581. This would enable your helpdesk staff to helpcustomers directly by restoring or backing up their files on their clientmachines.

Customizing functions


After you have finished editing the profile, you must close the Tivoli ServiceDesk interface and restart it in order to see the changes you made.

10.2.2 Starting the Tivoli Storage Manager administrative clientNow you should see the menu item you added. Choose starting the Webclient and you should see the following dialog box (Figure 81) on launchingthe Tivoli Storage Manager Web administrative client from Tivoli ServiceDesk.

Figure 81. Launching administrative client from Tivoli Service Desk

Enter the name of the Tivoli Storage Manager to which you want to connect,and your default browser should come up (Figure 82).

Figure 82. Tivoli Storage Manager Web administrative client


10.2.3 Migrating assets from Tivoli InventoryTo import information from the Tivoli Inventory database to Tivoli ServiceDesk Asset Management, you must set up an additional databaseconnection. Since Tivoli Service Desk is not a part of the Tivoli ManagementFramework, it cannot use the RIM object to access the Inventory database.

In our example, we are running the Tivoli Service Desk on a Windows NTserver on Microsoft SQL server. The Tivoli environment is running on an AIXmachine with DB2 as database. In order to access the DB2 Inventorydatabase from the NT machine, you must install a DB2 client and configure itas an ODBC source. After this, you must start the TSDBuild application onTivoli Service Desk and add the second database to the list of availabledatabases (Figure 83).

Figure 83. Configuring the Tivoli Inventory database into Tivoli Service Desk

Then go to the main menu and, in the Asset Management pull-down menu,choose the Configure Asset Management entry. Go to the Migration taband choose Tivoli Inventory and select the database source.


After that, from your previous added entry, choose the Tivoli InventoryMigration Utility. This will open a dialog box as shown in Figure 84.

Figure 84. Importing assets from Tivoli Inventory into Tivoli Service Desk

After you have clicked the Find button, the machines from your TivoliInventory repository should be displayed, and can be added to your TivoliService Desk database by choosing Migrate.

Since this procedure is a migration, you should schedule it to keep track ofthe changes made to the Inventory database.

Note


10.2.4 Opening a call in Tivoli Service DeskNow, with the changes in place, you can respond to incoming problemrecords (Figure 85) by instantly opening the administrative Web client of TivoliStorage Manager and by directly accessing asset information from yourrepository of machines.

Figure 85. Opening a call in Tivoli Service Desk

10.3 Hints and tips

• Add your own actions to Tivoli Service Desk.

• Schedule the migration from Tivoli Inventory to keep track of changes.

• Post status messages from your Tivoli Storage Manager serverenvironment to Tivoli Service Desk to allow the helpdesk staff to quicklyresolve problems occurring from server outages, and so on.


Part 3. Putting it all together

Part 3 provides examples of using the various Tivoli products and modules toshow how they can all work together to ease the load of the storagemanagement staff.


Chapter 11. Examples

Here are few examples to show what can be done using tools provided byTivoli Storage Manager and Tivoli Enterprise. Examples are written forspecific scenarios, but with minor modifications, can be used in manysituations. In the examples, some steps refer to procedures described in theprevious chapters.

11.1 Updating the Tivoli Storage Manager backup-archive client

Let us consider an example of operating the Tivoli Storage manager in TivoliEnterprise. In our scenario, the code for one of the Tivoli Storage Managerbackup-archive clients is not up-to-date, and this produces an error. Theadministrator of TEC has created a rule which increases the severity of thisevent if there are more than two events within one week.

At the same time, a message is sent to the Tivoli Service Desk (TSD)administrators for Problem Management, requesting that they open a ChangeRequest to update the software code. The event is displayed on theadministrator’s event console, and Tivoli Inventory can be used for queryingthe current software level data. After the Change Request from the TivoliService Desk is approved, an administrator performs an upgrade of the TivoliStorage Manager backup-archive client with Tivoli Software Distribution. Theresult, a successful upgrade, is also sent to TSD. After software distributionhas been accomplished, a software inventory scan is performed to update theclient’s data.

ImplementationIn a situation where a client has software code that is much older than thecode on the server, it cannot access the server. This gives the error messageANR0428W:

ANR0428W Session session number for node node name (client platform)refused - client is down-level with this server version.

The explanation of this message shows that the client needs new softwarecode for operating. The message type is W, which maps into Warning onTivoli Storage Manager. Our first task is to make sure that this event isrecorded by TEC. You need to check whether event logging on eventserveris on, what severity types are forwarded, and to which receivers.


To query the rules, you can use the following commands:

tsm: ACMESLAVE>query eventrules

Date/Time Server Event Rules--------------------------------------------------------------------------06/01/00 17:29:12 DISABLE EVENTS EVENTSERVER ALL06/01/00 17:29:12 ENABLE EVENTS EVENTSERVER ERROR06/01/00 17:29:12 ENABLE EVENTS EVENTSERVER SEVERE06/01/00 17:29:13 ENABLE EVENTS EVENTSERVER ANR521606/01/00 17:29:13 ENABLE EVENTS EVENTSERVER ANR5217

The result is the list of currently active rules. By default, messages withseverity type warning are not included in supplied macro ibmtsm.mac. Youcan enable just this event, or the whole severity warning range of events. Thecommands for these tasks may only apply to this message:

ENABLE EVENTS TIVOLI ANR0428

Or, they can apply to all messages with severity type warning:

ENABLE EVENTS TIVOLI WARNING

The next checkpoint is the TEC event class definition file. You must list theclass defined in our rule base. The list of all class definitions can be long, soit is better to grep out just our message:

brazil:/ > wlsrbclass itso | grep ANR0428TSM_SERVER_ANR0428

To test that this message really comes to the TEC, you can simulate themessage on Tivoli Storage Manager server with the command:

tsm: ACMESLAVE>evgen 0428

This should produce an event in TEC within TSM_SERVER_ANR0428 eventclass and warning severity. The next step is to create the rules and tasks forincreasing severity and notifying Tivoli Service Desk operators. You need toopen the rule base and edit or add a new rule set. With a right-mouse click,you select Edit Rules in the Event Server Rule Bases window. In the ruleset window, you select Rule Set, New Ruleset, replace name new_set withanother one, and click Enter to add this rule set to the rule base (Figure 86).

Next, you select this rule set and open it with Rule Set, Edit Ruleset. Intothis window, you must fill in rules for the event. With the graphical rule builder,you can create two types of rules. A simple rule is a rule in which you canuse one event class. With a compound rule, you can correlate events fromdifferent classes.


Figure 86. Rule sets

First you create a rule for increasing severity, if an event repeats multipletimes in a limited time window, and there is no response from administrators.You select New Rule, Simple. In the Description field, you type thedescription of the rule. With the Event Class button, you invoke a list ofavailable event classes, and select the class for the rule. In our scenario, thecorrect class is TSM_SERVER_ANR0428. See Figure 87.

Chapter 11. Examples 145

Figure 87. New Simple Rule

With the Conditions button, you open a window in which you can setconditions for this rule on each of the slots of the selected event class. In ourscenario, you are going to apply this rule only on events which are not closedor acknowledged. In the condition window, you select status as an attribute.In the Relation pull-down list, you select Not in list, and in the AttributeValue(s) section, from the Select Value menu, you select CLOSED andACK. With Add, you fill in the values after each selection. You can setmultiple conditions. See Figure 88.


Figure 88. Condition in Rule

The next step is to set the actions. With the Actions button, you open thiswindow, and select from the Add pull-down list: When frequency exceedsthe limit. In the Actions section, you select Set severity from the menu, andunder Set severity to, you enter the value MINOR. In the Edit When to Runsection, you set the wanted frequency. You type in 3 under When frequencyexceeds and 10080 under within a min. period. Click Enter to add this valueto the action. The action can be observed in the Action Synopsis section ofthe window. See Figure 89.


Figure 89. Actions in Rule

Click OK for actions, and you have finished creating this rule. Next, you willadd two more rules for sending e-mail to the TSD operators for opening theproblem and placing a Change Request. For those rules, you do not need toset conditions, and actions can be from the TEC tasks library send e-mail.With Tivoli Service Desk and Enterprise Console integration, you canautomate this task. Now you have three rules in your rule set. With Rule Set,Close, you go back to the rule base window, and you need to save themodified rule base with Rule Base, Save.

What remains is to compile, load, and activate the rule base. This is explainedin Chapter 6, “Tivoli Enterprise Console” on page 85. In this scenario, theadministrator’s responsibility also includes importing the correct softwaresignature to the inventory tables, distributing the scan profile, and executingsoftware and hardware scans with Tivoli Inventory. These procedures aredescribed in Chapter 5, “Tivoli Inventory” on page 69. After authorization orrequest from the Tivoli Service Desk operator, Tivoli Software Distribution canbe used to upgrade the client. This example is covered in Chapter 4, “TivoliSoftware Distribution” on page 55.


11.2 Extending the Tivoli Storage Manager recovery log

The next example is a scenario when the log is becoming full. You are goingto observe the log with Distributed Monitors and events in the TEC console.When one of those conditions is fulfilled, then you want to create anadditional Tivoli Storage Manager security log file and extend the logautomatically.

ImplementationYou have the Distributed Monitoring monitor, provided by the Plus Module forADSM, which measures occupancy of the Tivoli Storage Manager log, andyou have event forwarding to the TEC. When the log is full, Tivoli StorageManager posts a message to the activity log, which is forwarded to the TEC.Tivoli Distributed Monitoring monitors measure certain parameters in ourscenario percentage of log full. When log occupancy exceeds the limits youset in the monitor, severity is changed. In the monitor, TEC forwarding mustbe enabled to display this event at the TEC console.

Both of these events will generate a new event, which will drop all events fromthose event classes in a specific time window, execute the necessary tasks,and after successful correction, close the event. This is necessary becauseyou don’t know which one of these events is going to trigger the action. First,you have to create a new event. For this, you need a new event class. You canadd this class into the existing file or create a new one. Also, you have toconsider where this event class is going to be in the event class structure.The new file could look like this:

brazil:/ > more custom.barocTEC_CLASS:

tsm_log_full_cust ISA EVENTDEFINES {

msg: default = "Custom message for the log full event";};

END

You must to import this file into the active rule base, compile the rule base,and restart the event server. The next task is creation of the rules. You needto create two rules, one for each original event. This rules should generate anew event from the previously defined event class. The monitoring data ismapped into the universal_ncustom class, and the Tivoli Storage Manageractivity log message is mapped into the TSM_SERVER_ANR0130 class. Theevents must have critical severity and must not be closed.


You control the triggering level of distributed monitoring with mapping intoseverity. In our scenario, an event becomes critical if the log is more than 95%full. After generating a new event, the original ones are dropped. You set theseverity of the new generated event to minor and drop any other event fromthis class, which the event server receives in a 15-minute time window. Thefrequency of monitoring probes is set by the parameter in the monitor itself.The rules could look like this:

brazil:/ > cat custom.rlsrule:

trigger_monitor: (event:_event of_class 'universal_ncustom'where [

status: outside ['CLOSED'],severity: equals 'CRITICAL',hostname:_host],

action: (generate_event('tsm_log_full_cust',[severity='MINOR',

hostname=_host]),drop_received_event)

).rule:

trigger_log: (event:_event of_class 'TSM_SERVER_ANR0130'where [

status: outside ['CLOSED'],severity: equals 'CRITICAL',hostname:_host],

action: (generate_event('tsm_log_full_cust',[severity='MINOR',

hostname=_host]),drop_received_event)

).rule:

drop_events: (event:_event of_class 'tsm_log_full_cust'where [

status: outside ['CLOSED']],

action:(first_duplicate(_event, event:_dup_eventwhere [status: outside ['CLOSED']],


_event - 900 - 900),add_to_repeat_count(_dup_event, 1),drop_received_event)

).

For the action, you can create another rule manually or with the graphical rulebuilder, or you can use an automated task. Rule sets made by the graphicalrule builder cannot be edited with the manual one. You will use the graphicalrule builder for creating a rule that extends the Tivoli Storage Managerrecovery log when the event server receives a generated event. You create anew rule set, and in this one, a new rule. In the Tivoli Plus Module for ADSM,you have a task for extending the log. So this rule could read: if the log is fullor an event is not closed, then extend the log. See Figure 90.

Figure 90. Extend log rule

Besides the user name and password, this task requires the file name of thelog file. You are going to use the date_reception value for the file name,because this parameter generates a number which represents the time. Inthis case, you get a unique file name for the recovery log file. In the rulebuilder, below the Select Task button, you have Edit Arguments. This buttoninvokes the window for the parameters which are required for the specifictask. In the Format string (optional) section, you type the task’s parameters.


Variables are invoked from the event slot values, which you must select. Inour scenario you need to select the task itself and pass to the taskinformation about task library, host name, where to execute the task, loginparameters, and the name of the log file. If the file name already exists, thetask will fail. See Figure 91.

Figure 91. Extend log arguments

The last step is closing the events. When log volume is added to the TivoliStorage Manager, the message with code ANR2017I is generated. You aregoing to use this message to close previous warning for log full. For this, youcan again use the graphical rule builder. You are going to close all eventsfrom this class in a 5-minute time window, if they are generated by the samehost. See Figure 92.


Figure 92. Compound Rule

After successful creation of the recovery log files and extension of therecovery log, you get two confirmation messages. The first one is forsuccessful creation of the log file, and the second one is for extend itself, soyou must create a similar rule for that situation too. With this last rule, youclose all events except information about the successful extend of the log withharmless severity, to notify the Event Console administrator.

11.3 Offline backup of the Exchange server

Periodically, you may want to make an image of your system, by stopping thedatabase or groupware servers and then making a backup by file. In thisexample, you are going to use Microsoft Exchange 5.5 server, with TivoliManager for MS Exchange. In this scenario, you first stop the MicrosoftExchange server. When the server is stopped, you start the backup, andwhen the backup is finished, you start the Exchange server.


ImplementationYou begin the procedure with stopping the server. For managing the MSExchange services, you can use already configured tasks and jobs from theExchange Server Tasks task library. You have to schedule theStop_Services_Job to run at a specific time, periodically. To add the job tothe scheduler, you have to drag and drop the job icon in the scheduler icon,and you get the job parameters dialog window, where you need to select theservices you want to stop. See Figure 93.

Figure 93. Stop_Services parameters

The next window with which you are prompted is the scheduler window. Inthis window, you need to fill in the time parameters of the scheduled job. Forinformation about scheduler parameters, you can refer to Chapter 2, “TivoliFramework TME 10” on page 21. Tivoli Manager for Exchange with setupenables monitors to report the status of the event server. See Figure 94.


To separate the automated and planned stop of the Microsoft Exchangeservices from the manual stop or failures, you make a reference event. Youschedule to post this event at the same time as stopping of the services. Theevent must be in its own event class, in order to have a clear message thatthe scheduled service stop occurred. You must create a new event class,create a job wit the send_event task from the T/EC Tasks task library, andschedule the job.

Figure 94. Send_Event task parameters

Our backup should start when the Exchange server stops, and only when it isscheduled. In order to avoid unnecessary triggering of the backup, you createa rule which starts the backup when the event you scheduled to be postedand the Exchange stop come in a 10-minute time window. Backup is done byposting the immediate client action to the client schedule. First you create ascript for adding the immediate client action. A simple script is:

#!/bin/ksh/usr/tivoli/tsm/client/ba/bin/dsmadmc -id=admin -passw=admin def clientaaral act=i opt="-subdir=yes" obj="d:\exchsrvr"

From this script, you create a task for the Microsoft Exchange server backup.With trigger, condition and action you create a rule for backup:


rule: do_backup:(event:_event of_class 'exchg_sched_serv_stop'where [ status: outside ['CLOSED']],action: (all_instances(event:_exchg_ev of_class 'MSExchange_Event'where [ status: equals 'OPEN'],_event - 600 - 600 ),

exec_task(_exchg_ev,'exch_back','-l "acme_task" -h "palana" -m"3600"',[],'NO'))

).

You will be using immediate client action because you need confirmation thatthe backup job has finished. When the backup job is finished, the TivoliStorage Manager server forwards the event to the TEC console. This event isin the NT_Base event class, so you must first create a separate event classfor this event and modify the Windows NT adapter file. Here is an example ofclass definition file modification:

TEC_CLASS:tsm_back_succ ISA NT_Base;

END

For the Windows NT adapter format file, you take a file which is alreadymodified by Tivoli Manager for Exchange and add a separate instance for anew event class:

FORMAT tsm_back_succ FOLLOWS NT_Base%t %s %s %s %s %s AdsmClientService %s %s %s Successfully Completed.category $3eventType $4id $7END

Now you have information on when the Exchange backup is completed. Whenevent from the tsm_back_succ event class is posted on the TEC eventconsole, you execute the task from the Exchange Server Tasks task libraryStart_Services. The simple example of the rule could look like this:

rule: start_exchg:(event:_event of_class 'tsm_back_succ'where [ status: outside ['CLOSED']],action: (exec_task(_event,'Start_Services','-l "Exchange Server

Tasks" -h "@MSExchange:Exchange_Server_aral" -m "3600" -a "Y" -a "Y" -a "N"-a "N" -a "N" -a "Y" -a "N" -a "Y" -a "N" -a "Y"',[],'NO'))

).

When starting the Microsoft Exchange server, you can close all remainingmessages.


Appendix A. Special notices

This publication is intended to help storage administrators to understand howthe features of Tivoli Enterprise can help them in their day-to-day activitiesand responsibilities. The information in this publication is not intended as thespecification of any programming interfaces that are provided by TivoliStorage Manager or Tivoli Enterprise products. See the PUBLICATIONSsection of the IBM Programming Announcement for Tivoli products for moreinformation about what publications are considered to be productdocumentation.

References in this publication to IBM products, programs or services do notimply that IBM intends to make these available in all countries in which IBMoperates. Any reference to an IBM product, program, or service is notintended to state or imply that only IBM's product, program, or service may beused. Any functionally equivalent program that does not infringe any of IBM'sintellectual property rights may be used instead of the IBM product, programor service.

Information in this book was developed in conjunction with use of theequipment specified, and is limited in application to those specific hardwareand software products and levels.

IBM may have patents or pending patent applications covering subject matterin this document. The furnishing of this document does not give you anylicense to these patents. You can send license inquiries, in writing, to the IBMDirector of Licensing, IBM Corporation, North Castle Drive, Armonk, NY10504-1785.

Licensees of this program who wish to have information about it for thepurpose of enabling: (i) the exchange of information between independentlycreated programs and other programs (including this one) and (ii) the mutualuse of the information which has been exchanged, should contact IBMCorporation, Dept. 600A, Mail Drop 1329, Somers, NY 10589 USA.

Such information may be available, subject to appropriate terms andconditions, including in some cases, payment of a fee.

The information contained in this document has not been submitted to anyformal IBM test and is distributed AS IS. The use of this information or theimplementation of any of these techniques is a customer responsibility anddepends on the customer's ability to evaluate and integrate them into thecustomer's operational environment. While each item may have beenreviewed by IBM for accuracy in a specific situation, there is no guarantee


that the same or similar results will be obtained elsewhere. Customersattempting to adapt these techniques to their own environments do so at theirown risk.

Any pointers in this publication to external Web sites are provided forconvenience only and do not in any manner serve as an endorsement ofthese Web sites.

The following terms are trademarks of the International Business MachinesCorporation in the United States and/or other countries:

The following terms are trademarks of other companies:

Tivoli, Manage. Anything. Anywhere.,The Power To Manage., Anything.Anywhere.,TME, NetView, Cross-Site, Tivoli Ready, Tivoli Certified, PlanetTivoli, and Tivoli Enterprise are trademarks or registered trademarks of TivoliSystems Inc., an IBM company, in the United States, other countries, or both.In Denmark, Tivoli is a trademark licensed from Kjøbenhavns Sommer - TivoliA/S.

C-bus is a trademark of Corollary, Inc. in the United States and/or othercountries.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Sun Microsystems, Inc. in the United States and/or othercountries.

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

PC Direct is a trademark of Ziff Communications Company in the UnitedStates and/or other countries and is used by IBM Corporation under license.

ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of IntelCorporation in the United States and/or other countries.

UNIX is a registered trademark in the United States and other countrieslicensed exclusively through The Open Group.

IBM �

400RedbooksRedbooks Logo

Domino S/390Lotus SPLotus Notes SP1Notes SP2


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

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

Appendix A. Special notices 159

Appendix B. Related publications

The publications listed in this section are considered particularly suitable for amore detailed discussion of the topics covered in this redbook.

B.1 IBM Redbooks publications

For information on ordering these publications see “How to get IBMRedbooks” on page 165.

Book Title PublicationNumber

Tivoli Enterprise Performance Tuning Guide SG24-5392Tivoli Storage Manager Version 3.7: Technical Guide SG24-5477A Project Guide for Deploying Tivoli Solutions SG24-5310ADSM Operation and Management with TME 10 SG24-2214ADSM Server for Windows NT Configuration and Recovery Examples SG24-4878ADSM Server-to-Server Implementation and Operation SG24-5244ADSM/6000 on 9076 SP2 GG24-4499All About Tivoli Management Agents SG24-5134An Industry Around the Tivoli Framework: Examples from the 10/Plus Association SG24-2122An Introduction to Tivoli Enterprise SG24-5494An Introduction to Tivoli's TME 10 SG24-4948Backup, Recovery, and Availability with DB2 Parallel Edition on RISC/6000, SG24-4695ADSM Client Disaster Recovery: Bare Metal Restore SG24-4880Creating Custom Monitors for Tivoli Distributed Monitoring SG24-5211Deploying a Tivoli Infrastructure in Large-Scale Environments SG24-5210Designing Tivoli Solutions for End-to-End Systems and Service Management SG24-5104Developing Plus Modules for Tivoli with the TME 10 Integration Toolkit SG24-2007Getting Started with Tivoli Storage Manager: Implementation Guide SG24-5416High Availability Scenarios for Tivoli Software SG24-2032Implementing Tivoli Manager for Windows NT SG24-5519Implementing Tivoli Remote Control in Large Enterprises SG24-5125Laying the Foundation for Tivoli Modules SG24-5379Managing Domino/Notes with Tivoli Manager for Domino, Enterprise Edition, Version 1.5 SG24-2104Managing RDBMS Servers With Tivoli SG24-5240Managing SAP R/3 with Tivoli SG24-5298New Features in Tivoli Software Distribution 3.6 SG24-2045Problem Management Using Tivoli Service Desk and the TEC SG24-5301TEC Implementation Examples SG24-5216Tivoli Enterprise Internals and Problem Determination SG24-2034Tivoli Enterprise Management Across Firewalls SG24-5510Tivoli Service Desk V6.0 - IT Infrastructure Planning Guide SG24-5312Tivoli Storage Management Concepts SG24-4877TME 10 Cookbook for AIX: Systems Management and Networking Applications SG24-4867TME 10 Deployment Cookbook: Courier and Friends SG24-4976TME 10 Deployment Cookbook: Inventory and Company SG24-2120TME 10 Framework Version 3.2: An Introduction to the Lightweight Client Framework SG24-2025


B.2 IBM Redbooks collections

Redbooks are also available on the following CD-ROMs. Click the CD-ROMsbutton at ibm.com/redbooks for information about all the CD-ROMs offered,updates and formats.

B.3 Tivoli publications

These publications are also relevant as further information sources:

TME 10 Inventory 3.2: New Features and Database Support SG24-2135Using ADSM to Back Up and Recover Microsoft Exchange Server SG24-5266Using ADSM to Back Up Databases SG24-4335Using Databases with Tivoli Applications and RIM SG24-5112Using Tivoli Software Installation Service for Mass Installation SG24-5109Using Tivoli Storage Manager to Back Up Lotus Notes SG24-4534Using Tivoli to Manage a Large-Scale SAP R/3 Environment SG24-5500Using TSM in a Clustered Windows NT Environment SG24-5742Windows NT Backup and Recovery with ADSM SG24-2231

CD-ROM Title Collection KitNumber

IBM Networking Redbooks Collection SK2T-6022IBM Transaction Processing and Data Management Redbooks Collection SK2T-8038IBM Lotus Redbooks Collection SK2T-8039Tivoli Redbooks Collection SK2T-8044IBM Netfinity Hardware and Software Redbooks Collection SK2T-8046IBM RS/6000 Redbooks Collection (PDF Format) SK2T-8043

IBM Application Development Redbooks Collection SK2T-8037IBM Enterprise Storage and Systems Management Solutions SK3T-3694


Tivoli Asset Management Inventory Integration System Administration GC31-5204Tivoli Asset Management Inventory Integration User’s Guide GC32-0288

Tivoli Asset Management System Administrator’s Guide GC31-5195Tivoli Asset Management User’s Guide GC31-5194Tivoli Change Management System Administrator’s Guide GC31-5188Tivoli Change Management User’s Guide GC31-5190Tivoli Data Protection for Informix V3R7: Installation and User’s Guide SH26-4095Tivoli Data Protection for Lotus Domino for UNIX V1R1: Installation and User’s Guide SH26-4088





Tivoli Data Protection for Lotus Domino for Windows NT V1R1: Installation and User’sGuide

GC26-7320

ADSMConnect Agent for Lotus Notes on AIX Installation and User’s Guide SH26-4067

ADSMConnect Agent for Lotus Notes on Windows NT Installation and User’s Guide SH26-4065ADSMConnect Agent for Microsoft Exchange Server Installation and User’s Guide SH26-4071ADSMConnect Agent for Microsoft SQL Server Installation and User’s Guide SH26-4069ADSMConnect Agent for Oracle Backup on AIX Installation and User’s Guide SH26-4061ADSMConnect Agent for Oracle Backup on HP-UX Installation and User’s Guide SH26-4073ADSMConnect Agent for Oracle Backup on Sun Solaris Installation and User’s Guide SH26-4063

ADSMConnect Agent for Oracle Backup on Windows NT Installation and User’s Guide SH26-4086Tivoli Decision Support 2.1 Administrator Guide GC32-0437Tivoli Decision Support 2.1 Installation Guide GC32-0438Tivoli Decision Support 2.1 User’s Guide GC32-0436Tivoli Distributed Monitoring 3.6 Collection Reference SC31-5118Tivoli Distributed Monitoring 3.6 Release Notes (supplied with the product) GI10-3023

Tivoli Distributed Monitoring 3.6.1 Release Notes (supplied with the product) GI10-8021Tivoli Distributed Monitoring for OS/390 V3.6.1 GI10-8043Tivoli Distributed Monitoring User’s Guide 3.6 GC31-8382Tivoli Framework 3.6 User’s Guide GC31-8433Tivoli Framework 3.6.1 Release Notes (supplied with the product) GI10-8014Tivoli Inventory 3.6.1 Release Notes (supplied with the product) GI10-8018

Tivoli Inventory for OS/390 V3.6.1 Release Notes (supplied with the product) GI10-8048Tivoli Problem Management Distributed Data Manager SystemAdministrator’s Guide

GC31-5184

Tivoli Problem Management System Administrator’s Guide GC31-5173Tivoli Problem Management User’s Guide GC31-5175Tivoli Service Desk Administration User’s Guide GC31-5205Tivoli Service Desk Installation Guide GC31-5167

Tivoli Software Distribution 3.6 Release Notes (supplied with the product) GI10-3014Tivoli Software Distribution 3.6.1 Release Notes (supplied with the product) GI10-8019Tivoli Software Installation Service 3.6.1 Release Notes (supplied with the product) GI10-8015Tivoli Software Installation Services 3.6 User’s Guide GC31-5121Tivoli Storage Manager for AIX Version 3.7 Administrator’s Guide GC35-0368Tivoli Storage Manager for AIX Version 3.7 Administrator’s Reference GC35-0369

Tivoli Storage Manager for AIX Version 3.7 Quick Start GC35-0367Tivoli Storage Manager for AS/400 Version 3.1.2 Administrator’s Guide GC35-0315Tivoli Storage Manager for AS/400 Version 3.1.2 Administrator’s Reference GC35-0316Tivoli Storage Manager for AS/400 Version 3.1.2 Quick Start GC35-0317Tivoli Storage Manager for HP-UX Version 3.7 Administrator’s Guide GC35-0371Tivoli Storage Manager for HP-UX Version 3.7 Administrator’s Reference GC35-0372


Appendix B. Related publications 163

Tivoli Storage Manager for HP-UX Version 3.7 Quick Start GC35-0370

ADSTAR Distributed Storage Manager for MVS Version 3.7 Administrator’s Guide GC35-0277ADSTAR Distributed Storage Manager for MVS Version 3.7 Administrator’s Reference GC35-0278ADSTAR Distributed Storage Manager for MVS Version 3.7 Quick Start GC35-0276ADSM for OS/2 Version 3.1 Messages SH35-0133Tivoli Storage Manager for Sun Solaris Version 3.7 Administrator’s Guide GC35-0374Tivoli Storage Manager for Sun Solaris Version 3.7 Administrator’s Reference GC35-0375

Tivoli Storage Manager for Sun Solaris Version 3.7 Quick Start GC35-0373Tivoli ADSM for VM Version 3.1 Quick Start GC35-0351Tivoli Storage Manager for Windows NT Version 3.7 Administrator’s Guide GC35-0380Tivoli Storage Manager for Windows NT Version 3.7 Administrator’s Reference GC35-0381Tivoli Storage Manager for Windows NT Version 3.7 Quick Start GC35-0379Tivoli Storage Manager Version 3.7 AFS/DFS Backup Clients SH26-4106

Tivoli Storage Manager Version 3.7 Installing the Clients SH26-4102Tivoli Storage Manager Version 3.7 Messages GC35-0382Tivoli Storage Manager Version 3.7 Reference Cards for the Backup-Archive Clients SX26-6021Tivoli Storage Manager Version 3.7 Trace Facility Guide SH26-4104Tivoli Storage Manager Version 3.7 Using the Application Programming Interface SH26-4107Tivoli Storage Manager Version 3.7 for NetWare Using the Backup-Archive Client SH26-4100

Tivoli Storage Manager Version 3.7 for UNIX Using the Backup-Archive Client SH26-4105Tivoli Storage Manager Version 3.7 for Windows Using the Backup-Archive Client SH26-4101TME 10 Enterprise Console 3.6.1 Release Notes (supplied with the product) GI10-8020TME 10 Enterprise Console Adapters Guide Version 3.6 SC31-8507TME 10 Enterprise Console Rule Builder’s Guide Version 3.6 SC31-8508TME 10 Enterprise Console User’s Guide Version 3.6 GC31-8506

TME 10 Framework 3.6 Planning & Installation Guide SC31-8432TME 10 Framework 3.6 Reference Manual SC31-8434TME 10 Framework Release Notes Version 3.6 GI10-3028TME 10 Inventory 3.6 Release Notes (supplied with the product) GI10-3011TME 10 Inventory 3.6 User’s Guide GC31-8381

TME 10 Software Distribution 3.6 AutoPack Guide GC32-0294TME 10 Software Distribution 3.6 Reference Manual SC31-8331TME 10 Software Distribution 3.6 User’s Guide GC31-8330TME 10 Tivoli/Plus ADSM User's Guide GC31-8405Tivoli Framework Version 3.7 User’s Guide GC31-8433



How to get IBM Redbooks

This section explains how both customers and IBM employees can find out about IBM Redbooks,redpieces, and CD-ROMs. A form for ordering books and CD-ROMs by fax or e-mail is also provided.

• Redbooks Web Site ibm.com/redbooks

Search for, view, download, or order hardcopy/CD-ROM Redbooks from the Redbooks Web site.Also read redpieces and download additional materials (code samples or diskette/CD-ROM images)from this Redbooks site.

Redpieces are Redbooks in progress; not all Redbooks become redpieces and sometimes just a fewchapters will be published this way. The intent is to get the information out much quicker than theformal publishing process allows.

• E-mail Orders

Send orders by e-mail including information from the IBM Redbooks fax order form to:

• Telephone Orders

• Fax Orders

This information was current at the time of publication, but is continually subject to change. The latestinformation may be found at the Redbooks Web site.

In United States or CanadaOutside North America

e-mail [email protected] information is in the “How to Order” section at this site:http://www.elink.ibmlink.ibm.com/pbl/pbl

United States (toll free)Canada (toll free)Outside North America

1-800-879-27551-800-IBM-4YOUCountry coordinator phone number is in the “How to Order”section at this site:http://www.elink.ibmlink.ibm.com/pbl/pbl

United States (toll free)CanadaOutside North America

1-800-445-92691-403-267-4455Fax phone number is in the “How to Order” section at this site:http://www.elink.ibmlink.ibm.com/pbl/pbl

IBM employees may register for information on workshops, residencies, and Redbooks by accessingthe IBM Intranet Web site at http://w3.itso.ibm.com/ and clicking the ITSO Mailing List button.Look in the Materials repository for workshops, presentations, papers, and Web pages developedand written by the ITSO technical professionals; click the Additional Materials button. Employees mayaccess MyNews at http://w3.ibm.com/ for redbook, residency, and workshop announcements.

IBM Intranet for Employees


mailto: [email protected]

http://www.elink.ibmlink.ibm.com/pbl/pbl


http://w3.itso.ibm.com/

http://w3.ibm.com/










IBM Redbooks fax order form

Please send me the following:

We accept American Express, Diners, Eurocard, Master Card, and Visa. Payment by credit card notavailable in all countries. Signature mandatory for credit card payment.

Title Order Number Quantity

First name Last name

Company

Address

City Postal code

Telephone number Telefax number VAT number

Invoice to customer number

Country

Credit card number

Credit card expiration date SignatureCard issued to


Abbreviations and acronyms

ACC AutoPack ControlCenter

ACF Adapter ConfigurationFacility

ADE ApplicationDevelopment Files

ADSM ADSTAR DistributedStorage Manager

API ApplicationProgramming Interface

ARS Action Request System

CLI Command LineInterface

EIF Event IntegrationFacility

IBM International BusinessMachines Corporation

INV Tivoli Inventory

ITSO International TechnicalSupport Organization

LAN Local Area Network

MDist Multiplexed Distributionservices

MN Managed Node

OS Operating System

RDBMS Relational DatabaseManagement System

RIM RDBMS InterfaceModule

SQL Structured QueryLanguage

SWD Tivoli SoftwareDistribution

TCP/IP TransmissionProtocol/InternetProtocol

© Copyright IBM Corp. 2000

TDM Tivoli DistributedMonitoring

TDP Tivoli Data Protectionfor Applications

TEC Tivoli EnterpriseConsole

TMA Tivoli ManagementAgent (Endpoint)

TMR Tivoli Managed Region

TRIP Tivoli RemoteExecution Service

TSD Tivoli Service Desk

WAN Wide Area Network

167

Index

Aaction synopsis 147activity log 116add filter 98administrator 88ADSM Web Administration 134ADSMInterface 135ADSMPlus for Tivoli module for TSM 3.7 12alarms 7alerts 7append source path 60application servers 115AS/400 alert adapter 88AS/400 Message adapter 89asset information from Tivoli Inventory 131asynchronous monitoring 8automated task 102Autopack 56Autopack Control Center 58available subscribers 65

BBRArchive 12BRBACKUP 12BRRestore 12business continuance 119

Ccentralized point of integration and control 7change mode 60client action 155command line interface, alternative to desktop 5command routing 121communications methods 6communications services 4complex logical structures 11components of Tivoli Plus module 111compound rule 144compression on distribution 60configuration manager 124configuration repository 70configuring and managing TSM servers 123create rules manually 151creating packages with Autopack 60

© Copyright IBM Corp. 2000

Ddata collection for statistical analysis 5database files

excluding from normal backup 118database servers 15database servers in a distributed environment 13defining policy domains 124deleting rule sets 108determining if your application is down 116differential backups 8dispatch engine 87Distributed Monitoring 149distributing packages 64distribution profile 59DMTF 71Domino databases, document level backup 11dsm.opt 64dsm.sys 64duplicate messages 7

EEdit Filters 98Edit Rules 144Endpoint 67, 112Endpoint Gateway 58, 59enhanced TEC event forwarding 116Enterprise Console Events 103Enterprise event logging 125, 126Enterprise logon 121, 125enterprise-wide events 85event 15event adapters 15, 88event becoming critical 150event class 149, 156event console 15, 86, 88, 100event console administrator 153event forwarding to Tivoli Storage Manager 116event group 15

assigning 99display 100for Tivoli Storage Manager 96

event recording by TEC 143event server 13, 86, 150

for central logging 120Rule Bases 144

event slot values 152event sources 99

169

event triggered backup, response 116events

multiple Tivoli Storage Manager servers to TEC16Tivoli Data Protection for Applications to TEC16Tivoli Storage Manager to TEC 16

EVGEN command 130, 144Exchange Application Client 8Exchange Server Tasks task library 154, 156extending the log 151extending Tivoli Storage Manager recovery log 151

example 149extension of the recovery log 153

Ffile package 6, 58, 65

properties 60filter values 98filtered event source 86format files 89Framework, Tivoli Inventory 69frequency of monitoring probe 150

Ggeneric query 80geographically-dispersed platforms 5graphical rule builder 151, 152

Hhardware queries 80hardware scan 77historical trending analysis 119

IIBM DB/2 8IBMBACKUP class 93ibmtsm.baroc 92ibmtsm.mac 92import bitmap option 97information about task library 152integration

between Tivoli Enterprise and Tivoli StorageManager 112scenarios 115Tivoli Inventory with Service Desk 133TME 10 with Tivoli Storage Manager 12

inventoryinformation 6INVENTORY_QUERIES 81profiles 73scan profile 73

Llab environment 17levels of availability 7Linux client 62loading the rule base 96log information options 60logfile event adapter 89logging events to Tivoli Event Console 128logical volumes 80Lotus Domino API 11

Mmanaged node 58, 70, 112, 116management by subscription 5Management Information Format (MIF) 71Manager for R/3 15, 16managing multiple servers 121managing TSM servers from any server 124master server definitions 123MDist mechanism 58menu entries

none for starting the Tivoli Storage Manager cli-ent 132none for the integration of Tivoli Inventory 132

message time limits 100messages 7Microsoft Cluster Server (MSCS) 10Microsoft Exchange 5.5 server 153Microsoft Exchange Directory 8Microsoft SQL server 13

Service Desk 137migrating assets from Tivoli Inventory 137monitoring capabilities 119monitoring manual checks centrally by TEC 130MS Exchange 8MS SQL 83multiplexed distribution 6

Nnested file packages 56, 60Netview for OS/390 adapter 89


Netview maps 100NetView/6000 adapter 89network cards 80

Ooffline backup of the Exchange server 153online backup and restore of Microsoft SQL 9OpenView adapter 89Oracle Backup Agent 10Oracle7 10Oracle8 10

Ppackage distribution 57platform specific options 118Plus Module for ADSM 149posting a message to the activity log 149problem management 143problem records, triggered by TEC events 131profile manager 58, 112

ADSM Servers 113profile paradigm 6putting it all together 141

Qquerying the activity log 130

RR/3 application servers 16RDBMS 69, 87reception engine 87recovery log files 153registry changes, autopack 56relation list 146remote systems management 5repeater hierarchy 6responding to incoming problem records 139RIM 69RMAN 10rule bases 91Rule Sets

deleting 108Edit Ruleset 144

SSAP R/3 15

and Tivoli Storage Manager 12

SAPDBA 12scanning TMA Endpoints 71send_event task 155server console 116server definitions 121server reception 87server-to-server communication 121set class value 98severity, setting 147

of TEC events 106simple rule 144slave server 121

definitions 122SNMP adapter 89software distribution

process 57profile 118

Software Distribution Gateway 59software levels 83software scan 77software signature 81

file 71source host 58, 118Spectrum Enterprise Manager adapter 89SQL application client 10SQL server data 9status messages from Tivoli Storage Manager serv-er 139storing data on another server 124subscription lists 112

Tivoli Plus 111Sun Solstice/SunNet Manager adapter 89synchronous monitoring 7system environment used in our lab 17system management 13

services 4

TT/EC Tasks task library 155Tandem NonStop Kernel adapter 89targets for software distribution 58TEC

console 149event class definition file 144event server 92preparation for Tivoli Storage Manager 93rule language 91rules 15

171

server 89, 91testing event logging 130time window for Exchange stop 155Tivoli 8, 12, 14Tivoli Adapter Configuration Facility 86Tivoli Asset Management 17Tivoli Change Management 17Tivoli Data Protection 8, 83

for Lotus Domino 10for Microsoft Exchange Server 8for Microsoft SQL Server 9for Oracle 10for SAP R/3 12MS Exchange 117

Tivoli Data Protection for Applications 8, 115deploying 117modules 3overview 115

Tivoli Decision Support, data input to 13Tivoli desktop 5Tivoli Disaster Recovery Manager 119Tivoli Distributed Monitoring 7, 149

description 5features 5

Tivoli Endpoints 18Tivoli Enterprise 83

features of Tivoli Storage Manager 119Framework modules 4

Tivoli Enterprise Consolecomponents 85using to monitor all the servers 125

Tivoli Enterprise Console (TEC) 6, 13, 85adapters 86

Tivoli Event Console (TEC) 15Tivoli Event Integration Facility 86Tivoli event receiver 116Tivoli Framework 3Tivoli Framework scheduler 65Tivoli Framework TME 10 21Tivoli Inventory 6

collection engine 70concepts 69database interface and query facility 70installation 70migration utility 138scan 71

Tivoli Management Agent 59Tivoli Management products, overview 3Tivoli Management Region (TMR) 15

Tivoli Managerfor Lotus Domino 15for MS SQL 13for Oracle 14for SAP R/3 15

Tivoli Manager for MS Exchange 12, 153Tivoli Manager for Oracle

Distributed Monitoring 14Framework 14User Management 15

Tivoli Manager for R/3 15Tivoli Plus module

components 111for ADSM 111, 151setting up 112

Tivoli Problem Management 16Tivoli Service Desk 3, 16, 131, 143

customizing 132enhancements 131user profile 133

Tivoli Software Distribution 143description 6server 59using 117

Tivoli Storage Manageractivity log message 149administrative Web client 136backup-archive client for Linux 62enterprise 119event handling 16log 149messages 93updating the backup-archive client 143

Tivoli Storage Manager and Tivoli Enterpriseexamples 143

TMA Endpoint 58TME 10 Framework 13traps 7triggering level of distributed monitoring, controlling150TSDBuild application 137tsm_back_succ event class 156

Uunnecessary triggering of the backup 155

Vvirtual volumes 121


Wwfilesig 81Windows 89Windows NT adapter format file 156

173


IBM Redbooks review

Your feedback is valued by the Redbook authors. In particular we are interested in situations where aRedbook "made the difference" in a task or problem you encountered. Using one of the followingmethods, please review the Redbook, addressing value, subject matter, structure, depth andquality as appropriate.

• Use the online Contact us review redbook form found at ibm.com/redbooks• Fax this form to: USA International Access Code + 1 914 432 8264• Send your comments in an Internet note to [email protected]

Document NumberRedbook Title

SG24-6117-00Managing Storage Management: Tivoli Enterprise integration withTivoli Storage Manager

Review

What other subjects would youlike to see IBM Redbooksaddress?

Please rate your overallsatisfaction:

O Very Good O Good O Average O Poor

Please identify yourself asbelonging to one of thefollowing groups:

O Customer O Business Partner O Solution DeveloperO IBM, Lotus or Tivoli EmployeeO None of the above

Your email address:The data you provide here maybe used to provide you withinformation from IBM or ourbusiness partners about ourproducts, services or activities.

O Please do not use the information collected here for futuremarketing or promotional contacts or other communications beyondthe scope of this transaction.

Questions about IBM’s privacypolicy?

The following link explains how we protect your personal information.ibm.com/privacy/yourprivacy/




http://www.ibm.com/privacy/yourprivacy/


http://www.ibm.com/privacy/yourprivacy/

(0.2”spine)0.17”<->0.473”

90<->249 pages

Managing Storage M

anagement

®

SG24-6117-00 ISBN 0738418218

INTERNATIONAL TECHNICALSUPPORTORGANIZATION

BUILDING TECHNICALINFORMATION BASED ONPRACTICAL EXPERIENCE

IBM Redbooks are developed by the IBM International Technical Support Organization. Experts from IBM, Customers and Partners from around the world create timely technical information based on realistic scenarios. Specific recommendations are provided to help you implement IT solutions more effectively in your environment.

For more information:ibm.com/redbooks

Managing Storage ManagementTivoli Enterprise integration with Tivoli Storage Manager

Centrally manage your distributed storage management environment

Automatically react to storage events

Benefit from practical, real-life examples

This IBM Redbook covers the new features of Tivoli Storage Manager, which relate to the Tivoli Enterprise set of products and show how these, in return, can contribute to a traditional installation of Tivoli Storage Manager.

This book is addressed to Tivoli Storage Manager administrators, who have little or no knowledge of Tivoli Enterprise. It does not cover the basic installation of the Tivoli Framework or its applications.

We focus on Tivoli Enterprise products, such as Framework, Distributed Monitoring, Inventory, Software Distribution and Enterprise Console. We show how these modules can be used to ease daily tasks, to monitor conditions, and to report them accordingly. Additionally, we explain how to customize Tivoli Storage Manager to collaborate with the Tivoli Enterprise modules.

This book is divided into three parts. Part 1 contains an introduction to the different Tivoli Enterprise modules and special features of Tivoli Storage Manager. Part 2 covers each of the modules in depth. Part 3 describes a complete scenario, where all of the modules come together, therefore providing a holistic approach to an enterprise management system, including storage.




managing storage management tivoli enterprise integration with tivoli storage manager sg246117

Technology

components of tivoli

tivoli modules

tivoli storagemanagercentrally

tivoli storage management

tivoli enterprise console

tivoli enterprise modules

tivoli inventory components

tivoli inventory installation