tivoli storage manager km for patrol - sentry software · tivoli storage manager km for patrol...

User Documentation November 2012

Tivoli Storage Manager KM forPATROLVersion 2.7.00

Contacting BMC SoftwareYou can access the BMC Software Web site at http://www.bmc.com/. From this Web site, you canobtain information about the company, its products, corporate offices, special events, and careeropportunities.

United States and Canada Outside United States and Canada

Address BMC Software, Inc.2101 CityWest Blvd. Houston TX 77042-2827

Telephone (01) 713 918 8800

Telephone 713 918 8800 or 800 841 2031

Fax (01) 713 918 8000

Fax 713 918 8000

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 areregistered trademarks or trademarks of BMC Software, Inc.

IBM is a registered trademark of International Business Machines Corporation.

DB2 is a registered trademark of International Business Machines Corporation.

Oracle is a registered trademark, and the Oracle product names are registered trademarks ortrademarks of Oracle Corporation.

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 LicenseAgreement for the product and the proprietary and restricted rights notices included in thisdocumentation.

Restricted Rights Legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVEDUNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any dataand computer software by the U.S. Government is subject to restrictions, as applicable, set forth inFAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, andDFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC Software, Inc.,2101 CityWest Blvd., Houston, TX 77042-2827, USA. Any contract notices should be sent to this

2

Version 2.7.00

Tivoli Storage Manager KM for PATROL

You can obtain technical support by using the Support page on the BMC Software Web site or bycontacting Customer Support by telephone or e-mail. To expedite your inquiry, please see "BeforeContacting BMC Software."

Support Web Site

You can obtain technical support from BMC Software 24 hours a day, 7 days a week at http://www.bmc.com/support_home. 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 e-mail notices when new product versions are released

Find worldwide BMC Software support center locations and contact information, including e-mailaddresses, fax numbers, and telephone numbers

Support by Telephone or E-mail

In the United States and Canada, if you need technical support and do not have access to the Web,call 800 537 1813. Outside the United States and Canada, please contact your local support center forassistance. To find telephone and email contact information for the BMC Software support center thatservices your location, refer to the Contact Customer Support section of the Support page on the BMCSoftware Web site at http://www.bmc.com/support_home.

Before Contacting BMC Software

Before you contact BMC Software, have the following information available so that Customer Supportcan begin working on your problem immediately:

Product information

product name

product version (release number)

license number and password (trial or permanent)

Operating system and environment information machine type operating system type, version, andservice pack or other maintenance level such as:

PUT or PTF

system hardware configuration

serial numbers

related software (database, application, and communication) including type, version, andservice

pack or maintenance

level

Sequence of events leading to the problem

Commands and options that you used

Messages received (and the time and date that you received them)

product error messages

3

Version 2.7.00


http://www.bmc.com/support_home



Table of Contents 4

Version 2.7.00


Table of Contents...........................................................................................................................14Requirements

...........................................................................................................................14System Requirements

...........................................................................................................................14Software Requirements

...........................................................................................................................16Security Requirements

...........................................................................................................................20Disk Space Requirements

...........................................................................................................................21Getting the BMC Software Installation Utility

...........................................................................................................................22Packages

...........................................................................................................................22Extracting the Setup Files

...........................................................................................................................24Installing Tivoli Storage Manager KM for PATROL

...........................................................................................................................37Uninstalling Tivoli Storage Manager KM for PATROL

...........................................................................................................................42Upgrading the Platform

...........................................................................................................................43Performing Post-Installation Operations

...........................................................................................................................43Loading and Unloading the KM

..................................................................................................................43Loading the KM

..............................................................................................................44Loading the KM on PATROL Console

..............................................................................................................44Loading the KM on PATROL Central

..............................................................................................................44Configuring PATROL Agent to Preload the KM

..................................................................................................................45Unloading the KM

..............................................................................................................45Unloading the KM from the PATROL Agent

..............................................................................................................45Unloading the KM from the PATROL Console

..............................................................................................................46Unloading the KM from the PATROL Central Console

...........................................................................................................................46Configuring the KM User Account

...........................................................................................................................48Verifying Application Discovery

...........................................................................................................................49Checking the Instance Limits

...........................................................................................................................49Checking the Initial Setup of the KM

...........................................................................................................................50Restarting PATROL Agent and PATROL Console

...........................................................................................................................52Integrating with BMC Portal

...........................................................................................................................52Integrating with BMC ProactiveNet Performance Management 8.5.x and 8.6.x

...........................................................................................................................53Creating and Importing an Adapter for a BMC PATROL KM

...........................................................................................................................54Updating an Adapter for a BMC PATROL KM

...........................................................................................................................54Importing and Customizing Thresholds

...........................................................................................................................55Managing Baselines and Key Performance Indicators

Table of Contents 5

Version 2.7.00


...........................................................................................................................58Administering Tivoli Storage Manager

...........................................................................................................................58Starting/Stopping the Server

...........................................................................................................................58Starting/Stopping the Storage Agent

...........................................................................................................................58Administering Mount Requests

...........................................................................................................................59Administering Drives

...........................................................................................................................59Cancelling Processes

...........................................................................................................................59Configuring the KM

...........................................................................................................................60Configuring Paths

...........................................................................................................................60Specifying the Node Type

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

...........................................................................................................................62Filtering Elements to Monitor

...........................................................................................................................64Configuring Monitoring Periods

...........................................................................................................................68Configuring the Elements Status

...........................................................................................................................69Configuring the Log Filter

...........................................................................................................................71Configuring the Log Scan Limit

...........................................................................................................................71Configuring Domain Backup Restriction

...........................................................................................................................72Configuring Alert Acknowledgement

...........................................................................................................................75Refreshing Parameters

...........................................................................................................................77Enabling the Debug Mode

...........................................................................................................................80Reloading Commands

...........................................................................................................................80Acknowledging Alerts

...........................................................................................................................81Generating Reports

...........................................................................................................................83Classes and Parameters

...........................................................................................................................84TSM_SERVER

...........................................................................................................................90TSM_CLIENT_CONTAINER

...........................................................................................................................91TSM_CLIENT

...........................................................................................................................93TSM_DAEMON_CONTAINER

...........................................................................................................................94TSM_DAEMON

...........................................................................................................................96TSM_DATABASE_CONTAINER

...........................................................................................................................97TSM_DATABASE

...........................................................................................................................102TSM_LOG_CONTAINER

...........................................................................................................................104TSM_LOG

...........................................................................................................................107TSM_POLICY_CONTAINER

...........................................................................................................................108TSM_POLICY

...........................................................................................................................112TSM_PCLIENT

...........................................................................................................................114TSM_JOB_CONTAINER

Table of Contents 6

Version 2.7.00


...........................................................................................................................116TSM_JOB

...........................................................................................................................120TSM_MOUNT_CONTAINER

...........................................................................................................................121TSM_MOUNT

...........................................................................................................................123TSM_LIBRARY_CONTAINER

...........................................................................................................................124TSM_LIBRARY

...........................................................................................................................127TSM_LDEVICE

...........................................................................................................................129TSM_DEVICE_CONTAINER

...........................................................................................................................130TSM_DEVICE

...........................................................................................................................132TSM_POOL_CONTAINER

...........................................................................................................................133TSM_POOL

...........................................................................................................................136TSM_PROCESS_CONTAINER

...........................................................................................................................137TSM_PROCESS

...........................................................................................................................140Impact on Resources

...........................................................................................................................142Where to Find Additional Help

Release Notes for v2.7.00

8

Version 2.7.00


What's NewFully compatible with BMC ProactiveNet Central Monitoring Administration, a feature supportedby BMC ProactiveNet Performance Management version 9.0.00.

Now supports Tivoli Storage Manager 6.3 and Microsoft Clustered.

Ability to disable custom events from the KM.

The TSMDaemonCPUUtilization parameter that displays the percentage of CPU consumed bythe daemon, was added to the TSM_DAEMON application class.

In order to easily identify which step the initial discovery is processing, the setup icon nowreflects the successive phases:

Configuring: this information is only available for BMC ProactiveNet Performance Management

Upgrading: this information is only available for PATROL Classic Console

Loading: indicates that commands are being loaded.

Initializing: indicates that KM paths are being initialized. Missing paths are now specified in theSystem Output Window

Discovering: indicates that the monitored application is being monitored.

Cleaning: indicates that the temp files are being cleaned

Validating: indicates the application paths are being checked

Changes and ImprovementsThe KM performance has been improved to support large number Tivoli Storage components.

The performance of the initial job collection cycle has been improved. A new method was addedto enable users to run a PSL command to reduce the duration of the initial job query.

All previous pconfig variables available under /TSM are now split to /TSM and /Runtime/TSMwhile upgrading the KM.

<Component>Summary: Duplicate fields in summary text parameters are removed. Only thefirst entry is kept and all repetitions are ignored even when their values are different.

The job duration calculation method has been improved: job duration/age and job state durationare calculated using the current time instead of job collector start time.

Debug Mode:

The time during which the debug information is logged can now be set by the user.

The KM-related messages that are sent to the System Output Window (SOW) are also loggedto the TSM.log file available under <PATROL_HOME>/log.

Logs:The default log scan limit was increased to 500 KBytes.

The delay required to perform a discovery following an Agent restart has been substantiallyreduced.

All collectors are now automatically refreshed as soon as the KM configuration and the initialdiscovery are complete.

The default number of instances of Application Classes has been removed. This information mustbe defined by the user. When set to 0, the monitoring of a specific Application Class is notperformed.

Client and PClient policy monitoring is now enabled by default with an instance limit set to 50.

When one or more required paths are missing, the setup instance label will now indicate whichpaths are missing. A message will also be displayed in the System Output Window.

The TSMRemoveTempFiles parameter was removed since the temporary files are now createdand removed by default by the agent user.

Daemons: Non-critical daemons are monitored by default as long as they're alive. No alerts willbe triggered when they stop running.

9

Version 2.7.00


Fixed IssuesInitial Job Collection Cycle: The performance of the initial job collection cycle has beenimproved. Users can now run a PSL command to reduce the duration of the initial job query.

TSMClientState: This parameter sometimes mistakenly reported a "Never Communicated"status and triggered a false alarm.

TSM Monitoring: TSM could not be monitored when default TSM error log could not be updatedby the agent user. The DSMADMC commands issued by the KM have thus been modified toredirect the error logs to the KM temporary folder.

Incorrect management of date/time and elapsed time displayed by the KM for some timezones.

Due to a misinterpretation of the daemon status, the DaemonState parameter was set to"Unknown" while the daemon was actually running.

Debug Mode ZIP output: On Windows 2008, the KM failed to create a ZIP archive with thecontent of the debug mode.

Monitoring Mode: When the Multi-node mode was activated, the KM failed to distinguishremote nodes with fully qualified hostnames. This issue is now fixed so that the KM menu onlyrequires the PATROL Agent credentials once per remote node.

Node type was not detected on Windows platforms.

Incorrect 'schedule name' in job summary: The DSMADMC command used by the KM forquerying job details was changed to support comma delimited text in the field 'reason' andconsequently corrected the 'schedule name' .

With some Windows platforms the Debug KM Command was prompting for an OS login to turnthe debug on.

The TSMDaemonState parameter was set to "Not Running" when the PATROL Agent could notfork processes, which resulted in invalid alarms on the TSMDaemonStatus parameter.

Overview

11

Version 2.7.00


Tivoli Storage Manager KM for PATROL monitors your Tivoli Storage Manager application within acentralized 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 spacereclamations

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

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

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

Client: working status

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 quicklyand clearly identify peaks, troughs and trends in the performance of your backup resources.

12

Version 2.7.00


Monitoring Tivoli Storage Manager

Refer to the Reference Guide for more information about the application classes.

Preparing for Installation

14Requirements

Version 2.7.00


Requirements

System RequirementsOperating System Operating System Version

Sun® microsystems SolarisTM 8, 9, 10

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

IBM® AIXTM 5.1, 5.2, 5.3, 6.1

Red Hat® Linux® 7.2

Microsoft® Windows® 2003, 2008, 2008 R2

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

Software RequirementsSoftware Version

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

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

BMC Software PATROL Agent 3.4.20, 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

If the operating system is upgraded (or downgraded) at a later date, you will need to reload commandsfor 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 TivoliStorage 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 temporarytable storage space all the time to avoid exhausting the temporary table storage.

15Requirements

Version 2.7.00


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 atleast 5,000,000. This applies for all Tivoli Storage Manager servers and storage agents where the KMis installed. This adjustment will allow the data collectors to execute without incurring an internalscheduling 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 thefollowing single line PSL command through the PATROL Console OS> prompt to update this tuningvariable.

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)<5000000){pconfig("REPLACE",v,5000000);}

In large Tivoli Storage Manager systems, the value of 5,000,000 for the tuning variable “pslInstructionMax” may still beinsufficient. 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 zeroto disable this functionality.

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 readand write to these pconfig variables at anytime. If Access Control List (ACL) is used to control whichusers are authorized to connect to a PATROL Agent, please ensure that the mode for PATROL Agentuser includes “C” in the PATROL Agent variable /AgentSetup/accessControlList. Please refer thePATROL Agent Reference Manual for more details.

You cannot copy or distribute these KM configuration variables between managed nodes, because they may not havethe same value for each managed node. For example, the login user details may not be the same for all managednodes. Also some of these variables, like installation paths, are set automatically during the initial discovery.

16Requirements

Version 2.7.00


Additional Software Requirements

Purpose Software Version

When running TSM KM on Linuxmanaged nodes

Korn shell binary (/bin/ksh) Any

When running TSM KM on MicrosoftWindows x64 managed nodes

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

Any

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

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

The following user accounts can be used:

On Unix platforms:

a root user

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

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

On Windows platforms:

an administrator user

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

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

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

Access Permissions

The TSM KM user needs “read & execute” permission to executable and library files under the pathslisted below. The Tivoli Storage Manager installation path INSTALL_PATH, referenced below, isnormally /usr/tivoli/tsm or /opt/tivoli/tsm (on Unix) or C:\Program Files\Tivoli\TSM (onMicrosoft Windows).

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



17Requirements

Version 2.7.00


Unix Microsoft Windows

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

INSTALL_PATH/client/admin/bin INSTALL_PATH\Server

INSTALL_PATH/server/bin INSTALL_PATH\StorageAgent

INSTALL_PATH/StorageAgent/bin INSTALL_PATH\Server\tsmdiag

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

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

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

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

The TSM KM includes some scripts which should be executable by the PATROL Agent user and theTSM KM user. These scripts are stored under KM_HOME path, normally PATROL_HOME/TSM.

To list all OS commands used by the TSM KM, execute the following PSL code from the PATROLConsole, using PSL Task menu, after installing and loading the KM.

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

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

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

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

18Requirements

Version 2.7.00


Unix Microsoft Windows

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

DSM_LOG (KM_TEMP) DSM_LOG (KM_TEMP)

DSM_DIR/dsmadmc DSM_DIR\dsmadmc.exe

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

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

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

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

Sudo User for Operating System Access

If a non-root user with sudo privileges is preferred as the TSM KM user, configure the account as asudoer through the visudo utility using code appropriate for your platform as detailed below. Thisuser 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 andreport menu commands using their sudo privileges. The TSM KM accepts any non-root user with thefollowing sudo configuration in the sudoers file. Please replace user1, user2, user3 with appropriateKM user name. The Tivoli Storage Manager installation path INSTALL_PATH, referenced below isnormally /usr/tivoli/tsm or /opt/tivoli/tsm and PATROL_HOME is the path where the PATROLAgent is installed (including the target, like /opt/bmc/Patrol3/Solaris29-sun4/).

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

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

On Solaris:

User_Alias TSMKMUSERS = user1, user2, user3Defaults:TSMKMUSERS !lecture,!authenticate,\env_keep+="LD_LIBRARY_PATH INSTALL_PATH KM_HOME \KM_TEMP DSM_CONFIG DSM_DIR DSM_LOG",env_resetTSMKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\

19Requirements

Version 2.7.00


INSTALL_PATH/server/bin/*,\INSTALL_PATH/client/ba/bin/*,\PATROL_HOME/lib/TSM/*,PATROL_HOME/bin/*

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

On HP-UX:

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


On AIX & Linux:

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


Admin Interface User Access

Tivoli Storage Manager KM for PATROL requires that an administrator account (standardadministrator with no other privileges) be added to the Tivoli Storage Manager server for use byPATROL and the TSM KM.

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

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

20Requirements

Version 2.7.00


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

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

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

To list all DSMADMC commands used by the TSM KM, execute the following PSL code from thePATROL 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); }}

Disk Space RequirementsTivoli 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 generateapproximately 500 KBytes of history data per day. An enterprise installation of Tivoli Storage Manageron a server with multiple storage agents, clients, automated libraries, and manual drives willgenerate more history data (as per other KMs used by the PATROL Agent). These history data filesare 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_TEMPand KM_DEBUG paths. By default they are all under PATROL_HOME/lib/TSM, wherePATROL_HOME path is normally /opt/bmc/Patrol3/ (on Unix) or C:\Program Files (x86)\BMC Software\Patrol3\ (on Microsoft Windows).

If the location of the KM_TEMP or KM_DEBUG is not suitable, it can be changed using the

21Requirements

Version 2.7.00


Configuration > Paths menu from the main instance. These folder should have read, write andexecute permissions for both the PATROL Agent user and the KM login user.

Getting the BMC SoftwareInstallation UtilityIn order to install Tivoli Storage Manager KM for PATROL, you need the latest version of the BMCSoftware Installation Utility. You can download the latest Installation Utility from the BMC SoftwareEPD (electronic product download) from: http://webapps.bmc.com/signon/content/logon.jsp on theBMC Software Website, or from the Tivoli Storage Manager KM for PATROL page on the SentrySoftware Website

Choose the appropriate package depending on the platform you plan to install Tivoli Storage ManagerKM for PATROL on:

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

http://webapps.bmc.com/signon/content/logon.jsp

http://www.sentrysoftware.net/Products/TivoliStorageManagerKM_Downloads.asp

22Getting the BMC Software Installation Utility

Version 2.7.00


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

Downloading from Sentry Software Web site

For Windows systems: tsm_WINDOWS_2600.exe

For UNIX and Linux systems: tsm_UNIX_2600.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 availableversion of the BMC Software Installation Utility. Please see instructions.

Extracting the Setup FilesLike most Knowledge Modules for PATROL, you need to install Tivoli Storage Manager KM for PATROLon 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-relatedinformation and alerts

The Console Server

PATROL Central – Web Edition

http://www.sentrysoftware.com

Installing the KM

24

Version 2.7.00


Introduction

This section describes the installation procedure for Tivoli Storage Manager KM for PATROL on anyPATROL component (Agents, Consoles, Console Server, etc.). As the setup is based on the BMCSoftware Installation Utility, this procedure applies to all operating systems supported by TivoliStorage Manager KM for PATROL.

Installing Tivoli StorageManager KM for PATROLInstalling Tivoli Storage Manager KM for PATROL is an automated process managed by a wizard. Thewizard goes through the necessary steps to install Tivoli Storage Manager KM for PATROL and all filesassociated 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 ManagerKM for PATROL and the Common Installer).

25Installing Tivoli Storage Manager KM forPATROL

Version 2.7.00


On Windows: Launch the setup.exe program

On UNIX: Launch the setup.sh script

To install Tivoli Storage Manager KM for PATROL1. Allow the perl.exe program to listen on this port: Click Allow access.

Installation W izard - Step 1: W indow s Security Alert


Version 2.7.00


2. The welcome screen of the installer appears. Click Next to continue.

Installation W izard - Step 2: W elcome


Version 2.7.00


3. Read the license agreement, click the Accept option and then click Next to continue.

Installation W izard - Step 3: Review ing License Agreement


Version 2.7.00


4. Select Install products on this computer now and click Next to continue.

Installation W izard - Step 4: Selecting Installation Options


Version 2.7.00


5. Specify the BMC Software products folder. See the BMC Software documentation for moreinformation about the BMC Software products folder. Click Next to continue.

Installation W izard - Step 5: Selecting the Installation Directory


Version 2.7.00


6. Select Default. Installing Tivoli Storage Manager KM for PATROL does not require anycustomization. Click Next to continue.

Installation W izard - Step 6: Selecting an Installation Type

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

Common services to install Tivoli Storage Manager KM for PATROL on the Console Server oron PATROL Central – Web Edition.

Click Next to continue.


Version 2.7.00


Installation W izard - Step 7: Selecting Roles

Select as many options as required.


Version 2.7.00


8. Check the Tivoli Storage Manager KM for PATROL box to install the KM (it should beselected by default). Click Next to continue.

Installation W izard - Step 8: Selecting Products and Components


Version 2.7.00


9. Review the installation parameters and click Start Install to launch the installation procedure.

Installation W izard - Step 9: Review ing Installation Options


Version 2.7.00


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 W izard - Step 10: Installation Status


Version 2.7.00


11. The wizard displays the installation results.Click View Log to display a detailed log of the installation procedure. Click Next and thenFinish to exit the setup program.

Installation W izard - Step 11: Installation Results

12. Click the Finish button to complete and close the installation wizard.


Version 2.7.00


Installation W izard - Step 12: Completing and closing the Installation W izard

A Help button is available at each step of the procedure. Click to display the installation online help. The Exit buttonallows you to stop the installation procedure.


Version 2.7.00


Uninstalling Tivoli StorageManager KM for PATROLUninstalling 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 andall 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 PATROL1. 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 W izard — W elcome Step

38Uninstalling Tivoli Storage Manager KM forPATROL

Version 2.7.00


2. Specify the BMC Software products folder. See the BMC Software documentation for moreinformation about the BMC Software products folder.

Un-install W izard — Specifying folder


Version 2.7.00


3. To uninstall the KM, select Tivoli Storage Manager KM for PATROL.

Un-install W izard — Selecting Products and Components Directory


Version 2.7.00


4. Click Start Uninstall to run the program.

Un-install W izard — Review ing Selected Products & components and start uninstalling


Version 2.7.00


5. A page displays the list of products/components processed and the percentage of completion.Click Next to continue.

Un-install W izard — Status


Version 2.7.00


6. A page displaying SUCCESS indicates that Tivoli Storage Manager KM for PATROL is nowuninstalled.

Un-install W izard — Uninstall Results

Upgrading the PlatformIf you upgrade (or downgrade) your operating system or Tivoli Storage Manager, the commands forthe TSM KM need to be reloaded. Use the menu Reload Commands from the main TSM KMcontainer instance (labeled Tivoli Storage Manager).

43Performing Post-Installation Operations

Version 2.7.00


PerformingPost-InstallationOperationsIt is recommended to perform post installation checks once the KM is installed on the PATROLConsole 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

the instance limits

the initial setup

Restarting the PATROL Agent and PATROL Console.

Loading and Unloading the KMOnce 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 theTSM KM is installed.

3. Check the value of the PATROL Agent tuning variable, /AgentSetup/AgentTuning/pslInstructionMax, and if necessary, increase it.


Version 2.7.00


Loading the KM on PATROL Console

To load the KM on a PATROL Console:

1. From the PATROL Console menu bar, choose File>Load KM...

2. Select the TSM_LOAD.kml file, and click Open or OK.

The TSM KM will be loaded to the PATROL Console, and all connected PATROL Agents will startdiscovering 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.

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... TheLoad 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 wizardwill 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 beeninstalled on that system.

The TSM KM will be loaded to the PATROL Central Console Server, and all connected selectedmanaged 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 tobe loaded.

6. Configure the KMs.

Configuring PATROL Agent to Preload the KM

To configure PATROL Agent to preload the KM:

1. In order to enable Tivoli Storage Manager KM for PATROL to operate all the time, without aPATROL Console connection, the KM should be added to the PATROL Agent configurationvariable /AgentSetup/preloadedKMs. This can be achieved on the Tivoli Storage Managerinstance by using the menu Configuration>Preloading. The KM Preloading dialog will bedisplayed

2. Select Add to add the KM files to the list of preloaded KMs. If the TSM KM is successfully addedto the list, an acknowledgement will be displayed.

The same menu is used to remove the TSM KM files from the preloaded KMs list.


Version 2.7.00


Unloading the KMThis section describes the procedures for unloading (not uninstalling) the TSM KM from the PATROLAgent, PATROL Console or PATROL Central Console. The intention is that this section is only used ifyou no longer want to use some parts of the KM, though there may be circumstances where you maywish 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:

from a PATROL Agent: PATROL stops monitoring the Tivoli Storage Manager application onthat 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 StorageManager 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, usingthe utility wpconfig (on Microsoft Windows) or xpconfig (on Unix), remove TSM_LOAD.kmlfrom 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 beunloaded.

The TSM KM cannot be partially unloaded from the PATROL Agent using the above steps. If you need to unload someparts 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 itto 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, asrequired. All TSM KM application classes start with TSM_.

With the PATROL Console for Unix:

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


Version 2.7.00


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 thePATROL Console user preference.

3. Repeat these steps on every PATROL Console system where the TSM KM is to be unloaded.

Unloading the KM from the PATROL Central Console

A KM can be unloaded from particular managed systems or for all systems across the monitoredenvironment. 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 orall 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...

2. 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 appropriatemanaged systems, click Next> and Finish.

4. Repeat the above steps for each PATROL Central Management Profile where the TSM KM is to beunloaded.

Configuring the KM User AccountA user account with administrative privileges must be configured in BMC PATROL to read and executeTivoli Storage Manager application programs and file systems. Depending on the operating systemsused, several options will be available.

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

a root user

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

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

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


Version 2.7.00


an administrator user

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

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:

Login Configuration dialog

2. To use:

the default PATROL Agent Account, check the Use Agent Default Account box. The logindetails 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.

The password is stored in the PATROL Agent in a DES encrypted format. The encrypted password can beviewed by any user who has access to the PATROL Agent configuration variables (pconfig). This usercould then execute PSL statements using the encrypted password through the PATROL Console. This canbe prevented by setting up an appropriate Access Control List (ACL) for users. Please refer to thePATROL Agent Reference Manual for details on how to set up an ACL.


Version 2.7.00


Step 2: Configure the Admin Interface Login

1. In the Console, right-click the Tivoli Storage Manager instance > Configuration > AdminInterface Login. The Admin Interface Login Configuration dialog is displayed:

Admin Interface Login Configuration dialog

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

Verifying Application DiscoveryTo verify the application discovery:

1. Check that the TSM_SETUP instance is actually named Tivoli Storage Manager. If not, forcea full discovery by right-clicking the TSM_SETUP instance > KM Commands > ForceDiscovery

2. Check that the application class instances are actually instantiated. The initial data collectionmay take some time depending on the complexity of your environment (up to one hour). Ifneeded, force a data collection by right-clicking the Tivoli Storage Instance instance > KMCommands > Refresh Parameters.

If the Tivoli Storage Manager server is configured in a clustered environment, you'll have to enable


Version 2.7.00


and enable Multi-node Mode monitoring.

Checking the Instance LimitsTivoli Storage Manager KM for PATROL automatically sets the number of instances that will bedisplayed in the Console for each monitored elements. This configuration, set to offer maximumperformance, can however be modified to better suit your environment.

Because increasing the number of instances may impact the performance of the KM, it is recommendedto only monitor critical elements in large environments.

To modify the default configuration1. 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.

Checking the Initial Setup of the KMTo 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 > NodeType from the Tivoli Storage Manager instance.

3. Check the InfoBoxes and Parameters of all the TSM KM instances and verify that they are setcorrectly.

4. Under each container instance, open all detail parameters (text parameters with names in theformat TSM<Object>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 Statusfrom the Tivoli Storage Manager instance. A report is displayed, detailing information on themanaged 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 oralarms in the KM Status report), determine the cause(s) and take steps to resolve these errors. You may need to referto 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 asa text file.


Version 2.7.00


Restarting PATROL Agent andPATROL ConsoleIt should not be necessary to re-start the PATROL Agent and/or PATROL Console. However, it is agood practice to confirm that Tivoli Storage Manager KM for PATROL operates correctly after arestart of PATROL Agent and/or PATROL Console. In addition, the PATROL Agent restart will force allKM discoveries and data collections to start immediately.

Integrating the KM

52

Version 2.7.00


Introduction

This section provides detailed information about the integration of Tivoli Storage Manager KM forPATROL with BMC ProactiveNet Performance Management.

Integrating with BMCPortal1. Log on to BMC Portal with appropriate credentials to add infrastructure elements.

2. Click on Configure tab.

3. Under Tasks, select Elements to open the Elements page.

4. Click Add.

5. Select Infrastructure Element, and click Next.

6. Select appropriate RSM, and click Next.

7. Enter the label for the element, select PATROL Integration, and click Next.

8. Select/create a group name, and click Next.

9. Select appropriate method to discover the PATROL Agent hosts, and click Next.

10. Fill the required details for discovering the PATROL Agents, and click Commit.

Integrating with BMCProactiveNet PerformanceManagement 8.5.x and8.6.xOverviewTo integrate a BMC PATROL KM into BMC ProactiveNet 8.5.x or 8.6.x, you need to create a specificadapter. An adapter for BMC PATROL facilitates pulling of performance data from existing BMCPATROL solutions into BMC ProactiveNet. Using an Adapter, you can import BMC PATROL applicationclasses (provided in a Knowledge Module–KM) into BMC ProactiveNet. The Adapter periodicallysynchronizes the performance data collected by these application classes into BMC ProactiveNet.

53Integrating with BMC ProactiveNetPerformance Management 8.5.x and 8.6.x

Version 2.7.00


Creating and Importing an Adapter fora BMC PATROL KMCreating an Adapter for a BMC PATROL KM1. 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 > BMCPATROL.

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 performthe 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 3182.

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

Unselecting will delete the application classes that have already been imported during a previousoperation. Application classes ready to be deleted are marked with a red x.

7. Click Next to start the import process. The system displays a summary of the application classimport, 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 BMCProactiveNet to enable the update of a single KM independently.


Version 2.7.00


Updating an Adapter for a BMCPATROL KMUpdating an Adapter1. Delete the Adapter instance

2. Go through the Add an Adapter wizard to actually delete the monitor types that had beencreated 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 documentationavailable from BMC Web site.

Importing and CustomizingThresholds1. 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

The command has produced a text file with all the parameter threshold settings.

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 properlyconverted 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 -v enables the Verbose mode


Version 2.7.00


Class-level thresholds can be displayed using the Absolute Global Thresholds panel in the BMCProactiveNet Operator Console, while instance-level thresholds are displayed in the AbsoluteInstance Thresholds panel.

Managing Baselines and KeyPerformance IndicatorsIn order to facilitate the detection of abnormalities on your monitored environment, BMCProactiveNet calculates baselines per parameter (metrics or attributes) based on values collectedover a specified period of time to determine a normal operating range. When the collected values forthese parameters are out of range, an alert is triggered.

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

Managing baselines

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

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

Requirements for baseline generation

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

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 BMCProactiveNet Administration Console. In this KM, some parameters or attributes have beendesignated as important indicators of performance (KPIs). We do not recommend that these defaultsettings are modified.

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


Version 2.7.00


Console.

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

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

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

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

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

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

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

Parameters for which the system by default calculates baselines as well as parameters considered asKPIs are respectively identified by the following icons:

Baselining

KPI

Monitoring your Environment

58

Version 2.7.00


Tivoli Storage Manager KM for PATROL helps ensure the availability, maximum performance, andintegrity of your backup servers, thereby protecting associated data sets.

Administering TivoliStorage ManagerTivoli Storage Manager KM for PATROL provides secure server administration menus, which can beexecuted 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 ServerIn 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 AgentIn the Console, right-click the Tivoli Storage Managed instance > KM Commands and select:

Administration > Start Storage Agent

Administration > Stop Storage Agent

whether you want to start or stop the storage agent.

Administering Mount RequestsEach 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 therequested action was actually performed. To send the notification, right-click the relevant mountrequest instance > Administration > Reply

To cancel:

59Administering Tivoli Storage Manager

Version 2.7.00


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 containerinstance (labeled: Mount Requests) using the menu Administration > Cancel All.

Administering DrivesTo administer manual or automatic library drives, right-click the relevant drive instance and selectone of the following options:

Administration > Clean Drive

Administration > Online Drive

Administration > Offline Drive

Cancelling ProcessesTo administer processes, right-click the relevant process instance and select Administration >Cancel Process.

Configuring the KMTivoli Storage Manager KM for PATROL can be customized and optimized to suit your Tivoli StorageManager application environment. This section describes all menus available for customizing the TSMKM. These customization menus are accessed from the knowledge module command sub-menu Configuration> from each application instance. Most of these customization menus can beaccessed either from the parent container level or from the child instance level.

If a customization menu is accessed from the container instance and you make a change, you thenhave the option to apply this change to all child instances which appear under the selected containerin PATROL Console instance topology. If a customization menu is accessed from the child instance, itwill 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 itstopological parent path. If no customized configurations found, the KM will use the default configuration.

If a menu command is named Configuration > Client(s), it means that the menu command is available asConfiguration > Client from the parent container instance (client container instance) and Configuration > Clientsfrom the child instance (individual client instance).

60Configuring the KM

Version 2.7.00


Configuring PathsThe solution automatically discovers the installation, binary, and library paths. This information canhowever 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_LOGDirectory 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.

Specifying the Node TypeYou 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.


Version 2.7.00


Configuring the Multi-NodeMonitoring ModeIf the Tivoli Storage Manager environment is installed in a cluster using Veritas Cluster Server, VeritasCluster File System, Oracle Solaris Cluster or Microsoft Cluster, the TSM KM must be installed on allthe cluster nodes to enable continuous monitoring and avoid single point of failure. To avoidduplicate 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

Configuring the Multi-Node 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 VeritasCluster File System. The TSM KM will then monitor the entire cluster from the active mastersystem, which is identified by the vxdctl -c mode command. This method requires vxconfigd inenable mode with its clustered state active.

5. Enable Remote PATROL Agent Checking to check the monitoring status of the other nodesand click OK. You'll then have to indicate all the information required to communicate with theremote 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. Theother nodes, which are standing by for a failover, will be in passive multi-node mode and only thelocal Tivoli Storage Manager components will be monitored.


Version 2.7.00


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

Filtering Elements to MonitorBy default, the solution monitors all the elements discovered, which may represent an importantworkload to the agents and servers. Because the monitoring of some elements may be irrelevant forvarious 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 drivesdiscovered will be monitored

To filter the elements to be monitored:


Version 2.7.00


1. In the Console, right-click the instance for which you want to filter the elements to be monitoredand select KM Commands > Configuration> The Elements to be filtered

Client Configuration dialog

The [ALL] entry ensures that all the elements found during PATROL discovery are instantiated andmonitored.

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.


Version 2.7.00


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

Configuring Monitoring PeriodsBy default, Tivoli Storage Manager KM for PATROL monitors all mount requests for 1 day, allscheduled jobs that completed successfully for 1 day and any other scheduled job for 3 days, and allexecuted TSM internal server processes for 3 days. You can however modify these settings to bettersuit your requirements:

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


Version 2.7.00


Configuring the Jobs Monitoring Period1. In the Console, right-click the Jobs instance > KM Commands > Configuration > Jobs

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 areinstantiated. To force data collection, right-click the Jobs instance > KM Commands >Force Full Collection


Version 2.7.00


3. Uncheck Keep Monitoring Active Jobs Indefinitely if you prefer not to monitor active jobsendlessly 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 Period1. In the Console, right-click the Mount Requests instance > KM Commands > Configuration

> Mount Requests

Mount Request Filter Configuration Dialog


Version 2.7.00


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 Period1. In the Console, right-click the Processes instance > KM Commands > Configuration >

Processes

Process Filter Configuration Dialog

2. Indicate how long the processes will be monitored. If you:

decrease the monitoring period, older processes will be destroyed on the next data collectioncycle

increase the monitoring period, you'll have to force a full data collection to ensure all processesare instantiated. To force data collection, right-click the Processes instance > KMCommands > Force Full Collection

3. Click OK.


Version 2.7.00


Configuring the Elements StatusThe status of an element is determined by the State parameter and by the status mapping rule. Thismapping rule indicates which states will trigger a warning or an alarm on the Status parameter. Itcan be configured as follows:

1. In the Console, right-click the parent or child instance for which you want to configure status andselect > KM commands > Configuration > Instance Status

Client Status Configuration dialog


Version 2.7.00


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 awarning 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 30

4. 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 alarmwhen 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 60

6. 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 allcomponents available under that parent instance. To modify the mapping rule for a selectedcomponent, access the menu at the child component instance level.

Configuring the Log FilterA log error filter can be configured to specify the regular expressions that will generate a warning oran alarm. Each time the KM will find these expressions in a log file or in TSMLogText, the errormessage 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 enabledadditional log files for monitoring, you will have to customize the log filter by adding appropriateexpressions for those log files.

For an explanation of the possible error messages in the log files, refer to the Tivoli Storage Manager SystemAdministrator’s Guide and the Tivoli Storage Manager Troubleshooting Guide.

To configure the log error filter:


Version 2.7.00


1. In the Console, right-click the Logs instance > KM Commands > Configuration > LogsFilter

Log Filer Configuration dialog

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). Youcan also limit the exclusion to a particular expression already listed by using standard wildcardsyntax, such as “ANR2121W” or “ANR21[0-9].W”.”.

Select Exclude


Version 2.7.00


6. Click Update.

To revert to the default settings for either filter, type [default] as a new error expression for that filter, and clickUpdate. If you revert to the default settings when accessed from the log instance level, the settings will revert to theparent or container instance level. To revert to the shipped default settings (as shown above), access this dialog fromthe log container instance. From this level you will also have the option to reset the configuration of any modified childinstances.

Configuring the Log Scan LimitThe TSM KM scans log files by reading the new log entries since the last data collection cycle. Bydefault, only 500 Kbytes of data is scanned for each log file during each data collection cycle. This logscan limit can however be modified to better suit your requirements.

Increasing the Log Scan Limit may impact the performance of the data collector (TSMLogCollector), theKM, and the PATROL Agent.

To customize the log scan limit:

1. In the Console, right-click the Log(s) instance > KM Commands > Configuration Log(s)Scan Limit

Indicate the amount of data that will be read by the KM during each data collection cycle

2. Click OK.

Configuring Domain BackupRestrictionTSM KM can be configured to trigger a warning when a backup is started during a specific period oftime:

1. In the Console, right-click:

the Domains instance > KM Commands > Configuration> Domains BackupRestriction to apply this customization to all policies

a Domain instance > KM Commands > Configuration> Domain Backup Restriction toapply this customization to a specific policy


Version 2.7.00


Domain Backup Restriction W indow dialog

2. Select Enabled

3. Indicate the Restriction Start and End Time. The restriction window must at least last 5minutes.

4. Click OK.

Configuring Alert AcknowledgementBy default, alerts will automatically be acknowledged unless you modified the following settings toallow manual acknowledgement.

Manual acknowledgement may impact the performance of the application and of the PATROL Agent ifthe number of alerts waiting to be acknowledged constantly increases.

Configuring Logs Alert Acknowledgement

By default, log alerts are automatically acknowledged when new ones are detected. To change thedefault behavior:


Version 2.7.00


1. In the Console, right-click the Logs instance > KM Commands > Configuration> Log AlertAcknowledgement

Configuring Log Alert Acknow ledgement

2. Indicate whether the warning and alarm messages will be manually or automaticallyacknowledged

3. Click Ok.

Configuring Jobs Alert Acknowledgement

By default, the alerts triggered on the TSMJobStatus parameter for the completed jobs are notacknowledged. If you want these alerts to be automatically acknowledged, you'll have to configurethe job alert acknowledgement as follows:


Version 2.7.00


1. In the Console, right-click the Jobs instance > KM Commands > Configuration > Job AlertAcknowledgement

Configuring Job Alert Acknow ledgement


3. Click Ok.

Configuring Process Alert AcknowledgementIf you want alerts to be automatically acknowledged, you'll have to configure the process alertacknowledgement as follows:


Version 2.7.00


1. In the Console, right-click the Processes instance > KM Commands > Configuration >Process Alert Acknowledgement

Configuring Process Alert Acknow ledgement


5. Click Ok.

Refreshing ParametersThis section describes how to manually refresh parameters without waiting for an automatic pollingcycle.

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 KMapplications classes.

Forcing All Data Collectors

To force all data collectors, right-click the Tivoli Storage Manager instance and select:


Version 2.7.00


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 loadedon 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 refreshthe 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

Right-click the main Tivoli Storage Manager container instance and choose Parameterswithout Icons...

Select the required data collector.

Click Update.

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 nextcollection cycle.

To force full data collection for jobs, right-click the Jobs instance and select Force Full Collection.

If the Jobs container instance is not instantiated, this menu command cannot be accessed. The PATROL Agent needs tobe restarted to force a full data collection for jobs.


Version 2.7.00


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

Enabling the Debug Mode1. 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


Version 2.7.00


2. Select On for the debug switch(es) you want to enable. Refer to the table below to know theapplication classes and collector parameters included in the debug switch:

Object Debug Switch

Application Classes Collector Parameters

Server TSM_SERVER TSMCreateDistributionTSMUpdateAgent

Database TSM_DATABASE_CONTAINERTSM_DATABASE

TSMDatabaseCollector

Log TSM_LOG_CONTAINERTSM_LOG

TSMLogCollector

Client TSM_CLIENT_CONTAINERTSM_CLIENT

TSMClientCollector

Device(Automated Library / Drive)

TSM_LIBRARY_CONTAINERTSM_LIBRARYTSM_LDEVICETSM_DEVICE_CONTAINERTSM_DEVICE

TSMLibraryCollectorTSMDriveCollector

Daemon TSM_DAEMON_CONTAINERTSM_DAEMON

TSMDaemonCollector

Pool TSM_POOL_CONTAINERTSM_POO

TSMPoolCollector

Backup (Domain / Job / Mount Request)

TSM_POLICY_CONTAINERTSM_POLICYTSM_PCLIENTTSM_JOB_CONTAINERTSM_JOBTSM_MOUNT_CONTAINERTSM_MOUNT

TSMDomainCollectorTSMJobCollectorTSMRequestCollector

Process TSM_PROCESS_CONTAINERTSM_PROCESS

TSMProcessCollector

3. Set the Debug Options:

In the Debug End Time field, indicate the date and time after which debug information willno 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 onMicrosoft Windows systems). The debug folder must have at least 10MB of available disk spaceand read, write and execute permissions for both PATROL Agent user and the TSM KM loginuser

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 DebugOutput window. Before selecting this option, make sure the PATROL Console is connected tothe PATROL Agent.

Select Both (Recommended) to send the debug messages both to a file and task window.


Version 2.7.00


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/zipfile is then automatically created under <PATROL_HOME>/lib/TSM/ and can be sent to the BMCSupport 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.

If you chose to send debug information to file(s), you will be asked to prepare the debug files forsending to Sentry Software:

Click Yes to compress the files into a:

tsm_km_debug_<date>_<time>.tar.Z file (Unix systems). This file could later be foundin $PATROL_HOME/lib/TSM/

tsm_km_debug_<date>_<time>.zip file (Windows systems). This file could later befound 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 ordelete them.

If the compressed file is not created successfully, you can create it manually by including all files and sub-directoriesunder $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:

1. Disable the debug mode

2. Click No when asked to prepare the files for sending

3. Choose to Retain the debug files.

4. Start the next debug session.

5. Choose to append the output data to existing files.


Version 2.7.00


Reloading CommandsAll new commands are reloaded automatically but some situations, such as the operating systemupgrade or downgrade, may require a manual commands reload. To do so, in the Console, right-clickthe Tivoli Storage Manager instance > KM Commands > Reload Commands.

Acknowledging AlertsBy default, alerts are acknowledged automatically. They can however be acknowledged manually ifyou do not want to wait for the automatic cycle. Manual acknowledgement will also be required if youmodified 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 orTSMLogWarningText and will respectively trigger an Alarm or a Warning on TSMLogAlarmCountor TSMLogWarningCount.

To acknowledge log alerts:

1. In the Console, right-click the Log instance > KM Commands > Acknowledgement

2. Select:

Warning to view, select, and individually acknowledge errors in the TSMLogWarningTextparameter

Alarms to view, select, and individually acknowledge errors in the TSMLogAlarmTextparameter

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 willbe set to alert with a status of Warning or Alarm respectively. These alerts can be acknowledgedusing the menu Acknowledgement > Alert from the relevant job instance.

To acknowledge job alerts:

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

Acknowledgement > Alarms to view and acknowledge alerts for all jobs with a status ofAlarm.

Acknowledgement > All to view and acknowledge all job alerts (Warnings and Alarms) atonce

81Acknowledging Alerts

Version 2.7.00


Acknowledging Process Alerts

For a particular process instance, if the TSMProcessStatus has a value of 1=Suspicious or2=Failure, it will be set to alert with a status of Warning or Alarm respectively. These alerts can beacknowledged 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 astatus of Warning.

Acknowledgement > Alarms to view and acknowledge alerts for all processes with a statusof Alarm.

Acknowledgement > All to view and acknowledge all process alerts (Warnings and Alarms)at once.

Generating ReportsThe following reports are available in Tivoli Storage Manager KM for PATROL:

<Automated Library instance> > Reports > Automated Library Contents - reports thelibrary 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 databasebackup volume history for the last 7 days.

<Database instance> > Reports > Database Volumes - reports information about serverdatabase volumes and volume copies.

<Domain instance> > Reports > Domain Schedule - displays the schedule for the selecteddomain instance for the next 24 hours

Logs > Reports > Activity Log Messages - reports all messages logged today (sincemidnight)

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 themanaged node

<Storage Pool instance> > Reports > Volumes List - reports all volumes in the selectedstorage 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

Reference Guide

83

Version 2.7.00


Introduction

This chapter provides statistical information about resources, operating status, and performancesmanaged by Tivoli Storage Manager KM for PATROL. It contains tables describing the parametersused in the KM, grouped by Application Classes, and provides a brief description of each parameterand its default settings.

Classes and ParametersThis section lists the application classes of TSM KM. It gives you details on the icons that representthe class, Infobox, parameters and the menu commands available for each application class. Thereare 14 main application classes and 11 “container” classes.

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 thereforeautomatically included in the base lining calculation. To learn more about auto baselining and KPIs,please refer to the Managing Baselines and Key Performance Indicators chapter.

84Classes and Parameters

Version 2.7.00


In this guide, parameters flagged as KPIs and included by default in the baseline calculation processare respectively identified by the following icons:

Baselining

KPI

TSM_SERVERIcon

Parameters

Name Description Units DefaultAlertConditions

BPPM Type

ExtraFilesList Is used for pushing TSM KM library filesto the PATROL Agent during the"Commit" operation.

n/a n/a n/a

TSMClientCollector Collects Tivoli Storage Manager clientrelated information. It sets all consumerparameters in TSM_CLIENT_CONTAINER andTSM_CLIENT application classes. Bydefault, this collector is executed onlyon the server.

Polling Interval: 600 seconds

n/a n/a n/a

TSMCreateDistribution Is automatically activated at the end ofTSM KM debugging if the customerchooses to "prepare debug files forsending to Sentry Software". It isdeactivated on completion.


n/a n/a n/a

TSMDaemonCollector Collects Tivoli Storage Manager daemonrelated information. It sets all consumerparameters in TSM_DAEMON_CONTAINER andTSM_DAEMON application classes.


n/a n/a n/a

TSMDatabaseCollector Collects Tivoli Storage Manager serverdatabase related information. It sets allconsumer parameters in TSM_DATABASE_CONTAINER andTSM_DATABASE application classes.By default, this collector is executedonly on the server.

n/a n/a n/a


Version 2.7.00



TSMDomainCollector Collects Tivoli Storage Manager domainand client node related information. Itsets all consumer parameters in TSM_POLICY_CONTAINER,TSM_POLICY, and TSM_PCLIENTapplication classes.By default, this collector is executedonly on the server.


n/a n/a n/a

TSMDriveCollector Collects Tivoli Storage Manager manualdrive related information. It sets allconsumer parameters in TSM_DEVICE_CONTAINER andTSM_DEVICE application classes.


n/a n/a n/a

TSMJobCollector Collects Tivoli Storage Manager backup/restore event related information. Itsets all consumer parameters in TSM_JOB_CONTAINER andTSM_JOB application classes.By default, this collector is executedonly on the server.


n/a n/a n/a

TSMLibraryCollector Collects Tivoli Storage Managerautomated library and automated librarydrive related information. It sets allconsumer parameters in TSM_LIBRARY_CONTAINER,TSM_LIBRARY, and TSM_LDEVICEapplication classes.


n/a n/a n/a

TSMLogCollector Collects Tivoli Storage Manager log filerelated information. It sets all consumerparameters in TSM_LOG_CONTAINERand TSM_LOG application classes.


n/a n/a n/a

TSMLoginStatus* Monitors the status of the TSM KM logindetails (username/password) for theoperating system and DSMADMC. It isset by TSM_SERVER application classdiscovery.If no valid username/password isdetected for the operating system orDSMADMC, this parameter will be set toFailure state. If there are any suspiciouscommand exits, this parameter will beset to Suspicious state.If this status parameter changes towarning or alarm state, the recoveryaction will trigger an event andannotate the last data point.

0 = Ok1 =Suspicious 2 = Failure

Warning = 1Alarm = 2

Collection Status


Version 2.7.00


TSMMonitoringMode* Monitors failover mode of the TSM KM.It is set by TSM_SERVER applicationclass discovery.By default TSM KM runs in PermanentSingle-node Mode. Multi-nodemonitoring can be configured using theKM command Configuration >Monitoring Mode from the TivoliStorage Manager icon.

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

n/a Collection Status

TSMNodeStatus* Monitors error messages for the TivoliStorage Manager application on thismanaged system. It is set byTSM_SERVER application classdiscovery.

The value of this parameter isdetermined by the node status mappingrule defined in the KM command Configuration > Node Status fromthe Tivoli Storage Manager icon.

If this status parameter changes towarning or alarm state, the recoveryaction will trigger an event andannotate the last data point.

0 = Ok1 =Suspicious2 = Failure


Availability

TSMPoolCollector Collects Tivoli Storage Manager storagepool related information. It sets allconsumer parameters inTSM_POOL_CONTAINER andTSM_POOL application classes.

By default, this collector is executedonly on the server.


n/a n/a n/a

TSMProcessCollector Collects Tivoli Storage Manager serverprocess related information. It sets allconsumer parameters inTSM_PROCESS_CONTAINER andTSM_PROCESS application classes.By default, this collector is executedonly on the server.


n/a n/a n/a

TSMRequestCollector Collects Tivoli Storage Manager mountrequest related information. It sets allconsumer parameters inTSM_MOUNT_CONTAINER andTSM_MOUNT application classes.By default, this collector is executedonly on the server. Polling Interval: 300 seconds

n/a n/a n/a


Version 2.7.00


TSMUpdateAgent Used by the TSM KM to set the PATROLAgent KM variables when the PATROLConsole user is not authorized to update(ACL) any PATROL Agent variables. It isactivated automatically when the KMfails to update the PATROL Agent.Polling Interval: 300 seconds

n/a n/a n/a

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.

PATROL Agent Version 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 www.bmc.com

Support [email protected]


Version 2.7.00


Menu Commands

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

Starts server daemons.

Administration > StopServer

Stops server daemons.

Administration > StopStorage Agent

Stops storage agent daemons.

Administration >StartStorage Agent

Starts storage agent daemons.

Configuration> Login Accesses the Login Configuration dialog for viewing and entering TSM KM login details for theoperating system.This user account should have privileges to execute Tivoli Storage manager administrationcommands 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 usedby any KM commands.The password is encrypted and stored on the PATROL Agent using the BMC PATROLencryption function.

Configuration> AdminInterface Login

Accesses the Admin Interface Login Configuration dialog for entering and viewing DSMADMClogin account details.This admin account (suggested name patrol) is used by the TSM KM to query Tivoli StorageManager.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 KMcommands.The password is encrypted and stored on the PATROL Agent using BMC PATROL encryptionfunction.

Configuration> Preloading Accesses Preloading Configuration dialog, which adds or removes the KM from PATROL Agentvariable "/AgentSetup/preloadedKMs".By preloading the NSR KM, the PATROL Agent will monitor the Tivoli Storage Managerapplication without any PATROL Console connection.

Configuration> MonitoringMode

Accesses the Monitoring Mode Configuration dialog, which is used for enabling or disablingTSM 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 TSMKM.Paths are automatically discovered by the TSM KM server discovery. They are used asenvironment variables for executing various Tivoli Storage Manager application commands.Altering these paths may impact the operation of the KM.

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.


Version 2.7.00


Installation Path is the application installation path discovered by the KM. Thisinformation can be overridden through the KM command

Binary Paths are the Application and operating system binary path, which is used forsetting PATH environment variable. The KM discovers and set this automatically. This menucan be used, if the discovered paths are incorrect.

Library Paths are the Application and operating system library path, which is used forsetting 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 pathsare 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.

Configuration> Node Type Accesses the Node Type Configuration dialog, which displays and sets the type of the TivoliStorage Manager application node.The TSM KM server discovery detects the type of the node automatically; the type can eitherbe Server or Storage Agent. The operation of the KM depends on this node type.

Configuration> NodeStatus

Accesses the Node Status Configuration dialog for viewing and modifying the error expressionfilters, which determine the status of the node (parameter TSMNodeStatus).By default, the following "Included" expressions are checked. If detected, they set theparameter TSMNodeStatus to alert, unless the message also contains an "Excluded"expression. Error Expression TSMNodeStatus ANS1017E Failure ANS1473E Failure ANS8023E Failure Availability: Disabled Failure Central Scheduler: Inactive Suspicious Server License Compliance: FAILED SuspiciousType "[default]" to reset to the default configuration.

Configuration> InstanceLimits

Accesses the Instance Limits Configuration dialog to view and modify the maximum numberof 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.


Version 2.7.00


TSM_CLIENT_CONTAINERIcon

Parameters


BPPM Type

TSMClientDetails Set by TSMClientCollector. Displays alldata returned to the standard out fromcommands executed by the datacollector.

n/a n/a n/a

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

Menu Commands


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

Accesses the global configuration for determining the client status for monitored clientinstances.By default, following TSMClientState to TSMClientStatus mapping rule is used: TSMClientState TSMClientStatus Never Communicated with Server Failure Unknown Failure Locked Suspicious all other states OkSelect [default] to reset to the default client status mapping rule.


Version 2.7.00


TSM_CLIENTIcon

Parameters


BPPM Type

TSMClientLastAccessElapsed

*

Set by TSMClientCollector. Displaysthe time elapsed since the lastcommunication from the client.The specified alarm ranges can beenabled to allow the output of theparameter to be actively monitored.Then, if this parameter changes towarning or alarm state, the recoveryaction will trigger an event.

hours None Statistics

TSMClientSpaceUsed* Set by TSMClientCollector. Displaysthe amount of space used on the clientnode.

GB None Statistics

TSMClientState Set by TSMClientCollector. Displaysthe state of the client as reported in thecommand executed by the datacollector.

0 = Running1 = Locked2 = NeverCommunicated-1 =Unknown

None Availability

TSMClientStatus Set by TSMClientCollector. Monitorsthe status of the client. This status isdetermined by the client status mappingrule defined in the KM command Configuration > Client(s) Status.

If this status parameter changes towarning or alarm state, the recoveryaction will trigger an event and annotatethe last data point.


Warning = 1Alarm =2

Availability

TSMClientSummary Set by TSMClientCollector.Summarizes the client information asreported in commands executed by thedata collector.

n/a None n/a




Version 2.7.00


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 LastCommunication

Number of days, hours, minutes and seconds since the last connection from the currentnode.

Last Communication Method Method of the last connection from the current node.






Menu Commands


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 theTSM KM

Configuration> Client Status Accesses the individual configuration for determining client status for the selected clientinstance.By default, the global TSMClientState to TSMClientStatus mapping rule is used, asconfigured at the container level. Select [default] to revert to the client status mapping ruleconfigured at the global/container level.


Version 2.7.00


TSM_DAEMON_CONTAINERIcon

Parameters


BPPM Type

TSMDaemonDetails Set by TSMDaemonCollector, displaysall data returned to the standard outfrom commands executed by the datacollector.

n/a None n/a

InfoBox

Name Description






Menu Commands


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.

On Server:Daemon Description Statusdsmserv TSM Server Daemon Enableddsmsta TSM Storage Agent Daemon Disabledall other daemons Disabled On Storage Agent:Daemon Description Statusdsmserv TSM Server Daemon Disableddsmsta TSM Storage Agent Daemon Enabledall other daemons Disabled


Version 2.7.00


Note that this default configuration is for a UNIX platform; the difference for a MicrosoftWindows platform is that the name of the TSM Server Daemon is shown as "dsmserv ordsmsvc" and the TSM Storage Agent Daemon is shown as "dsmsta or dstasvc".Type [default] to reset to the default configuration.

Configuration > DaemonsStatus

Accesses the global configuration for determining the daemon status for monitored daemoninstances.By default, the following TSMDaemonState to TSMDaemonStatus mapping rule is used: TSMDaemonState TSMDaemonStatus Nonexistent/Not Responding Failure Not Running Failure Terminated or Stopped Suspicious Growing or Unknown Suspicious all other states OkSelect [default] to reset to the default mapping rule.

TSM_DAEMONIcon

Parameters


BPPM Type

TSMDaemonCPUDuration Set by TSMDaemonCollector. Displaysthe CPU seconds consumed by thedaemon.

seconds None Statistics

TSMDaemonCPUUtilization*

Set by TSMDaemonCollector. Displaysthe CPU seconds used by the daemon.

% None Statistics

TSMDaemonMemorySize*

Set by TSMDaemonCollector. Displaysthe core image size of the daemon in thevirtual memory.

KB None Statistics

TSMDaemonProcessCount

Set by TSMDaemonCollector. Displaysthe number of daemon processes/threads found.

processes None Statistics


Version 2.7.00


TSMDaemonState Set by TSMDaemonCollector. Displaysthe state of the daemon as reported inthe command executed by the datacollector.

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

None Availability

TSMDaemonStatus Set by TSMDaemonCollector. Monitorsthe status of the daemon. This status isdetermined by the daemon statusmapping rule defined in the KMcommand Configuration > Daemon(s) Status.



None Availability

TSMDaemonSummary Set by TSMDaemonCollector.Summarizes the daemon information asreported by commands executed by thedata collector.

n/a n/a n/a



InfoBox

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.


Version 2.7.00


Collector Name Name of the data collector that sets variables and parameters under this applicationinstance.





Menu Commands


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 bythe TSM KM.

Configuration > DaemonsStatus

Accesses the individual configuration for determining daemon status for the selected thedaemon instance.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_CONTAINERIcon

Parameters


BPPM Type

TSMDatabaseDetails Set by TSMDatabaseCollector.Displays all data returned to the standardout from commands executed by thedata collector.

n/a n/a n/a

InfoBox

Name Description





Version 2.7.00




Menu Commands


Reports > Database BackupVolume 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.

Database Description Statusdb Server Database Enabledlog Server Recovery Log Enabled

Type [default] to reset to the default configuration.

TSM_DATABASEIcon

Parameters


BPPM Type

TSMDatabaseBackupElapse

d*

Set by TSMDatabaseCollector. Displaysthe elapsed time since the last successfuldatabase backup.

The specified alarm ranges can beenabled to allow the output of theparameter to be actively monitored. Then,if this parameter changes to warning oralarm state, the recovery action willtrigger an event.

This parameter is only available forthe server database (db)


TSMDatabaseBufferRequest

Count

Set by TSMDatabaseCollector. Displaysthe cumulative number of requests fordatabase pages since the buffer pool waslast reset (or since the server was laststarted).

count None Statistics


Version 2.7.00



TSMDatabaseCacheHitPerce

nt*

Set by TSMDatabaseCollector. Displays(as a percentage of the total number ofrequests) the number of requests for adatabase pages that are already in thebuffer pool.


% None Statistics

TSMDatabaseCacheWaitPer

cent*

Set by TSMDatabaseCollector. Displays(as a percentage of the total number ofrequests) the number of requests fordatabase buffer pool pages where nopages are available, because all pages arein use.


% None Statistics

TSMDatabaseFSSpaceUsed

Percent*

Set by TSMDatabaseCollector. Monitorsthe percentage of space used by the filesystem where the database resides.If this parameter changes to warning oralarm state, the recovery action willtrigger an event.


% Warning: 95-98 Alarm: over98

Statistics

TSMDatabaseLogConsumed

Size

Set by TSMDatabaseCollector. Displaysthe cumulative consumption of log spaceused by the server since the last reset of

this parameter.


MB None Statistics

TSMDatabaseLogPoolUsedP

ercent*

Set by TSMDatabaseCollector. Displays(as a percentage of all recovery log bufferpool pages) the number of buffer poolpages used to write changes to therecovery log after a transaction iscommitted.


% None Statistics


Version 2.7.00


TSMDatabaseLogPoolWaitP

ercent*

Set by TSMDatabaseCollector. Displays(as a percentage of all recovery log bufferpool requests) the number of requests forbuffer pool pages where no pages are

available because all pages are in use.


% None Statistics

TSMDatabasePoolHitPercent

*

Set by TSMDatabaseCollector. Displays(as a percentage of the total number ofrequests) the number of requests fordatabase pages that are already in thebuffer pool.

This parameter is only available forthe server database (db).

% None

TSMDatabaseReorgElapsed*

Set by TSMDatabaseCollector. Displaysthe elapsed time since the last databasereorganization. The specified alarm rangescan be enabled to allow the output of theparameter to be actively monitored. Then,if this parameter changes to warning oralarm state, the recovery action willtrigger an event.

This parameter is only available forthe server database (db).


TSMDatabaseSpaceAvailable

Set by TSMDatabaseCollector. Monitorsthe amount of assigned space remainingavailable for use by the server database.

If this parameter changes to warning oralarm state, the recovery action willtrigger an event.

The name of this parameter shouldnot be confused with the TSMterminology "Available Space"reported in the InfoBox, which isthe total volume space madeavailable to the server database

MB Warning: 2-5Alarm: lessthan 2

Availability

TSMDatabaseSpaceChange

d

Set by TSMDatabaseCollector. Displaysthe database pages (in megabytes) thathave changed since the last backup.


MB None Statistics

TSMDatabaseSpaceChange

dPercent*

Set by TSMDatabaseCollector. Displaysthe percentage of database pages thathave changed since the last backup.

% None Statistics


Version 2.7.00



TSMDatabaseSpaceGrowthRate

Set by TSMDatabaseCollector. Displaysthe growth rate of the space used by theserver database.

MB/s None Statistics

TSMDatabaseSpaceMaxExte

nsion

Set by TSMDatabaseCollector. Displaysthe maximum amount the database canbe extended by.

MB None Statistics

TSMDatabaseSpaceMaxRed

uction

Set by TSMDatabaseCollector. Displaysthe maximum amount the database canbe reduced by.


Statistics

TSMDatabaseSpaceUsed Set by TSMDatabaseCollector. Displaysthe amount of assigned space used by theserver database.

MB None Statistics

TSMDatabaseSpaceUsedPer

cent*

Set by TSMDatabaseCollector. Monitorsthe percentage of assigned space used bythe server database.If this parameter changes to warning oralarm state, the recovery action willtrigger an event.

The total assigned space is theused space(TSMDatabaseSpaceUsed) plus theavailable space(TSMDatabaseSpaceAvailable).

% None Statistics

TSMDatabaseSummary Set by TSMDatabaseCollector.Summarizes the database information asreported by commands executed by thedata collector.

n/a n/a n/a



InfoBox

Name 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 thedatabase.

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.


Version 2.7.00


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, bya 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 thehighest 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.






Menu Commands


Reports > DatabaseVolumes

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 bythe TSM KM.


Version 2.7.00


TSM_LOG_CONTAINERIcon

Parameters


BPPM Type

TSMLogDetails Set by TSMLogCollector. Displays all datareturned to the standard out fromcommands executed by the data collector.

n/a n/a n/a

InfoBox

Name Description







Version 2.7.00


Menu Commands

Name Description

Reports > Activity LogMessages

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.

On Solaris:Log File Description Statusactlog Server Activity Log Enabled/var/adm/messages System Log Enabledall other log files Disabled

On HP-UX:Log File Description Statusactlog Server Activity Log Enabled/var/adm/syslog/syslog.log System Log Enabledall other log files Disabled

On AIX and Microsoft Windows:Log File Description Statusactlog Server Activity Log Enabledall other log files Disabled


Configuration > Logs Filter Accesses the global configuration of the filter for error expressions in monitored log fileinstances.By default, following error messages are looked for in each log file. If detected, they areadded to appropriate text parameter:Error Expression Set to Parameter StatusAN[A-Z][0-9]...K TSMLogAlarmText IncludedAN[A-Z][0-9]...S TSMLogAlarmText IncludedAN[A-Z][0-9]...W TSMLogWarningText Included


Configuration > Logs ScanLimit

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 fileduring each data collection cycle.

Configuration > Logs AlertAcknowledgement

Accesses the global configuration of the method of acknowledgement for alerts on monitoredlog file instances.By default, the log collector automatically acknowledges previous log alerts (warnings andalarms) when it detects new errors.


Version 2.7.00


TSM_LOGIcon

Parameters


BPPM Type

TSMLogAlarmCount* Set by TSMLogCollector. Monitors thenumber alarm messages set in theparameter TSMLogAlarmText.

If this parameter changes to alarm state,the recovery action will trigger an event.

count Alarm: 1 andover

Statistics

TSMLogAlarmText Set by TSMLogCollector. Displays allalarm messages in the log file whichhave not been acknowledged. The filterused by the data collector to determinealarm messages can be customizedusing the KM command Configuration> Log(s) Filter.

These alarm messages can beacknowledged automatically (default) ormanually, depending on theconfiguration in the KM command Configuration > Log(s) AlertAcknowledgement. Manualacknowledgement is available under theKM sub-menu Acknowledgement.

n/a None n/a

TSMLogFSSpaceUsedPercen

t*

Set by TSMLogCollector. Monitors thepercentage of space used by the filesystem (where the log file resides).If this parameter changes to warning oralarm state, the recovery action willtrigger an event.

This parameter is not available forthe activity log (actlog).

% Warning: 95-98Alarm: over 98

Statistics

TSMLogSpaceAvailable Set by TSMLogCollector. Monitors theavailable space for the log file to use(this is also the available space on thefile system).If this parameter changes to warning oralarm state, the recovery action will

trigger an event.


Availability


Version 2.7.00



TSMLogSpaceGrowthRate Set by TSMLogCollector. Displays thegrowth rate of the amount of space usedby the log file.


KB/s None Statistics

TSMLogSpaceUsed Set by TSMLogCollector. Displays theamount of space used by the log file.


KB None Statistics

TSMLogSpaceUsedPercent*

Set by TSMLogCollector. Monitors thepercentage of capacity used by the logfile.If this parameter changes to warning oralarm state, the recovery action willtrigger an event.

The total capacity is the used space(TSMLogSpaceUsed) plusavailable space(TSMLogSpaceAvailable). This parameter is not availablefor the activity log (actlog).

% Warning: 95-98Alarm: over 98

Statistics

TSMLogSummary Set by TSMLogCollector. Summarizesthe log file information as reported bycommands executed by the datacollector

n/a n/a n/a

TSMLogText Set by TSMLogCollector. Displays alllog text scanned by the data collectorduring the last collection cycle. The sizeof the data scanned by the data collectoris configured in the KM command Configuration > Log(s) Scan Limit.

n/a n/a n/a

TSMLogWarningCount* Set by TSMLogCollector. Monitors thenumber warning messages set in theparameter TSMLogWarningText.If this parameter changes to a warningstate, the recovery action will trigger anevent

count Warning: over1

Statistics

TSMLogWarningText Set by TSMLogCollector. Displays allwarning messages in the log file whichhave not been acknowledged. The filterused by the data collector to determinewarning messages can be customizedusing the KM command Configuration> Log(s) Filter.

n/a n/a n/a


Version 2.7.00


These warning messages can beacknowledged automatically (default) ormanually, depending on theconfiguration in the KM command Configuration > Log(s) AlertAcknowledgement. Manualacknowledgement is available under theKM sub-menu Acknowledgement



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 filepath of the log file.

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






Menu Commands


Acknowledgement > Warnings

Allows acknowledgement of warning alerts on the selected log file instance.This dialog allows selective acknowledgement of "suspicious" error messages detected in thelog 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 logfile 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 tothe text parameter TSMLogWarningText or TSMLogAlarmText.


Version 2.7.00


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 theTSM 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 levelType "[default]" to reset to the log filter configured at the global/container level.

Configuration > Log ScanLimit

Accesses the individual configuration of the data scanning limit for the selected log fileinstance.By default, the global log file scanning limit is used, as configured at the container level.

Configuration > Log AlertAcknowledgement

Accesses the individual configuration of the method of acknowledgement for alerts on theselected log file instance.By default, the global method of log error acknowledgement is used, as configured at thecontainer level.

TSM_POLICY_CONTAINERIcon

Parameters


BPPM Type

TSMDomainDetails Set by TSMPolicyCollector. Displays alldata returned to the standard out fromcommands executed by the datacollector.

n/a n/a n/a

InfoBox

Name Description







Version 2.7.00


Menu Commands


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 > DomainsBackup Restriction

Accesses the global configuration to set a backup restriction window for all monitored domaininstances.By default, backup restriction is disabled.When the backup restriction window is defined and enabled using this menu, and if thedomain status mapping rule is configured appropriately, an alert will be triggered if anybackup activity is detected during this restriction window.

Configuration > DomainsStatus

Accesses the global configuration for determining the domain status for all monitored domaininstances.By default, the following TSMDomainState to TSMDomainStatus mapping rule is used:TSMDomainState TSMDomainStatusRunning in Restricted Window FailureRunning for more than 600 minutes SuspiciousUnknown Suspiciousall other states OkSelect [default] to reset to the default mapping rule.

TSM_POLICYIcon

Parameters


BPPM Type

TSMDomainBackupElapsed*

Set by TSMDomainCollector. Displaysthe elapsed time since the last backup forthis domain, regardless of completionstatus of the backup. This last backup isdetermined from the monitored jobs asconfigured in the KM command Configuration > Jobs from the Jobsicon.The specified alarm ranges can beenabled to allow the output of theparameter to be actively monitored.Then, if this parameter changes towarning or alarm state, the recoveryaction will trigger an event.

hours none Statistics

TSMDomainBackupSummary

Set by TSMDomainCollector.Summarizes the last backup for thisdomain

n/a n/a n/a


Version 2.7.00


TSMDomainBackupThrough

put*

Set by TSMDomainCollector. Displaysthe throughput of the last successfulbackup for this domain.

GB/s none Statistics

TSMDomainFullBackupDurat

ion

Set by TSMDomainCollector. Displaysthe duration of the last successful fullbackup for this domain.

seconds none Statistics

TSMDomainFullBackupElaps

ed*

Set by TSMDomainCollector. Displaysthe elapsed time since the last successfulfull backup for this domain. This lastbackup is determined from the monitoredjobs as configured in the KM command Configuration > Jobs from the Jobsicon.The specified alarm ranges can beenabled to allow the output of theparameter to be actively monitored.Then, if this parameter changes towarning or alarm state, the recoveryaction will trigger an event.


TSMDomainFullBackupObjec

tCount

Set by TSMDomainCollector. Displays thenumber of objects backed up in the lastsuccessful full backup for this domain.

count none Statistics

TSMDomainFullBackupSize

Set by TSMDomainCollector. Displays thesize of the last successful full backup forthis domain.

GB none Statistics

TSMDomainIncrBackupDura

tion

Set by TSMDomainCollector. Displays theduration of the last successfulincremental backup for this domain.


TSMDomainIncrBackupElaps

ed*

Set by TSMDomainCollector. Displaysthe elapsed time since the last successfulincremental backup for this domain. Thislast backup is determined from themonitored jobs as configured in the KMcommand Configuration > Jobs fromthe Jobs icon.

The specified alarm ranges can beenabled to allow the output of theparameter to be actively monitored.Then, if this parameter changes towarning or alarm state, the recoveryaction will trigger an event.


TSMDomainIncrBackupObje

ctCount

Set by TSMDomainCollector. Displaysthe number of objects backed up in thelast successful incremental backup forthis domain.


TSMDomainIncrBackupSize

Set by TSMDomainCollector. Displaysthe size of the last successful incrementalbackup for this domain.

GB none Statistics

TSMDomainState Set by TSMDomainCollector. Displaysthe state of the domain.If a backup restriction window is definedin the KM command Configuration >Domain(s) Backup Restriction, thisparameter will be set to Running inRestricted Window if there is any activityduring the specified period.

0 = Idle1 = Running2 = Runningin RestrictedWindow-1 =Unknown

none Availability


Version 2.7.00


TSMDomainStatus Set by TSMDomainCollector. Monitorsthe status of the domain. This status isdetermined by the domain statusmapping rule defined in the KMcommand Configuration > Domain(s)Status.If this status parameter changes towarning or alarm state, the recoveryaction will trigger an event and annotatethe last data point.


none Availability

TSMDomainSuccBackupElap

sed*

Set by TSMDomainCollector. Displaysthe elapsed time since the last successfulbackup for this domain. This last backupis determined from the monitored jobs asconfigured in the KM command Configuration > Jobs from the Jobsicon.The specified alarm ranges can beenabled to allow the output of theparameter to be actively monitored.Then, if this parameter changes towarning or alarm state, the recoveryaction will trigger an event.


TSMDomainSummary Set by TSMDomainCollector.Summarizes the domain information asreported by commands executed by thedata collector.

n/a n/a n/a



InfoBox

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


Version 2.7.00


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.






Menu Commands


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 bythe TSM KM.

Configuration > DomainBackup Restriction

Accesses the individual configuration for the backup restriction window for the selecteddomain instance.By default, the global backup restriction window setting is used, as configured at thecontainer level.

Configuration > DomainStatus

Accesses the individual configuration for determining domain status for the selected domaininstance.By default, the global TSMDomainState to TSMDomainStatus mapping rule is used, asconfigured at the container level. Select [default] to revert to the domain status mappingrule configured at the global/ container level.

Configuration > ClientNodes

Accesses the dialog for specifying which client nodes of the selected domain are to bemonitored by the TSM KM.By default, all client nodes of enabled domains are monitored. Type [default] to reset tothe default configuration.


Version 2.7.00


TSM_PCLIENTIcon

Parameters


BPPM Type

TSMNodeBackupSummary Set by TSMDomainCollector.Summarizes the last backup for this clientnode.

n/a n/a n/a

TSMNodeBackupThroughpu

t*

Set by TSMDomainCollector. Displaysthe throughput of the last successfulbackup for this client node.

MB/s none Statistics

TSMNodeFullBackupDuratio

n

Set by TSMDomainCollector. Displaysthe duration of the last successful fullbackup for this client node.


TSMNodeFullBackupObjectC

ount

Set by TSMDomainCollector. Displaysthe number of objects backed up in thelast successful full backup for this clientnode.


TSMNodeFullBackupSize*

Set by TSMDomainCollector. Displaysthe size of the last successful full backupfor this client node.

MB none Statistics

TSMNodeIncrBackupDuratio

n

Set by TSMDomainCollector. Displaysthe duration of the last successfulincremental backup for this client node.


TSMNodeIncrBackupObject

Count

Set by TSMDomainCollector. Displaysthe number of objects backed up in thelast successful incremental backup for thisclient node.


TSMNodeIncrBackupSize*

Set by TSMDomainCollector. Displaysthe size of the last successful incrementalbackup for this client node.

MB none Statistics

TSMNodeSummary Set by TSMDomainCollector.Summarizes the client node informationas reported by commands executed bythe data collector.

n/a n/a n/a

TSMObjectExcludeList Set by TSMDomainCollector. Lists allobjects and file systems excluded frombackup for this client node.

n/a n/a n/a


Version 2.7.00


TSMObjectIncludeList Set by TSMDomainCollector. Lists allobjects and file systems included forbackup for this client node.

n/a n/a n/a



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 Backup Save Group Name 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 ScheduleName

Name of schedule to be used during the next backup job.






Menu Commands


Configuration > ClientNode

Accesses the individual configuration for monitoring the selected client node instance.


Version 2.7.00


This dialog allows the selected client node instance to be enabled or disabled for monitoringby the TSM KM.

TSM_JOB_CONTAINERIcon

Parameters


BPPM Type

TSMJobActiveBackupCount

*

Set by TSMJobCollector. Displays thenumber of active backup jobs currentlydiscovered and monitored.


TSMJobActiveCount* Set by TSMJobCollector. Displays thenumber of active jobs currently discoveredand monitored.


TSMJobActiveNonBackupCo

unt*

Set by TSMJobCollector. Displays thenumber of active non-backup jobscurrently discovered and monitored.


TSMJobDetails Set by TSMJobCollector. Displays alldata returned to the standard out fromcommands executed by the data collector.

n/a n/a n/a



InfoBox

Name Description







Version 2.7.00


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 nextcollection cycle.


Allows acknowledgement of warning alerts occurring on any monitored job instance.This dialog allows acknowledgement of any job in a "suspicious" state (which sets theparameter 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 setsthe 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 followingconditions:TSMJobStatus Monitored ForOk 1 daySuspicious 3 daysFailure 3 days The age of a job is calculated from the job start time. The status of a job is determined bythe state of the job (from the parameter TSMJobState) and the job status mapping rule,described below.

Configuration> Jobs Status Accesses the configuration for determining the status for all monitored job instances.By default, the following TSMJobState to TSMJobStatus mapping rule is used: TSMJobState TSMJobStatus Missed, Severed or Failed Failure Pending for more than 1 hour Suspicious Started for more than 5 hours Suspicious Restarted for more than 5 hours Suspicious Completed/Errors Suspicious Started/Errors Suspicious Restarted/Errors Suspicious all other states OkSelect [default] to reset to the default job status mapping rule.

Configuration> Jobs AlertAcknowledgement

Accesses the global configuration of the method of acknowledgement for alerts on monitoredjob instances.By default, the job alerts are manually acknowledged. Using this menu you can change thisso 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.


Version 2.7.00


TSM_JOBIcon

Parameters


BPPM Type

TSMJobDuration Set by TSMJobCollector. Displays theduration of the job from the start.


TSMJobErrorCount* Set by TSMJobCollector. Monitors thenumber of client node errors logged inthe server activity log during this job.

The default settings for thisparameter dictate that when anyerror is detected during a job, thisparameter is always set towarning state. And the recoveryaction will trigger an event.

count Warning when> 100

Statistics

TSMJobNetworkThroughput

*

Set by TSMJobCollector. Displays thethroughput of the job on the network.


TSMJobSize Set by TSMJobCollector. Displays theamount of data backed up for the job.

MB none Statistics


Version 2.7.00


TSMJobState Set by TSMJobCollector. Displays thestate of the job. This is determined usingthe event status and result of the event.

0 =Completed1 = Future2 = Pending3 = InProgress4 = Started5 =Restarted6 =Completed/Errors7 = Started/Errors8 =Restarted/Errors9 = Failed -No Restart10 = Missed11 =Severed12 =Uncertain13 = Failed-1 =Unknown

none Availability

TSMJobStatus Set by TSMJobCollector. Monitors thestatus of the job. This status isdetermined by the job status mappingrule defined in the KM commandConfiguration > Jobs Status.If this status parameter changes towarning or alarm state, the recoveryaction will trigger an event and annotatethe last data point.



Availability

TSMJobSummary Set by TSMJobCollector. Summarizesthe job information as reported bycommands executed by the datacollector.

n/a none n/a

TSMJobText Set by TSMJobCollector. Displays allreported messages related to this job.

n/a none n/a

TSMJobThroughput* Set by TSMJobCollector. Displays thethroughput of the job.


TSMObjectCount Set by TSMJobCollector. Displays thenumber of objects inspected for this job.


TSMObjectExpiredCount Set by TSMJobCollector. Displays thetotal number of objects for this job thathave expired.


TSMObjectFailedCount Set by TSMJobCollector. Displays thetotal number of objects for this job thathave failed.If this parameter changes to a warningstate, the recovery action will trigger anevent.

count Warning when> 100

Statistics

TSMObjectProcessedCount

Set by TSMJobCollector. Displays thetotal number of objects for this job thathave been processed.



Version 2.7.00


TSMObjectReboundCount

Set by TSMJobCollector. Displays thetotal number of objects for this job thathave been rebound.


TSMObjectUpdatedCount

Set by TSMJobCollector. Displays thetotal number of objects for this job thathave been updated.




InfoBox

Name Description

Job Identifier assigned to the job by TSM KM (<Domain Name>:<Client Node Name> @ <JobStart 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.

Processing Time 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.


Version 2.7.00


Data Transfer Time Time taken for the data transfer.

Network Data Transfer Rate Rate of data transfer on the network.

Aggregate Data TransferRate

Aggregated rate of data transfer.

Percent Completed Estimated percentage of the job that has been completed in comparison with the last similarsuccessful 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






Menu Commands


Acknowledgement > Alert 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).


Version 2.7.00


TSM_MOUNT_CONTAINERIcon

Parameters


BPPM Type

TSMRequestDetails Set by TSMRequestCollector. Displaysall data returned to the standard outfrom commands executed by the datacollector.

n/a n/a n/a

InfoBox

Name Description






Menu Commands


Administration > Cancel All Assigns all current mount requests to be canceled.

Reports > Pending MountRequests

Reports a list of all pending mount requests.

Configuration > MountRequests

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 > MountRequests Status

Accesses the configuration for determining the status for all monitored mount requestinstances.By default, the following TSMRequestState to TSMRequestStatus mapping rule is used: TSMRequestState TSMRequestStatus Pending for more than 30 minutes Failure Pending or Unknown Suspicious all other states OkSelect [default] to reset to the default mount request status mapping rule.


Version 2.7.00


TSM_MOUNTIcon

Parameters


BPPM Type

TSMRequestElapsed* Set by TSMRequestCollector.Displays the elapsed time since themount request was issued.

minutes none Statistics

TSMRequestState Set by TSMRequestCollector.Displays the state of the mount requestas reported in the command executedby the data collector.

0 = Completed1 = Pending-1 = Unknown

none Availability

TSMRequestStatus Set by TSMRequestCollector.Monitors the status of the mountrequest. This status is determined bythe mount request status mapping ruledefined in the KM command Configuration > Mount Request(s)Status.


0 = Ok1 = Suspicious2 = Failure


Availability

TSMRequestSummary Set by TSMRequestCollector.Summarizes the mount requestinformation as reported by commandsexecuted by the data collector.

n/a n/a

TSMRequestTimeout* Set by TSMRequestCollector.Displays the time remaining until themount request times out.If the alert state changes to alarmstate, the recovery action will triggeran event.

minutes Alarm: 0-30 Statistics



InfoBox

Name Description

Request ID Identifier assigned to the mount request by Tivoli Storage Manager.


Version 2.7.00


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






Menu Commands

KM Command Action

Administration > Reply Allows a reply to be sent for the selected mount request once a requested action has beentaken.A reply may be required to allow this mount request to continue processing. This requirementis noted in the in the InfoBox item "Reply Required".

Administration > Cancel Allows the selected mount request to be cancelled.


Version 2.7.00


TSM_LIBRARY_CONTAINERIcon

Parameters


BPPM Type

TSMLibraryDetails Set by TSMLibraryCollector. Displaysall data returned to the standard out fromcommands executed by the datacollector.

n/a n/a n/a

InfoBox

Name Description






Menu Commands


Configuration > AutomatedLibraries

Accesses the dialog for specifying which automated libraries are to be monitored by the TSMKM.By default, all local and remote automated libraries are monitored for a server and all localautomated libraries are monitored for a storage agent. Type [default] to reset to the defaultconfiguration.

Configuration > AutomatedLibraries Status

Accesses the global configuration for determining the status for monitored automated libraryinstances.By default, the following TSMLibraryState to TSMLibraryStatus mapping rule is used: TSMLibraryState TSMLibraryStatus Offline or Path Offline Failure Unknown Suspicious all other states OkSelect [default] to reset to the default library status mapping rule.

Configuration > AutomatedLibrary Drives Status

Accesses the global configuration for determining the status for monitored automated librarydrive instances (configured under monitored automated library instances).By default, the following TSMLDriveState to TSMLDriveStatus mapping rule is used: TSMLDriveState TSMLDriveStatus


Version 2.7.00


Unavailable Failure Drive Offline or Path Offline Failure Reserved for more than 1 hour Suspicious Unknown Suspicious all other states OkSelect [default] to reset to the default drive status mapping rule.

TSM_LIBRARYIcon

Parameters


BPPM Type

TSMLibraryState Set by TSMLibraryCollector. Displayswhether the path for the automatedlibrary is online or offline. It will notperform any remote automated librarytest command on the storage agent.

0 = Online1 = Offline2 = PathOffline-1 =Unknown

none Availability

TSMLibraryStatus Set by TSMLibraryCollector. Monitorsthe status of the automated library.This status is determined by theautomated library status mapping ruledefined in the KM command Configuration > Automated Library(Libraries) Status.




Availability

TSMLibrarySummary Set by TSMLibraryCollector.Summarizes the automated libraryinformation as reported by commandsexecuted by the data collector.

n/a n/a n/a

TSMLibraryUpDriveCount

Set by TSMLibraryCollector. Displaysthe number up / online state drives inthis robotic library.



TSMLibraryVolumeCount

Set by TSMLibraryCollector. Displaysthe total number of volume loaded inthis automated library.



Version 2.7.00


TSMLibraryVolumePrivateCo

unt

Set by TSMLibraryCollector. Displaysthe number of private volumes in theautomated library.


TSMLibraryVolumeScratchC

ount

Set by TSMLibraryCollector. Displaysthe number of scratch volumes in theautomated library.


TSMLibraryVolumeScratchP

ercent*

Set by TSMLibraryCollector. Monitorsthe percentage of scratch volumeagainst the total number of volumeloaded in this automated library.If this parameter changes to warning oralarm state, the recovery action willtrigger an event.

% none Statistics



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.

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 withthis 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, SystemAdministrator). This can be a number from 1 to 64.

Private Category Category number for private volumes.

Scratch Category Category number for scratch volumes.



Version 2.7.00






Menu Commands


Reports > AutomatedLibrary Contents

Reports the library volume contents of the selected automated library instance.

Configuration > AutomatedLibrary

Accesses the individual configuration for monitoring the selected automated library instance.This dialog allows the selected automated library instance to be enabled or disabled formonitoring by the TSM KM.

Configuration > AutomatedLibrary Status

Accesses the individual configuration for determining the status for the selected automatedlibrary instance.By default, the global TSMLibraryState to TSMLibraryStatus mapping rule is used, asconfigured at the container level. Select [default] to revert to the library status mapping ruleconfigured at the global/container level.

Configuration > AutomatedLibrary Drives

Accesses the dialog for specifying which drives of the selected automated library are to bemonitored by the TSM KM.By default, all automated library drives are monitored.

Configuration > AutomatedLibrary Drives Status

Accesses the configuration for determining status for monitored drive instances on theselected automated library instance.By default, the global TSMLDriveState to TSMLDriveStatus mapping rule is used, asconfigured at the container level. Select [default] to revert to the drive status mapping ruleconfigured at the global/container level.


Version 2.7.00


TSM_LDEVICEIcon

Parameters


BPPM Type

TSMLDriveState Set by TSMLibraryCollector. Displaysthe state of the automated library drive.This is determined from the automatedlibrary drive control information.

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

none Availability

TSMLDriveStatus Set by TSMLibraryCollector. Monitorsthe status of the automated library drive.This status is determined by theautomated library drive status mappingrule defined in the KM command Configuration > Automated LibraryDrive(s) Status.




Availability

TSMLDriveSummary Set by TSMLibraryCollector.Summarizes the automated library driveinformation as reported by commandsexecuted by the data collector.

n/a n/a n/a

InfoBox

Name Description

Name Name of the automated library drive.

Description Description of the drive.

Device Device path of the drive.


Version 2.7.00


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






Menu Commands


Administration > CleanDrive

Allows the selected automated library drive to be cleaned.

Administration > OnlineDrive

Allows the selected automated library drive to be brought online.

Administration > OfflineDrive

Allows the selected automated library drive to be taken offline.

Configuration > Automated Library Drive

Accesses the individual configuration for monitoring the selected automated library driveinstance.This dialog allows the selected drive instance to be enabled or disabled for monitoring by theTSM KM.

Configuration > Automated Library DriveStatus

Accesses the individual configuration for determining the drive status for the selectedautomated library drive instance.By default, the TSMLDriveState to TSMLDriveStatus mapping rule configured at theparent level is used. (Note that if the mapping rule has not been modified for the parentautomated library, then the default is the global mapping rule configured at the containerlevel.) Select [default] to revert to the drive status mapping rule configured at the parentinstance level.


Version 2.7.00


TSM_DEVICE_CONTAINERIcon

Parameters


BPPM Type

TSMDriveDetails Set by TSMDeviceCollector. Displays alldata returned to standard out fromcommands executed by the data collector.

n/a n/a n/a

InfoBox

Name Description






Menu Commands


Configuration > ManualDrives

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 manualdrives are monitored for a storage agent. Type [default] to reset to the defaultconfiguration.

Configuration > ManualDrives Status

Accesses the global configuration for determining the status for monitored manual driveinstances.By default, the following TSMDriveState to TSMDriveStatus mapping rule is used: TSMDriveState TSMDriveStatus Unavailable Failure Drive Offline or Path Offline Failure Reserved for more than 1 hour Suspicious Unknown Suspicious all other states OkSelect [default] to reset to the default manual drive status mapping rule.


Version 2.7.00


TSM_DEVICEIcon

Parameters


BPPM Type

TSMDriveState Set by TSMDriveCollector. Displays thestate of the manual drive. This isdetermined from the manual drivecontrol information.

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

none Availability

TSMDriveStatus Set by TSMDriveCollector. Monitorsthe status of the manual drive. Thisstatus is determined by the manual drivestatus mapping rule defined in the KMcommand Configuration > ManualDrive(s) Status.




Availability

TSMDriveSummary Set by TSMDriveCollector. Summarizesthe manual drive information as reportedby commands executed by the datacollector.

n/a n/a n/a

InfoBox

Name Description

Name Name of the manual drive.

Description Description of the drive.

Device Device path of the drive.


Version 2.7.00


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






Menu Commands


Administration > CleanDrive

Allows the selected manual library drive to be cleaned.

Administration > OnlineDrive

Allows the selected manual library drive to be brought online.

Administration > OfflineDrive

Allows the selected manual library drive to be taken offline.

Configuration > ManualDrive

Accesses the individual configuration for monitoring the selected manual drive instance.This dialog allows the selected manual drive instance to be enabled or disabled for monitoringby the TSM KM.

Configuration > ManualDrive Status

Accesses the individual configuration for determining the manual drive status for the selectedmanual drive instance.By default, the global TSMDriveState to TSMDriveStatus mapping rule is used, asconfigured at the container level. Select [default] to revert to the drive status mapping ruleconfigured at the global/container level.


Version 2.7.00


TSM_POOL_CONTAINERIcon

Parameters


BPPM Type

TSMPoolDetails Set by TSMPoolCollector. Displays alldata returned to the standard out fromcommands executed by the data collector.

n/a n/a n/a

InfoBox

Name Description






Menu Commands


Configuration > VolumePools

Accesses the dialog for specifying which storage pools are to be monitored by the TSM KM.By default, all storage pools configured on the server are monitored. Type "[default]" to resetto the default configuration.


Version 2.7.00


TSM_POOLIcon

Parameters


BPPM Type

TSMPoolSpaceAvailable* Set by TSMPoolCollector. Monitors theavailable volume space for the backupdata to use in this storage pool.


GB Warning < 1Alarm = 0

Availability

TSMPoolSpaceGrowthRate Set by TSMPoolCollector. Displays thegrowth rate of the total volume spaceused by the backup data in this storagepool.

GB/s None Statistics

TSMPoolSpaceLogicalPerce

nt*

Set by TSMPoolCollector. Displays thelogical occupancy of the storage pool asa percentage of the total occupancy.

% None Statistics

TSMPoolSpaceMigrated* Set by TSMPoolCollector. Displays theamount of data that has been migrated,if migration is in progress. If migration isnot in progress, this value indicates theamount of data migrated during the lastmigration.

GB None Statistics

TSMPoolSpaceMigratedPerc

ent*

Set by TSMPoolCollector. Displays anestimate of the percentage of data in thestorage pool that can be migrated.

% None Statistics

TSMPoolSpaceMigrationEla

psed

Set by TSMPoolCollector. Displays theamount of time that has elapsed sincemigration of the storage pool began, ifmigration is active. If migration is notactive, this value indicates the amount oftime required to complete the lastmigration.


TSMPoolSpaceReclaimable*

Set by TSMPoolCollector. Displays theamount of space in the storage pool thatis reclaimable.

GB None Statistics

TSMPoolSpaceReclaimableP

ercent*

Set by TSMPoolCollector. Displays theamount of reclaimable space as apercentage of the total storage poolspace.

% None Statistics


Version 2.7.00


TSMPoolSpaceUsed* Set by TSMPoolCollector. Displays thetotal volume space occupied by thebackup data in this storage pool.

GB None Statistics

TSMPoolSpaceUsedPercent

*

Set by TSMPoolCollector. Monitors thepercentage of total occupied volumespace against the total volume capacityof this storage pool (not including anyscratch volumes).If this parameter changes to warning oralarm state, the recovery action willtrigger an event.

% Warning: over95Alarm: over 98

Statistics

TSMPoolSummary Set by TSMPoolCollector. Summarizesthe storage pool information as reportedby commands executed by the datacollector.

n/a n/a n/a

TSMVolumeActiveCount Set by TSMPoolCollector. Displays thenumber of active volumes in this storagepool. (Active volumes are available diskvolumes with a status of "Online" or tapevolumes with a status of "Filling", wheredata has been written but the volume isnot yet full.)


TSMVolumeActivePercent*

Set by TSMPoolCollector. Monitors thepercentage of active volumes against thetotal number of volumes in this storagepool.If the status of the parameter changes towarning or alarm state, the recoveryaction will trigger an event.

% None Statistics

TSMVolumeAvailableCount

Set by TSMPoolCollector. Displays thenumber of volumes assigned to thisstorage pool.


TSMVolumeAvailablePercen

t*

Set by TSMPoolCollector. Monitors thepercentage of available volumes againstthe total number of volumes in thisstorage pool.If this parameter changes to warning oralarm state, the recovery action willtrigger an event.

% None Statistics

TSMVolumeCount Set by TSMPoolCollector. Displays thetotal number of volumes in this storagepool.


TSMVolumeEmptyCount Set by TSMPoolCollector. Displays thenumber of empty volumes in this storagepool. ("Empty" is a possible status for atape volume, indicating that no data isstored on that volume)


TSMVolumeFullCount Set by TSMPoolCollector. Displays thenumber of full volumes in this storagepool. ("Full" is a possible status for atape volume.)


TSMVolumeFullPercent*

Set by TSMPoolCollector. Monitors thepercentage of full volumes against thetotal number of volumes in this storagepool.If this parameter changes to warning oralarm state, the recovery action willtrigger an event.

% None Statistics


Version 2.7.00


TSMVolumeOfflineCount

Set by TSMPoolCollector. Displays thenumber of offline volumes in this storagepool. ("Offline" is a possible status for adisk volume.)


TSMVolumePendingCount Set by TSMPoolCollector. Displays thenumber of pending volumes in thisstorage pool. ("Pending" is a possiblestatus for a tape volume, where all fileshave been deleted but a delay has beenplaced on the volume before reuse.)




InfoBox

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 orreclamation processes are active, this field displays as N/A.






Menu Commands


Reports > Volumes List Reports all volumes in the selected storage pool, and their states.

Configuration > StoragePool

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 monitoringby the TSM KM.


Version 2.7.00


TSM_PROCESS_CONTAINERIcon

Parameters


BPPM Type

TSMProcessDetails Set by TSMProcessCollector. Displaysall data returned to the standard outfrom commands executed by the datacollector.

n/a n/a n/a

InfoBox

Name Description






Menu Commands



Allows acknowledgement of warning alerts occurring on any monitored process instance.This dialog allows acknowledgement of any process in a "suspicious" state (which sets theparameter 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 theparameter TSMProcessStatus to Alarm).

Acknowledgement > All Allows acknowledgement of all warnings and alarms occurring on any monitored processinstance.This dialog allows acknowledgement of any process in a "suspicious" or "failure" state (whichsets the parameter TSMProcessStatus to Warning or Alarm, respectively).

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 theprocess start time.


Version 2.7.00


Configuration > ProcessesStatus

Accesses the configuration for determining the status for all monitored process instances.By default, the following TSMProcessState to TSMProcessStatus mapping rule is used:TSMProcessState TSMProcessStatusComplete/Failure FailureRunning/Errors or Unknown SuspiciousRunning for more than 10 hours Suspiciousall other states OkSelect [default] to reset to the default mapping rule.

TSM_PROCESSIcon

Parameters


BPPM Type

TSMProcessDuration Set by TSMProcessCollector. Displaysthe number of seconds since the start ofthe process.


TSMProcessItemCount* Set by TSMProcessCollector. Displaysthe number of items processed.


TSMProcessSize Set by TSMProcessCollector. Displaysthe amount of data processed.

MB None Statistics

TSMProcessState Set by TSMProcessCollector. Displaysthe state of the process. This isdetermined from the process controlinformation.

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

None Availability

TSMProcessStatus Set by TSMProcessCollector. Monitorsthe status of the process. This status isdetermined by the process statusmapping rule defined in the KMcommand Configuration > ProcessesStatus.




Availability


Version 2.7.00


TSMProcessSummary Set by TSMProcessCollector.Summarizes the process information asreported by commands executed by thedata collector.

n/a None n/a

TSMProcessThroughput*

Set by TSMProcessCollector. Displaysthe throughput of the process during thelast backup event.

MB/s None Statistics



InfoBox

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.






Menu Commands


Acknowledgement > Alert Allows acknowledgement of all warnings and alarms occurring on the selected processinstance.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 > CancelProcess

Allows the selected process instance to be canceled.

Troubleshooting

140Impact on Resources

Version 2.7.00


Impact on ResourcesThis 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 TSMKM configuration. As you increase data collection frequency, increase the number of instancesmonitored by the KM or add functionality through customization, your CPU and memory usage willincrease.

When monitoring a standard installation of Tivoli Storage Manager using TSM KM, the PATROL Agentwill consume between 5MBytes and 10MBytes of additional system memory. An enterprise installationof Tivoli Storage Manager Server with multiple Storage Agents, Clients, Automated Libraries, andManual Drives can consume more memory (as per other KMs used by the PATROL Agent). Thememory 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

The data collectors in TSM KM uses Tivoli Storage Manager command line interface to obtain TivoliStorage Manager information. Most of the performance degradation is associated with thesecommand executions and amount of data returned. It may improve the overall performance, if theregular housekeeping is followed on all Tivoli Storage Manager systems.

Network Traffic

Under normal conditions, the TSM KM generates minimal network traffic. Most of the data is kept onthe managed node. The amount of network traffic that it generates depends on the number ofPATROL Consoles that are connected to the PATROL Agent and the frequency of data collection.

Additional Information

142Where to Find Additional Help

Version 2.7.00


Where to Find AdditionalHelpAdditional 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

http://www.tivoli.com/support

Additional help for Tivoli Storage Manager KM for PATROL can be found in the following location: http://www.sentrysoftware.com


http://www.tivoli.com/support

http://www.sentrysoftware.com

Index 143

Version 2.7.00


Index

- A -Abnormalities 55

Access

Permissions 16

User 16Acknowledge

Alarm 80

Alerts 80

Job Alerts 80

Log Alerts 80

Process Alerts 80

Warning 80Acknowledgement

Configure 72

Job 72

Log 72Adapter 52

Add 53, 54

Create 53

Update 54Admin Interface Login 46

Administer

Library Drives 59

Manual Drives 59

Mount Requests 58Agent

PATROL 46Alarm

Acknowledge 80Alarm Filter State Rules 68

Alert Acknowledgement 72

Configure 72

Job 72

Log 72Alerts

Acknowledge 80Application Clas

TSM_POLICY 108Application Class

TSM_CLIENT 91

TSM_CLIENT_CONTAINER 90

TSM_DAEMON 94

TSM_DAEMON_CONTAINER 93

TSM_DATABASE 97

TSM_DATABASE_CONTAINER 96

TSM_DEVICE 130

TSM_DEVICE_CONTAINER 129

TSM_JOB 116

TSM_LDEVICE 127

TSM_LIBRARY 124

TSM_LIBRARY_CONTAINER 123

TSM_LOG 104

TSM_LOG_CONTAINER 102

TSM_MOUNT 121

TSM_MOUNT_CONTAINER 120

TSM_PCLIENT 112

TSM_POLICY_CONTAINER 107

TSM_POOL 133

TSM_POOL_CONTAINER 132

TSM_PROCESS 137

TSM_PROCESS_CONTAINER 136

TSM_SERVER 84

- B -Baselines

BMC ProactiveNet Performance Management 55

Generation 55

Manage 55

Requirements 55BMC

BMC ProactiveNet Performance ManagementPortal 52

BMC PATROL

Changes 14BMC ProactiveNet

Integration 52BMC ProactiveNet Performance Management

Abnormalities 55

Baselines 55

Key Performance Indicators 55

KPI 55

- C -Cancel

Mount Request 58Changes 8

Check

Index 144

Version 2.7.00


Check

Instance Limits 49Classes 83

Clean

Drive 59Clients

Delete 62

Disable 62

Enable 62

Status Configuration 68Cluster

Configure 61Clustering Application 61

Commands

Reload 80Configuration

Admin Interface Login 84

Debug 84

Instance Limits 84

Login 84

Monitoring Mode 84

Node Status 84

Node Type 84

Paths 84

Preloading 84Configure

Alert Acknowledgement 72

Cluster 61

Domain Backup Restriction 71

KM User Account 46

Log Error Filter 69

Log Scan Limit 71

Monitoring Period 64

Multi-Node Monitoring Mode 61

Node Type 60

Paths 60

PATROL Agent 44Customize

KM 59

- D -Daemons

Delete 62

Disable 62

Enable 62

Status Configuration 68Data Collectors

Force 75Databases

Delete 62

Disable 62

Enable 62Debug

Disable 77

Enable 77

End 77

Files 77

Path 77Delete

Clients 62

Daemons 62

Databases 62

Logs 62

Policies 62

Policy Clients 62

Robotic Drives 62

Robotic Libraries 62

Standalone Drives 62

Storages 62

Volume Pools 62Disable

Clients 62

Daemons 62

Databases 62

Debug 77

Logs 62

Policies 62

Policy Clients 62

Robotic Drives 62



Storages 62

Volume Pools 62Discoveries

Force 75Discovery

Verify 48Domain Backup Restriction

Configure 71DSM_CONFIG 60

DSM_DIR 60

DSM_LOG 60

Index 145

Version 2.7.00


- E -Enable

Clients 62

Daemons 62

Databases 62

Debug 77

Logs 62

Policies 62

Policy Clients 62

Robotic Drives 62



Storages 62

Volume Pools 62

- F -Failover Group Name 61

Files 22

ins_ALL_<version>.tar 21

ins_WINDOWS_<version>.exe 21

Setup 22

setup.exe 24

setup.sh 24

uninstall.exe 37

uninstall.sh 37Filtering Options

Clients 62

Daemons 62

Databases 62

Logs 62

Policies 62

Policy Clients 62

Robotic Drives 62



Storages 62

Volume Pools 62Force

All Data Collectors 75

All Discoveries 75

Full data collection 75

Selected Data Collectors 75Force Discovery 84

- G -Generate

Baselines 55

Reports 81

- H -help 142

- I -Improvement 8

InfoBox

Access 133

ACS Id 124

Action 116

Activated Default Management Class 108

Activated Policy Set 108

Activation Date/Time 108

Actual Start 116

Aggregate Data Transfer Rate 116

Allocated To 127, 130

Application 91

Application Name 84

Application Version 84

Archive Retention 108

Assigned Space 97

Available FS Space 104

Available Space 97

Backup Retention 108

Binary Path 84

Buffer Pool Pages 97

Collector Last End 90, 91, 93, 94, 96, 97,102, 104, 107, 108, 112, 114, 116, 120, 121,123, 124, 127, 129, 130, 132, 133, 136, 137

Collector Last Start 90, 93, 94, 96, 97,102, 104, 107, 108, 112, 114, 116, 120, 121,123, 124, 127, 129, 130, 132, 133, 136, 137

Collector Name 90, 91, 93, 94, 96, 97,102, 104, 107, 108, 112, 114, 116, 120, 121,123, 124, 127, 129, 130, 132, 133, 136, 137

Collector Next Start 90, 91, 93, 94, 96,97, 102, 104, 107, 108, 112, 114, 116, 120,121, 123, 124, 127, 129, 130, 132, 133, 136,137

Index 146

Version 2.7.00


InfoBox

Collector Status 90, 91, 93, 94, 96, 97,102, 104, 107, 108, 112, 114, 116, 120, 121,123, 124, 127, 129, 130, 132, 133, 136, 137

Command 94

Completed 116

Copyright 84

Data Transfer Time 116

Description 91, 94, 97, 104, 108, 112,121, 124, 127, 130, 133

Device 124, 127, 130

Device Class 133

Domain Name 112, 116

Drive Name 121

Drive Online 127, 130

Duration 137

Element 127, 130

End 137

Event Status 116

External Manager 124, 127, 130

FS Percent Used 104

Host Name 84

Installation Path 84

Items 137

Job 116

Job Type 121

Lan Free 124

Last Backup 97

Last Backup Duration 116

Last Backup End 108, 112, 116

Last Backup Job 108, 116

Last Backup Mode 97

Last Backup Objects 116

Last Backup Save Group 112

Last Backup Size 116

Last Backup Start 108, 112, 116

Last Backup Status 108, 112

Last Communication Method 91

Last Full Backup End 108, 112

Last Full Backup Job 108, 112

Last Full Backup Start 108, 112

Last Incr Backup End 108

Last Incr Backup End Time 112

Last Incr Backup Job 108, 112

Last Incr Backup Start 108, 112

Last Message 137

Last Purge 97, 104

Library Name 121, 127, 130

Library Path 84

Log File Modification Time 104

Log File Size 104

Maximum Extension 97

Maximum Percent Utilized 97

Maximum Reduction 97

Maximum Scratch Volumes 133

Migration In Progress 133

Mode 116, 121

Monitoring Mode 84

Monitoring Node 84

Name 91, 94, 97, 104, 108, 112, 124,127, 130, 133

Network Data Transfer Rate 116

Next Backup 108, 112

Next Backup Schedule Name 108, 112

Node Name 116, 124, 127, 130

Node Name(s) 84

Node Type 84

Number of Registered Nodes 108

Obey Mount Retention 124

Objects Compression 116

Objects Deleted 116

Objects Expired 116

Objects Failed 116

Objects Inspected 116

Objects Processed 116

Objects Rebound 116

Objects Updated 116

Operating System 84, 91, 112

Owner 94

Page Size 97

Path 97, 104

Path Online 124, 127, 130

PATROL Agent Version 84

Percent Completed 116

Percent Utilized 97

Physical Volumes 97

PID 94

Platform 84

PPID 94

Primary Library Manager 124

Private Category 124

Process Mode 137

Process Name 137

Process Number 137

Processing Time 116

Product Name 84

Product Release Date 84

Product Version 84

Index 147

Version 2.7.00


InfoBox

Reason 116

Reclamation In Progress 133

Reply Required 121

Request ID 121

Request Time 121

Request Timeout 121

Result 116

Schedule 116

Scheduled Start 116

Scratch Category 124

Serial Number 124, 127, 130

Server 84

Server Name 121, 124, 127, 130

Session Numbers 116

Shared 124

Size 116, 137

Start 137

Status 91, 94, 108, 116, 124, 127, 130,137

Storage Pool Data Format 133

Support 84

Time Remaining 116

Time Since Last Communication 91

Total FS Space 104

Total Usable Pages 97

Type 116, 124, 127, 130, 133

Used Pages 97

Version 91

Volume 121

Volume Being Migrated/Reclaimed 133

Volume Type 121

Web Site 84

World Wide Name 124, 127, 130Install / Un-install 24, 37

BMC Software Installation Utility 21

Log 24

Packages 22

Procedure 24

Setup Files 22Installation 60

Instance Limits

Check 49Integration

BMC ProactiveNet 52Integration Service Agent 53

Introduction 24

Issues

Fixed 8

- J -Job Alerts

Acknowledge 80Jobs

Configure 64


Status Configuration 68

- K -Key Performance Indicators


Manage 55KM

Configure 46

Customize 59

Initial Setup 49

Load 43, 44, 52

Preload 44

Preloaded 45, 46

Unload 45, 46

User Account 46KPI


Manage 55

- L -Library Drives

Administer 59

Clean 59

Offline 59

Online 59Load

KM 43, 44, 52

PATROL Central 44Log Alerts

Acknowledge 80Log Error Filter

Configure 69Log Scan Limit

Configure 71Logs

Delete 62

Index 148

Version 2.7.00


Logs

Disable 62

Enable 62

- M -Manage

Baselines 55

Key Performance Indicators 55

KPI 55Managed Node

Status Configuration 68Manual Drives

Administer 59

Clean 59

Offline 59

Online 59Master Server

Configure 60Media Server

Configure 60Menu Commands

About 84

Acknowledgement 104, 114, 116, 136,137

Active Processes 136

Activity Log Messages 102

Administration 84, 120, 121, 127, 130,137

Al 136

Alarms 104, 114, 136

Alert 116, 137

All 104, 114

Automated Libraries 123

Automated Libraries Status 123

Automated Library 124

Automated Library Contents 124

Automated Library Drive 127

Automated Library Drive Status 127

Automated Library Drives 124

Automated Library Drives Status 123, 124

Automated Library Status 124

Cancel 121

Cancel All 120

Cancel Process 137

Clean Drive 127, 130

Client 91

Client Node 112

Client Nodes 108

Client Status 91

Clients 90

Clients Status 90

Configuration 90, 91, 93, 94, 96, 97, 102,107, 108, 112, 114, 120, 123, 124, 127, 129,130, 132, 133, 136

Daemon 94

Daemon List 93

Daemons 93

Daemons Status 93, 94

Database 97

Database Backup Volume History 96

Database Volumes 97

Databases 96

Domain 108

Domain Backup Restriction 108

Domain Schedule 108

Domain Status 108

Domains 107

Domains Backup Restriction 107

Domains Status 107

Force Discovery 84

Force Full Collection 114

Jobs 114

Jobs Alert Acknowledgement 114

Jobs Status 114

KM Status 84

Log 104

Log Alert Acknowledgement 104

Log Filter 104

Log Scan Limit 104

Logs 102

Logs Alert Acknowledgement 102

Logs Filter 102

Logs Scan Limit 102

Manual Drive 130

Manual Drive Status 130

Manual Drives 129

Manual Drives Status 129

Mount Requests 120

Mount Requests Status 120

Offline Drive 127, 130

Online Drive 127, 130

Pending Mount Requests 120

Processes 136

Processes Status 136

Refresh Parameters 84

Refresh Process Cache 84

Index 149

Version 2.7.00


Menu Commands

Reload Commands 84

Reply 121

Reports 93, 96, 97, 102, 108, 120, 124,133, 136

Start Server 84

Start Storage Agent 84

Stop Server 84

Storage Pool 133

Volume Pools 132

Volumes List 133

Warnings 104, 114, 136Monitor Type 53

Monitoring Period

Configure 64

Jobs 64

Mount Requests 64

Processes 64Mount Requests

Administer 58

Cancel 58

Configure 64


Status Configuration 68Multi-Node Monitoring Mode

Configure 61

- N -New features 8

Node Type

Configure 60

Master Server 60

Media Server 60Notification 58

- O -Offline

Drive 59Online

Drive 59Operating Systems

Linux 21, 22, 24, 37

Unix 21, 22, 37

Windows 21, 22, 24, 37Options

Common services 24

Console Systems role 24

Managed System 24

View Log 24Oracle Solaris Cluster 61

- P -Parameter

TSMLoginStatus 46Parameters 83

ExtraFilesList 84

Refresh 75

TSMClientCollector 84

TSMClientDetails 90

TSMClientLastAccessElapsed 91

TSMClientSpaceUsed 91

TSMClientState 91

TSMClientStatus 91

TSMClientSummary 91

TSMCreateDistribution 84

TSMDaemonCollector 84

TSMDaemonCPUDuration 94

TSMDaemonCPUUtilization 94

TSMDaemonDetails 93

TSMDaemonMemorySize 94

TSMDaemonProcessCount 94

TSMDaemonState 94

TSMDaemonStatus 94

TSMDaemonSummary 94

TSMDatabaseBackupElapsed 97

TSMDatabaseCacheHitPercent 97

TSMDatabaseCacheWaitPercent 97

TSMDatabaseCollector 84

TSMDatabaseDetails 96

TSMDatabaseFSSpaceUsedPercent 97

TSMDatabaseLogConsumedSize 97

TSMDatabaseLogPoolUsedPercent 97

TSMDatabaseLogPoolWaitPercent 97

TSMDatabasePoolHitPercent 97

TSMDatabaseReorgElapsed 97

TSMDatabaseSpaceAvailable 97

TSMDatabaseSpaceChanged 97

TSMDatabaseSpaceChangedPercent 97

TSMDatabaseSpaceGrowthRate 97

TSMDatabaseSpaceMaxExtension 97

TSMDatabaseSpaceMaxReduction 97

TSMDatabaseSpaceUsed 97

TSMDatabaseSpaceUsedPercent 97

Index 150

Version 2.7.00


Parameters 83

TSMDatabaseSummary 97

TSMDomainBackupElapsed 108

TSMDomainBackupSummary 108

TSMDomainBackupThroughput 108

TSMDomainCollector 84

TSMDomainDetails 107

TSMDomainFullBackupDuration 108

TSMDomainFullBackupElapsed 108

TSMDomainFullBackupObjectCount 108

TSMDomainFullBackupSize 108

TSMDomainIncrBackupDuration 108

TSMDomainIncrBackupElapsed 108

TSMDomainIncrBackupObjectCount 108

TSMDomainIncrBackupSize 108

TSMDomainState 108

TSMDomainStatus 108

TSMDomainSuccBackupElapsed 108

TSMDomainSummary 108

TSMDriveCollector 84

TSMDriveDetails 129

TSMDriveState 130

TSMDriveStatus 130

TSMDriveSummary 130

TSMJobActiveBackupCount 114

TSMJobActiveCount 114

TSMJobActiveNonBackupCount 114

TSMJobCollector 84

TSMJobDetails 114

TSMJobDuration 116

TSMJobErrorCount 116

TSMJobNetworkThroughput 116

TSMJobSize 116

TSMJobState 116

TSMJobStatus 116

TSMJobSummary 116

TSMJobText 116

TSMJobThroughput 116

TSMLDriveState 127

TSMLDriveStatus 127

TSMLDriveSummary 127

TSMLibraryCollector 84

TSMLibraryDetails 123

TSMLibraryState 124

TSMLibraryStatus 124

TSMLibrarySummary 124

TSMLibraryUpDriveCount 124

TSMLibraryVolumeCount 124

TSMLibraryVolumePrivateCount 124

TSMLibraryVolumeScratchCount 124

TSMLibraryVolumeScratchPercent 124

TSMLogAlarmCount 104

TSMLogAlarmText 104

TSMLogCollector 84

TSMLogDetails 102

TSMLogFSSpaceUsedPercent 104

TSMLoginStatus 84

TSMLogSpaceAvailable 104

TSMLogSpaceGrowthRate 104

TSMLogSpaceUsed 104

TSMLogSpaceUsedPercent 104

TSMLogSummary 104

TSMLogText 104

TSMLogWarningCount 104

TSMLogWarningText 104

TSMMonitoringMode 84

TSMNodeBackupSummary 112

TSMNodeBackupThroughput 112

TSMNodeFullBackupDuration 112

TSMNodeFullBackupObjectCount 112

TSMNodeFullBackupSize 112

TSMNodeIncrBackupDuration 112

TSMNodeIncrBackupObjectCount 112

TSMNodeIncrBackupSize 112

TSMNodeStatus 84

TSMNodeSummary 112

TSMObjectCount 116

TSMObjectExcludeList 112

TSMObjectExpiredCount 116

TSMObjectFailedCount 116

TSMObjectIncludeList 112

TSMObjectProcessedCount 116

TSMObjectReboundCount 116

TSMObjectUpdatedCount 116

TSMPoolCollector 84

TSMPoolDetails 132

TSMPoolSpaceAvailable 133

TSMPoolSpaceGrowthRate 133

TSMPoolSpaceLogicalPercent 133

TSMPoolSpaceMigrated 133

TSMPoolSpaceMigratedPercent 133

TSMPoolSpaceMigrationElapsed 133

TSMPoolSpaceReclaimable 133

TSMPoolSpaceReclaimablePercent 133

TSMPoolSpaceUsed 133

TSMPoolSpaceUsedPercent 133

TSMPoolSummary 133

TSMProcessCollector 84

Index 151

Version 2.7.00


Parameters 83

TSMProcessDetails 136

TSMProcessDuration 137

TSMProcessItemCount 137

TSMProcessSize 137

TSMProcessState 137

TSMProcessStatus 137

TSMProcessSummary 137

TSMProcessThroughput 137

TSMRequestCollector 84

TSMRequestDetails 120

TSMRequestElapsed 121

TSMRequestState 121

TSMRequestStatus 121

TSMRequestSummary 121

TSMRequestTimeout 121

TSMUpdateAgent 84

TSMVolumeActiveCount 133

TSMVolumeActivePercent 133

TSMVolumeAvailableCount 133

TSMVolumeAvailablePercent 133

TSMVolumeCount 133

TSMVolumeEmptyCount 133

TSMVolumeFullCount 133

TSMVolumeFullPercent 133

TSMVolumeOfflineCount 133

TSMVolumePendingCount 133Paths

Binary 60

DSM_CONFIG 60

DSM_DIR 60

DSM_LOG 60

Installation 60

Library 60PATROL

Agent 46

PATROL Agent 45

PATROL Central Console 45, 46

PATROL Console 45PATROL Agent

Configure 44

Restart 50PATROL Console 44

Restart 50Platform

Upgrade 42Platforms

Unix 46Policies

Delete 62

Disable 62

Enable 62Policy Clients

Delete 62

Disable 62

Enable 62Preload

KM 44Preloaded

KM 45, 46Prepare

Debug Files 77ProactiveNet 53

Process Alerts

Acknowledge 80Processes

Configure 64

Monitoring Period 64PW Commands 54

- R -Refresh

Parameters 75Release Notes 8

Reload

Commands 80remote PATROL Agent Checking 61

Reports

Generate 81Requirements

Security 16

Software 14

System 14Restart

PATROL Agent 50

PATROL Console 50Robotic Drives

Delete 62

Disable 62

Enable 62

Status Configuration 68Robotic Libraries

Delete 62

Disable 62

Enable 62

Status Configuration 68

Index 152

Version 2.7.00


- S -Security

Requirements 16Server

Start 58

Stop 58Setup

Check 49

Initial 49

KM 49Software

Requirements 14Standalone Drives

Delete 62

Disable 62

Enable 62

Status Configuration 68Start

Server 58

Storage Agent 58Status Configuration

Clients 68

Daemons 68

Jobs 68

Managed Node 68

Mount Requests 68

Robotic Drives 68


Standalone Drives 68Stop

Server 58

Storage Agent 58Storage Agent

Start 58

Stop 58Storages

Delete 62

Disable 62

Enable 62Sudo 16, 46

System

Requirements 14

- T -Thresholds

Customize 54

Import 54Tivoli Storage Manager

Changes 14TSM_CLIENT

Application Class 91TSM_CLIENT_CONTAINER

Application Class 90TSM_DAEMON

Application Class 94TSM_DAEMON_CONTAINER

Application Class 93TSM_DATABASE

Application Class 97TSM_DATABASE_CONTAINER

Application Class 96TSM_DEVICE

Application Class 130TSM_DEVICE_CONTAINER

Application Class 129TSM_JOB

Application Class 116TSM_LDEVICE

Application Class 127TSM_LIBRARY

Application Class 124TSM_LIBRARY_CONTAINER

Application Class 123TSM_LOG

Application Class 104TSM_LOG_CONTAINER

Application Class 102TSM_MOUNT

Application Class 121TSM_MOUNT_CONTAINER

Application Class 120TSM_PCLIENT

Application Class 112TSM_POLICY

Application Class 108TSM_POLICY_CONTAINER

Application Class 107TSM_POOL

Application Class 133TSM_POOL_CONTAINER

Application Class 132TSM_PROCESS

Application Class 137TSM_PROCESS_CONTAINER

Index 153

Version 2.7.00


TSM_PROCESS_CONTAINER

Application Class 136TSM_SERVER

Application Class 84TSMRequestTimeout 58

- U -Unix 46

Unload

KM 45, 46Upgrade

Platform 42

- V -Verify

Application Discovery 48Veritas Cluster File System 61

Veritas Cluster Server 61

Volume Pools

Delete 62

Disable 62

Enable 62

- W -Warning

Acknowledge 80Warning Filter State Rules 68

What's new 8

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

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

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

please visit www.sentrysoftware.net.

tivoli storage manager km for patrol - sentry software · tivoli storage manager km for patrol...

Documents