BMC ProactiveNet - Tivoli Storage Manager Storage · PDF fileConfiguring the TSM Server...

User Documentation November 2012

BMC ProactiveNet PerformanceManagement - Tivoli StorageManager MonitoringVersion 2.7.00

Table of Contents 2

Version 2.7.00

BMC ProactiveNet Performance Management - Tivoli Storage Manager Monitoring

Table of Contents...........................................................................................................................9User Goals and Features

...........................................................................................................................9Business Value

...........................................................................................................................10Requirements

...........................................................................................................................10System Requirements

...........................................................................................................................10Software Requirements

...........................................................................................................................11Security Requirements

...........................................................................................................................17Adding Central Monitoring Administration Tags

...........................................................................................................................19Preparing for Installation

...........................................................................................................................20Creating a Component Installation Package

...........................................................................................................................22Editing a Component Installation Package

...........................................................................................................................23Downloading and Installing an Installation Package

...........................................................................................................................25Configuring General Settings

...........................................................................................................................26Managing Policies

...........................................................................................................................27Configuring Monitor Settings

...........................................................................................................................29Configuring Tivoli Storage Manager KM

..................................................................................................................29Configuring the User Account

..................................................................................................................31Enabling the Debug Mode

..................................................................................................................35Configuring the Maximum Number of Instances

..................................................................................................................38Configuring the Multi-Node Monitoring Mode

..................................................................................................................43Configuring the TSM Server Discovery Overrides (Optional)

...........................................................................................................................46Filtering Elements to Monitor

...........................................................................................................................47Configuring Jobs

...........................................................................................................................48Configuring Mount Requests

...........................................................................................................................49Configuring Domains

...........................................................................................................................50Configuring Processes

...........................................................................................................................52Configuring Thresholds

...........................................................................................................................54Using BMC ProactiveNet Performance Management

...........................................................................................................................54Navigating the BMC ProactiveNet Operations Console

...........................................................................................................................57Adding attributes to the graph

...........................................................................................................................58Viewing and manipulating attribute graphs

...........................................................................................................................58Viewing monitors for a device

...........................................................................................................................59Changing thresholds

Table of Contents 3

Version 2.7.00


...........................................................................................................................59Managing Baselines and Key Performance Indicators

...........................................................................................................................63Tivoli Storage Manager KM

...........................................................................................................................64TSM Automated Drive

...........................................................................................................................64TSM Automated Library

...........................................................................................................................65TSM Client

...........................................................................................................................65TSM Daemon

...........................................................................................................................66TSM Database

...........................................................................................................................68TSM Domain

...........................................................................................................................69TSM Domain Client Node

...........................................................................................................................70TSM Jobs

...........................................................................................................................71TSM Job

...........................................................................................................................72TSM Log

...........................................................................................................................73TSM Manual Drive

...........................................................................................................................73TSM Mount Request

...........................................................................................................................74TSM Process

...........................................................................................................................74TSM Storage Pool

Support Information

5

Version 2.7.00


This section contains information about how to contact Customer Support and the levels of supportoffered for this and other releases.

If you have problems with or questions about a BMC product, or for the latest support policies, seethe Customer Support website at http://www.bmc.com/support. You can also access productdocuments and search the Knowledge Base for help with an issue at http://www.SentrySoftware.com. If you do not have access to the web and you are in the United States orCanada, contact Customer Support at 800 537 1813. Outside the United States or Canada, contactyour local BMC office or agent.

http://www.bmc.com/support

http://www.sentrysoftware.com

http://www.sentrysoftware.com

Legal Notices

7

Version 2.7.00


© Copyright 2011 BMC Software, Inc.

BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc.,are registered with the U.S. Patent and Trademark Office, and may be registered or pendingregistration in other countries. All other BMC trademarks, service marks, and logos may be registeredor pending registration in the U.S. or in other countries. All other trademarks or registeredtrademarks are the property of their respective owners.

Linux is the registered trademark of Linus Torvalds.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may betrademarks of their respective owners.

UNIX is the registered trademark of The Open Group in the US and other countries.

The information included in this documentation is the proprietary and confidential information of BMCSoftware, Inc., its affiliates, or licensors. Your use of this information is subject to the terms andconditions of the applicable End User License agreement for the product and to the proprietary andrestricted rights notices included in the product documentation.

BMC Softw are Inc.2101 CityW est Blvd, Houston TX 77042-2827, USA713 918 8800Customer Support: 800 537 1813 (United States and Canada) or contact your local support center

Key Concepts

9

Version 2.7.00


The pages in this section provide a high-level overview of the product.

User Goals and Features

Business Value

Requirements

Note that for convenience and brevity, reference to BMC ProactiveNet Performance Management - Tivoli StorageManager Monitoring, may also be made as Tivoli Storage Manager KM.

User Goals and Features

Tivoli Storage Manager KM enables you to monitor the following in your environment:

Jobs: size, duration, throughput, time elapsed since last backup, number of objects and status

Server and Storage Agent availability: status memory and CPU time consumption

Internal server processes: monitoring of database backups, data migration and spacereclamations

Server database and recovery logs: database and file system utilization, cache and bufferperformance, time elapsed since last backup and database reorganization, etc.

Storage pools: space utilization, status, capacity, logical occupancy, growth rates, etc.

Libraries and drives: number of available drives, status, and number of scratch volumesloaded, etc.

Client: working status

Business Value

BMC ProactiveNet Performance Management - Tivoli Storage Manager Monitoring provides currentand historical information through a centralized console so you can easily view and manage yourentire Tivoli Storage Manager environment. The product collects and brings critical performance dataand useful metrics into the BMC ProactiveNet Performance Management environment and enablesSAN Administrators to be warned whenever a problem occurs in their Tivoli Storage Managerenvironment.

The BMC ProactiveNet Performance Management - Tivoli Storage Manager Monitoring:

Detects backup and restore errors

Ensures maximum data protection and maximum availability

Measures jobs progress

Helps diagnosing server problems

Analyzes trend

Detects disk or tapes space shortages

Ensures backups are successful

Helps identify bottlenecks and optimize backup domains.

10Requirements

Version 2.7.00


Requirements

Before installing the Tivoli Storage Manager KM, verify the:

software requirements

system requirements

security requirements.

System Requirements

Operating System Operating System Version

Sun® microsystems SolarisTM 8, 9, 10

HP-UX 11.00, 11.11, 11iv2, 11iv3

IBM® AIXTM 5.1, 5.2, 5.3, 6.1

Red Hat® Linux® 7.2

Microsoft® Windows® 2003, 2008, 2008 R2

If the operating system is upgraded (or downgraded) at a later date, you will need to reload commands for the TivoliStorage Manager KM.

Software Requirements

The Tivoli Storage Manager KM supports the following platforms:

Software Version

Tivoli Storage Manager Server 5.1.x, 5.2.x, 5.3.x, 5.4.x, 5.5.x, 6.1.x, 6.2.x, 6.3.x

Tivoli® Storage Manager Administrative Client 5.1.x, 5.2.x, 5.3.x, 5.4.x, 5.5.x, 6.1.x, 6.2.x, 6.3.x

If you're running the Tivoli Storage Manager KM on LINUX, or Microsoft Windows x64 managednodes, please verify these additional software requirements:

11Requirements

Version 2.7.00


Purpose Software Version

When running Tivoli Storage ManagerKM on Linux managed nodes

Korn shell binary (/bin/ksh) Any

When running Tivoli Storage ManagerKM on Microsoft Windows x64managed nodes

Reg.exe patch KB948698 (http://support.microsoft.com/kb/948698)

Any

The Microsoft Windows x64 Reg.exe patch, KB948698 is required to allow access to 64-bit registry keys from PATROLAgent. Access the above patch site from the managed node to obtain the correct patch for that platform.

Security RequirementsA user account with administrative privileges must be configured in BMC PATROL to read andexecute Tivoli Storage Manager application programs and access file systems. Depending on theoperating systems used, several options will be available.

The following user accounts can be used:

On Unix platforms:

a root user

a non-root user, such as patrol, that has sudo privileges on Tivoli Storage Manager to executeapplication programs and access file systems

a non-root account, such as patrol, configured in Tivoli Storage Manager application toadminister the Tivoli Storage Manager application.

On Windows platforms:

an administrator user

a non-administrator account, such as patrol, configured in Tivoli Storage Manager applicationto administer the Tivoli Storage Manager application.

The user login details are configured in the KM. The password is stored in the PATROL Agent in aDES encrypted format.

The encrypted password can be viewed by any user who has access to the PATROL Agent configurationvariables (pconfig). This user could then execute PSL statements using the encrypted password throughthe PATROL Console. This can be prevented by setting up an appropriate Access Control List (ACL) forusers. Please refer to the PATROL Agent Reference Manual for details on how to set up an ACL.

Access Permissions

The Tivoli Storage Manager KM user needs “read & execute” permission to executable and libraryfiles under the paths listed below. The Tivoli Storage Manager installation path INSTALL_PATH,referenced below, is normally /usr/tivoli/tsm or /opt/tivoli/tsm (on Unix) or C:\ProgramFiles\Tivoli\TSM (on Microsoft Windows).

http://support.microsoft.com/kb/948698



12Requirements

Version 2.7.00


Unix Microsoft Windows

INSTALL_PATH/client/ba/bin (or bin64) INSTALL_PATH\baclient

INSTALL_PATH/client/admin/bin INSTALL_PATH\Server

INSTALL_PATH/server/bin INSTALL_PATH\StorageAgent

INSTALL_PATH/StorageAgent/bin INSTALL_PATH\Server\tsmdiag

INSTALL_PATH/server/bin/tsmdiag INSTALL_PATH\StorageAgent\tsmdiag

INSTALL_PATH/StorageAgent/bin/tsmdiag/usr/lib C:\Windows\system32

If the KM is enabled to failover in a clustered environment, the login user needs execute permissionsto the following cluster commands:

/opt/VRTSvcs/bin/hagrp (in Veritas Cluster Server)vxdctl (in Veritas Cluster File System)/usr/cluster/bin/clrg (in Oracle Solaris Cluster)C:\Windows\sysnative\cluster (in Microsoft Cluster)

The Tivoli Storage Manager KM includes some scripts which should be executable by the PATROLAgent user and the Tivoli Storage Manager KM user. These scripts are stored under KM_HOMEpath, normally PATROL_HOME/TSM.

To list all OS commands used by the Tivoli Storage Manager KM, execute the following PSL codefrom the PATROL Console, using PSL Task menu, after installing and loading the KM.

i=0; sudoers="";foreach var (grep("^/Runtime/TSM/CommandControls/",pconfig("LIST"))){ ctl=get(var); opt=ntharg(grep("Option",ctl),"2-"," ="); nsa=ntharg(grep("NoSudoAttempt",ctl),"2-"," ="); sua=ntharg(grep("SingleUserAttempt",ctl),"2-"," ="); typ=ntharg(grep("CommandType",ctl),"2-"," ="); cmd=nthargf(grep("CommandText",ctl),"2-","=","=");

if((typ == "")||(typ == "OS")) { met=""; if(opt == "NoLogin") { met = "(run as patrol user)"; } elsif(nsa == "YES") { met = "(run as configured user without sudo)"; } elsif(sua == "YES") { met = "(run as supplied user - used in menu)"; } else { scmd=cmd; s=index(scmd,"%sudo"); if(s) { scmd=replace(substr(scmd,s,length(scmd)),"%sudo",""); } sudoers=union(sudoers,ntharg(ntharg(scmd,1,"|"),"1-"," "," ")); } printf("(%2d) %-30s %-40s: %s\n",i++,ntharg(var,"5","/"),met,cmd); }}

printf("\n\nCommands used with sudo:\n%s",sort(sudoers));

The PATROL Agent user (normally patrol) requires write permission to DSM_LOG directory anddsmerror.log file. For all other paths and files listed in the table below the PATROL Agent user needs“read & execute” permission.

13Requirements

Version 2.7.00


Unix Microsoft Windows

DSM_DIR (INSTALL_PATH/client/ba/bin or bin64) DSM_DIR (INSTALL_PATH\baclient)

DSM_LOG (KM_TEMP) DSM_LOG (KM_TEMP)

DSM_DIR/dsmadmc DSM_DIR\dsmadmc.exe

DSM_CONFIG (DSM_DIR/dsm.opt) DSM_CONFIG (DSM_DIR/dsm.opt)

If a monitored log file cannot be read by the PATROL Agent user, it will copied to KM_HOME path usingthe configured KM login account, and processed by the PATROL Agent user. On completion the copiedlog file will be removed. This may increase the file system usage under KM_HOME temporarily duringthis activity.

On Windows platforms the Tivoli Storage Manager installation is identified by checking the registrysub-keys under HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\.

The configured login user should have sufficient privileges to run regedit command on the managednode.

Sudo User for Operating System Access

If a non-root user with sudo privileges is preferred as the Tivoli Storage Manager KM user, configurethe account as a sudoer through the visudo utility using code appropriate for your platform asdetailed below. This user should be able to execute TSM commands and OS commands.

The code below also applies to all non-root users who may execute Tivoli Storage Manager KMadministration and report menu commands using their sudo privileges. The Tivoli Storage ManagerKM accepts any non-root user with the following sudo configuration in the sudoers file. Please replaceuser1, user2, user3 with appropriate KM user name. The Tivoli Storage Manager installation path INSTALL_PATH, referenced below is normally /usr/tivoli/tsm or /opt/tivoli/tsm andPATROL_HOME is the path where the PATROL Agent is installed (including the target, like /opt/bmc/Patrol3/Solaris29-sun4/).

This non-root sudo user configured in the KM will be able to execute Tivoli Storage Manager commands.To prevent unauthorized access, ensure this user is only used within the KM and not made public forgeneral use.

Entering the non-root sudo user with ‘Use Sudo’ option selected in to the login configuration dialog,before updating the sudoers file, will generate sudo errors. Also if the sudo user is configureddifferently, the KM may run sudo commands using incorrect sudo settings, which may expose the sudouser password.

On Solaris:

User_Alias TSMKMUSERS = user1, user2, user3Defaults:TSMKMUSERS !lecture,!authenticate,\env_keep+="LD_LIBRARY_PATH INSTALL_PATH KM_HOME \KM_TEMP DSM_CONFIG DSM_DIR DSM_LOG",env_reset

14Requirements

Version 2.7.00


TSMKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\INSTALL_PATH/server/bin/*,\INSTALL_PATH/client/ba/bin/*,\PATROL_HOME/lib/TSM/*,PATROL_HOME/bin/*

user1, user2, user3 must be replaced with username(s) used by the KM; INSTALL_PATH and PATROL_HOME with therelevant paths.

On HP-UX:

User_Alias TSMKMUSERS = user1, user2, user3Defaults:TSMKMUSERS !lecture,!authenticate,\env_keep+="SHLIB_PATH INSTALL_PATH KM_HOME \KM_TEMP DSM_CONFIG DSM_DIR DSM_LOG",env_resetTSMKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\INSTALL_PATH/server/bin/*,\INSTALL_PATH/client/ba/bin/*,\PATROL_HOME/lib/TSM/*,PATROL_HOME/bin/*


On AIX & Linux:

User_Alias TSMKMUSERS = user1, user2, user3Defaults:TSMKMUSERS !lecture,!authenticate,\env_keep+="LIBPATH INSTALL_PATH KM_HOME \KM_TEMP DSM_CONFIG DSM_DIR DSM_LOG",env_resetTSMKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\INSTALL_PATH/server/bin/*,\INSTALL_PATH/client/ba/bin/*,\PATROL_HOME/lib/TSM/*,PATROL_HOME/bin/*


Admin Interface User Access

BMC ProactiveNet Performance Management - Tivoli Storage Manager Monitoring requires that anadministrator account (standard administrator with no other privileges) be added to the TivoliStorage Manager server for use by PATROL and the Tivoli Storage Manager KM.

This account is used to query the configuration details and resource utilization of the server throughthe Tivoli Storage Manager Administrative Client interface (DSMADMC). No changes are made by thisuser on the Tivoli Storage Manager server - the Tivoli Storage Manager KM operates in “read-only”mode for normal operation.

The suggested name for this DSMADMC user account is patrol and it can be created as part of theconfiguration procedure described in Configuring the User Accounts. Alternatively, the user accountcan be set up directly in Tivoli Storage Manager, and the details simply entered during KMconfiguration in the same way that the OS login details are entered. The password is stored in thePATROL Agent in a DES encrypted format.

15Requirements

Version 2.7.00


This DSMADMC user does not require operating system access. Therefore it is not required to be the same as the OSlogin account.

DSMADMC command binary is executed using PATROL Agent user account. Therefore the PATROLAgent user should be able to access required paths and binaries of DSMADMC. This includes execute permission to DSM_CONFIG path and dsmadmc (or dsmadmc.exe) file and writepermission to DSM_LOG path and dsmerror.log file.

The encrypted password can be viewed by any user who has access to the PATROL Agentconfiguration variables (pconfig). This user could then execute PSL statements using the encryptedpassword through the PATROL Console. This can be prevented by setting up an appropriate AccessControl List (ACL) for users. Please refer to the PATROL Agent Reference Manual for details on howto set up an ACL.

To list all DSMADMC commands used by the Tivoli Storage Manager KM, execute the following PSLcode from the PATROL Console, using “PSL Task” menu, after installing and loading the KM.

i=0;foreach var (grep("^/Runtime/TSM/CommandControls/",pconfig("LIST"))){ ctl=pconfig("GET", var); typ=ntharg(grep("CommandType",ctl),"2-"," ="); cmd=nthargf(grep("CommandText",ctl),"2-","=","="); if(typ == "DSMADMC") { printf("(%2d) %-25s: %s\n",i++,ntharg(var,"3","/"),cmd); }}

Planning

17Adding Central Monitoring Administration Tags

Version 2.7.00


Adding Central MonitoringAdministration Tags

Adding Central Monitoring Administration tags should be taken into consideration before installation.

A policy specifies a set of actions to be taken when a specific condition on the BMC PATROL Agent isfulfilled. A policy enables you to perform the following actions:

Apply specific configuration to one or more BMC PATROL Agents

Configure thresholds and set baselines on BMC ProactiveNet Child Servers

Each policy is assigned a BMC ProactiveNet Central Monitoring Administration tag and each BMCPATROL Agent can have one or more tags assigned to it. When you assign a tag to a BMC PATROLAgent the associated policy is applied to the PATROL Agent. You can assign the tag value of a policyto a PATROL Agent in the following ways:

You can add a PATROL Agent and set the tag as part of the configuration process that youperform from Central Monitoring Administration. For details, see Managing downloads in CentralMonitoring Administration.

If the PATROL Agent has already been installed, use PATROL Configuration Manager to set thefollowing ruleset that provides the tags:/AgentSetup/Identification/Tags/TAG/tagName =tagDescription

For example if the tag which has to be applied is oracleTag, the ruleset is as follows/AgentSetup/Identification/Tags/TAG/oracleTag= “ORACLE MONITORING”

In BMC ProactiveNet version 9.0, the tag description is ignored, and only the tag name is used to evaluate the policy.

Installing

19

Version 2.7.00


The creation of the Tivoli Storage Manager KM installation package is performed directly from BMCProactiveNet Central Monitoring Administration. An installation package for a component can bedownloaded and installed on several servers. The component installation package can be edited andsaved under a new name.

With Central Monitoring Administration, administrators select monitor installation components, suchas the BMC PATROL Agent and monitoring solutions, from a repository to create an installationpackage. The components can then be installed together using the installation package.Administrators can reuse the installation packages, or deploy the packages to multiple computers.

Preparing for Installation

The BMC ProactiveNet Central Monitoring Repository is a requirement on the BMC ProactiveNetCentral Server where Central Monitoring Administration is enabled. The Central Monitoring Repositoryincludes the current versions of BMC components that you can use with BMC ProactiveNet.

After creating a component installation package, administrators can save the package to theMonitoring Installation Packages list for future use, or download the package on the current hostwithout saving the package. For saved packages, administrators can download and install thepackage on any host, or edit a package.

For supported 64-bit Linux versions, you must install the Linux runtime package, glibc.i686, version 2.3.4 or later.Without the Linux runtime package, BMC ProactiveNet component installations might fail.

For further details regarding the BMC ProactiveNet Central Monitoring Administration, please refer to the BMCdocumentation.

20Creating a Component Installation Package

Version 2.7.00


Creating a Component InstallationPackage

If you want to import the entire repository, first download Central Monitoring Repository files fromthe BMC Electronic Product Distribution (EPD) facility, or copy the files from your installation kit, tothe BMC ProactiveNet Central Server file system.

To import a single or custom solution1. In the navigation pane of Central Monitoring Administration, click the Repository drawer and

select Manage Repository.

2. Click Import.

3. In the Import a New Solution dialog box, select Single solution or Custom solution.

4. Browse to a source file in one of the following formats: zip, tar, or tar.gz.The solution must be located on the local computer from which you are running the CentralMonitoring Administration web-based console.

5. (Custom solution, only) provide the following details:

Custom solutions name: The name of the custom solution, as it will be displayed in CentralMonitoring Administration.

Custom solution version: The version number for the custom solution. Values in the firsttwo version boxes are required.

6. Click Import.

The selected archive file is imported to the repository and extracted. You can close the windowduring the import process.

21Creating a Component Installation Package

Version 2.7.00


To create a component installation package1. In the navigation pane of Central Monitoring Administration, click the Repository drawer and

select Monitoring Repository.

2. Click Add .

3. Select the operating system for which you want to create a package, and then select a platformon which you want to install the package.The list of components in the repository that are supported on the specified operating systemand platform is displayed.

4. From the Available components list, select components that you want to include in thepackage.

5. From the Version list, select the version of the component that you want to include in thepackage.You can select a specific version or you can select latest, which automatically updates thepackage with the latest versions of the components when new versions of those components areadded to the Central Monitoring Repository. By default, the appropriate BMC PATROL Agent for the operating system and platform that youchose is included in the Selected components list.

6. Click the right arrow button to move the selected components into the Selected Componentslist, and then click Next.The installation wizards for the products that you selected are displayed. They'll vary dependingon the products or components that you selected to include in the package. Go through thewizards to complete the installation.

7. The Installation Package Details is displayed. Verify that the operating system and platformare correct for the type of package that you want to create. Also verify that the components thatyou want to include are listed in the Included Components list. Provide the followinginformation:

Name: Enter a unique name for the package.

(Optional) Description: Enter a description of the package.The description is displayed in the Monitoring Installation Packages list on the MonitoringRepository window.

Format: Select a file compression format for the package.

8. Perform one or both of the following actions:

To save the package for future installation on the current host or other hosts, click SaveInstallation Package. The package is available in the Monitoring Installation Packageslist.

To download the package immediately, click Download.

If you click Download and do not click Save Installation Package, the package is not saved in the Monitoring InstallationPackages list for later use or editing.

9. When you are finished, click Close.

22Editing a Component Installation Package

Version 2.7.00


Editing a Component InstallationPackage

You can edit any part of an existing component installation package except the operating system andplatform.

1. In the navigation pane of Central Monitoring Administration, click the Repository drawer andselect Monitoring Repository.

2. (Optional) To filter the list of packages, select an operating system from the Filter byOperating System list.

3. Select the row for a package and click Edit .

4. From the Available components list, add or remove components, and click Next.

5. Perform one or more of the following actions, depending on your requirements:

Edit the installation details of existing components.

Add installation details for new components.

Click Finish Update to skip to the Installation Package Details window.

If you add a component to the package, you must complete the configuration process. The Finish Update button showsan explanatory tooltip and does not skip to the Installation Package Details window.

6. In the Installation Package Details window, modify the following information as needed:

Name: To save your changes to the same package, do not change the name. To save thepackage under a unique name, change the name.

(Optional) Description: Enter a description of the package.The description is displayed in the Monitoring Installation Packages list on the MonitoringRepository window.

Format: Select a file compression format for the installation package.

7. Perform one or both of the following actions:

To save the package for future installation on the current host or other hosts, click SaveInstallation Package.The package is available through the Monitoring Installation Packages list.

To download the installation package immediately, click Download.

If you click Download and do not click Save Installation Package, the changes are not saved in the MonitoringInstallation Packages list for later use or editing.

8. When you are finished, click Close.

23Downloading and Installing an InstallationPackage

Version 2.7.00


Downloading and Installing anInstallation Package

You can download an installation package and install the components on one or more hosts. Theinstallation runs silently with the information entered during package creation.

RecommendationIf you defined the BMC ProactiveNet Integration Service variable for PATROL Agents in theinstallation package, ensure the agents are started in phases. Do not start newly deployed agentsall at once. Start and configure monitoring for the agents in planned phases to reduce theperformance impact on the Integration Service nodes and on the BMC ProactiveNet Serverassociated with the automatic workflow process.

To download and install an installation package1. From the computer on which you want to install the package, log on to BMC ProactiveNet

Central Monitoring Administration.

2. (Optional) To filter the list of installation packages, select an operating system from the Filterby Operating System list.

3. Click the link for the installation package that you want to download.

4. Through the browser's download dialog box, save the installation package.

5. Extract the installation package as appropriate for your operating system. The package isextracted to the bmc_products directory on the current host.

6. From the bmc_products directory, run the installation utility for your operating system:

(UNIX or Linux) RunSilentInstall.sh

(Microsoft Windows) RunSilentInstall.exe

The package is installed on the current host. If the package includes a BMC PATROL Agent, the agentsends a configuration request by passing its tags to BMC ProactiveNet Central MonitoringAdministration, via the Integration Service. Central Monitoring Administration evaluates policies thatmatch the tags, determines the final configuration to be applied, and sends the configurationinformation back to the agent. Monitoring is based on the configuration information received by theagent.

If no policy matches the tags associated with the agent, the agent does not receive configurationinformation. The agent does not begin monitoring until a matching policy is created.

For further information regarding the Repository management, please refer to the BMC ProactiveNet Central MonitoringAdministration documentation.

Configuring After Installation

25

Version 2.7.00


You configure monitoring of Tivoli Storage Manager KM when you create a policy. A policy is atemplate containing the configuration of a PATROL Agent. A policy can be assigned to one or morePATROL Agents using a unique tag (Central Monitoring Administration tag), and a PATROL Agent canbe assigned one or more policies with different priorities.

If you have not already added the Central Monitoring Administration tag to your PATROL Agentsduring the solution installation, then you must manually assign the tag after you have configured thepolicy. For details, see Adding Central Monitoring Administration Tags.

Configuring General Settings

Through the General tab of the Add Policy dialog, you can create a new policy. A policy specifies aset of actions to be taken when a specific condition on the PATROL Agent is fulfilled. First andforemost, actions include monitor configuration. Once a monitor is configured, policies can alsospecify threshold creation and the setting of baselines. A policy can also include intelligent server-sidethresholds so that IT administrators can immediately be alerted on potential problems.

Field Instructions

Name Enter a policy name. Policy names must be unique. In an environment with tenants, policy names must be unique for a single tenant

Tenant(For environments withtenants)

Select a tenant name. See Policies and tenants for details.

Global indicates a policy applicable to all tenants.

Provider indicates a policy applicable to the cloud service provider

Enable policy Select this option to enable the policy, or clear the option to disable the policy. The option isselected by default. If you clear the option, the policy and its associations remain intact, but thepolicy configuration is not applied until the policy is enabled again.

Precedence Enter a number from 0 to 999.

Description (Optional) Enter a policy description.

Tag Enter a Central Monitoring Administration tag.Policies are applied to BMC PATROL Agents with matching tags.Tags are case sensitive and cannot contain spaces or any of the following characters: /, \, {, },<, >, ‘, “, &.

Policy precedence

When more than one policy is applied to a BMC PATROL Agent and BMC ProactiveNet Child Server,configuration is a union of every attribute defined the policies. If a conflict arises (that is, two policiesconfigure the same attributes), it is resolved in one of the following ways:

Policies with the same tag: If conflicting policies have the same tag, the precedence valuedetermines the order the policies are applied. The policy with the lower number value forprecedence is the policy from which the final configuration is applied.

Policies with different tags: If conflicting policies have different tags, then the policies areapplied according to the order they are listed on the BMC PATROL Agent. The policy listed laston the agent is the policy from which the final configuration is applied.

26Configuring General Settings

Version 2.7.00


Managing PoliciesThis topic provides general instructions for the following policy management tasks: editing, deleting,enabling and disabling.

Before you begin

Enable Central Monitoring Administration and log on to Central Monitoring Administration. Refer tothe BMC documentation and more especially to the section Enabling and configuring CentralMonitoring Administration for details.

Policies with only threshold configuration or server side configuration are applicable only after a policy with monitorconfiguration is applied.

To edit a monitoring policy1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select

a policy view.

2. Select a policy and click Edit .

3. Edit the Configuring general settings of the policy.

4. Edit information on one or more of the following tabs:

Configuring monitor settings.

Configuring threshold settings.

5. Click Update.

To delete a monitoring policy

Deleting a policy deletes all monitor instances and most settings configured through the policy. Devicesremain in the User Groups to which they have been added.

1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and selecta policy view.

2. Select one or more policies and click Delete .

3. Click Yes to confirm deletion.

To enable or disable a monitoring policy

Enable or disable policies for maintenance and troubleshooting. When a policy is disabled, the policyand its associations remain intact, but the policy configuration is not applied until the policy isenabled again.


2. Select one or more policies and click Enable or Disable.

27Configuring Monitor Settings

Version 2.7.00


Configuring Monitor Settings

When you create or edit a policy, you can add and configure monitor types. The Add MonitorTypes dialog box presents configuration fields for compatible BMC PATROL monitoring solutions thatare located in the Central Monitoring Repository. For a list of monitoring solutions that you canconfigure through Central Monitoring Administration, see the Monitoring solutions configurablethrough Central Monitoring Administration chapter in the BPPM online documentation.

For configuration details for a specific monitor type, see the monitor documentation. To configurecustom monitoring solutions through Central Monitoring Administration, ensure the solution isstructured correctly; for details, see the Building a PATROL Knowledge Module Developers Guide onBMC Support website.

To configure the Monitor Type settings using the AddMonitor Types dialog box

To add a monitor type:


2. Click Add to display the Add Policy dialog box.

3. Configure the policy general settings.

4. Click the Monitor Configuration tab.


Version 2.7.00


5. Click Add

Adding Monitor Types

6. From the Solution menu, select Tivoli Storage Manager.

7. From the Version menu, select the required version.

8. From the Monitor Type menu, select the required monitor:

Monitor Type Description

Tivoli Storage Manager KM To set the general settings of Tivoli Storage Manager KM (credentials, debug mode,instances, multi-node mode, etc.)

TSM Automated Drive To set filtering options that indicate the automated drives to monitor.

TSM Automated Library To set filtering options that indicate the automatic libraries to monitor.


Version 2.7.00


TSM Client To set filtering options that indicate the clients to monitor.

TSM Daemon To set filtering options that indicate the daemons to monitor.

TSM Domain To set:filtering options that indicate the domains to monitorbackup restrictions.

TSM Domain Client Node To set filtering options that indicate the domain client nodes to monitor.

TSM Job To indicate:how long the jobs in OK, Suspicious, and Failure status will be monitored.the status the jobs will have when the monitoring period is over.

TSM Manual Drive To set filtering options that indicate the manual drives to monitor.

TSM Mount Request To indicate how long the mount requests will be monitored.

TSM Process To indicate how long the processes will be monitored.

TSM Storage Pool To set filtering options that indicate the storage pools to monitor.

Configuring Tivoli Storage Manager KMBefore using Tivoli Storage Manager KM, you'll have to configure its general settings. This section willlearn you how to:

configure the user account

enable the debug mode

configure the maximum number of instances

configure the multi-node monitoring mode

configure the TSM server discovery overrides (Optional).

Configuring the User AccountA user account with administrative privileges must be configured in BMC ProactiveNet to read andexecute Tivoli Storage Manager application programs and file systems. Depending on the operatingsystems used, several options will be available.

On Unix platforms, you can use the following user accounts:

a root user

a non-root user, such as patrol, that has sudo privileges on Tivoli Storage Manager to executeapplication programs and access file systems

a non-root account, such as patrol, configured in the Tivoli Storage Manager application toadminister the Tivoli Storage Manager application.

On Windows platforms, you can use the following user accounts:


Version 2.7.00


an administrator user

a non-administrator account, such as patrol, configured in the Tivoli Storage Manager applicationto administer the Tivoli Storage Manager application.

To configure the user account1. Add or edit a monitor type

2. From the Monitor Type menu, select Tivoli Storage Manager KM


Version 2.7.00


3. In the Hostname field, enter:

localhost to apply these settings to all PATROL Agents installed on the Tivoli StorageManager servers

a hostname or IP address to apply these settings to a specific server

3. Set the TSM Credentials:

To use the default PATROL Agent Account, check the Use Agent Default Account box

To use a different user account, enter the login details in the Username and Password fields

(Unix Only) If the user account has sudo privileges, check the Use Sudo box and indicate thesudo binary file path (by default: /usr/local/bin/sudo)

5. Specify the TSM Admin Client User ID and Password

6. Indicate the DSMADMC path. By default, the KM discovers the DSMADMC binary path under thedefault installation path.

7. Click the Advanced button if you need to configure:

the debug mode

the maximum number of instances

the multi-node monitoring mode

the TSM Server discovery overrides (Optional).

6. Click Add to List.

7. Click Update.

Enabling the Debug ModeWhen you encounter an issue and wish to report it to Sentry Software, you will be asked to enablethe Debug Mode and provide the debug output to the Sentry Software support team.

To enable the debug mode1. Edit a Tivoli Storage Manager KM monitor type:

In the navigation pane of Central Monitoring Administration, click the Policies drawer andselect a policy view

Select a policy and click Edit

In the Monitor Configuration tab, select Tivoli Storage Manager KM monitor type and

click Edit


Version 2.7.00


Editing the Tivoli Storage Manager Monitoring Settings


Version 2.7.00


2. From the List - TSM Monitoring Settings, select the host or localhost

3. Click the Advanced button

Advanced Settings


Version 2.7.00


4. Click the Debug button

Configuring the Debug Mode

5. Select all the elements for which you want to obtain debug information

6. In the Options section, indicate:

when the system must stop logging debug information. The required format is: YYYY/MM/DDHH:MM:SS

where the debug file will be stored. The default path is: <PATROL_HOME>/lib/TSM/debug

7. Click Close on all pop-ups

8. Click Modify Selection in the main window and click Update.

When the debug end time is reached, a tar/zip file is automatically created under <PATROL_HOME>/lib/TSM/ and can be sent to the BMC Support for help. It is also recommended to check the TSM.logfile, stored in <PATROL_HOME>/log, for any error.


Version 2.7.00


Configuring the Maximum Number of Instances1. Edit a Tivoli Storage Manager KM monitor type:



In the Monitor Configuration tab, select a Tivoli Storage Manager monitor type and click

Edit

Editing the Tivoli Storage Manager Monitoring Settings


Version 2.7.00




Advanced Settings


Version 2.7.00


4. Click the Instance Max button

5. For each monitored element, indicate the maximum number of instances to be displayed

6. Enter 0 in the relevant field to disable the monitoring of a specific element




Version 2.7.00


Configuring the Multi-Node Monitoring ModeIf the Tivoli Storage Manager environment is installed in a cluster using Veritas Cluster Server,Veritas Cluster File System, Oracle Solaris Cluster or Microsoft Cluster, Tivoli Storage Manager KMmust be installed on all the cluster nodes to enable continuous monitoring and avoid single point offailure. To avoid duplicate alerts from multiple nodes, it is recommended to configure the solution tooperate in multi-node monitoring mode.

To configure the multi-node monitoring mode1. Edit a Tivoli Storage Manager KM monitor type:



In the Monitor Configuration tab, select Tivoli Storage Manager KM monitor type and click

Edit


Version 2.7.00


Editing the Tivoli Storage Manager KM Monitor Type


Version 2.7.00




Advanced Settings


Version 2.7.00


4. Select Enable Multi-node Monitoring Mode and click the Multi-node M... button

Configuring Multi-node Mode

5. Configure the Multi-node Mode:

Select the appropriate Cluster Application.

Indicate the Failover Group Name. Leave this field blank if you previously selected VeritasCluster File System. Then the Tivoli Storage Manager KM will monitor the entire cluster fromthe active master system, which is identified by “vxdctl -c mode” command. This methodrequires vxconfigd in enable mode with its clustered state active.

In the Monitoring Node Names field, name all the nodes where the solution is installed. Thelist must be delimited by commas.

6. (Optional) Allow the solution to check the monitoring mode of the remote PATROL Agents. If the Remote PATROL Agent Checking is disabled, the solution will monitor actively through activeTSM Server system or on the node where failover group is online and will not check themonitoring status of the other nodes through PATROL Agent:

Check the Enable Remote PATROL Agent Checking box.

Click the Remote Agent button


Version 2.7.00


Configuring the Remote Agent

In the Monitoring Node Name field, indicate the cluster node used for multi-node modefailover

Indicate all the information required to communicate with the remote PATROL Agent (protocol,port number, and credentials)

In the Number of Attempts field, indicate how many times the solution will try tocommunicate with the remote PATROL Agent before failing over

Enter the timeout between attempts

Click Add to List

Resume the procedure for all the nodes previously listed in step 5



Tivoli Storage Manager will then be monitored through the active or online node. The other nodes,which are standing by for a failover, will be in passive multi-node mode and only the local TivoliStorage Manager components will be monitored.


Version 2.7.00


If a managed node is unable to determine the system which should be in Active Multi-node Mode, it will change toTemporary Single-node Mode.

Configuring the TSM Server Discovery Overrides (Optional)The solution automatically discovers the Tivoli Storage Manager installation path, the DSM_DIR andDSM_LOG directory paths, the DSM_CONFIG file path, the temporary directory path used by the TSMKM, the node type, and the node status. This information can however be overridden.

To configure TSM server discovery overrides1. Edit a TSM KM monitor type:



In the Monitor Configuration tab, select a Tivoli Storage Manager KM monitor type and

click Edit


Version 2.7.00


Editing the Tivoli Storage Manager KM Monitor Type


Version 2.7.00




Advanced Settings

4. In the TSM Server Discovery Overrides section, indicate:

the TSM installation path

the DSM_DIR directory path

the DSM_CONFIG file path

the DSM_LOG directory path

the temporary directory path

the node type

the node status alarms and warnings




Version 2.7.00


Filtering Elements to MonitorBy default, the solution monitors all the elements discovered, which may represent an importantworkload to the agents and the BPPM servers. Because the monitoring of some elements may beirrelevant for various reasons, you can apply filters to indicate which elements will be monitored ornot.

Filtering options are available for the following monitor types: TSM Automated Drive, TSM AutomatedLibrary, TSM Client, TSM Daemon, TSM Domain, TSM Domain Client Node, TSM Manual Drive, andTSM Storage Pool.

To filter elements to monitor1. Add or edit a monitor type

2. Select the Monitor Type for which you wish to apply filters.


localhost to apply these settings to all PATROL Agents installed on Tivoli Storage ManagerServers


4. Indicate which elements will be monitored:

Click the Filtering button

In the Keep Only... section, indicate the regular expression for the element to be monitoredand click Add to List

In the Exclude... section, indicate the regular expression for the element not to be monitoredand click Add To List

Resume procedure to keep and/or exclude as many elements as required

Click Close

5. If needed, manually add elements to be monitored:

Click the Manual Add button

Indicate the element to be monitored and click Add to List

Resume procedure to add as many elements as required

Click Close

6. Click Add to List.

7. Click Add.

8. Finally, Update the policy.


Version 2.7.00


Configuring JobsBy default, the Tivoli Storage Manager KM monitors all scheduled jobs that completed successfully for24 hours and any other scheduled job for 72 hours. This monitoring duration can however bemodified to better suit your requirements.

Increasing the monitoring duration may affect the performance of the application.

To configure jobs1. Add or edit a monitor type and select TSM Job as a Monitor Type.

Configuring Tivoli Storage Manager Jobs


localhost to apply these settings to all PATROL Agents installed on Tivoli Storage Managerservers


3. In the Monitoring Duration section:

Indicate how many hours the jobs in OK, Suspicious, and Failure status will be monitored


Version 2.7.00


Uncheck Keep Monitoring Active Jobs Indefinitely if you prefer not to monitor active jobswhen their duration exceeds the monitoring duration set above

5. Click Add to List

6. Click Add.

7. Finally, Update the policy.

Configuring Mount RequestsBy default, the Tivoli Storage Manager KM monitors all mount requests for 24 hours. This monitoringduration can however be modified to better suit your requirements.


To configure mount requests:

1. Add or edit a monitor type and select TSM Mount Request as a Monitor Type.

Configuring Mount Requests





Version 2.7.00


3. In the Mount Request Configuration section, indicate how many hours the mount requestswill be monitored


5. Click Add.

Configuring Domains

To Configure Domains:

1. Add or edit a monitor type and select TSM Domain as a Monitor Type.

Configuring Domains




Version 2.7.00



1. Set the filtering options. Refer to Filtering Elements to Monitor for more details.

2. If you want a warning to be triggered when a backup is started during a specific period of time,configure a backup restriction window:

Check the Enable Backup Restriction Window box

Indicate the Restriction Start and End Time. The format required is HH:MM:SS and therestriction window must at least last 5 minutes.

3. Click Add to list.

4. Click Add.

Configuring TSM ProcessesBy default, the Tivoli Storage Manager KM monitors all processes for 24 hours. This monitoringduration can however be modified to better suit your requirements.


To configure TSM processes:


Version 2.7.00


1. Add or edit a monitor type and select TSM Process as a Monitor Type.

Configuring Mount Requests




3. In the Process Configuration section, indicate how many hours the processes will bemonitored


5. Click Add.

52Configuring Thresholds

Version 2.7.00


Configuring Thresholds

When you are creating or editing a policy, you can add and configure monitor thresholds. The AddThresholds dialog box presents threshold configuration fields for BMC ProactiveNet monitors thatare configured through Central Monitoring Administration.

For details about baselines and Key Performance Indicators (KPI), see BMC ProactiveNet CentralMonitoring Administration or BMC ProactiveNet documentation or refer to the Managing Baselinesand Key Performance Indicators section. For details about the monitored attributes, refer to thespecific monitor type in the Reference Guide section.

Before you begin

Ensure that monitor configuration is complete before thresholds are applied. Thresholds cannot beapplied to monitors that are not configured through Central Monitoring Administration. If you havenot done so already, define general policy details.

To add and configure monitor thresholds1. Open the Add Policy dialog box. Click for steps:

In the navigation pane of Central Monitoring Administration, click the Policies drawer andselect a policy view.

Click Add , or select an existing policy and click Edit .

2. Select the Threshold Configuration tab and click Add .

3. In the Add Thresholds dialog box, select an item from each of the following lists: Solution,Version, and Monitor Type. Configuration fields are displayed.

4. In the Scope list, the Instance option is automatically selected. Type an Instance Namestring or regular expression to apply threshold configuration to instances with matching patterns.Select Match Device Name to include the associated device and use the entire<deviceName>\<instanceName> string for pattern matching. Instance thresholds are applied tothe matched monitor instance names or instance names patterns.You can use the following regular expression patterns for the instance name: ?, +, *, ( ), |, [ ],{ }, ,̂ $, .If the instance name contains one of the pattern characters (except for *), use a backslash ( \ )before the pattern character. For example, to enter the instance name Storage1 (1), enterStorage1 $1$.

5. From the Attribute list, select a monitor attribute.

In the Attribute list, some attributes are designated as key performance indicators (KPIs). Depending on the monitoredenvironment and version, the list of KPIs might appear differently in the BMC ProactiveNet Operations Console.

6. From the Type of Threshold list, select the threshold type.

7. Select and enter values for the threshold parameters.

8. To continue configuration, perform one or more of the following actions in the Add Thresholdsdialog box, and then select a different monitor type, version, or solution:

To add the configuration details for the threshold to the Threshold Configuration tab, clickthe Add button at the bottom of the window.

53Configuring Thresholds

Version 2.7.00


To return the settings in the current window to default values, click the Reset button at thebottom of the window. The values on the current window are reset. Be sure to click the Addbutton to save the configuration on the Threshold Configuration tab.

9. When you finish configuration, click Close. The configuration details are displayed in the table onthe Threshold Configuration tab.

10. When you finish configuring thresholds, click Save at the bottom of the Add Policy dialog box,or Update at the bottom of the Edit Policy dialog box.

After you save or update the policy, new threshold configurations are pushed to BMC PATROL Agentswith matching Central Monitoring Configuration tags.

To edit a threshold configuration1. On the Threshold Configuration tab, select a threshold definition, and click Edit.

2. Edit the configuration values and click Update.

3. When you finish editing the threshold configuration, click Close.

4. To save changes to the policy, click Update at the bottom of the Edit Policy dialog box.

After you update the policy, updated threshold configurations are pushed to BMC PATROL Agentswith matching Central Monitoring Configuration tags.

To delete a threshold configuration1. On the Threshold Configuration tab, select attributes, monitor types, versions, or

solutions.

2. Click Delete.

3. After you delete one or more threshold configurations, click Close.

4. To save changes to the policy, click Update at the bottom of the Edit Policy dialog box.

After you update the policy, deleted threshold configurations are removed from BMC PATROL Agentswith matching Central Monitoring Configuration tags.

Recommended Thresholds

Thresholds define acceptable high and/or low values for the data collected. Thresholds can becreated as part of a policy that can be applied to multiple monitors types on multiple BMC PATROLAgents. The Reference Guide provides a list of monitor types with their respective attributes and,when meaningful, a recommended threshold.

54Using BMC ProactiveNet PerformanceManagement

Version 2.7.00


Using BMC ProactiveNetPerformance Management

This section provides a brief overview of how to navigate and use the product in the BMCProactiveNet Operations Console.

Navigating the BMC ProactiveNet Operations Console

Adding attributes to the graph

Viewing and manipulating attribute graphs

Viewing monitors for a device

Changing Thresholds

For more detailed information, see BMC ProactiveNet User Guide in the PDF product guides.

Navigating the BMC ProactiveNet OperationsConsoleThe BMC ProactiveNet Operations Console is a Web-based application that provides options tonavigate through BMC ProactiveNet and view all of the information collected and computed by theBMC ProactiveNet Server related to events, views, and graphs.

Navigation tree

The navigation tree shows an at-a-glance synopsis of events and views. Event and componentfolders are displayed hierarchically and are divided into the following categories, or nodes.

Object Definition

Global node The Global node contains the following default collectors:All Event Collectors—displays the entire event collector hierarchyAll Abnormalities—displays all the abnormality eventsAll Services—displays all the servicesAll Groups—displays all the groupsAll Devices—displays all the devicesBased on permissions, users can create event and component folders under this node to organize theevent view.

My Foldernode

Based on permissions, users can create event and component folders under this node to organize theevent view.

To further organize your display, beneath these top-level folders you can add event and componentfolders, including folders for Component Instances (CIs) associated with a service model. Your abilityto add event and component folders depends on your permissions.

The severity icons for a collector dynamically change depending on the severity level of the events


Version 2.7.00


for that collector.

For example, if there is a Critical event on one of the devices, the green icon changes to a red icon,indicating a Critical event. The icons enable you to see the status of devices on your systemimmediately.

For complete details, see the BMC ProactiveNet Getting Started Guide on the BMC Support website.

Navigation drawers

The navigation pane in the Operations Console contains a series of drawers that enable you tonavigate through BMC ProactiveNet functions and views. You can select which drawers to display inthe navigation pane.

The following table describes the available drawers in the navigation pane and describes theirfunctions.

Drawer Description

Main Provides access to event lists and displays event information and status.

Other cells Lists available remote cells connected to the BMC ProactiveNet Server and monitored by BMCProactiveNet.

Reports Enables you to generate and manage reports based on data collected by BMC ProactiveNet.Note: You must have permission to view this drawer.

Views & graphs Provides options for the management of views and graphs in the Operations Console

Bookmarks Enables you to view, rename, and delete bookmarks of objects and their related views that youcreate in the navigation tree.

Find CI Provides a search mechanism so that you can search for Component Instances that meet thespecified search criteria.Note: You must have permission to view this drawer.

Event and component folders

Event and component folders enable you to organize cells and collectors to make event displaysmeaningful for operators. For example, you might create an event folder for collectors that gatherdatabase warning events and allow only operators who are database administrators access to thatevent folder. You can drag components from one existing folder to another within the top-levelfolders in the navigation tree. You also can drag and drop CIs from the Tile or Graph view to anexisting folder in the All Services folder.

Event folders

An event folder is a grouping of collectors that shows the relationship of events or abnormalitiesthrough the hierarchy of the navigation tree. Administrators define event folders and associate themwith one or more collectors. Each level of the collector is shown as a node under the event folder. An


Version 2.7.00


event list is associated with the lowest level nodes of an event folder. The parent level of an eventfolder represents all of the events or abnormalities associated with the collectors.

Event collectors

Event collectors gather events for display in an event list to provide operators with meaningfulgroups of events or abnormalities and to show relationship through the hierarchy of the nodes in thenavigation tree. To access the event list for a collector, operators click the collector node in thenavigation tree. Event collectors are dynamic or static. Nodes for dynamic collectors appear ordisappear from the navigation tree based on whether or not events are present that meet the criteriafor those collectors. Nodes for static collectors remain in the navigation tree regardless of whetherevents are present or not.

Component folders

A component folder is a grouping of groups, services, or devices from several different event lists(collectors) that shows the relationship of groups, services, or devices through the hierarchy of thenavigation tree. Administrators define component folders and associate them with one or moregroups, services, or devices. Each level of the component folder is shown as a node under the parentcomponent folder. An event list is associated with the lowest level nodes of a component folder. Theparent level of a component folder represents all of the events associated with the groups, services,or devices. Component folders are static or dynamic. You populate static component folders byselecting from a list of objects. You populate dynamic component folders by creating a query. Staticfolders always contain only the objects that you manually select. Dynamic folders contain the objectsthat match the query, so the contents of these folders can change without further editing.

Operations Console views

The following table shows the different views that are available, depending on what object you selectin the navigation tree. Each view is accessed by clicking the associated Console view icon. If a view isnot available for the object that is selected in the navigation tree, the icon for that view is notdisplayed in the toolbar.

View Description

Event The Event view displays all events in an event list. This is the default view for all objects. Use the Event viewto check the details of events and to address events that highlight incorrect state. Probable Cause Analysiscan help you to identify the cause of the event. An event could be assigned to other users, who canacknowledge and take ownership of the event, fix the problem, and close the event. You can also address theincorrect condition by invoking remote actions, detailed diagnostics, and local actions. The Graph view helpscheck the impacting service and you can cross-launch to Impact Model Designer, Service Level Manager andProduct Catalog in BMC Remedy IT Service Management (BMC Remedy ITSM).You can display an Event view for:

Event collectors

Abnormalities

Services

Groups

Devices


Version 2.7.00


View Description

Monitors

Title The Canvas view enables you to you create a graphical representation of the components that are beingmonitored in your environment. The components are represented by objects that you can place on abackground image. The objects can be graphics, such as images or connectors, or metrics informationrepresented in a tile.You can create and display a Canvas view for:

Event collectors

services

Groups

Devices

Tree/Graph The Tree/Graph view displays information for a selected object as a tree that represents the hierarchy of theobject. The Tree view is available for groups and services. You can use the Tree view to get a real-time,interactive visualization of the event status and other details of the selected group or service. In the Grouphyperbolic tree, the entire group hierarchy and devices are visible on a hyperbolic pane that is mapped to acircular display region. Service tree is applicable only for the selected service.If a service is selected in the navigation tree, this view displays a graphical representation of the configurationitems in the service model and shows how those configuration items relate to each other. Use the Graph viewto monitor events for published service models that represent your business services.You can display a Tree/Graph view for:

Services

Groups

Grid Grid view displays information for the selected object in a tabular format. you can view the event status andother details of the selected object through hyperlinks to graphs, views, etc. You can display a Grid view for:

Abnormalities

Groups

Devices

For more detailed information, BMC ProactiveNet Getting Started Guide on the BMC Support website.

Adding attributes to the graphFollowing configuration, only one attribute is enabled for the graph of each monitor. You might wantto add additional attributes to the monitor graph.

1. In the BMC ProactiveNet Operations console, select the Navigation drawer.

2. Select Global > Devices.

3. Select the Grid view.All the monitored devices are displayed in table format.

4. Select a device from the displayed table.

5. Select a monitor.

6. Click Tools >Show Graph

7. Select the Attributes & Indicators tab.

8. Select one or more attributes.Up to 12 attributes of a monitor can be displayed on a single graph. Though only two units ofmeasurement can be used.


Version 2.7.00


Viewing and manipulating attribute graphsThe graph provides a visual display of the attributes of a monitor. Up to 12 attributes of a monitorcan be displayed on a single graph.

1. In the BMC ProactiveNet Operations console, select the Navigation drawer.


3. Select the Grid view. All the monitored devices are displayed in table format.

4. Select a device from the table.


6. Click Tools > Show Graph

If Collect Data is not enabled then no data is available.

The Graph Display window opens, displaying a graph displaying the values of the selected attributesfor this monitor.You can use the options available on this tab to manipulate the graph. For complete details, refer toBMC ProactiveNet User Guide on the BMC Support website.

Viewing monitors for a deviceThis section provides a brief overview of how to view the monitors for a selected device. Forcomplete details, refer to BMC ProactiveNet User Guide on the BMC Support website.

To view the Monitor types for a device1. In the BMC ProactiveNet Operations console, select the Navigation drawer.



4. Select a device from the table. A hierarchical tree listing the monitors for that device is displayed.You can click the + and - to expand and collapse nodes of the hierarchical tree.

The following information is displayed:

Information Description

Monitor Name Device name or process name, a device might appear more than once if it is monitored byseveral PATROL Agents

Monitor Type Name of the monitor type.This will correspond to the element displayed in the Monitor Name column, specifying thetype of device or process monitored

Source Agent ProactiveNet server where the PATROL Agent and integration service are running

Open Number of open alerts, a green globe is displayed if no alerts are open

Closed Number of closed alerts

Enabled Enabled if data is being collected


Version 2.7.00


Changing thresholdsYou can adjust the thresholds for the attributes of a monitor type either globally or for a specificdevice instance. In the BMC ProactiveNet Operations console, select the Navigation drawer.



3. Select a device from the table.


5. Select Tools > Thresholds. A menu containing the available thresholds is displayed.

Global thresholds are applied to all monitor instances of the selected monitor type. Instance thresholds are applied tothe selected monitor instance.

6. Edit the Threshold settings

7. Click Apply.

Managing Baselines and Key PerformanceIndicatorsIn order to facilitate the detection of abnormalities on your monitored environment, BMCProactiveNet calculates baselines per attributes based on values collected over a specified period oftime to determine a normal operating range. When the collected values for these attributes are outof range, an alert is triggered.

Some attributes are identified by default as Key Performance Indicators and therefore automaticallyincluded in the base lining calculation.

Managing baselines

The baseline is the expected normal operating range for a metric or attribute of a monitor.

The baseline is calculated by collecting the values for a monitor’s attributes and metrics over aspecified time period and establishing a low baseline value (consisting of the 10th percentile of all thevalues for a given time period) and a high baseline value (consisting of the 90th percentile of all thevalues for a given time period), taking a weighted average of these values over time. A higher weightis given to the latest data being factored into the baseline average. The accuracy of the baselineimproves over time.

Requirements for baseline generation

For baselines to be generated for an attribute, that abnormality threshold means that the thresholdexists and is not suppressed. Additionally, if the Key Performance Indicator (KPI) mode is active, only those attributes that have anactive abnormality threshold and are also KPI attributes will have baselines generated for them.


Version 2.7.00


Absolute thresholds (with "outside baseline") or signature thresholds do not satisfy these requirements.

Managing Key Performance Indicators

The KPI attribute of an attribute can be activated or deactivated manually through the BMCProactiveNet Administration Console. In this KM, some attributes have been designated as importantindicators of performance (KPIs). We do not recommend that these default settings are modified.

However, advanced users may activate or deactivate KPIs from the BMC ProactiveNet AdministrationConsole.

To add or remove Key Performance Indicator (KPI) attributes for amonitor type

1. In the Administration Console, from the menu bar, choose Tools > KPI Administration.The KPI Administration dialog box is displayed.

2. From the Monitor Type list, choose the monitor type for which you want to add or remove KPIattributes. A list of attributes for the selected monitor type is displayed.

3. In the KPI column for the attributes that you want to add or remove as Key PerformanceIndicators:

select the KPI check box to add the corresponding attribute as a KPI

deselect the KPI check box to remove the corresponding attribute from the KPIs for thatmonitor type

For complete and detailed information on this procedure, please refer to the BMC ProactiveNet documentation availablefrom BMC Web site.

Attributes considered as KPIs are respectively identified by the following icon: .

Reference Guide

62

Version 2.7.00


Introduction

This chapter provides statistical information about resources, operating status, and performancesmanaged by the Tivoli Storage Manager KM. It contains tables describing the attributes used in theKM, grouped by Monitor Types, and provides a brief description of each attribute and its defaultsettings.

Monitor Types

Tivoli Storage Manager KM

TSM Automatic Drive

TSM Automatic Library

TSM Client

TSM Daemon

TSM Database

TSM Domain

TSM Domain Client Node

TSM Job

TSM Jobs

TSM Log

TSM Manual Drive

TSM Mount Request

TSM Process

TSM Storage Pool

Baselines and Key Performance Indicators

Some attributes are identified by default as Key Performance Indicators (KPIs) and thereforeautomatically included in the base lining calculation. To learn more about auto baselining and KPIs,please refer to the Managing Baselines and Key Performance Indicators chapter.

In this guide, attributes flagged as KPIs are respectively identified by the following icon: .

63

Version 2.7.00


Tivoli Storage Manager KM

Attributes

Name Description Units RecommendedAlert Conditions

BMC ProactiveNetAttribute Type

Login Status Monitors the status of theTSM KM login details(username/password) forthe operating system andDSMADMC.

If no valid username/password is detected forthe operating system orDSMADMC, this parameterwill be set to Failure. Ifthere are any suspiciouscommand exits, thisparameter will be set toSuspicious.

0 = Ok1 = Suspicious2 = Failure

Warning = 1Alarm = 2

Collection Status

Monitoring Mode Monitors the failover modeof the TSM KM. By defaultTSM KM runs in PermanentSingle-node Mode.

0 = PermanentSingle-nodeMode1 = TemporarySingle-nodeMode2 = ActiveMulti-nodeMode3 = PassiveMulti-nodeMode-1 = Unknown

n/a Collection Status

Node Status Monitors the errormessages generated forthe Tivoli Storage Managerapplication on themanaged system.



Availability

64Tivoli Storage Manager KM

Version 2.7.00


TSM Automated Drive

Attributes



State Displays the state of theautomated library drive.This is determined fromthe automated library drivecontrol information.

0 = Online1 = Empty2 = Loaded3 = Unloaded4 = Reserved5 =Unavailable6 = DriveOffline7 = PathOffline-1 = Unknown

none Availability

Status Monitors the status of theautomated library drive



Availability

TSM Automated Library

Attributes



State Displays whether the pathfor the automated library isonline or offline. It will notperform any remoteautomated library testcommand on the storageagent.

0 = Online 1= Offline 2 =Path Offline-1 = Unknown

none Availability

Status Monitors the status of theautomated library.



Availability

Up Drive Count Displays the number up /online state drives in thisrobotic library.

count none Statistics

Volume Count Displays the total numberof volume loaded in thisautomated library.


Volume Private Count Displays the number ofprivate volumes in theautomated library.


65TSM Automated Library

Version 2.7.00


Volume Scratch Count Displays the number ofscratch volumes in theautomated library.


Volume Scratch

Percent

Monitors the percentage ofscratch volume against thetotal number of volumeloaded in this automatedlibrary.

% none Statistics

For detailed information about KPI, see Managing Baselines and Key Performance Indicators.

TSM Client

Attributes



Last Access Elapsed

Time

Displays the time elapsedsince the lastcommunication from theclient.

hours None Statistics

Space Used Displays the amount ofspace used on the clientnode.

GB None Statistics

State Displays the state of theclient.

0 = Running1 = Locked2 = NeverCommunicated-1 = Unknown

None Availability

Status Displays the client status. 0 = Ok1 =Suspicious 2 = Failure

Warning = 1Alarm =2

Availability


TSM Daemon

Attributes



CPU Duration Displays the CPU secondsconsumed by the daemon.

seconds None Statistics

CPU Utilization Displays the percentage ofCPU used by the daemon.

% None Statistics

Memory Size Displays the core imagesize of the daemon in thevirtual memory.

KB None Statistics

66TSM Daemon

Version 2.7.00


Processes Count Displays the number ofdaemon processes/threadsfound.

processes None Statistics

State Displays the state of thedaemon as reported in thecommand executed by thedata collector.

0 = Running1 = Sleeping2 = Waiting3 = Queued4 =Intermediate5 =Terminated6 = Stopped/Disabled7 = Growing8 =Nonexistent/NotResponding9 = NotRunning-1 = Unknown

None Availability

Status Monitors the status of thedaemon.

0 = Ok1 =Suspicious 2 = Failure

None Availability


TSM Database

Attributes



Backup Elapsed * Displays the elapsed timesince the last successfuldatabase backup.


Buffer Request Count * Displays the cumulativenumber of requests fordatabase pages since thebuffer pool was last reset(or since the server waslast started).

count None Statistics

Cache Hit Percent * Displays (as a percentageof the total number ofrequests) the number ofrequests for a databasepages that are already inthe buffer pool.

% None Statistics

67TSM Database

Version 2.7.00


Cache Wait Percent * Displays (as a percentageof the total number ofrequests) the number ofrequests for databasebuffer pool pages whereno pages are available,because all pages are inuse.

% None Statistics

File System Space Used

Percent *

Monitors the percentage ofspace used by the filesystem where thedatabase resides.

% Warning: 95-98 Alarm: over 98

Statistics

Log Consumed Size* Displays the cumulativeconsumption of the logspace used by the serversince the last reset of thisparameter.

MB None Statistics

Log Pool Used Percent

*

Displays (as a percentageof all recovery log bufferpool pages) the number ofbuffer pool pages used towrite changes to therecovery log after atransaction is committed.

% None Statistics

Log Pool Wait Percent

*

Set by TSMDatabaseCollector.Displays (as a percentageof all recovery log bufferpool requests) the numberof requests for buffer poolpages where no pages areavailable because all pages

are in use.

% None Statistics

Pool Hit Percent * Displays (as a percentageof the total number ofrequests) the number ofrequests for databasepages that are already inthe buffer pool.

% None

Reorg Elapsed* Displays the elapsed timesince the last databasereorganization.


Space Available Monitors the amount ofassigned space remainingavailable for use by theserver database.

MB Warning: 2-5Alarm: less than 2

Availability

Space Changed * Displays the databasepages (in megabytes) thathave changed since thelast backup.

MB None Statistics

Space Changed

Percent *

Displays the percentage ofdatabase pages that havechanged since the lastbackup.

% None Statistics

68TSM Database

Version 2.7.00


Space Growth Rate Displays the growth rate ofthe space used by theserver database.

MB/s None Statistics

Space Max Extension Displays the maximumamount the database canbe extended by.

MB None Statistics

Space Max Reduction Displays the maximumamount the database canbe reduced by.


Statistics

Space Used Displays the amount ofassigned space used bythe server database.

MB None Statistics

Space Used Percent Monitors the percentage ofassigned space used bythe server database.

The total assigned space isthe used space (SpaceUsed) plus the availablespace (Space Available).

% None Statistics

* This parameter is only available for the server database (db).


TSM Domain

Attributes



Backup Elapsed Displays the elapsed timesince the last backup forthis domain, regardless ofcompletion status of thebackup.

hours none Statistics

Backup Throughput Displays the throughput ofthe last successful backupfor this domain.

GB/s none Statistics

Full Backup Duration Displays the duration ofthe last successful fullbackup for this domain.

seconds none Statistics

Full Backup Elapsed Displays the elapsed timesince the last successfulfull backup for thisdomain.


Full Backup Object

Count� Displays the number ofobjects backed up in thelast successful full backupfor this domain.


69TSM Domain

Version 2.7.00


Full Backup Size Displays the size of thelast successful full backupfor this domain.

GB none Statistics

Incremental Backup

Duration

Displays the duration ofthe last successfulincremental backup forthis domain.


Incremental Backup

Elapsed

Displays the elapsed timesince the last successfulincremental backup forthis domain.


Incremental Backup

Object Count

Displays the number ofobjects backed up in thelast successful incrementalbackup for this domain.


Incremental Backup

Size� Displays the size of thelast successful incrementalbackup for this domain.

GB none Statistics

State Displays the state of thedomain.

0 = Idle1 = Running2 = Running inRestrictedWindow-1 = Unknown

none Availability

Status Monitors the status of thedomain.


none Availability

Successful Backup

Elapsed

Displays the elapsed timesince the last successfulbackup for this domain.



TSM Domain Client Node

Attributes



Backup Throughput Displays the throughput ofthe last successful backupfor this client node.

MB/s none Statistics

Last Full Backup

Duration

Displays the duration ofthe last successful fullbackup for this clientnode.


70TSM Domain Client Node

Version 2.7.00


Last Full Backup Object

Count �

Displays the number ofobjects backed up in thelast successful full backupfor this client node.


Last Full Backup Size

Displays the size of thelast successful full backupfor this client node.

MB none Statistics

Last Incremental

Backup Duration

Displays the duration ofthe last successfulincremental backup forthis client node.


Last IncrementalBackup Object Count

Displays the number ofobjects backed up in thelast successful incrementalbackup for this clientnode.


Last Incremental

Backup Size

Displays the size of thelast successful incrementalbackup for this clientnode.

MB none Statistics


TSM Jobs

Attributes



Active Backup Count Displays the number ofactive backup jobscurrently discovered andmonitored.


Active Count Displays the number ofactive jobs currentlydiscovered and monitored.


Active Non-Backup

Count

Displays the number ofactive non-backup jobscurrently discovered andmonitored.



71TSM Jobs

Version 2.7.00


TSM Job

Attributes


BMC ProactiveNet

Duration Displays the duration ofthe job from the start.


Error Count Monitors the number ofclient node errors loggedin the server activity logduring this job.

count Warning when > 100 Statistics

Network Throughput Displays the throughput ofthe job on the network.


Object Count Displays the number ofobjects inspected for thisjob.


Object Expired Count Displays the total numberof objects for this job thathave expired.


Object Failed Count Displays the total numberof objects for this job thathave failed.

count Warning when > 100 Statistics

Object Processed

Count

Displays the total numberof objects for this job thathave been processed.


Object Rebound Count

� Displays the total numberof objects for this job thathave been rebound.


Object Updated Count Displays the total numberof objects for this job thathave been updated.


Size Displays the amount ofdata backed up for the job.

MB none Statistics

State Displays the state of thejob.

0 = Completed1 = Future2 = Pending

none Availability

72TSM Job

Version 2.7.00


3 = InProgress4 = Started5 = Restarted6 =Completed/Errors7 = Started/Errors8 = Restarted/Errors9 = Failed - NoRestart10 = Missed11 = Severed12 = Uncertain13 = Failed-1 = Unknown

Status Monitors the status of thejob.



Availability

Throughput Displays the throughput ofthe job.



TSM Log

Attributes



Alarm Message Count Monitors the number ofalarm messages.

count Alarm: 1 and over Statistics

File Space GrowthRate*

Displays the growth rate ofthe amount of space usedby the log file.

KB/s None Statistics

File Space Used* Displays the amount ofspace used by the log file.

KB None Statistics

File System Space Used

Percent*

Monitors the percentage ofspace used by the filesystem (where the log fileresides).

% Warning: 95-98Alarm: over 98

Statistics

Space Available* Monitors the availablespace for the log file touse (this is also theavailable space on the filesystem).


Availability

Space Used Percent* Monitors the percentage ofcapacity used by the logfile.

% Warning: 95-98Alarm: over 98

Statistics

73TSM Log

Version 2.7.00


The total capacity is theused space (Log SpaceUsed) plus available space(Log Space Available).

Warning MessageCount

Monitors the number ofwarning messages.

count Warning: over 1 Statistics

*This parameter is not available for the activity log (actlog).


TSM Manual Drive

Attributes



State Displays the state of theautomated library drive.This is determined fromthe automated librarydrive control information.

0 = Online1 = Empty2 = Loaded3 = Unloaded4 = Reserved5 =Unavailable6 = DriveOffline7 = PathOffline-1 = Unknown

none Availability

Status Monitors the status of theautomated library drive.

0 = Ok 1 = Suspicious2 = Failure


Availability

TSM Mount Request

Attributes



Elapsed Displays the elapsed timesince the mount requestwas issued.

minutes none Statistics

State Displays the state of themount request as reportedin the command executedby the data collector.

0 =Completed1 =Pending-1 = Unknown

none Availability

Status Monitors the status of themount request.



Availability

74TSM Mount Request

Version 2.7.00


Timeout Displays the timeremaining until the mountrequest times out.

minutes Alarm: 0-30 Statistics


TSM Process

Attributes



Duration Displays the duration ofthe process.


Item Count Displays the number ofitems found.


Size Displays the process size. MB none Statistics

State Displays the state of theprocess.

0 = Running1 = Running/Errors2 =Completed/Success3 = Completed/ Failure-1 = Unknown

none Availability

Status Monitors the status of theprocess



Availability

Throughput Displays the throughput ofthe process.



TSM Storage Pool

Attributes



Space Available Monitors the availablevolume space for thebackup data to use in thisstorage pool.

GB Warning < 1Alarm = 0

Availability

Space Growth Rate Displays the growth rate ofthe total volume spaceused by the backup datain this storage pool.

GB/s None Statistics

75TSM Storage Pool

Version 2.7.00


Space Logical Percent Displays the logicaloccupancy of the storagepool as a percentage ofthe total occupancy.

% None Statistics

Space Migrated Displays the amount ofdata that has beenmigrated, if migration is inprogress. If migration isnot in progress, this valueindicates the amount ofdata migrated during thelast migration.

GB None Statistics

Space Migration

Percent

Displays an estimate of thepercentage of data in thestorage pool that can bemigrated.

% None Statistics

Space Migration

Elapsed � Displays the amount oftime that has elapsedsince migration of thestorage pool began, ifmigration is active. Ifmigration is not active, thisvalue indicates the amountof time required tocomplete the lastmigration.

seconds None Statistics

Space Reclaimable Displays the amount ofspace in the storage poolthat is reclaimable.

GB None Statistics

Space Reclaimable

Percent

Displays the amount ofreclaimable space as apercentage of the totalstorage pool space.

% None Statistics

Space Used Displays the total volumespace occupied by thebackup data in this storagepool.

GB None Statistics

Space Used Percent Monitors the percentage oftotal occupied volumespace against the totalvolume capacity of thisstorage pool (not includingany scratch volumes).

% Warning: over 95Alarm: over 98

Statistics

Volumes Active Count Displays the number ofactive volumes in thisstorage pool.

Active volumes areavailable disk volumeswith a status of "Online" ortape volumes with a statusof "Filling", where data hasbeen written but thevolume is not yet full.


Volume Active Percent Monitors the percentage ofactive volumes against thetotal number of volumes inthis storage pool.

% None Statistics

76TSM Storage Pool

Version 2.7.00


Volume Available

Count

Displays the number ofvolumes assigned to thisstorage pool.


Volume Available

Percent

Monitors the percentage ofavailable volumes againstthe total number ofvolumes in this storagepool.

% None Statistics

Volume Count Displays the total numberof volumes in this storagepool.


Volume Empty Count Displays the number ofempty volumes in thisstorage pool.

Empty is a possible statusfor a tape volume,indicating that no data isstored on that volume.


Volume Full Count Displays the number of fullvolumes in this storagepool.


Volume Full Percent Monitors the percentage offull volumes against thetotal number of volumes inthis storage pool.

% None Statistics

Volume Offline Count Displays the number ofoffline volumes in thisstorage pool.

"Offline" is a possiblestatus for a disk volume.


Volume Pending Count Displays the number ofpending volumes in thisstorage pool.

"Pending" is a possiblestatus for a tape volume,where all files have beendeleted but a delay hasbeen placed on the volumebefore reuse.



Index 77

Version 2.7.00


Index

- A -Abnormalities 59

Access

Permissions 11

User 11Add Monitor Types 27

Attribute 57, 58

Attributes

Active Backup Count 70

Active Count 70

Active Non-Backup Count 70

Alarm Message Count 72

Backup Elapsed 66, 68

Backup Throughput 68, 69

Buffer Request Count 66

Cache Hit Percent 66

Cache Wait Percent 66

CPU Duration 65

CPU Utilization 65

Duration 71, 74

Elapsed 73

Error Count 71

File Space Growth Rate 72

File Space Used 72

File System Space Used Percent 66, 72

Full Backup Duration 68

Full Backup Elapsed 68

Full Backup Object Count 68

Full Backup Size 68

Incremental Backup Duration 68

Incremental Backup Elapsed 68

Incremental Backup Object Count 68

Incremental Backup Size 68

Item Count 74

Last Access Elapsed Time 65

Last Full Backup Duration 69

Last Full Backup Object Count 69

Last Full Backup Size 69

Last Incremental Backup Duration 69

Last Incremental Backup Object Count 69

Last Incremental Backup Size 69

Log Consumed Size 66

Log Pool User Percent 66

Log Pool Wait Percent 66

Login Status 63

Memory Size 65

Monitoring Mode 63

Network Throughput 71

Node Status 63

Object Count 71

Object Expired Count 71

Object Failed Count 71

Object Processed Count 71

Object Rebound Count 71

Object Updated Count 71

Pool Hit Percent 66

Processes Count 65

Reorg Elapsed 66

Size 71, 74

Space Available 66, 72, 74

Space Changed 66

Space Changed Percent 66

Space Growth Rate 66, 74

Space Logical Percent 74

Space Max Extension 66

Space Max Reduction 66

Space Migrated 74

Space Migration Elapsed 74

Space Migration Percent 74

Space Reclaimable 74

Space Reclaimable Percent 74

Space Used 65, 66, 74

Space Used Percent 66, 72, 74

State 64, 65, 68, 71, 73, 74

Status 64, 65, 68, 71, 73, 74

Successful Backup Elapsed 68

Throughput 71, 74

Timeout 73

Up Drive Count 64

Volume Active Percent 74

Volume Available Count 74

Volume Available Percent 74

Volume Count 64, 74

Volume Empty Count 74

Volume Full Count 74

Volume Full Percent 74

Volume Offline Count 74

Volume Pending Count 74

Volume Private Count 64

Volume Scratch Count 64

Volume Scratch Percent 64

Index 78

Version 2.7.00


Attributes

Volumes Active Count 74

Warning Message Count 72Automated Drives

Debug 31Automated Libraries

Debug 31

- B -Baseline 62

Baselines

BMC ProactiveNet Performance Management 59

Generation 59

Manage 59

Requirements 59BMC PATROL

Changes 10BMC ProactiveNet Performance Management

Abnormalities 59

Baselines 59

Key Performance Indicators 59

KPI 59Business Value 9

- C -Client

Maximum Instances 35Clients

Debug 31Cluster Application 38

Component

folders 54Component Installation package

creating 20

downloading 23

editing 22Configure

Domains 49

Hostname 47

Jobs 47

Maximum Instances 35

Monitoring Duration 47

Mount Request 48

Multi-node monitoring mode 38

Overrides 43

Processes 50Configuring

monitor settings 27

- D -Daemon

Maximum Instances 35Daemons

Debug 31Database

Maximum Instances 35Databases

Debug 31Debug

Automated Drives 31

Automated Libraries 31

Clients 31

Daemons 31

Databases 31

Directory Path 31

Domains 31

End Time 31

Jobs 31

Logs 31

Mount Requests 31

Processes 31

Server 31

Storage Pools 31Disk Pool

Maximum Instances 35Disk Storage

Maximum Instances 35Disk Volume

Maximum Instances 35Domains

Configure 49

Debug 31Downloading 23

Duration

Duration 48, 50

Monitoring 48, 50

- E -Event

collectors 54

folders 54

Index 79

Version 2.7.00


- F -Failover Group Name 38

Features 9

Filtering Options

TSM Automated Drive 46

TSM Automated Library 46

TSM Client 46

TSM Daemon 46

TSM Domain 46

TSM Domain Client Node 46

TSM Manual Drive 46

TSM Storage Pool 46Filters



TSM Client 46

TSM Daemon 46

TSM Domain 46

TSM Domain Client Node 46

TSM Manual Drive 46

TSM Storage Pool 46

- G -Generate

Baselines 59Goals 9

Graphs 57, 58

- I -Information

Closed 58

Enabled 58

Open 58

Source Agent 58Installation 19

configuring 25Installing

Preparation 19Instances

Client 35

Configure 35

Daemon 35

Database 35

Disk Pool 35

Disk Storage 35

Disk Volume 35

Job 35

Log 35

Maximum 35

Mount Request 35

Policy 35

Policy Client 35

Robotic Drive 35

Robotic Library 35

Standalone Drive 35

Volume Pool 35

- J -Job

Maximum Instances 35Jobs

Active 47

Configure 47

Debug 31

Monitoring 47

- K -Key Concepts 9



Manage 59KPI 62


Manage 59

- L -Log

Maximum Instances 35Logs

Debug 31

- M -Manage

Baselines 59

Index 80

Version 2.7.00


Manage


KPI 59Monitor

name 58

type 58Monitor Settings

configuring 27Monitor Types

Tivoli Storage Manager KM 62, 63



TSM Automatic Drive 62

TSM Automatic Library 62

TSM Client 62, 65

TSM Daemon 62, 65

TSM Database 62, 66

TSM Domain 62, 68

TSM Domain Client Node 62, 69

TSM Job 62, 71

TSM Jobs 62, 70

TSM Log 62, 72

TSM Manual Drive 62, 73

TSM Mount Request 62, 73

TSM Process 62, 74

TSM Storage Pool 62, 74Monitoring

Configure 48, 50

Duration 48, 50Monitoring Duration

Jobs 47Monitoring Node Names 38

Mount Request

Configure 48


Monitoring Duration 48Mount Requests

Debug 31Multi-node monitoring mode

Configure 38

- N -Navigation

drawers 54

tree 54

- O -Operations Console views

Event 54

Grid 54

Title 54

Tree/Graph 54Overrides

Configure 43

TSM Server Discovery 43

- P -Package 20, 22, 23

PATROL Configuration Manager 17

Policies

Manage 26Policy

Maximum Instances 35Policy Client

Maximum Instances 35Process

Configure 50

Monitoring Duration 50Processes

Debug 31

- R -Reference Guide 62

Remote PATROL Agent Checking 38

Requirements

Security 11

Software 10

System 10Robotic Drive

Maximum Instances 35Robotic Library


- S -Security

Requirements 11Server

Debug 31

Index 81

Version 2.7.00


Software

Requirements 10Standalone Drive

Maximum Instances 35Storage Pools

Debug 31Sudo 11, 29

System

Requirements 10

- T -Tags 17

Thresholds

modifications 59Tivoli Storage Manager

Changes 10TSM Server Discovery

Overrides 43

- U -UNIX 29

User Account

Configure 29

patrol 29

Privileges 29

Sudo 29

- V -Volume Pool


- W -Windows 29

About BMC® SoftwareBMC Software, Inc. NYSE:BMC, is a leading provider of enterprise management solutionsthat empower companies to manage their IT infrastructure from a business perspective.Delivering Business Service Management, BMC Software solutions span enterprisesystems, applications, databases, and service management. Founded in 1980, BMCSoftware has offices worldwide and fiscal 2004 revenues of more than $1.4 billion. For

more information about BMC Software, visit www.bmc.com.

About Sentry Software™Sentry Software, a strategic Technology Alliance Partner of BMC Software, provides keymonitoring solutions specifically designed to expand the capabilities of BMCPerformance Manager, thus enabling up to 100% coverage of any infrastructure. SentrySoftware specializes in single solutions for multi-platform monitoring of hardware,custom applications or any IT component, and blackout windows. Sentry Softwareproducts are deployed in 45 countries across the globe and lead the list of BMCSoftware’s third-party product sales. For more information about Sentry Software,

please visit www.sentrysoftware.net.

BMC ProactiveNet - Tivoli Storage Manager Storage · PDF fileConfiguring the TSM Server...

Documents

Transcript of BMC ProactiveNet - Tivoli Storage Manager Storage · PDF fileConfiguring the TSM Server...