Tivoli Storage Manager KM for PATROL vx.x Storage Manager KM for PATROL Version 2.7.02 4 Tivoli...

Tivoli Storage Manager KM forPATROL

STORAGE MONITORING

USER DOCUMENTATION

Version 2.7.02

September 2015

http://sentrysoftware.com/Solutions/Storage_solution.asp

http://www.sentrysoftware.com

Contacting BMC Software

You 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

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

Telephone 1 (713) 918 8800 or 1 (800) 841 2031 (Toll Free)

Copyright 2006 BMC Software, Inc. or licensors, as an unpublished work. All rights reserved.

BMC Software, the BMC Software logos, and all other BMC Software product or service names areregistered trademarks or trademarks of BMC Software, Inc.

All other trademarks belong to their respective companies.

BMC Software considers information included in this documentation to be proprietary andconfidential. Your use of this information is subject to the terms and conditions of the applicableEnd User License Agreement for the product and the proprietary and restricted rights noticesincluded in this documentation.

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 forthin FAR 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 thisaddress.

2

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Customer Support

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.

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-mail addresses, fax numbers, and telephone numbers

You can also access product documents and search the Knowledge Base for help with an issue at http://www.sentrysoftware.com

Support by Telephone or E-mail

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

3

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

http://www.bmc.com/support_home




4

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Table of Contents.....................................................................................................................................................................................15Requirements

.......................................................................................................................................................................................15System Requirements

.......................................................................................................................................................................................15Software Requirements

.......................................................................................................................................................................................17Security Requirements

.......................................................................................................................................................................................22Disk Space Requirements

.....................................................................................................................................................................................22Getting the BMC Software Installation Utility

.....................................................................................................................................................................................24Packages

.....................................................................................................................................................................................24Extracting the Setup Files

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

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

.....................................................................................................................................................................................44Upgrading the Platform

.....................................................................................................................................................................................44Performing Post-Installation Operations

.......................................................................................................................................................................................45Loading and Unloading the KM

......................................................................................................................................................................45Loading the KM

..........................................................................................................................................................................45Loading the KM on PATROL Console

..........................................................................................................................................................................46Loading the KM on PATROL Central

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

......................................................................................................................................................................46Unloading the KM

..........................................................................................................................................................................47Unloading the KM from the PATROL Agent

..........................................................................................................................................................................47Unloading the KM from the PATROL Console

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

.......................................................................................................................................................................................48Configuring the KM User Account

.......................................................................................................................................................................................51Verifying Application Discovery

.......................................................................................................................................................................................51Checking the Instance Limits

.......................................................................................................................................................................................52Checking the Initial Setup of the KM

.......................................................................................................................................................................................52Restarting PATROL Agent and PATROL Console

.....................................................................................................................................................................................54Integrating with BMC Portal

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

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

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

.......................................................................................................................................................................................56Importing and Customizing Thresholds

.......................................................................................................................................................................................57Managing Baselines and Key Performance Indicators

5

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

.....................................................................................................................................................................................60Administering Tivoli Storage Manager

.......................................................................................................................................................................................60Starting/Stopping the Server

.......................................................................................................................................................................................60Starting/Stopping the Storage Agent

.......................................................................................................................................................................................60Administering Mount Requests

.......................................................................................................................................................................................61Administering Drives

.......................................................................................................................................................................................61Cancelling Processes

.....................................................................................................................................................................................61Configuring the KM

.......................................................................................................................................................................................62Configuring Paths

.......................................................................................................................................................................................63Specifying the Node Type

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

.......................................................................................................................................................................................65Filtering Elements to Monitor

.......................................................................................................................................................................................67Configuring Monitoring Periods

.......................................................................................................................................................................................71Configuring the Elements Status

.......................................................................................................................................................................................72Configuring the Log Filter

.......................................................................................................................................................................................74Configuring the Log Scan Limit

.......................................................................................................................................................................................76Configuring Domain Backup Restriction

.......................................................................................................................................................................................76Configuring Alert Acknowledgement

.......................................................................................................................................................................................79Refreshing Parameters

.......................................................................................................................................................................................81Enabling the Debug Mode

.......................................................................................................................................................................................84Reloading Commands

.....................................................................................................................................................................................84Acknowledging Alerts

.....................................................................................................................................................................................86Generating Reports

.....................................................................................................................................................................................89Classes and Parameters

.......................................................................................................................................................................................90TSM_SERVER

.......................................................................................................................................................................................97TSM_CLIENT_CONTAINER

.......................................................................................................................................................................................99TSM_CLIENT

.......................................................................................................................................................................................102TSM_DAEMON_CONTAINER

.......................................................................................................................................................................................103TSM_DAEMON

.......................................................................................................................................................................................106TSM_DATABASE_CONTAINER

.......................................................................................................................................................................................107TSM_DATABASE

.......................................................................................................................................................................................112TSM_LOG_CONTAINER

.......................................................................................................................................................................................114TSM_LOG

.......................................................................................................................................................................................118TSM_POLICY_CONTAINER

.......................................................................................................................................................................................119TSM_POLICY

.......................................................................................................................................................................................124TSM_PCLIENT

.......................................................................................................................................................................................126TSM_JOB_CONTAINER

6

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

.......................................................................................................................................................................................129TSM_JOB

.......................................................................................................................................................................................134TSM_MOUNT_CONTAINER

.......................................................................................................................................................................................135TSM_MOUNT

.......................................................................................................................................................................................137TSM_LIBRARY_CONTAINER

.......................................................................................................................................................................................138TSM_LIBRARY

.......................................................................................................................................................................................142TSM_LDEVICE

.......................................................................................................................................................................................144TSM_DEVICE_CONTAINER

.......................................................................................................................................................................................145TSM_DEVICE

.......................................................................................................................................................................................147TSM_POOL_CONTAINER

.......................................................................................................................................................................................149TSM_POOL

.......................................................................................................................................................................................153TSM_PROCESS_CONTAINER

.......................................................................................................................................................................................154TSM_PROCESS

.....................................................................................................................................................................................158Impact on Resources

.....................................................................................................................................................................................160Where to Find Additional Help

Release Notes for v2.7.02

8

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

What's NewTSM-248: TSM KM now supports Tivoli Storage Manager Server 7.1.x and Tivoli StorageManager Administrative Client 6.4.x and 7.1.x, as well as the two operating systems Solaris11 and Windows 2012.

Changes and ImprovementsTSM-204: The query limit for actlogs has been reduced from 1 day to 5 hours. Also, theactlogs query limit can now be user-limited (only available from an actlog instance).

TSM-225: The KM Home Directory path can now be shared when multiple TSM instances aremonitored. The KM Temp Directory, KM Debug Directory and DSM Log paths must howeverremain different (see KB article “Monitoring Multiple IBM Tivoli Storage Manager ServerInstances (TSM)).

Fixed IssuesTSM-134: A configuration problem prevented the proper monitoring of different TSMinstances through different PATROL Agents on the same TSM server, causing the KM to stopoperating. A procedure is now available in the Knowledge Base of the Sentry’s Web site thatdescribes how to configure the KM in order to monitor multiple IBM Tivoli Storage ManagerServer instances.

TSM-141: The TSMLoginStatus parameter triggered false warning when errors from theJOB_TEXT command output occurred.

TSM-142: The product sometimes failed to trigger alerts for missing TSM daemons.

TSM-161 & TSM-168: When activated, the TSMDaemonCollectorExecTime parameter was notappearing in the console under Daemons. Also, an error is displayed on the SOW for thesame missing parameter.

TSM-167: When monitoring multiple TSM instances using different PATROL Agents,dsmadmc interface hangs intermittently. The interface access is changed to lock acrossAgents to avoid simultaneous dsmadmc command executions.

TSM-179: Migration related parameters (TSMPoolSpaceMigrated,TSMPoolSpaceMigratedPercent & TSMPoolSpaceMigrationElapsed) are not available forcopy storage pools.

TSM-180: The KM would create unknown job instance (: @ <unknown>) at times, with alloffline parameters.

TSM-186: When upgrading the KM to version 2.7.01, custom log filters for alarm and warningwere lost.

TSM-188: The KM temporary file system fills up when aclog query grows. To avoid this, awarning message is added to System Output Window (SOW) when any monitored log is notfully processed due to log scan limitation.

TSM-224: On Linux platforms, the commands were randomly corrupted and caused the KM tofail.

TSM-241: The KM custom paths were lost when they were set through PCM and when thePATROL Agent was not restarted immediately after the update.

http://www.sentrysoftware.com/kb/KB1136.asp



9

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSM-269: Due to a PATROL events limitation, the KM failed to trigger log events when a largeamount of errors were found in the TSM activity log.

TSM-285: The product failed to identify the creation error for PCM suppressed instances andcontinued running commands against it, affecting the collector performance.

TSM-291: PATROL Agent was crashing when large actlogs were being processed. To solve thisissue, the TSM KM user related activity is no more processed in the actlog. As a consequence,the memory consumption has been reduced.

TSM-297: TSM KM failed to detect Node Status errors as configured in the KM menuConfiguration > Node Status.

TSM-303: The Sudo configuration requirements have been updated in the SecurityRequirements chapter of the user documentation.

TSM-309: Old TSM jobs were not removed from the console if they were discovered ascompleted.

TSM-321: Full and incremental domain level backup summary parameters were not setcorrectly, preventing the product to properly monitor backups at the domain and nodelevels.

TSM-328: On Windows systems, if the PATROL Agent installation path contained spaces,custom KM scripts and commands with output redirection failed.

TSM-329: The TSMLoginStatus parameter was in warning due to an incorrect configurationvariable used while checking the active cluster node.

TSM-330: The Microsoft Cluster active node was not properly detected when the KM wasoperating in multi-node monitoring mode.

TSM-335: The main discovery cycle was irregular due to an asynchronous default KMdiscovery interval. It is now reduced to 30 seconds to avoid such irregularity.

10

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Overview

12

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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 andstatus

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 PATROLConsole. Alarms and warnings inform you when a suspicious behavior is detected; thus allowingyou to quickly and clearly identify peaks, troughs and trends in the performance of your backupresources.

13

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Monitoring Tivoli Storage Manager

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

Preparing for Installation

15 Requirements

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

RequirementsSystem Requirements

Operating System Operating System Version

Sun® microsystems SolarisTM 8, 9, 10, 11

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

IBM® AIXTM 5.1, 5.2, 5.3, 6.1

Red Hat® Linux® 7.2

Microsoft® Windows® 2003, 2008, 2008 R2, 2012

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

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, 7.1.x

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

BMC Software PATROL Agent 3.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

BMC TrueSight Operations Management 10

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 theTivoli Storage Manager server for use by PATROL and the TSM KM. Refer to Admin Interface UserAccess.

To allow this user to execute SQL SELECT queries, there should be at least 4Mbytes of temporary

16Requirements

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

table storage space all the time to avoid exhausting the temporary table storage.

Changes to BMC PATROL

To improve the performance of the TSM KM, the PATROL Agent tuning variable /AgentSetup/AgentTuning/pslInstructionMax should be disabled by setting it to 0 (zero) or increased to atleast 5,000,000. This applies for all Tivoli Storage Manager servers and storage agents where theKM is installed. This adjustment will allow the data collectors to execute without incurring aninternal scheduling delay.

This PATROL Agent tuning variable can be updated using wpconfig (on MicrosoftWindows),xpconfig (on Unix) or PATROL Configuration Manager (PCM). Alternatively, you canuse one of the following single line PSL command through the PATROL Console OS> prompt toupdate this tuning variable.

To disable:

%PSL pconfig("REPLACE",

"/AgentSetup/AgentTuning/pslInstructionMax",0);

To set to at least 5,000,000:

%PSL v="/AgentSetup/AgentTuning/pslInstructionMax";

if(get(v)<5000000){pconfig("REPLACE",v,5000000);}

In large Tivoli Storage Manager systems, the value of 5,000,000 for the tuning variable“pslInstructionMax” may still be insuf f icient. In such situations, error messages will appear on the PATROLConsole System Output Window (SOW) reporting that some TSM KM data collectors are in an inf inite loop.In this case you can set the tuning variable to zero to 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) shouldbe able to read and write to these pconfig variables at anytime. If Access Control List (ACL) isused to control which users are authorized to connect to a PATROL Agent, please ensure that themode for PATROL Agent user includes “C” in the PATROL Agent variable /AgentSetup/accessControlList. Please refer the PATROL Agent Reference Manual for more details.

You cannot copy or distribute these KM conf iguration variables between managed nodes, because theymay not have the same value for each managed node. For example, the login user details may not be thesame for all managed nodes. Also some of these variables, like installation paths, are set automaticallyduring the initial discovery.

Additional Software Requirements

Purpose Software Version

17 Requirements

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

When running TSM KM on Linuxmanaged nodes

Korn shell binary (/bin/ksh) Any

When running TSM KM onMicrosoft Windows x64 managednodes

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 keysfrom PATROL Agent. Access the above patch site f rom the managed node to obtain the correct patch forthat platform.

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

The following user accounts can be used:

On Unix platforms:

a root user

a non-root user, such as patrol, that has sudo privileges on Tivoli Storage Manager toexecute application 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 Managerapplication to 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 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 how toset up an ACL.

Access Permissions

The TSM KM user needs “read & execute” permission to executable and library files under thepaths listed below. The Tivoli Storage Manager installation path INSTALL_PATH, referenced

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




18Requirements

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

below, is normally /usr/tivoli/tsm or /opt/tivoli/tsm (on Unix) or C:\Program Files\Tivoli\TSM(on Microsoft Windows).

Unix Microsoft Windows

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

INSTALL_PATH/client/admin/bin INSTALL_PATH\Server

INSTALL_PATH/server/bin INSTALL_PATH\StorageAgent

INSTALL_PATH/StorageAgent/bin INSTALL_PATH\Server\tsmdiag

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

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

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

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

The TSM KM includes some scripts which should be executable by the PATROL Agent user andthe TSM 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-"," "," "));

}

19 Requirements

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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 userneeds “read & execute” permission.

Unix Microsoft Windows

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

DSM_LOG (KM_TEMP) DSM_LOG (KM_TEMP)

DSM_DIR/dsmadmc DSM_DIR\dsmadmc.exe

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

If a monitored log file cannot be read by the PATROL Agent user, it will copied to KM_HOME path 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 theregistry sub-keys under HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\.

The configured login user should have sufficient privileges to run regedit command on themanaged node.

Sudo User for Operating System Access

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

The code below also applies to all non-root users who may execute TSM KM administration andreport menu commands using their sudo privileges. The TSM KM accepts any non-root user withthe following sudo configuration in the sudoers file. Please replace user1, user2, user3 withappropriate KM user name. The Tivoli Storage Manager installation path INSTALL_PATH,referenced below is normally /usr/tivoli/tsm or /opt/tivoli/tsm and PATROL_HOME is the pathwhere the PATROL Agent is installed (including the target, like /opt/bmc/Patrol3/Solaris29-sun4/).

20Requirements

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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, user3

Defaults:TSMKMUSERS !lecture,!authenticate,!requiretty,\

env_keep+="PATH LD_LIBRARY_PATH INSTALL_PATH KM_HOME KM_TEMP",env_reset

KM_TEMP DSM_CONFIG DSM_DIR DSM_LOG",env_reset

TSMKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\

INSTALL_PATH/server/bin/*,\

INSTALL_PATH/client/ba/bin/*,\

PATROL_HOME/lib/TSM/*,PATROL_HOME/bin/*

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

On HP-UX:



env_keep+="PATH SHLIB_PATH INSTALL_PATH KM_HOME KM_TEMP",env_reset







On AIX & Linux:



env_keep+="PATH LIBPATH INSTALL_PATH KM_HOME KM_TEMP",env_reset






21 Requirements

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2


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 serverthrough the Tivoli Storage Manager Administrative Client interface (DSMADMC). No changes aremade by this user on the Tivoli Storage Manager server - the TSM KM operates in “read-only”mode for normal operation.

The suggested name for this DSMADMC user account is patrol and it can be created as part of 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 duringKM configuration in the same way that the OS login details are entered. The password is storedin the PATROL Agent in a DES encrypted format.

DSMADMC command binary is executed using an OS user account matching the DSMADMC login.If this account does not exists, the PATROL Agent user account will be used. Therefore it isrecommended to create an operating system user account matching the DSMADMC usernamewith the same password to avoid invalid user login attempts and to improve the performance.This user should be able to access required paths and binaries of DSMADMC. This includes an'execute' permission to DSM_CONFIG path and dsmadmc (or dsmadmc.exe) file and a 'write'permission to DSM_LOG path and dsmerror.log file.

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 theencrypted password through the PATROL Console. This can be prevented by setting up anappropriate Access Control List (ACL) for users. Please refer to the PATROL Agent ReferenceManual for details on how to set up an ACL.

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

22Requirements

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

}

}

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 willgenerate approximately 500 KBytes of history data per day. An enterprise installation of TivoliStorage Manager on a server with multiple storage agents, clients, automated libraries, andmanual drives will generate more history data (as per other KMs used by the PATROL Agent).These history data files are recycled by PATROL depending on the PATROL Agent historyretention period.

During execution, the TSM KM creates and maintains temporary files under KM_HOME,KM_TEMP and KM_DEBUG paths. By default they are all under PATROL_HOME/lib/TSM, wherePATROL_HOME path is normally /opt/bmc/Patrol3/ (on Unix) or C:\Program Files (x86)\BMCSoftware\Patrol3\ (on Microsoft Windows).

If the location of the KM_TEMP or KM_DEBUG is not suitable, it can be changed using theConfiguration > 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 Software InstallationUtilityIn 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 BMCSoftware EPD (electronic product download) from: http://webapps.bmc.com/signon/content/logon.jsp on the BMC Software Website, or from the Tivoli Storage Manager KM for PATROL pageon the Sentry Software Website

Choose the appropriate package depending on the platform you plan to install Tivoli StorageManager KM for PATROL on:

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

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

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

23 Getting the BMC Software Installation Utility

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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 forPATROL packages.

24Getting the BMC Software Installation Utility

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

PackagesThe Tivoli Storage Manager KM for PATROL packages are available on the Sentry Software Website.

There are two packages, each of which can be used to install the KM on every PATROLcomponent (Agent, Console, etc.) according to the platform you are using:

For Windows systems: tsm_ALL_<version>.exe

For UNIX and Linux systems: tsm_ALL_<version>.tar

The Tivoli Storage Manager KM for PATROL packages are designed for use with the BMC SoftwareInstallation 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 forPATROL on the following components of your PATROL architecture:

Every managed system with a PATROL Agent

Every PATROL Console (Classic) that will show Tivoli Storage Manager performance-relatedinformation and alerts

The Console Server

PATROL Central – Web Edition



Installing the KM

26

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Introduction

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

Installing Tivoli Storage Manager KMfor PATROLInstalling Tivoli Storage Manager KM for PATROL is an automated process managed by a wizard.The wizard goes through the necessary steps to install Tivoli Storage Manager KM for PATROL andall files associated with it. You are simply prompt for the product's folder location and theproduct/components to install.

Browse to the bmc_products folder where the files have been extracted (both Tivoli StorageManager KM for PATROL and the Common Installer).

27 Installing Tivoli Storage Manager KM for PATROL

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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 Wizard - Step 1: Windows Security Alert

28Installing Tivoli Storage Manager KM for PATROL

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

Installation Wizard - Step 2: Welcome


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

Installation Wizard - Step 3: Reviewing License Agreement


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

Installation Wizard - Step 4: Selecting Installation Options


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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 Wizard - Step 5: Selecting the Installation Directory


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

Installation Wizard - 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 Serveror on PATROL Central – Web Edition.

Click Next to continue.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Installation Wizard - Step 7: Selecting Roles

Select as many options as required.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

Installation Wizard - Step 8: Selecting Products and Components


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

Installation Wizard - Step 9: Reviewing Installation Options


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

10. The setup program displays the actions performed and indicates the percentage ofcompletion.Once the installation complete, click Next to view the installation results.

Installation Wizard - Step 10: Installation Status


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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 Wizard - Step 11: Installation Results

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


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Installation Wizard - Step 12: Completing and closing the Installation Wizard

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


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Uninstalling Tivoli Storage ManagerKM for PATROLUninstalling Tivoli Storage Manager KM for PATROL is an automated process managed by awizard. The wizard goes through the necessary steps to remove Tivoli Storage Manager KM forPATROL and all files associated with it. You are simply prompt for the product's folder locationand 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 Wizard — Welcome Step

40Uninstalling Tivoli Storage Manager KM forPATROL

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

Un-install Wizard — Specifying folder

41 Uninstalling Tivoli Storage Manager KM forPATROL

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

Un-install Wizard — Selecting Products and Components Directory


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

4. Click Start Uninstall to run the program.

Un-install Wizard — Reviewing Selected Products & components and start uninstalling

43 Uninstalling Tivoli Storage Manager KM forPATROL

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

Un-install Wizard — Status


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

Un-install Wizard — Uninstall Results

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

Performing Post-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

45 Performing Post-Installation Operations

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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.

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.

46Performing Post-Installation Operations

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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 f ind the TSM_LOAD.kml f ile in the wizard list for any system you selected, then the KM hasnot been installed 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 isto be 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 successfullyadded to the list, an acknowledgement will be displayed.

The same menu is used to remove the TSM KM f iles f rom the preloaded KMs list.

Unloading the KMThis section describes the procedures for unloading (not uninstalling) the TSM KM from thePATROL Agent, PATROL Console or PATROL Central Console. The intention is that this section isonly used if you no longer want to use some parts of the KM, though there may be circumstanceswhere you may wish to fully unload the KM without uninstalling the files; if you want tocompletely uninstall the KM, refer to the uninstall procedure.

When the KM is unloaded:


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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 TivoliStorage Manager application on any PATROL Console connected system.

Unloading the KM from the PATROL Agent

To unload the KM from the PATROL Agent:

1. Remove the TSM KM from the list of preloaded KMs using the menu Configuration>Preloading from the Tivoli Storage Manager instance. Alternatively, using theutility wpconfig (on Microsoft Windows) or xpconfig (on Unix), remove TSM_LOAD.kml fromthe 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 tobe unloaded.

The TSM KM cannot be partially unloaded from the PATROL Agent using the above steps. If you need tounload some parts of the KM from the PATROL Agent, refer to the PATROL Agent Reference Manual.

Unloading the KM from the PATROL Console

Application classes are unloaded individually. This allows for a partial unloading of the KM toenable it to run as a reduced installation.

To unload the TSM KM completely or partially:

1. Remove the unwanted TSM KM application classes from the list of loaded applicationclasses, as required. 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.

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.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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 atonce. This allows for a partial unloading of the KM to enable it to run as a reduced installation onsome or all of the managed systems.

To completely or partially unload the TSM KM from some or all of the managed systems:

1. Right click on the PATROL Main Map, and choose Unload Knowledge Modules...

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 theappropriate managed systems, click Next> and Finish.

4. Repeat the above steps for each PATROL Central Management Profile where the TSM KM isto be unloaded.

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

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

a root user

a non-root user, such as patrol, that has sudo privileges on Tivoli Storage Manager to 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:


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

an administrator user

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

Step 1: Configure the KM User Account:1. In the Console, right-click the Tivoli Storage Manager instance > Configuration>Login. The

Login Configuration dialog is displayed:

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.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

The password is stored in the PATROL Agent in a DES encrypted format. The encrypted password canbe viewed 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. Thiscan be 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.

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

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.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Verifying Application DiscoveryTo verify the application discovery:

1. Check that the TSM_SETUP instance is actually named Tivoli Storage Manager. If not, force afull discovery by right-clicking the TSM_SETUP instance > KM Commands > Force Discovery

2. Check that the application class instances are actually instantiated. The initial data 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 toenable 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 isrecommended to 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.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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 inthe format TSM<Obj ect>Details), and check for error messages.

5. Check the new values of parameter TSMLoginStatus set after completion of all datacollection. If either is not in OK state, open the annotation point to determine the cause ofthe 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 anywarnings or alarms in the KM Status report), determine the cause(s) and take steps to resolve these errors.You may need to refer to the User Guide or contact Technical Support at Sentry Software, attaching the KMStatus report.

To save the KM Status report as a task window, click Save As Task. This task window can then be printedor saved as a text f ile.

Restarting PATROL Agent and PATROL 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 forceall KM discoveries and data collections to start immediately.

Integrating the KM

54

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Introduction

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

Integrating with BMC Portal1. 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 BMC ProactiveNetPerformance Management 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 PATROLapplication classes (provided in a Knowledge Module–KM) into BMC ProactiveNet. The Adapterperiodically synchronizes the performance data collected by these application classes into BMCProactiveNet.

55 Integrating with BMC ProactiveNet PerformanceManagement 8.5.x and 8.6.x

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Creating and Importing an Adapter for a BMCPATROL 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 ServiceAgent.

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 toconfirm. 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 Adaptersfolder, right-click the Adapter and select Details.

We strongly recommend that you create a specific adapter for each KM you need to integrate intoBMC ProactiveNet to enable the update of a single KM independently.

56Integrating with BMC ProactiveNet PerformanceManagement 8.5.x and 8.6.x

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Updating an Adapter for a BMC PATROL 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 ProactiveNetdocumentation available f rom BMC Web site.

Importing and Customizing Thresholds1. 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 properlyinterpreted.

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 notproperly converted by the PATROL Adapter.

6. Save the file.

7. Execute the following command:pw threshold loadpatrolthreshold [<thresholdfilename> [-v]]

where:

<thresholdfilename> is a thresholds file name. If no file path is specified then

the default '<Installation Directory>/pw/tmp/' is used

57 Integrating with BMC ProactiveNet PerformanceManagement 8.5.x and 8.6.x

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

-v enables the Verbose mode

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 Key PerformanceIndicatorsIn order to facilitate the detection of abnormalities on your monitored environment, BMCProactiveNet calculates baselines per parameter (metrics or attributes) based on valuescollected over a specified period of time to determine a normal operating range. When thecollected values for these parameters are out of range, an alert is triggered.

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

Managing baselines

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

The baseline is calculated by collecting the values for a monitor’s attributes and metrics over aspecified time period and establishing a low baseline value (consisting of the 10th percentile ofall the values for a given time period) and a high baseline value (consisting of the 90th percentileof all the values for a given time period), taking a weighted average of these values over time. Ahigher weight is given to the latest data being factored into the baseline average. The accuracyof the baseline improves over time.

Requirements for baseline generation

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

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

Managing Key Performance Indicators

The KPI attribute of a parameter can be activated or deactivated manually through the BMC

58Integrating with BMC ProactiveNet PerformanceManagement 8.5.x and 8.6.x

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

ProactiveNet Administration Console. In this KM, some parameters or attributes have beendesignated as important indicators of performance (KPIs). We do not recommend that thesedefault settings are modified.

However, advanced users may activate or deactivate KPIs from the BMC ProactiveNetAdministration Console.

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

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

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

3. In the KPI column for the attributes that you want to add or remove as Key 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 ProactiveNetdocumentation available f rom BMC Web site.

Parameters for which the system by default calculates baselines as well as parametersconsidered as KPIs are respectively identified by the following icons:

Baselining

KPI

Monitoring your Environment

60

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

Administering Tivoli Storage ManagerTivoli Storage Manager KM for PATROL provides secure server administration menus, which canbe executed by PATROL Console users, if they have appropriate privileges. They can moreespecially:

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 thatthe requested action was actually performed. To send the notification, right-click the relevantmount request instance > Administration > Reply

To cancel:

61 Administering Tivoli Storage Manager

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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 andselect one 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 TivoliStorage Manager application environment. This section describes all menus available forcustomizing the TSM KM. These customization menus are accessed from the knowledge modulecommand sub-menu Configuration> from each application instance. Most of these customizationmenus can be accessed 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, youthen have the option to apply this change to all child instances which appear under the selectedcontainer in PATROL Console instance topology. If a customization menu is accessed from thechild instance, it will only modify the configuration applicable for that instance.

In the absence of a child instance level conf iguration, the KM will search for any modif ied conf igurationthrough its topological parent path. If no customized conf igurations found, the KM will use the defaultconf iguration.

62Configuring the KM

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

If a menu command is named Configuration > Client(s), it means that the menu command is availableas Configuration > Client f rom the parent container instance (client container instance) and Configuration> Clients f rom the child instance (individual client instance).

Configuring PathsThe solution automatically discovers the installation, binary, and library paths. This informationcan however be overridden.

Altering these paths may impact the operation of the KM.

To configure paths:

1. In the Console, right-click the Tivoli Storage Manager instance > KM commands >Configuration > Paths

2. In the KM section, verify and possibly modify the Home, Temp, and Debug Directory Paths

3. In the TSM section, verify and possibly modify the Installation and the DSM_DIR, DSM_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 f ields, click OK, and restart the PATROL Agent.

63 Configuring the KM

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Specifying the Node TypeYou may have to manually indicate the type of node monitored if the discovery fails to recognizeit:

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.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Configuring the Multi-Node Monitoring ModeIf the Tivoli Storage Manager environment is installed in a cluster using Veritas Cluster Server,Veritas Cluster File System, Oracle Solaris Cluster or Microsoft Cluster, the TSM KM must beinstalled on all the cluster nodes to enable continuous monitoring and avoid single point offailure. To avoid duplicate alerts from multiple nodes, it is recommended to configure thesolution 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 vxconfigdin enable 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 withthe remote PATROL Agent (authentication server, protocol, port number, and credentials)

6. Click OK.

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


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

Filtering Elements to MonitorBy default, the solution monitors all the elements discovered, which may represent animportant workload to the agents and servers. Because the monitoring of some elements maybe irrelevant for various reasons, you can apply filters to indicate which elements will bemonitored or not.

Some instances have specif ic 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 localmanual drives discovered will be monitored

To filter the elements to be monitored:


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

Client Configuration dialog

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

2. To enable elements for monitoring:

In the current configuration list, select the elements to enable

Select Enable

Click Update

A log f ilter will have to be conf igured if you enable log f iles for monitoring.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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, thusleaving parameters not set.

4. To delete elements for monitoring:

In the current configuration list, select the elements to delete

Select Delete

Click Update

5. To add a new element to monitor:

Type the name of the element to be monitored

If needed, enter a description

From the Status list, select Enable

Click Update.

To revert to the default monitoring conf iguration, type “[default]” as a new entry and click Update.

6. Resume the procedure for all the application classes for which you wish to apply monitoringfilters.

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, andall executed TSM internal server processes for 3 days. You can however modify these settings tobetter suit your requirements:

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


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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 collectioncycle

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


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

2. Indicate how long the mount requests will be monitored. If you decrease the monitoringperiod, 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 datacollection cycle

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

3. Click OK.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

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

Client Status Configuration dialog


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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 analarm when the Never Communicated state of the Clients instance lasts more than 60minutes:

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 f ilter, select [default] f rom the list of states and clickUpdate.

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 awarning or an alarm. Each time the KM will find these expressions in a log file or in TSMLogText,the error message will be written to the TSMLogAlarmText or TSMLogWarningText parameter.By default, the default log filter is configured for the Server Activity Log and the system log file.If you enabled additional log files for monitoring, you will have to customize the log filter byadding appropriate expressions for those log files.

For an explanation of the possible error messages in the log f iles, refer to the Tivoli Storage ManagerSystem Administrator’s Guide and the Tivoli Storage Manager Troubleshooting Guide.

To configure the log error filter:


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

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 standardwildcard syntax, such as “ANR2121W” or “ANR21[0-9].W”.”.

Select Exclude


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

6. Click Update.

To revert to the default settings for either f ilter, type [default] as a new error expression for that f ilter,and click Update. If you revert to the default settings when accessed from the log instance level, the settingswill revert to the parent or container instance level. To revert to the shipped default settings (as shownabove), access this dialog from the log container instance. From this level you will also have the option toreset the conf iguration of any modif ied child instances.

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. Thislog scan limit can however be modified to better suit your requirements.

Increasing the Log Scan Limit may impact the performance of the data collector (TSMLogCollector), 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 ScanLimit


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Configuring Log Scan Limit

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

3. Indicate the maximum query limit (in minutes). By default the KM queries up to 300 minutes(5 hours) of actlog data. (only available from an actlog instance)

4. Click OK.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Configuring Domain Backup RestrictionTSM KM can be configured to trigger a warning when a backup is started during a specific periodof time:

1. In the Console, right-click:

the Domains instance > KM Commands > Configuration> Domains Backup Restriction toapply this customization to all policies

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

Domain Backup Restriction Window 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 settingsto allow manual acknowledgement.

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


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Configuring Logs Alert Acknowledgement

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

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

Configuring Log Alert Acknowledgement

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 toconfigure the job alert acknowledgement as follows:


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

Configuring Job Alert Acknowledgement


3. Click Ok.

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


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

Configuring Process Alert Acknowledgement


5. Click Ok.

Refreshing ParametersThis section describes how to manually refresh parameters without waiting for an automaticpolling cycle.

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.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Forcing All Data Collectors

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

Refresh Process Cache to refresh the PATROL Agent process cache

Refresh parameters to force all data collectors at the same time.

The TSM KM data collectors and all the data collectors defined under the application classesloaded on the PATROL Agent will then be refreshed.

Forcing Selected Data Collectors

This option is only available from a PATROL Developer Console.

1. Right-click the Tivoli Storage Manager instance and select Refresh Process Cache to 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 collectioncycle. However, it can be forced to search for all jobs within the monitored time period duringthe next collection cycle.

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


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

Enabling the Debug ModeWhen you encounter an issue and wish to report it to Sentry Software, you will be asked toenable the 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


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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 diskspace and read, write and execute permissions for both PATROL Agent user and the TSMKM login user

Select Send to File(s) to write all debug messages in a file or set of files.

Select Send to Task Window to view the debug messages as they occur in the TSM DebugOutput window. Before selecting this option, make sure the PATROL Console is connectedto the PATROL Agent.

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


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

4. Click OK first to start TSM KM debugging

5. Click Yes to reload the KM and capture debug from the initial collection cycle.

Disabling the Debug Mode

The debug switches will be turned off automatically when the debug end time is reached. A tar/zip file is then automatically created under <PATROL_HOME>/lib/TSM/ and can be sent to theBMC Support for help. It is also recommended to check the SOW or TSM.log file, stored in<PATROL_HOME>/log, for any error.

If you want to manually stop debugging:

1. Access the TSM KM Debug Configuration dialog

2. Select Off for the debug switch(es) you want to disable

3. Click OK.

Preparing the Debug Files for Sending to Sentry Software

If you chose to only send the output to a task window, you can save the debug output as follows:

Right-click in the TSM KM Debug Output window.

Select Save As and specify a location to save data.

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 found in$PATROL_HOME/lib/TSM/

tsm_km_debug_<date>_<time>.zip file (Windows systems). This file could later be foundin %PATROL_HOME%\lib\TSM\

Click No if you do not want to compress the files. You will then be asked if you want to retainor delete them.

If the compressed f ile is not created successfully, you can create it manually by including all f iles and sub-directories under $PATROL_HOME/lib/TSM/ (on Unix) or %PATROL_HOME%\lib\TSM\ (on Microsoft Windows).

Appending Output Data to Existing Files

If you want to gather output from several debug sessions:


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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.

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-click the Tivoli Storage Manager instance > KM Commands > Reload Commands.

Acknowledging AlertsBy default, alerts are acknowledged automatically. They can however be acknowledgedmanually if you do not want to wait for the automatic cycle. Manual acknowledgement will alsobe required if you modified the alert acknowledgement default settings.

Manually Acknowledging Log Alerts

When an error is detected in a monitored log file, it will either appear in TSMLogAlarmText 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:

85 Acknowledging Alerts

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

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 canbe acknowledged using the menu Acknowledgement > Alert from the relevant process instance.

To acknowledge process alerts:

3. In the Console, right-click the Processes instance > KM Commands > Acknowledgement

4. Select:

Acknowledgement > Warnings to view and acknowledge alerts for all processes with 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.

86Generating Reports

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

<Automated Library instance> > Reports > Automated Library Contents - reports the libraryvolume contents of the automated library instance

Daemons > Reports > Daemon List - lists all running Tivoli Storage Manager daemons

Databases > Reports > Database Backup Volume History - reports server database backupvolume 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 (since midnight)

Mount Requests > Reports > Mount Requests - reports a list of all pending mount requests

Processes > Reports > Active Processes - reports a list of all active processes on the managednode

<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 savedas a text f ile

Reference Guide

88

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Introduction

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

89 Classes and Parameters

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Classes and ParametersThis section lists the application classes of TSM KM. It gives you details on the icons thatrepresent the class, Infobox, parameters and the menu commands available for each applicationclass. There are 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 andKPIs, please refer to the Managing Baselines and Key Performance Indicators chapter.

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

90Classes and Parameters

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Baselining

KPI

TSM_SERVERIcon

Parameters

Name Description Units Default AlertConditions

BPPM Type

ExtraFilesList Is used for pushing TSM KMlibrary files to the PATROL Agentduring the "Commit" operation.

n/a n/a n/a

TSMClientCollector Collects Tivoli Storage Managerclient related information. It setsall consumer parameters in TSM_CLIENT_CONTAINER andTSM_CLIENT application classes.By default, this collector isexecuted only on the server.

Polling Interval: 600 seconds

n/a n/a n/a

TSMCreateDistribution Is automatically activated at theend of TSM KM debugging if thecustomer chooses to "preparedebug files for sending to SentrySoftware". It is deactivated oncompletion.


n/a n/a n/a

TSMDaemonCollector Collects Tivoli Storage Managerdaemon related information. Itsets all consumer parameters in TSM_DAEMON_CONTAINER andTSM_DAEMON applicationclasses.


n/a n/a n/a


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSMDatabaseCollector Collects Tivoli Storage Managerserver database relatedinformation. It sets all consumerparameters in TSM_DATABASE_CONTAINER andTSM_DATABASE applicationclasses.By default, this collector isexecuted only on the server.


n/a n/a n/a

TSMDomainCollector Collects Tivoli Storage Managerdomain and client node relatedinformation. It sets all consumerparameters in TSM_POLICY_CONTAINER,TSM_POLICY, and TSM_PCLIENTapplication classes.By default, this collector isexecuted only on the server.


n/a n/a n/a

TSMDriveCollector Collects Tivoli Storage Managermanual drive related information.It sets all consumer parametersin TSM_DEVICE_CONTAINER andTSM_DEVICE application classes.


n/a n/a n/a

TSMJobCollector Collects Tivoli Storage Managerbackup/restore event relatedinformation. It sets all consumerparameters in TSM_JOB_CONTAINER andTSM_JOB application classes.By default, this collector isexecuted only on the server.


n/a n/a n/a

TSMLibraryCollector Collects Tivoli Storage Managerautomated library and automatedlibrary drive related information.It sets all consumer parametersin TSM_LIBRARY_CONTAINER,TSM_LIBRARY, and TSM_LDEVICEapplication classes.


n/a n/a n/a

TSMLogCollector Collects Tivoli Storage Managerlog file related information. It setsall consumer parameters inTSM_LOG_CONTAINER andTSM_LOG application classes.

n/a n/a n/a


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2


TSMLoginStatus* Monitors the status of the TSM KMlogin details (username/password) for the operatingsystem and DSMADMC. It is set byTSM_SERVER application classdiscovery.If no valid username/password isdetected for the operating systemor DSMADMC, this parameter willbe set to Failure state. If there areany suspicious command exits,this parameter will be set toSuspicious state.If this status parameter changesto warning or alarm state, therecovery action will trigger anevent and annotate the last datapoint.

0 = Ok1 =Suspicious 2 = Failure

Warning = 1Alarm = 2

CollectionStatus

TSMMonitoringMode* Monitors failover mode of the TSMKM. It is set by TSM_SERVERapplication class discovery.By default TSM KM runs inPermanent Single-node Mode.Multi-node monitoring can beconfigured using the KMcommand Configuration >Monitoring Mode from the TivoliStorage Manager icon.

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

n/a CollectionStatus

TSMNodeStatus* Monitors error messages for theTivoli Storage Managerapplication on this managedsystem. It is set by TSM_SERVERapplication class discovery.

The value of this parameter isdetermined by the node statusmapping rule defined in the KMcommand Configuration > NodeStatus from the Tivoli StorageManager icon.

If this status parameter changesto warning or alarm state, therecovery action will trigger anevent and annotate the last datapoint.

0 = Ok1 =Suspicious2 = Failure


Availability


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSMPoolCollector Collects Tivoli Storage Managerstorage pool related information.It sets all consumer parameters inTSM_POOL_CONTAINER andTSM_POOL application classes.

By default, this collector isexecuted only on the server.


n/a n/a n/a

TSMProcessCollector Collects Tivoli Storage Managerserver process relatedinformation. It sets all consumerparameters inTSM_PROCESS_CONTAINER andTSM_PROCESS applicationclasses.By default, this collector isexecuted only on the server.


n/a n/a n/a

TSMRequestCollector Collects Tivoli Storage Managermount request relatedinformation. It sets all consumerparameters inTSM_MOUNT_CONTAINER andTSM_MOUNT application classes.By default, this collector isexecuted only on the server. Polling Interval: 300 seconds

n/a n/a n/a

TSMUpdateAgent Used by the TSM KM to set thePATROL Agent KM variables whenthe PATROL Console user is notauthorized to update (ACL) anyPATROL Agent variables. It isactivated automatically when theKM fails to update the PATROLAgent.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 instancein 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.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

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

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]


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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 discoverycycle. 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 logindetails for the operating system.This user account should have privileges to execute Tivoli Storage manageradministration commands and can use sudo privileges on Unix PATROL Agents.This user account will be used by TSM KM pre-discoveries, discoveries, datacollectors, recovery actions, and InfoBoxes to execute operating systemcommands. It will not be used by any KM commands.The password is encrypted and stored on the PATROL Agent using the BMCPATROL encryption function.

Configuration> AdminInterface Login

Accesses the Admin Interface Login Configuration dialog for entering and viewingDSMADMC login account details.This admin account (suggested name patrol) is used by the TSM KM to queryTivoli Storage Manager.This user account will be used by TSM KM pre-discoveries, discoveries, datacollectors, recovery actions, and InfoBoxes to execute DSMADMC queries. It willnot be used by any KM commands.The password is encrypted and stored on the PATROL Agent using BMC PATROLencryption function.

Configuration> Preloading

Accesses Preloading Configuration dialog, which adds or removes the KM fromPATROL Agent variable "/AgentSetup/preloadedKMs".By preloading the NSR KM, the PATROL Agent will monitor the Tivoli StorageManager application without any PATROL Console connection.

Configuration> Monitoring Mode

Accesses the Monitoring Mode Configuration dialog, which is used for enablingor disabling TSM KM failover, when monitoring clustered Tivoli Storage Managerenvironment.

Configuration> Paths Accesses the Path Configuration dialog, which displays and sets all paths usedby the TSM KM.Paths are automatically discovered by the TSM KM server discovery. They areused as environment variables for executing various Tivoli Storage Managerapplication commands. Altering these paths may impact the operation of the KM.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

KM paths are used as environment variables and internally:

KM_HOME keeps all KM scripts.

KM_TEMP is used for creating KM temporary files.

KM_DEBUG is used for creating KM debug files.

Installation Path is the application installation path discovered by the KM. This informationcan be overridden through the KM command

Binary Paths are the Application and operating system binary path, which isused for setting PATH environment variable. The KM discovers and set thisautomatically. This menu can be used, if the discovered paths are incorrect.

Library Paths are the Application and operating system library path, which isused for setting the following environment variables:

LD_LIBRARY_PATH (on Solaris)SHLIB_PATH (on HP-UX)LIBPATH (on AIX)

The KM discovers and set this automatically. This menu can be used, if thediscovered paths are incorrect.

DSM_DIR Directory Path, DSM_DIR Directory Path, and DSM_DIR Directory Path

are the TSM application paths used while executing DSMADMC commands.

TSM application paths used while executing DSMADMC commands.

Configuration> NodeType

Accesses the Node Type Configuration dialog, which displays and sets the type ofthe Tivoli Storage Manager application node.The TSM KM server discovery detects the type of the node automatically; the typecan either be Server or Storage Agent. The operation of the KM depends on thisnode type.

Configuration> NodeStatus

Accesses the Node Status Configuration dialog for viewing and modifying theerror expression filters, which determine the status of the node (parameterTSMNodeStatus).By default, the following "Included" expressions are checked. If detected, they setthe parameter TSMNodeStatus to alert, unless the message also contains an"Excluded" expression.

Type "[default]" to reset to the default configuration.

Configuration> Instance Limits

Accesses the Instance Limits Configuration dialog to view and modify themaximum number of TSM KM application instances allowed for eachapplication class.

Configuration> Debug Accesses the Debug Configuration dialog for enabling/disabling the TSM KMdebug 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.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSM_CLIENT_CONTAINERIcon

Parameters


BPPM Type

TSMClientDetails Set by TSMClientCollector. Displaysall data returned to the standardout from commands executed bythe data collector.

n/a n/a n/a

InfoBox

Name Description

Collector Name Name of the data collector that sets variables and parameters under thisapplication 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 TSMKM.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 formonitored client instances.By default, following TSMClientState to TSMClientStatus mapping rule is used:


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Select [default] to reset to the default client status mapping rule.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSM_CLIENTIcon

Parameters


BPPM Type

TSMClientLastAccessElapsed*

Set by TSMClientCollector.Displays the time elapsed sincethe last communication from theclient.The specified alarm ranges can beenabled to allow the output of theparameter to be activelymonitored. Then, if this parameterchanges to warning or alarm state,the recovery action will trigger anevent.

Hours None Statistics

TSMClientSpaceUsed* Set by TSMClientCollector.Displays the amount of space usedon the client node.

Gigabytes(GB)

None Statistics

TSMClientState Set by TSMClientCollector.Displays the state of the client asreported in the command executedby the data collector.

0 = Running1 = Locked2 = NeverCommunicated-1 =Unknown

None Availability

TSMClientStatus Set by TSMClientCollector.Monitors the status of the client.This status is determined by theclient status mapping rule definedin the KM command Configuration> Client(s) Status.

If this status parameter changes towarning or alarm state, therecovery action will trigger anevent and annotate the last datapoint.

0 = OK1 =Suspicious 2 = Failure

Warning = 1Alarm =2

Availability

TSMClientSummary Set by TSMClientCollector.Summarizes the client informationas reported in commands executedby the data collector.

n/a None n/a


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2




Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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 theconnection 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 thecurrent node.

Last CommunicationMethod

Method of the last connection from the current node.






Menu Commands


Configuration> Client Accesses the individual configuration for monitoring the selected clientinstance.This dialog allows the selected client instance to be enabled or disabled formonitoring by the TSM KM

Configuration> ClientStatus

Accesses the individual configuration for determining client status for theselected client instance.By default, the global TSMClientState to TSMClientStatus mapping rule is used,as configured at the container level. Select [default] to revert to the client statusmapping rule configured at the global/container level.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSM_DAEMON_CONTAINERIcon

Parameters


BPPM Type

TSMDaemonDetails Set by TSMDaemonCollector,displays all data returned to thestandard out from commandsexecuted by the data collector.

n/a None n/a

TSMDaemonCollectorExecTime

Inactive standard parametermonitors the collector executiontime. To activate this parameter,use the PSL below, and restartthe PATROL Agent:


"/Runtime/TSM/

TSMDeamonsCollectorExecT

ime", 1);

When activated it will run everyminute and trigger a warningwhen the collector runs for morethan the observed maximumtime. This maximum time can beoverridden by a preset value(example: 3600 seconds), usingthe PSL below:


"/Runtime/TSM/

NBUDaemonCollectorWarn",

3600);

Seconds Warning > presetvalue orobservedmaximum(default)

CollectionStatus

InfoBox

Name Description





Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2



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 theTSM KM.By default, the following daemons are monitored.

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

Configuration > Daemons Status

Accesses the global configuration for determining the daemon status formonitored daemon instances.By default, the following TSMDaemonState to TSMDaemonStatus mapping ruleis used:

Select [default] to reset to the default mapping rule.

TSM_DAEMONIcon


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Parameters


BPPM Type

TSMDaemonCPUDuration

Set by TSMDaemonCollector.Displays the CPU secondsconsumed by the daemon.

Seconds None Statistics

TSMDaemonCPUUtilization*

Set by TSMDaemonCollector.Displays the CPU seconds used bythe daemon.

Percentage (%)

None Statistics

TSMDaemonMemorySize*

Set by TSMDaemonCollector.Displays the core image size of thedaemon in the virtual memory.

Kilobytes(KB)

None Statistics

TSMDaemonProcessCount

Set by TSMDaemonCollector.Displays the number of daemonprocesses/threads found.

Processes None Statistics

TSMDaemonState Set by TSMDaemonCollector.Displays the state of the daemon asreported in the command executedby the data collector.

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

None Availability

TSMDaemonStatus Set by TSMDaemonCollector.Monitors the status of the daemon.This status is determined by thedaemon status mapping ruledefined in the KM command Configuration > Daemon(s) Status.

0 = OK1 =Suspicious2 = Failure

None Availability


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2


TSMDaemonSummary Set by TSMDaemonCollector.Summarizes the daemoninformation as reported bycommands executed by the datacollector.

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.






Menu Commands


Configuration > Daemon

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

Configuration > Daemons Status

Accesses the individual configuration for determining daemon status for theselected the daemon instance.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

By default, the global TSMDaemonState to TSMDaemonStatus mapping rule isused. Select [default] to revert to the daemon status mapping rule configured atthe global/container level.

TSM_DATABASE_CONTAINERIcon

Parameters


BPPM Type

TSMDatabaseDetails Set by TSMDatabaseCollector.Displays all data returned to thestandard out from commandsexecuted by the data collector.

n/a n/a n/a

InfoBox

Name Description






Menu Commands


Reports > DatabaseBackup Volume History

Reports server database backup volume history for the last 7 days.

Configuration > Databases

Accesses the dialog for specifying which server databases are monitored by theTSM KM.By default, following server databases are monitored.

Type [default] to reset to the default configuration.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSM_DATABASEIcon

Parameters


BPPM Type

TSMDatabaseBackupElapsed*

Set by TSMDatabaseCollector.Displays the elapsed time since thelast successful database backup.

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.

This parameter is only availablefor the server database (db)


TSMDatabaseBufferRequestCount

Set by TSMDatabaseCollector.Displays the cumulative number ofrequests for database pages sincethe buffer pool was last reset (orsince the server was last started).


Count None Statistics

TSMDatabaseCacheHitPercent*

Set by TSMDatabaseCollector.Displays (as a percentage of thetotal number of requests) thenumber of requests for a databasepages that are already in the bufferpool.


Percentage(%)

None Statistics


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSMDatabaseCacheWaitPercent*

Set by TSMDatabaseCollector.Displays (as a percentage of thetotal number of requests) thenumber of requests for databasebuffer pool pages where no pagesare available, because all pages arein use.


Percentage(%)

None Statistics

TSMDatabaseFSSpaceUsedPercent*

Set by TSMDatabaseCollector.Monitors the percentage of spaceused by the file system where thedatabase resides.If this parameter changes towarning or alarm state, the recoveryaction will trigger an event.


Percentage(%)

Warning =95-98 Alarm > 98

Statistics

TSMDatabaseLogConsumedSize

Set by TSMDatabaseCollector.Displays the cumulativeconsumption of log space used bythe server since the last reset of this

parameter.


Megabytes(MB)

None Statistics

TSMDatabaseLogPoolUsedPercent*

Set by TSMDatabaseCollector.Displays (as a percentage of allrecovery log buffer pool pages) thenumber of buffer pool pages used towrite changes to the recovery logafter a transaction is committed.


Percentage(%)

None Statistics

TSMDatabaseLogPoolWaitPercent*

Set by TSMDatabaseCollector.Displays (as a percentage of allrecovery log buffer pool requests)the number of requests for bufferpool pages where no pages areavailable because all pages are in

use.

Percentage(%)

None Statistics


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2


TSMDatabasePoolHitPercent*

Set by TSMDatabaseCollector.Displays (as a percentage of thetotal number of requests) thenumber of requests for databasepages that are already in the bufferpool.

This parameter is onlyavailable for the serverdatabase (db).

Percentage(%)

None

TSMDatabaseReorgElapsed*

Set by TSMDatabaseCollector.Displays the elapsed time since thelast database reorganization. Thespecified 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.

This parameter is only availablefor the server database (db).


TSMDatabaseSpaceAvailable

Set by TSMDatabaseCollector.Monitors the amount of assignedspace remaining available for useby the server database.

If this parameter changes towarning or alarm state, the recoveryaction will trigger an event.

The name of this parametershould not be confused with theTSM terminology "AvailableSpace" reported in the InfoBox,which is the total volume spacemade available to the serverdatabase

Megabytes(MB)

Warning =2-5Alarm < 2

Availability

TSMDatabaseSpaceChanged

Set by TSMDatabaseCollector.Displays the database pages (inmegabytes) that have changed sincethe last backup.

Megabytes(MB)

None Statistics


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2


TSMDatabaseSpaceChangedPercent*

Set by TSMDatabaseCollector.Displays the percentage of databasepages that have changed since thelast backup.


Percentage(%)

None Statistics

TSMDatabaseSpaceGrowthRate

Set by TSMDatabaseCollector.Displays the growth rate of thespace used by the server database.

Megabytesper second(MB/s)

None Statistics

TSMDatabaseSpaceMaxExtension

Set by TSMDatabaseCollector.Displays the maximum amount thedatabase can be extended by.

Megabytes(MB)

None Statistics

TSMDatabaseSpaceMaxReduction

Set by TSMDatabaseCollector.Displays the maximum amount thedatabase can be reduced by.

Megabytes(MB)


Statistics

TSMDatabaseSpaceUsed

Set by TSMDatabaseCollector.Displays the amount of assignedspace used by the server database.

Megabytes(MB)

None Statistics

TSMDatabaseSpaceUsedPercent*

Set by TSMDatabaseCollector.Monitors the percentage of assignedspace used by the server database.If this parameter changes towarning or alarm state, the recoveryaction will trigger an event.

The total assigned space is theused space(TSMDatabaseSpaceUsed) plusthe available space(TSMDatabaseSpaceAvailable).

Percentage(%)

None Statistics

TSMDatabaseSummary Set by TSMDatabaseCollector.Summarizes the databaseinformation as reported bycommands executed by the datacollector.

n/a n/a n/a



InfoBox


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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 pathof the database.

Available Space Amount of space made available as volumes for the server database, inmegabytes.

Assigned Space Amount of the Available Space assigned as the server database, in megabytes.

Maximum Extension Maximum amount the database can be extended by, in megabytes.

Maximum Reduction Maximum amount the database can be reduced by, in megabytes.

Page Size Page Size, in bytes.

Total Usable Pages Total number of pages available. This will always be a multiple of the AssignedSpace value, by a factor of 256 (1megabyte /256 pages).

Used Pages Total number of pages currently being used.

Percent Utilized Current utilization as a percentage of the Assigned Space.

Maximum PercentUtilized

Maximum occupancy of the database, as a percentage of the Assigned Space. Thisvalue is the highest utilization percentage reached by the database since the lastreset 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 serverdatabase instance.This dialog allows the selected database instance to be enabled or disabled formonitoring by the TSM KM.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSM_LOG_CONTAINERIcon

Parameters


BPPM Type

TSMLogDetails Set by TSMLogCollector. Displays alldata returned to the standard outfrom commands executed by thedata collector.

n/a n/a n/a

InfoBox

Name Description







Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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 theTSM KM.By default, the following log files are monitored.


Configuration > LogsFilter

Accesses the global configuration of the filter for error expressions inmonitored log file instances.By default, following error messages are looked for in each log file. If detected,they are added to appropriate text parameter:


Configuration > LogsScan Limit

Accesses the global configuration of the data scanning limit for monitored logfile instances.By default, the log collector only scans 5KBytes of new log data for eachmonitored log file during each data collection cycle.

Configuration > LogsAlert Acknowledgement

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


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSM_LOGIcon

Parameters


BPPM Type

TSMLogAlarmCount* Set by TSMLogCollector. Monitorsthe number alarm messages set inthe parameter TSMLogAlarmText.

If this parameter changes to alarmstate, the recovery action willtrigger an event.

Count Alarm ≥ 1 Statistics

TSMLogAlarmText Set by TSMLogCollector. Displaysall alarm messages in the log filewhich have not beenacknowledged. The filter used bythe data collector to determinealarm messages can becustomized using the KMcommand Configuration > Log(s)Filter.

These alarm messages can beacknowledged automatically(default) or manually, dependingon the configuration in the KMcommand Configuration > Log(s)Alert Acknowledgement. Manualacknowledgement is availableunder the KM sub-menuAcknowledgement.

n/a None n/a

TSMLogFSSpaceUsedPercent*

Set by TSMLogCollector. Monitorsthe percentage of space used bythe file system (where the log fileresides).If this parameter changes towarning or alarm state, therecovery action will trigger anevent.

Percentage(%)

Warning =95-98Alarm > 98

Statistics


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

This parameter is notavailable for the activity log(actlog).

TSMLogSpaceAvailable Set by TSMLogCollector. Monitorsthe available space for the log fileto use (this is also the availablespace on the file system).If this parameter changes towarning or alarm state, therecovery action will trigger an

event.


Megabytes(MB)


Availability

TSMLogSpaceGrowthRate

Set by TSMLogCollector. Displaysthe growth rate of the amount ofspace used by the log file.


Kilobytesper second(KB/s)

None Statistics

TSMLogSpaceUsed Set by TSMLogCollector. Displaysthe amount of space used by thelog file.


Kilobytes(KB)

None Statistics

TSMLogSpaceUsedPercent*

Set by TSMLogCollector. Monitorsthe percentage of capacity used bythe log file.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.

The total capacity is the usedspace (TSMLogSpaceUsed)plus available space(TSMLogSpaceAvailable). This parameter is notavailable for the activity log(actlog).

Percentage(%)

Warning =95-98Alarm > 98

Statistics


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSMLogSummary Set by TSMLogCollector.Summarizes the log fileinformation as reported bycommands executed by the datacollector

n/a n/a n/a

TSMLogText Set by TSMLogCollector. Displaysall log text scanned by the datacollector during the last collectioncycle. The size of the data scannedby the data collector is configuredin the KM command Configuration> Log(s) Scan Limit.

n/a n/a n/a

TSMLogWarningCount* Set by TSMLogCollector. Monitorsthe number warning messages setin the parameter TSMLogWarningText.If this parameter changes to awarning state, the recovery actionwill trigger an event

Count Warning > 1 Statistics

TSMLogWarningText Set by TSMLogCollector. Displaysall warning messages in the logfile which have not beenacknowledged. The filter used bythe data collector to determinewarning messages can becustomized using the KMcommand Configuration > Log(s)Filter.

These warning messages can beacknowledged automatically(default) or manually, dependingon the configuration in the KMcommand Configuration > Log(s)Alert Acknowledgement. Manualacknowledgement is availableunder the KM sub-menuAcknowledgement

n/a n/a n/a



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) orthe full file path of the log file.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Log File ModificationTime

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 messagesdetected in the log file and sent to the text parameter TSMLogWarningText.

Acknowledgement > Alarms

Allows acknowledgement of alarm alerts on the selected log file instance.This dialog allows selective acknowledgement of "failure" error messagesdetected in the log file and sent to the text parameter TSMLogAlarmText.

Acknowledgement > All Allows acknowledgement of all warning and alarm alerts on the selected log fileinstance.This dialog allows acknowledgement of all error messages detected in the logfile and sent to the text parameter TSMLogWarningText or TSMLogAlarmText.

Configuration > Log Accesses the individual configuration for monitoring the selected log fileinstance.This dialog allows the selected log file instance to enabled or disabled formonitoring by the TSM KM.

Configuration > LogFilter

Accesses the individual configuration of the log error filter for the selected logfile 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 > LogScan Limit

Accesses the individual configuration of the data scanning limit for the selectedlog file instance.By default, the global log file scanning limit is used, as configured at thecontainer level.

Configuration > LogAlert Acknowledgement

Accesses the individual configuration of the method of acknowledgement foralerts on the selected log file instance.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

By default, the global method of log error acknowledgement is used, asconfigured at the container level.

TSM_POLICY_CONTAINERIcon

Parameters


BPPM Type

TSMDomainDetails Set by TSMPolicyCollector. Displaysall data returned to the standardout from commands executed bythe data collector.

n/a n/a n/a

InfoBox

Name Description







Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Menu Commands


Configuration > Domains

Accesses the dialog for specifying which domains are to be monitored by theTSM KM.By default, all domains configured on the server are monitored.Type [default] to reset to the default configuration.

Configuration > Domains BackupRestriction

Accesses the global configuration to set a backup restriction window for allmonitored domain instances.By default, backup restriction is disabled.When the backup restriction window is defined and enabled using this menu,and if the domain status mapping rule is configured appropriately, an alert willbe triggered if any backup activity is detected during this restriction window.

Configuration > Domains Status

Accesses the global configuration for determining the domain status for allmonitored domain instances.By default, the following TSMDomainState to TSMDomainStatus mapping rule isused:


Configuration >ClientNodes

Accesses the dialog for specifying which client nodes of the selected domain areto be monitored by the KM.By default, all client nodes of enabled domains are monitored. Type [default]toreset to the default configuration.

TSM_POLICYIcon

Parameters


BPPM Type


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSMDomainBackupElapsed*

Set by TSMDomainCollector.Displays the elapsed time since thelast backup for this domain,regardless of completion status ofthe backup. This last backup isdetermined from the monitoredjobs 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, therecovery action will trigger anevent.


TSMDomainBackupSummary

Set by TSMDomainCollector.Summarizes the last backup for thisdomain

n/a n/a n/a

TSMDomainBackupThroughput*

Set by TSMDomainCollector.Displays the throughput of the lastsuccessful backup for this domain.

Gigabytesper second(GB/s)

None Statistics

TSMDomainFullBackupDuration

Set by TSMDomainCollector.Displays the duration of the lastsuccessful full backup for thisdomain.


TSMDomainFullBackupElapsed*

Set by TSMDomainCollector.Displays the elapsed time since thelast successful full backup for thisdomain. This last backup isdetermined from the monitoredjobs 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, therecovery action will trigger anevent.


TSMDomainFullBackupObjectCount

Set by TSMDomainCollector.Displays the number of objectsbacked up in the last successful fullbackup for this domain.


TSMDomainFullBackupSize

Set by TSMDomainCollector.Displays the size of the lastsuccessful full backup for thisdomain.

Gigabytes(GB)

None Statistics


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSMDomainIncrBackupDuration

Set by TSMDomainCollector.Displays the duration of the lastsuccessful incremental backup forthis domain.


TSMDomainIncrBackupElapsed*

Set by TSMDomainCollector.Displays the elapsed time since thelast successful incremental backupfor this domain. This last backup isdetermined from the monitoredjobs 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, therecovery action will trigger anevent.


TSMDomainIncrBackupObjectCount

Set by TSMDomainCollector.Displays the number of objectsbacked up in the last successfulincremental backup for thisdomain.


TSMDomainIncrBackupSize

Set by TSMDomainCollector.Displays the size of the lastsuccessful incremental backup forthis domain.

Gigabytes(GB)

None Statistics

TSMDomainState Set by TSMDomainCollector.Displays the state of the domain.If a backup restriction window isdefined in the KM commandConfiguration > Domain(s) BackupRestriction, this parameter will beset to Running in RestrictedWindow if there is any activityduring the specified period.

0 = Idle1 =Running2 =Running inRestrictedWindow3 = NotStarted4 =Inactive-1 =Unknown

None Availability

TSMDomainStatus Set by TSMDomainCollector.Monitors the status of the domain.This status is determined by thedomain status mapping ruledefined in the KM command Configuration > Domain(s) Status.If this status parameter changes towarning or alarm state, therecovery action will trigger an eventand annotate the last data point.


None Availability


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSMDomainSuccBackupElapsed*

Set by TSMDomainCollector.Displays the elapsed time since thelast successful backup for thisdomain. This last backup isdetermined from the monitoredjobs 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, therecovery action will trigger anevent.


TSMDomainSummary Set by TSMDomainCollector.Summarizes the domaininformation as reported bycommands executed by the datacollector.

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 RegisteredNodes

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

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.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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

Last Incr Backup End Date & time at the completion of the last successful incremental backup for thedomain.

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 ScheduleName

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






Menu Commands


Reports > DomainSchedule

Displays the schedule for the selected domain instance for the next 24 hours.

Configuration > Domain Accesses the individual configuration for monitoring the selected domaininstance.This dialog allows the selected domain instance to be enabled or disabled formonitoring by the TSM KM.

Configuration > DomainBackup Restriction

Accesses the individual configuration for the backup restriction window for theselected domain instance.By default, the global backup restriction window setting is used, as configuredat the container level.

Configuration > DomainStatus

Accesses the individual configuration for determining domain status for theselected domain instance.By default, the global TSMDomainState to TSMDomainStatus mapping rule isused, as configured at the container level. Select [default] to revert to thedomain status mapping rule configured at the global/ container level.

Configuration > ClientNodes

Accesses the dialog for specifying which client nodes of the selected domainare to be monitored by the TSM KM.By default, all client nodes of enabled domains are monitored. Type [default] toreset to the default configuration.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSM_PCLIENTIcon

Parameters


BPPM Type

TSMNodeBackupSummary

Set by TSMDomainCollector.Summarizes the last backup for thisclient node.

n/a n/a n/a

TSMNodeBackupThroughput*

Set by TSMDomainCollector.Displays the throughput of the lastsuccessful backup for this clientnode.

Megabytes persecond(MB/s)

None Statistics

TSMNodeFullBackupDuration

Set by TSMDomainCollector.Displays the duration of the lastsuccessful full backup for thisclient node.


TSMNodeFullBackupObjectCount

Set by TSMDomainCollector.Displays the number of objectsbacked up in the last successful fullbackup for this client node.


TSMNodeFullBackupSize*

Set by TSMDomainCollector.Displays the size of the lastsuccessful full backup for thisclient node.

Megabytes (MB)

None Statistics

TSMNodeIncrBackupDuration

Set by TSMDomainCollector.Displays the duration of the lastsuccessful incremental backup forthis client node.


TSMNodeIncrBackupObjectCount

Set by TSMDomainCollector.Displays the number of objectsbacked up in the last successfulincremental backup for this clientnode.


TSMNodeIncrBackupSize*

Set by TSMDomainCollector.Displays the size of the lastsuccessful incremental backup forthis client node.

Megabytes (MB)

None Statistics


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSMNodeSummary Set by TSMDomainCollector.Summarizes the client nodeinformation as reported bycommands executed by the datacollector.

n/a n/a n/a

TSMObjectExcludeList Set by TSMDomainCollector. Lists allobjects and file systems excludedfrom backup for this client node.

n/a n/a n/a

TSMObjectIncludeList Set by TSMDomainCollector. Lists allobjects and file systems includedfor backup 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 clientnode.

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

Last Incr Backup EndTime

Date & time at the completion of the last successful incremental backup for theclient 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.



Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2





Menu Commands


Configuration > ClientNode

Accesses the individual configuration for monitoring the selected client nodeinstance.This dialog allows the selected client node instance to be enabled or disabledfor monitoring by the TSM KM.

TSM_JOB_CONTAINERIcon

Parameters


BPPM Type

TSMJobActiveBackupCount*

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

count none Statistics

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


TSMJobActiveNonBackupCount*

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


TSMJobDetails Set by TSMJobCollector. Displays alldata returned to the standard outfrom commands executed by thedata collector.

n/a n/a n/a




Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

InfoBox

Name Description







Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Menu Commands

KM Command Action

Force Full Collection Allows the user to force the data collector for jobs to perform a full discoveryduring the next collection cycle.


Allows acknowledgement of warning alerts occurring on any monitored jobinstance.This dialog allows acknowledgement of any job in a "suspicious" state (whichsets the parameter TSMJobStatus to Warning).


Allows acknowledgement of alarms occurring on any monitored job instance.This dialog allows acknowledgement of any job in a "failure" state (which setsthe parameter TSMJobStatus to Alarm).

Acknowledgement > All Allows acknowledgement of all warnings and alarms occurring on anymonitored job instance.This dialog allows acknowledgement of any job in a "suspicious" or "failure"state (which sets the parameter TSMJobStatus to Warning or Alarm,respectively).

Configuration> Jobs Accesses the dialog for specifying which jobs are to be monitored by the TSMKM.By default, all scheduled jobs on the server are monitored according to thefollowing conditions:

The age of a job is calculated from the job start time. The status of a job isdetermined by the state of the job (from the parameter TSMJobState) and the jobstatus mapping rule, described below.

Configuration> JobsStatus

Accesses the configuration for determining the status for all monitored jobinstances.By default, the following TSMJobState to TSMJobStatus mapping rule is used:

Select [default] to reset to the default job status mapping rule.

Configuration> JobsAlert Acknowledgement

Accesses the global configuration of the method of acknowledgement for alertson monitored job instances.By default, the job alerts are manually acknowledged. Using this menu you canchange this so the job collector automatically acknowledges previous job alerts(warnings or alarms) when it detects new errors.Refer to the User Guide for Tivoli Storage Manager KM for PATROL for moredetails.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSM_JOBIcon

Parameters


BPPM Type

TSMJobDuration Set by TSMJobCollector. Displaysthe duration of the job from thestart.


TSMJobErrorCount* Set by TSMJobCollector. Monitorsthe number of client node errorslogged in the server activity logduring this job.

The default settings for thisparameter dictate that whenany error is detected during ajob, this parameter is alwaysset to warning state. And therecovery action will trigger anevent.

Count Warningwhen > 100

Statistics

TSMJobNetworkThroughput*

Set by TSMJobCollector. Displaysthe throughput of the job on thenetwork.


None Statistics

TSMJobSize Set by TSMJobCollector. Displaysthe amount of data backed up forthe job.

Megabytes(MB)

None Statistics


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSMJobState Set by TSMJobCollector. Displaysthe state of the job. This isdetermined using the event statusand 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. Monitorsthe status of the job. This status isdetermined by the job statusmapping rule defined in the KMcommand Configuration > JobsStatus.If this status parameter changes towarning or alarm state, therecovery action will trigger anevent and annotate the last datapoint.



Availability

TSMJobSummary Set by TSMJobCollector.Summarizes the job information asreported by commands executed bythe data collector.

n/a None n/a

TSMJobText Set by TSMJobCollector. Displaysall reported messages related tothis job.

n/a None n/a

TSMJobThroughput* Set by TSMJobCollector. Displaysthe throughput of the job.


None Statistics

TSMObjectCount Set by TSMJobCollector. Displaysthe number of objects inspected forthis job.



Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSMObjectExpiredCount

Set by TSMJobCollector. Displaysthe total number of objects for thisjob that have expired.


TSMObjectFailedCount

Set by TSMJobCollector. Displaysthe total number of objects for thisjob that have failed.If this parameter changes to awarning state, the recovery actionwill trigger an event.

Count Warningwhen > 100

Statistics

TSMObjectProcessedCount

Set by TSMJobCollector. Displaysthe total number of objects for thisjob that have been processed.


TSMObjectReboundCount

Set by TSMJobCollector. Displaysthe total number of objects for thisjob that have been rebound.


TSMObjectUpdatedCount

Set by TSMJobCollector. Displaysthe total number of objects for thisjob that have been updated.




InfoBox

Name Description

Job Identifier assigned to the job by TSM KM (<Domain Name>:<Client Node Name>@ <Job Start Time>).

Type Type of the job.

Mode Mode of the job (such as Incremental or Full).

Schedule Name of the schedule used by the job.

Action Action performed by the schedule.

Status Status of the job as determined by the TSM KM.

Event Status Status of the event.

Result Result of the event.

Reason Additional text depending on the Event Status and Result.

Domain Name Name of the domain this job is assigned to.

Node Name Name of the client node this job is assigned to.

Scheduled Start Date & time that the job was scheduled to start.

Actual Start Date & time that the job actually started.

Completed Date & time at the completion of the job.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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.

Data Transfer Time Time taken for the data transfer.

Network Data TransferRate

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 withthe last similar successful job for the same domain, client node, and mode.

Time Remaining Remaining time of the job in comparison with the last similar successful job.

Session Numbers List of sessions opened on the client node by the job (sessions are listed bynumber).

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



Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Acknowledgement > Alert

Allows acknowledgement of all warnings and alarms occurring on the selectedjob instance.This dialog allows acknowledgement if the selected job instance is in a"suspicious" or "failure" state (which sets the parameter TSMJobStatus toWarning or Alarm, respectively).


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSM_MOUNT_CONTAINERIcon

Parameters


BPPM Type

TSMRequestDetails Set by TSMRequestCollector.Displays all data returned to thestandard out from commandsexecuted by the data collector.

n/a n/a n/a

InfoBox

Name Description






Menu Commands


Administration > Cancel All

Assigns all current mount requests to be canceled.

Reports > PendingMount Requests

Reports a list of all pending mount requests.

Configuration > MountRequests

Accesses the dialog for specifying which mount requests are to be monitored bythe TSM KM.By default, all mount requests are monitored for 1 day from the time they areissued.

Configuration > MountRequests Status

Accesses the configuration for determining the status for all monitored mountrequest instances.By default, the following TSMRequestState to TSMRequestStatus mapping rule isused:


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Select [default] to reset to the default mount request status mapping rule.

TSM_MOUNTIcon

Parameters


BPPM Type

TSMRequestElapsed* Set by TSMRequestCollector.Displays the elapsed time sincethe mount request was issued.

Minutes None Statistics

TSMRequestState Set by TSMRequestCollector.Displays the state of the mountrequest as reported in thecommand executed by the datacollector.

0 =Completed1 = Pending-1 = Unknown

None Availability

TSMRequestStatus Set by TSMRequestCollector.Monitors the status of the mountrequest. This status is determinedby the mount request statusmapping rule defined in the KMcommand Configuration > MountRequest(s) Status.




Availability

TSMRequestSummary Set by TSMRequestCollector.Summarizes the mount requestinformation as reported bycommands executed by the datacollector.

n/a n/a

TSMRequestTimeout* Set by TSMRequestCollector.Displays the time remaining untilthe mount request times out.

Minutes Alarm = 0-30

Statistics


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

If the alert state changes to alarmstate, the recovery action willtrigger an event.



InfoBox

Name Description

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

Description Full detail of the mount request.

Job Type Type of job the mount request belongs to (Backup or Restore).

Mode Mode of the mount request (Read, Write or both).

Volume Requested volume name.

Volume Type Type of the requested volume.

Drive Name Name of the drive the mount request is assigned to.

Library Name Name of the library the mount request is assigned to.

Server Name Name of the server or storage agent the library is connected to.

Request Time Date & time that the mount request was detected.

Request Timeout Time remaining until the mount request times out.

Reply Required Whether a reply is required for the mount request (Yes or No).






Menu Commands

KM Command Action

Administration > Reply

Allows a reply to be sent for the selected mount request once a requested actionhas been taken.A reply may be required to allow this mount request to continue processing. Thisrequirement is noted in the in the InfoBox item "Reply Required".

Administration > Cancel

Allows the selected mount request to be cancelled.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSM_LIBRARY_CONTAINERIcon

Parameters


BPPM Type

TSMLibraryDetails Set by TSMLibraryCollector.Displays all data returned to thestandard out from commandsexecuted by the data collector.

n/a n/a n/a

InfoBox

Name Description






Menu Commands


Configuration > Automated Libraries

Accesses the dialog for specifying which automated libraries are to bemonitored by the TSM KM.By default, all local and remote automated libraries are monitored for a serverand all local automated libraries are monitored for a storage agent. Type [default] to reset to the default configuration.

Configuration > Automated LibrariesStatus

Accesses the global configuration for determining the status for monitoredautomated library instances.By default, the following TSMLibraryState to TSMLibraryStatus mapping rule isused:


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Select [default] to reset to the default library status mapping rule.

Configuration > Automated LibraryDrives Status

Accesses the dialog for specifying which drives of the selected automated libraryare to be monitored by the KM. By default, all automated library drives aremonitored.

Select [default] to reset to the default drive status mapping rule.

TSM_LIBRARYIcon

Parameters


BPPM Type

TSMLibraryState Set by TSMLibraryCollector.Displays whether the path for theautomated library is online oroffline. It will not perform anyremote automated library testcommand on the storage agent.

0 = Online1 = Offline2 = PathOffline-1 =Unknown

None Availability

TSMLibraryStatus Set by TSMLibraryCollector.Monitors the status of theautomated library. This status isdetermined by the automatedlibrary status mapping ruledefined in the KM command Configuration > AutomatedLibrary (Libraries) Status.


0 = OK1 =Suspicious 2 = Failure


Availability


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSMLibrarySummary Set by TSMLibraryCollector.Summarizes the automated libraryinformation as reported bycommands executed by the datacollector.

n/a n/a n/a

TSMLibraryUpDriveCount

Set by TSMLibraryCollector.Displays the number up / onlinestate drives in this robotic library.

If this parameter changes towarning or alarm state, therecovery action will trigger anevent.


TSMLibraryVolumeCount

Set by TSMLibraryCollector.Displays the total number ofvolume loaded in this automatedlibrary.


TSMLibraryVolumePrivateCount

Set by TSMLibraryCollector.Displays the number of privatevolumes in the automated library.


TSMLibraryVolumeScratchCount

Set by TSMLibraryCollector.Displays the number of scratchvolumes in the automated library.


TSMLibraryVolumeScratchPercent*

Set by TSMLibraryCollector.Monitors the percentage ofscratch volume against the totalnumber of volume loaded in thisautomated library.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.

Percentage(%)

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.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

External Manager Name of the external server responsible for controlling access to libraryresources.

Primary LibraryManager

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 (Yesor 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 classassociated with this external library.

Serial Number Serial number of the automated library.

World Wide Name World Wide Name of the port the automated library is attached to.

ACS Id Number of this STK library assigned by the ACSSA (Automatic Cartridge System,System Administrator). This can be a number from 1 to 64.

Private Category Category number for private volumes.

Scratch Category Category number for scratch volumes.






Menu Commands


Reports > AutomatedLibrary Contents

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

Configuration > Automated Library

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

Configuration > Automated LibraryStatus

Accesses the individual configuration for determining the status for the selectedautomated library instance.By default, the global TSMLibraryState to TSMLibraryStatus mapping rule is used,as configured at the container level. Select [default] to revert to the library statusmapping rule configured at the global/container level.

Configuration > Automated LibraryDrives

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


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Configuration > Automated LibraryDrives Status

Accesses the configuration for determining status for monitored drive instanceson the selected automated library instance.By default, the global TSMLDriveState to TSMLDriveStatus mapping rule is used,as configured at the container level. Select [default] to revert to the drive statusmapping rule configured at the global/container level.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSM_LDEVICEIcon

Parameters


BPPM Type

TSMLDriveState Set by TSMLibraryCollector. Displaysthe state of the automated librarydrive. This is determined from theautomated library drive controlinformation.

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

None Availability

TSMLDriveStatus Set by TSMLibraryCollector.Monitors the status of theautomated library drive. This statusis determined by the automatedlibrary drive status mapping ruledefined in the KM command Configuration > Automated LibraryDrive(s) Status.

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



Availability

TSMLDriveSummary Set by TSMLibraryCollector.Summarizes the automated librarydrive information as reported bycommands executed by the datacollector.

n/a n/a n/a

InfoBox


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Name Description

Name Name of the automated library drive.

Description Description of the drive.

Device Device path of the drive.

Type Volume type used in the drive.

Server Name Name of the remote host where the drive is connected.

Node Name Name of the node that the drive is assigned to.

External Manager Name of the external server responsible for controlling access to driveresources.

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 usesthe element address to connect the physical location of the drive to SCSI addressof 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.


Allows the selected automated library drive to be brought online.


Allows the selected automated library drive to be taken offline.

Configuration > Automated LibraryDrive

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


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Configuration > Automated LibraryDrive Status

Accesses the individual configuration for determining the drive status for theselected automated library drive instance.By default, the TSMLDriveState to TSMLDriveStatus mapping rule configured atthe parent level is used. (Note that if the mapping rule has not been modified forthe parent automated library, then the default is the global mapping ruleconfigured at the container level.) Select [default] to revert to the drive statusmapping rule configured at the parent instance level.

TSM_DEVICE_CONTAINERIcon

Parameters


BPPM Type

TSMDriveDetails Set by TSMDeviceCollector. Displaysall data returned to standard outfrom commands executed by thedata collector.

n/a n/a n/a

InfoBox

Name Description






Menu Commands


Configuration > Manual Drives

Accesses the dialog for specifying which manual drives are to be monitored bythe TSM KM.By default, all local and remote manual drives are monitored for a server and alllocal manual drives are monitored for a storage agent. Type [default] to reset tothe default configuration.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Configuration > Manual Drives Status

Accesses the global configuration for determining the status for monitoredmanual drive instances.By default, the following TSMDriveState to TSMDriveStatus mapping rule is used:

Select [default] to reset to the default manual drive status mapping rule.

TSM_DEVICEIcon

Parameters


BPPM Type

TSMDriveState Set by TSMDriveCollector. Displaysthe state of the manual drive. Thisis determined from the manualdrive control 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 manualdrive status mapping rule definedin the KM command Configuration >Manual Drive(s) Status.



Availability


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2


TSMDriveSummary Set by TSMDriveCollector.Summarizes the manual driveinformation as reported bycommands 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.

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

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 serveruses the element address to connect the physical location of the drive to SCSIaddress 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.







Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Menu Commands


Administration > CleanDrive

Allows the selected manual library drive to be cleaned.


Allows the selected manual library drive to be brought online.


Allows the selected manual library drive to be taken offline.

Configuration > ManualDrive

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

Configuration > ManualDrive Status

Accesses the individual configuration for determining the manual drive statusfor the selected manual 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 statusmapping rule configured at the global/container level.

TSM_POOL_CONTAINERIcon

Parameters


BPPM Type

TSMPoolDetails Set by TSMPoolCollector. Displaysall data returned to the standardout from commands executed by thedata collector.

n/a n/a n/a

InfoBox

Name Description





Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2



Menu Commands


Configuration > VolumePools

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


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSM_POOLIcon

Parameters


BPPM Type

TSMPoolSpaceAvailable*

Set by TSMPoolCollector. Monitorsthe available volume space for thebackup data to use in this storagepool.

If this parameter changes towarning or alarm state, therecovery action will trigger anevent.

Gigabytes(GB)

Warning < 1Alarm = 0

Availability

TSMPoolSpaceGrowthRate

Set by TSMPoolCollector. Displaysthe growth rate of the total volumespace used by the backup data inthis storage pool.

Gigabytesper second(GB/s)

None Statistics

TSMPoolSpaceLogicalPercent*

Set by TSMPoolCollector. Displaysthe logical occupancy of thestorage pool as a percentage of thetotal occupancy.

Percentage(%)

None Statistics

TSMPoolSpaceMigrated*

Set by TSMPoolCollector. Displaysthe amount of data that has beenmigrated, if migration is inprogress. If migration is not inprogress, this value indicates theamount of data migrated during thelast migration.Note: This parameter is notavailable for copy storage pools.

Gigabytes(GB)

None Statistics

TSMPoolSpaceMigratedPercent*

Set by TSMPoolCollector. Displaysan estimate of the percentage ofdata in the storage pool that can bemigrated.Note: This parameter is notavailable for copy storage pools.

Percentage(%)

None Statistics


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSMPoolSpaceMigrationElapsed

Set by TSMPoolCollector. Displaysthe amount of time that haselapsed since migration of thestorage pool began, if migration isactive. If migration is not active,this value indicates the amount oftime required to complete the lastmigration.Note: This parameter is notavailable for copy storage pools.


TSMPoolSpaceReclaimable*

Set by TSMPoolCollector. Displaysthe amount of space in the storagepool that is reclaimable.

Gigabytes(GB)

None Statistics

TSMPoolSpaceReclaimablePercent*

Set by TSMPoolCollector. Displaysthe amount of reclaimable spaceas a percentage of the total storagepool space.

Percentage(%)

None Statistics

TSMPoolSpaceUsed* Set by TSMPoolCollector. Displaysthe total volume space occupied bythe backup data in this storagepool.

Gigabytes(GB)

None Statistics

TSMPoolSpaceUsedPercent*

Set by TSMPoolCollector. Monitorsthe percentage of total occupiedvolume space against the totalvolume capacity of this storagepool (not including any scratchvolumes).If this parameter changes towarning or alarm state, therecovery action will trigger anevent.

Percentage(%)

Warning > 95Alarm > 98

Statistics

TSMPoolSummary Set by TSMPoolCollector.Summarizes the storage poolinformation as reported bycommands executed by the datacollector.

n/a n/a n/a

TSMVolumeActiveCount

Set by TSMPoolCollector. Displaysthe number of active volumes inthis storage pool. (Active volumesare available disk volumes with astatus of "Online" or tape volumeswith a status of "Filling", wheredata has been written but thevolume is not yet full.)


TSMVolumeActivePercent*

Set by TSMPoolCollector. Monitorsthe percentage of active volumesagainst the total number ofvolumes in this storage pool.If the status of the parameterchanges to warning or alarm state,the recovery action will trigger anevent.

Percentage(%)

None Statistics


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSMVolumeAvailableCount

Set by TSMPoolCollector. Displaysthe number of volumes assigned tothis storage pool.


TSMVolumeAvailablePercent*

Set by TSMPoolCollector. Monitorsthe percentage of availablevolumes against the total numberof volumes in this storage pool.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.

Percentage(%)

None Statistics

TSMVolumeCount Set by TSMPoolCollector. Displaysthe total number of volumes in thisstorage pool.


TSMVolumeEmptyCount

Set by TSMPoolCollector. Displaysthe number of empty volumes inthis storage pool. ("Empty" is apossible status for a tape volume,indicating that no data is stored onthat volume)


TSMVolumeFullCount

Set by TSMPoolCollector. Displaysthe number of full volumes in thisstorage pool. ("Full" is a possiblestatus for a tape volume.)


TSMVolumeFullPercent*

Set by TSMPoolCollector. Monitorsthe percentage of full volumesagainst the total number ofvolumes in this storage pool.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.

Percentage(%)

None Statistics

TSMVolumeOfflineCount

Set by TSMPoolCollector. Displaysthe number of offline volumes inthis storage pool. ("Offline" is apossible status for a disk volume.)


TSMVolumePendingCount

Set by TSMPoolCollector. Displaysthe number of pending volumes inthis storage pool. ("Pending" is apossible status for a tape volume,where all files have been deletedbut a delay has been placed on thevolume before reuse.)




InfoBox


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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 DataFormat

Type of data format used to write data to this storage pool,For example: NATIVE or NETAPPDUMP.

Maximum ScratchVolumes

Maximum number of scratch volumes that the server can request for the storagepool. (Sequential access storage pools only.)

Migration In Progress Whether at least one migration process is active for the storage pool .

Reclamation InProgress

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 nomigration or reclamation 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 > Storage Pool

Accesses the individual configuration for monitoring the selected storage poolinstance.This dialog allows the selected storage pool instance to be enabled or disabledfor monitoring by the TSM KM.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSM_PROCESS_CONTAINERIcon

Parameters


BPPM Type

TSMProcessDetails Set by TSMProcessCollector.Displays all data returned to thestandard out from commandsexecuted by the data collector.

n/a n/a n/a

InfoBox

Name Description






Menu Commands



Allows acknowledgement of warning alerts occurring on any monitored processinstance.This dialog allows acknowledgement of any process in a "suspicious" state(which sets the parameter TSMProcessStatus to Warning).


Allows acknowledgement of alarms occurring on any monitored processinstance.This dialog allows acknowledgement of any process in a "failure" state (whichsets the parameter TSMProcessStatus to Alarm).

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


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Reports > ActiveProcesses

Reports a list of all active processes on the managed node.

Configuration > Processes

Accesses the dialog for specifying which processes are to be monitored bytheTSM KM.By default, all processes are monitored for 3 days. The age of a process iscalculated from the process start time.

Configuration > Processes Status

Accesses the configuration for determining the status for all monitored processinstances.By default, the following TSMProcessState to TSMProcessStatus mapping rule isused:


TSM_PROCESSIcon

Parameters


BPPM Type

TSMProcessDuration

Set by TSMProcessCollector.Displays the number of secondssince the start of the process.


TSMProcessItemCount*

Set by TSMProcessCollector.Displays the number of itemsprocessed.


TSMProcessSize Set by TSMProcessCollector.Displays the amount of dataprocessed.

Megabytes(MB)

None Statistics

TSMProcessState Set by TSMProcessCollector.Displays the state of the process.This is determined from the processcontrol information.

0 = Running1 =Running/Errors2 =Completed/Success

None Availability


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

3 =Completed/Failure-1 =Unknown

TSMProcessStatus Set by TSMProcessCollector.Monitors the status of the process.This status is determined by theprocess status mapping ruledefined in the KM command Configuration > Processes Status.

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


Warning =1Alarm = 2

Availability

TSMProcessSummary Set by TSMProcessCollector.Summarizes the processinformation as reported bycommands executed by the datacollector.

n/a None n/a

TSMProcessThroughput*

Set by TSMProcessCollector.Displays the throughput of theprocess during the last backupevent.


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.


Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2






Menu Commands


Acknowledgement > Alert

Allows acknowledgement of all warnings and alarms occurring on the selectedprocess instance.This dialog allows acknowledgement if the selected process is in a "suspicious"or "failure" state (which sets the parameter TSMProcessStatus to Warning orAlarm, respectively).

Administration > Cancel Process

Allows the selected process instance to be canceled.

Troubleshooting

158Impact on Resources

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

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 yourTSM KM configuration. As you increase data collection frequency, increase the number ofinstances monitored by the KM or add functionality through customization, your CPU andmemory usage will increase.

When monitoring a standard installation of Tivoli Storage Manager using TSM KM, the PATROLAgent will consume between 5MBytes and 10MBytes of additional system memory. Anenterprise installation of Tivoli Storage Manager Server with multiple Storage Agents, Clients,Automated Libraries, and Manual Drives can consume more memory (as per other KMs used bythe PATROL Agent). The memory usage of TSM KM can be reduced by:

• disabling monitoring unnecessary component instances (by using the configuration menu)

• disabling unwanted components (by setting their instance limits to 0)

• disabling unwanted collectors (by using the PATROL Configuration Manager)

• increasing the collector scheduling interval (by using the PATROL Configuration Manager)

• decreasing the instance limits to limit the number of instances created by the collectors

The data collectors in TSM KM uses Tivoli Storage Manager command line interface to obtainTivoli Storage Manager information. Most of the performance degradation is associated withthese command executions and amount of data returned. It may improve the overallperformance, if the regular 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 iskept on the managed node. The amount of network traffic that it generates depends on thenumber of PATROL Consoles that are connected to the PATROL Agent and the frequency of datacollection.

Additional Information

160Where to Find Additional Help

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Where to Find Additional HelpAdditional 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 followinglocation: http://www.sentrysoftware.com


http://www.tivoli.com/support


161

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Index

- A -Abnormalities 57

Access

Permissions 17

User 17Acknowledge

Alarm 84

Alerts 84

Job Alerts 84

Log Alerts 84

Process Alerts 84

Warning 84Acknowledgement

Configure 76

Job 76

Log 76Adapter 54

Add 55, 56

Create 55

Update 56Admin Interface Login 48

Administer

Library Drives 61

Manual Drives 61

Mount Requests 60Agent

PATROL 48Alarm

Acknowledge 84Alarm Filter State Rules 71

Alert Acknowledgement 76

Configure 76

Job 76

Log 76Alerts

Acknowledge 84Application Clas

TSM_POLICY 119Application Class

TSM_CLIENT 99

TSM_CLIENT_CONTAINER 97

TSM_DAEMON 103

TSM_DAEMON_CONTAINER 102

TSM_DATABASE 107

TSM_DATABASE_CONTAINER 106

TSM_DEVICE 145

TSM_DEVICE_CONTAINER 144

TSM_JOB 129

TSM_LDEVICE 142

TSM_LIBRARY 138

TSM_LIBRARY_CONTAINER 137

TSM_LOG 114

TSM_LOG_CONTAINER 112

TSM_MOUNT 135

TSM_MOUNT_CONTAINER 134

TSM_PCLIENT 124

TSM_POLICY_CONTAINER 118

TSM_POOL 149

TSM_POOL_CONTAINER 147

TSM_PROCESS 154

TSM_PROCESS_CONTAINER 153

TSM_SERVER 90

- B -Baselines

BMC ProactiveNet Performance Management 57

Generation 57

Manage 57

Requirements 57BMC

BMC ProactiveNet Performance ManagementPortal 54

BMC PATROL

Changes 15BMC ProactiveNet

Integration 54BMC ProactiveNet Performance Management

Abnormalities 57

Baselines 57

Key Performance Indicators 57

KPI 57

- C -Cancel

Mount Request 60Changes 8

Check

162

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Check

Instance Limits 51Classes 89

Clean

Drive 61Clients

Delete 65

Disable 65

Enable 65

Status Configuration 71Cluster

Configure 64Clustering Application 64

Commands

Reload 84Configuration

Admin Interface Login 90

Debug 90

Instance Limits 90

Login 90

Monitoring Mode 90

Node Status 90

Node Type 90

Paths 90

Preloading 90Configure

Alert Acknowledgement 76

Cluster 64

Domain Backup Restriction 76

KM User Account 48

Log Error Filter 72

Log Scan Limit 74

Monitoring Period 67

Multi-Node Monitoring Mode 64

Node Type 63

Paths 62

PATROL Agent 46Customize

KM 61

- D -Daemons

Delete 65

Disable 65

Enable 65

Status Configuration 71Data Collectors

Force 79Databases

Delete 65

Disable 65

Enable 65Debug

Disable 81

Enable 81

End 81

Files 81

Path 81Delete

Clients 65

Daemons 65

Databases 65

Logs 65

Policies 65

Policy Clients 65

Robotic Drives 65

Robotic Libraries 65

Standalone Drives 65

Storages 65

Volume Pools 65Disable

Clients 65

Daemons 65

Databases 65

Debug 81

Logs 65

Policies 65

Policy Clients 65

Robotic Drives 65



Storages 65

Volume Pools 65Discoveries

Force 79Discovery

Verify 51Domain Backup Restriction

Configure 76DSM_CONFIG 62

DSM_DIR 62

DSM_LOG 62

163

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

- E -Enable

Clients 65

Daemons 65

Databases 65

Debug 81

Logs 65

Policies 65

Policy Clients 65

Robotic Drives 65



Storages 65

Volume Pools 65

- F -Failover Group Name 64

Files 24

ins_ALL_<version>.tar 22

ins_WINDOWS_<version>.exe 22

Setup 24

setup.exe 26

setup.sh 26

uninstall.exe 39

uninstall.sh 39Filtering Options

Clients 65

Daemons 65

Databases 65

Logs 65

Policies 65

Policy Clients 65

Robotic Drives 65



Storages 65

Volume Pools 65Force

All Data Collectors 79

All Discoveries 79

Full data collection 79

Selected Data Collectors 79Force Discovery 90

- G -Generate

Baselines 57

Reports 86

- H -help 160

- I -Improvement 8

InfoBox

Access 149

ACS Id 138

Action 129

Activated Default Management Class 119

Activated Policy Set 119

Activation Date/Time 119

Actual Start 129

Aggregate Data Transfer Rate 129

Allocated To 142, 145

Application 99

Application Name 90

Application Version 90

Archive Retention 119

Assigned Space 107

Available FS Space 114

Available Space 107

Backup Retention 119

Binary Path 90

Buffer Pool Pages 107

Collector Last End 97, 99, 102, 103, 106,107, 112, 114, 118, 119, 124, 126, 129, 134,135, 137, 138, 142, 144, 145, 147, 149, 153,154

Collector Last Start 97, 102, 103, 106, 107,112, 114, 118, 119, 124, 126, 129, 134, 135,137, 138, 142, 144, 145, 147, 149, 153, 154

Collector Name 97, 99, 102, 103, 106, 107,112, 114, 118, 119, 124, 126, 129, 134, 135,137, 138, 142, 144, 145, 147, 149, 153, 154

Collector Next Start 97, 99, 102, 103, 106,107, 112, 114, 118, 119, 124, 126, 129, 134,135, 137, 138, 142, 144, 145, 147, 149, 153,154

164

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

InfoBox

Collector Status 97, 99, 102, 103, 106,107, 112, 114, 118, 119, 124, 126, 129, 134,135, 137, 138, 142, 144, 145, 147, 149, 153,154

Command 103

Completed 129

Copyright 90

Data Transfer Time 129

Description 99, 103, 107, 114, 119, 124,135, 138, 142, 145, 149

Device 138, 142, 145

Device Class 149

Domain Name 124, 129

Drive Name 135

Drive Online 142, 145

Duration 154

Element 142, 145

End 154

Event Status 129

External Manager 138, 142, 145

FS Percent Used 114

Host Name 90

Installation Path 90

Items 154

Job 129

Job Type 135

Lan Free 138

Last Backup 107

Last Backup Duration 129

Last Backup End 119, 124, 129

Last Backup Job 119, 129

Last Backup Mode 107

Last Backup Objects 129

Last Backup Save Group 124

Last Backup Size 129

Last Backup Start 119, 124, 129

Last Backup Status 119, 124

Last Communication Method 99

Last Full Backup End 119, 124

Last Full Backup Job 119, 124

Last Full Backup Start 119, 124

Last Incr Backup End 119

Last Incr Backup End Time 124

Last Incr Backup Job 119, 124

Last Incr Backup Start 119, 124

Last Message 154

Last Purge 107, 114

Library Name 135, 142, 145

Library Path 90

Log File Modification Time 114

Log File Size 114

Maximum Extension 107

Maximum Percent Utilized 107

Maximum Reduction 107

Maximum Scratch Volumes 149

Migration In Progress 149

Mode 129, 135

Monitoring Mode 90

Monitoring Node 90

Name 99, 103, 107, 114, 119, 124, 138,142, 145, 149

Network Data Transfer Rate 129

Next Backup 119, 124

Next Backup Schedule Name 119, 124

Node Name 129, 138, 142, 145

Node Name(s) 90

Node Type 90

Number of Registered Nodes 119

Obey Mount Retention 138

Objects Compression 129

Objects Deleted 129

Objects Expired 129

Objects Failed 129

Objects Inspected 129

Objects Processed 129

Objects Rebound 129

Objects Updated 129

Operating System 90, 99, 124

Owner 103

Page Size 107

Path 107, 114

Path Online 138, 142, 145

PATROL Agent Version 90

Percent Completed 129

Percent Utilized 107

Physical Volumes 107

PID 103

Platform 90

PPID 103

Primary Library Manager 138

Private Category 138

Process Mode 154

Process Name 154

Process Number 154

Processing Time 129

Product Name 90

Product Release Date 90

165

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

InfoBox

Product Version 90

Reason 129

Reclamation In Progress 149

Reply Required 135

Request ID 135

Request Time 135

Request Timeout 135

Result 129

Schedule 129

Scheduled Start 129

Scratch Category 138

Serial Number 138, 142, 145

Server 90

Server Name 135, 138, 142, 145

Session Numbers 129

Shared 138

Size 129, 154

Start 154

Status 99, 103, 119, 129, 138, 142, 145,154

Storage Pool Data Format 149

Support 90

Time Remaining 129

Time Since Last Communication 99

Total FS Space 114

Total Usable Pages 107

Type 129, 138, 142, 145, 149

Used Pages 107

Version 99

Volume 135

Volume Being Migrated/Reclaimed 149

Volume Type 135

Web Site 90

World Wide Name 138, 142, 145Install / Un-install 26, 39

BMC Software Installation Utility 22

Log 26

Packages 24

Procedure 26

Setup Files 24Installation 62

Instance Limits

Check 51Integration

BMC ProactiveNet 54Integration Service Agent 55

Introduction 26

Issues

Fixed 8

- J -Job Alerts

Acknowledge 84Jobs

Configure 67


Status Configuration 71

- K -Key Performance Indicators


Manage 57KM

Configure 48

Customize 61

Initial Setup 52

Load 45, 46, 54

Preload 46

Preloaded 47, 48

Unload 46, 47, 48

User Account 48KPI


Manage 57

- L -Library Drives

Administer 61

Clean 61

Offline 61

Online 61Load

KM 45, 46, 54

PATROL Central 46Log Alerts

Acknowledge 84Log Error Filter

Configure 72Log Scan Limit

Configure 74Logs

166

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Logs

Delete 65

Disable 65

Enable 65

- M -Manage

Baselines 57

Key Performance Indicators 57

KPI 57Managed Node

Status Configuration 71Manual Drives

Administer 61

Clean 61

Offline 61

Online 61Master Server

Configure 63Media Server

Configure 63Menu Commands

About 90

Acknowledgement 114, 126, 129, 153, 154

Active Processes 153

Activity Log Messages 112

Administration 90, 134, 135, 142, 145, 154

Al 153

Alarms 114, 126, 153

Alert 129, 154

All 114, 126

Automated Libraries 137

Automated Libraries Status 137

Automated Library 138

Automated Library Contents 138

Automated Library Drive 142

Automated Library Drive Status 142

Automated Library Drives 138

Automated Library Drives Status 137, 138

Automated Library Status 138

Cancel 135

Cancel All 134

Cancel Process 154

Clean Drive 142, 145

Client 99

Client Node 124

Client Nodes 119

Client Status 99

Clients 97

Clients Status 97

Configuration 97, 99, 102, 103, 106, 107,112, 118, 119, 124, 126, 134, 137, 138, 142,144, 145, 147, 149, 153

Daemon 103

Daemon List 102

Daemons 102

Daemons Status 102, 103

Database 107

Database Backup Volume History 106

Database Volumes 107

Databases 106

Domain 119

Domain Backup Restriction 119

Domain Schedule 119

Domain Status 119

Domains 118

Domains Backup Restriction 118

Domains Status 118

Force Discovery 90

Force Full Collection 126

Jobs 126

Jobs Alert Acknowledgement 126

Jobs Status 126

KM Status 90

Log 114

Log Alert Acknowledgement 114

Log Filter 114

Log Scan Limit 114

Logs 112

Logs Alert Acknowledgement 112

Logs Filter 112

Logs Scan Limit 112

Manual Drive 145

Manual Drive Status 145

Manual Drives 144

Manual Drives Status 144

Mount Requests 134

Mount Requests Status 134

Offline Drive 142, 145

Online Drive 142, 145

Pending Mount Requests 134

Processes 153

Processes Status 153

Refresh Parameters 90

Refresh Process Cache 90

Reload Commands 90

167

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Menu Commands

Reply 135

Reports 102, 106, 107, 112, 119, 134, 138,149, 153

Start Server 90

Start Storage Agent 90

Stop Server 90

Storage Pool 149

Volume Pools 147

Volumes List 149

Warnings 114, 126, 153Monitor Type 55

Monitoring Period

Configure 67

Jobs 67

Mount Requests 67

Processes 67Mount Requests

Administer 60

Cancel 60

Configure 67


Status Configuration 71Multi-Node Monitoring Mode

Configure 64

- N -New features 8

Node Type

Configure 63

Master Server 63

Media Server 63Notification 60

- O -Offline

Drive 61Online

Drive 61Operating Systems

Linux 22, 24, 26, 39

Unix 22, 24, 39

Windows 22, 24, 26, 39Options

Common services 26

Console Systems role 26

Managed System 26

View Log 26Oracle Solaris Cluster 64

- P -Parameter

TSMLoginStatus 48Parameters 89

ExtraFilesList 90

Refresh 79

TSMClientCollector 90

TSMClientDetails 97

TSMClientLastAccessElapsed 99

TSMClientSpaceUsed 99

TSMClientState 99

TSMClientStatus 99

TSMClientSummary 99

TSMCreateDistribution 90

TSMDaemonCollector 90

TSMDaemonCollectorExecTime 102

TSMDaemonCPUDuration 103

TSMDaemonCPUUtilization 103

TSMDaemonDetails 102

TSMDaemonMemorySize 103

TSMDaemonProcessCount 103

TSMDaemonState 103

TSMDaemonStatus 103

TSMDaemonSummary 103

TSMDatabaseBackupElapsed 107

TSMDatabaseCacheHitPercent 107

TSMDatabaseCacheWaitPercent 107

TSMDatabaseCollector 90

TSMDatabaseDetails 106

TSMDatabaseFSSpaceUsedPercent 107

TSMDatabaseLogConsumedSize 107

TSMDatabaseLogPoolUsedPercent 107

TSMDatabaseLogPoolWaitPercent 107

TSMDatabasePoolHitPercent 107

TSMDatabaseReorgElapsed 107

TSMDatabaseSpaceAvailable 107

TSMDatabaseSpaceChanged 107

TSMDatabaseSpaceChangedPercent 107

TSMDatabaseSpaceGrowthRate 107

TSMDatabaseSpaceMaxExtension 107

TSMDatabaseSpaceMaxReduction 107

TSMDatabaseSpaceUsed 107

TSMDatabaseSpaceUsedPercent 107

168

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Parameters 89

TSMDatabaseSummary 107

TSMDomainBackupElapsed 119

TSMDomainBackupSummary 119

TSMDomainBackupThroughput 119

TSMDomainCollector 90

TSMDomainDetails 118

TSMDomainFullBackupDuration 119

TSMDomainFullBackupElapsed 119

TSMDomainFullBackupObjectCount 119

TSMDomainFullBackupSize 119

TSMDomainIncrBackupDuration 119

TSMDomainIncrBackupElapsed 119

TSMDomainIncrBackupObjectCount 119

TSMDomainIncrBackupSize 119

TSMDomainState 119

TSMDomainStatus 119

TSMDomainSuccBackupElapsed 119

TSMDomainSummary 119

TSMDriveCollector 90

TSMDriveDetails 144

TSMDriveState 145

TSMDriveStatus 145

TSMDriveSummary 145

TSMJobActiveBackupCount 126

TSMJobActiveCount 126

TSMJobActiveNonBackupCount 126

TSMJobCollector 90

TSMJobDetails 126

TSMJobDuration 129

TSMJobErrorCount 129

TSMJobNetworkThroughput 129

TSMJobSize 129

TSMJobState 129

TSMJobStatus 129

TSMJobSummary 129

TSMJobText 129

TSMJobThroughput 129

TSMLDriveState 142

TSMLDriveStatus 142

TSMLDriveSummary 142

TSMLibraryCollector 90

TSMLibraryDetails 137

TSMLibraryState 138

TSMLibraryStatus 138

TSMLibrarySummary 138

TSMLibraryUpDriveCount 138

TSMLibraryVolumeCount 138

TSMLibraryVolumePrivateCount 138

TSMLibraryVolumeScratchCount 138

TSMLibraryVolumeScratchPercent 138

TSMLogAlarmCount 114

TSMLogAlarmText 114

TSMLogCollector 90

TSMLogDetails 112

TSMLogFSSpaceUsedPercent 114

TSMLoginStatus 90

TSMLogSpaceAvailable 114

TSMLogSpaceGrowthRate 114

TSMLogSpaceUsed 114

TSMLogSpaceUsedPercent 114

TSMLogSummary 114

TSMLogText 114

TSMLogWarningCount 114

TSMLogWarningText 114

TSMMonitoringMode 90

TSMNodeBackupSummary 124

TSMNodeBackupThroughput 124

TSMNodeFullBackupDuration 124

TSMNodeFullBackupObjectCount 124

TSMNodeFullBackupSize 124

TSMNodeIncrBackupDuration 124

TSMNodeIncrBackupObjectCount 124

TSMNodeIncrBackupSize 124

TSMNodeStatus 90

TSMNodeSummary 124

TSMObjectCount 129

TSMObjectExcludeList 124

TSMObjectExpiredCount 129

TSMObjectFailedCount 129

TSMObjectIncludeList 124

TSMObjectProcessedCount 129

TSMObjectReboundCount 129

TSMObjectUpdatedCount 129

TSMPoolCollector 90

TSMPoolDetails 147

TSMPoolSpaceAvailable 149

TSMPoolSpaceGrowthRate 149

TSMPoolSpaceLogicalPercent 149

TSMPoolSpaceMigrated 149

TSMPoolSpaceMigratedPercent 149

TSMPoolSpaceMigrationElapsed 149

TSMPoolSpaceReclaimable 149

TSMPoolSpaceReclaimablePercent 149

TSMPoolSpaceUsed 149

TSMPoolSpaceUsedPercent 149

TSMPoolSummary 149

TSMProcessCollector 90

169

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

Parameters 89

TSMProcessDetails 153

TSMProcessDuration 154

TSMProcessItemCount 154

TSMProcessSize 154

TSMProcessState 154

TSMProcessStatus 154

TSMProcessSummary 154

TSMProcessThroughput 154

TSMRequestCollector 90

TSMRequestDetails 134

TSMRequestElapsed 135

TSMRequestState 135

TSMRequestStatus 135

TSMRequestSummary 135

TSMRequestTimeout 135

TSMUpdateAgent 90

TSMVolumeActiveCount 149

TSMVolumeActivePercent 149

TSMVolumeAvailableCount 149

TSMVolumeAvailablePercent 149

TSMVolumeCount 149

TSMVolumeEmptyCount 149

TSMVolumeFullCount 149

TSMVolumeFullPercent 149

TSMVolumeOfflineCount 149

TSMVolumePendingCount 149Paths

Binary 62

DSM_CONFIG 62

DSM_DIR 62

DSM_LOG 62

Installation 62

Library 62PATROL

Agent 48

PATROL Agent 46, 47

PATROL Central Console 46, 48

PATROL Console 46, 47PATROL Agent

Configure 46

Restart 52PATROL Console 45

Restart 52Platform

Upgrade 44Platforms

Unix 48Policies

Delete 65

Disable 65

Enable 65Policy Clients

Delete 65

Disable 65

Enable 65Preload

KM 46Preloaded

KM 47, 48Prepare

Debug Files 81ProactiveNet 55

Process Alerts

Acknowledge 84Processes

Configure 67

Monitoring Period 67PW Commands 56

- R -Refresh

Parameters 79Release Notes 8

Reload

Commands 84remote PATROL Agent Checking 64

Reports

Generate 86Requirements

Security 17

Software 15

System 15Restart

PATROL Agent 52

PATROL Console 52Robotic Drives

Delete 65

Disable 65

Enable 65

Status Configuration 71Robotic Libraries

Delete 65

Disable 65

Enable 65

Status Configuration 71

170

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

- S -Security

Requirements 17Server

Start 60

Stop 60Setup

Check 52

Initial 52

KM 52Software

Requirements 15Standalone Drives

Delete 65

Disable 65

Enable 65

Status Configuration 71Start

Server 60

Storage Agent 60Status Configuration

Clients 71

Daemons 71

Jobs 71

Managed Node 71

Mount Requests 71

Robotic Drives 71


Standalone Drives 71Stop

Server 60

Storage Agent 60Storage Agent

Start 60

Stop 60Storages

Delete 65

Disable 65

Enable 65Sudo 17, 48

System

Requirements 15

- T -Thresholds

Customize 56

Import 56Tivoli Storage Manager

Changes 15TSM_CLIENT

Application Class 99TSM_CLIENT_CONTAINER

Application Class 97TSM_DAEMON

Application Class 103TSM_DAEMON_CONTAINER

Application Class 102TSM_DATABASE

Application Class 107TSM_DATABASE_CONTAINER

Application Class 106TSM_DEVICE

Application Class 145TSM_DEVICE_CONTAINER

Application Class 144TSM_JOB

Application Class 129TSM_LDEVICE

Application Class 142TSM_LIBRARY

Application Class 138TSM_LIBRARY_CONTAINER

Application Class 137TSM_LOG

Application Class 114TSM_LOG_CONTAINER

Application Class 112TSM_MOUNT

Application Class 135TSM_MOUNT_CONTAINER

Application Class 134TSM_PCLIENT

Application Class 124TSM_POLICY

Application Class 119TSM_POLICY_CONTAINER

Application Class 118TSM_POOL

Application Class 149TSM_POOL_CONTAINER

Application Class 147TSM_PROCESS

Application Class 154TSM_PROCESS_CONTAINER

171

Tivo

li St

orag

e M

anag

er

KM f

or

PA

TRO

L V

ersi

on 2

.7.0

2

TSM_PROCESS_CONTAINER

Application Class 153TSM_SERVER

Application Class 90TSMRequestTimeout 60

- U -Unix 48

Unload

KM 46, 47, 48Upgrade

Platform 44

- V -Verify

Application Discovery 51Veritas Cluster File System 64

Veritas Cluster Server 64

Volume Pools

Delete 65

Disable 65

Enable 65

- W -Warning

Acknowledge 84Warning Filter State Rules 71

What's new 8

About Sentry Software™Sentry Software, a strategic Technology Alliance Partner of BMC Software, providescomprehensive multi-platform monitoring solutions that enable management of thehardware and software aspects of all servers and SANs and covering up to 100 % ofcustom applications within the BMC ProactiveNet Performance Managementenvironment. Sentry Software also develops adapters for BMC Atrium Orchestrator thatenables IT administrators to automate the execution of common requests and tasksthat occur in the daily course of IT operations. Combined with BMC’s servers andnetwork automation tools, the adapters allow IT administrators to implementprovisioning and decommissioning workflows that cover all layers of their ITinfrastructure. Finally, Sentry Software designs connectors that bring storage capacitymetrics into BMC TrueSight Capacity Optimization to ensure IT administrators that theirstorage infrastructure is properly sized for their current and future needs.

Like us on Facebook:facebook.com/sentrysoftware

Follow us on Twitter:

twitter.com/sentrysoftware

LEARN MORE

To learn more about our solutions, please visit :www.sentrysoftware.com/solutions

© BMC Software, Inc. All rights reserved.

ABOUT MARKETZONE DIRECT PRODUCTS

The BMC MarketZone Directprogram sells and supportsthird-party products thatcomplement and/or augment BMCsolutions. MarketZone Directproducts are available under BMClicense and support terms.

About BMC Software™BMC Software helps leading companies around the world put technology at the forefrontof business transformation, improving the delivery and consumption of digital services.From mainframe to cloud to mobile, BMC delivers innovative IT management solutionsthat have enabled more than 20,000 customers to leverage complex technology intoextraordinary business performance—increasing their agility and exceeding anythingthey previously thought possible. For more information about BMC Software, visit

www.bmc.com.

Bus ines s thrives when IT runs s marter,fas ter and s tronger. That’s why the mos tdemanding IT organizations in the worldrely on BMC Software acros s dis tributed,mainframe, virtual and cloudenvironments . Recognized as the leader inBus ines s Service Management, BMC offersa comprehens ive approach and unifiedplatform that helps IT organizations cutcos t , reduce ris k and drive bus ines sprofit . For the four fis cal quarters endedSeptember 30,2011, BMC revenue wasapproximately $2.2 billion.

BUSINESS RUNS ON I.T .

I.T . RUNS ON BMC SOFT WARE

http://facebook.com/sentrysoftware

http://twitter.com/sentrysoftware

http://twitter.com/sentrysoftware

http://facebook.com/sentrysoftware

Date post:	25-Apr-2018
Category:	Documents
Upload:	hamien
View:	220 times
Download:	2 times

Tivoli Storage Manager KM for PATROL vx.x Storage Manager KM for PATROL Version 2.7.02 4 Tivoli...

Documents