Tivoli Storage Manager KM for PATROL

Transcription

1 USER DOCUMENTATION STORAGE MONITORING Tivoli Storage Manager KM for PATROL Version September 2015

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 2006 BMC Software, Inc. or licensors, as an unpublished work. All rights reserved. BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software, Inc. 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. 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 Restricted Rights Legend

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 You can obtain technical support from BMC Software 24 hours a day, 7 days a week at From this Web site, you can: 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 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 Support by Telephone or

4 Table of Contents...15 Requirements...15 System Requirements...15 Software Requirements...17 Security Requirements Disk...22 Space Requirements Getting...22 the BMC Software Installation Utility...24 Packages...24 Extracting the Setup Files...26 Installing Tivoli Storage Manager KM for PATROL...39 Uninstalling Tivoli Storage Manager KM for PATROL...44 Upgrading the Platform...44 Performing Post-Installation Operations...45 Loading and Unloading the KM...45 Loading the KM...45 Loading the KM on PATROL Console...46 Loading the KM on PATROL Central...46 Configuring PATROL Agent to Preload the KM Unloading...46 the KM...47 Unloading the KM from the PATROL Agent...47 Unloading the KM from the PATROL Console...48 Configuring the KM User Account...51 Verifying Application Discovery...51 Checking the Instance Limits...52 Checking the Initial Setup of the KM...52 Restarting PATROL Agent and PATROL Console...54 Integrating with BMC Portal...54 Integrating with BMC ProactiveNet Performance Management 8.5.x and 8.6.x...55 Creating and Importing an Adapter for a BMC PATROL KM...56 Updating an Adapter for a BMC PATROL KM...56 Importing and Customizing Thresholds...57 Managing Baselines and Key Performance Indicators Unloading the KM from the PATROL Central Console

5 ...60 Administering Tivoli Storage Manager...60 Starting/Stopping the Server...60 Starting/Stopping the Storage Agent...60 Administering Mount Requests...61 Administering Drives...61 Cancelling Processes...61 Configuring the KM...62 Configuring Paths...63 Specifying the Node Type...64 Configuring the Multi-Node Monitoring Mode...65 Filtering Elements to Monitor...67 Configuring Monitoring Periods...71 Configuring the Elements Status...72 Configuring the Log Filter...74 Configuring the Log Scan Limit...76 Configuring Domain Backup Restriction...76 Configuring Alert Acknowledgement...79 Refreshing Parameters...81 Enabling the Debug Mode...84 Reloading Commands...84 Acknowledging Alerts...86 Generating Reports Classes...89 and Parameters...90 TSM_SERVER...99 TSM_CLIENT TSM_DAEMON_CONTAINER TSM_DAEMON TSM_DATABASE_CONTAINER TSM_DATABASE TSM_LOG_CONTAINER TSM_LOG TSM_POLICY_CONTAINER TSM_POLICY TSM_PCLIENT TSM_JOB_CONTAINER TSM_CLIENT_CONTAINER

6 TSM_JOB TSM_MOUNT_CONTAINER TSM_MOUNT TSM_LIBRARY_CONTAINER TSM_LIBRARY TSM_LDEVICE TSM_DEVICE_CONTAINER TSM_DEVICE TSM_POOL_CONTAINER TSM_POOL TSM_PROCESS_CONTAINER TSM_PROCESS Impact on Resources Where to Find Additional Help 6

7 Release Notes for v2.7.02

8 What's New TSM-248: TSM KM now supports Tivoli Storage Manager Server 7.1.x and Tivoli Storage Manager Administrative Client 6.4.x and 7.1.x, as well as the two operating systems Solaris 11 and Windows Changes and Improvements TSM-204: The query limit for actlogs has been reduced from 1 day to 5 hours. Also, the actlogs query limit can now be user-limited (only available from an actlog instance). TSM-225: The KM Home Directory path can now be shared when multiple TSM instances are monitored. The KM Temp Directory, KM Debug Directory and DSM Log paths must however remain different (see KB article Monitoring Multiple IBM Tivoli Storage Manager Server Instances (TSM)). TSM-134: A configuration problem prevented the proper monitoring of different TSM instances through different PATROL Agents on the same TSM server, causing the KM to stop operating. A procedure is now available in the Knowledge Base of the Sentry s Web site that describes how to configure the KM in order to monitor multiple IBM Tivoli Storage Manager Server instances. TSM-141: The TSMLoginStatus parameter triggered false warning when errors from the JOB_TEXT command output occurred. TSM-142: The product sometimes failed to trigger alerts for missing TSM daemons. TSM-161 & TSM-168: When activated, the TSMDaemonCollectorExecTime parameter was not appearing in the console under Daemons. Also, an error is displayed on the SOW for the same missing parameter. TSM-167: When monitoring multiple TSM instances using different PATROL Agents, dsmadmc interface hangs intermittently. The interface access is changed to lock across Agents to avoid simultaneous dsmadmc command executions. TSM-179: Migration related parameters (TSMPoolSpaceMigrated, TSMPoolSpaceMigratedPercent & TSMPoolSpaceMigrationElapsed) are not available for copy storage pools. TSM-180: The KM would create unknown job instance <unknown>) at times, with all offline parameters. TSM-186: When upgrading the KM to version , custom log filters for alarm and warning were lost. TSM-188: The KM temporary file system fills up when aclog query grows. To avoid this, a warning message is added to System Output Window (SOW) when any monitored log is not fully processed due to log scan limitation. TSM-224: On Linux platforms, the commands were randomly corrupted and caused the KM to fail. TSM-241: The KM custom paths were lost when they were set through PCM and when the PATROL Agent was not restarted immediately after the update. 8 Fixed Issues

9 TSM-269: Due to a PATROL events limitation, the KM failed to trigger log events when a large amount of errors were found in the TSM activity log. TSM-285: The product failed to identify the creation error for PCM suppressed instances and continued running commands against it, affecting the collector performance. TSM-291: PATROL Agent was crashing when large actlogs were being processed. To solve this issue, the TSM KM user related activity is no more processed in the actlog. As a consequence, the memory consumption has been reduced. TSM-297: TSM KM failed to detect Node Status errors as configured in the KM menu Configuration > Node Status. TSM-303: The Sudo configuration requirements have been updated in the Security Requirements chapter of the user documentation. TSM-309: Old TSM jobs were not removed from the console if they were discovered as completed. TSM-321: Full and incremental domain level backup summary parameters were not set correctly, preventing the product to properly monitor backups at the domain and node levels. TSM-328: On Windows systems, if the PATROL Agent installation path contained spaces, custom KM scripts and commands with output redirection failed. TSM-329: The TSMLoginStatus parameter was in warning due to an incorrect configuration variable used while checking the active cluster node. TSM-330: The Microsoft Cluster active node was not properly detected when the KM was operating in multi-node monitoring mode. TSM-335: The main discovery cycle was irregular due to an asynchronous default KM discovery interval. It is now reduced to 30 seconds to avoid such irregularity. 9

10 10

11 Overview

12 Tivoli Storage Manager KM for PATROL monitors your Tivoli Storage Manager application within a centralized management console to ensure its runs efficiently 24 hours a day. The KM more especially monitors the: 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 All the information collected is grouped into application classes and displayed in the PATROL Console. Alarms and warnings inform you when a suspicious behavior is detected; thus allowing you to quickly and clearly identify peaks, troughs and trends in the performance of your backup resources. 12

13 Monitoring Tivoli Storage Manager Refer to the Reference Guide for more information about the application classes. 13

14 Preparing for Installation

15 Requirements System 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 If the operating system is upgraded (or downgraded) at a later date, you will need to reload commands for the TSM KM. 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 BMC Software PATROL Console 3.4.x, 3.5.x, 7.x BMC Portal 2.3.x, 2.4.x, 2.5.x, 2.6.x, 2.7.x, 2.8.x BMC ProactiveNet Performance Manager 8.x, 8.5.x, 8.6.x, 9.x BMC TrueSight Operations Management 10 If the operating system is upgraded (or downgraded) at a later date, you will need to reload commands for the TSM KM. Refer to Upgrading the Platform. Changes to Tivoli Storage Manager Tivoli Storage Manager KM for PATROL requires that an administrator account be added to the Tivoli Storage Manager server for use by PATROL and the TSM KM. Refer to Admin Interface User Access. To allow this user to execute SQL SELECT queries, there should be at least 4Mbytes of temporary 15 Requirements Software Requirements

16 table storage space all the time to avoid exhausting the temporary table storage. Changes to BMC PATROL To improve the performance of the TSM KM, the PATROL Agent tuning variable /AgentSetup/ AgentTuning/pslInstructionMax should be disabled by setting it to 0 (zero) or increased to at least 5,000,000. This applies for all Tivoli Storage Manager servers and storage agents where the KM is installed. This adjustment will allow the data collectors to execute without incurring an internal scheduling delay. This PATROL Agent tuning variable can be updated using wpconfig (on Microsoft Windows),xpconfig (on Unix) or PATROL Configuration Manager (PCM). Alternatively, you can use one of the following single line PSL command through the PATROL Console OS> prompt to update this tuning variable. To disable: %PSL pconfig("replace", "/AgentSetup/AgentTuning/pslInstructionMax",0); To set to at least 5,000,000: %PSL v="/agentsetup/agenttuning/pslinstructionmax"; if(get(v)< ){pconfig("replace",v, );} The KM stores all configuration information in the PATROL Agent configuration database (pconfig), under the /TSM and/runtime/tsm paths. PATROL Agent user (default: patrol) should be able to read and write to these pconfig variables at anytime. If Access Control List (ACL) is used to control which users are authorized to connect to a PATROL Agent, please ensure that the mode for PATROL Agent user includes C in the PATROL Agent variable /AgentSetup/ accesscontrollist. Please refer the PATROL Agent Reference Manual for more details. You cannot copy or distribute these KM configuration variables between managed nodes, because they may not have the same value for each managed node. For example, the login user details may not be the same for all managed nodes. Also some of these variables, like installation paths, are set automatically during the initial discovery. Additional Software Requirements Purpose Requirements Software Version 16 In large Tivoli Storage Manager systems, the value of 5,000,000 for the tuning variable pslinstructionmax may still be insufficient. In such situations, error messages will appear on the PATROL Console System Output Window (SOW) reporting that some TSM KM data collectors are in an infinite loop. In this case you can set the tuning variable to zero to disable this functionality.

17 When running TSM KM on Linux managed nodes Korn shell binary (/bin/ksh) When running TSM KM on Reg.exe patch KB ( Microsoft Windows x64 managed support.microsoft.com/ nodes kb/948698) Any 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. 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: The user login details are configured in the KM. The password is stored in the PATROL Agent in a DES encrypted format. The encrypted password can be viewed by any user who has access to the PATROL Agent configuration variables (pconfig). This user could then execute PSL statements using the encrypted password through the PATROL Console. This can be prevented by setting up an appropriate Access Control List (ACL) for users. Please refer to the PATROL Agent Reference Manual for details on how to set up an ACL. Access Permissions The TSM 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 17 Requirements 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.

18 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 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 TSM KM includes some scripts which should be executable by the PATROL Agent user and the TSM KM user. These scripts are stored under KM_HOME path, normally PATROL_HOME/TSM. i=0; sudoers=""; foreach var (grep("^/runtime/tsm/commandcontrols/",pconfig("list"))) { ctl=get(var); opt=ntharg(grep("option",ctl),"2-"," ="); nsa=ntharg(grep("nosudoattempt",ctl),"2-"," ="); sua=ntharg(grep("singleuserattempt",ctl),"2-"," ="); typ=ntharg(grep("commandtype",ctl),"2-"," ="); cmd=nthargf(grep("commandtext",ctl),"2-","=","="); if((typ == "") (typ == "OS")) { met=""; if(opt == "NoLogin") { met = "(run as patrol user)"; } elsif(nsa == "YES") { met = "(run as configured user without sudo)"; } elsif(sua == "YES") { met = "(run as supplied user - used in menu)"; } else { scmd=cmd; s=index(scmd,"%sudo"); if(s) { scmd=replace(substr(scmd,s,length(scmd)),"%sudo",""); } sudoers=union(sudoers,ntharg(ntharg(scmd,1," "),"1-"," "," ")); } Requirements 18 To list all OS commands used by the TSM KM, execute the following PSL code from the PATROL Console, using PSL Task menu, after installing and loading the KM.

19 printf("(%2d) %-30s %-40s: %s\n",i++,ntharg(var,"5","/"),met,cmd); } } printf("\n\ncommands used with sudo:\n%s",sort(sudoers)); The PATROL Agent user (normally patrol) requires write permission to DSM_LOG directory 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_HOME 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_HOME temporarily during this activity. On Windows platforms the Tivoli Storage Manager installation is identified by checking the registry sub-keys under HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\. The configured login user should have sufficient privileges to run regedit command on the managed node. If a non-root user with sudo privileges is preferred as the TSM 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 TSM KM administration and report menu commands using their sudo privileges. The TSM 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/solaris29sun4/). 19 Requirements Sudo User for Operating System Access

20 This non-root sudo user configured in the KM will be able to execute Tivoli Storage Manager commands. To prevent unauthorized access, ensure this user is only used within the KM and not made public for general use. Entering the non-root sudo user with Use Sudo option selected in to the login configuration dialog, before updating the sudoers file, will generate sudo errors. Also if the sudo user is configured differently, the KM may run sudo commands using incorrect sudo settings, which may expose the sudo user password. 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",env_reset 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. 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 LIBPATH INSTALL_PATH KM_HOME KM_TEMP",env_reset 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/* Requirements 20 User_Alias TSMKMUSERS = user1, user2, user3 Defaults:TSMKMUSERS!lecture,!authenticate,!requiretty,\ env_keep+="path SHLIB_PATH INSTALL_PATH KM_HOME KM_TEMP",env_reset 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/*

21 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 Tivoli Storage Manager KM for PATROL 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 TSM KM. 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 TSM 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 Tivoli Storage Manager, 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 a DES encrypted format. The encrypted password can be viewed by any user who has access to the PATROL Agent configuration variables (pconfig). This user could then execute PSL statements using the encrypted password through the PATROL Console. This can be prevented by setting up an appropriate Access Control List (ACL) for users. Please refer to the PATROL Agent Reference Manual for details on how to set up an ACL. To list all DSMADMC commands used by the TSM 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-"," ="); cmd=nthargf(grep("commandtext",ctl),"2-","=","="); if(typ == "DSMADMC") { printf("(%2d) %-25s: %s\n",i++,ntharg(var,"3","/"),cmd); 21 Requirements DSMADMC command binary is executed using an OS user account matching 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 an 'execute' permission to DSM_CONFIG path and dsmadmc (or dsmadmc.exe) file and a 'write' permission to DSM_LOG path and dsmerror.log file.

22 } } Disk Space Requirements Tivoli Storage Manager KM for PATROL 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 TSM KM is installed under the PATROL installation path. 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. During execution, the TSM 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). Getting the BMC Software Installation Utility In order to install Tivoli Storage Manager KM for PATROL, you need the latest version of the BMC Software Installation Utility. You can download the latest Installation Utility from the BMC Software EPD (electronic product download) from: logon.jsp on the BMC Software Website, or from the Tivoli Storage Manager KM for PATROL page on the Sentry Software Website Choose the appropriate package depending on the platform you plan to install Tivoli Storage Manager KM for PATROL on: Requirements 22 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.

23 For UNIX/Linux systems: ins_all_<version>.tar For Windows systems: ins_windows_<version>.exe The packages are valid for all the PATROL components: Agent, Console, Console Server, etc. Place the Installation Utility package in the same folder as the Tivoli Storage Manager KM for PATROL packages. 23 Getting the BMC Software Installation Utility

24 Packages The Tivoli Storage Manager KM for PATROL packages are available on the Sentry Software Web site. There are two packages, each of which can be used to install the KM on every PATROL component (Agent, Console, etc.) according to the platform you are using: For Windows systems: tsm_all_<version>.exe For UNIX and Linux systems: tsm_all_<version>.tar The Tivoli Storage Manager KM for PATROL packages are designed for use with the BMC Software Installation Utility (formerly known as Thorium). They need to be merged with the latest available version of the BMC Software Installation Utility. Please see instructions. Extracting the Setup Files Like most Knowledge Modules for PATROL, you need to install Tivoli Storage Manager KM for PATROL on the following components of your PATROL architecture: Every managed system with a PATROL Agent Every PATROL Console (Classic) that will show Tivoli Storage Manager performance-related information and alerts The Console Server PATROL Central Web Edition Getting the BMC Software Installation Utility 24

25 Installing the KM

26 Introduction This section describes the installation procedure for Tivoli Storage Manager KM for PATROL on any PATROL component (Agents, Consoles, Console Server, etc.). As the setup is based on the BMC Software Installation Utility, this procedure applies to all operating systems supported by Tivoli Storage Manager KM for PATROL. Installing Tivoli Storage Manager KM for PATROL Installing Tivoli Storage Manager KM for PATROL is an automated process managed by a wizard. The wizard goes through the necessary steps to install Tivoli Storage Manager KM for PATROL and all files associated with it. You are simply prompt for the product's folder location and the product/components to install. Browse to the bmc_products folder where the files have been extracted (both Tivoli Storage Manager KM for PATROL and the Common Installer). 26

27 On Windows: Launch the setup.exe program On UNIX: Launch the setup.sh script To install Tivoli Storage Manager KM for PATROL 1. Allow the perl.exe program to listen on this port: Click Allow access. Installation Wizard - Step 1: Windows Security Alert 27 Installing Tivoli Storage Manager KM for PATROL

28 2. The welcome screen of the installer appears. Click Next to continue. Installation Wizard - Step 2: Welcome Installing Tivoli Storage Manager KM for PATROL 28

29 3. Read the license agreement, click the Accept option and then click Next to continue. Installation Wizard - Step 3: Reviewing License Agreement 29 Installing Tivoli Storage Manager KM for PATROL

30 4. Select Install products on this computer now and click Next to continue. Installation Wizard - Step 4: Selecting Installation Options Installing Tivoli Storage Manager KM for PATROL 30

31 5. Specify the BMC Software products folder. See the BMC Software documentation for more information about the BMC Software products folder. Click Next to continue. Installation Wizard - Step 5: Selecting the Installation Directory 31 Installing Tivoli Storage Manager KM for PATROL

32 6. Select Default. Installing Tivoli Storage Manager KM for PATROL does not require any customization. Click Next to continue. 7. Select one or several of the following options: Managed System to install Tivoli Storage Manager KM for PATROL on a PATROL Agent. Console Systems role to install Tivoli Storage Manager KM for PATROL on a PATROL Classic Console. Common services to install Tivoli Storage Manager KM for PATROL on the Console Server or on PATROL Central Web Edition. Click Next to continue. Installing Tivoli Storage Manager KM for PATROL 32 Installation Wizard - Step 6: Selecting an Installation Type

33 Installation Wizard - Step 7: Selecting Roles Select as many options as required. 33 Installing Tivoli Storage Manager KM for PATROL

34 8. Check the Tivoli Storage Manager KM for PATROL box to install the KM (it should be selected by default). Click Next to continue. Installation Wizard - Step 8: Selecting Products and Components Installing Tivoli Storage Manager KM for PATROL 34

35 9. Review the installation parameters and click Start Install to launch the installation procedure. Installation Wizard - Step 9: Reviewing Installation Options 35 Installing Tivoli Storage Manager KM for PATROL

36 10. The setup program displays the actions performed and indicates the percentage of completion. Once the installation complete, click Next to view the installation results. Installation Wizard - Step 10: Installation Status Installing Tivoli Storage Manager KM for PATROL 36

37 11. The wizard displays the installation results. Click View Log to display a detailed log of the installation procedure. Click Next and then Finish to exit the setup program. Installation Wizard - Step 11: Installation Results 12. Click the Finish button to complete and close the installation wizard. 37 Installing Tivoli Storage Manager KM for PATROL

38 Installation Wizard - Step 12: Completing and closing the Installation Wizard A Help button is available at each step of the procedure. Click to display the installation online help. The Exit button allows you to stop the installation procedure. Installing Tivoli Storage Manager KM for PATROL 38

39 Uninstalling Tivoli Storage Manager KM for PATROL Uninstalling Tivoli Storage Manager KM for PATROL is an automated process managed by a wizard. The wizard goes through the necessary steps to remove Tivoli Storage Manager KM for PATROL and all files associated with it. You are simply prompt for the product's folder location and the product/components to uninstall. To uninstall Tivoli Storage Manager KM for PATROL 1. Locate the Uninstall folder under the BMC products directory (typically under C:\Program Files\BMC Software, or /opt/bmc): On Windows systems, launch uninstall.exe On UNIX, launch uninstall.sh Un-install Wizard Welcome Step 39 Installing Tivoli Storage Manager KM for PATROL

40 2. Specify the BMC Software products folder. See the BMC Software documentation for more information about the BMC Software products folder. Un-install Wizard Specifying folder Uninstalling Tivoli Storage Manager KM for PATROL 40

41 3. To uninstall the KM, select Tivoli Storage Manager KM for PATROL. Un-install Wizard Selecting Products and Components Directory 41 Uninstalling Tivoli Storage Manager KM for PATROL

42 4. Click Start Uninstall to run the program. Un-install Wizard Reviewing Selected Products & components and start uninstalling Uninstalling Tivoli Storage Manager KM for PATROL 42

43 5. A page displays the list of products/components processed and the percentage of completion. Click Next to continue. Un-install Wizard Status 43 Uninstalling Tivoli Storage Manager KM for PATROL

44 6. A page displaying SUCCESS indicates that Tivoli Storage Manager KM for PATROL is now uninstalled. Un-install Wizard Uninstall Results If you upgrade (or downgrade) your operating system or Tivoli Storage Manager, the commands for the TSM KM need to be reloaded. Use the menu Reload Commands from the main TSM KM container instance (labeled Tivoli Storage Manager). Performing Post-Installation Operations It is recommended to perform post installation checks once the KM is installed on the PATROL Console to ensure it properly operates. Post-installation operations include: Loading the KM on the PATROL Console Configuring the KM user account Verifying: the application discovery Uninstalling Tivoli Storage Manager KM for PATROL 44 Upgrading the Platform

45 the instance limits the initial setup Restarting the PATROL Agent and PATROL Console. Loading and Unloading the KM Once installed the KM will have to be preloaded on one of the following PATROL consoles: PATROL Console PATROL Central The PATROL Agent can also be configured to automatically preload the KM. Loading the KM Before loading the TSM KM: 1. Make sure you properly installed the KM on PATROL Console and PATROL Agent systems 2. Start the PATROL Console and update the connection to all PATROL Agent systems where the TSM KM is installed. 3. Check the value of the PATROL Agent tuning variable, /AgentSetup/AgentTuning/ pslinstructionmax, and if necessary, increase it. Loading the KM on PATROL Console To load the KM on a PATROL Console: The TSM KM will be loaded to the PATROL Console, and all connected PATROL Agents will start discovering the Tivoli Storage Manager environment. If you want to save the new list of loaded files as the PATROL Console user preference: 1. From the PATROL Console menu bar, choose File > Save Configuration 2. Load the TSM_LOAD.kml file on each PATROL Console. 3. Configure the KMs. 45 Performing Post-Installation Operations 1. From the PATROL Console menu bar, choose File>Load KM Select the TSM_LOAD.kml file, and click Open or OK.

46 Loading the KM on PATROL Central To load the KM on PATROL Central: 1. In the Console, right-click the Managed System and select Load Knowledge Modules... The Load Knowledge Modules wizard is displayed 2. Click Next 3. Select the managed systems where the TSM KM is to be loaded, and click Next>. The wizard will display a list of all available.kml files for the managed systems you selected. 4. Select the TSM_LOAD.kml file for each managed system, click Next> and Finish. If you cannot find the TSM_LOAD.kml file in the wizard list for any system you selected, then the KM has not been installed on that system. The TSM KM will be loaded to the PATROL Central Console Server, and all connected selected managed systems will start discovering the Tivoli Storage Manager environment. 5. Load the TSM_LOAD.kml file on each PATROL Central Management Profile where TSM KM is to be loaded. 6. Configure the KMs. Configuring PATROL Agent to Preload the KM To configure PATROL Agent to preload the KM: The same menu is used to remove the TSM KM files from the preloaded KMs list. Unloading the KM This section describes the procedures for unloading (not uninstalling) the TSM KM from the PATROL Agent, PATROL Console or PATROL Central Console. The intention is that this section is only used if you no longer want to use some parts of the KM, though there may be circumstances where you may wish to fully unload the KM without uninstalling the files; if you want to completely uninstall the KM, refer to the uninstall procedure. When the KM is unloaded: Performing Post-Installation Operations In order to enable Tivoli Storage Manager KM for PATROL to operate all the time, without a PATROL Console connection, the KM should be added to the PATROL Agent configuration variable /AgentSetup/preloadedKMs. This can be achieved on the Tivoli Storage Manager instance by using the menu Configuration>Preloading. The KM Preloading dialog will be displayed 2. Select Add to add the KM files to the list of preloaded KMs. If the TSM KM is successfully added to the list, an acknowledgement will be displayed.

47 from a PATROL Agent: PATROL stops monitoring the Tivoli Storage Manager application on that system when there is no connection to a PATROL Console with TSM KM loaded. from PATROL Console: the PATROL Console stops displaying and monitoring the Tivoli Storage Manager application on any PATROL Console connected system. Unloading the KM from the PATROL Agent To unload the KM from the PATROL Agent: 1. Remove the TSM KM from the list of preloaded KMs using the menu Configuration>Preloading from the Tivoli Storage Manager instance. Alternatively, using the utility wpconfig (on Microsoft Windows) or xpconfig (on Unix), remove TSM_LOAD.kml from the PATROL Agent configuration variable /AgentSetup/preloadedKMs. 2. Restart the PATROL Agent. 3. Repeat these steps on every PATROL Agent system (managed node) where the TSM KM is to be unloaded. The TSM KM cannot be partially unloaded from the PATROL Agent using the above steps. If you need to unload some parts of the KM from the PATROL Agent, refer to the PATROL Agent Reference Manual. Unloading the KM from the PATROL Console Application classes are unloaded individually. This allows for a partial unloading of the KM to enable it to run as a reduced installation. To unload the TSM KM completely or partially: 1. Remove the unwanted TSM KM application classes from the list of loaded application classes, as required. All TSM KM application classes start with TSM_. From the PATROL Console main window choose Attributes> Application Classes... Select a TSM KM application class to be removed and choose Edit>Delete. Repeat for all classes to be removed. With the PATROL Console for MS Windows: From the PATROL Console tree view choose the KM tab and expand the folder Application Classes. Right-click on a TSM KM application class to be removed and choose Delete. Repeat for all classes to be removed. 2. Select File>Save Configuration to save the modified list of loaded application classes as the PATROL Console user preference. 3. Repeat these steps on every PATROL Console system where the TSM KM is to be unloaded. 47 Performing Post-Installation Operations With the PATROL Console for Unix:

48 Unloading the KM from the PATROL Central Console A KM can be unloaded from particular managed systems or for all systems across the monitored environment. Application classes may be unloaded individually, or by selecting all classes at once. This allows for a partial unloading of the KM to enable it to run as a reduced installation on some or all of the managed systems. To completely or partially unload the TSM KM from some or all of the managed systems: 1. Right click on the PATROL Main Map, and choose Unload Knowledge Modules Select the managed systems where the TSM KM is to be unloaded, and click Next>. 3. Select the TSM KM application classes to be removed that starts with TSM_ for the appropriate managed systems, click Next> and Finish. 4. Repeat the above steps for each PATROL Central Management Profile where the TSM KM is to be unloaded. Configuring the KM User Account A user account with administrative privileges must be configured in BMC PATROL to read and execute Tivoli Storage Manager application programs and file systems. Depending on the operating systems used, several options will be available. On Unix platforms, you can use the following user accounts: a root user a non-root user, such as patrol, that has sudo privileges on Tivoli Storage Manager to 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: Performing Post-Installation Operations 48

49 an administrator user a non-administrator account, such as patrol, configured in the Tivoli Storage Manager application to administer the Tivoli Storage Manager application. Step 1: Configure the KM User Account: 1. In the Console, right-click the Tivoli Storage Manager instance > Configuration>Login. The Login Configuration dialog is displayed: 2. To use: the default PATROL Agent Account, check the Use Agent Default Account box. The login details entered in the Username and Password fields will then be ignored. a different user account, enter the login details in the Username and Password fields 3. If a sudo user account is used: check the Use Sudo box click SUDO Binary File to verify the sudo binary file path 4. Click OK. If the credentials are not valid, the TSMLoginStatus parameter will appear in suspicious state after the next data collection. 49 Performing Post-Installation Operations Login Configuration dialog

50 The password is stored in the PATROL Agent in a DES encrypted format. The encrypted password can be viewed by any user who has access to the PATROL Agent configuration variables (pconfig). This user could then execute PSL statements using the encrypted password through the PATROL Console. This can be prevented by setting up an appropriate Access Control List (ACL) for users. Please refer to the PATROL Agent Reference Manual for details on how to set up an ACL. Step 2: Configure the Admin Interface Login 1. In the Console, right-click the Tivoli Storage Manager instance > Configuration > Admin Interface Login. The Admin Interface Login Configuration dialog is displayed: 3. Enter the login details for the KM user for DSMADMC (suggested name is patrol) 4. Select Create new account if you want the KM to create a new account if it has not already been set up. This operation requires a DSMADMC user account with administrative privileges. 5. Click DSMADMC Binary File to verify its location 6. Click OK. If the credentials are not valid, the TSMLoginStatus parameter will appear in suspicious state after the next data collection. Performing Post-Installation Operations 50 Admin Interface Login Configuration dialog

51 Verifying Application Discovery To verify the application discovery: 1. Check that the TSM_SETUP instance is actually named Tivoli Storage Manager. If not, force a full discovery by right-clicking the TSM_SETUP instance > KM Commands > Force Discovery 2. Check that the application class instances are actually instantiated. The initial data collection may take some time depending on the complexity of your environment (up to one hour). If needed, force a data collection by right-clicking the Tivoli Storage Instance instance > KM Commands > Refresh Parameters. If the Tivoli Storage Manager server is configured in a clustered environment, you'll have to enable and enable Multi-node Mode monitoring. Checking the Instance Limits Tivoli Storage Manager KM for PATROL automatically sets the number of instances that will be displayed in the Console for each monitored elements. This configuration, set to offer maximum performance, can however be modified to better suit your environment. Because increasing the number of instances may impact the performance of the KM, it is recommended to only monitor critical elements in large environments. To modify the default configuration 1. In the Console, right-click the Tivoli Storage Manager instance > Configuration> Instance Limits 2. Enter the number of instances to be displayed in the console for each monitored element 3. To disable the monitoring of a specific application class, enter 0 in the relevant field 4. Click OK. 51 Performing Post-Installation Operations

52 Checking the Initial Setup of the KM To check the initial setup of the KM: 1. Check whether the discovered files and directory paths are correct, using the menu Configuration > Paths from the Tivoli Storage Manager instance. 2. Check whether the discovered Node Type is correct using the menu Configuration > Node Type from the Tivoli Storage Manager instance. 3. Check the InfoBoxes and Parameters of all the TSM KM instances and verify that they are set correctly. 4. Under each container instance, open all detail parameters (text parameters with names in the format TSM<Obj ect>details), and check for error messages. 5. Check the new values of parameter TSMLoginStatus set after completion of all data collection. If either is not in OK state, open the annotation point to determine the cause of the error. 6. After the KM has been running for at least an hour, run the menu Configuration > KM Status from the Tivoli Storage Manager instance. A report is displayed, detailing information on the managed system. Check through the report for any warnings or alarms. If any errors are found during any of the above steps (including any incorrect data in Infoboxes or any warnings or alarms in the KM Status report), determine the cause(s) and take steps to resolve these errors. You may need to refer to the User Guide or contact Technical Support at Sentry Software, attaching the KM Status report. To save the KM Status report as a task window, click Save As Task. This task window can then be printed or saved as a text file. It should not be necessary to re-start the PATROL Agent and/or PATROL Console. However, it is a good practice to confirm that Tivoli Storage Manager KM for PATROL operates correctly after a restart of PATROL Agent and/or PATROL Console. In addition, the PATROL Agent restart will force all KM discoveries and data collections to start immediately. Performing Post-Installation Operations 52 Restarting PATROL Agent and PATROL Console

53 Integrating the KM

54 Introduction This section provides detailed information about the integration of Tivoli Storage Manager KM for PATROL with BMC ProactiveNet Performance Management. Integrating with BMC Portal Log on to BMC Portal with appropriate credentials to add infrastructure elements. Click on Configure tab. Under Tasks, select Elements to open the Elements page. Click Add. Select Infrastructure Element, and click Next. Select appropriate RSM, and click Next. Enter the label for the element, select PATROL Integration, and click Next. Select/create a group name, and click Next. Select appropriate method to discover the PATROL Agent hosts, and click Next. Fill the required details for discovering the PATROL Agents, and click Commit. Integrating with BMC ProactiveNet Performance Management 8.5.x and 8.6.x To integrate a BMC PATROL KM into BMC ProactiveNet 8.5.x or 8.6.x, you need to create a specific adapter. An adapter for BMC PATROL facilitates pulling of performance data from existing BMC PATROL solutions into BMC ProactiveNet. Using an Adapter, you can import BMC PATROL application classes (provided in a Knowledge Module KM) into BMC ProactiveNet. The Adapter periodically synchronizes the performance data collected by these application classes into BMC ProactiveNet. 54 Overview

55 Creating and Importing an Adapter for a BMC PATROL KM Creating an Adapter for a BMC PATROL KM 1. Open the BMC ProactiveNet Administration Console. The BMC ProactiveNet Administration Console is displayed as shown in the following figure: 2. Right-click the Adapters folder and select Import Monitor Type and Add Adapter > BMC PATROL. 3. In the Configuration tab, enter the required information: In the Instance Name field, enter a name for this instance of the Adapter that will perform the integration of the targeted KM into BMC ProactiveNet. Select the Agent where this instance of the Adapter will be executed Enter the Integration Service Agent hostname or IP address Enter the Integration Service Agent Port. The default port is Enter the required credential to connect to the Integration Service Agent 4. Click Next to continue 5. Click Next to let the system load the BMC PATROL application classes. 6. Select the application classes to import 7. Click Next to start the import process. The system displays a summary of the application class import, click Next to continue. 8. Select the application classes you wish to auto-synchronize with the Integration Service Agent. 9. Click Next to continue 10. Set the Filter details if need. 11. Click Next to continue. 12. Set the Auto-sync poll scheduling, if needed. 13. Click Next to continue. The system displays a summary of your settings, click Finish to confirm. The Adapter has been added to the Adapters folder of the Administration Console. 14. To see the class instances that have been imported by the Adapter, expand the Adapters folder, right-click the Adapter and select Details. We strongly recommend that you create a specific adapter for each KM you need to integrate into BMC ProactiveNet to enable the update of a single KM independently. 55 Integrating with BMC ProactiveNet Performance Management 8.5.x and 8.6.x Unselecting will delete the application classes that have already been imported during a previous operation. Application classes ready to be deleted are marked with a red x.

56 Updating an Adapter for a BMC PATROL KM Updating an Adapter 1. Delete the Adapter instance 2. Go through the Add an Adapter wizard to actually delete the monitor types that had been created based on the previous version of the KM 3. Close 4. Resume the entire Creating an Adapter for a BMC PATROL KM procedure For complete and detailed information on these procedures, please refer to the BMC ProactiveNet documentation available from BMC Web site. Importing and Customizing Thresholds 1. Launch the BMC ProactiveNet PW Commands. On Windows 2008, you need to run the PW Commands as Administrator. 2. Execute the following command line: pw adapter -type patrol -get_thresholds <file name> -pproxy_host <hostname ipaddress> [-pproxy_port <port_number>] [-pproxy_user <username>] [-pproxy_passwd <password>] -i -v where -get_thresholds <file name> = File name with absolute path at which thresholds will be imported -pproxy_host <hostname ipaddress> = Host name or IP Address of Patrol Proxy Server -pproxy_port <port_number> = Port at which Patrol Proxy Agent communicates with Patrol Proxy Server -pproxy_user <username> = User name of Patrol Proxy user -pproxy_passwd <password> = Password to authenticate Patrol Proxy user -i = import Instance level thresholds -v = run in "verbose" mode, producing extra lines of output during extraction and conversion processes 3. Open the file in a text editor. Check that the global thresholds have been properly interpreted. 4. Then go to the # INSTANCE LEVEL THRESHOLDS section of the file. 5. Uncomment all instance level thresholds for the _PATROL TSM_ prefixed instances. Search the file for the 'NOT_IMPLEMENTED' occurrences to detect thresholds that were not properly converted by the PATROL Adapter. 6. Save the file. 7. Execute the following command: pw threshold loadpatrolthreshold [<thresholdfilename> [-v]] where: <thresholdfilename> is a thresholds file name. If no file path is specified then the default '<Installation Directory>/pw/tmp/' is used Integrating with BMC ProactiveNet Performance Management 8.5.x and 8.6.x 56 The command has produced a text file with all the parameter threshold settings.

57 -v enables the Verbose mode Class-level thresholds can be displayed using the Absolute Global Thresholds panel in the BMC ProactiveNet Operator Console, while instance-level thresholds are displayed in the Absolute Instance Thresholds panel. Managing Baselines and Key Performance Indicators In order to facilitate the detection of abnormalities on your monitored environment, BMC ProactiveNet calculates baselines per parameter (metrics or attributes) 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 parameters are identified by default as Key Performance Indicators and therefore automatically included in the base lining calculation. Managing baselines The baseline is the expected normal operating range for a metric or attribute of a monitor. The baseline is calculated by collecting the values for a monitor s attributes and metrics over a specified time period and establishing a low baseline value (consisting of the 10th percentile of all the values for a given time period) and a high baseline value (consisting of the 90th percentile of all the values for a given time period), taking a weighted average of these values over time. A higher weight is given to the latest data being factored into the baseline average. The accuracy of the baseline improves over time. For baselines to be generated for an attribute, that abnormality threshold means that the threshold exists and is not suppressed. Additionally, if the Key Performance Indicator (KPI) mode is active, only those attributes that have an active abnormality threshold and are also KPI attributes will have baselines generated for them. Absolute thresholds (with "outside baseline") or signature thresholds do not satisfy these requirements. Managing Key Performance Indicators The KPI attribute of a parameter can be activated or deactivated manually through the BMC 57 Integrating with BMC ProactiveNet Performance Management 8.5.x and 8.6.x Requirements for baseline generation

58 ProactiveNet Administration Console. In this KM, some parameters or attributes have been designated as important indicators of performance (KPIs). We do not recommend that these default settings are modified. However, advanced users may activate or deactivate KPIs from the BMC ProactiveNet Administration Console. To add or remove Key Performance Indicator (KPI) attributes for a monitor type 1. In the Administration Console, from the menu bar, choose Tools > KPI Administration. The KPI Administration dialog box is displayed. 2. From the Monitor Type list, choose the monitor type for which you want to add or remove KPI attributes. A list of attributes for the selected monitor type is displayed. 3. In the KPI column for the attributes that you want to add or remove as Key Performance Indicators: select the KPI check box to add the corresponding attribute as a KPI deselect the KPI check box to remove the corresponding attribute from the KPIs for that monitor type For complete and detailed information on this procedure, please refer to the BMC ProactiveNet documentation available from BMC Web site. Parameters for which the system by default calculates baselines as well as parameters considered as KPIs are respectively identified by the following icons: Baselining KPI Integrating with BMC ProactiveNet Performance Management 8.5.x and 8.6.x 58

59 Monitoring your Environment

60 Tivoli Storage Manager KM for PATROL helps ensure the availability, maximum performance, and integrity of your backup servers, thereby protecting associated data sets. Administering Tivoli Storage Manager Tivoli Storage Manager KM for PATROL provides secure server administration menus, which can be executed by PATROL Console users, if they have appropriate privileges. They can more especially: Starting/stopping the server Starting/stopping the storage agent Administering mount requests Administering drives Cancelling processes. Starting/Stopping the Server In the Console, right-click the Tivoli Storage Manager instance > KM Commands and select: Administration > Start Server Administration > Stop Server whether you want to start or stop the server. Starting/Stopping the Storage Agent In the Console, right-click the Tivoli Storage Managed instance > KM Commands and select: whether you want to start or stop the storage agent. Administering Mount Requests Each time a mount request appears, an alert is triggered on the TSMRequestTimeout parameter. Some requests will automatically continue processing, others will require that you notify that the requested action was actually performed. To send the notification, right-click the relevant mount request instance > Administration > Reply To cancel: 60 Administration > Start Storage Agent Administration > Stop Storage Agent

61 a mount request, right-click the relevant mount request instance > Administration > Cancel all mount requests at once request, right-click the Mount Requests instance > A mount request can be canceled from the relevant mount request instance, using the menu Administration > Cancel, or you can cancel all mount requests at once from the container instance (labeled: Mount Requests) using the menu Administration > Cancel All. Administering Drives To administer manual or automatic library drives, right-click the relevant drive instance and select one of the following options: Administration > Clean Drive Administration > Online Drive Administration > Offline Drive Cancelling Processes To administer processes, right-click the relevant process instance and select Administration > Cancel Process. Configuring the KM If a customization menu is accessed from the container instance and you make a change, you then have the option to apply this change to all child instances which appear under the selected container in PATROL Console instance topology. If a customization menu is accessed from the child instance, it will only modify the configuration applicable for that instance. In the absence of a child instance level configuration, the KM will search for any modified configuration through its topological parent path. If no customized configurations found, the KM will use the default configuration. 61 Administering Tivoli Storage Manager Tivoli Storage Manager KM for PATROL can be customized and optimized to suit your Tivoli Storage Manager application environment. This section describes all menus available for customizing the TSM KM. These customization menus are accessed from the knowledge module command sub-menu Configuration> from each application instance. Most of these customization menus can be accessed either from the parent container level or from the child instance level.

62 If a menu command is named Configuration > Client(s), it means that the menu command is available as Configuration > Client from the parent container instance (client container instance) and Configuration > Clients from the child instance (individual client instance). Configuring Paths The solution automatically discovers the installation, binary, and library paths. This information can however be overridden. Altering these paths may impact the operation of the KM. To configure paths: 1. In the Console, right-click the Tivoli Storage Manager instance > KM commands > Configuration > Paths 2. In the KM section, verify and possibly modify the Home, Temp, and Debug Directory Paths 3. In the TSM section, verify and possibly modify the Installation and the DSM_DIR, DSM_LOG Directory Paths, and the DSM_CONFIG File path 4. In the Binary Paths and Library Paths sections: From the list, select the paths to be removed In the Path field, enter the new path(s) to be included. If several paths are to be entered, separate them with a colon (:) for Unix, with a semi-colon (;) for Microsoft Windows. 5. Click OK. If you want to rediscover the paths, empty all fields, click OK, and restart the PATROL Agent. Configuring the KM 62

63 Specifying the Node Type You may have to manually indicate the type of node monitored if the discovery fails to recognize it: 1. In the Console, right-click the Tivoli Storage Manager instance > KM Commands > Configuration > Node Type Specifying the Node Type 2. Select the node type 3. Click OK. 63 Configuring the KM

64 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, the TSM 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. To configure the multi-node monitoring mode: 1. In the Console, right-click the Tivoli Storage Manager instance > KM Commands > Configuration > Monitoring Mode 2. Select Multi-node Mode 3. Select the appropriate Clustering Application 4. Indicate the Failover Group Name. Leave this field blank if you previously selected Veritas Cluster File System. The TSM KM will then 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. 5. Enable Remote PATROL Agent Checking to check the monitoring status of the other nodes and click OK. You'll then have to indicate all the information required to communicate with the remote PATROL Agent (authentication server, protocol, port number, and credentials) 6. Click OK. Tivoli Storage Manager will then be monitored through the active or online TSM Server 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. Configuring the KM 64 Configuring the Multi-Node Monitoring Mode

65 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. Filtering Elements to Monitor 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 apply filters to indicate which elements will be monitored or not. Some instances have specific monitoring rules: - Daemons: Only the Server Daemon or the Storage Agent Daemon is monitored - Jobs: Future jobs are not monitored by the TSM KM - Automated libraries and manual drives: On a Storage Agent, only the local automated libraries and local manual drives discovered will be monitored To filter the elements to be monitored: 65 Configuring the KM

66 1. In the Console, right-click the instance for which you want to filter the elements to be monitored and select KM Commands > Configuration> The Elements to be f iltered The [ALL] entry ensures that all the elements found during PATROL discovery are instantiated and monitored. 2. To enable elements for monitoring: In the current configuration list, select the elements to enable Select Enable Click Update A log filter will have to be configured if you enable log files for monitoring. Configuring the KM 66 Client Configuration dialog

67 3. To disable elements for monitoring: In the current configuration list, select the elements to disable Select Disable Click Update All jobs associated to disabled domains are not monitored. Disabled instances will be instantiated in an OFFLINE state. Commands will not be executed, thus leaving parameters not set. 4. To delete elements for monitoring: In the current configuration list, select the elements to delete Select Delete Click Update 5. To add a new element to monitor: Type the name of the element to be monitored If needed, enter a description From the Status list, select Enable Click Update. To revert to the default monitoring configuration, type [default] as a new entry and click Update. 6. Resume the procedure for all the application classes for which you wish to apply monitoring filters. By default, Tivoli Storage Manager KM for PATROL monitors all mount requests for 1 day, all scheduled jobs that completed successfully for 1 day and any other scheduled job for 3 days, and all executed TSM internal server processes for 3 days. You can however modify these settings to better suit your requirements: Increasing the monitoring period may affect the performance of the application. 67 Configuring the KM Configuring Monitoring Periods

68 Configuring the Jobs Monitoring Period Job Filter Configuration dialog 2. Indicate how long the jobs in OK, Suspicious, and Failure status will be monitored. If you: decrease the monitoring period, older jobs will be destroyed on the next data collection cycle increase the monitoring period, you'll have to force a full data collection to ensure all jobs are instantiated. To force data collection, right-click the Jobs instance > KM Commands > Force Full Collection Configuring the KM In the Console, right-click the Jobs instance > KM Commands > Configuration > Jobs

69 3. Uncheck Keep Monitoring Active Jobs Indefinitely if you prefer not to monitor active jobs endlessly and remove them from console when they exceed the monitoring duration above 4. Uncheck Ignore Inactive Jobs Initially if you don't want to discover and monitor completed/ inactive jobs during initial discovery cycles 5. Click OK. All jobs associated to disabled domains are not monitored. Configuring the Mount Request Monitoring Period 1. In the Console, right-click the Mount Requests instance > KM Commands > Configuration > Mount Requests Mount Request Filter Configuration Dialog 69 Configuring the KM

70 2. Indicate how long the mount requests will be monitored. If you decrease the monitoring period, older mount requests will be destroyed on the next data collection cycle 3. Click OK. Configuring the Processes Monitoring Period 1. In the Console, right-click the Processes instance > KM Commands > Configuration > Processes 2. Indicate how long the processes will be monitored. If you: decrease the monitoring period, older processes will be destroyed on the next data collection cycle increase the monitoring period, you'll have to force a full data collection to ensure all processes are instantiated. To force data collection, right-click the Processes instance > KM Commands > Force Full Collection 3. Click OK. Configuring the KM 70 Process Filter Configuration Dialog

71 Configuring the Elements Status The status of an element is determined by the State parameter and by the status mapping rule. This mapping rule indicates which states will trigger a warning or an alarm on the Status parameter. It can be configured as follows: 1. In the Console, right-click the parent or child instance for which you want to configure status and select > KM commands > Configuration > Instance Status Client Status Configuration dialog 71 Configuring the KM

72 2. In the Warning Filter State Rules list, select the states that will not trigger a warning 3. If needed, apply a time condition to a specific state. For example, if you want to trigger a warning when the Unknown state of the Client instance lasts more than 30 minutes: From the State list, select -1 (Unknown) From the Condition list, select > In the Minutes field, enter In the Alarm Filter State Rules list, select the states that will not trigger an alarm 5. If needed, apply a time condition to a specific state. For example, if you want to trigger an alarm when the Never Communicated state of the Clients instance lasts more than 60 minutes: From the State list, select 2 (Never Communicated) From the Condition list, select > In the Minutes field, enter Click Update. To revert to the default status mapping rule for either filter, select [default] from the list of states and click Update. 7. Click Close. If this menu was accessed at a parent (container) level, the new mapping rule applies to all components available under that parent instance. To modify the mapping rule for a selected component, access the menu at the child component instance level. A log error filter can be configured to specify the regular expressions that will generate a warning or an alarm. Each time the KM will find these expressions in a log file or in TSMLogText, the error message will be written to the TSMLogAlarmText or TSMLogWarningText parameter. By default, the default log filter is configured for the Server Activity Log and the system log file. If you enabled additional log files for monitoring, you will have to customize the log filter by adding appropriate expressions for those log files. For an explanation of the possible error messages in the log files, refer to the Tivoli Storage Manager System Administrator s Guide and the Tivoli Storage Manager Troubleshooting Guide. To configure the log error filter: Configuring the KM 72 Configuring the Log Filter

73 1. In the Console, right-click the Logs instance > KM Commands > Configuration > Logs Filter 2. In the Warning Filter Expressions list, select the expressions that will not trigger a warning 3. In the Alarm Filter Expressions list, select the expressions that will not trigger an alarm 4. To add a new regular expression to the warning or alarm filter: In the Expression field, indicate the regular expression to be included (e.g.: skipping) Select Include Regular expressions are case-sensitive. 5. To exclude a regular expression from the warning or alarm filter: In the Expression field, indicate the regular expression to be excluded (e.g.: otlsol01). You can also limit the exclusion to a particular expression already listed by using standard wildcard syntax, such as ANR2121W or ANR21[0-9].W.. Select Exclude 73 Configuring the KM Log Filer Configuration dialog

74 6. Click Update. To revert to the default settings for either filter, type [default] as a new error expression for that filter, and click Update. If you revert to the default settings when accessed from the log instance level, the settings will revert to the parent or container instance level. To revert to the shipped default settings (as shown above), access this dialog from the log container instance. From this level you will also have the option to reset the configuration of any modified child instances. Configuring the Log Scan Limit The TSM KM 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 KM, and the PATROL Agent. To customize the log scan limit: 1. In the Console, right-click the Log(s) instance > KM Commands > Configuration > Log Scan Limit Configuring the KM 74

75 2. Indicate the amount of data that will be read by the KM during each data collection cycle 3. Indicate the maximum query limit (in minutes). By default the KM queries up to 300 minutes (5 hours) of actlog data. (only available from an actlog instance) 4. Click OK. 75 Configuring the KM Configuring Log Scan Limit

76 Configuring Domain Backup Restriction TSM KM can be configured to trigger a warning when a backup is started during a specific period of time: 1. In the Console, right-click: the Domains instance > KM Commands > Configuration> Domains Backup Restriction to apply this customization to all policies a Domain instance > KM Commands > Configuration> Domain Backup Restriction to apply this customization to a specific policy 2. Select Enabled 3. Indicate the Restriction Start and End Time. The restriction window must at least last 5 minutes. 4. Click OK. Configuring Alert Acknowledgement By default, alerts will automatically be acknowledged unless you modified the following settings to allow manual acknowledgement. Manual acknowledgement may impact the performance of the application and of the PATROL Agent if the number of alerts waiting to be acknowledged constantly increases. Configuring the KM 76 Domain Backup Restriction Window dialog

77 Configuring Logs Alert Acknowledgement By default, log alerts are automatically acknowledged when new ones are detected. To change the default behavior: 1. In the Console, right-click the Logs instance > KM Commands > Configuration> Log Alert Acknowledgement 2. Indicate whether the warning and alarm messages will be manually or automatically acknowledged 3. Click Ok. Configuring Jobs Alert Acknowledgement By default, the alerts triggered on the TSMJobStatus parameter for the completed jobs are not acknowledged. If you want these alerts to be automatically acknowledged, you'll have to configure the job alert acknowledgement as follows: 77 Configuring the KM Configuring Log Alert Acknowledgement

78 1. In the Console, right-click the Jobs instance > KM Commands > Configuration > Job Alert Acknowledgement Configuring Job Alert Acknowledgement 2. Indicate whether the warning and alarm messages will be manually or automatically acknowledged 3. Click Ok. Configuring Process Alert Acknowledgement If you want alerts to be automatically acknowledged, you'll have to configure the process alert acknowledgement as follows: Configuring the KM 78

79 1. In the Console, right-click the Processes instance > KM Commands > Configuration > Process Alert Acknowledgement Configuring Process Alert Acknowledgement 4. Indicate whether the warning and alarm messages will be manually or automatically acknowledged 5. Click Ok. Refreshing Parameters Forcing All Discoveries To force all discoveries, right-click the Tivoli Storage Manager instance and select: Refresh Process Cache to refresh the PATROL Agent process cache Force Discovery. The discovery will then be forced on all the KMs loaded on the PATROL Agent and on all the KM applications classes. 79 Configuring the KM This section describes how to manually refresh parameters without waiting for an automatic polling cycle.

80 Forcing All Data Collectors To force all data collectors, right-click the Tivoli Storage Manager instance and select: Refresh Process Cache to refresh the PATROL Agent process cache Refresh parameters to force all data collectors at the same time. The TSM KM data collectors and all the data collectors defined under the application classes loaded on the PATROL Agent will then be refreshed. Forcing Selected Data Collectors This option is only available from a PATROL Developer Console. 1. Right-click the Tivoli Storage Manager instance and select Refresh Process Cache to refresh the PATROL Agent process cache. 2. Force a data collector to execute immediately as follows: With the PATROL Central Console Right-click the main Tivoli Storage Manager container instance Select the Parameter List tab Select the required data collector Click Update. With the PATROL Console for MS Windows With the PATROL Console for Unix Right-click the main Tivoli Storage Manager container instance and choose Customize > Parameters... Select the required data collector. Click on Options > Update. Forcing Full Data Collection for Jobs By default, the TSMJobCollector only searches for new jobs started since the last collection cycle. However, it can be forced to search for all jobs within the monitored time period during the next collection cycle. To force full data collection for jobs, right-click the Jobs instance and select Force Full Collection. Configuring the KM 80 Right-click the main Tivoli Storage Manager container instance and choose Parameters without Icons... Select the required data collector. Click Update.

81 If the Jobs container instance is not instantiated, this menu command cannot be accessed. The PATROL Agent needs to be restarted to force a full data collection for jobs. 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. Enabling the Debug Mode 1. In the Console, right-click the Tivoli Storage Manager instance > KM Commands > Configuration > Debug. The TSM KM Debug Configuration dialog will be displayed: Enabling the Debug Mode 81 Configuring the KM

82 Object Debug Switch Application Classes Collector Parameters Server TSM_SERVER TSMCreateDistribution TSMUpdateAgent Database TSM_DATABASE_CONTAINER TSM_DATABASE TSMDatabaseCollector Log TSM_LOG_CONTAINER TSM_LOG TSMLogCollector Client TSM_CLIENT_CONTAINER TSM_CLIENT TSMClientCollector Device (Automated Library / Drive) TSM_LIBRARY_CONTAINER TSM_LIBRARY TSM_LDEVICE TSM_DEVICE_CONTAINER TSM_DEVICE TSMLibraryCollector TSMDriveCollector Daemon TSM_DAEMON_CONTAINER TSM_DAEMON TSMDaemonCollector Pool TSM_POOL_CONTAINER TSM_POO TSMPoolCollector Backup (Domain / Job / Mount Request) TSM_POLICY_CONTAINER TSM_POLICY TSM_PCLIENT TSM_JOB_CONTAINER TSM_JOB TSM_MOUNT_CONTAINER TSM_MOUNT TSMDomainCollector TSMJobCollector TSMRequestCollector Process TSM_PROCESS_CONTAINER TSM_PROCESS TSMProcessCollector 3. Set the Debug Options: In the Debug End Time field, indicate the date and time after which debug information will no longer be logged. In the Debug Path field, indicate where the debug file will be stored (by default: <PATROL_HOME>/lib/TSM/debug on Unix systems; %PATROL_HOME%\lib\TSM\debug on Microsoft Windows systems). The debug folder must have at least 10MB of available disk space and read, write and execute permissions for both PATROL Agent user and the TSM KM login user Select Send to File(s) to write all debug messages in a file or set of files. Select Send to Task Window to view the debug messages as they occur in the TSM Debug Output window. Before selecting this option, make sure the PATROL Console is connected to the PATROL Agent. Select Both (Recommended) to send the debug messages both to a file and task window. Configuring the KM Select On for the debug switch(es) you want to enable. Refer to the table below to know the application classes and collector parameters included in the debug switch:

83 4. Click OK first to start TSM KM debugging 5. Click Yes to reload the KM and capture debug from the initial collection cycle. Disabling the Debug Mode The debug switches will be turned off automatically when the debug end time is reached. A tar/ zip file is then automatically created under <PATROL_HOME>/lib/TSM/ and can be sent to the BMC Support for help. It is also recommended to check the SOW or TSM.log file, stored in <PATROL_HOME>/log, for any error. If you want to manually stop debugging: 1. Access the TSM KM Debug Configuration dialog 2. Select Off for the debug switch(es) you want to disable 3. Click OK. Preparing the Debug Files for Sending to Sentry Software If you chose to only send the output to a task window, you can save the debug output as follows: Right-click in the TSM KM Debug Output window. Select Save As and specify a location to save data. Click Yes to compress the files into a: tsm_km_debug_<date>_<time>.tar.z file (Unix systems). This file could later be found in $PATROL_HOME/lib/TSM/ tsm_km_debug_<date>_<time>.zip file (Windows systems). This file could later be found in %PATROL_HOME%\lib\TSM\ Click No if you do not want to compress the files. You will then be asked if you want to retain or delete them. If the compressed file is not created successfully, you can create it manually by including all files and subdirectories under $PATROL_HOME/lib/TSM/ (on Unix) or %PATROL_HOME%\lib\TSM\ (on Microsoft Windows). Appending Output Data to Existing Files If you want to gather output from several debug sessions: 83 Configuring the KM If you chose to send debug information to file(s), you will be asked to prepare the debug files for sending to Sentry Software:

84 Disable the debug mode Click No when asked to prepare the files for sending Choose to Retain the debug files. Start the next debug session. Choose to append the output data to existing files. Reloading Commands All new commands are reloaded automatically but some situations, such as the operating system upgrade or downgrade, may require a manual commands reload. To do so, in the Console, rightclick the Tivoli Storage Manager instance > KM Commands > Reload Commands. Acknowledging Alerts By default, alerts are acknowledged automatically. They can however be acknowledged manually if you do not want to wait for the automatic cycle. Manual acknowledgement will also be required if you modified the alert acknowledgement default settings. Manually Acknowledging Log Alerts When an error is detected in a monitored log file, it will either appear in TSMLogAlarmText or TSMLogWarningText and will respectively trigger an Alarm or a Warning on TSMLogAlarmCount or TSMLogWarningCount. 1. In the Console, right-click the Log instance > KM Commands > Acknowledgement 2. Select: Warning to view, select, and individually acknowledge errors in the TSMLogWarningText parameter Alarms to view, select, and individually acknowledge errors in the TSMLogAlarmText parameter All to acknowledge all alerts (Warnings and Alarms) at once without viewing Manually Acknowledging Job Alerts For a particular job instance, if the TSMJobStatus has a value of 1=Suspicious or 2=Failure, it will be set to alert with a status of Warning or Alarm respectively. These alerts can be acknowledged using the menu Acknowledgement > Alert from the relevant job instance. To acknowledge job alerts: Configuring the KM 84 To acknowledge log alerts:

85 1. In the Console, right-click the Jobs instance > KM Commands > Acknowledgement 2. Select: Acknowledgement > Warnings to view and acknowledge alerts for all jobs with a status of Warning. Acknowledgement > Alarms to view and acknowledge alerts for all jobs with a status of Alarm. Acknowledgement > All to view and acknowledge all job alerts (Warnings and Alarms) at once Acknowledging Process Alerts For a particular process instance, if the TSMProcessStatus has a value of 1=Suspicious or 2=Failure, it will be set to alert with a status of Warning or Alarm respectively. These alerts can be acknowledged using the menu Acknowledgement > Alert from the relevant process instance. To acknowledge process alerts: 3. In the Console, right-click the Processes instance > KM Commands > Acknowledgement 4. Select: Acknowledgement > Warnings to view and acknowledge alerts for all processes with a status of Warning. Acknowledgement > Alarms to view and acknowledge alerts for all processes with a status of Alarm. Acknowledgement > All to view and acknowledge all process alerts (Warnings and Alarms) at once. 85 Acknowledging Alerts

86 Generating Reports The following reports are available in Tivoli Storage Manager KM for PATROL: <Automated Library instance> > Reports > Automated Library Contents - reports the library volume contents of the automated library instance Daemons > Reports > Daemon List - lists all running Tivoli Storage Manager daemons Databases > Reports > Database Backup Volume History - reports server database backup volume history for the last 7 days. <Database instance> > Reports > Database Volumes - reports information about server database volumes and volume copies. <Domain instance> > Reports > Domain Schedule - displays the schedule for the selected domain instance for the next 24 hours Logs > Reports > Activity Log Messages - reports all messages logged today (since midnight) Mount Requests > Reports > Mount Requests - reports a list of all pending mount requests Processes > Reports > Active Processes - reports a list of all active processes on the managed node <Storage Pool instance> > Reports > Volumes List - reports all volumes in the selected storage pool, and their states To save the report as a task window click Save As Task. This task window can then be printed or saved as a text file Generating Reports 86

87 Reference Guide

88 Introduction This chapter provides statistical information about resources, operating status, and performances managed by Tivoli Storage Manager KM for PATROL. It contains tables describing the parameters used in the KM, grouped by Application Classes, and provides a brief description of each parameter and its default settings. 88

89 Classes and Parameters TSM_SERVER TSM_CLIENT_CONTAINER TSM_CLIENT TSM_DAEMON_CONTAINER TSM_DAEMON TSM_DATABASE_CONTAINER TSM_DATABASE TSM_LOG_CONTAINER TSM_LOG TSM_POLICY_CONTAINER TSM_POLICY TSM_PCLIENT TSM_JOB_CONTAINER TSM_JOB TSM_MOUNT_CONTAINER TSM_MOUNT TSM_LIBRARY_CONTAINER TSM_LIBRARY TSM_LDEVICE TSM_DEVICE_CONTAINER TSM_DEVICE TSM_POOL_CONTAINER TSM_POOL TSM_PROCESS_CONTAINER TSM_PROCESS Baselines and Key Performance Indicators Some parameters 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, parameters flagged as KPIs and included by default in the baseline calculation process are respectively identified by the following icons: 89 Classes and Parameters This section lists the application classes of TSM KM. It gives you details on the icons that represent the class, Infobox, parameters and the menu commands available for each application class. There are 14 main application classes and 11 container classes.

90 Baselining KPI TSM_SERVER Icon Parameters Name Description Units Default Alert Conditions BPPM Type ExtraFilesList Is used for pushing TSM KM library files to the PATROL Agent during the "Commit" operation. TSMClientCollector Collects Tivoli Storage Manager client related information. It sets all consumer parameters in TSM_CLIENT_CONTAINER and TSM_CLIENT application classes. By default, this collector is executed only on the server. TSMCreateDistribution Is automatically activated at the end of TSM KM debugging if the customer chooses to "prepare debug files for sending to Sentry Software". It is deactivated on completion. Polling Interval: 300 seconds TSMDaemonCollector Collects Tivoli Storage Manager daemon related information. It sets all consumer parameters in TSM_DAEMON_CONTAINER and TSM_DAEMON application classes. Polling Interval: 300 seconds Classes and Parameters 90 Polling Interval: 600 seconds

91 TSMDatabaseCollector Collects Tivoli Storage Manager server database related information. It sets all consumer parameters in TSM_DATABASE_CONTAINER and TSM_DATABASE application classes. By default, this collector is executed only on the server. Collects Tivoli Storage Manager manual drive related information. It sets all consumer parameters in TSM_DEVICE_CONTAINER and TSM_DEVICE application classes. Polling Interval: 1800 seconds TSMDomainCollector Collects Tivoli Storage Manager domain and client node related information. It sets all consumer parameters in TSM_POLICY_CONTAINER, TSM_POLICY, and TSM_PCLIENT application classes. By default, this collector is executed only on the server. Polling Interval: 900 seconds TSMDriveCollector TSMJobCollector Collects Tivoli Storage Manager backup/restore event related information. It sets all consumer parameters in TSM_JOB_CONTAINER and TSM_JOB application classes. By default, this collector is executed only on the server. Polling Interval: 300 seconds TSMLibraryCollector Collects Tivoli Storage Manager automated library and automated library drive related information. It sets all consumer parameters in TSM_LIBRARY_CONTAINER, TSM_LIBRARY, and TSM_LDEVICE application classes. Polling Interval: 600 seconds TSMLogCollector Collects Tivoli Storage Manager log file related information. It sets all consumer parameters in TSM_LOG_CONTAINER and TSM_LOG application classes. 91 Classes and Parameters Polling Interval: 600 seconds

92 Polling Interval: 1800 seconds Monitors the status of the TSM KM login details (username/ password) for the operating system and DSMADMC. It is set by TSM_SERVER application class discovery. If no valid username/password is detected for the operating system or DSMADMC, this parameter will be set to Failure state. If there are any suspicious command exits, this parameter will be set to Suspicious state. If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. 0 = Ok 1= Suspicious 2 = Failure TSMMonitoringMode* Monitors failover mode of the TSM KM. It is set by TSM_SERVER application class discovery. By default TSM KM runs in Permanent Single-node Mode. Multi-node monitoring can be configured using the KM command Configuration > Monitoring Mode from the Tivoli Storage Manager icon. 0= Permanent Single-node Mode 1= Temporary Single-node Mode 2 = Active Multi-node Mode 3 = Passive Multi-node Mode -1 = Unknown Collection Status TSMNodeStatus* Monitors error messages for the Tivoli Storage Manager application on this managed system. It is set by TSM_SERVER application class discovery. 0 = Ok 1= Suspicious 2 = Failure Availability The value of this parameter is determined by the node status mapping rule defined in the KM command Configuration > Node Status from the Tivoli Storage Manager icon. If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. Classes and Parameters 92 Warning = 1 Alarm = 2 Warning = 1 Alarm = 2 Collection Status TSMLoginStatus*

93 TSMPoolCollector Collects Tivoli Storage Manager storage pool related information. It sets all consumer parameters in TSM_POOL_CONTAINER and TSM_POOL application classes. By default, this collector is executed only on the server. Polling Interval: 1800 seconds TSMProcessCollector Collects Tivoli Storage Manager server process related information. It sets all consumer parameters in TSM_PROCESS_CONTAINER and TSM_PROCESS application classes. By default, this collector is executed only on the server. TSMRequestCollector Collects Tivoli Storage Manager mount request related information. It sets all consumer parameters in TSM_MOUNT_CONTAINER and TSM_MOUNT application classes. By default, this collector is executed only on the server. Polling Interval: 300 seconds TSMUpdateAgent Used by the TSM KM to set the PATROL Agent KM variables when the PATROL Console user is not authorized to update (ACL) any PATROL Agent variables. It is activated automatically when the KM fails to update the PATROL Agent. Polling Interval: 300 seconds For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. InfoBox Name Description Product Name Name of the Knowledge Module. Product Version Version number of the Knowledge Module. Product Release Date Release date of the Knowledge Module. 93 Classes and Parameters Polling Interval: 300 seconds

94 Version number of the PATROL Agent installed on the managed system. Application Name Name of the application monitored by this Knowledge Module. Application Version Monitored application version number. Server(s) Name of the server(s) that the current managed system belongs to. Storage agent(s) Names of the discovered storage agents. Node Name(s) Name of the current managed system (node) as defined in Tivoli Storage Manager. Node Type Type of the node (Server or Storage Agent). Host Name Name of the host as configured on the PATROL Agent. Platform Operating system platform as reported by PATROL Agent (HP, SOLARIS, RS6000 or NT). Operating System Operating system description as reported by PATROL Agent. Installation Path Tivoli Storage Manager software installation path. Binary Path Tivoli Storage Manager software binary paths used by TSM KM. Library Path Tivoli Storage Manager software library paths used by TSM KM Monitoring Mode Monitoring mode of the Knowledge Module Monitoring Node Node currently monitoring Tivoli Storage Manager Copyright Copyright (C) Sentry Software Web Site Support PATROL Agent Version Classes and Parameters 94

95 Function Description Refresh Process Cache Forces the PATROL Agent to reload its process cache from the kernel process list. Force Discovery Forces application discovery. Refresh Parameters Forces an update of the application parameter values. Reload Commands Forces a reload of commands used by TSM KM during the next full discovery cycle. By default, all new commands are reloaded automatically. Administration > Start Server Starts server daemons. Administration > Stop Server Stops server daemons. Administration > Stop Storage Agent Stops storage agent daemons. Administration >Start Storage Agent Starts storage agent daemons. Configuration> Login Accesses the Login Configuration dialog for viewing and entering TSM KM login details for the operating system. This user account should have privileges to execute Tivoli Storage manager administration commands and can use sudo privileges on Unix PATROL Agents. This user account will be used by TSM KM pre-discoveries, discoveries, data collectors, recovery actions, and InfoBoxes to execute operating system commands. It will not be used by any KM commands. The password is encrypted and stored on the PATROL Agent using the BMC PATROL encryption function. Configuration> Admin Interface Login Accesses the Admin Interface Login Configuration dialog for entering and viewing DSMADMC login account details. This admin account (suggested name patrol) is used by the TSM KM to query Tivoli Storage Manager. This user account will be used by TSM KM pre-discoveries, discoveries, data collectors, recovery actions, and InfoBoxes to execute DSMADMC queries. It will not be used by any KM commands. The password is encrypted and stored on the PATROL Agent using BMC PATROL encryption function. Configuration> Preloading Accesses Preloading Configuration dialog, which adds or removes the KM from PATROL Agent variable "/AgentSetup/preloadedKMs". By preloading the NSR KM, the PATROL Agent will monitor the Tivoli Storage Manager application without any PATROL Console connection. Configuration> Monitoring Mode Accesses the Monitoring Mode Configuration dialog, which is used for enabling or disabling TSM KM failover, when monitoring clustered Tivoli Storage Manager environment. Configuration> Paths Accesses the Path Configuration dialog, which displays and sets all paths used by the TSM KM. Paths are automatically discovered by the TSM KM server discovery. They are used as environment variables for executing various Tivoli Storage Manager application commands. Altering these paths may impact the operation of the KM. 95 Classes and Parameters Menu Commands

96 KM paths are used as environment variables and internally: KM_HOME keeps all KM scripts. KM_TEMP is used for creating KM temporary files. KM_DEBUG is used for creating KM debug files. Installation Path is the application installation path discovered by the KM. This information can be overridden through the KM command Configuration> Node Type Accesses the Node Type Configuration dialog, which displays and sets the type of the Tivoli Storage Manager application node. The TSM KM server discovery detects the type of the node automatically; the type can either be Server or Storage Agent. The operation of the KM depends on this node type. Configuration> Node Status Accesses the Node Status Configuration dialog for viewing and modifying the error expression filters, which determine the status of the node (parameter TSMNodeStatus). By default, the following "Included" expressions are checked. If detected, they set the parameter TSMNodeStatus to alert, unless the message also contains an "Excluded" expression. Type "[default]" to reset to the default configuration. Configuration> Instance Limits Accesses the Instance Limits Configuration dialog to view and modify the maximum number of TSM KM application instances allowed for each application class. Configuration> Debug Accesses the Debug Configuration dialog for enabling/disabling the TSM KM debug switches. By default, all KM debug messages are sent to a file and a task window. KM Status Generates a summary report containing information on the managed system. About Displays information about the product and the manufacturer. Classes and Parameters 96 Binary Paths are the Application and operating system binary path, which is used for setting PATH environment variable. The KM discovers and set this automatically. This menu can be used, if the discovered paths are incorrect. Library Paths are the Application and operating system library path, which is used for setting the following environment variables: LD_LIBRARY_PATH (on Solaris) SHLIB_PATH (on HP-UX) LIBPATH (on AIX) The KM discovers and set this automatically. This menu can be used, if the discovered paths are incorrect. DSM_DIR Directory Path, DSM_DIR Directory Path, and DSM_DIR Directory Path are the TSM application paths used while executing DSMADMC commands. TSM application paths used while executing DSMADMC commands.

97 TSM_CLIENT_CONTAINER Icon Parameters Name Description Units Default Alert Conditions BPPM Type TSMClientDetails Set by TSMClientCollector. Displays all data returned to the standard out from commands executed by the data collector. InfoBox Name Description Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Function Description Configuration > Clients Accesses the dialog for specifying which clients are to be monitored by the TSM KM. By default, all clients configured on the server are monitored. Type [default] to reset to the default configuration. Configuration > Clients Status Accesses the global configuration for determining the client status for monitored client instances. By default, following TSMClientState to TSMClientStatus mapping rule is used: 97 Classes and Parameters Menu Commands

98 Select [default] to reset to the default client status mapping rule. Classes and Parameters 98

99 TSM_CLIENT Icon Name Description TSMClientLastAccessEla psed* Units Default Alert Conditions BPPM Type Set by TSMClientCollector. Hours Displays the time elapsed since the last communication from the client. The specified alarm ranges can be enabled to allow the output of the parameter to be actively monitored. Then, if this parameter changes to warning or alarm state, the recovery action will trigger an event. None TSMClientSpaceUsed* Set by TSMClientCollector. Gigabytes Displays the amount of space used (GB) on the client node. None TSMClientState Set by TSMClientCollector. Displays the state of the client as reported in the command executed by the data collector. 0 = Running None 1 = Locked 2 = Never Communic ated -1 = Unknown Availability TSMClientStatus Set by TSMClientCollector. Monitors the status of the client. This status is determined by the client status mapping rule defined in the KM command Configuration > Client(s) Status. 0 = OK 1= Suspicious 2 = Failure Warning = 1 Alarm =2 Availability None If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. TSMClientSummary Set by TSMClientCollector. Summarizes the client information as reported in commands executed by the data collector. 99 Classes and Parameters Parameters

100 For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. Classes and Parameters 100

101 InfoBox Name Description Name Name of the Tivoli Storage Manager client. Description Description of the Tivoli Storage Manager client. Operating System Operating system of the client. Status Status of client connectivity from the current node. Application Name of the application installed on the client, which responds to the connection request. Version Version number of the application installed on the client. Time Since Last Communication Number of days, hours, minutes and seconds since the last connection from the current node. Last Communication Method Method of the last connection from the current node. Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Function Description Configuration> Client Accesses the individual configuration for monitoring the selected client instance. This dialog allows the selected client instance to be enabled or disabled for monitoring by the TSM KM Configuration> Client Status Accesses the individual configuration for determining client status for the selected client instance. By default, the global TSMClientState to TSMClientStatus mapping rule is used, as configured at the container level. Select [default] to revert to the client status mapping rule configured at the global/container level. 101 Classes and Parameters Menu Commands

102 TSM_DAEMON_CONTAINER Icon Parameters Name Description Units Default Alert Conditions BPPM Type TSMDaemonDetails Set by TSMDaemonCollector, displays all data returned to the standard out from commands executed by the data collector. None Seconds Warning > preset value or observed maximum (default) Collection Status TSMDaemonCollectorEx ectime 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/ TSMDeamonsCollectorExecT ime", 1); %PSL pconfig("replace", "/Runtime/TSM/ NBUDaemonCollectorWarn", 3600); InfoBox Name Description Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Classes and Parameters 102 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:

103 Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Menu Commands Function Description Reports > Daemon List Lists all running Tivoli Storage Manager daemons. Configuration > Daemons Accesses the dialog for specifying which daemons are to be monitored by the TSM KM. By default, the following daemons are monitored. Note that this default configuration is for a UNIX platform; the difference for a Microsoft Windows platform is that the name of the TSM Server Daemon is shown as "dsmserv or dsmsvc" and the TSM Storage Agent Daemon is shown as "dsmsta or dstasvc". Type [default] to reset to the default configuration. Accesses the global configuration for determining the daemon status for monitored daemon instances. By default, the following TSMDaemonState to TSMDaemonStatus mapping rule is used: Configuration > Daemons Status Select [default] to reset to the default mapping rule. TSM_DAEMON Icon 103 Classes and Parameters

104 Name Description Units Default Alert Conditions BPPM Type TSMDaemonCPUDuratio n Set by TSMDaemonCollector. Displays the CPU seconds consumed by the daemon. Seconds None TSMDaemonCPUUtilizati Set by TSMDaemonCollector. on* Displays the CPU seconds used by the daemon. Percentag e (%) None TSMDaemonMemorySize Set by TSMDaemonCollector. * Displays the core image size of the daemon in the virtual memory. Kilobytes (KB) None TSMDaemonProcessCou nt Set by TSMDaemonCollector. Displays the number of daemon processes/threads found. Processes None TSMDaemonState Set by TSMDaemonCollector. Displays the state of the daemon as reported in the command executed by the data collector. 0= None Running 1= Sleeping 2= Waiting 3= Queued 4= Intermedi ate 5= Terminate d 6= Stopped/ Disabled 7= Growing 8= Nonexiste nt/not Respondin g 9 = Not Running -1 = Unknown Availability TSMDaemonStatus Set by TSMDaemonCollector. Monitors the status of the daemon. This status is determined by the daemon status mapping rule defined in the KM command Configuration > Daemon(s) Status. 0 = OK None 1= Suspiciou s 2 = Failure Availability Classes and Parameters 104 Parameters

105 If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. TSMDaemonSummary For detailed information about Set by TSMDaemonCollector. Summarizes the daemon information as reported by commands executed by the data collector. Baselining and KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. Name Description Name Name of the Tivoli Storage Manager daemon. Description Description of the Tivoli Storage Manager daemon. PID Process ID of the daemon. PPID Parent process ID of the daemon. Owner Owner of the daemon. Status Status of the daemon as reported in the PATROL Agent process cache. Command Command that started the daemon. Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Menu Commands Function Description Configuration > Daemon Accesses the individual configuration for monitoring the selected daemon instance. This dialog allows the selected daemon instance to be enabled or disabled for monitoring by the TSM KM. Configuration > Daemons Status Accesses the individual configuration for determining daemon status for the selected the daemon instance. 105 Classes and Parameters InfoBox

106 By default, the global TSMDaemonState to TSMDaemonStatus mapping rule is used. Select [default] to revert to the daemon status mapping rule configured at the global/container level. TSM_DATABASE_CONTAINER Icon Parameters Name Description Units Default Alert Conditions BPPM Type TSMDatabaseDetails Set by TSMDatabaseCollector. Displays all data returned to the standard out from commands executed by the data collector. Name Description Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Menu Commands Function Description Reports > Database Backup Volume History Reports server database backup volume history for the last 7 days. Configuration > Databases Accesses the dialog for specifying which server databases are monitored by the TSM KM. By default, following server databases are monitored. Type [default] to reset to the default configuration. Classes and Parameters 106 InfoBox

107 TSM_DATABASE Icon Parameters Name Description Units Default Alert BPPM Type Conditions TSMDatabaseBackupEla Set by TSMDatabaseCollector. psed* Displays the elapsed time since the last successful database backup. Hours None Count None Percentage None (%) The specified alarm ranges can be enabled to allow the output of the parameter to be actively monitored. Then, if this parameter changes to warning or alarm state, the recovery action will trigger an event. TSMDatabaseBufferReq uestcount Set by TSMDatabaseCollector. Displays the cumulative number of requests for database pages since the buffer pool was last reset (or since the server was last started). This parameter is only available for the server database (db) TSMDatabaseCacheHitP Set by TSMDatabaseCollector. ercent* 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. This parameter is only available for the server database (db) 107 Classes and Parameters This parameter is only available for the server database (db)

108 TSMDatabaseCacheWai Set by TSMDatabaseCollector. Percentage None tpercent* 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. This parameter is only available for the server database (db) TSMDatabaseFSSpaceU sedpercent* Set by TSMDatabaseCollector. Percentage Warning = Monitors the percentage of space (%) used by the file system where the Alarm > 98 database resides. If this parameter changes to warning or alarm state, the recovery action will trigger an event. This parameter is only available for the server database (db) TSMDatabaseLogConsu medsize Set by TSMDatabaseCollector. Displays the cumulative consumption of log space used by the server since the last reset of this parameter. Megabytes (MB) None TSMDatabaseLogPoolUs Set by TSMDatabaseCollector. Percentage None edpercent* 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. This parameter is only available for the server database (db) TSMDatabaseLogPoolW aitpercent* Classes and Parameters Set by 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. 108 Percentage None (%) This parameter is only available for the server database (db)

109 This parameter is only available for the server database (db) TSMDatabasePoolHitPe Set by TSMDatabaseCollector. rcent* 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 None (%) This parameter is only available for the server database (db). TSMDatabaseReorgElap Set by TSMDatabaseCollector. Hours sed* Displays the elapsed time since the last database reorganization. The specified alarm ranges can be enabled to allow the output of the parameter to be actively monitored. Then, if this parameter changes to warning or alarm state, the recovery action will trigger an event. None Warning = 2-5 Alarm < 2 Availability None This parameter is only available for the server database (db). TSMDatabaseSpaceAvai Set by TSMDatabaseCollector. lable Monitors the amount of assigned space remaining available for use by the server database. Megabytes (MB) The name of this parameter should not be confused with the TSM terminology "Available Space" reported in the InfoBox, which is the total volume space made available to the server database TSMDatabaseSpaceCha nged Set by TSMDatabaseCollector. Megabytes Displays the database pages (in (MB) megabytes) that have changed since the last backup. 109 Classes and Parameters If this parameter changes to warning or alarm state, the recovery action will trigger an event.

110 This parameter is only available for the server database (db) TSMDatabaseSpaceCha ngedpercent* Set by TSMDatabaseCollector. Percentage None Displays the percentage of database (%) pages that have changed since the last backup. TSMDatabaseSpaceGro wthrate Set by TSMDatabaseCollector. Displays the growth rate of the space used by the server database. Megabytes None per second (MB/s) TSMDatabaseSpaceMax Set by TSMDatabaseCollector. Extension Displays the maximum amount the database can be extended by. Megabytes (MB) None TSMDatabaseSpaceMax Set by TSMDatabaseCollector. Reduction Displays the maximum amount the database can be reduced by. Megabytes (MB) Warning = 4-8 Alarm < 4 TSMDatabaseSpaceUse d Set by TSMDatabaseCollector. Displays the amount of assigned space used by the server database. Megabytes (MB) None TSMDatabaseSpaceUse dpercent* Set by TSMDatabaseCollector. Percentage None Monitors the percentage of assigned (%) space used by the server database. If this parameter changes to warning or alarm state, the recovery action will trigger an event. The total assigned space is the used space (TSMDatabaseSpaceUsed) plus the available space (TSMDatabaseSpaceAvailable). TSMDatabaseSummary For detailed information about Set by TSMDatabaseCollector. Summarizes the database information as reported by commands executed by the data collector. Baselining and KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. InfoBox Classes and Parameters 110 This parameter is only available for the server database (db)

111 Description Name Name of the Tivoli Storage Manager server database. Description Description of the Tivoli Storage Manager server database. Path Name of the table that holds information about the database or the full file path of the database. Available Space Amount of space made available as volumes for the server database, in megabytes. Assigned Space Amount of the Available Space assigned as the server database, in megabytes. Maximum Extension Maximum amount the database can be extended by, in megabytes. Maximum Reduction Maximum amount the database can be reduced by, in megabytes. Page Size Page Size, in bytes. Total Usable Pages Total number of pages available. This will always be a multiple of the Assigned Space value, by a factor of 256 (1megabyte /256 pages). Used Pages Total number of pages currently being used. Percent Utilized Current utilization as a percentage of the Assigned Space. Maximum Percent Utilized Maximum occupancy of the database, as a percentage of the Assigned Space. This value is the highest utilization percentage reached by the database since the last reset of this statistic. Physical Volumes Number of database volumes and copies. Buffer Pool Pages Number of pages in the database buffer pool. Last Backup Date & time that the server database was last backed up. Last Backup Mode Backup mode of the last backup of the database. Last Purge Date & time when the server database was purged last. Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Menu Commands Function Description Reports > Database Volumes Reports information about server database volumes and volume copies. Configuration > Database Accesses the individual configuration for monitoring the selected server database instance. This dialog allows the selected database instance to be enabled or disabled for monitoring by the TSM KM. 111 Classes and Parameters Name

112 TSM_LOG_CONTAINER Icon Parameters Name Description Units TSMLogDetails Set by TSMLogCollector. Displays all data returned to the standard out from commands executed by the data collector. Default Alert Conditions BPPM Type InfoBox Description Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Name Classes and Parameters 112

113 Menu Commands Name Description Reports > Activity Log Messages Reports all Tivoli Storage Manager messages today (logged since midnight). Configuration > Logs Accesses the dialog for specifying which log files are to be monitored by the TSM KM. By default, the following log files are monitored. Type [default] to reset to the default configuration. Configuration > Logs Filter Accesses the global configuration of the filter for error expressions in monitored log file instances. By default, following error messages are looked for in each log file. If detected, they are added to appropriate text parameter: Configuration > Logs Scan Limit Accesses the global configuration of the data scanning limit for monitored log file instances. By default, the log collector only scans 5KBytes of new log data for each monitored log file during each data collection cycle. Configuration > Logs Alert Acknowledgement Accesses the global configuration of the method of acknowledgement for alerts on monitored log file instances. By default, the log collector automatically acknowledges previous log alerts (warnings and alarms) when it detects new errors. 113 Classes and Parameters Type [default] to reset to the default configuration.

114 TSM_LOG Icon Parameters Name Description Units Default Alert Conditions BPPM Type TSMLogAlarmCount* Set by TSMLogCollector. Monitors the number alarm messages set in the parameter TSMLogAlarmText. Count Alarm 1 None TSMLogAlarmText Set by TSMLogCollector. Displays all alarm messages in the log file which have not been acknowledged. The filter used by the data collector to determine alarm messages can be customized using the KM command Configuration > Log(s) Filter. These alarm messages can be acknowledged automatically (default) or manually, depending on the configuration in the KM command Configuration > Log(s) Alert Acknowledgement. Manual acknowledgement is available under the KM sub-menu Acknowledgement. TSMLogFSSpaceUsedPer cent* Classes and Parameters Set by TSMLogCollector. Monitors the percentage of space used by the file system (where the log file resides). If this parameter changes to warning or alarm state, the recovery action will trigger an event. 114 Percentage Warning = (%) Alarm > 98 If this parameter changes to alarm state, the recovery action will trigger an event.

115 This parameter is not available for the activity log (actlog). TSMLogSpaceAvailable Set by TSMLogCollector. Monitors the available space for the log file to use (this is also the available space on the file system). If this parameter changes to warning or alarm state, the recovery action will trigger an event. Megabytes (MB) Warning = 2-5 Alarm < 2 Availability Kilobytes per second (KB/s) None Kilobytes (KB) None This parameter is not available for the activity log (actlog). TSMLogSpaceGrowthRat e Set by TSMLogCollector. Displays the growth rate of the amount of space used by the log file. This parameter is not available for the activity log (actlog). TSMLogSpaceUsed Set by TSMLogCollector. Displays the amount of space used by the log file. This parameter is not available for the activity log (actlog). Set by TSMLogCollector. Monitors the percentage of capacity used by the log file. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Percentage Warning = (%) Alarm > 98 TSMLogSpaceUsedPerce nt* The total capacity is the used space (TSMLogSpaceUsed) plus available space (TSMLogSpaceAvailable). This parameter is not available for the activity log (actlog). 115 Classes and Parameters

116 TSMLogSummary Set by TSMLogCollector. Summarizes the log file information as reported by commands executed by the data collector TSMLogText Set by TSMLogCollector. Displays all log text scanned by the data collector during the last collection cycle. The size of the data scanned by the data collector is configured in the KM command Configuration > Log(s) Scan Limit. TSMLogWarningCount* Set by TSMLogCollector. Monitors the number warning messages set in the parameter TSMLogWarningText. If this parameter changes to a warning state, the recovery action will trigger an event Count Warning > 1 TSMLogWarningText Set by TSMLogCollector. Displays all warning messages in the log file which have not been acknowledged. The filter used by the data collector to determine warning messages can be customized using the KM command Configuration > Log(s) Filter. For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. InfoBox Name Description Name Name of the Tivoli Storage Manager log file. Description Description of the Tivoli Storage Manager log file. Path Name of the table that holds information about the server activity log (actlog) or the full file path of the log file. Classes and Parameters 116 These warning messages can be acknowledged automatically (default) or manually, depending on the configuration in the KM command Configuration > Log(s) Alert Acknowledgement. Manual acknowledgement is available under the KM sub-menu Acknowledgement

117 Log File Modification Time Date & time when the log file was last modified. Not applicable for activity log (actlog). Log File Size File size of the log file. Not applicable for activity log (actlog). Total FS Space Total space used by the file system. Not applicable for activity log (actlog). Available FS Space Space available for use by the file system. Not applicable for activity log (actlog). FS Percent Used Percentage of the total file system space used. Not applicable for activity log (actlog). Last Purge Date & time when the log file was last purged. Not applicable for activity log (actlog). Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Function Description Acknowledgement > Warnings Allows acknowledgement of warning alerts on the selected log file instance. This dialog allows selective acknowledgement of "suspicious" error messages detected in the log file and sent to the text parameter TSMLogWarningText. Acknowledgement > Alarms Allows acknowledgement of alarm alerts on the selected log file instance. This dialog allows selective acknowledgement of "failure" error messages detected in the log file and sent to the text parameter TSMLogAlarmText. Acknowledgement > All Allows acknowledgement of all warning and alarm alerts on the selected log file instance. This dialog allows acknowledgement of all error messages detected in the log file and sent to the text parameter TSMLogWarningText or TSMLogAlarmText. Configuration > Log Accesses the individual configuration for monitoring the selected log file instance. This dialog allows the selected log file instance to enabled or disabled for monitoring by the TSM KM. Configuration > Log Filter Accesses the individual configuration of the log error filter for the selected log file instance. By default, the global log error filter is used, as configured at the container level Type "[default]" to reset to the log filter configured at the global/container level. Configuration > Log Scan Limit Accesses the individual configuration of the data scanning limit for the selected log file instance. By default, the global log file scanning limit is used, as configured at the container level. Configuration > Log Alert Acknowledgement Accesses the individual configuration of the method of acknowledgement for alerts on the selected log file instance. 117 Classes and Parameters Menu Commands

118 By default, the global method of log error acknowledgement is used, as configured at the container level. TSM_POLICY_CONTAINER Icon Parameters Name Description Units Default Alert Conditions BPPM Type TSMDomainDetails Set by TSMPolicyCollector. Displays all data returned to the standard out from commands executed by the data collector. InfoBox Description Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Name Classes and Parameters 118

119 Menu Commands Function Description Configuration > Domains Accesses the dialog for specifying which domains are to be monitored by the TSM KM. By default, all domains configured on the server are monitored. Type [default] to reset to the default configuration. Configuration > Domains Backup Restriction Accesses the global configuration to set a backup restriction window for all monitored domain instances. By default, backup restriction is disabled. When the backup restriction window is defined and enabled using this menu, and if the domain status mapping rule is configured appropriately, an alert will be triggered if any backup activity is detected during this restriction window. Configuration > Domains Status Accesses the global configuration for determining the domain status for all monitored domain instances. By default, the following TSMDomainState to TSMDomainStatus mapping rule is used: Select [default] to reset to the default mapping rule. Configuration >Client Nodes Accesses the dialog for specifying which client nodes of the selected domain are to be monitored by the KM. By default, all client nodes of enabled domains are monitored. Type [default]to reset to the default configuration. TSM_POLICY Parameters Name Description Units 119 Default Alert Conditions BPPM Type Classes and Parameters Icon

120 Set by TSMDomainCollector. Hours Displays the elapsed time since the last backup for this domain, regardless of completion status of the backup. This last backup is determined from the monitored jobs as configured in the KM command Configuration > Jobs from the Jobs icon. The specified alarm ranges can be enabled to allow the output of the parameter to be actively monitored. Then, if this parameter changes to warning or alarm state, the recovery action will trigger an event. None TSMDomainBackupSum mary Set by TSMDomainCollector. Summarizes the last backup for this domain TSMDomainBackupThro ughput* Set by TSMDomainCollector. Displays the throughput of the last successful backup for this domain. Gigabytes None per second (GB/s) TSMDomainFullBackup Duration Set by TSMDomainCollector. Displays the duration of the last successful full backup for this domain. Seconds None TSMDomainFullBackupE Set by TSMDomainCollector. Hours lapsed* Displays the elapsed time since the last successful full backup for this domain. This last backup is determined from the monitored jobs as configured in the KM command Configuration > Jobs from the Jobs icon. The specified alarm ranges can be enabled to allow the output of the parameter to be actively monitored. Then, if this parameter changes to warning or alarm state, the recovery action will trigger an event. None TSMDomainFullBackup ObjectCount None None Set by TSMDomainCollector. Count Displays the number of objects backed up in the last successful full backup for this domain. TSMDomainFullBackupS Set by TSMDomainCollector. ize Displays the size of the last successful full backup for this domain. Classes and Parameters 120 Gigabytes (GB) TSMDomainBackupElap sed*

121 TSMDomainIncrBackup Duration Set by TSMDomainCollector. Displays the duration of the last successful incremental backup for this domain. Seconds None None Count None TSMDomainIncrBackupS Set by TSMDomainCollector. ize Displays the size of the last successful incremental backup for this domain. Gigabytes (GB) None TSMDomainState Set by TSMDomainCollector. Displays the state of the domain. If a backup restriction window is defined in the KM command Configuration > Domain(s) Backup Restriction, this parameter will be set to Running in Restricted Window if there is any activity during the specified period. 0 = Idle None 1= Running 2= Running in Restricted Window 3 = Not Started 4= Inactive -1 = Unknown Availability TSMDomainStatus Set by TSMDomainCollector. Monitors the status of the domain. This status is determined by the domain status mapping rule defined in the KM command Configuration > Domain(s) Status. If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. 0 = OK None 1= Suspicious 2 = Failure Availability TSMDomainIncrBackupE Set by TSMDomainCollector. Hours lapsed* Displays the elapsed time since the last successful incremental backup for this domain. This last backup is determined from the monitored jobs as configured in the KM command Configuration > Jobs from the Jobs icon. TSMDomainIncrBackup ObjectCount Set by TSMDomainCollector. Displays the number of objects backed up in the last successful incremental backup for this domain. 121 Classes and Parameters The specified alarm ranges can be enabled to allow the output of the parameter to be actively monitored. Then, if this parameter changes to warning or alarm state, the recovery action will trigger an event.

122 TSMDomainSuccBackup Elapsed* Set by TSMDomainCollector. Hours Displays the elapsed time since the last successful backup for this domain. This last backup is determined from the monitored jobs as configured in the KM command Configuration > Jobs from the Jobs icon. The specified alarm ranges can be enabled to allow the output of the parameter to be actively monitored. Then, if this parameter changes to warning or alarm state, the recovery action will trigger an event. None TSMDomainSummary Set by TSMDomainCollector. Summarizes the domain information as reported by commands executed by the data collector. For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. Name Description Name Name of the Tivoli Storage Manager domain. Description Description of the Tivoli Storage Manager domain. Activated Policy Set Name of the policy set that was last activated in the domain. Activation Date/Time Date & Time when the policy set was activated. Activated Default Management Class Assigned default management class for the policy set. Number of Registered Nodes Number of client nodes registered to the policy domain. Backup Retention Number of days to retain inactive backup versions of files. Archive Retention Number of days to retain an archive file. Status Current execution status of the domain (Idle, Running, or Running in Restricted Window). Last Backup Start Date & time when the last backup job started for the domain. Last Backup End Date & time at the completion of the last backup job for the domain. Last Backup Status Status of the last backup job for the domain. Last Backup Job Name of the last backup for the domain. Classes and Parameters 122 InfoBox

123 Last Full Backup Start Date & time when the last successful full backup started for the domain. Last Full Backup End Date & time at the completion of the last successful full backup for the domain. Last Full Backup Job Name of the last successful full backup for the domain. Last Incr Backup Start Date & time when the last successful incremental backup started for the domain. Last Incr Backup End Date & time at the completion of the last successful incremental backup for the domain. Last Incr Backup Job Name of the last successful incremental backup for the domain. Next Backup Date & time that the next backup will start for this domain. Next Backup Schedule Name Name of schedule to be used during the next backup job. Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Function Description Reports > Domain Schedule Displays the schedule for the selected domain instance for the next 24 hours. Configuration > Domain Accesses the individual configuration for monitoring the selected domain instance. This dialog allows the selected domain instance to be enabled or disabled for monitoring by the TSM KM. Configuration > Domain Accesses the individual configuration for the backup restriction window for the Backup Restriction selected domain instance. By default, the global backup restriction window setting is used, as configured at the container level. Configuration > Domain Status Accesses the individual configuration for determining domain status for the selected domain instance. By default, the global TSMDomainState to TSMDomainStatus mapping rule is used, as configured at the container level. Select [default] to revert to the domain status mapping rule configured at the global/ container level. Configuration > Client Nodes Accesses the dialog for specifying which client nodes of the selected domain are to be monitored by the TSM KM. By default, all client nodes of enabled domains are monitored. Type [default] to reset to the default configuration. 123 Classes and Parameters Menu Commands

124 TSM_PCLIENT Icon Name Units Default Alert Conditions BPPM Type TSMNodeBackupSumma Set by TSMDomainCollector. ry Summarizes the last backup for this client node. TSMNodeBackupThroug hput* Megabyte s per second (MB/s) None TSMNodeFullBackupDur Set by TSMDomainCollector. ation Displays the duration of the last successful full backup for this client node. Seconds None TSMNodeFullBackupObj Set by TSMDomainCollector. ectcount Displays the number of objects backed up in the last successful full backup for this client node. Count None TSMNodeFullBackupSiz e* Set by TSMDomainCollector. Displays the size of the last successful full backup for this client node. Megabyte s (MB) None TSMNodeIncrBackupDu ration Set by TSMDomainCollector. Displays the duration of the last successful incremental backup for this client node. Seconds None TSMNodeIncrBackupOb jectcount Set by TSMDomainCollector. Displays the number of objects backed up in the last successful incremental backup for this client node. Count None TSMNodeIncrBackupSiz e* Set by TSMDomainCollector. Displays the size of the last successful incremental backup for this client node. Megabyte s (MB) None Classes and Parameters Description Set by TSMDomainCollector. Displays the throughput of the last successful backup for this client node. 124 Parameters

125 TSMNodeSummary Set by TSMDomainCollector. Summarizes the client node information as reported by commands executed by the data collector. TSMObjectExcludeList Set by TSMDomainCollector. Lists all objects and file systems excluded from backup for this client node. TSMObjectIncludeList Set by TSMDomainCollector. Lists all objects and file systems included for backup for this client node. For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. InfoBox Name Description Name Host name of the Tivoli Storage Manager client node. Description Description of the Tivoli Storage Manager client node. Domain Name Name of the domain that the client belongs to. Operating System Operating system of the client node. Last Backup Start Date & time when the last backup started for the client node. Last Backup End Date & time at the completion of the last backup for the client node. Last Backup Status Status of the last backup for the client node. Last Full Backup Start Date & time when the last successful full backup started for the client node. Last Full Backup End Date & time at the completion of the last successful full backup for the client node. Last Full Backup Job Name of the last successful full backup of the client node. Last Incr Backup Start Date & time when the last successful incremental backup started for the client node. Last Incr Backup End Time Date & time at the completion of the last successful incremental backup for the client node. Last Incr Backup Job Name of the last successful incremental backup of the client node. Next Backup Date & time that the next backup will start for this client node. Next Backup Schedule Name Name of schedule to be used during the next backup job. Collector Name Name of the data collector that sets variables and parameters under this application instance. 125 Classes and Parameters Last Backup Save Group Name of the last backup for the client node.

126 Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Menu Commands Function Description Configuration > Client Node Accesses the individual configuration for monitoring the selected client node instance. This dialog allows the selected client node instance to be enabled or disabled for monitoring by the TSM KM. TSM_JOB_CONTAINER Icon Name Description TSMJobActiveBackupCo unt* TSMJobActiveCount* Default Alert Conditions BPPM Type Set by TSMJobCollector. Displays the count number of active backup jobs currently discovered and monitored. none Set by TSMJobCollector. Displays the count number of active jobs currently discovered and monitored. none TSMJobActiveNonBacku Set by TSMJobCollector. Displays the count pcount* number of active non-backup jobs currently discovered and monitored. none TSMJobDetails For detailed information about Units Set by TSMJobCollector. Displays all data returned to the standard out from commands executed by the data collector. Baselining and KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. Classes and Parameters 126 Parameters

127 InfoBox Description Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Name 127 Classes and Parameters

128 Menu Commands KM Command Action Force Full Collection Allows the user to force the data collector for jobs to perform a full discovery during the next collection cycle. Acknowledgement > Warnings Allows acknowledgement of warning alerts occurring on any monitored job instance. This dialog allows acknowledgement of any job in a "suspicious" state (which sets the parameter TSMJobStatus to Warning). Acknowledgement > Alarms Allows acknowledgement of alarms occurring on any monitored job instance. This dialog allows acknowledgement of any job in a "failure" state (which sets the parameter TSMJobStatus to Alarm). Acknowledgement > All Allows acknowledgement of all warnings and alarms occurring on any monitored job instance. This dialog allows acknowledgement of any job in a "suspicious" or "failure" state (which sets the parameter TSMJobStatus to Warning or Alarm, respectively). Configuration> Jobs Accesses the dialog for specifying which jobs are to be monitored by the TSM KM. By default, all scheduled jobs on the server are monitored according to the following conditions: The age of a job is calculated from the job start time. The status of a job is determined by the state of the job (from the parameter TSMJobState) and the job status mapping rule, described below. Accesses the configuration for determining the status for all monitored job instances. By default, the following TSMJobState to TSMJobStatus mapping rule is used: Select [default] to reset to the default job status mapping rule. Configuration> Jobs Alert Acknowledgement Classes and Parameters Accesses the global configuration of the method of acknowledgement for alerts on monitored job instances. By default, the job alerts are manually acknowledged. Using this menu you can change this so the job collector automatically acknowledges previous job alerts (warnings or alarms) when it detects new errors. Refer to the User Guide for Tivoli Storage Manager KM for PATROL for more details. 128 Configuration> Jobs Status

129 TSM_JOB Icon Parameters Name Description Units Default Alert Conditions BPPM Type TSMJobDuration Set by TSMJobCollector. Displays the duration of the job from the start. Seconds None TSMJobErrorCount* Set by TSMJobCollector. Monitors the number of client node errors logged in the server activity log during this job. Count Warning when > 100 The default settings for this parameter dictate that when any error is detected during a job, this parameter is always set to warning state. And the recovery action will trigger an event. Set by TSMJobCollector. Displays the throughput of the job on the network. Megabytes None per second (MB/s) TSMJobSize Set by TSMJobCollector. Displays the amount of data backed up for the job. Megabytes (MB) 129 None TSMJobNetworkThrough put* Classes and Parameters

130 Set by TSMJobCollector. Displays the state of the job. This is determined using the event status and result of the event. 0= None Completed 1 = Future 2= Pending 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 TSMJobStatus Set by TSMJobCollector. Monitors the status of the job. This status is determined by the job status mapping rule defined in the KM command Configuration > Jobs Status. If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. 0 = OK Warning = 1 Availability 1= Alarm = 2 Suspicious 2 = Failure TSMJobSummary Set by TSMJobCollector. Summarizes the job information as reported by commands executed by the data collector. None TSMJobText Set by TSMJobCollector. Displays all reported messages related to this job. None TSMJobThroughput* Set by TSMJobCollector. Displays the throughput of the job. Megabytes None per second (MB/s) TSMObjectCount Set by TSMJobCollector. Displays Count the number of objects inspected for this job. Classes and Parameters 130 None Availability TSMJobState

131 TSMObjectExpiredCount Set by TSMJobCollector. Displays the total number of objects for this job that have expired. Count None TSMObjectFailedCount Set by TSMJobCollector. Displays the total number of objects for this job that have failed. If this parameter changes to a warning state, the recovery action will trigger an event. Count Warning when > 100 TSMObjectProcessedCo unt Set by TSMJobCollector. Displays the total number of objects for this job that have been processed. Count None TSMObjectReboundCoun Set by TSMJobCollector. Displays t the total number of objects for this job that have been rebound. Count None TSMObjectUpdatedCoun Set by TSMJobCollector. Displays t the total number of objects for this job that have been updated. Count None For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. InfoBox Description Job Identifier assigned to the job by TSM KM (<Domain Name>:<Client Node <Job Start Time>). Type Type of the job. Mode Mode of the job (such as Incremental or Full). Schedule Name of the schedule used by the job. Action Action performed by the schedule. Status Status of the job as determined by the TSM KM. Event Status Status of the event. Result Result of the event. Reason Additional text depending on the Event Status and Result. Domain Name Name of the domain this job is assigned to. Node Name Name of the client node this job is assigned to. Scheduled Start Date & time that the job was scheduled to start. Actual Start Date & time that the job actually started. Completed Date & time at the completion of the job. 131 Name Classes and Parameters

132 Duration of the job. Size Amount of data that has been written. Objects Inspected Total number of objects inspected for this job. Objects Processed Total number of objects for this job that have been processed. Objects Updated Total number of objects for this job that have been updated. Objects Rebound Total number of objects for this job that have been rebound. Objects Deleted Total number of objects for this job that have been deleted. Objects Expired Total number of objects for this job that have expired. Objects Failed Total number of objects for this job that have failed. Objects Compression Percentage of compression achieved by the job. Data Transfer Time Time taken for the data transfer. Network Data Transfer Rate Rate of data transfer on the network. Aggregate Data Transfer Rate Aggregated rate of data transfer. Percent Completed Estimated percentage of the job that has been completed in comparison with the last similar successful job for the same domain, client node, and mode. Time Remaining Remaining time of the job in comparison with the last similar successful job. Session Numbers List of sessions opened on the client node by the job (sessions are listed by number). Last Backup Start Date & time when the last similar successful backup started. Last Backup End Date & time when the last similar successful backup ended. Last Backup Job Job ID of the last similar successful backup. Last Backup Duration Duration of the last similar successful backup. Last Backup Size Data size written by the last similar successful backup. Last Backup Objects Number of objects written by the last similar successful backup Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Menu Commands Function Classes and Parameters Description 132 Processing Time

133 Allows acknowledgement of all warnings and alarms occurring on the selected job instance. This dialog allows acknowledgement if the selected job instance is in a "suspicious" or "failure" state (which sets the parameter TSMJobStatus to Warning or Alarm, respectively). Acknowledgement > Alert 133 Classes and Parameters

134 TSM_MOUNT_CONTAINER Icon Parameters Name Description Units Default Alert Conditions BPPM Type TSMRequestDetails Set by TSMRequestCollector. Displays all data returned to the standard out from commands executed by the data collector. InfoBox Name Description Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Function Description Administration > Cancel All Assigns all current mount requests to be canceled. Reports > Pending Mount Requests Reports a list of all pending mount requests. Configuration > Mount Requests Accesses the dialog for specifying which mount requests are to be monitored by the TSM KM. By default, all mount requests are monitored for 1 day from the time they are issued. Configuration > Mount Requests Status Accesses the configuration for determining the status for all monitored mount request instances. By default, the following TSMRequestState to TSMRequestStatus mapping rule is used: Classes and Parameters 134 Menu Commands

135 Select [default] to reset to the default mount request status mapping rule. TSM_MOUNT Icon Parameters Name Description Units Default Alert Conditions BPPM Type TSMRequestElapsed* Set by TSMRequestCollector. Displays the elapsed time since the mount request was issued. Minutes None TSMRequestState Set by TSMRequestCollector. Displays the state of the mount request as reported in the command executed by the data collector. 0= None Completed 1 = Pending -1 = Unknown TSMRequestStatus Set by TSMRequestCollector. Monitors the status of the mount request. This status is determined by the mount request status mapping rule defined in the KM command Configuration > Mount Request(s) Status. 0 = OK 1= Suspicious 2 = Failure Availability If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. TSMRequestSummary Set by TSMRequestCollector. Summarizes the mount request information as reported by commands executed by the data collector. TSMRequestTimeout* Set by TSMRequestCollector. Displays the time remaining until the mount request times out. Minutes 135 Alarm = 030 Classes and Parameters Warning = 1 Availability Alarm = 2

136 If the alert state changes to alarm state, the recovery action will trigger an event. For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. Name Description Request ID Identifier assigned to the mount request by Tivoli Storage Manager. Description Full detail of the mount request. Job Type Type of job the mount request belongs to (Backup or Restore). Mode Mode of the mount request (Read, Write or both). Volume Requested volume name. Volume Type Type of the requested volume. Drive Name Name of the drive the mount request is assigned to. Library Name Name of the library the mount request is assigned to. Server Name Name of the server or storage agent the library is connected to. Request Time Date & time that the mount request was detected. Request Timeout Time remaining until the mount request times out. Reply Required Whether a reply is required for the mount request (Yes or No). Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Menu Commands KM Command Action Administration > Reply Allows a reply to be sent for the selected mount request once a requested action has been taken. A reply may be required to allow this mount request to continue processing. This requirement is noted in the in the InfoBox item "Reply Required". Administration > Cancel Allows the selected mount request to be cancelled. Classes and Parameters 136 InfoBox

137 TSM_LIBRARY_CONTAINER Icon Parameters Name Description Units Default Alert Conditions BPPM Type TSMLibraryDetails Set by TSMLibraryCollector. Displays all data returned to the standard out from commands executed by the data collector. InfoBox Name Description Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Function Description Configuration > Automated Libraries Accesses the dialog for specifying which automated libraries are to be monitored by the TSM KM. By default, all local and remote automated libraries are monitored for a server and all local automated libraries are monitored for a storage agent. Type [default] to reset to the default configuration. Configuration > Automated Libraries Status Accesses the global configuration for determining the status for monitored automated library instances. By default, the following TSMLibraryState to TSMLibraryStatus mapping rule is used: 137 Classes and Parameters Menu Commands

138 Select [default] to reset to the default library status mapping rule. Configuration > Automated Library Drives Status Accesses the dialog for specifying which drives of the selected automated library are to be monitored by the KM. By default, all automated library drives are monitored. Select [default] to reset to the default drive status mapping rule. TSM_LIBRARY Icon Name Description Units Default Alert Conditions BPPM Type TSMLibraryState Set by TSMLibraryCollector. 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 None Availability TSMLibraryStatus Set by TSMLibraryCollector. Monitors the status of the automated library. This status is determined by the automated library status mapping rule defined in the KM command Configuration > Automated Library (Libraries) Status. 0 = OK 1= Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. Classes and Parameters 138 Parameters

139 TSMLibrarySummary Set by TSMLibraryCollector. Summarizes the automated library information as reported by commands executed by the data collector. TSMLibraryUpDriveCou nt Set by TSMLibraryCollector. Count Displays the number up / online state drives in this robotic library. None Count None TSMLibraryVolumePriva Set by TSMLibraryCollector. Count tecount Displays the number of private volumes in the automated library. None TSMLibraryVolumeScrat Set by TSMLibraryCollector. Count chcount Displays the number of scratch volumes in the automated library. None TSMLibraryVolumeScrat Set by TSMLibraryCollector. chpercent* Monitors the percentage of scratch volume against the total number of volume loaded in this automated library. If this parameter changes to warning or alarm state, the recovery action will trigger an event. None If this parameter changes to warning or alarm state, the recovery action will trigger an event. TSMLibraryVolumeCoun Set by TSMLibraryCollector. t Displays the total number of volume loaded in this automated library. For detailed information about Baselining and Percentage (%) KPI, see Managing Baselines and Key Performance Indicators. InfoBox Name Description Name Name of the automated library. Description Description of the automated library. Device Device path of the automated library. Type Type of the automated library. Server Name Name of the remote host where the automated library is connected. Node Name Name of the node that the automated library is assigned to. 139 Classes and Parameters * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM.

140 External Manager Name of the external server responsible for controlling access to library resources. Primary Library Manager Name of the server responsible for controlling access to library resources. Path Online Whether the path for the automated library is online and available for use (Yes or No). Status Status of the automated library as determined by the TSM KM. Shared Whether this library is shared with other servers in a storage area network (SAN). Lan Free Whether an external library is used for LAN-free operations. Obey Mount Retention Whether the server uses the value set for mount retention in the device class associated with this external library. Serial Number Serial number of the automated library. World Wide Name World Wide Name of the port the automated library is attached to. ACS Id Number of this STK library assigned by the ACSSA (Automatic Cartridge System, System Administrator). This can be a number from 1 to 64. Private Category Category number for private volumes. Scratch Category Category number for scratch volumes. Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Function Description Reports > Automated Library Contents Reports the library volume contents of the selected automated library instance. Configuration > Automated Library Accesses the individual configuration for monitoring the selected automated library instance. This dialog allows the selected automated library instance to be enabled or disabled for monitoring by the TSM KM. Configuration > Automated Library Status Accesses the individual configuration for determining the status for the selected automated library instance. By default, the global TSMLibraryState to TSMLibraryStatus mapping rule is used, as configured at the container level. Select [default] to revert to the library status mapping rule configured at the global/container level. Configuration > Automated Library Drives Accesses the dialog for specifying which drives of the selected automated library are to be monitored by the TSM KM. By default, all automated library drives are monitored. Classes and Parameters 140 Menu Commands

141 Accesses the configuration for determining status for monitored drive instances on the selected automated library instance. By default, the global TSMLDriveState to TSMLDriveStatus mapping rule is used, as configured at the container level. Select [default] to revert to the drive status mapping rule configured at the global/container level. Configuration > Automated Library Drives Status 141 Classes and Parameters

142 TSM_LDEVICE Icon Parameters Description Units Default Alert Conditions BPPM Type TSMLDriveState Set by TSMLibraryCollector. Displays the state of the automated library drive. This is determined from the automated library drive control information. 0 = Online None 1 = Empty 2 = Loaded 3= Unloaded 4= Reserved 5= Unavailabl e 6 = Drive Offline 7 = Path Offline -1 = Unknown Availability TSMLDriveStatus Set by TSMLibraryCollector. Monitors the status of the automated library drive. This status is determined by the automated library drive status mapping rule defined in the KM command Configuration > Automated Library Drive(s) Status. 0 = OK 1= Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. TSMLDriveSummary Set by TSMLibraryCollector. Summarizes the automated library drive information as reported by commands executed by the data collector. InfoBox Classes and Parameters 142 Name

143 Description Name Name of the automated library drive. Description Description of the drive. Device Device path of the drive. Type Volume type used in the drive. Server Name Name of the remote host where the drive is connected. Node Name Name of the node that the drive is assigned to. External Manager Name of the external server responsible for controlling access to drive resources. Library Name Name of the automated library the drive is assigned to. Drive Online Whether the drive is available for use. (Yes or No) Path Online Whether the path for the drive is online and available for use (Yes or No). Element Location of the element address of the drive within a SCSI library. The server uses the element address to connect the physical location of the drive to SCSI address of the drive. Status Status of the drive as determined by the TSM KM. Allocated To The name of the library client currently using the drive. Serial Number Serial number of the drive. World Wide Name World Wide Name of the port the drive is attached to. Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Menu Commands Function Description Administration > Clean Allows the selected automated library drive to be cleaned. Drive Administration > Online Drive Allows the selected automated library drive to be brought online. Administration > Offline Drive Allows the selected automated library drive to be taken offline. Configuration > Automated Library Drive Accesses the individual configuration for monitoring the selected automated library drive instance. This dialog allows the selected drive instance to be enabled or disabled for monitoring by the TSM KM. 143 Classes and Parameters Name

144 Configuration > Automated Library Drive Status Accesses the individual configuration for determining the drive status for the selected automated library drive instance. By default, the TSMLDriveState to TSMLDriveStatus mapping rule configured at the parent level is used. (Note that if the mapping rule has not been modified for the parent automated library, then the default is the global mapping rule configured at the container level.) Select [default] to revert to the drive status mapping rule configured at the parent instance level. TSM_DEVICE_CONTAINER Icon Parameters Name Description Units Default Alert Conditions BPPM Type TSMDriveDetails Set by TSMDeviceCollector. Displays all data returned to standard out from commands executed by the data collector. Name Description Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Menu Commands Function Description Configuration > Manual Drives Accesses the dialog for specifying which manual drives are to be monitored by the TSM KM. By default, all local and remote manual drives are monitored for a server and all local manual drives are monitored for a storage agent. Type [default] to reset to the default configuration. Classes and Parameters 144 InfoBox

145 Configuration > Manual Drives Status Accesses the global configuration for determining the status for monitored manual drive instances. By default, the following TSMDriveState to TSMDriveStatus mapping rule is used: Select [default] to reset to the default manual drive status mapping rule. TSM_DEVICE Icon Parameters Description Units TSMDriveState Set by TSMDriveCollector. Displays the state of the manual drive. This is determined from the manual drive control information. 0 = Online None 1 = Empty 2 = Loaded 3= Unloaded 4= Reserved 5= Unavailabl e 6 = Drive Offline 7 = Path Offline -1 =Unknown Availability TSMDriveStatus Set by TSMDriveCollector. Monitors the status of the manual drive. This status is determined by the manual drive status mapping rule defined in the KM command Configuration > Manual Drive(s) Status. 0 = OK Warning = 1 1= Alarm = 2 Suspicious 2 = Failure Availability 145 Default Alert Conditions BPPM Type Classes and Parameters Name

146 If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. TSMDriveSummary Set by TSMDriveCollector. Summarizes the manual drive information as reported by commands executed by the data collector. Name Description Name Name of the manual drive. Description Description of the drive. Device Device path of the drive. Type Volume type used in the drive. Server Name Name of the remote host where the drive is connected. Node Name Name of the node that the drive is assigned to. External Manager Name of the external server responsible for controlling access to drive resources. Library Name Name of the manual library the drive is assigned to. Drive Online Whether the drive is available for use. (Yes or No) Path Online Whether the path for the drive is online and available for use (Yes or No). Element Location of the element address of the drive within a SCSI library. The server uses the element address to connect the physical location of the drive to SCSI address of the drive. Status Status of the drive as determined by the TSM KM. Allocated To The name of the library client currently using the drive. Serial Number Serial number of the drive. World Wide Name World Wide Name of the port the drive is attached to. Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Classes and Parameters 146 InfoBox

147 Menu Commands Function Description Administration > Clean Drive Allows the selected manual library drive to be cleaned. Administration > Online Drive Allows the selected manual library drive to be brought online. Administration > Offline Drive Allows the selected manual library drive to be taken offline. Configuration > Manual Accesses the individual configuration for monitoring the selected manual drive Drive instance. This dialog allows the selected manual drive instance to be enabled or disabled for monitoring by the TSM KM. Configuration > Manual Accesses the individual configuration for determining the manual drive status Drive Status for the selected manual drive instance. By default, the global TSMDriveState to TSMDriveStatus mapping rule is used, as configured at the container level. Select [default] to revert to the drive status mapping rule configured at the global/container level. TSM_POOL_CONTAINER Icon Name Description Units TSMPoolDetails Set by TSMPoolCollector. Displays all data returned to the standard out from commands executed by the data collector. Default Alert Conditions BPPM Type InfoBox Name Description Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. 147 Classes and Parameters Parameters

148 Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Menu Commands Function Description Configuration > Volume Accesses the dialog for specifying which storage pools are to be monitored by Pools the TSM KM. By default, all storage pools configured on the server are monitored. Type "[default]" to reset to the default configuration. Classes and Parameters 148

149 TSM_POOL Icon Parameters Name Description Units Default Alert Conditions BPPM Type TSMPoolSpaceAvailabl e* Set by TSMPoolCollector. Monitors the available volume space for the backup data to use in this storage pool. Gigabytes (GB) Warning < 1 Alarm = 0 Availability TSMPoolSpaceGrowthR ate Set by TSMPoolCollector. Displays the growth rate of the total volume space used by the backup data in this storage pool. Gigabytes None per second (GB/s) TSMPoolSpaceLogicalP ercent* Set by TSMPoolCollector. Displays Percentage None the logical occupancy of the (%) storage pool as a percentage of the total occupancy. TSMPoolSpaceMigrated Set by TSMPoolCollector. Displays Gigabytes * the amount of 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 parameter is not available for copy storage pools. None TSMPoolSpaceMigrated Set by TSMPoolCollector. Displays Percentage None Percent* an estimate of the percentage of (%) data in the storage pool that can be migrated. Note: This parameter is not available for copy storage pools. 149 Classes and Parameters If this parameter changes to warning or alarm state, the recovery action will trigger an event.

150 Set by TSMPoolCollector. Displays the amount of 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 parameter is not available for copy storage pools. Seconds None Gigabytes (GB) None TSMPoolSpaceReclaima Set by TSMPoolCollector. Displays Percentage None blepercent* the amount of reclaimable space (%) as a percentage of the total storage pool space. TSMPoolSpaceUsed* TSMPoolSpaceReclaima Set by TSMPoolCollector. Displays ble* the amount of space in the storage pool that is reclaimable. Set by TSMPoolCollector. Displays Gigabytes the total volume space occupied by (GB) the backup data in this storage pool. None TSMPoolSpaceUsedPerc Set by TSMPoolCollector. Monitors ent* the percentage of total occupied volume space against the total volume capacity of this storage pool (not including any scratch volumes). If this parameter changes to warning or alarm state, the recovery action will trigger an event. Percentage Warning > 95 (%) Alarm > 98 TSMPoolSummary TSMVolumeActiveCount Set by TSMPoolCollector. Displays the number of 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.) Count None TSMVolumeActivePerce nt* Percentage None (%) Classes and Parameters Set by TSMPoolCollector. Summarizes the storage pool information as reported by commands executed by the data collector. Set by TSMPoolCollector. Monitors the percentage of active volumes against the total number of volumes in this storage pool. If the status of the parameter changes to warning or alarm state, the recovery action will trigger an event. 150 TSMPoolSpaceMigratio nelapsed

151 Count None TSMVolumeAvailablePe Set by TSMPoolCollector. Monitors rcent* the percentage of available volumes against the total number of volumes in this storage pool. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Percentage None (%) TSMVolumeCount Count None TSMVolumeEmptyCount Set by TSMPoolCollector. Displays Count the number of empty volumes in this storage pool. ("Empty" is a possible status for a tape volume, indicating that no data is stored on that volume) None TSMVolumeFullCount Set by TSMPoolCollector. Displays the number of full volumes in this storage pool. ("Full" is a possible status for a tape volume.) Count None TSMVolumeFullPercent * Set by TSMPoolCollector. Monitors the percentage of full volumes against the total number of volumes in this storage pool. If this parameter changes to warning or alarm state, the recovery action will trigger an event. Percentage None (%) TSMVolumeOfflineCoun Set by TSMPoolCollector. Displays t the number of offline volumes in this storage pool. ("Offline" is a possible status for a disk volume.) Count None TSMVolumePendingCou Set by TSMPoolCollector. Displays nt the number of pending volumes in this storage pool. ("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.) Count None For detailed information about Set by TSMPoolCollector. Displays the total number of volumes in this storage pool. Baselining and KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. InfoBox 151 Classes and Parameters TSMVolumeAvailableCo Set by TSMPoolCollector. Displays unt the number of volumes assigned to this storage pool.

152 Name Description Name Name of the storage pool. Description Description of the storage pool. Type Type of the storage pool Device Class Name of the device class assigned to the storage pool. Access How the data in the storage pool can be accessed. Storage Pool Data Format Type of data format used to write data to this storage pool, For example: NATIVE or NETAPPDUMP. Maximum Scratch Volumes Maximum number of scratch volumes that the server can request for the storage pool. (Sequential access storage pools only.) Migration In Progress Whether at least one migration process is active for the storage pool. Reclamation In Progress Whether a reclamation process is active for the storage pool. Volume Being Migrated/Reclaimed Name of a volume for which migration or reclamation processing is active. If no migration or reclamation processes are active, this field displays as N/A. Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Function Description Reports > Volumes List Reports all volumes in the selected storage pool, and their states. Configuration > Storage Pool Accesses the individual configuration for monitoring the selected storage pool instance. This dialog allows the selected storage pool instance to be enabled or disabled for monitoring by the TSM KM. Classes and Parameters 152 Menu Commands

153 TSM_PROCESS_CONTAINER Icon Parameters Name Description Units Default Alert BPPM Type Conditions TSMProcessDetails Set by TSMProcessCollector. Displays all data returned to the standard out from commands executed by the data collector. InfoBox Name Description Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Function Description Acknowledgement > Warnings Allows acknowledgement of warning alerts occurring on any monitored process instance. This dialog allows acknowledgement of any process in a "suspicious" state (which sets the parameter TSMProcessStatus to Warning). Acknowledgement > Alarms Allows acknowledgement of alarms occurring on any monitored process instance. This dialog allows acknowledgement of any process in a "failure" state (which sets the parameter TSMProcessStatus to Alarm). Acknowledgement > All Allows acknowledgement of all warnings and alarms occurring on any monitored process instance. This dialog allows acknowledgement of any process in a "suspicious" or "failure" state (which sets the parameter TSMProcessStatus to Warning or Alarm, respectively). 153 Classes and Parameters Menu Commands

154 Reports > Active Processes Reports a list of all active processes on the managed node. Configuration > Processes Accesses the dialog for specifying which processes are to be monitored by thetsm KM. By default, all processes are monitored for 3 days. The age of a process is calculated from the process start time. Configuration > Processes Status Accesses the configuration for determining the status for all monitored process instances. By default, the following TSMProcessState to TSMProcessStatus mapping rule is used: Select [default] to reset to the default mapping rule. TSM_PROCESS Icon Name Description Units Default Alert Conditions BPPM Type TSMProcessDuration Set by TSMProcessCollector. Displays the number of seconds since the start of the process. Seconds None TSMProcessItemCount* Set by TSMProcessCollector. Displays the number of items processed. Count None TSMProcessSize Set by TSMProcessCollector. Displays the amount of data processed. Megabytes (MB) None TSMProcessState Set by TSMProcessCollector. Displays the state of the process. This is determined from the process control information. 0 = Running None 1= Running/ Errors 2= Completed/ Success Classes and Parameters 154 Availability Parameters

155 3= Completed/ Failure -1 = Unknown TSMProcessStatus Set by TSMProcessCollector. Monitors the status of the process. This status is determined by the process status mapping rule defined in the KM command Configuration > Processes Status. 0 = OK 1= Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability None Megabytes per second (MB/s) None If this status parameter changes to warning or alarm state, the recovery action will trigger an event and annotate the last data point. TSMProcessSummary Set by TSMProcessCollector. Summarizes the process information as reported by commands executed by the data collector. TSMProcessThroughput Set by TSMProcessCollector. * Displays the throughput of the process during the last backup event. For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators. * Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance in BPPM. Name Description Process Name Name of the process. Process Number Number assigned to the process. Process Mode Mode in which the process is/was run. For example BACKGROUND Status Completion status of the process. Start Date & time when the process started. End Date & time at the completion of the process. Duration Duration of the process. Size Size of the process, in bytes. Items Number of items processed. Last Message Last message reported in the server activity log. 155 InfoBox Classes and Parameters

156 Collector Name Name of the data collector that sets variables and parameters under this application instance. Collector Last Start Date & time when the last data collection cycle started. Collector Last End Date & time at the completion of the last data collection cycle. Collector Next Start Date & time when the next data collection cycle is expected to start. Collector Status Data collector execution status (Idle or Running). Menu Commands Description Acknowledgement > Alert Allows acknowledgement of all warnings and alarms occurring on the selected process instance. This dialog allows acknowledgement if the selected process is in a "suspicious" or "failure" state (which sets the parameter TSMProcessStatus to Warning or Alarm, respectively). Administration > Cancel Process Allows the selected process instance to be canceled. Function Classes and Parameters 156

157 Troubleshooting

158 Impact on Resources This section describes: CPU and memory usage of the KM Network traffic generated by the KM CPU and Memory Usage CPU and memory usage will depend on the size and complexity of your environment and your TSM KM configuration. As you increase data collection frequency, increase the number of instances monitored by the KM or add functionality through customization, your CPU and memory usage will increase. When monitoring a standard installation of Tivoli Storage Manager using TSM KM, the PATROL Agent will consume between 5MBytes and 10MBytes of additional system memory. An enterprise installation of Tivoli Storage Manager Server with multiple Storage Agents, Clients, Automated Libraries, and Manual Drives can consume more memory (as per other KMs used by the PATROL Agent). The memory usage of TSM KM can be reduced by: disabling monitoring unnecessary component instances (by using the configuration menu) disabling unwanted components (by setting their instance limits to 0) disabling unwanted collectors (by using the PATROL Configuration Manager) increasing the collector scheduling interval (by using the PATROL Configuration Manager) decreasing the instance limits to limit the number of instances created by the collectors Network Traffic Under normal conditions, the TSM KM generates minimal network traffic. Most of the data is kept on the managed node. The amount of network traffic that it generates depends on the number of PATROL Consoles that are connected to the PATROL Agent and the frequency of data collection. Impact on Resources 158 The data collectors in TSM KM uses Tivoli Storage Manager command line interface to obtain Tivoli Storage Manager information. Most of the performance degradation is associated with these command executions and amount of data returned. It may improve the overall performance, if the regular housekeeping is followed on all Tivoli Storage Manager systems.

159 Additional Information

160 Where to Find Additional Help Additional help for BMC PATROL can be found in the following locations: PATROL Console User Guide PATROL Console Online Help Other PATROL Manuals and Guides Additional help for Tivoli Storage Manager can be found in the following locations: Tivoli Storage Manager Quick Start Tivoli Storage Manager Administrator s Guide Tivoli Storage Manager Administrator s Reference Tivoli Storage Manager Messages Document Tivoli Storage Manager Backup-Archive Clients Installation and User s Guide Additional help for Tivoli Storage Manager KM for PATROL can be found in the following location: Where to Find Additional Help 160

161 TSM_DAEMON_CONTAINER 102 TSM_DATABASE 107 TSM_DATABASE_CONTAINER 106 TSM_DEVICE 145 TSM_DEVICE_CONTAINER 144 TSM_JOB 129 TSM_LDEVICE 142 TSM_LIBRARY 138 TSM_LIBRARY_CONTAINER 137 TSM_LOG 114 TSM_LOG_CONTAINER 112 TSM_MOUNT 135 TSM_MOUNT_CONTAINER 134 TSM_PCLIENT 124 TSM_POLICY_CONTAINER 118 TSM_POOL 149 TSM_POOL_CONTAINER 147 TSM_PROCESS 154 TSM_PROCESS_CONTAINER 153 TSM_SERVER 90 Index -A Abnormalities Access 57 Permissions User 17 Acknowledge 17 Alarm 84 Alerts 84 Job Alerts 84 Log Alerts 84 Process Alerts 84 Warning 84 Acknowledgement 76 -B- Add 55, 56 Create 55 Update 56 Admin Interface Login Administer Baselines BMC ProactiveNet Performance Management 57 Generation 57 Manage 57 Requirements 57 BMC 48 Library Drives 61 Manual Drives 61 Mount Requests 60 Agent PATROL Alarm 48 Acknowledge 84 Alarm Filter State Rules Alert Acknowledgement Configure Job 76 Log 76 Alerts BMC ProactiveNet Performance Management Portal 54 BMC PATROL Changes 15 BMC ProactiveNet Integration 54 BMC ProactiveNet Performance Management Abnormalities 57 Baselines 57 Key Performance Indicators KPI Acknowledge Application Clas 84 TSM_POLICY Application Class 119 TSM_CLIENT 99 TSM_CLIENT_CONTAINER TSM_DAEMON 103 -CCancel 97 Mount Request Changes 8 Check Configure Job 76 Log 76 Adapter 54

162 Instance Limits Classes 89 Clean Drive Clients Force Databases 51 Delete Disable Enable Debug 61 Delete 65 Disable 65 Enable 65 Status Configuration Cluster Configure 64 Clustering Application Commands Reload 84 Configuration Admin Interface Login Debug 90 Instance Limits 90 Login 90 Monitoring Mode 90 Node Status 90 Node Type 90 Paths 90 Preloading 90 Configure 90 Alert Acknowledgement 76 Cluster 64 Domain Backup Restriction 76 KM User Account 48 Log Error Filter 72 Log Scan Limit 74 Monitoring Period 67 Multi-Node Monitoring Mode 64 Node Type 63 Paths 62 PATROL Agent 46 Customize KM Disable 81 Enable 81 End 81 Files 81 Path 81 Delete Clients 65 Daemons 65 Databases 65 Logs 65 Policies 65 Policy Clients 65 Robotic Drives 65 Robotic Libraries 65 Standalone Drives 65 Storages 65 Volume Pools 65 Disable Clients 65 Daemons 65 Databases 65 Debug 81 Logs 65 Policies 65 Policy Clients 65 Robotic Drives 65 Robotic Libraries 65 Standalone Drives 65 Storages 65 Volume Pools 65 Discoveries Force Discovery 79 Verify 51 Domain Backup Restriction -D- Configure 76 DSM_CONFIG 62 DSM_DIR 62 DSM_LOG 62 Daemons Delete 65 Disable 65 Enable 65 Status Configuration Data Collectors Check

163 -E- -G- Enable Generate Clients 65 Daemons 65 Databases 65 Debug 81 Logs 65 Policies 65 Policy Clients 65 Robotic Drives 65 Robotic Libraries 65 Standalone Drives 65 Storages 65 Volume Pools 65 Baselines 57 Reports 86 -Hhelp -IAccess 149 ACS Id 138 Action 129 Activated Default Management Class 119 Activated Policy Set 119 Activation Date/Time 119 Actual Start 129 Aggregate Data Transfer Rate 129 Allocated To 142, 145 Application 99 Application Name 90 Application Version 90 Archive Retention 119 Assigned Space 107 Available FS Space 114 Available Space 107 Backup Retention 119 Binary Path 90 Buffer Pool Pages 107 Collector Last End 97, 99, 102, 103, 106, 107, 112, 114, 118, 119, 124, 126, 129, 134, 135, 137, 138, 142, 144, 145, 147, 149, 153, 154 Collector Last Start 97, 102, 103, 106, 107, 112, 114, 118, 119, 124, 126, 129, 134, 135, 137, 138, 142, 144, 145, 147, 149, 153, 154 Collector Name 97, 99, 102, 103, 106, 107, 112, 114, 118, 119, 124, 126, 129, 134, 135, 137, 138, 142, 144, 145, 147, 149, 153, 154 Collector Next Start 97, 99, 102, 103, 106, 107, 112, 114, 118, 119, 124, 126, 129, 134, 135, 137, 138, 142, 144, 145, 147, 149, 153, ins_all_<version>.tar 22 ins_windows_<version>.exe Setup 24 setup.exe 26 setup.sh 26 uninstall.exe 39 uninstall.sh 39 Filtering Options 22 Clients 65 Daemons 65 Databases 65 Logs 65 Policies 65 Policy Clients 65 Robotic Drives 65 Robotic Libraries 65 Standalone Drives 65 Storages 65 Volume Pools 65 Force All Data Collectors 79 All Discoveries 79 Full data collection 79 Selected Data Collectors Force Discovery Improvement InfoBox -FFailover Group Name Files

164 Library Path 90 Log File Modification Time 114 Log File Size 114 Maximum Extension 107 Maximum Percent Utilized 107 Maximum Reduction 107 Maximum Scratch Volumes 149 Migration In Progress 149 Mode 129, 135 Monitoring Mode 90 Monitoring Node 90 Name 99, 103, 107, 114, 119, 124, 138, 142, 145, 149 Network Data Transfer Rate 129 Next Backup 119, 124 Next Backup Schedule Name 119, 124 Node Name 129, 138, 142, 145 Node Name(s) 90 Node Type 90 Number of Registered Nodes 119 Obey Mount Retention 138 Objects Compression 129 Objects Deleted 129 Objects Expired 129 Objects Failed 129 Objects Inspected 129 Objects Processed 129 Objects Rebound 129 Objects Updated 129 Operating System 90, 99, 124 Owner 103 Page Size 107 Path 107, 114 Path Online 138, 142, 145 PATROL Agent Version 90 Percent Completed 129 Percent Utilized 107 Physical Volumes 107 PID 103 Platform 90 PPID 103 Primary Library Manager 138 Private Category 138 Process Mode 154 Process Name 154 Process Number 154 Processing Time 129 Product Name 90 Product Release Date 90 Collector Status 97, 99, 102, 103, 106, 107, 112, 114, 118, 119, 124, 126, 129, 134, 135, 137, 138, 142, 144, 145, 147, 149, 153, 154 Command 103 Completed 129 Copyright 90 Data Transfer Time 129 Description 99, 103, 107, 114, 119, 124, 135, 138, 142, 145, 149 Device 138, 142, 145 Device Class 149 Domain Name 124, 129 Drive Name 135 Drive Online 142, 145 Duration 154 Element 142, 145 End 154 Event Status 129 External Manager 138, 142, 145 FS Percent Used 114 Host Name 90 Installation Path 90 Items 154 Job 129 Job Type 135 Lan Free 138 Last Backup 107 Last Backup Duration 129 Last Backup End 119, 124, 129 Last Backup Job 119, 129 Last Backup Mode 107 Last Backup Objects 129 Last Backup Save Group 124 Last Backup Size 129 Last Backup Start 119, 124, 129 Last Backup Status 119, 124 Last Communication Method 99 Last Full Backup End 119, 124 Last Full Backup Job 119, 124 Last Full Backup Start 119, 124 Last Incr Backup End 119 Last Incr Backup End Time 124 Last Incr Backup Job 119, 124 Last Incr Backup Start 119, 124 Last Message 154 Last Purge 107, 114 Library Name 135, 142, InfoBox

165 InfoBox Fixed BMC Software Installation Utility Log 26 Packages 24 Procedure 26 Setup Files 24 Installation 62 Instance Limits 22 -J Job Alerts Acknowledge Jobs 84 Configure 67 Monitoring Period 67 Status Configuration 71 -KKey Performance Indicators BMC ProactiveNet Performance Management 57 Manage 57 KM Configure 48 Customize 61 Initial Setup 52 Load 45, 46, 54 Preload 46 Preloaded 47, 48 Unload 46, 47, 48 User Account 48 KPI BMC ProactiveNet Performance Management 57 Manage 57 -LLibrary Drives Administer 61 Clean 61 Offline 61 Online 61 Load KM 45, 46, 54 PATROL Central Log Alerts Check 51 Integration Acknowledge Log Error Filter BMC ProactiveNet 54 Integration Service Agent 55 Introduction 26 Issues Configure 72 Log Scan Limit Configure Logs Product Version 90 Reason 129 Reclamation In Progress 149 Reply Required 135 Request ID 135 Request Time 135 Request Timeout 135 Result 129 Schedule 129 Scheduled Start 129 Scratch Category 138 Serial Number 138, 142, 145 Server 90 Server Name 135, 138, 142, 145 Session Numbers 129 Shared 138 Size 129, 154 Start 154 Status 99, 103, 119, 129, 138, 142, 145, 154 Storage Pool Data Format 149 Support 90 Time Remaining 129 Time Since Last Communication 99 Total FS Space 114 Total Usable Pages 107 Type 129, 138, 142, 145, 149 Used Pages 107 Version 99 Volume 135 Volume Being Migrated/Reclaimed 149 Volume Type 135 Web Site 90 World Wide Name 138, 142, 145 Install / Un-install 26, 39 8

166 Delete Disable Enable Client Status 99 Clients 97 Clients Status 97 Configuration 97, 99, 102, 103, 106, 107, 112, 118, 119, 124, 126, 134, 137, 138, 142, 144, 145, 147, 149, 153 Daemon 103 Daemon List 102 Daemons 102 Daemons Status 102, 103 Database 107 Database Backup Volume History 106 Database Volumes 107 Databases 106 Domain 119 Domain Backup Restriction 119 Domain Schedule 119 Domain Status 119 Domains 118 Domains Backup Restriction 118 Domains Status 118 Force Discovery 90 Force Full Collection 126 Jobs 126 Jobs Alert Acknowledgement 126 Jobs Status 126 KM Status 90 Log 114 Log Alert Acknowledgement 114 Log Filter 114 Log Scan Limit 114 Logs 112 Logs Alert Acknowledgement 112 Logs Filter 112 Logs Scan Limit 112 Manual Drive 145 Manual Drive Status 145 Manual Drives 144 Manual Drives Status 144 Mount Requests 134 Mount Requests Status 134 Offline Drive 142, 145 Online Drive 142, 145 Pending Mount Requests 134 Processes 153 Processes Status 153 Refresh Parameters 90 Refresh Process Cache 90 Reload Commands MManage Baselines 57 Key Performance Indicators KPI 57 Managed Node Status Configuration Manual Drives Administer 61 Clean 61 Offline 61 Online 61 Master Server Configure Media Server 63 Configure 63 Menu Commands About 90 Acknowledgement 114, 126, 129, 153, 154 Active Processes 153 Activity Log Messages 112 Administration 90, 134, 135, 142, 145, 154 Al 153 Alarms 114, 126, 153 Alert 129, 154 All 114, 126 Automated Libraries 137 Automated Libraries Status 137 Automated Library 138 Automated Library Contents 138 Automated Library Drive 142 Automated Library Drive Status 142 Automated Library Drives 138 Automated Library Drives Status 137, 138 Automated Library Status 138 Cancel 135 Cancel All 134 Cancel Process 154 Clean Drive 142, 145 Client 99 Client Node 124 Client Nodes Logs

167 Reply 135 Reports 102, 106, 107, 112, 119, 134, 138, 149, 153 Start Server 90 Start Storage Agent 90 Stop Server 90 Storage Pool 149 Volume Pools 147 Volumes List 149 Warnings 114, 126, 153 Monitor Type 55 Monitoring Period Configure 67 Jobs 67 Mount Requests Processes 67 Mount Requests Managed System View Log 26 Oracle Solaris Cluster Parameter TSMLoginStatus Parameters Configure 63 Master Server 63 Media Server 63 Notification 60 -OOffline Drive Online 48 ExtraFilesList 90 Refresh 79 TSMClientCollector 90 TSMClientDetails 97 TSMClientLastAccessElapsed 99 TSMClientSpaceUsed 99 TSMClientState 99 TSMClientStatus 99 TSMClientSummary 99 TSMCreateDistribution 90 TSMDaemonCollector 90 TSMDaemonCollectorExecTime 102 TSMDaemonCPUDuration 103 TSMDaemonCPUUtilization 103 TSMDaemonDetails 102 TSMDaemonMemorySize 103 TSMDaemonProcessCount 103 TSMDaemonState 103 TSMDaemonStatus 103 TSMDaemonSummary 103 TSMDatabaseBackupElapsed 107 TSMDatabaseCacheHitPercent 107 TSMDatabaseCacheWaitPercent 107 TSMDatabaseCollector 90 TSMDatabaseDetails 106 TSMDatabaseFSSpaceUsedPercent 107 TSMDatabaseLogConsumedSize 107 TSMDatabaseLogPoolUsedPercent 107 TSMDatabaseLogPoolWaitPercent 107 TSMDatabasePoolHitPercent 107 TSMDatabaseReorgElapsed 107 TSMDatabaseSpaceAvailable 107 TSMDatabaseSpaceChanged 107 TSMDatabaseSpaceChangedPercent 107 TSMDatabaseSpaceGrowthRate 107 TSMDatabaseSpaceMaxExtension 107 TSMDatabaseSpaceMaxReduction 107 TSMDatabaseSpaceUsed 107 TSMDatabaseSpaceUsedPercent 107 -NNew features Node Type 64 -P- Administer 60 Cancel 60 Configure 67 Monitoring Period 67 Status Configuration 71 Multi-Node Monitoring Mode Configure Drive 61 Operating Systems Linux 22, 24, 26, 39 Unix 22, 24, 39 Windows 22, 24, 26, 39 Options Common services 26 Console Systems role Menu Commands

168 89 TSMLibraryVolumeScratchCount 138 TSMLibraryVolumeScratchPercent 138 TSMLogAlarmCount 114 TSMLogAlarmText 114 TSMLogCollector 90 TSMLogDetails 112 TSMLogFSSpaceUsedPercent 114 TSMLoginStatus 90 TSMLogSpaceAvailable 114 TSMLogSpaceGrowthRate 114 TSMLogSpaceUsed 114 TSMLogSpaceUsedPercent 114 TSMLogSummary 114 TSMLogText 114 TSMLogWarningCount 114 TSMLogWarningText 114 TSMMonitoringMode 90 TSMNodeBackupSummary 124 TSMNodeBackupThroughput 124 TSMNodeFullBackupDuration 124 TSMNodeFullBackupObjectCount 124 TSMNodeFullBackupSize 124 TSMNodeIncrBackupDuration 124 TSMNodeIncrBackupObjectCount 124 TSMNodeIncrBackupSize 124 TSMNodeStatus 90 TSMNodeSummary 124 TSMObjectCount 129 TSMObjectExcludeList 124 TSMObjectExpiredCount 129 TSMObjectFailedCount 129 TSMObjectIncludeList 124 TSMObjectProcessedCount 129 TSMObjectReboundCount 129 TSMObjectUpdatedCount 129 TSMPoolCollector 90 TSMPoolDetails 147 TSMPoolSpaceAvailable 149 TSMPoolSpaceGrowthRate 149 TSMPoolSpaceLogicalPercent 149 TSMPoolSpaceMigrated 149 TSMPoolSpaceMigratedPercent 149 TSMPoolSpaceMigrationElapsed 149 TSMPoolSpaceReclaimable 149 TSMPoolSpaceReclaimablePercent 149 TSMPoolSpaceUsed 149 TSMPoolSpaceUsedPercent 149 TSMPoolSummary 149 TSMProcessCollector 90 TSMDatabaseSummary 107 TSMDomainBackupElapsed 119 TSMDomainBackupSummary 119 TSMDomainBackupThroughput 119 TSMDomainCollector 90 TSMDomainDetails 118 TSMDomainFullBackupDuration 119 TSMDomainFullBackupElapsed 119 TSMDomainFullBackupObjectCount 119 TSMDomainFullBackupSize 119 TSMDomainIncrBackupDuration 119 TSMDomainIncrBackupElapsed 119 TSMDomainIncrBackupObjectCount 119 TSMDomainIncrBackupSize 119 TSMDomainState 119 TSMDomainStatus 119 TSMDomainSuccBackupElapsed 119 TSMDomainSummary 119 TSMDriveCollector 90 TSMDriveDetails 144 TSMDriveState 145 TSMDriveStatus 145 TSMDriveSummary 145 TSMJobActiveBackupCount 126 TSMJobActiveCount 126 TSMJobActiveNonBackupCount 126 TSMJobCollector 90 TSMJobDetails 126 TSMJobDuration 129 TSMJobErrorCount 129 TSMJobNetworkThroughput 129 TSMJobSize 129 TSMJobState 129 TSMJobStatus 129 TSMJobSummary 129 TSMJobText 129 TSMJobThroughput 129 TSMLDriveState 142 TSMLDriveStatus 142 TSMLDriveSummary 142 TSMLibraryCollector 90 TSMLibraryDetails 137 TSMLibraryState 138 TSMLibraryStatus 138 TSMLibrarySummary 138 TSMLibraryUpDriveCount 138 TSMLibraryVolumeCount 138 TSMLibraryVolumePrivateCount Parameters

169 89 TSMProcessDetails 153 TSMProcessDuration 154 TSMProcessItemCount 154 TSMProcessSize 154 TSMProcessState 154 TSMProcessStatus 154 TSMProcessSummary 154 TSMProcessThroughput 154 TSMRequestCollector 90 TSMRequestDetails 134 TSMRequestElapsed 135 TSMRequestState 135 TSMRequestStatus 135 TSMRequestSummary 135 TSMRequestTimeout 135 TSMUpdateAgent 90 TSMVolumeActiveCount 149 TSMVolumeActivePercent 149 TSMVolumeAvailableCount 149 TSMVolumeAvailablePercent 149 TSMVolumeCount 149 TSMVolumeEmptyCount 149 TSMVolumeFullCount 149 TSMVolumeFullPercent 149 TSMVolumeOfflineCount 149 TSMVolumePendingCount 149 Paths Binary 62 DSM_CONFIG 62 DSM_DIR 62 DSM_LOG 62 Installation 62 Library 62 PATROL Agent 48 PATROL Agent 46, 47 PATROL Central Console 46, 48 PATROL Console 46, 47 PATROL Agent Configure 46 Restart 52 PATROL Console 45 Restart Platform 52 Upgrade Platforms Unix Policies Delete 65 Disable 65 Enable 65 Policy Clients Delete Disable Enable Preload KM 46 Preloaded KM 47, 48 Prepare Debug Files 81 ProactiveNet 55 Process Alerts Acknowledge Processes 84 Configure 67 Monitoring Period PW Commands RRefresh Parameters Release Notes Reload 79 8 Commands 84 remote PATROL Agent Checking Reports Generate Requirements 86 Security 17 Software 15 System 15 Restart PATROL Agent 52 PATROL Console 52 Robotic Drives Delete 65 Disable 65 Enable 65 Status Configuration Robotic Libraries Delete 65 Disable 65 Enable 65 Status Configuration Parameters

170 Customize 56 Import 56 Tivoli Storage Manager -S- Changes TSM_CLIENT Security Start Stop Setup 17 Application Class 99 TSM_CLIENT_CONTAINER Application Class TSM_DAEMON Application Class 103 TSM_DAEMON_CONTAINER Check 52 Initial 52 KM 52 Software Requirements Standalone Drives Application Class TSM_DATABASE Application Class TSM_DEVICE 71 Server 60 Storage Agent 60 Status Configuration Clients 71 Daemons 71 Jobs 71 Managed Node 71 Mount Requests 71 Robotic Drives 71 Robotic Libraries 71 Standalone Drives 71 Stop Start Stop Storages Delete 65 Disable 65 Enable 65 Sudo 17, 48 System Requirements 102 Application Class 107 TSM_DATABASE_CONTAINER 15 Delete 65 Disable 65 Enable 65 Status Configuration Start Server 60 Storage Agent Storage Agent Application Class 145 TSM_DEVICE_CONTAINER Application Class TSM_JOB 144 Application Class TSM_LDEVICE 129 Application Class TSM_LIBRARY 142 Application Class 138 TSM_LIBRARY_CONTAINER Application Class TSM_LOG 137 Application Class 114 TSM_LOG_CONTAINER Application Class TSM_MOUNT 112 Application Class 135 TSM_MOUNT_CONTAINER Application Class TSM_PCLIENT 134 Application Class TSM_POLICY 124 Application Class 119 TSM_POLICY_CONTAINER Application Class TSM_POOL Application Class 149 TSM_POOL_CONTAINER -T - Application Class TSM_PROCESS Thresholds Application Class 154 TSM_PROCESS_CONTAINER Requirements Server 15

171 TSM_PROCESS_CONTAINER Application Class TSM_SERVER 153 Application Class TSMRequestTimeout UUnix 48 Unload KM 46, 47, 48 Upgrade Platform 44 -V Verify Application Discovery 51 Veritas Cluster File System 64 Veritas Cluster Server 64 Volume Pools Delete Disable Enable W Warning 71 Acknowledge 84 Warning Filter State Rules What's new 8 171

172 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 ProactiveNet Performance Management 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.