BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring

Transcription

1 USER DOCUMENTATION STORAGE MONITORING BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring Version January 2017

2 Contacting BMC Software You can access the BMC Software Web site at From this Web site, you can obtain information about the company, its products, corporate offices, special events, and career opportunities. United States and Canada Address BMC Software, Inc CityWest Blvd. Houston TX Telephone 1 (713) or 1 (800) (Toll Free) Copyright 2015 BMC Software, Inc. or licensors, as an unpublished work. All rights reserved. All other trademarks belong to their respective companies. BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices included in this documentation. Restricted Rights Legend U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section , DFARS , DFARS , DFARS , and DFARS , as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101 CityWest Blvd., Houston, TX , USA. Any contract notices should be sent to this address. 2 BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software, Inc.

3 Customer Support You can obtain technical support by using the Support page on the BMC Software Web site or by contacting Customer Support by telephone or . Support Web Site Read overviews about support services and programs that BMC Software offers Find the most current information about BMC Software products Search a database for problems similar to yours and possible solutions Order or download product documentation Report a problem or ask a question Subscribe to receive notices when new product versions are released Find worldwide BMC Software support center locations and contact information, including addresses, fax numbers, and telephone numbers You can also access product documents and search the Knowledge Base for help with an issue at Support by Telephone or In the United States and Canada, if you need technical support and do not have access to the Web, call Outside the United States and Canada, please contact your local support center for assistance. To find telephone and contact information for the BMC Software support center that services your location, refer to the Contact Customer Support section of the Support page on the BMC Software Web site at 3 You can obtain technical support from BMC Software 24 hours a day, 7 days a week at From this Web site, you can:

4 Table of Contents...9 User Goals and Features...10 Business Value...11 Requirements...11 System Requirements...11 Software Requirements...13 Security Requirements Disk...18 Space Requirements...18 Remote Monitoring Requirements...22 Importing the Monitoring Solution into Central Administration...23 Creating the Installation Package...24 Downloading the Installation Package...24 Installing the Package...27 Configuring Monitor Settings Configuring Tivoli Storage Manager Servers Monitoring Configuring the User Account Configuring Advanced Settings...33 Configuring TSM Server Discovery Overrides (Optional)...35 Configuring Remote Connection Settings...36 Configuring the Maximum Number of Instances...38 Configuring the Multi-Node Monitoring Mode...42 Enabling the Debug Mode...45 Configuring Other Monitor Types...45 Configuring Automated Drives...46 Configuring Automated Libraries...47 Configuring Clients...48 Configuring Daemons...49 Configuring Domains...50 Configuring Domain Client Nodes...51 Configuring Jobs...52 Configuring Logs...53 Configuring Manual Drives Configuring the Tivoli Storage Manager Solution

5 ...54 Configuring Mount Requests...55 Configuring Processes...56 Configuring Storage Pools...61 Tivoli Storage Manager KM...62 TSM Clients...63 TSM Client...64 TSM Daemons...65 TSM Daemon...67 TSM Databases...68 TSM Database...71 TSM Logs...72 TSM Log...73 TSM Domains...74 TSM Domain...76 TSM Jobs...78 TSM Job...80 TSM Mount Requests...81 TSM Mount Request...82 TSM Automated Libraries...83 TSM Automated Library...84 TSM Manual Drive...85 TSM Automated Drives...86 TSM Automated Drive...87 TSM Domain Client Node...88 TSM Storage Pools...89 TSM Storage Pool...93 TSM Processes...94 TSM Process...95 Managing Baselines and Key Performance Indicators Filtering Elements to Monitor

6 Release Notes for v3.0.00

7 What's New TSM-14: BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring now supports multiple TSM server monitoring on local and remote hosts. Changes and Improvements TSM-14: The overall performance of the Tivoli Storage Manager KM has been significantly improved. TSM-155: Tivoli Storage Manager KM now fully supports the monitoring of libraries controlled by ACSLS (StorageTek Automated Cartridge System Library Software). TSM-371: Tivoli Storage Manager KM has been improved to support all PATROL Agent v10+ versions and prevent failures due to a compatibility error. Fixed Issues TSM-380: The default actlog query limit has been modified to allow querying all actlog messages since the last collection cycle (default: 300 minutes). 7

8 Key Concepts

9 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 TrueSight Operations Management - Tivoli Storage Manager Monitoring, may also be made as Tivoli Storage Manager KM. User Goals and Features 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 space reclamations. Server database and recovery logs: database and file system utilization, cache and buffer performance, 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 volumes loaded, etc. Client: working status. 9 Tivoli Storage Manager KM enables you to monitor the following in your environment:

10 Business Value BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring provides current and historical information through a centralized console so you can easily view and manage your entire Tivoli Storage Manager environment. The product collects and brings critical performance data and useful metrics into the BMC TrueSight Operations Management environment and enables SAN Administrators to be warned whenever a problem occurs in their Tivoli Storage Manager environment. BMC TrueSight Operations 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. User Goals and Features 10

11 Requirements Before installing the Tivoli Storage Manager KM, verify the: software requirements system requirements security requirements remote monitoring requirements. Operating System Operating System Version Sun microsystems Solaris TM 8, 9, 10, 11 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, 2012 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, 7.1.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, 6.4.x, 7.1.x BMC Software PATROL Agent , 3.5.x, 3.6.x, 3.7.x, 3.8.x, 3.9.x, 9.x, 10.x BMC ProactiveNet Performance Manager 8.x, 8.5.x, 8.6.x, 9.x BMC TrueSight Operations Management 10.x Java 1.6 or higher 11 Business Value System Requirements

12 If you're running the Tivoli Storage Manager KM on LINUX, or Microsoft Windows x64 managed nodes, please verify these additional software requirements: Purpose Software Version When running Tivoli Storage Manager KM with sudo user account on Solaris, HP-UX, AIX or Linux managed nodes Sudo (superuser do) or later When running Tivoli Storage Manager KM on AIX managed nodes Default ncargs value for processing bpdbjobs output may not be sufficient. Any Check this attribute using: lsattr -EH -l sys0 grep ncargs When running Tivoli Storage Manager KM on Linux managed nodes Korn shell binary (/bin/ksh) Alternatively a soft link from bin/ksh to /bin/bash will be needed. Any When running Tivoli Storage Manager KM on Microsoft Windows x64 managed nodes Reg.exe patch KB ( kb/948698) Any The Microsoft Windows x64 Reg.exe patch, KB is required to allow access to 64-bit registry keys from PATROL Agent. Access the above patch site from the managed node to obtain the correct patch for that platform. To support bash shell platforms when ksh is not installed To collect TSM stats when ksh was not installed on UNIX/Linux servers, you need to create a soft link for /bin/ksh to /bin/bash: ln s Requirements /bin/bash /bin/ksh 12 If the value is below 16, increase it using: chdev -l sys0 -a ncargs=16

13 Security Requirements A user account with administrative privileges must be configured in BMC PATROL to read and execute Tivoli Storage Manager application programs and access file systems. Depending on the operating 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 execute application programs and access file systems a non-root account, such as patrol, configured in Tivoli Storage Manager application to administer the Tivoli Storage Manager application. On Windows platforms: an administrator user a non-administrator account, such as patrol, configured in Tivoli Storage Manager application to administer the Tivoli Storage Manager application. Access Permissions The Tivoli Storage Manager KM user needs read & execute permission to executable and library files 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:\Program Files \Tivoli\TSM (on Microsoft Windows). 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 13 Requirements The user login details are configured in the KM. The password is stored in the PATROL Agent in a DES encrypted format.

14 If the KM is enabled to failover in a clustered environment, the login user needs execute permissions to 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 PATROL Agent user and the Tivoli Storage Manager KM user. These scripts are stored under KM_HOME path, normally PATROL_HOME/lib/TSM. To list all OS commands used by the Tivoli Storage Manager KM, execute the following PSL code from the PATROL Console, using PSL Task menu, after installing and loading the KM. 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,fields,"/"),met,cmd); } } if((osp!="windows") && sudoers) { printf("\n\ncommands used with sudo:\n%s",sort(sudoers)); } Requirements 14 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(osp=="") { osp=trim(nthargf(grep("osplatform",ctl),"2-","=","="), " "); } fields=lines(ntharg(var,"1-","/")); old_host=host; host=(fields == 5)? ntharg(var,"3","/") : "localhost"; if(host!=old_host) { if((osp!="windows") && sudoers) { printf("\n\ncommands used with sudo:\n%s",sort(sudoers)); } printf("\n\non %s:\n\n", host); i=0; sudoers=""; osp=""; }

15 The PATROL Agent user (normally patrol) requires write permission to DSM_LOG directory and dsmerror.log file. For all other paths and files listed in the table below the PATROL Agent user needs read & execute permission. 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_TEMP path using the configured KM login account, and processed by the PATROL Agent user. On completion the copied log file will be removed. This may increase the file system usage under KM_TEMP temporarily during this activity. The configured login user should have sufficient privileges to run regedit command on the managed node. Sudo User for Operating System Access If a non-root user with sudo privileges is preferred as the Tivoli Storage Manager KM user, configure the account as a sudoer through the visudo utility using code appropriate for your platform as detailed 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 KM administration and report menu commands using their sudo privileges. The Tivoli Storage Manager KM accepts any non-root user with the following sudo configuration in the sudoers file. Please replace user1, 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 and PATROL_HOME is the path where the PATROL Agent is installed (including the target, like / opt/bmc/patrol3/solaris29-sun4/). 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 configured differently, the KM may run sudo commands using incorrect sudo settings, which may expose the sudo user password. 15 Requirements On Windows platforms the Tivoli Storage Manager installation is identified by checking the registry sub-keys under HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\.

16 On Solaris: User_Alias TSMKMUSERS = user1, user2, user3 Defaults:TSMKMUSERS!lecture,!authenticate,!requiretty,\ env_keep+="path LD_LIBRARY_PATH INSTALL_PATH KM_HOME KM_TEMP \ DSM_CONFIG DSM_DIR DSM_LOG",env_reset TSMKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\ INSTALL_PATH/server/bin/*,\ INSTALL_PATH/client/ba/bin/*,\ PATROL_HOME/lib/TSM/*,PATROL_HOME/bin/* env_keep+="path LD_LIBRARY_PATH INSTALL_PATH KM_HOME KM_TEMP \DSM_CONFIG DSM_DIR DSM_LOG",env_reset user1, user2, user3 must be replaced with username(s) used by the KM; INSTALL_PATH and PATROL_HOME with the relevant paths. On HP-UX: user1, user2, user3 must be replaced with username(s) used by the KM; INSTALL_PATH and PATROL_HOME with the relevant paths. On AIX & Linux: User_Alias TSMKMUSERS = user1, user2, user3 Defaults:TSMKMUSERS!lecture,!authenticate,!requiretty,\ env_keep+="path LD_LIBRARY_PATH INSTALL_PATH KM_HOME KM_TEMP \ DSM_CONFIG DSM_DIR DSM_LOG",env_reset 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 the relevant paths. Admin Interface User Access BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring requires that an administrator account (standard administrator with no other privileges) be added to the Tivoli Storage Manager server for use by PATROL and the Tivoli Storage Manager KM. Requirements 16 User_Alias TSMKMUSERS = user1, user2, user3 Defaults:TSMKMUSERS!lecture,!authenticate,!requiretty,\ env_keep+="path LD_LIBRARY_PATH INSTALL_PATH KM_HOME KM_TEMP \ DSM_CONFIG DSM_DIR DSM_LOG",env_reset TSMKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\ INSTALL_PATH/server/bin/*,\ INSTALL_PATH/client/ba/bin/*,\ PATROL_HOME/lib/TSM/*,PATROL_HOME/bin/*

17 This account is used to query the configuration details and resource utilization of the server through the Tivoli Storage Manager Administrative Client interface (DSMADMC). No changes are made by this user 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 the configuration procedure described in Configuring the KM User Accounts. Alternatively, the user account can be set up directly in TSM Server, and the details simply entered during KM configuration in the same way that the OS login details are entered. The password is stored in the PATROL Agent in an encrypted format. DSMADMC command binary is executed using an OS user account matching the the DSMADMC login. If this account does not exists, the PATROL Agent user account will be used. Therefore it is recommended to create an operating system user account matching the DSMADMC username with the same password to avoid invalid user login attempts and to improve the performance. This 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 write permission to DSM_LOG path and dsmerror.log file. To list all DSMADMC commands used by the Tivoli Storage Manager KM, execute the following PSL code 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-"," ="); if(typ!= "DSMADMC") { next; } fields=lines(ntharg(var,"1-","/")); old_host=host; host=(fields == 5)? ntharg(var,"3","/") : "localhost"; if(host!=old_host) { printf("\n\non %s:\n\n", host); i=0; } cmd=nthargf(grep("commandtext",ctl),"2-","=","="); printf("(%2d) %-25s: %s\n",i++,ntharg(var,fields,"/"),cmd); } 17 Requirements

18 Disk Space Requirements BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring requires approximately: 1.5 MBytes disk space on each monitored PATROL Agent system 2.5 MBytes disk space on each PATROL Console system 600 KBytes disk space on each PATROL Central Console Server system 1.4 MBytes disk space on each PATROL Central Web Server system The Tivoli Storage Manager KM is installed under the PATROL installation path. During execution, the Tivoli Storage Manager KM creates and maintains temporary files under KM_HOME, KM_TEMP and KM_DEBUG paths. By default they are all under PATROL_HOME/lib/ TSM, where PATROL_HOME path is normally /opt/bmc/patrol3/ (on Unix) or C:\Program Files (x86)\bmc Software\Patrol3\ (on Microsoft Windows). Please make sure you have sufficient space under KM_TEMP and KM_DEBUG paths. If the location of the KM_TEMP or KM_DEBUG is not suitable, it can be changed using the Configuration > Paths menu from the main instance. These folder should have read, write and execute permissions for both the PATROL Agent user and the KM login user. Remote Monitoring Requirements Remote monitoring is required for all servers on which no PATROL Agent can be installed. This feature is also interesting if you lack resources or time to deploy a PATROL Agent and Tivoli Storage Manager KM on several servers since it allows to monitor multiple hosts from one PATROL Agent. Remote monitoring is not possible from a UNIX/Linux PATROL Agent system to a Windows-based TSM server. The requirements listed below must be met to be able to use remote monitoring. Requirements 18 When monitoring a standard installation of Tivoli Storage Manager, the PATROL Agent will generate approximately 500 KBytes of history data per day. An enterprise installation of Tivoli Storage Manager on a server with multiple storage agents, clients, automated libraries, and manual drives will generate more history data (as per other KMs used by the PATROL Agent). These history data files are recycled by PATROL depending on the PATROL Agent history retention period.

19 JAVA BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring requires Java 1.6 or higher and a Java Runtime Environment (JRE) to be installed on the same system that runs the PATROL Agent. The solution will automatically detect the JRE path if it has been installed in the default location or under the BMC PATROL Agent installation path. If it has been installed in a different location, you will have to set it to the PATH for the PATROL Agent default account before starting the PATROL Agent. You can download the Java Runtime Environment along with the KM on the Sentry Software Web site. SSH/WMI Connection Disabling the SSH Host Key Authentication SSH host key authentication is enabled by default on most TSM servers. To disable it: 1. Open the global SSH configuration file (ssh_config) stored in the /etc/ssh/ directory on the remote host 2. Add the line StrictHostKeyChecking no 3. Save the file. 19 Requirements An SSH (UNIX/Linux platforms) or a WMI (Windows platforms) connection is required to monitor remote TSM servers. When using an SSH connection, the SSH host key authentication must be disabled on the remote host.

20 Installing the Monitoring Solution

21 Once the latest version of the solution has been loaded into Central Monitoring Administration, administrators can create all the installation packages required for their different operating systems and platforms and save them for later use in the Monitoring Installation Packages list. These packages can then be deployed to multiple computers. Administrators just have to connect to TrueSight Operations Management from the server where they want to install the package, download it and launch the installation. This section describes the different steps to follow to install Tivoli Storage Manager KM: Importing Tivoli Storage Manager KM into Central Monitoring Administration Creating the Installation Package Downloading the Installation Package Installing the Package 21

22 Importing the Monitoring Solution into Central Administration The TrueSight Central Monitoring Repository includes the current versions of BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring that you can use with BMC TrueSight. If the version available in the Repository does not correspond to the latest one, you will have to manually import it: Log on to the BMC TrueSight Operations Management Console. Launch Central Monitoring Administration. Click the Repository drawer and select Manage Repository. Check that the version of the BMC component available is actually the latest one. If not, download the latest version corresponding to your operating system (Windows or UNIX/ Linux) available on the Sentry Software Website. From TrueSight Operations Management, click Import. Select Single solution. Browse to the.zip source file. Click Import. The selected archive file is imported to the repository. 22

23 Creating the Installation Package The installation package to deploy to managed systems can be created directly from TrueSight Operations Management: Log on to TrueSight Operations Management Click the Repository drawer and select Deployable Package Repository. Click Add. Select the operating system and platform for which you want to create a package. The components available in the repository for the selected operating system and platform are displayed. Select the Installation Package Component: From the Available components list, select the relevant component. From the Version list, select the latest version. Click the right arrow button to move the component into the Selected Components list. By default, the appropriate BMC PATROL Agent for the operating system and platform that you chose is included in the Selected components list. Click Next. The Add Component Installation Package wizard are displayed. Go through the wizard and specify the required PATROL information. The Installation Package Details is displayed. Verify that: the operating system and platform are correct the components that you want to include are listed in the Included Components list. Provide the following information: 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 Monitoring Repository window. Format: Select a file compression format for the package. Click Save Installation Package. Click Close. The package is now available in the Monitoring Installation Packages list. 23 Importing the Monitoring Solution into Central Administration

24 Downloading the Installation Package You can download an installation package and install the components on one or more hosts. The installation runs silently with the information entered during package creation. Recommendation If you defined the BMC TrueSight Integration Service variable for PATROL Agents in the installation package, ensure the agents are started in phases. Do not start newly deployed agents all at once. Start and configure monitoring for the agents in planned phases to reduce the performance impact on the Integration Service nodes and on the BMC TrueSight Server associated with the automatic workflow process. Installing the Package This chapter provides a step by step procedure to install a monitoring solution package: 1. From the computer on which you want to install the package, log on to TrueSight Operations Management. 2. (Optional) To filter the list of installation packages, select an operating system from the Filter by 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 in a temporary file. 5. Extract the installation package that is appropriate for your operating system. The package is extracted 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 agent sends a configuration request by passing its tags to Central Monitoring Administration, via the Integration Service. Central Monitoring Administration evaluates policies that match the tags, determines the final configuration to be applied, and sends the configuration information back to the agent. Monitoring is based on the configuration information received by the agent. Creating the Installation Package Log on to TrueSight Operations Management from the computer on which the PATROL Agent is installed or to be installed. 2. Click the Repository drawer and select Deployable Package Repository. 3. (Optional) To filter the list of installation packages, select an operating system from the Filter by Operating System list. 4. Click the link for the installation package that you want to download. 5. Through the browser's download dialog box, save the installation package.

25 Configuring After Installation

26 You configure monitoring of Tivoli Storage Manager KM when you create a policy. A policy is a template containing the configuration of a PATROL Agent. A policy can be assigned to one or more PATROL Agents using a unique tag (Central Monitoring Administration tag), and a PATROL Agent can be assigned one or more policies with different priorities. If you have not already added the Central Monitoring Administration tag to your PATROL Agents during the solution installation, then you must manually assign the tag after you have configured the policy. For details, see Adding Central Monitoring Administration Tags. 26

27 Configuring Monitor Settings When you create a policy, you can configure monitor types. The Add Monitor Types dialog box presents configuration fields for compatible BMC PATROL monitoring solutions that are located in the Central Monitoring Repository. To configure the Monitor Type settings To add a monitor type: Log on to Central Monitoring Administration. In the Navigation pane, click the Policies drawer and select a policy view (e.g. All). Click Add. Configure the policy general settings and click Next. In the Monitoring Policy Configuration window, click Add. From the Monitoring Solution menu, select Tivoli Storage Manager. From the Version menu, select the required version

28 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 Enables access to the filtering options to select the automated drives elements that will be monitored. TSM Automated Library Enables access to the filtering options to select the automated libraries elements that will be monitored. TSM Client Enables access to the filtering options to select the clients elements that will be monitored. TSM Daemon Enables access to the filtering options to select the daemons elements that will be monitored. TSM Domain To: enable access to the filtering options to select the domains elements that will be monitored set backup restrictions. TSM Domain Client Node Enables access to the filtering options to select the domain client nodes elements that will be monitored. 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 Enables access to the filtering options to select the manual drives elements that will be monitored. 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 Enables access to the filtering options to select the storage pools elements that will be monitored. Configuring Monitor Settings From the Monitor Type menu, select the required monitor:

29 Configuring the Tivoli Storage Manager Solution Before using Tivoli Storage Manager KM, you'll have to configure its general settings. This section will learn you how to: Specify the Tivoly Storage Manager servers to be monitored. Configure the user account. Configure the remote connection settings. Possibly configure the advanced settings (Discovery Overrides, debug mode, number of instances, and multi-node monitoring mode). 29 Configuring Monitor Settings

30 1. Configuring Tivoli Storage Manager Servers Monitoring To specify the remote or local Tivoli Storage Manager server or the Tivoli Storage Manager appliance to be monitored: 1. Create a new monitor type. 2. From the Monitor Type menu, select Tivoli Storage Manager KM. 3. In the TSM Server section: Enter the TSM server instance ID for the Tivoli Storage Manager server instance Enter the Hostname, IP Address, or FQDN of the Tivoli Storage Manager server to be monitored Specify whether the Tivoli Storage Manager server is a UNIX/Linux or Windows system Check Create a Device in the Console if you want the Tivoli Storage Manager server to appear as a separate device in TrueSight OM 4. You will then have to configure the user account to be used. Configuring Monitor Settings 30 TSM Server Configuration

31 2. Configuring the User Account An operating system login as well as a TSM Admin Client login must be configured in BMC TrueSight Operations Management to monitor a Tivoli Storage Manager server. Refer to the Security Requirements chapter for detailed information about login requirement. 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 execute application programs and access file systems a non-root account, such as patrol, configured in the Tivoli Storage Manager application to administer the Tivoli Storage Manager application. On Windows platforms, you can use the following user accounts: an administrator user a non-administrator account, such as patrol, configured in the Tivoli Storage Manager application to administer the Tivoli Storage Manager application. 31 Configuring Monitor Settings

32 To configure the user account 3. To use: 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 the sudo binary file path (by default: /usr/local/bin/sudo) 4. (UNIX Only) If the user account has sudo privileges, check the Use Sudo box and indicate the sudo binary file path (by default: /usr/local/bin/sudo). 5. Specify the TSM Admin Client User ID and Password. 6. Indicate the DSMADMC file path on the PATROL Agent system. By default, the solution searches for the default TSM Backup Admin Client installation path. 7. Click Add to List. 8. (Optional) You can now configure advanced settings. Configuring Monitor Settings Specify the Tivoli Storage Manager Server to be monitored 2. Locate the TSM Credentials section:

33 3. Configuring Advanced Settings Once the Tivoli Storage Manager server to be monitored and the account to be used are specified, you can configure the following advanced settings: The TSM server discovery overrides The remote connection settings The maximum number of instances The multi-node monitoring mode The debug mode Configuring TSM Server Discovery Overrides (Optional) The solution automatically discovers the Tivoli Storage Manager installation path, the DSM_DIR and DSM_LOG directory paths, the DSM_CONFIG file path, the temporary directory path used by Tivoli Storage Manager KM, the node type, and the node status. This information can however be overridden. To configure TSM server discovery overrides 1. Specify the Tivoli Storage Manager server to be monitored and the user account to be used. 2. In the Advanced Settings section, click the Discovery Overrides button. Accessing Advanced Settings 33 Configuring Monitor Settings

34 Configuring Discovery Overrides Options 4. Provide the following information: the TSM Installation path the DSM_DIR Directory path the DSM_CONFIG File path the DSM_LOG Directory path the Remote Temp Directory path the Local Temp Directory path The DSM_CONFIG file will contain the.opt file that specifies the TSM server instance ID and the required connection setting used by the TSM Admin Client to connect to the TSM server instance. 5. Configure the Node Type: Select the the Node Type (Server or Storage Agent). 6. Provide the Node Status Alarms and Warnings: Enter the regular expressions to determine the Node Status in Alarm or Warning status. This regular expression will be used on the result from DSMADMC command: "query status" on the TSM server. 7. Click Close. Configuring Monitor Settings The Discovery Overrides dialog is displayed.

35 Configuring Remote Connection Settings If you configured the monitoring of a remote host, you may want to specify the time after which the connection to the remote node will timeout or the maximum number of simultaneous connections allowed to the remote node. This configuration is possible through the Advanced Settings options. To configure the remote connection settings 1. Specify the Tivoli Storage Manager server to be monitored and the user account to be used. 2. In the Advanced Settings section, click the Advanced button. Accessing Advanced Settings 3. The Advanced dialog is displayed. Advanced Settings Options 35 Configuring Monitor Settings

36 4. In the Remote Connection Settings section, click Connection Settings. 5. Provide the required values: Configuring Connection Settings Remote monitoring cannot be performed from UNIX/Linux PATROL Agent to Windows TSM server. Configuring the Maximum Number of Instances By default, the solution monitors all the elements discovered, which may represent an important workload to the agents and servers. Because the monitoring of some elements may be irrelevant for various reasons, you can configure the maximum number of instances to be monitored. Because increasing the number of instances may impact the performance of the solution, it is recommended to only monitor critical elements in large environments. To configure the maximum number of instances 1. Specify the Tivoli Storage Manager server to be monitored and the user account to be used. 2. In the Advanced Settings section, click the Advanced button. Accessing Advanced Settings Configuring Monitor Settings 36 Connection Timeout (in Seconds): Enter the number of seconds after which the connection to the remote node will timeout. Maximum Connections: Enter the maximum number of simultaneous connections allowed to the remote node. 6. Click Close on all pop-ups. 7. Click Add to List in the main window.

37 3. The Advanced dialog is displayed. Advanced Settings Options 37 Configuring Monitor Settings

38 Configuring Maximum Number of Instances 6. Enter 0 in the relevant field to disable the monitoring of a specific element. 7. Click Close on all pop-ups. 8. Click Add to List in the main window. Configuring the Multi-Node Monitoring Mode If 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 KM must be installed on all the cluster nodes to enable continuous monitoring and avoid single point of failure. To avoid duplicate alerts from multiple nodes, it is recommended to configure the solution to operate in multi-node monitoring mode. Configuring Monitor Settings In the Maximum Number of Instances section, click Instance Max. 5. For each monitored element, indicate the maximum number of instances to be displayed:

39 To configure the multi-node monitoring mode 1. Specify the Tivoli Storage Manager server to be monitored and the user account to be used. 2. In the Advanced Settings section, click the Advanced button. Accessing Advanced Settings 3. The Advanced dialog is displayed. Advanced Settings Options 39 Configuring Monitor Settings

40 4. In the Multi-node Monitoring Mode section, click Multi-node Mode Config Configure the multi-node mode: 6. Select the appropriate Cluster Application: Veritas Cluster Server, Veritas Cluster File System, Oracle Solaris Cluster or Microsoft Cluster. Indicate the Failover Group Name. Leave this field blank if you previously selected Veritas Cluster File System. Then the Tivoli Storage Manager KM will monitor the entire cluster from the active master system, which is identified by the vxdctl -c mode command. This method requires vxconfigd in enable mode with its clustered state active. In the Monitoring Node Names field, name all the nodes where the solution is installed. The list must be delimited by commas. 7. (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 active master system or on the node where failover group is online and will not check the monitoring status of the other nodes through PATROL Agent: Check the Enable Remote PATROL Agent Checking box. Click the Remote Agent button. The following dialog box is displayed: Configuring Monitor Settings 40 Configuring Multi-node Mode

41 In the Monitoring Node Name field, indicate the cluster node used for multi-node mode failover 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 to communicate with the remote PATROL Agent before failing over Enter the timeout between attempts, in seconds Click Add to List Resume the procedure for all the nodes previously listed 41 Configuring Monitor Settings Configuring Remote Agent Settings

42 8. Click Close on all pop-ups. 9. Click Add to List in the main window. 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 Tivoli Storage Manager components will be monitored. If a managed node is unable to determine the system which should be in Active Multi-node Mode, it will change to Temporary Single-node Mode. Enabling the Debug Mode When you encounter an issue and wish to report it to Sentry Software, you will be asked to enable the Debug Mode and provide the debug output to the Sentry Software support team. To enable the debug mode 1. Specify the Tivoli Storage Manager server to be monitored and the user account to be used. 2. In the Advanced Settings section, click the Advanced button. Accessing Advanced Settings Configuring Monitor Settings 42

43 3. The Advanced dialog is displayed. Advanced Settings Options 43 Configuring Monitor Settings

44 Configuring Debug Settings 5. In the Options section, indicate: when the system must stop logging debug information. The required format is: YYYY/MM/ DD HH: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 Add to the List in the main window. 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_<port>.log file, stored in <PATROL_HOME>/log, for any error. Configuring Monitor Settings In the Debug Mode section, click Debug. 5. Select all the elements for which you want to obtain debug information:

45 Configuring Other Monitor Types Configuring Automated Drives By default, BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring monitors all the discovered automated drives for a local or remote TSM server. However, it is possible to apply filters to specify whether or not specific drives will be monitored. To configure the monitoring of automated drives Configuring Automated Drives Monitoring 2. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on Tivoli Storage Manager servers a hostname or IP address to apply these settings to a specific server 3. (Optional) In the Filtering (automatically discovered), click Filtering to specify the drives that will be monitored. 4. (Optional) In the Additional Automated Drives (manual discovery), click Manual Add to add specific drives you wish to monitor. 5. Click Add to List. 6. Click Add. 7. Finally, Update the policy. 45 Configuring Monitor Settings 1. Add or edit a monitor type and select TSM Automated Drive as a Monitor Type.

46 Configuring Automated Libraries By default, BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring monitors all the discovered libraries for a local or remote TSM server. However, it is possible to apply filters to specify whether or not specific libraries will be monitored. To configure the monitoring of automated libraries Configuring Automated Libraries Monitoring 2. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on Tivoli Storage Manager servers a hostname or IP address to apply these settings to a specific server 3. (Optional) In the Filtering (automatically discovered), click Filtering to specify the libraries that will be monitored. 4. (Optional) In the Additional Automated Libraries (manual discovery), click Manual Add to add specific libraries you wish to monitor. 5. Click Add to List. 6. Click Add. 7. Finally, Update the policy. Configuring Monitor Settings Add or edit a monitor type and select TSM Automated Library as a Monitor Type.

47 Configuring Clients By default, BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring monitors all the discovered clients for a local or remote TSM server. However, it is possible to apply filters to specify whether or not specific clients will be monitored. To configure the monitoring of clients Configuring Clients Monitoring 2. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on Tivoli Storage Manager servers a hostname or IP address to apply these settings to a specific server 3. (Optional) In the Filtering (automatically discovered), click Filtering to specify the clients that will be monitored. 4. (Optional) In the Additional Clients (manual discovery), click Manual Add to add specific clients you wish to monitor. 5. Click Add to List. 6. Click Add. 7. Finally, Update the policy. 47 Configuring Monitor Settings 1. Add or edit a monitor type and select TSM Client as a Monitor Type.

48 Configuring Daemons By default, BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring monitors all the discovered daemons for a local or remote TSM server. However, it is possible to apply filters to specify whether or not specific daemons will be monitored. To configure the monitoring of daemons Configuring Daemons Monitoring 2. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on Tivoli Storage Manager servers a hostname or IP address to apply these settings to a specific server 3. (Optional) In the Filtering (automatically discovered), click Filtering to specify the daemons that will be monitored. 4. (Optional) In the Additional Daemons (manual discovery), click Manual Add to add specific daemons you wish to monitor. 5. Click Add to List. 6. Click Add. 7. Finally, Update the policy. Configuring Monitor Settings Add or edit a monitor type and select TSM Daemon as a Monitor Type.

49 Configuring Domains By default, BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring monitors all the discovered domains for a local or remote TSM server. However, it is possible to apply filters to specify whether or not specific domains will be monitored. To configure the monitoring of domains Configuring Domains Monitoring 2. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on Tivoli Storage Manager servers a hostname or IP address to apply these settings to a specific server 49 Configuring Monitor Settings 1. Add or edit a monitor type and select TSM Domain as a Monitor Type.

50 3. (Optional) In the Filtering (automatically discovered), click Filtering to specify the domains that will be monitored. 4. (Optional) In the Additional Domains (manual discovery), click Manual Add to add specific domains you wish to monitor. 5. 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 the restriction window must at least last 5 minutes 6. Click Add to list. 7. Click Add. Configuring Domain Client Nodes By default, BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring monitors all the discovered domain client nodes for a local or remote TSM server. However, it is possible to apply filters to specify whether or not specific domain client nodes will be monitored. To configure the monitoring of domain client nodes Configuring domain client nodes Monitoring 2. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on Tivoli Storage Manager Configuring Monitor Settings Add or edit a monitor type and select TSM Domain Client Nodes as a Monitor Type.

51 servers a hostname or IP address to apply these settings to a specific server (Optional) In the Filtering (automatically discovered), click Filtering to specify the domain client nodes that will be monitored. (Optional) In the Additional Domain Client Nodes (manual discovery), click Manual Add to add specific domain client nodes you wish to monitor. Click Add to List. Click Add. Finally, Update the policy. Configuring Jobs By default, the Tivoli Storage Manager KM monitors all scheduled jobs that completed successfully for 24 hours and any other scheduled job for 72 hours. This monitoring duration can however be modified to better suit your requirements. Increasing the monitoring duration may affect the performance of the application. To configure jobs Configuring Tivoli Storage Manager Server Jobs 2. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on Tivoli Storage Manager servers 51 Configuring Monitor Settings 1. Add or edit a monitor type and select TSM Job as a Monitor Type.

52 a hostname or IP address to apply these settings to a specific server In the Monitoring Duration section: Indicate how many hours the jobs in OK, Suspicious, and Failure status will be monitored Uncheck Keep Monitoring Active Jobs Indefinitely if you prefer not to monitor active jobs when their duration exceeds the monitoring duration set above Click Add to List Click Add. Finally, Update the policy. Configuring Logs BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring scans log files by reading the new log entries since the last data collection cycle. By default, only 500 KBytes of data is scanned for each log file during each data collection cycle. This log scan limit can however be modified to better suit your requirements. Increasing the Log Scan Limit may impact the performance of the data collector (TSMLogCollector), the monitoring solution, and the PATROL Agent. 1. Add or edit a monitor type 2. Select TSM Log as a Monitor Type. Configuring the Logs Monitoring 3. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on TSM Servers a hostname or IP address to apply these settings to a specific server Configuring Monitor Settings 52 To customize the log scan limit

53 4. In the Log Scan Limit field, indicate the amount of data (in KBytes) that will be read by the monitoring solution during each data collection cycle (Default is 500 kbytes). 5. In the Actlog Query Limit field, indicate the maximum query limit (in minutes). By default the solution queries up to 300 minutes (5 hours) of actlog data. 6. Click Add to List. 7. Click Add. 8. Finally, Update the policy. Configuring Manual Drives By default, BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring monitors all the discovered manual drives for a local or remote TSM server. However, it is possible to apply filters to specify whether or not specific drives will be monitored. To configure the monitoring of manual drives Configuring Manual Drives Monitoring 2. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on Tivoli Storage Manager servers a hostname or IP address to apply these settings to a specific server 53 Configuring Monitor Settings 1. Add or edit a monitor type and select TSM Manual Drive as a Monitor Type.

54 3. (Optional) In the Filtering (automatically discovered), click Filtering to specify the drives that will be monitored. 4. (Optional) In the Additional Manual Drives (manual discovery), click Manual Add to add specific drives you wish to monitor. 5. Click Add to List. 6. Click Add. 7. Finally, Update the policy. Configuring Mount Requests By default, the Tivoli Storage Manager KM monitors all mount requests for 24 hours. This monitoring duration can however be modified to better suit your requirements. Increasing the monitoring duration may affect the performance of the application. To configure the monitoring of mount requests Configuring Mount Requests Monitoring 2. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on Tivoli Storage Manager servers a hostname or IP address to apply these settings to a specific server 3. In the Mount Request Configuration section, indicate how many hours the mount requests will be monitored. 4. Click Add to List. 5. Click Add. Configuring Monitor Settings Add or edit a monitor type and select TSM Mount Request as a Monitor Type.

55 Configuring TSM Processes By default, the Tivoli Storage Manager KM monitors all processes for 24 hours. This monitoring duration can however be modified to better suit your requirements. Increasing the monitoring duration may affect the performance of the application. To configure the monitoring of processes Configuring Processes Monitoring 2. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on Tivoli Storage Manager servers a hostname or IP address to apply these settings to a specific server 3. In the Process Configuration section, indicate how many hours the processes will be monitored. 4. Click Add to List. 5. Click Add. 55 Configuring Monitor Settings 1. Add or edit a monitor type and select TSM Process as a Monitor Type.

56 Configuring Storage Pools By default, BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring monitors all the discovered storage pools for a local or remote TSM server. However, it is possible to apply filters to specify whether or not specific storage pools will be monitored. To configure the monitoring of storage pools Configuring Storage Pools Monitoring 2. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on Tivoli Storage Manager servers a hostname or IP address to apply these settings to a specific server 3. (Optional) In the Filtering (automatically discovered), click Filtering to specify the storage pools that will be monitored. 4. (Optional) In the Additional Storage Pools (manual discovery), click Manual Add to add specific storage pools you wish to monitor. 5. Click Add to List. 6. Click Add. 7. Finally, Update the policy. Configuring Monitor Settings Add or edit a monitor type and select TSM Storage Pool as a Monitor Type.

57 Filtering Elements to Monitor Filtering options are available for the following monitor types: TSM Automated Drive, TSM Automated Library, TSM Client, TSM Daemon, TSM Domain, TSM Domain Client Node, TSM Manual Drive, and TSM Storage Pool. 1. Add or edit a monitor type 2. Select the Monitor Type for which you wish to apply filters. 3. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on Tivoli Storage Manager Servers a hostname or IP address to apply these settings to a specific server 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 monitored and click Add to List In the Exclude... section, indicate the regular expression for the element not to be monitored and 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. 57 Configuring Monitor Settings To filter elements to monitor

58 Reference Guide

59 Introduction This chapter provides statistical information about resources, operating status, and performances managed by the Tivoli Storage Manager KM. It contains tables describing the attributes used in the monitoring solution, grouped by Monitor Types, and provides a brief description of each attribute and its default settings. Monitor Types Tivoli Storage Manager KM TSM Clients TSM Client TSM Daemons TSM Daemon TSM Databases TSM Database TSM Logs TSM Log TSM Domains TSM Domain TSM Jobs TSM Job TSM Mount Requests TSM Mount Request TSM Automated Libraries TSM Automated Library TSM Manual Drive TSM Automated Drives TSM Automated Drive TSM Domain Client Node TSM Storage Pools TSM Storage Pool TSM Processes TSM Process 59

60 Baselines and Key Performance Indicators Some attributes are identified by default as Key Performance Indicators (KPIs) and therefore automatically 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:. 60

61 Tivoli Storage Manager KM Attributes Name Description Units Recommended Alert Conditions Attribute Type Login Status Monitors the status of the TSM KM login details (username/ password) for the operating system and DSMADMC. 0 = OK 1= Suspicious 2 = Failure Warning = 1 Alarm = 2 Collection Status Monitoring Mode Monitors the failover mode of the TSM KM. By default TSM KM runs in Permanent Single-node Mode. 0= Permanent Single-node Mode 1= Temporary Single-node Mode 2 = Active Multi-node Mode 3 = Passive Multi-node Mode -1 = Unknown n/a Collection Status Node Status Monitors the error messages generated for the Tivoli Storage Manager application on the managed system. 0 = OK 1= Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability 61 If no valid username/ password is detected for the operating system or DSMADMC, this attribute will be set to Failure. If there are any suspicious command exits, this attribute will be set to Suspicious.

62 TSM Clients Attributes Name Exec Time Description Units Seconds Inactive standard parameter monitors the collector execution time. To activate this parameter, use the PSL below, and restart the PATROL Agent: %PSL pconfig("replace", "/Runtime/TSM/<node-id>/ TSMClientCollectorExecTi me", 1); Recommende d Alert Conditions Attribute TypeType Warning > preset value or observed maximum (default) Collection Status %PSL pconfig("replace", "/Runtime/TSM/<node-id>/ TSMClientCollectorWarn", 3600); Tivoli Storage Manager KM 62 When activated it will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below:

63 TSM Client Name Description Units Recommended Alert Conditions Attribute Type Last Access Elapsed Time Displays the time elapsed since the last communication from the client. Hours Space Used Displays the amount of Gigabytes space used on the (GB) client node. State Displays the state of the client. 0 = Running 1 = Locked 2 = Never Communicat ed -1 = Unknown Availability Status Displays the client status. The following State to Status mapping rule is used: Never Communicated > Failure Unknown > Failure Locked > Suspicious All other states > OK 0 = OK 1= Suspicious 2 = Failure Warning = 1 Alarm =2 Availability For detailed information about Attributes KPI, see Managing Baselines and Key Performance Indicators. 63 TSM Clients

64 TSM Daemons Attributes Name Exec Time Description Units Seconds Inactive standard attribute monitors the collector execution time. To activate this attribute, use the PSL below, and restart the PATROL Agent: %PSL pconfig("replace", "/Runtime/TSM/<node-id>/ TSMDaemonsCollectorExecT ime", 1); Recommende Attribute Type d Alert Conditions Warning: > preset value or observed maximum (default) Collection Status %PSL pconfig("replace", "/Runtime/TSM/<node-id>/ TSMDaemonCollectorWarn", 3600); TSM Client 64 When activated it will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below:

65 TSM Daemon Name Description Units Recommended Alert Conditions Attribute Type CPU Duration Displays the CPU seconds consumed by the daemon. Seconds CPU Utilization Displays the percentage of CPU used by the daemon. Percentage (%) Memory Size Displays the core image size of the daemon in the virtual memory. Kilobytes (KB) Processes Count Displays the number of Processes daemon processes/ threads found. State Displays the state of the daemon as reported in the command executed by the data collector. 0 = Running 1 = Sleeping 2 = Waiting 3 = Queued 4= Intermediate 5= Terminated 6 = Stopped/ Disabled 7 = Growing 8= xistent/ Not Responding 9 = Not Running -1 = Unknown Availability Status Monitors the status of the daemon. The following State to Status mapping rule is used: xistent/not Responding > Failure Not Running > Failure Terminated or Stopped > Suspicious 0 = OK 1= Suspicious 2 = Failure Availability 65 Attributes TSM Daemons

66 Name Description Units Recommended Alert Conditions Attribute Type Growing or Unknown > Suspicious All other states > OK KPI, see Managing Baselines and Key Performance Indicators. For detailed information about TSM Daemon 66

67 TSM Databases Attributes Exec Time Description Units Seconds Inactive standard parameter monitors the collector execution time. To activate this parameter, use the PSL below, and restart the PATROL Agent: %PSL pconfig("replace", "/Runtime/TSM/<node-id>/ TSMDatabaseCollectorExec Time", 1); Recommende Attribute Type d Alert Conditions Warning > preset value or observed maximum (default) Collection Status When activated it will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: Name %PSL pconfig("replace", "/Runtime/TSM/<node-id>/ TSMDatabaseCollectorWarn ", 3600); 67 TSM Daemon

68 TSM Database Name Description Units Recommended Alert Conditions Attribute Type Backup Elapsed * Displays the elapsed time since the last successful database backup. Hours Buffer Request Count * Displays the cumulative number of requests for database pages since the buffer pool was last reset (or since the server was last started). Count Cache Hit Percent * Displays (as a percentage of the total number of requests) the number of requests for a database pages that are already in the buffer pool. Percentage (%) Cache Wait Percent Displays (as a percentage of the total number of requests) the number of requests for database buffer pool pages where no pages are available, because all pages are in use. Percentage (%) Monitors the percentage of space used by the file system where the database resides. Percentage (%) Warning = Alarm > 98 * File System Space Used Percent * Megabytes Log Consumed Size * Displays the cumulative (MB) consumption of the log space used by the server since the last reset of this attribute. TSM Databases 68 Attributes

69 Description Units Recommended Alert Conditions Attribute Type Log Pool Used Percent * Displays (as a percentage of all recovery log buffer pool pages) the number of buffer pool pages used to write changes to the recovery log after a transaction is committed. Percentage (%) Log Pool Wait Percent * Set by Percentage TSMDatabaseCollector. (%) Displays (as a percentage of all recovery log buffer pool requests) the number of requests for buffer pool pages where no pages are available because all pages are in use. Pool Hit Percent * Displays (as a percentage of the total number of requests) the number of requests for database pages that are already in the buffer pool. Percentage (%) Reorg Elapsed * Displays the elapsed time since the last database reorganization. Hours Space Available Monitors the amount of assigned space remaining available for use by the server database. Megabytes (MB) Warning = 2-5 Alarm < 2 Availability Space Changed * Displays the database pages (in megabytes) that have changed since the last backup. Megabytes (MB) Space Changed Percent * Displays the Percentage percentage of database (%) pages that have changed since the last backup. Space Growth Rate Displays the growth Megabytes rate of the space used per second by the server database. (MB/s) 69 Name TSM Database

70 Description Space Max Extension Units Recommended Alert Conditions Attribute Type Displays the maximum Megabytes amount the database (MB) can be extended by. Space Max Reduction Displays the maximum Megabytes amount the database (MB) can be reduced by. Warning: 4-8 Alarm: less than 4 Space Used Displays the amount of Megabytes assigned space used (MB) by the server database. Space Used Percent Monitors the Percentage percentage of assigned (%) space used by the server database. The total assigned space is the used space (Space Used) plus the available space (Space Available). * This attribute is only available for the server database (db). For detailed information about TSM Database KPI, see Managing Baselines and Key Performance Indicators. 70 Name

71 TSM Logs Attributes Exec Time Description Inactive standard parameter monitors the collector execution time. To activate this parameter, use the PSL below, and restart the PATROL Agent: %PSL pconfig("replace", "/Runtime/TSM/<node-id>/ TSMLogCollectorExecTime", 1); Units Recommende Attribute Type d Alert Conditions Seconds Warning > preset value or observed maximum (default) Collection Status When activated it will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: Name %PSL pconfig("replace", "/Runtime/TSM/<node-id>/ TSMLogCollectorWarn", 3600); 71 TSM Database

72 TSM Log Attributes Name Description Units Recommended Alert Conditions Attribute Type Alarm Message Count Monitors the number of alarm messages. Count Alarm > 1 File Space Growth Rate* Displays the growth rate of the amount of space used by the log file. Kilobytes per second (KB/ s) File Space Used* Displays the amount of Kilobytes space used by the log (KB) file. File System Space Used Percent* Monitors the percentage of space used by the file system (where the log file resides). Warning = Alarm: > 98 Space Available* Monitors the Megabytes available space for the (MB) log file to use (this is also the available space on the file system). Warning = 2-5 Alarm < 2 Availability Percentage (%) Warning = Alarm: > 98 Count Warning > 1 The total capacity is the used space (Log Space Used) plus available space (Log Space Available). Warning Message Count Monitors the number of warning messages. *This attribute is not available for the activity log (actlog). For detailed information about TSM Logs KPI, see Managing Baselines and Key Performance Indicators. 72 Space Used Percent* Monitors the percentage of capacity used by the log file. Percentage (%)

73 TSM Domains Attributes Exec Time Description Inactive standard parameter monitors the collector execution time. To activate this parameter, use the PSL below, and restart the PATROL Agent: %PSL pconfig("replace", "/Runtime/TSM/<node-id>/ TSMDomainCollectorExecTi me", 1); Units Recommende d Alert Conditions Attribute Type Seconds Warning > preset value or observed maximum (default) Collection Status When activated it will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: Name %PSL pconfig("replace", "/Runtime/TSM/<node-id>/ TSMDomainCollectorWarn", 3600); 73 TSM Log

74 TSM Domain Name Description Units Recommended Alert Conditions Attribute Type Backup Elapsed Displays the elapsed time since the last backup for this domain, regardless of completion status of the backup. Hours Backup Throughput Displays the throughput of the last successful backup for this domain. Gigabytes per second (GB/s) Full Backup Duration Displays the duration of the last successful full backup for this domain. Seconds Full Backup Elapsed Displays the elapsed time since the last successful full backup for this domain. Hours Full Backup Object Count Displays the number of Count objects backed up in the last successful full backup for this domain. Full Backup Size Displays the size of the Gigabytes last successful full (GB) backup for this domain. Incremental Backup Duration Displays the duration Seconds of the last successful incremental backup for this domain. Incremental Backup Elapsed Displays the elapsed Hours time since the last successful incremental backup for this domain. Incremental Backup Object Count Displays the number of Count objects backed up in the last successful incremental backup for this domain. TSM Domains 74 Attributes

75 Description Incremental Backup Size Recommended Alert Conditions Attribute Type Displays the size of the Gigabytes last successful (GB) incremental backup for this domain. State Displays the state of the domain. 0 = Idle 1 = Running 2 = Running in Restricted Window 3 = Not Started 4 = Inactive -1 = Unknown Availability Status Monitors the status of the domain. The following State to Status mapping rule is used: Running in restricted window > Failure Running for more than 600 minutes > Suspicious Unknown > Suspicious All other states > OK 0 = OK 1= Suspicious 2 = Failure Availability Successful Backup Elapsed Displays the elapsed time since the last successful backup for this domain. hours For detailed information about Units Name KPI, see Managing Baselines and Key Performance Indicators. 75 TSM Domain

76 TSM Jobs Attributes Description Active Backup Count Recommended Alert Conditions Attribute Type Displays the number of Count active backup jobs currently discovered and monitored. Active Count Displays the number of Count active jobs currently discovered and monitored. Active Non-Backup Count Displays the number of Count active non-backup jobs currently discovered and monitored. Warning > preset value or observed maximum (default) Collection Status Exec Time Inactive standard parameter monitors the collector execution time. To activate this parameter, use the PSL below, and restart the PATROL Agent: Units Seconds Name %PSL pconfig("repla CE", "/ Runtime/TSM/ <node-id>/ TSMJobCollecto rexectime", 1); When activated it will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: TSM Domain 76

77 Name Description Units Recommended Alert Conditions Attribute Type %PSL pconfig("repla CE", "/ Runtime/TSM/ <node-id>/ TSMJobCollecto rwarn", 3600); KPI, see Managing Baselines and Key Performance Indicators. For detailed information about 77 TSM Jobs

78 TSM Job TSM Jobs Name Description Units Recommended Alert Conditions Attribute Type Duration Displays the duration of the job from the start. Seconds Error Count Monitors the number of client node errors logged in the server activity log during this job. Count Warning when > 100 Network Throughput Displays the throughput of the job on the network. Megabytes per second (MB/s) Object Count Displays the number of Count objects inspected for this job. Object Expired Count Displays the total number of objects for this job that have expired. Count Object Failed Count Displays the total number of objects for this job that have failed. Count Warning when > 100 Object Processed Count Displays the total number of objects for this job that have been processed. Count Object Rebound Count Displays the total number of objects for this job that have been rebound. Count Object Updated Count Displays the total number of objects for this job that have been updated. Count Size Displays the amount of Megabytes data backed up for the (MB) job. State Displays the state of the job. Availability 0= Completed 1 = Future 2 = Pending 78 Attributes

79 Name Description Units Recommended Alert Conditions Attribute Type Status Monitors the status of the job. The following State to Status mapping rule is used: Missed, Severed, or Failed > Failure Pending for more than 1 hour > Suspicious Started for more than 5 hours > Suspicious Restarted for more than 5 hours > Suspicious Completed/Errors > Suspicious Started/Errors > Suspicious Restarted/Errors > Suspicious All other states > OK 0 = OK 1= Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability Throughput Displays the throughput of the job. Megabytes per second (MB/s) For detailed information about 3 = In Progress 4 = Started 5 = Restarted 6= Completed/ Errors 7 = Started/ Errors 8= Restarted/ Errors 9 = Failed No Restart 10 = Missed 11 = Severed 12 = Uncertain 13 = Failed -1 = Unknown KPI, see Managing Baselines and Key Performance Indicators. 79 TSM Job

80 TSM Mount Requests Attributes Name Exec Time Description Units Seconds Inactive standard parameter monitors the collector execution time. To activate this parameter, use the PSL below, and restart the PATROL Agent: %PSL pconfig("replace", "/Runtime/TSM/<node-id>/ TSMRequestCollectorExecT ime", 1); Recommende d Alert Conditions Attribute Type Warning > preset value or observed maximum (default) Collection Status %PSL pconfig("replace", "/Runtime/TSM/<node-id>/ TSMRequestCollectorWarn", 3600); TSM Job 80 When activated it will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below:

81 TSM Mount Request Name Description Units Recommended Alert Conditions Attribute Type Elapsed Displays the elapsed time since the mount request was issued. Minutes State Displays the state of the mount request as reported in the command executed by the data collector. 0= Completed1 = Pending -1 = Unknown Availability Status Monitors the status of the mount request. The following State to Status mapping rule is used: Pending for more than 30 minutes > Failure Pending or Unknown > Suspicious All other states > OK 0 = OK 1= Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability Timeout Displays the time remaining until the mount request times out. Minutes Alarm = 0-30 For detailed information about KPI, see Managing Baselines and Key Performance Indicators. 81 TSM Mount Requests Attributes

82 TSM Automated Libraries Attributes Name Exec Time Description Units Seconds Inactive standard parameter monitors the collector execution time. To activate this parameter, use the PSL below, and restart the PATROL Agent: %PSL pconfig("replace", "/Runtime/TSM/<node-id>/ TSMLibraryCollectorExecT ime", 1); Recommende d Alert Conditions Attribute Type Warning > preset value or observed maximum (default) Collection Status %PSL pconfig("replace", "/Runtime/TSM/<node-id>/ TSMLibraryCollectorWarn", 3600); TSM Mount Request 82 When activated it will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below:

83 TSM Automated Library Name Description Units Recommended Alert Conditions Attribute Type State Displays whether the path for the automated library is online or offline. It will not perform any remote automated library test command on the storage agent. 0 = Online 1 = Offline 2 = Path Offline -1 = Unknown Availability Status Monitors the status of the automated library. 0 = OK 1= Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability Up Drive Count Displays the number up / online state drives in this robotic library. Count Volume Count Displays the total number of volume loaded in this automated library. Count Volume Private Count Displays the number of Count private volumes in the automated library. Volume Scratch Count Displays the number of Count scratch volumes in the automated library. Volume Scratch Percent Monitors the Percentage percentage of scratch (%) volume against the total number of volume loaded in this automated library. For detailed information about KPI, see Managing Baselines and Key Performance Indicators. 83 TSM Automated Libraries Attributes

84 TSM Manual Drive Attributes Name Description Units Recommended Alert Conditions State Displays the state of the automated library drive. This is determined from the automated library drive control information. 0 = Online 1 = Empty 2 = Loaded 3 = Unloaded 4 = Reserved 5= Unavailable 6 = Drive Offline 7 = Path Offline -1 = Unknown Availability Status Monitors the status of the automated library drive. 0 = OK 1= Suspicious 2 = Failure Availability Warning = 1 Alarm = 2 Attribute Type TSM Automated Library 84

85 TSM Automated Drives Attributes Exec Time Description Inactive standard parameter monitors the collector execution time. To activate this parameter, use the PSL below, and restart the PATROL Agent: %PSL pconfig("replace", "/Runtime/TSM/<node-id>/ TSMDriveCollectorExecTime ", 1); Units Recommende d Alert Conditions Attribute Type Seconds Warning > preset value or observed maximum (default) Collection Status When activated it will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: Name %PSL pconfig("replace", "/Runtime/TSM/<node-id>/ TSMDriveCollectorWarn", 3600); 85 TSM Manual Drive

86 TSM Automated Drive Attributes Description Units Recommended Alert Conditions Attribute Type State Displays the state of the automated library drive. This is determined from the automated library drive control information. 0 = Online 1 = Empty 2 = Loaded 3= Unloaded 4 = Reserved 5= Unavailable 6 = Drive Offline 7 = Path Offline -1 = Unknown Availability Status Monitors the status of the automated library drive 0 = OK 1= Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability Name TSM Automated Drives 86

87 TSM Domain Client Node Name Description Units Recommended Alert Conditions Attribute Type Backup Throughput Displays the throughput of the last successful backup for this client node. Megabytes per second (MB/s) Last Full Backup Duration Displays the duration of the last successful full backup for this client node. Seconds Last Full Backup Object Count Displays the number of Count objects backed up in the last successful full backup for this client node. Last Full Backup Size Displays the size of the Megabytes last successful full (MB) backup for this client node. Last Incremental Backup Duration Displays the duration of the last successful incremental backup for this client node. Last Incremental Backup Object Count Displays the number of Count objects backed up in the last successful incremental backup for this client node. Last Incremental Backup Size Displays the size of the Megabytes last successful (MB) incremental backup for this client node. For detailed information about Seconds KPI, see Managing Baselines and Key Performance Indicators. 87 TSM Automated Drive Attributes

88 TSM Storage Pools Attributes Name Exec Time Description Inactive standard parameter monitors the collector execution time. To activate this parameter, use the PSL below, and restart the PATROL Agent: %PSL pconfig("replace", "/Runtime/TSM/<node-id>/ TSMPoolCollectorExecTime", 1); Units Recommende d Alert Conditions Attribute Type Seconds Warning > preset value or observed maximum (default) Collection Status %PSL pconfig("replace", "/Runtime/TSM/<node-id>/ TSMPoolCollectorWarn", 3600); TSM Domain Client Node 88 When activated it will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below:

89 TSM Storage Pool Attributes Description Space Available Units Recommended Alert Conditions Attribute Type Monitors the available Gigabytes volume space for the (GB) backup data to use in this storage pool. Warning < 1 Alarm = 0 Availability Space Growth Rate Displays the growth Gigabytes rate of the total volume per second space used by the (GB/s) backup data in this storage pool. Space Logical Percent Displays the logical occupancy of the storage pool as a percentage of the total occupancy. Space Migrated Displays the amount of Gigabytes data that has been (GB) migrated, if migration is in progress. If migration is not in progress, this value indicates the amount of data migrated during the last migration. Note: This attribute is not available for copy storage pools. Space Migration Percent Displays an estimate of the percentage of data in the storage pool that can be migrated. Note: This attribute is not available for copy storage pools. Percentage (%) Percentage (%) 89 Name TSM Storage Pools

90 Description Space Migration Elapsed Units Recommended Alert Conditions Attribute Type Displays the amount of Seconds time that has elapsed since migration of the storage pool began, if migration is active. If migration is not active, this value indicates the amount of time required to complete the last migration. Note: This attribute is not available for copy storage pools. Space Reclaimable Displays the amount of Gigabytes space in the storage (GB) pool that is reclaimable. Space Reclaimable Percent Displays the amount of Percentage reclaimable space as a (%) percentage of the total storage pool space. Space Used Displays the total Gigabytes volume space occupied (GB) by the backup data in this storage pool. Space Used Percent Monitors the Percentage percentage of total (%) occupied volume space against the total volume capacity of this storage pool (not including any scratch volumes). Warning > 95 Alarm > 98 Volumes Active Count Displays the number of Count active volumes in this storage pool. Active volumes are available disk volumes with a status of "Online" or tape volumes with a status of "Filling", where data has been written but the volume is not yet full. TSM Storage Pool 90 Name

91 Name Description Volume Active Percent Units Recommended Alert Conditions Attribute Type Monitors the Percentage percentage of active (%) volumes against the total number of volumes in this storage pool. Volume Available Count Displays the number of Count volumes assigned to this storage pool. Volume Available Percent Monitors the percentage of available volumes against the total number of volumes in this storage pool. Percentage (%) Volume Count Displays the total number of volumes in this storage pool. Count Volume Empty Count Displays the number of Count empty volumes in this storage pool. Volume Full Count Displays the number of Count full volumes in this storage pool. Volume Full Percent Monitors the Percentage percentage of full (%) volumes against the total number of volumes in this storage pool. Volume Offline Count Displays the number of Count offline volumes in this storage pool. Empty is a possible status for a tape volume, indicating that no data is stored on that volume. "Offline" is a possible status for a disk volume. Volume Pending Count Displays the number of Count pending volumes in this storage pool. 91 TSM Storage Pool

92 Name Description Units Recommended Alert Conditions Attribute Type "Pending" is a possible status for a tape volume, where all files have been deleted but a delay has been placed on the volume before reuse. KPI, see Managing Baselines and Key Performance Indicators. For detailed information about TSM Storage Pool 92

93 TSM Processes Attributes Exec Time Description Units Seconds Inactive standard parameter monitors the collector execution time. To activate this parameter, use the PSL below, and restart the PATROL Agent: %PSL pconfig("replace", "/Runtime/TSM/<node-id>/ TSMProcessCollectorExecT ime", 1); Recommend ed Alert Conditions Attributes Type Warning > preset value or observed maximum (default) Collection Status When activated it will run every minute and trigger a warning when the collector runs for more than the observed maximum time. This maximum time can be overridden by a preset value (example: 3600 seconds), using the PSL below: Name %PSL pconfig("replace", "/Runtime/TSM/<node-id>/ TSMProcessCollectorWarn", 3600); 93 TSM Storage Pool

94 TSM Process Name Description Units Recommended Alert Conditions Attribute Type Duration Displays the duration of the process. Seconds Item Count Displays the number of Count items found. Size Displays the process size. Megabytes (MB) State Displays the state of the process. 0 = Running 1 = Running/ Errors 2= Completed/ Success 3= Completed / Failure -1 = Unknown Availability Status Monitors the status of the process. The following State to Status mapping rule is used: Completed/Failure > Failure Running/Errors or Unknown > Suspicious Running for more than 10 hours > Suspicious All other states > OK. 0 = OK 1= Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability Throughput Displays the throughput of the process. Megabytes per second (MB/s) For detailed information about TSM Processes KPI, see Managing Baselines and Key Performance Indicators. 94 Attributes

95 Managing Baselines and Key Performance Indicators To detect abnormalities on the monitored environment, BMC TrueSight Operations Management calculates baselines per attribute based on values collected over a specified period of time to determine a normal operating range. When the collected values for these parameters are out of range, an alert is triggered. Some attributes are identified by default as Key Performance Indicators (identified with the icon) and automatically included in the base lining calculation. Managing baselines The baseline is the expected normal operating range for an attribute of a monitor. There are two baselines: Baseline High and Baseline Low. Baseline High represents the point at which 95% of the weighted average of the historical values fall below this value for the selected time period; Baseline Low represents the point at which 90% of the weighted average of historical values for the selected time period fall above this line. Managing Key Performance Indicators Starting from v9.5 of BPPM, attributes that have not been initially designated in the KM as Key Performance Indicators (KPIs) cannot be flagged as KPIs from BPPM/TrueSight. Although enabling baseline is possible through the Options > Administration > Intelligent Event Thresholds feature available in the Infrastructure Management Server operator console, BMC does not recommend doing it. For more information, refer to the BMC TrueSight Operations Management documentation available from docs.bmc.com. 95 TSM Process Baselines are generated for KPI attributes that have an active abnormality thresholds.

96 Index -A Abnormalities Access 95 Permissions 13 User 13 Add Monitor Types 27 Attributes Active Backup Count 76 Active Count 76 Active Non-Backup Count 76 Alarm Message Count 72 Backup Elapsed 68, 74 Backup Throughput 74, 87 Buffer Request Count 68 Cache Hit Percent 68 Cache Wait Percent 68 CPU Duration 65 CPU Utilization 65 Duration 78, 94 Elapsed 81 Error Count 78 Exec Time 62, 64, 67, 71, 73, 76, 80, 82, 85, 88, 93 File Space Growth Rate 72 File Space Used 72 File System Space Used Percent 68, 72 Full Backup Duration 74 Full Backup Elapsed 74 Full Backup Object Count 74 Full Backup Size 74 Incremental Backup Duration 74 Incremental Backup Elapsed 74 Incremental Backup Object Count 74 Incremental Backup Size 74 Item Count 94 Last Access Elapsed Time 63 Last Full Backup Duration 87 Last Full Backup Object Count 87 Last Full Backup Size 87 Last Incremental Backup Duration 87 Last Incremental Backup Object Count 87 Last Incremental Backup Size Log Consumed Size 68 Log Pool User Percent 68 Log Pool Wait Percent 68 Login Status 61 Memory Size 65 Monitoring Mode 61 Network Throughput 78 Node Status 61 Object Count 78 Object Expired Count 78 Object Failed Count 78 Object Processed Count 78 Object Rebound Count 78 Object Updated Count 78 Pool Hit Percent 68 Processes Count 65 Reorg Elapsed 68 Size 78, 94 Space Available 68, 72, 89 Space Changed 68 Space Changed Percent 68 Space Growth Rate 68, 89 Space Logical Percent 89 Space Max Extension 68 Space Max Reduction 68 Space Migrated 89 Space Migration Elapsed 89 Space Migration Percent 89 Space Reclaimable 89 Space Reclaimable Percent 89 Space Used 63, 68, 89 Space Used Percent 68, 72, 89 State 65, 74, 78, 81, 83, 84, 86, 94 Status 63, 65, 74, 78, 81, 83, 84, 86, 94 Successful Backup Elapsed 74 Throughput 78, 94 Timeout 81 Up Drive Count 83 Volume Active Percent 89 Volume Available Count 89 Volume Available Percent 89 Volume Count 83, 89 Volume Empty Count 89 Volume Full Count 89 Volume Full Percent 89 Volume Offline Count 89 Volume Pending Count 89 Volume Private Count 83 Volume Scratch Count 83

97 Attributes Maximum Instances 36 Monitoring Duration 51 Mount Request 54 Multi-node monitoring mode Overrides 33 Processes 55 Configuring Volume Scratch Percent 83 Volumes Active Count 89 Warning Message Count 72 Automated Drive Maximum Instances Automated Drives 36 Debug 42 Automated Libraries monitor settings Connection Debug 42 Automated Library SSH 18 WMI 18 Connection Timeout Maximum Instances 36 -B- 35 -D59 Daemon BMC ProactiveNet Performance Management 95 Generation 95 Manage 95 Requirements 95 BMC PATROL Changes 11 BMC ProactiveNet Performance Management Abnormalities 95 Baselines 95 Key Performance Indicators KPI 95 Business Value CChanges Client 27 7 Maximum Instances Clients 36 Debug 42 Cluster Application 38 Component Installation package creating 23 downloading 24 Configuration Tivoli Storage Manager Settings Configure 29 Maximum Instances Daemons Debug Databases 42 Debug Debug Automated Drives 42 Automated Libraries 42 Clients 42 Daemons 42 Databases 42 Directory Path 42 Domains 42 End Time 42 Jobs 42 Logs 42 Mount Requests 42 Processes 42 Server 42 Storage Pools 42 Domain Maximum Instances Domain Client Node 36 Maximum Instances Domains 36 Configure 49 Debug 42 Downloading 24 Duration Duration 54, 55 Monitoring 54, 55 Domains 49 Hostname 51 Jobs Baseline Baselines 38

98 Log 36 Manual Drive 36 Mount Request 36 Process 36 Storage Pool 36 -F38 -J - TSM Automated Drive 57 TSM Automated Library 57 TSM Client 57 TSM Daemon 57 TSM Domain 57 TSM Domain Client Node 57 TSM Manual Drive 57 TSM Storage Pool 57 Filters JAVA Job Maximum Instances Jobs 36 Active 51 Configure 51 Debug 42 Monitoring 51 TSM Automated Drive 57 TSM Automated Library 57 TSM Client 57 TSM Daemon 57 TSM Domain 57 TSM Domain Client Node 57 TSM Manual Drive 57 TSM Storage Pool 57 Fixed Issues 7 -KKey Concepts 9 Key Performance Indicators 59 BMC ProactiveNet Performance Management 95 Manage 95 KPI 59 -G- BMC ProactiveNet Performance Management 95 Manage 95 Generate Baselines Goals L- -IImporting the Monitoring Solution Improvements 7 Installation configuring 26 Installing 24 Installing the Monitoring Solution Instances Automated Drive 36 Automated Library 36 Client 36 Deamon 36 Domain 36 Domain Client Node 36 Job 36 Log 22 Maximum Instances Logs Debug M21 Manage Baselines 95 Key Performance Indicators KPI 95 Manual Drive Maximum Instances Maximum Connections Monitor Settings configuring Failover Group Name Features 9 Filtering Options

99 Monitor Type Configure 33 DSM_CONFIG File 33 DSM_DIR Directory 33 DSM_LOG Directory 33 Local Temp Directory 33 Node Status Warnings 33 Node Type 33 Remote Temp Directory 33 TSM Installation 33 TSM Server Discovery 33 TSM Clients 62 TSM Daemons 64 TSM Databases 67 TSM Logs 71 Monitor Types Configure 54, 55 Duration 54, 55 Remotely 18 Monitoring Duration 38 Configure 54 Maximum Instances Monitoring Duration Mount Requests OOverrides 23, 24 Configure 55 Maximum Instances Monitoring Duration Processes Debug RReference Guide 59 Remote Connection Settings 18 Remote Connection Settings Connection Timeout 35 Maximum Connections 35 Remote PATROL Agent Checking Requirements -S- Debug 42 Multi-node monitoring mode 38 Package Process Security 13 Software 11 System 11 Jobs 51 Monitoring Node Names Mount Request Configure -P- Security Requirements Server Debug Software Requirements SSH 18 SSH Host Key 11 Authentication Storage Pool Tivoli Storage Manager KM 59, 61 TSM Automated Drive 86 TSM Automated Drives 85 TSM Automated Libraries 82 TSM Automated Library 83 TSM Automatic Drive 59 TSM Automatic Library 59 TSM Client 59, 63 TSM Daemon 59, 65 TSM Database 59, 68 TSM Domain 59, 74 TSM Domain Client Node 59, 87 TSM Domains 73 TSM Job 59, 78 TSM Jobs 59, 76 TSM Log 59, 72 TSM Manual Drive 59, 84 TSM Mount Request 59, 81 TSM Mount Requests 80 TSM Process 59, 94 TSM Processes 93 TSM Storage Pool 59, 89 TSM Storage Pools 88 Monitoring

100 Storage Pool Maximum Instances Storage Pools 36 Debug 42 Sudo 13, 31 System Requirements 11 -T Tivoli Storage Manager Changes 11 Tivoli Storage Manager Settings TSM Server Discovery Overrides UUNIX 31 User Account Configure 31 patrol 31 Privileges 31 Sudo 31 -W Windows 31 WMI

101 ABOUT MARKETZONE DIRECT PRODUCTS The BMC MarketZone Direct program sells and supports third-party products that complement and/or augment BMC solutions. MarketZone Direct products are available under BMC license and support terms. BUSINESS RUNS ON I.T. I.T. RUNS ON BMC SOFT WARE About Sentry Software Sentry Software, a strategic Technology Alliance Partner of BMC Software, provides comprehensive multi-platform monitoring solutions that enable management of the hardware and software aspects of all servers and SANs and covering up to 100 % of custom applications within the BMC TrueSight environment. Sentry Software also develops adapters for BMC Atrium Orchestrator that enables IT administrators to automate the execution of common requests and tasks that occur in the daily course of IT operations. Combined with BMC s servers and network automation tools, the adapters allow IT administrators to implement provisioning and decommissioning workflows that cover all layers of their IT infrastructure. Finally, Sentry Software designs connectors that bring storage capacity metrics into BMC TrueSight Capacity Optimization to ensure IT administrators that their storage infrastructure is properly sized for their current and future needs. Bus ines s t hrives when IT runs s ma rt er, fa s t er a nd s t ronger. Tha t s why t he mos t dema nding IT orga niza t ions in t he world rely on BMC Soft wa re a cros s dis t ribut ed, ma infra me, virt ua l a nd cloud environment s. Recognized a s t he lea der in Bus ines s Service Ma na gement, BMC offers a comprehens ive a pproa ch a nd unified pla t form t ha t helps IT orga niza t ions cut cos t, reduce ris k a nd drive bus ines s profit. For t he four fis ca l qua rt ers ended Sept ember 30,2011, BMC revenue wa s a pproxima t ely $2.2 billion. About BMC Software BMC Software helps leading companies around the world put technology at the forefront of business transformation, improving the delivery and consumption of digital services. From mainframe to cloud to mobile, BMC delivers innovative IT management solutions that have enabled more than 20,000 customers to leverage complex technology into extraordinary business performance increasing their agility and exceeding anything they previously thought possible. For more information about BMC Software, visit LEARN MORE To learn more about our solutions, please visit : Like us on Facebook: facebook.com/sentrysoftware Follow us on Twitter: twitter.com/sentrysoftware BMC Software, Inc. All rights reserved.