Managing Storage Management Tivoli Enterprise Integration With Tivoli Storage Manager Sg246117

7/31/2019 Managing Storage Management Tivoli Enterprise Integration With Tivoli Storage Manager Sg246117

1/196

ibm.com/redbooks

Managing Storage

ManagementTivoli Enterprise integration with Tivoli StorageManager

Patrick Randall

Michel Baus

Andrej Marencic

Melinda Sangargir

Centrally manage your distributed

storage management environment

Automatically react to

storage events

Benefit from practical,

real-life examples
http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/


2/196


3/196

Managing Storage Management

Tivoli Enterprise integration with

Tivoli Storage Manager

October 2000

SG24-6117-00

International Technical Support Organization


4/196

Copyr ight Inter national Busi ness Mach ines Cor poration 200 0. All righ ts 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 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.

Before using this information and the product it supports, be sure to read the general information in

Appendix A, Special notices on page 157.

Take Note!


5/196

Copyright IBM Corp. 2000 iii

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


6/196

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

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 886.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


7/196

v

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


8/196

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

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


9/196

Copyright IBM Corp. 2000 vii

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


10/196

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

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9250. 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10162. 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 . . . . . . . . . . 12274. 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


11/196

ix

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15393. Stop_Services parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

94. Send_Event task parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155


12/196

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


13/196

Copyright IBM Corp. 2000 xi

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 acomplete scenario where all of the modules come together, therefore

providing a holistic approach to an enterprise management system, including

storage.


14/196

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

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 disasterand 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

bachelors 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


15/196


16/196

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


17/196

Copyright IBM Corp. 2000 1

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.


18/196

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


19/196


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.


20/196


21/196

Chapter 1. Introduction to Tivoli Management products 5

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 Tivolidesktop 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


22/196


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 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 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 Inventoryaddresses 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 asscalability 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


23/196


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 statusinformation 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 monitoringsystem 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.


24/196


25/196


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 StorageManager 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 Ser ver. 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 backupsand 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 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 system

applications.

Automate scheduled backups.


26/196


27/196


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.


28/196


29/196


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.


30/196


31/196


32/196


33/196


34/196


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


35/196


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 M anager.


36/196



37/196


38/196


39/196


40/196


41/196


42/196


43/196


44/196


45/196


46/196


47/196


48/196


49/196

Chapter 2. Tivoli Framework TME 10 33

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 ormore 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 onUNIX platform). See Figure 12.

1. Double-click on the icon of the task library. Select the Task... option from

the task librarys 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.


50/196


51/196


52/196


53/196


54/196


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 Retry

option, you can specify that a job can retried if it is unable to start at the

scheduled time. With the Cancel option, you can specify that a job should

be cancelled if it does not start within a specified time period after its

scheduled stat time. With the Restriction option, you can restrict a job to

run during the day, at night, during the week or on weekends. See Figure

16.


55/196


56/196


57/196


58/196


59/196


60/196


61/196

Chapter 3. Tivoli Distributed Monitoring 45

The first thing to do is to create a Distributed Monitoring profile in a profile

manager. If you are using Endpoints, be sure to have dataless mode enabled

on the profile manager. Also verify that the Sentry Profile is among the

managed resources of your current policy region.

In our example we use just one profile which holds multiple monitors related

to Tivoli Storage Manager server on the AIX platform. We named the profile

dm_tsm_server_aix, as seen in Figure 19.

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


62/196


63/196


64/196


65/196


66/196


67/196

Chapter 3. Tivoli Distributed Monitoring 51

3.2.2 Custom script monitors

The next example we want to show involves reporting a certain condition via a

custom script and integrating it into a Tivoli Distributed Monitoring monitor.

3.2.2.1 Defining shell scripts

In this example, we used one of the sample scripts provided by Tivoli Storage

Manager. You can import these scripts to your Tivoli Storage Manager server

by running: dsmserv runfile /usr/tivoli/tsm/server/webimages/scripts.smp

This will provide you with some sample scripts which can be used to monitor

specific conditions inside your Tivoli Storage Manager.

The one we chose is q_scratch_stg, which gives back the percentage of

allowed 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 by

setting triggers to the response levels in Tivoli Distributed Monitoring.

The first step consists of writing a shell script which logs in to Tivoli Storage

Manager server using the batch mode of the administrative command-line

interpreter dsmadmc. For security reasons, it is suggested that you create an

unprivileged operator account in your Tivoli Storage Manager for thesemonitoring issues. The script then passes the command to run the script, and

the returned value is piped through some shell commands to get only the

desired numeric figure.

#!/bin/ksh

dsmadmc -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.sh

1.000

3.2.2.2 Using shell scripts in a monitor

Now, to import this script into Tivoli Distributed Monitoring, we add a new

monitor from the universal monitoring collection with the name Numeric

script. Then you have to provide the full path for the script you created. After

adding it, you should get a screen like the one shown in Figure 23.


68/196


69/196


70/196


71/196


72/196


73/196

Chapter 4. Tivoli Software Distribution 57

4.2 Installation

Using Tivoli Software Distribution, first you prepare the package to be

distributed; 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

6

3

4

63

5

7

4

33

4

8

Connection to Source

Host and transfer of data


74/196


75/196


76/196


77/196


78/196


79/196


80/196


81/196


82/196


83/196


84/196


85/196


86/196


87/196


88/196


89/196

Chapter 5. Tivoli Inventory 73

5.2 Examples

These examples are designed to stimulate your imagination they arent

intended 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 profiles

In 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 and

their subscribers. As with other modules, you have to set subscribers to the

profiles in order to distribute them to the target machines.

There is only one default Inventory scan profile, so upon creation, a default

one will appear. You then have to customize it to the designated function.

Inventory scans target machines in parallel, but writes the collected

information to the configuration repository serially ; so, it is important that

the network connectivity between the TMR, Inventory server, RIM host, and

the RDBMS is sufficient and configured for optimum operation. Also,

inventory does not save the information to the configuration repository until

all targets of the distribution are scanned.

Note


90/196


Figure 36. Profile manager with inventory profiles and subscribers

5.2.1.1 Hardware scan

To 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 profile

manager is in dataless mode, and that Inventory Profile is a managed

resource of your current policy region. See Figure 37.


91/196


92/196


93/196


When you are scanning only for hardware, then only the upper part of the

screen is important. Be sure that only hardware scan is selected, and that

the appropriate MIF files are created. For more about MIF files, see the Tivoli

Inventory Users Guide, GI10-8048.

Then save and close, and you can now distribute this inventory profile to the

target machines. It will scan for all hardware which is known to inventory. This

includes processors, memory, file systems, hard disks, BIOS information, and

so 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 scan

In order to create an inventory profile for scanning software, create another

profile called sw_scan and open it for customizing (Figure 39).

The execute on target should be software scan and read results to

Software MIF file. The save results in database section is for incremental

(update with differences) or replace all collected information. End user

access relates to Tivoli Userlink which we dont cover in this book. See the

Tivoli Inventory Users Guide, GI10-8048.

When you are not having separate inventory profiles for each platform, it is

recommended that you scan all files with all extensions. Thats because

executables in UNIX platforms dont need extensions, but on Windows

platforms, 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 for

each machine to perform, and your database will be quite busy. Although the

scans run parallel on all targets, the results are being written to the database

serially after all scans have finished. So no updates are visible as long as the

scan is running.


94/196


95/196


However, you can also save the contents of the dsm.opt/sys file and your

Tivoli Storage Managers recovery plan file. This is especially useful when

these files have been altered or deleted, since you cant access the Tivoli

Storage Manager server to restore them, if they dont exist. If you choose

Store as ASCII they will be copied to the database directory of your TMR

server ($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 the

distribution of the scanning profiles.


96/196


97/196


Processor, memory, paging space

Determine if compression should be on or not.

5.2.2.2 Software queries

For Tivoli Inventory to recognize which software products are installed on a

target (rather than just knowing which files are on), you have to provide

Software Signatures. They consist of stanzas for each Software product

which include a filename, its size, the name of the product and its version.

With this unique combination, Tivoli Inventory recognizes a software product

which then can be queried. For standard products, these signature files are

provided by Tivoli and are updated regularly. They can be downloaded from

the 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 Tivoli

Storage Manager administrators.

The command wfilesig is used to import software signatures into Tivoli

Inventory. 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 typing

man wfilesig or in the Tivoli Inventory Users Guide, GI10-8048.

This will make Tivoli Inventory recognize the Tivoli Storage Manager

Backup/Archive client version 3.7.2 on the Windows platforms. With this

information stored in the repository database, you can create a custom query

to list all the Tivoli Storage manager clients and versions on all client

machines. To create such a custom query, open a query library (for example,

INVENTORY_QUERIES). Create a query and change it, using the values in

Figure 42.


98/196


99/196


100/196


5.3 Hints and tips

If you are running multiple scans on multiple machines, make sure your

database log is big enough.

Queries over multiple views or tables can take a significantamount of time

and CPU to proceed.

If you have large fileservers, dont scan all files. Search only specific

directories.

If your company is developing software, create software signatures for

these products as well.

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


101/196

Copyright IBM Co rp. 2000 85

Chapter 6. Tivoli Enterprise Console

This chapter explains basic Tivoli Enterprise Console components and how to

set 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 as

operating systems, network management data, databases, or applications

events. In TEC, all these events from the IT environment are brought together

in one place, which offers the administrators a centralized and filtered view of

the enterprise-wide events. See Figure 44.

Figure 44. Tivoli Enterprise Console

End-

point

End-

point

End-

point

End-

point

End-

point

Tivoli

EnterpriseConsole

Tivoli

Storage

Manager

Managed

Node

gateway

send events

RDBMSinterface

module

RDBMS

Task

Libraries

actions

Framework


102/196


103/196


104/196


105/196


106/196


107/196


108/196


109/196


110/196


111/196


112/196


113/196

Chapter 6. Tivoli Enterprise Console 97

right click on the event server icon you select Event Groups. In Event Group

Management 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 and

select an icon. You can import new icons with Import Bitmap option. See

Figure 57.


114/196


Figure 57. New Event Group

After you created new event group, it does not contain any filters. Filters are

set 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 window

you select appropriate filters. For all events which are generated by Tivoli

Storage Manager you click Event Class button in Filter Values section and

from list of available event classes select I BMBACKUP. With Set Class Valueand Add Filter buttons you add this filter to event group. In case that you

want to add additional information to this event group, you can set additional

filters or if you want to distribute information on several event groups, then

you must replace this filter with subsided. For getting the events from only

selected nodes you type in or select appropriate node in origin section. See

Figure 58.


115/196


116/196


Figure 59. Assign Event Groups

In case that you need to change event group name or to delete it, we

recommend that you first unassign event group from all administrators.

6.3.3 Display setting of the event console

Administrators event console is used for displaying event to administrator andas tool for responding manually or automatically to the events. When you

open event console two windows with title TME 10 Enterprise Console are

automatically opened. One is for displaying the source groups. There are

options to display source groups in text mode and to sort source groups

vertically. Second one displays event groups. See Figure 60. In this window

you can choose:

Severity Display for setting text colors, background colors and icons or

different severities

Event Group Display for setting the event group icons and enable or

disable 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 keeping

open or closed messages. This dialog box enables option to view some

old events

Netview Connections to establish connection between TEC and Netview

server and Netview maps


117/196


118/196


119/196


120/196


121/196


122/196


123/196


124/196


125/196


126/196


127/196


128/196


129/196


130/196


131/196


132/196


133/196


134/196


135/196


136/196


137/196


138/196


139/196


140/196


141/196


142/196


143/196


144/196


145/196


146/196


When event receiver on server ACMESLAVE receives an event with event

number ANR1400, it checks it with event rules to see if this event is enabled

or not. The event ANR1400 will be routed to the master server. On the master

server Receiver Engine REC receives the event ANR1400 and forwards the

event to TEC, where it will be handled in order the rules set for each specific

event.

Testing event logging

You can test that the event logging is working as it should by issuing theEVGEN command.This command generates an event with the event number

specified by you. By querying the activity log, you can see if your event is

generated.

For example:

evgen 1400

q actlog

ANR2017I Administrator ADMIN issued command: EVGEN 1400

ANR1400W Mount request denied for volume - mount canceled.

9.4 Hints and tips

Most of the manual checks can be automated and monitored centrally by

TEC.

Make a list of events you find useful to monitor and enable these events for

event logging. For example, check if backup is missed, event number

ANR2578.


147/196


148/196


149/196


150/196


151/196


152/196


153/196


154/196


155/196


156/196


157/196


158/196


159/196


160/196


161/196


162/196


163/196


164/196


165/196


166/196


167/196


168/196


169/196

Chapter 11. Examples 153

Figure 92. Compound Rule

After successful creation of the recovery log files and extension of the

recovery log, you get two confirmation messages. The first one is for

successful creation of the log file, and the second one is for extend itself, so

you must create a similar rule for that situation too. With this last rule, you

close all events except information about the successful extend of the log with

harmless 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 the

database or groupware servers and then making a backup by file. In thisexample, you are going to use Microsoft Exchange 5.5 server, with Tivoli

Manager for MS Exchange. In this scenario, you first stop the Microsoft

Exchange server. When the server is stopped, you start the backup, and

when the backup is finished, you start the Exchange server.


170/196


171/196


172/196


173/196

Copyright IBM Co rp. 2000 157

Appendix A. Special notices

This publication is intended to help storage administrators to understand how

the features of Tivoli Enterprise can help them in their day-to-day activities

and responsibilities. The information in this publication is not intended as the

specification of any programming interfaces that are provided by Tivoli

Storage Manager or Tivoli Enterprise products. See the PUBLICATIONS

section of the IBM Programming Announcement for Tivoli products for more

information about what publications are considered to be product

documentation.

References in this publication to IBM products, programs or services do not

imply that IBM intends to make these available in all countries in which IBM

operates. Any reference to an IBM product, program, or service is not

Managing Storage Management Tivoli Enterprise Integration With Tivoli Storage Manager Sg246117

Documents

Transcript of Managing Storage Management Tivoli Enterprise Integration With Tivoli Storage Manager Sg246117