Managing storage management tivoli enterprise integration with tivoli storage manager sg246117

Managing Storage
Management
Tivoli Enterprise integration with Tivoli Storage
Manager
Centrally manage your distributed
storage management environment

Automatically react to
storage events

Benefit from practical,
real-life examples

Patrick Randall
Michel Baus
Andrej Marencic
Melinda Sangargir

ibm.com/redbooks

SG24-6117-00

International Technical Support Organization

Managing Storage Management
Tivoli Enterprise integration with
Tivoli Storage Manager

October 2000

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

First Edition (October 2000)

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

Comments may be addressed to:
IBM Corporation, International Technical Support Organization
Dept. QXXE Building 80-E2
650 Harry Road
San Jose, California 95120-6099

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

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

Contents

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

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xi
The team that wrote this redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Comments welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

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

Chapter 1. Introduction to Tivoli Management products . . . . . .. . . . . .3
1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .3
1.2 Parts and pieces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .4
1.2.1 Tivoli Enterprise modules . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .4
1.2.2 Tivoli Data Protection for Applications . . . . . . . . . . . . . . .. . . . . .8
1.2.3 Other Tivoli modules for managing applications . . . . . . . .. . . . . 12
1.2.4 Tivoli Storage Manager event handling . . . . . . . . . . . . . . .. . . . . 16
1.2.5 Tivoli Service Desk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 16
1.3 System environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 17

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

Chapter 2. Tivoli Framework TME 10 . . . . .. . . . . .. . . . .. . . . . .. . . . . 21
2.1 Framework architecture . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 21
2.2 Framework desktop . . . . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 22
2.2.1 Desktop window . . . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 23
2.3 Framework components . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 24
2.3.1 Tivoli Management Region . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 25
2.3.2 Policy regions . . . . . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 25
2.3.3 TME administrators . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 25
2.3.4 Profile managers . . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 26
2.3.5 Task libraries . . . . . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 27
2.3.6 Scheduler . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 27
2.3.7 Notice groups . . . . . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 27
2.4 Framework configuration: examples . . . .. . . . . .. . . . .. . . . . .. . . . . 28
2.4.1 Defining administrators . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 28
2.4.2 Creating tasks and jobs . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 33
2.5 Hints and tips . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 39

Chapter 3. Tivoli Distributed Monitoring . . . . . . . . . . . . . . . . . . . . . . . . 41
3.1 Tivoli Distributed Monitoring concepts . . . . . . . . . . . . . . . . . . . . . . . . 41
3.1.1 Tivoli Distributed Monitoring components . . . . . . . . . . . . . . . . . . 42

© Copyright IBM Corp. 2000 iii

3.1.2 Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.2 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.2.1 Monitoring the status of the dsmserv daemon. . . . . . . . . . . . . . . 47
3.2.2 Custom script monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.3 Hints and tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Chapter 4. Tivoli Software Distribution . . .. . . . . .. . . . .. . . . . .. . . . . 55
4.1 Overview of Tivoli Software Distribution .. . . . . .. . . . .. . . . . .. . . . . 55
4.1.1 Source host . . . . . . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 55
4.1.2 Target. . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 56
4.1.3 Repeaters. . . . . . . . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 56
4.1.4 File package . . . . . . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 56
4.1.5 Autopack . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 56
4.2 Installation . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 57
4.3 Setting the environment . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 59
4.3.1 Profiles . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 59
4.3.2 Creating packages . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 60
4.3.3 Distributing packages . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 64
4.4 Hints and tips . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . . 67

Chapter 5. Tivoli Inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
5.1 Tivoli Inventory concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
5.1.1 Tivoli Inventory components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
5.1.2 Tivoli Inventory installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
5.1.3 Tivoli Inventory scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
5.2 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.2.1 Inventory profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.2.2 Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
5.3 Hints and tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Chapter 6. Tivoli Enterprise Console . . . . . . . . . . . . . . .. . . . . .. . . . . 85
6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . . 85
6.2 Overview of the Tivoli Enterprise Console . . . . . . . . . .. . . . . .. . . . . 86
6.2.1 Event adapters . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . . 88
6.2.2 Event classes . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . . 90
6.2.3 Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . . 90
6.2.4 Handling of the messages . . . . . . . . . . . . . . . . . .. . . . . .. . . . . 91
6.3 How to prepare TEC for Tivoli Storage Manager . . . . .. . . . . .. . . . . 93
6.3.1 Importing files for Tivoli Storage Manager. . . . . . .. . . . . .. . . . . 93
6.3.2 Creating event group for Tivoli Storage Manager .. . . . . .. . . . . 96
6.3.3 Display setting of the event console . . . . . . . . . . .. . . . . .. . . . 100
6.3.4 Creating an automated task . . . . . . . . . . . . . . . . .. . . . . .. . . . 102
6.3.5 Setting the severity of TEC events . . . . . . . . . . . .. . . . . .. . . . 106
6.3.6 Deleting rule sets . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . 108

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

Chapter 7. Tivoli Plus Module for ADSM . .. . . . . .. . . . .. . . . . .. . . . 111
7.1 Components of Tivoli Plus Module . . . . .. . . . . .. . . . .. . . . . .. . . . 111
7.2 How it works . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . 112
7.3 Setting up the Tivoli Plus Module . . . . . .. . . . . .. . . . .. . . . . .. . . . 112
7.4 Hints and tips . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . .. . . . . .. . . . 114

Chapter 8. Tivoli Data Protection for Applications . . . . .. . . . . .. . . . 115
8.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . 115
8.2 Event forwarding to Tivoli Storage Manager . . . . . . . . .. . . . . .. . . . 116
8.3 Using tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . 116
8.4 Using Tivoli Software Distribution . . . . . . . . . . . . . . . . .. . . . . .. . . . 117
8.5 Hints and tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . 118

Chapter 9. Tivoli Enterprise features of Tivoli Storage Manager . . . . 119
9.1 Tivoli Storage Manager enterprise features . . . . . . . . . . . . . . . . . . . 119
9.1.1 How to set up server-to-server communication . . . . . . . . . . . . . 121
9.1.2 Configuring and managing the servers . . . . . . . . . . . . . . . . . . . 123
9.1.3 Storing data on another server . . . . . . . . . . . . . . . . . . . . . . . . . 124
9.1.4 Managing servers from any server . . . . . . . . . . . . . . . . . . . . . . 124
9.1.5 Central monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
9.2 Predefined items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
9.3 Example of event logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
9.4 Hints and tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Chapter 10. Tivoli Service Desk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
10.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
10.2 Customizing Tivoli Service Desk. . . . . . . . . . . . . . . . . . . . . . . . . . . 132
10.2.1 Editing a Tivoli Service Desk user profile . . . . . . . . . . . . . . . . 133
10.2.2 Starting the Tivoli Storage Manager administrative client . . . . 136
10.2.3 Migrating assets from Tivoli Inventory. . . . . . . . . . . . . . . . . . . 137
10.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 143
11.1 Updating the Tivoli Storage Manager backup-archive client . .. . . . 143
11.2 Extending the Tivoli Storage Manager recovery log . . . . . . . .. . . . 149
11.3 Offline backup of the Exchange server . . . . . . . . . . . . . . . . . .. . . . 153

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

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

v

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

How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
IBM 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 . . . 4
2. Tivoli Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3. Tivoli desktop — example of window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4. Desktop Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5. Create Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6. Create Administrator, Set TMR Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7. Create Administrator, Set Login Names . . . . . . . . . . . . . . . . . . . . . . . . . . 30
8. Create Administrator, Set Resource Roles . . . . . . . . . . . . . . . . . . . . . . . . 31
9. Create Administrator, Set Notice Groups. . . . . . . . . . . . . . . . . . . . . . . . . . 32
10. Create Administrator, administrator desktop . . . . . . . . . . . . . . . . . . . . . . . 32
11. Task Library, acme_task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
12. Create Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
13. Task Library, acme_task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
14. Create Job menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
15. Schedule a job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
16. Schedule a job, Set Retry/Cancel/Restriction . . . . . . . . . . . . . . . . . . . . . . 39
17. Tivoli Distributed Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
18. Interaction between Tivoli Distributed Monitoring and the TMR server . . . 43
19. Profile to monitor Tivoli Storage Manager and subscribed Endpoint . . . . . 45
20. Monitors inside Distributed Monitoring profile . . . . . . . . . . . . . . . . . . . . . . 46
21. Monitor daemon status of Tivoli Storage Manager . . . . . . . . . . . . . . . . . . 48
22. User and group ID to execute the monitors . . . . . . . . . . . . . . . . . . . . . . . . 50
23. Universal numeric monitor with custom script . . . . . . . . . . . . . . . . . . . . . . 52
24. Distributing a custom script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
25. Tivoli Software Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
26. Tivoli Software Distribution process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
27. Create Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
28. Autopack main menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
29. Scanning the system with Autopack Control Center . . . . . . . . . . . . . . . . . 61
30. Build Autopack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
31. File Package Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
32. Unix After Distribution Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
33. Distribute File Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
34. Tivoli Inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
35. Tivoli Inventory architecture when scanning Endpoints . . . . . . . . . . . . . . . 72
36. Profile manager with inventory profiles and subscribers . . . . . . . . . . . . . . 74
37. Inventory profile manager and query libraries . . . . . . . . . . . . . . . . . . . . . . 75
38. Inventory scan for hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
39. Inventory scan for software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
40. Storing configuration files as ASCII through inventory profile . . . . . . . . . . 79

© Copyright IBM Corp. 2000 vii

41. Sample hardware query. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
42. Custom query TSM clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
43. Query results of custom TSM client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
44. Tivoli Enterprise Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
45. Tivoli Enterprise Console event flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
46. Components of the TEC Event Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
47. TEC Adapter profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
48. Rule Bases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
49. Tivoli Storage Manager message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
50. Translating Tivoli Storage Manager messages into TEC Events. . . . . . . . 93
51. Rule Base Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
52. Copy Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
53. Import Into Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
54. Compile Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
55. Load Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
56. Event Group Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
57. New Event Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
58. Edit Event Group Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
59. Assign Event Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
60. Event Groups display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
61. Sort Event Group Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
62. Tivoli Enterprise Console Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
63. Select Event Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
64. Summary of the Automated Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
65. Setup Automatic Task Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
66. Automated Task Execution Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
67. Tivoli Plus Module for Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . 111
68. ADSMPlus for Tivoli menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
69. Set ADSM Home menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
70. Tivoli Data Protection for Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
71. Tivoli Data Protection for MS Exchange . . . . . . . . . . . . . . . . . . . . . . . . . 117
72. Tivoli Storage Manager event forwarding . . . . . . . . . . . . . . . . . . . . . . . . 120
73. Server-to-server communication, enterprise administration . . . . . . . . . . 122
74. Server-to-server event logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
75. Event logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
76. Tivoli Service Desk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
77. Tivoli Service Desk main window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
78. Configuration of a user profile in Tivoli Service Desk . . . . . . . . . . . . . . . 133
79. Action groups in Tivoli Service Desk . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
80. System actions in Tivoli Service Desk . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
81. Launching administrative client from Tivoli Service Desk . . . . . . . . . . . . 136
82. Tivoli Storage Manager Web administrative client. . . . . . . . . . . . . . . . . . 136
83. 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 . . . . . . . . 138
85. Opening a call in Tivoli Service Desk. . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
86. Rule sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
87. New Simple Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
88. Condition in Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
89. Actions in Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
90. Extend log rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
91. Extend log arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
92. Compound Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
93. Stop_Services parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
94. 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, 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 redbook is addressed to Tivoli Storage Manager administrators, who
have little or no knowledge of Tivoli Enterprise. However, it does not cover the
basic installation of the Tivoli Framework or its applications. This is covered in
other books listed in Appendix B, “Related publications” on page 161.

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 these 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.

© Copyright IBM Corp. 2000 xi

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

Pat Randall is a Distributed Storage Software Specialist at the International
Technical Support Organization, San Jose, California. He has written eleven
redbooks on ADSM and Tivoli Storage Manager, teaches IBM classes
worldwide on all areas of distributed storage, and is a consultant in disaster
and business recovery. Before joining the ITSO in July 1996, Patrick worked
in IBM UK's Business Recovery Services as a Solutions Architect.

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

Andrej Marencic is an IT Specialist in Nibble Data Systems. He has four
years of experience in the Technical Support and Systems Management
fields, and he teaches IBM courses. His areas of expertise include Windows
NT and UNIX operating systems, Tivoli Storage Manager/ADSM, Tivoli
Framework, and Tivoli Enterprise Console.

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

Thanks to the following people for their invaluable contributions to the project:
Tetsuya Shirai
International Technical Support Organization, San Jose Center

Yvonne Lyon
International 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 your
comments about this or other Redbooks in one of the following ways:
• Fax the evaluation form found in “IBM Redbooks review” on page 175 to
the fax number shown on the form.
• Use the online evaluation form found at ibm.com/redbooks
• Send your comments in an Internet note to redbook@us.ibm.com

xiii

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 Tivoli
products 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 Tivoli
modules, which are used in the other parts of the book. We explain their basic
functions and their special features.

1.1 Overview
In Figure 1 you can see all the products which are mentioned in the book and
their logical connections to each other. In the upper left corner, there is the
Tivoli Framework underlaying most of the Tivoli modules except Tivoli Service
Desk. In the lower part there is the Tivoli Storage Manager suite with the
server itself and the different clients and special modules. On the right side
you can see some applications, which can be managed by Tivoli
Management modules and its storage managed by the Tivoli Data Protection
modules for Applications. By using all these products together, you will get a
closed cycle of events, management, and data flow.


Framework Tivoli
Manager for
Oracle

Tivoli Oracle
Distributed
Monitoring
Tivoli
Manager for
SQL
Tivoli
SQL
Inventory

Tivoli Tivoli Tivoli
RDBMS ADSM Manager for
Tivoli Interface Plus Exchange
Software Module Module
Distribution
Tivoli
Tivoli Manager for Exchange
Tivoli Service Domino
Enterprise Desk Plus
Console Module

Domino
Tivoli
Service
RDBMS Desk

Tivoli
Tivoli Tivoli Tivoli
Storage Admin
Backup
Data Data Data
Tivoli
Data
Server Archive
Protection for Protection for Protection for
Manager Client
Client
Oracle SQL Exchange
Protection for
Domino

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 the
Framework, the Tivoli Data Protection for Applications modules, other Tivoli
modules such as the ADSMPlus module for Tivoli Storage Manager and Tivoli
Manager for Applications, and some basics for event flow in Tivoli Storage
Manager itself and the Tivoli Service Desk.

1.2.1 Tivoli Enterprise modules
1.2.1.1 Tivoli Framework
The Tivoli Framework provides the basic system management services, such
as communications, presentation, and security, that most of the Tivoli


Management applications use, thus, ensuring consistency and integration. At
its core, the Tivoli Framework provides the facilities to transfer files and
execute commands on remote systems with built-in security and authorization
roles. The Tivoli Management applications can use these core facilities to
implement management functions, such as software distribution, resource
monitoring, and system configuration.

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

1.2.1.2 Tivoli Distributed Monitoring
Tivoli Distributed Monitoring is an application that allows you to monitor the
status of a wide range of geographically-dispersed platforms from different
vendors running different operating systems, including resources that are not
part of your Tivoli Environment.

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

Tivoli Distributed Monitoring provides your network computing environment
with 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 Distribution
Tivoli Software Distribution provides facilities for the distribution and
installation of software to managed systems in a Tivoli environment. Tivoli
Software Distribution uses the facilities provided by the Tivoli Management
Framework to distribute file packages in an efficient manner. Administrators
use the profile paradigm used by most other Tivoli applications to define file
packages to be distributed. These file packages can include any files
(executable programs, data files, and so on) and scripts that will be executed
before and after the distribution for a proper installation of the files on the
target 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 to
define nodes as repeaters so that they become fan-out points for the
distribution. By defining an appropriate repeater hierarchy for your network
environment, large file packages will only be moved once across slower links,
but will still reach multiple target systems.

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

Tivoli Inventory has three major advantages:
• It is based on the Tivoli Management Framework and therefore can be
tightly and automatically integrated with other Tivoli applications.
• It stores inventory information in a Relational Database Management
System (RDBMS) and therefore allows any non-Tivoli applications that
can access SQL data to share the inventory information. Moreover, it
benefits from the advanced features of an RDBMS system, such as
scalability and performance.
• Tivoli Inventory has close links with other applications, such as Tivoli
Software distribution and Tivoli Service Desk.

1.2.1.5 Tivoli Enterprise Console
For many companies, the computing enterprise is becoming more
heterogeneous in nature. It is supporting a wider variety of operating system
platforms, communications methods, and a diverse set of applications and
databases. 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 to
manage and control, and it is getting more difficult to attain acceptable levels
of availability. Availability or the lack of availability of the computing resources
may be directly related to the bottom line of a company as well as to its
competitiveness within the industry.

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

To issue these problems, Tivoli Enterprise Console (TEC) provides a
centralized point of integration and control for enterprise client/server
environments. It allows administrators to monitor information about the
environments 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 helps
detect potential problems before they cause outages. When problems are
detected, TEC may be configured to take action and intervene as defined by
the customer.

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

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

The scope of events which TEC can monitor is broader. However, most
environments 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 be
forwarded to TEC for further analysis.

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

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

1.2.2.1 Tivoli Data Protection for MS Exchange
Tivoli Data Protection for Microsoft Exchange Server is an application that
allows you to perform online backups of Microsoft Exchange Server
databases to Tivoli Storage Manager storage. Tivoli Data Protection for
Microsoft Exchange Server is referred to as the Exchange Application Client
in this document. The Exchange Application Client helps protect and manage
Exchange Server data by making it easy to do the following actions:
• Perform full, copy, differential, and incremental backups of the Microsoft
Exchange Directory and Information Store databases.
• Restore a full Directory or Information Store database and any number of
associated transaction logs.
• Delete a Directory or Information Store database backup from TSM
storage.
• Back up the Exchange Server databases to any TSM server with
drag-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 a
Microsoft Cluster Server (MSCS) environment.
• Set up seamless failover for scheduled backups in an MSCS environment.
The Exchange Application Client communicates with Tivoli Storage
Manager using its application program interface (API) and with an
Exchange Server using the Exchange API.

The Exchange Application Client must be installed on the same machine as
the Exchange Server. However, the Exchange Application Client must be able
to connect to a TSM server which can run on any supported operating
system. The Exchange Application Client can compress Exchange data
before sending it to the TSM server. The Exchange Application Client also
runs in a Microsoft Cluster Server environment.

1.2.2.2 Tivoli Data Protection for MS SQL
Tivoli Data Protection for Microsoft SQL Server (referred to as the SQL
Application Client) is an application that allows you to perform online backups
and restores of Microsoft SQL databases to Tivoli Storage Manager storage.
The SQL Application Client helps you protect and manage SQL Server data
by making it easy to:
• Perform full database and transaction log (incremental) backups.
• Perform a restore of a full database and any number of associated
transaction logs.
• Delete an SQL database backup from Tivoli Storage Manager storage.
• Back up any SQL database to any Tivoli Storage Manager server with
drag-and-drop ease.
• Set TSM connection information options to Tivoli Storage Manager
servers.
• 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 system
applications.
• Automate scheduled backups.


• Automate deletion of old backups.
• Back up and restore a Microsoft SQL Server running in a Microsoft Cluster
Server (MSCS) environment.
• Set up seamless failover for scheduled backups in an MSCS environment.

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

The SQL Application Client must be installed on the same machine as the
SQL Server, not the Tivoli Storage Manager server. However, the SQL
Application 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 Cluster
Server environment.

1.2.2.3 Tivoli Data Protection for Oracle
The 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) and
restore (online and offline) of Oracle databases. After the Oracle7 EBU or
Oracle8 RMAN initiates a backup or restore, the Oracle Backup Agent acts as
the interface to Tivoli Storage Manager. The Tivoli Storage Manager server
then applies its storage management functions to the data, which can be
done while users are working, with minimal disruption. The Oracle Backup
Agent can work with any Version 3 ADSM or Version 3.7 Tivoli Storage
Manager server. The Oracle Backup Agent translates the Oracle7 or Oracle8
API commands into Tivoli Storage Manager API calls.

1.2.2.4 Tivoli Data Protection for Lotus Domino
The Tivoli Data Protection module for Lotus Domino is a Lotus Domino
application that provides backup and restore of individual documents within a
Lotus Domino database, or an entire database with folders, documents,
forms, and views. Each Lotus Domino database can consist of two types of
notes:
• 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 a
single structured file, usually with a .NSF file extension. Domino databases
are complex logical structures that appear to traditional storage management
tools, such as the Tivoli Storage Manager Backup-Archive Client, as single
workstation files. It runs only at operating system level and will always back
up the entire database. Whenever a single document is updated within a
database, an incremental backup updates the entire database, because the
database modification timestamp has changed.

Most backup products can perform incremental backups of files, except
Domino. The Tivoli Data Protection module incrementally backs up Domino
databases on a document level to allow the administrator to retain a certain
number of backup versions for each document.

The Tivoli Data Protection module for Lotus Domino application uses the
Lotus Domino API to communicate with the Lotus Domino databases. The
Tivoli Data Protection module uses the Tivoli Storage Manager API to
communicate with the Tivoli Storage Manager server. The Tivoli Storage
Manager API is configured in a way similar to the standard backup-archive
client. It has its own dsm.opt client user options file, which contains standard
options such as node name, connectivity options, and include-exclude filter
lists. The syntax for the include-exclude list for the Lotus Domino is different
from the backup-archive client. It is highly recommended that you use a
unique node name for the Lotus Domino Agent. Then the Tivoli Storage
Manager server will view the application as a separate, self-contained
workstation client.

The Lotus Domino Agent helps you protect your Lotus Domino databases by
using the backup and recovery services of Tivoli Storage Manager. Functions
are available that enable you to:
• Incrementally back up only those portions of a database that have
changed since the last back up, such as new or changed documents,
forms, and views.
• Restore selected documents from a database (graphical user interface
only).
• 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 a
command-line interface.


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

1.2.3 Other Tivoli modules for managing applications
Tivoli provide modules for managing appliactions. We outline those currently
available below:

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

Note: ADSMPlus for Tivoli Version 3.7 will work only with Tivoli Storage
Manager (formerly known as ADSM) Version 3.7 and not with any earlier
versions of ADSM.

This integration allows centralized management of the Tivoli Storage
Manager application across a multi-platform network. This module provides
the 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 Exchange
Tivoli Manager for Exchange (Manager for Exchange) provides a centralized
system management tool for Microsoft Exchange servers on the Tivoli
platform. Manager for Exchange facilitates the management of Microsoft
Exchange Servers on endpoints and the installation of Microsoft Exchange
file 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 for
further 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 to
perform system management functions for Microsoft Exchange:
• Tasks to control and automate Microsoft Exchange administrative
activities on endpoints
• A selection of monitors for key performance and availability statistics for
Microsoft Exchange Servers
• Configuration files for the NT event adapter to receive, filter, and forward
selected events to the TEC
• Automated Microsoft Exchange client distribution
• Data input to Tivoli Decision Support

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

This product provides the ability to manage and monitor Microsoft SQL
Servers by providing extensions to TME 10 Framework, Distributed
Monitoring, Enterprise Console, and Global Enterprise Manager (GEM). It
includes the MSSQLManagerTasks library and the MSSQLServer and
MSSQLDatabase monitoring collections.

These tools enable you to manage distributed Microsoft SQL Server
computing 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 or
databases. Tivoli tasks work on multiple servers or databases in a single
action.

The tasks provided can:
• Ensure that optimal reading of data by monitoring and correcting
fragmentation.
• 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 for
global database server and database availability and performance
monitoring facilities. The monitors can be configured to respond
automatically to problems. They can run tasks to perform corrective
actions.
• Alert administrators to performance problems or serious errors and
failures. Monitors can notify administrators in a number of ways. They can
also send events to the Tivoli Enterprise Console (TEC).
• Integrate with the Tivoli Storage Manager backup tool to take advantage of
features such as secure backups and backup device management.
• Integrate with Tivoli GEM (Global Enterprise Manager) to allow
business-system views of managed servers and databases.

1.2.3.4 Tivoli Manager for Oracle
With Tivoli Manager for Oracle - Framework, you can manage the
tablespaces, datafiles, rollback segments, and redo logs in an Oracle
database, and manage sessions and instances associated with a database.
Tivoli Manager for Oracle - Framework enables you to use the other Tivoli
Manager for Oracle products to manage your Oracle environment. The
module 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 Domino
The Tivoli Manager for Domino (Manager for Domino) allows the Tivoli or
Domino system administrator to manage Lotus Domino within a Tivoli
Management Environment (TME). That is, you can manage Domino servers
from the same Tivoli Framework desktop where you control Tivoli
Management Regions (TMRs).
• Manager for Domino Monitor Collections offer a wide range of monitoring
options, including monitors for all statistics in the events4.nsf database
that return numeric values. Program status monitor check the state of
Domino add-in tasks.
• Manager for Domino makes use of Tivoli Software Distribution file
packages to customize and distribute Notes client software.
• Manager for Domino uses TEC rules and classes to filter and manage
Domino events. Using Event Server rule base functionality, you can modify
or extend Manager for Domino rule sets to meet your processing
requirements. You can also assign Domino events to an event group, and
then view these events on one or more Event Consoles.

1.2.3.6 Tivoli Manager for SAP R/3
A typical SAP R/3 environment includes one or more R/3 systems, where
each R/3 system consists of one database server and one or more
application servers. The R/3 application servers run on the UNIX and
Windows 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 installations
of 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 the
Tivoli Distributed Monitoring product. These monitors provide status on the
machines 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/3
represents each R/3 system and server as a Tivoli object. Each object is a
special type of Tivoli endpoint that enables the Manager for R/3 to distribute
monitors 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/3
systems that the TMR server manages.

Manager for R/3 provides two event adapters for R/3 application servers. The
event adapters are specific to each application server. You must configure
each event adapter for each application server. R/3 application servers are
the primary resources used in managing the R/3 system. The application
servers obtain most performance metrics. Manager for R/3 obtains
performance information about the R/3 database server through calls made
to one of the R/3 system's application servers. This allows the Manager for
R/3 to gather database information for all platforms, including DB2 on
OS/390.

1.2.4 Tivoli Storage Manager event handling
1.2.4.1 Events from Tivoli Storage Manager to TEC
In its current release, Tivoli Storage Manager supports the forwarding of
events to the Tivoli Enterprise Console (TEC). This happens in the same way
as other event receivers such as activity log or console. This includes the
standard messages originating from the Tivoli Storage Manager itself and its
clients.

1.2.4.2 Events from multiple Tivoli Storage Manager servers to TEC
By using the central event logging feature, which is included in the enterprise
features of Tivoli Storage Manager, you can use a central server to forward
the events originating from all Tivoli Storage Manager servers in your
organization.

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

1.2.5 Tivoli Service Desk
Service Desk is a help desk software solution whose primary goal is to
improve the efficiency and effectiveness of a corporate service and support
operation. It is a suite of three integrated applications:
• Tivoli Problem Management: This application, which is the core
application of Tivoli Service Desk, addresses help desk services related to
user requests for problem resolution.


• Tivoli Change Management: This application addresses the operational
changes associated with delivering IT services.
• Tivoli Asset Management: This application addresses issues surrounding
corporate 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 Tivoli
Storage 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 Data
Protection for different applications and Tivoli Storage Manager. We do not
cover the installation, and expect that the system is already installed and
running.

We give you a description of individual modules starting with product
architecture, concepts, definitions of components, how they work, and, at the
end, examples of how to set them up. These examples are based on our
environment and can be different from the system environment in your
organization.

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

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


Chapter 2. Tivoli Framework TME 10

In this chapter we give you a brief description of the Tivoli Management
Environment 10 (TME 10) Framework, which is the base component for the
TME 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 the
TME 10 applications installed on the Framework. See Figure 2.

Framework
Task Libraries
Query Libraries
RIM
RDBMS
Endpoint
interface Manager
module
Scheduler

communication
tasks
RDBMS

Managed Managed
Node Node

gateway

communication
tasks

End- End- End- End- End-
point point point point point

Figure 2. Tivoli Framework


Following are some examples of the services provided by the Framework:
• Task Library — A task library through which you can create tasks and
execute them on multiple TME 10 resources.
• Scheduler — A scheduler that enables the administrator to schedule all
TME 10 operations, such as execution of the tasks created in the TME 10
task library.
• Relational Database Management System (RDBMS) Interface Module
(RIM) — This enables some of the TME 10 applications to write
application specific information to a relational database.
• Query facility — This enables an administrator to search and retrieve
information from a relational database.

The introduction of the Gateway and the Endpoints enables a Tivoli
Enterprise installation to be three-tiered, as shown in Figure 2 on page 21.
Tivoli Management servers communicate with Managed Nodes. Managed
Nodes can host a Gateway to handle communication with Endpoints.
Gateway controls all the communications with and operations on Tivoli
Enterprise Endpoints. Using fewer Managed Nodes and more Endpoints
reduces 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 Tivoli
Management server database.
• There are fewer Managed Node databases to synchronize with the Tivoli
Management server database.

2.2 Framework desktop
The TME 10 desktop is the user interface that provides access to TME 10
features and components. The desktop provides a central control to manage
and organize the system management tasks of all modules. The desktop is
available for Microsoft Windows and for other platforms having the X11
environment or a graphical interface installed.

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


2.2.1 Desktop window
The desktop window is a graphical representation of TME 10 and provides
status information of modules, objects, and resources. Windows are used to
move or copy the resources. See Figure 3.

Figure 3. Tivoli desktop — example of window

2.2.1.1 Desktop Navigator
The Desktop Navigator provides filtering of the resources and keyword
search. By using Navigator, you can go directly to the resource you would like
to see without going through other intermediate resources. Navigator can be
accessed 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 Collections
A collection is a container that you can create and place on your desktop. A
collection can contain shortcuts that enable you to access resources. You can
populate 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 Framework
components. In addition, it guides you through examples of how to define
administrators, tasks, and jobs, as well as how to make a profile and
distribute 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 Region
A Tivoli Management Region (TMR) consists of a TME 10 server and a set of
TME clients that it serves. After base installation of Framework on a system,
that system becomes the TME server for the TMR. The TME server
installation process automatically allocates a unique 10-digit region number
that 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 is
installed. TME server can install a Managed Node remotely and add it to
the TMR. A Managed Node, which supports the majority of TME 10
management applications, occupies a disk space of 200-300 MB.
• Endpoints
The Endpoints can execute methods sent to them by the Gateway, where
they can then cache locally. Endpoints occupies a disk space of about
5 MB.

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

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

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


Each administrator ID is associated with certain administrator “roles”. Roles
define administrator levels of authority. The possible authorization roles for
administrator that may be defined are:
• Super — Authority to perform any operation.
• Senior — Authority to create TME 10 resources. The senior role is
required for configuration and policy tasks such as creating an
administrator or setting policy.
• Admin — Authority to manage and create system resources, such as
assign 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 policy
regions.
• Additional modules can define additional roles.

2.3.4 Profile managers
A profile manager is a container that links a collection of profiles to a set of
subscribers. Subscribers can be the following managed resources:
• Managed Nodes
• Endpoints
• Other profile managers

Profile managers are created within a policy region. Subscribers of these
profiles can be from same policy region or other policy regions. An example of
this situation could be Managed Nodes within a department or location which
are 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 Profiles
Profiles are collections of applications-specified information. A profile defines
the characteristics of the function to be performed.

For example, a software distribution defines the Courier file package
properties. This would typically include the files to be distributed, their source
locations, and any pre-distribution or post-distribution functions to be
performed on the target workstation.


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

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

2.3.5.2 Jobs
Jobs can be created in a task library (however, you must create a task before
you can create a job). A job is a task that is executed at specific managed
resources. The execution information you specify when you create a job
includes a list of task Endpoints on which the associated task will run and
where the output will be displayed. Jobs can be run at predefined times by
using the scheduler.

2.3.6 Scheduler
An administrator may need to schedule a job to begin in a specific time frame
some time in the future. The scheduler allows the administrator to schedule
previously 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 time
intervals.
• 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 groups
TME 10 management operations are logged and results are displayed as
“notices”. Notices are the response mechanism for the administrators to
monitor the status of management operations. Notices are sent to application
or operation-specific notice groups. Notice groups stores notices sorted by
function of modules. For example an administration notice group receives
notices 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 administrators
An existing administrator with a senior function role can define another
TME 10 administrator. Our example is performed by a TME administrator. You
can create a new administrator from the desktop or the command line. Here is
an example using desktop.
1. Select Create Administrator from administrator icon pop-up menu to
display 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 the
administrator. TMR roles are roles for the whole TMR. Resource roles are
roles for specific resources which are superseded by TMR. In the Set TMR
Roles dialog, it is possible to select admin, senior, user and other roles
from the available Roles list. The combination of these roles is sufficient
for the tasks an administrator can perform. To define an administrator, you


should at least have senior role; otherwise you cannot give someone else
the 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. See
Figure 6.

Figure 6. Create Administrator, Set TMR Roles

6. Click on the Set Logins... button to define the login names under which
the new administrator will be able to start the TME 10 desktop or issue
TME commands. The login name can be one of the following forms:
- username
- username@ManagedNode
- NTdomainusername
- NTdomainusername@ManagedNode
- Kerberos-name:realm

If you want more than one login name, repeat this step for each login that you
wish to add. See Figure 7. The user must exist on the Managed Nodes on
which you are going to run the desktop or issuing the commands. For more
information, 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 resource
roles for the administrator “melinda”. Again, there are different roles
available 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. See
Figure 8.


Figure 8. Create Administrator, Set Resource Roles

8. Click on the Set Notice Group... button to set the notice groups for this
administrator. 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 administrator
desktop is now ready to start. The final step of setting up the TME
administrator “melinda” is to add resources to its desktop. This is done by


dragging resource icons from an existing desktop and dropping them onto the
newly 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 library
A task library enables you to create tasks and jobs that can be run on one or
more managed resources in a network. You can create multiple task libraries
within each policy region.

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

Figure 11. Task Library, acme_task

2.4.2.2 Creating a task
Example of creating a task named df (this task will run the df command on
UNIX platform). See Figure 12.
1. Double-click on the icon of the task library. Select the Task... option from
the 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 the
task. Choose the platform on which you would like to run the task. If you
have a generic executable, for example, a shell script can be run on
multiple architectures.


Figure 12. Create Task

3. Then you choose the platform you want the task to run from the available
platform list. Framework displays the Executable for Task dialog for the
specified platform, in which you can enter the name of the managed node
that contains the executable for the chosen platform in the On Host text
field, and the path name in the Path to File text field — for example, “IBM
RS/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 role
required to start this task. For example, selecting admin will permit any
administrator with that authority to execute the task.
5. Under Execution Privileges, in the User Name field, insert the user ID
under which the task should run on the target node. The default value for
this field is ‘*’, which specifies that the task should run under the ID of the


Managing storage management tivoli enterprise integration with tivoli storage manager sg246117

Managing storage management tivoli enterprise integration with tivoli storage manager sg246117

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (19)

Similar a Managing storage management tivoli enterprise integration with tivoli storage manager sg246117

Similar a Managing storage management tivoli enterprise integration with tivoli storage manager sg246117 (20)

Más de Banking at Ho Chi Minh city

Más de Banking at Ho Chi Minh city (20)

Último

Último (20)

Managing storage management tivoli enterprise integration with tivoli storage manager sg246117