BMC TrueSight Operations Management - Tivoli Storage Manager … · 2018-03-27 · BMC TrueSight Operations Management - IBM Spectrum Protect Monitoring STORAGE MONITORING USER DOCUMENTATION

BMC TrueSight OperationsManagement - IBM SpectrumProtect Monitoring

STORAGE MONITORING

USER DOCUMENTATION

Version 3.1.00

March 2018

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

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

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 the Web,call 800 537 1813. Outside the United States and Canada, please contact your local support centerfor assistance. To find telephone and email contact information for the BMC Software supportcenter that services your location, refer to the Contact Customer Support section of the Supportpage on the BMC Software Web site at http://www.bmc.com/support_home.

3

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

http://www.bmc.com/support_home


http://www.sentrysoftware.com


4

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

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

.....................................................................................................................................................................................10Business Value

.....................................................................................................................................................................................11Requirements

.......................................................................................................................................................................................11System Requirements

.......................................................................................................................................................................................11Software Requirements

.......................................................................................................................................................................................13Security Requirements

.......................................................................................................................................................................................18Disk Space Requirements

.......................................................................................................................................................................................18Remote Monitoring Requirements

.....................................................................................................................................................................................22Importing the Monitoring Solution into Central Administration

.....................................................................................................................................................................................23Creating the Installation Package

.....................................................................................................................................................................................24Downloading the Installation Package

.....................................................................................................................................................................................24Installing the Package

.....................................................................................................................................................................................291. Configuring TSM Servers Monitoring

.....................................................................................................................................................................................312. Configuring Advanced Settings

.......................................................................................................................................................................................32Enabling the Debug Mode

.......................................................................................................................................................................................33Configuring the Maximum Number of Instances

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

.......................................................................................................................................................................................40Configuring TSM Server Discovery Overrides (Optional)

.....................................................................................................................................................................................433. Configuring Other Monitor Types

.......................................................................................................................................................................................44Configuring Automated Drives

.......................................................................................................................................................................................46Configuring Automated Libraries

.......................................................................................................................................................................................48Configuring Clients

.......................................................................................................................................................................................50Configuring Daemons

.......................................................................................................................................................................................52Configuring Domains

.......................................................................................................................................................................................54Configuring Domain Client Nodes

.......................................................................................................................................................................................56Configuring Jobs

.......................................................................................................................................................................................57Configuring Logs

.......................................................................................................................................................................................61Configuring Manual Drives

.......................................................................................................................................................................................62Configuring Mount Requests

.......................................................................................................................................................................................63Configuring Processes

.......................................................................................................................................................................................64Configuring Storage Pools

.....................................................................................................................................................................................65Blocking the Monitoring of Servers

5

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

.....................................................................................................................................................................................69IBM Spectrum Protect KM

.....................................................................................................................................................................................70TSM Clients

.....................................................................................................................................................................................71TSM Client

.....................................................................................................................................................................................72TSM Daemons

.....................................................................................................................................................................................73TSM Daemon

.....................................................................................................................................................................................75TSM Databases

.....................................................................................................................................................................................76TSM Database

.....................................................................................................................................................................................79TSM Logs

.....................................................................................................................................................................................80TSM Log

.....................................................................................................................................................................................81TSM Domains

.....................................................................................................................................................................................82TSM Domain

.....................................................................................................................................................................................84TSM Jobs

.....................................................................................................................................................................................86TSM Job

.....................................................................................................................................................................................88TSM Mount Requests

.....................................................................................................................................................................................89TSM Mount Request

.....................................................................................................................................................................................90TSM Automated Libraries

.....................................................................................................................................................................................91TSM Automated Library

.....................................................................................................................................................................................92TSM Manual Drive

.....................................................................................................................................................................................93TSM Automated Drives

.....................................................................................................................................................................................94TSM Automated Drive

.....................................................................................................................................................................................95TSM Domain Client Node

.....................................................................................................................................................................................96TSM Storage Pools

.....................................................................................................................................................................................97TSM Storage Pool

.....................................................................................................................................................................................101TSM Processes

.....................................................................................................................................................................................102TSM Process

.....................................................................................................................................................................................103Managing Baselines and Key Performance Indicators

Release Notes for v3.1.00

7

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Important Information

The BMC patch 11.0.00.01: Patch 1 for BMC PATROL Agent 11.0.00 must be installed to use anyversion of BMC TrueSight Operations Management - IBM Spectrum Protect Monitoring. Version11.0.00i of the PATROL Agent on Windows prevents IBM Spectrum Protect KM from operatingproperly. While apparently successfully loaded, IBM Spectrum Protect KM fails to start and canneither monitor the local system or the remote systems. An error message is displayed statingthat no hardware connectors are loaded and that the product needs to be re-installed.

What's New

TrueSight Operations Management - Tivoli Storage Manager Monitoring has been renamedBMC TrueSight Operations Management - IBM Spectrum Protect Monitoring to comply with therebranding of Tivoli Storage Manager.

TSM-477: Full support for IBM Spectrum Protect v8.x.

TSM-453: The monitoring of any additional log file can now be configured in TrueSight. Thelog filter can also be customized to indicate when Warnings and Alarms are triggered.

TSM-503: The multi-node mode failover supports the new remote monitoring architecture.

Changes and ImprovementsTSM-442: IBM Spectrum Protect KM now properly takes user-configured log scan limit intoaccount.

TSM-451: The overall performance of IBM Spectrum Protect KM is significantly improved.

TSM-497: TSM Tape Libraries are now properly discovered and monitored.

TSM-452: The monitoring of remote servers can be blocked from the remote node, to avoidunnecessary alerts and notifications.

Fixed IssuesTSM-454: The Exit status of each command run by IBM Spectrum Protect KM on a remoteWindows system is now properly verified and reported.

TSM-517: The debug settings are now correctly interpreted and applied when set from theTrueSight (CMA) console.

https://docs.bmc.com/docs/PATROLAgent/110/11-0-00-01-patch-1-for-bmc-patrol-agent-11-0-00-784075031.html

Key Concepts

9

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

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

User Goals and Features

Business Value

Requirements

Note that for convenience and brevity, reference to BMC TrueSight Operations Management - IBM SpectrumProtect Monitoring, may also be made as IBM Spectrum Protect KM.

User Goals and FeaturesIBM Spectrum Protect KM enables you to monitor the following in your environment:

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.

10User Goals and Features

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Business ValueBMC TrueSight Operations Management - IBM Spectrum Protect Monitoring provides current andhistorical information through a centralized console so you can easily view and manage yourentire TSM environment. The product collects and brings critical performance data and usefulmetrics into the BMC TrueSight Operations Management environment and enables SANAdministrators to be warned whenever a problem occurs in their TSM environment.

BMC TrueSight Operations Management - IBM Spectrum Protect Monitoring:

Detects backup and restore errors

Ensures maximum data protection and maximum availability

Measures jobs progress

Helps diagnosing server problems

Analyzes trend

Detects disk or tapes space shortages

Ensures backups are successful

Helps identify bottlenecks and optimize backup domains.

11 Business Value

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

RequirementsBefore installing the IBM Spectrum Protect KM, verify the:

System Requirements

Software Requirements

Security Requirements

Disk Space Requirements

Remote Monitoring Requirements

System Requirements

Operating System Version

Oracle SolarisTM 8 and higher

HP-UX 11 and higher

IBM® AIXTM 5.1 and higher

Linux® All distributions

Microsoft® Windows® 2008 and higher

Software RequirementsThe IBM Spectrum Protect KM supports the following platforms:

Software Version

IBM Spectrum Protect (Tivoli Storage Manager) 5.1 and higher

IBM Spectrum Protect Backup-Archive Client (TivoliStorage Manager Backup-Archive Client)

5.1 and higher

BMC Software PATROL Agent Any version

BMC Software PATROL Console Any version

BMC Portal 2.3 and higher

BMC ProactiveNet Performance Manager 9.5 and higher

BMC TrueSight Operations Management 10 and higher

Java 1.8 and higher

12Requirements

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

If you're running the IBM Spectrum Protect KM on AIX, Linux, or Microsoft Windows x64 managednodes, please verify these additional software requirements:

Purpose Software Version

When running IBM SpectrumProtect KM with sudo useraccount on Solaris, HP-UX, AIX orLinux managed nodes

Sudo (superuser do) 1.6.7 or later

When running IBM SpectrumProtect KM on AIX managed nodes

Default ncargs value forprocessing bpdbjobs output maynot be sufficient. Check this attribute using:lsattr -EH -l sys0 | grep ncargs If the value is below 16, increaseit using:chdev -l sys0 -a ncargs=16

Any

When running IBM SpectrumProtect KM on Linux managednodes

Korn shell binary (/bin/ksh)Alternatively a soft link frombin/ksh to /bin/bash will beneeded.

Any

When running IBM SpectrumProtect KM on MicrosoftWindows x64 managed nodes

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

Any

The Microsoft Windows x64 Reg.exe patch, KB948698 is required to allow access to 64-bit registry keysfrom PATROL Agent. Access the above patch site f rom the managed node to obtain the correct patch forthat platform.

To support bash shell platforms when ksh is not installed

To collect TSM stats when ksh was not installed on UNIX/Linux servers, you need to create a softlink for /bin/ksh to /bin/bash:

ln –s /bin/bash /bin/ksh

JAVA

BMC TrueSight Operations Management - IBM Spectrum Protect Monitoring requires Java 1.8 orhigher and a Java Runtime Environment (JRE) to be installed on the same system that runs thePATROL Agent.

The solution will automatically detect the JRE path if it has been installed in the default locationor under the BMC PATROL Agent installation path. If it has been installed in a different location,

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



13 Requirements

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

you will have to set it to the PATH for the PATROL Agent default account before starting thePATROL Agent.

You can download the Java Runtime Environment along with the KM on the Sentry Software Website.

Security RequirementsA user account with administrative privileges must be configured in BMC PATROL to read andexecute IBM Spectrum Protect 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 IBM Spectrum Protect toexecute application programs and access file systems

a non-root account, such as patrol, configured in IBM Spectrum Protect application toadminister the IBM Spectrum Protect application.

On Windows platforms:

an administrator user

a non-administrator account, such as patrol, configured in IBM Spectrum Protectapplication to administer the IBM Spectrum Protect application.

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

Access Permissions

The IBM Spectrum Protect KM user needs “read & execute” permission to executable and libraryfiles under the paths listed below. The Tivoli Storage Manager installation path INSTALL_PATH,referenced below, is normally /usr/tivoli/tsm or /opt/tivoli/tsm (on Unix) or C:\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

http://www.sentrysoftware.com/products/km-tivoli-storage-manager.asp

http://www.sentrysoftware.com/products/km-tivoli-storage-manager.asp

14Requirements

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

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/VRTStsm/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 IBM Spectrum Protect KM includes some scripts which should be executable by the PATROLAgent user and the IBM Spectrum Protect KM user. These scripts are stored under KM_HOMEpath, normally PATROL_HOME/lib/TSM.

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

foreach var (grep("^/Runtime/TSM/.*CommandControls/",pconfig("LIST")))

{

ctl=get(var);

opt=ntharg(grep("Option",ctl),"2-"," =");

nsa=ntharg(grep("NoSudoAttempt",ctl),"2-"," =");

sua=ntharg(grep("SingleUserAttempt",ctl),"2-"," =");

typ=ntharg(grep("CommandType",ctl),"2-"," =");

cmd=nthargf(grep("CommandText",ctl),"2-","=","=");

if(osp=="") { osp=trim(nthargf(grep("OSPlatform",ctl),"2-","=","="), " "); }

fields=lines(ntharg(var,"1-","/"));

old_host=host;

host=(fields == 5)? ntharg(var,"3","/") : "localhost";

if(host!=old_host)

{

if((osp!="WINDOWS") && sudoers) { printf("\n\nCommands used with sudo:\n%s",sort(sudoers)); }

printf("\n\nOn %s:\n\n", host);

i=0; sudoers=""; osp="";

}

if((typ == "")||(typ == "OS"))

{

met="";

if(opt == "NoLogin") { met = "(run as patrol user)"; }

elsif(nsa == "YES") { met = "(run as configured user without sudo)"; }

elsif(sua == "YES") { met = "(run as supplied user - used in menu)"; }

else

{

scmd=cmd;

s=index(scmd,"%sudo");

if(s) { scmd=replace(substr(scmd,s,length(scmd)),"%sudo",""); }

sudoers=union(sudoers,ntharg(ntharg(scmd,1,">|"),"1-"," "," "));

}

printf("(%2d) %-30s %-40s: %s\n",i++,ntharg(var,fields,"/"),met,cmd);

}

}

if((osp!="WINDOWS") && sudoers) { printf("\n\nCommands used with sudo:\n%s",sort(sudoers)); }

15 Requirements

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

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_TEMP 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_TEMP temporarily during thisactivity.

On Windows platforms the IBM Spectrum Protect 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 IBM Spectrum Protect KM user,configure the account as a sudoer through the visudo utility using code appropriate for yourplatform as detailed below. This user should be able to execute TSM commands and OScommands.

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

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

16Requirements

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

On Solaris:

User_Alias TSMKMUSERS = user1, user2, user3

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

env_keep+="PATH LD_LIBRARY_PATH INSTALL_PATH KM_HOME KM_TEMP \

DSM_CONFIG DSM_DIR DSM_LOG",env_reset

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

INSTALL_PATH/server/bin/*,\

INSTALL_PATH/client/ba/bin/*,\

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

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

Replace PATROL_HOME/lib/TSM/* with the Remote Temp Directory Path, default /var/tmp/*, whenmonitoring remotely.

On HP-UX:



env_keep+="PATH SHLIB_PATH INSTALL_PATH KM_HOME KM_TEMP \








On AIX & Linux:



env_keep+="PATH SHLIB_PATH INSTALL_PATH KM_HOME KM_TEMP \







17 Requirements

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0


Admin Interface User Access

BMC TrueSight Operations Management - IBM Spectrum Protect Monitoring requires that anadministrator account (standard administrator with no other privileges) be added to the IBMSpectrum Protect server for use by PATROL and the IBM Spectrum Protect KM.

This account is used to query the configuration details and resource utilization of the serverthrough the IBM Spectrum Protect Backup-Archive Client interface. No changes are made by this useron the IBM Spectrum Protect server - the IBM Spectrum Protect KM operates in “read-only” modefor normal operation.

The suggested name for this DSMADMC user account is patrol. This user account must be set updirectly in TSM Server, and the login details are entered during KM configuration in the same waythat the OS login details are entered. The password is stored in the TSOM in an encrypted format.

DSMADMC command binary is executed using an OS user account matching the the DSMADMClogin. 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 includesexecute permission to DSM_CONFIG path and dsmadmc (or dsmadmc.exe) file and writepermission to DSM_LOG path and dsmerror.log file.

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

i=0;

foreach var (grep("^/Runtime/TSM/.*CommandControls/",pconfig("LIST")))

{

ctl=pconfig("GET", var);

typ=ntharg(grep("CommandType",ctl),"2-"," =");

if(typ != "DSMADMC") { next; }

fields=lines(ntharg(var,"1-","/"));

old_host=host;

host=(fields == 5)? ntharg(var,"3","/") : "localhost";

if(host!=old_host)

{

printf("\n\nOn %s:\n\n", host);

i=0;

}

cmd=nthargf(grep("CommandText",ctl),"2-","=","=");

printf("(%2d) %-25s: %s\n",i++,ntharg(var,fields,"/"),cmd);

}

18Requirements

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Disk Space RequirementsBMC TrueSight Operations Management - IBM Spectrum Protect Monitoring requiresapproximately:

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 IBM Spectrum Protect KM is installed under the PATROL installation path.

When monitoring a standard installation of IBM Spectrum Protect, the PATROL Agent willgenerate approximately 500 KBytes of history data per day. An enterprise installation of IBMSpectrum Protect 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 IBM Spectrum Protect KM creates and maintains temporary files under KM_HOME, KM_TEMP and KM_DEBUG paths. By default they are all under PATROL_HOME/lib/TSM, where PATROL_HOME path is normally /opt/bmc/Patrol3/ (on Unix) or C:\Program Files(x86)\BMC Software\Patrol3\ (on Microsoft Windows). Please make sure you have sufficientspace under KM_TEMP and KM_DEBUG paths.

If the location of the KM_TEMP or KM_DEBUG is not suitable, it can be changed using theConfiguring Advanced Settings from the monitoring policy menu from the main instance. Thesefolder should have read, write and execute permissions for both the PATROL Agent user and theKM login user.

Remote Monitoring RequirementsBMC TrueSight Operations Management - IBM Spectrum Protect Monitoring supports the

monitoring of multiple IBM Spectrum Protect Server and Storage Agent instances locally and

remotely without the need to run multiple PATROL Agents. The KM can be installed on any

PATROL Agent node to monitor TSM servers remotely. Therefore, the TSM Backup-Archive Client

software needs to be installed on the PATROL Agent node. Follow the TSM Backup-Archive Client

installation procedure to install and configure the API before installing the KM.

Upon the initial discovery, IBM Spectrum Protect KM will discover the TSM Backup-Archive Client

installation on the PATROL Agent node and search for the dsmadmc binary file path following the

installation path in the registry (Windows) and under the default paths. If the file is not

detected, a message will be displayed in the SOW (System Output Window) and in the

TSM_<port>.log file. This path is shared between all TSM server instances monitored from the

19 Requirements

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

PATROL Agent node. It is possible to manually configure the path, if the TSM Backup-Archive

Client is installed under a custom path, in the TSM Credentials section in the monitoring policy.

Managing Remote Connection SettingsIn order to remotely access a TSM server, you need to configure a specific OS login account in the

TSM Credentials in the monitoring policy.

Remote monitoring cannot be performed from UNIX/Linux PATROL Agent to Windows TSM server.

The requirements listed below must be met to be able to use remote monitoring.

SSH/WMI Connection

An SSH (UNIX/Linux platforms) or a WMI (Windows platforms) connection is required to monitorremote TSM servers. When using an SSH connection, the SSH host key authentication must bedisabled on the remote host.

Disabling the SSH Host Key Authentication

SSH host key authentication is enabled by default on most TSM servers. To disable it:

1. Open the global SSH configuration file (ssh_config) stored in the /etc/ssh/ directory on theremote host

2. Add the line StrictHostKeyChecking no

3. Save the file.

Installing the Monitoring Solution

21

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Once the latest version of the solution has been loaded into Central Monitoring Administration,administrators can create all the installation packages required for their different operatingsystems and platforms and save them for later use in the Monitoring Installation Packages list.These packages can then be deployed to multiple computers. Administrators just have toconnect to TrueSight Operations Management from the server where they want to install thepackage, download it and launch the installation.

This section describes the different steps to follow to install IBM Spectrum Protect KM:

Importing IBM Spectrum Protect KM into Central Monitoring Administration

Creating the Installation Package

Downloading the Installation Package

Installing the Package

22

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Importing the Monitoring Solutioninto Central AdministrationThe TrueSight Central Monitoring Repository includes the current versions of BMC TrueSightOperations Management - IBM Spectrum Protect Monitoring that you can use with BMCTrueSight. If the version available in the Repository does not correspond to the latest one, youwill have to manually import it:

1. Log on to the BMC TrueSight Operations Management Console.

2. Launch Central Monitoring Administration.

3. Click the Repository drawer and select Manage Repository.

4. Check that the version of the BMC component available is actually the latest one. If not,download the latest version corresponding to your operating system (Windows or UNIX/Linux) available on the Sentry Software Website.

5. From TrueSight Operations Management, click Import .

6. Select Single solution.

7. Browse to the .zip source file.

8. Click Import.

The selected archive file is imported to the repository.

http://www.sentrysoftware.com/support/product-lifecycle.asp

23 Importing the Monitoring Solution into CentralAdministration

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Creating the Installation PackageThe installation package to deploy to managed systems can be created directly from TrueSightOperations Management:

1. Log on to TrueSight Operations Management

2. Click the Repository drawer and select Deployable Package Repository.

3. Click Add .

4. Select the operating system and platform for which you want to create a package. Thecomponents available in the repository for the selected operating system and platform aredisplayed.

5. Select the Installation Package Component:

From the Available components list, select the relevant component.

From the Version list, select the latest version.

Click the right arrow button to move the component into the Selected Components list.By default, the appropriate BMC PATROL Agent for the operating system and platform thatyou chose is included in the Selected components list.

Click Next. The Add Component Installation Package wizard are displayed.

6. Go through the wizard and specify the required PATROL information. The InstallationPackage Details is displayed.

7. Verify that:

the operating system and platform are correct

the components that you want to include are listed in the Included Components list.

8. Provide the following information:

Name: Enter a unique name for the package.

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

Format: Select a file compression format for the package.

9. Click Save Installation Package.

10. Click Close. The package is now available in the Monitoring Installation Packages list.

24Creating the Installation Package

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

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

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

1. Log on to TrueSight Operations Management from the computer on which the PATROL Agentis installed or to be installed.

2. Click the Repository drawer and select Deployable Package Repository.

3. (Optional) To filter the list of installation packages, select an operating system from the Filter by Operating System list.

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

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

Installing the PackageThis chapter provides a step by step procedure to install a monitoring solution package:

1. From the computer on which you want to install the package, log on to TrueSight OperationsManagement.

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

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

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

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

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

(UNIX or Linux) RunSilentInstall.sh

(Microsoft Windows) RunSilentInstall.exe

The package is installed on the current host. If the package includes a BMC PATROL Agent, theagent sends a configuration request by passing its tags to Central Monitoring Administration, viathe Integration Service. Central Monitoring Administration evaluates policies that match thetags, determines the final configuration to be applied, and sends the configuration informationback to the agent. Monitoring is based on the configuration information received by the agent.

Configuring After Installation

26

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Once IBM Spectrum Protect KM is installed, you will have to configure the TSM Monitor Typesthrough policies. Policies enable you to deploy configurations on PATROL Agents and monitoringsolutions, such as IBM Spectrum Protect KM in an automated way. Policies are designed to defineand configure monitoring criteria and apply them to the specified PATROL Agents. Theconfiguration criteria are automatically pushed to the PATROL Agents on which the policy isapplied. When a monitoring policy is applied to a PATROL Agent, the device is automaticallyadded to the list of monitored devices.

To create a monitoring policy1. Log on to the TrueSight console.

2. In the navigation pane, expand Configuration and select Infrastructure Policies.

3. In the Infrastructure Policies page, ensure that the Monitoring tab is selected and clickCreate Policy.

4. In the Create Monitoring Policy page, specify the monitoring policy properties:

Step 1 - Define the General Properties

Property Description

Name Name for the policy. The policy names must be unique. In an environment with tenants, thepolicy names must be unique for a single tenant. It is a mandatory field.

Description (Optional) A brief description about the policy.

Associated UserGroup

Name of the user group that is associated with the PATROL Agents as defined in theAuthorization Profile or in the PATROL Agent ACLs. The policy is applicable to thesePATROL Agents.

Share with UserGroup

Specify whether this policy is to be shared with the users across the associated usergroup or not. This property can be viewed in READ-ONLY mode by other users of theassociated user group. Only the owner of the policy can modify this property.

Precedence Priority of the policy. Based on the precedence number that you configure, theconfiguration is applied to the PATROL Agents and the Infrastructure Management servers.The precedence number ranges from 0 to 999. A lower number indicates a higherprecedence. The default value is 900.The configuration from a policy with a higher precedence overrides the configuration froma policy with a lower precedence. If two policies have the same precedence number, thenthe configuration from the latest created policy takes priority.

Enable Policy Indicates whether the policy is enabled or disabled. By default, the policy is disabled. Ifyou do not enable a policy when you create it, the policy configurations are not applied tothe PATROL Agents and the Infrastructure Management Servers. If you disable any existingpolicy, the policy configurations are removed from the PATROL Agents and theInfrastructure Management servers, where the policy was applied.

Step 2 - Select the PATROL AgentsDefine conditions to select the PATROL Agents on which you want to apply the policy:

27

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

1. Select a property.

2. Select an operator to create the condition. The available operators depend on the propertythat you select.

3. Specify a value for the selected property.

4. (Optional) To add more than one condition, click the button, and perform the earliersteps.

5. (Optional) To group the conditions, use the parentheses and Boolean operators from theircorresponding lists.

The Add Monitor Types dialog box presents configuration fields for compatible BMC PATROLmonitoring solutions that are located in the Central Monitoring Repository.

Step 3 - Select the Required Monitor Type1. Click the Monitoring tab.

2. Click Add Monitoring Configuration.

3. In the Add Monitoring Configuration dialog box, configure the properties:

From the Monitoring Solution menu, select TSM.

From the Version menu, select the required version.

The Monitor Profile IBM Spectrum Protect KM is automatically selected.

Selecting the Required Monitor Type

Refer to the table below to know which monitor types are available and their function

Monitor Type Description

IBM Spectrum ProtectKM

To set the general settings of IBM Spectrum Protect KM (credentials,debug mode, instances, multi-node mode, etc.)

TSM Automated Drive Enables access to the filtering options to select the automated driveselements that will be monitored.

TSM AutomatedLibrary

Enables access to the filtering options to select the automatedlibraries elements that will be monitored.

28

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Monitor Type Description

TSM Client Enables access to the filtering options to select the clients elementsthat will be monitored.

TSM Daemon Enables access to the filtering options to select the daemonselements that will be monitored.

TSM Domain To:enable access to the filtering options to select the domainselements that will be monitoredset backup restrictions.

TSM Domain ClientNode

Enables access to the filtering options to select the domain clientnodes elements that will be monitored.

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

TSM Log To modify the log default monitoring. You can more especially specifythe number of KBytes of data to be scanned for each log file duringeach data collection cycle. By default: 500 KBytes.

TSM Manual Drive Enables access to the filtering options to select the manual driveselements that will be monitored.

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

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

TSM Storage Pool Enables access to the filtering options to select the storage poolselements that will be monitored.

Step 4 - Configure the Selected Monitor Type1. Depending on the selected Monitor Type, the available fields will vary. Refer to appropriate

section to know how to configure them.

2. Click Save to apply your changes to the selected PATROL Agent(s).

To edit a monitoring policy1. Log on to the TrueSight console.

2. In the navigation pane, expand Configuration and select Infrastructure Policies.

3. In the Infrastructure Policies page, locate the monitoring policy you wish to modify, click its

action button and click Edit.

4. In the Edit Monitoring Policy page, locate the monitoring configuration you wish to modify

and click its action button to access the monitoring options panel.

5. Customize the configuration.

6. Click Save to apply your changes to the selected PATROL Agent(s).

29

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

1. Configuring TSM ServersMonitoringBefore using IBM Spectrum Protect KM, you need to configure the monitoring settings for theIBM Spectrum Protect KM Monitor Type. You will then be able to create and customize otherMonitor Types according to the component(s) you wish to monitor.

To configure the IBM Spectrum Protect KM monitoring settings

Specify the options that will constitute the TSM monitoring settings.

1. Create your monitoring policy.

2. In the Add Monitoring Configuration dialog box, configure the properties:

From the Monitoring Solution menu, select IBM Spectrum Protect KM

From the Version menu, select the required version

The Monitor Profile IBM Spectrum Protect KM is automatically selected

3. In the TSM Monitoring Settings section, click Add.

4. Specify the settings for the TSM Host to be monitored:

In the Hostname/IP Address/FQDN field:

· for a local host, enter localhost to apply these settings to all PATROL Agents installedon the TSM Servers

· for a remote host, enter a hostname or IP address to apply these settings to a specificserver

Click the Create a Device in the Console box if you want the TSM server to appear as aseparate device in TrueSight.

Adding a TSM Host to the Monitoring Environment

301. Configuring TSM Servers Monitoring

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

5. Set the TSM Credentials:

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

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

(Unix Only) If the user account has sudo privileges, check the Use Sudo box and indicatethe sudo binary file path, if it is installed on a custom path. The KM will automaticallydetect the sudo path from the default paths, if it is left blank (Default: /usr/local/bin/sudo)

Enter a valid TSM Backup-Archive Client User ID and Password and indicate the DSMADMCfile path. The KM will automatically detect the DSMADMC file path from the default paths,if it is left blank.

Configuring TSM User Account

31 1. Configuring TSM Servers Monitoring

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

6. (Optional - Remote Monitoring Only) Set the Remote Connection Settings:

Configuring the Remote Connection Settings

In the Connection Timeout (in Seconds) field, enter the number of seconds after which theconnection to the remote node will time out

In the Maximum Connections field, enter the maximum number of simultaneousconnections allowed to the remote node

7. (Optional) Define the Advanced Settings:

the debug mode

the maximum number of instances

the multi-node monitoring mode

the TSM discovery overrides.

8. Click OK twice.

9. Click Save.

2. Configuring Advanced SettingsOnce the IBM Spectrum Protect server to be monitored and the account to be used are specified,you can configure the following advanced settings:

The debug mode

The maximum number of instances

The multi-node monitoring mode

The TSM server discovery overrides

322. Configuring Advanced Settings

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

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.

To enable the debug mode1. Edit your monitoring policy.

2. Click the action button of the TSM system for which you wish to enable the Debug Modeand click Edit.

3. In the TSM Monitoring Settings panel, scroll down to the Debug section.

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

Configuring the Debug Mode Settings

4. In the Options section, indicate:

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

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

33 2. Configuring Advanced Settings

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Setting the Debug End Time and Directory Path

5. Click OK to validate.

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

Configuring the Maximum Number ofInstancesBy default, the solution discovers and monitors all the instances. Because there may be a verylarge number of instances to monitor and this may represent a important workload to the agentsand the TrueSight servers, it is recommended to only monitor the critical ones. This can be doneby configuring the instance limits.


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

To configure the maximum number of instances1. Edit your monitoring policy.

2. Click the action button of the TSM server for which you wish to configure the maximumnumber of instances and click Edit.

3. In the TSM Monitoring Settings panel, scroll down to the Maximum Number of Instancessection.

4. For each monitored element, indicate the maximum number of instances to be displayed, orenter 0 in the relevant field to disable the monitoring of a specific element. (By default, themaximum number of instances is left empty to allow an unlimited number of instances).


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Configuring the Maximum Number of Instances

5. Click OK twice.

6. Click Save.


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Configuring the Multi-Node Monitoring ModeWhen an application is installed in a cluster environment, i.e. active on one cluster node andpassive on others, false alarms and duplicate alerts may occur. To avoid such situation, usersneed to configure IBM Spectrum Protect KM in Multi-node monitoring mode, if TSM is installed in

a supported cluster.

The procedure below is generic. To learn more about all the configuration methods available,see Configuring the Multi-node Monitoring Mode with the VCS KM. Although the article refersto Veritas Cluster Server KM for PATROL, the monitoring concepts and principles remain validfor BMC TrueSight Operations Management - IBM Spectrum Protect Monitoring.

To configure the multi-node monitoring mode1. Edit your monitoring policy.

2. Click the action button of the TSM server for which you wish to configure the multi-nodemonitoring mode and click Edit.

3. In the TSM Monitoring Settings panel, scroll down to the Multi-node Monitoring Modesection.

Configuring the Multi-Node Mode

https://www.sentrysoftware.com/kb/KB1211.asp


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

4. Check the Enable Multi-node Monitoring Mode option.

5. Configure the Multi-node Mode:

Select the appropriate Cluster Application

Indicate the Failover Group Name. Leave this field blank if you have previously selectedVeritas Cluster File System. Then the IBM Spectrum Protect KM will then monitor the TSMsystem from the active master system, which is identified by “vxdctl -c mode” command.This method requires vxconfigd in enable mode with its clustered state active

6. (Optional) Check the Enable Remote PATROL Agent Checking option to allow the solution tocheck the monitoring mode of the remote PATROL Agents. If the Remote PATROL AgentChecking is disabled, the solution will monitor actively through active cluster node or on thenode where failover group is online and will not check the monitoring status of the IBMSpectrum Protect KM on the other PATROL Agent nodes.

Repeat the procedure for each TSM node that is part of the multi-node mode configuration

7. In the Monitoring Nodes section:

Click Add to configure the details of all managed nodes of the cluster to be configured inthe multi-node mode

Identifying the Node to Monitor

Provide the PATROL Agent Hostname (host where the PATROL agent is installed), the NodeID (the unique ID of the TSM node derived from the hostname in the TSM Serverconfiguration), and Cluster Node Name (the hostname defined in the selected ClusterApplication)

Click OK

Repeat the procedure for each TSM node that is part of the multi-node mode configuration


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

8. If the Enable Remote PATROL Agent Checking option is selected, click Add in the RemoteAgent section, to provide all the information required to communicate with the PATROLAgents. There should be one entry per each PATROL Agent.

Configuring the Remote Agent Communication Settings

Provide the Monitoring Node Name

Select the Protocol you wish to use to connect to the PATROL Agent

Enter the Port number you wish to use to connect to the PATROL Agent

Provide the Username and Password you wish to use to connect to the PATROL Agent

In the Number of Attempts field, specify the number of times the solution will try tocommunicate with the remote PATROL Agent before failing over

Enter the timeout you wish to set, in seconds, between each attempt


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

9. Click OK twice.

10. Click Save.

The TSM server will then be monitored through the master or online node in Active Multi-nodeMode. The other nodes, which are standing by for a failover, will be in Passive Multi-node Mode,monitoring only the components that are not visible from the active node.

If a managed node is unable to check the monitoring status of the active managed node, it willchange to Temporary Single-node Mode allowing a full TSM monitoring. It will remain inTemporary Single-node Mode until it finds the active node in full monitoring mode again.

If the Remote PATROL Agent Checking is Disabled, while there are more than one PATROL Agentinvolved, the managed node on the master or online node will be in Active Multi-node Modeand all others will be in Passive Multi-node Mode, without checking the monitoring status of theactive node. In addition, the above procedure to configure Multi-node Mode needs to berepeated from each PATROL Agent involved.


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Configuring TSM Server Discovery Overrides(Optional)The solution automatically discovers the TSM installation, the temporary directory paths used bythe IBM Spectrum Protect KM, and the node status. This information can however be overridden.

Altering these paths may impact the operation of IBM Spectrum Protect KM.


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

To configure TSM server discovery overrides1. Edit your monitoring policy.

2. Click the action button of the TSM server for which you wish to configure the discoveryoverrides and click Edit.

3. In the TSM Monitoring Settings panel, scroll down to the Discovery Overrides section.

Configuring TSM Discovery Overrides

4. Specify the TSM Server Discovery Overrides options:

TSM Installation Path: Provide the path to the directory where the TSM software isinstalled. By default, IBM Spectrum Protect KM automatically locates the TSM softwareinstallation directory if you have installed the solution with the default recommended


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

settings. If you have chosen to install the solution in a custom directory, you are requiredto provide its location.

DSM_DIR Directory Path: Provide the path to the directory where the temporary files aresaved on remote nodes. Default is /var/tmp (on UNIX/Linux) or C:\Windows\Temp (onWindows).

DSM_CONFIG Directory Path: Provide the path to the directory where the configurationtemporary files are saved on the PATROL Agent node (Default is <PATROL_HOME>/lib/TSM/tmp where PATROL_HOME is the PATROL Agent installation path). The DSM_CONFIGDirectory contains the .opt file that specifies the TSM server instance ID and the requiredconnection setting used by the TSM Admin Client to connect to the TSM server instance.

DSM_LOG Directory Path:

Remote Temp Directory Path: Provide the path to the directory where the temporary filesare saved on remote nodes (Default is /var/tmp).

Local Temp Directory Path: Provide the path to the directory where the temporary files aresaved on the PATROL Agent node (Default is <PATROL_HOME>/lib/TSM/tmp wherePATROL_HOME is the PATROL Agent installation path)

Node Type: Select the appropriate node type: media or master server. By default, IBMSpectrum Protect KM automatically discovers the type of node when the type is not user-specified.

Node Status Alarms: Enter the regular expressions to determine the Node Status in Alarm.This regular expression will be used on the result from DSMADMC command: "querystatus" on the TSM server.

Node Status Warning: Enter the regular expressions to determine the Node Status inWarning. This regular expression will be used on the result from DSMADMC command:"query status" on the TSM server.

5. Click OK twice.

6. Click Save.


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

3. Configuring Other Monitor TypesOnce the IBM Spectrum Protect KM monitor type is properly configured, you can create andcustomize the following Monitor Types, according to the component(s) you wish to monitor.

These conf iguration steps are optional. The monitor types below are automatically discovered andmonitored using defaults settings.

Configuring Automated Drives

Configuring Automated Libraries

Configuring Clients

Configuring Daemons

Configuring Domains

Configuring Domain Client Nodes

Configuring Jobs

Configuring Logs

Configuring Manual Drives

Configuring Mount Requests

Configuring Processes

Configuring Storage Pools

443. Configuring Other Monitor Types

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Configuring Automated DrivesBy default, BMC TrueSight Operations Management - IBM Spectrum Protect Monitoring monitorsall the discovered automated drives for a local or remote TSM server. However, it is possible toapply filters to specify whether or not specific drives will be monitored.

To configure the monitoring of automated drives1. From the Add Monitoring Configuration panel, select TSM Automated Drive from the

Monitor Type list.

2. In the TSM Server Automated Drives panel, click Add.

Configuring TSM Automated Drives

45 3. Configuring Other Monitor Types

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

3. In the Hostname field, enter:

localhost to apply these settings to all PATROL Agents installed on the TSM Server

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

4. Configure the Filtering options:

In the Keep Only Automated Drives section, click Add and identify the TSM automateddrive you wish to monitor. Enter the name of the TSM automated drive or identify it byusing a regular expression (example: prod-automateddrive). Click OK to validate. Repeatthe operation for any other TSM automated drive you wish to include in the monitoringprocess

In the Exclude Automated Drives section, click Add and identify the TSM automated driveyou do not want to monitor. Enter the name of the TSM automated drive or identify it byusing a regular expression (example:prod-automateddrive). Click OK to validate. Repeatthe operation for any other TSM automated drive you wish to exclude from the monitoringprocess

5. The Additional Automated Drives (manual discovery) section allows you to add TSMautomated drives manually, when they are not automatically discovered:

Click Add and enter the name of the TSM automated drive you wish to add to themonitoring environment. Click OK to validate. Repeat the operation for each TSMautomated drive you want to monitor

(Optional) Enter a short description that will allow you to quickly identify the added TSMautomated drives.



BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Configuring Automated LibrariesBy default, BMC TrueSight Operations Management - IBM Spectrum Protect Monitoring monitorsall the discovered automated libraries for a local or remote TSM server. However, it is possible toapply filters to specify whether or not specific libraries will be monitored.

To configure the monitoring of automated libraries1. From the Add Monitoring Configuration panel, select TSM Automated Library from the

Monitor Type list.

2. In the TSM Server Automated Libraries panel, click Add.

Configuring TSM Automated Libraries


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0





In the Keep Only Automated Libraries section, click Add and identify the TSM automatedlibrary you wish to monitor. Enter the name of the TSM automated library or identify it byusing a regular expression (example: prod-automatedlibrary). Click OK to validate. Repeatthe operation for any other TSM automated library you wish to include in the monitoringprocess

In the Exclude Automated Libraries section, click Add and identify the TSM automatedlibrary you do not want to monitor. Enter the name of the TSM automated library oridentify it by using a regular expression (example:prod-automatedlibrary). Click OK tovalidate. Repeat the operation for any other TSM automated library you wish to excludefrom the monitoring process

5. The Additional Automated Libraries (manual discovery) section allows you to add TSMautomated libraries manually, when they are not automatically discovered:

Click Add and enter the name of the TSM automated library you wish to add to themonitoring environment. Click OK to validate. Repeat the operation for each TSMautomated library you want to monitor

(Optional) Enter a short description that will allow you to quickly identify the added TSMautomated libraries.



BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Configuring ClientsBy default, BMC TrueSight Operations Management - IBM Spectrum Protect Monitoring monitorsall the discovered clients for a local or remote TSM server. However, it is possible to apply filtersto specify whether or not specific clients will be monitored.

To configure the monitoring of clients1. From the Add Monitoring Configuration panel, select TSM Client from the Monitor Type list.

2. In the TSM Server Client panel, click Add.

Configuring TSM Clients


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0





In the Keep Only Clients section, click Add and identify the TSM client you wish to monitor.Enter the name of the TSM client or identify it by using a regular expression (example:prod-client). Click OK to validate. Repeat the operation for any other TSM client you wishto include in the monitoring process

In the Exclude Clients section, click Add and identify the TSM client you do not want tomonitor. Enter the name of the TSM client or identify it by using a regular expression(example:prod-client). Click OK to validate. Repeat the operation for any other TSM clientyou wish to exclude from the monitoring process

5. The Additional Clients (manual discovery) section allows you to add TSM clients manually,when they are not automatically discovered:

Click Add and enter the name of the TSM client you wish to add to the monitoringenvironment. Click OK to validate. Repeat the operation for each TSM client you want tomonitor

(Optional) Enter a short description that will allow you to quickly identify the added TSMclients.



BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Configuring DaemonsBy default, BMC TrueSight Operations Management - IBM Spectrum Protect Monitoring monitorsall the discovered daemons for a local or remote TSM server. However, it is possible to applyfilters to specify whether or not specific daemons will be monitored.

To configure the monitoring of daemons1. From the Add Monitoring Configuration panel, select TSM Daemon from the Monitor Type

list.

2. In the TSM Server Daemon panel, click Add.

Configuring TSM Daemon


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0





In the Keep Only Daemons section, click Add and identify the TSM daemon you wish tomonitor. Enter the name of the TSM daemon or identify it by using a regular expression(example: prod-daemon). Click OK to validate. Repeat the operation for any other TSMdaemon you wish to include in the monitoring process

In the Exclude Daemons section, click Add and identify the TSM daemon you do not wantto monitor. Enter the name of the TSM daemon or identify it by using a regular expression(example:prod-daemon). Click OK to validate. Repeat the operation for any other TSMdaemon you wish to exclude from the monitoring process

5. The Additional Daemons (manual discovery) section allows you to add TSM daemonsmanually, when they are not automatically discovered:

Click Add and enter the name of the TSM daemon you wish to add to the monitoringenvironment. Click OK to validate. Repeat the operation for each TSM daemon you want tomonitor

(Optional) Enter a short description that will allow you to quickly identify the added TSMdaemons.



BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Configuring DomainsBy default, BMC TrueSight Operations Management - IBM Spectrum Protect Monitoring monitorsall the discovered domains for a local or remote TSM server. However, it is possible to applyfilters to specify whether or not specific domains will be monitored.

To configure the monitoring of domains1. From the Add Monitoring Configuration panel, select TSM Domain from the Monitor Type

list.

2. In the TSM Server Domain panel, click Add.

Configuring TSM Domain


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0





In the Keep Only Domains section, click Add and identify the TSM domain you wish tomonitor. Enter the name of the TSM domain or identify it by using a regular expression(example: prod-domain). Click OK to validate. Repeat the operation for any other TSMdomain you wish to include in the monitoring process

In the Exclude Domains section, click Add and identify the TSM domain you do not want tomonitor. Enter the name of the TSM domain or identify it by using a regular expression(example:prod-domain). Click OK to validate. Repeat the operation for any other TSMdomain you wish to exclude from the monitoring process

5. The Additional Domains (manual discovery) section allows you to add TSM domainsmanually, when they are not automatically discovered:

Click Add and enter the name of the TSM domain you wish to add to the monitoringenvironment. Click OK to validate. Repeat the operation for each TSM domain you want tomonitor

(Optional) Enter a short description that will allow you to quickly identify the added TSMdomains.

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

Check the Enable Backup Restriction Window option

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



BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Configuring Domain Client NodesBy default, BMC TrueSight Operations Management - IBM Spectrum Protect Monitoring monitorsall the discovered daemons for a local or remote TSM server. However, it is possible to applyfilters to specify whether or not specific daemons will be monitored.

To configure the monitoring of daemons1. From the Add Monitoring Configuration panel, select TSM Domain Client Node from the

Monitor Type list.

2. In the TSM Server Domain Client Nodes panel, click Add.

Configuring TSM Domain Client Nodes


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0





In the Keep Only Domain Client Nodes section, click Add and identify the TSM domainclient node you wish to monitor. Enter the name of the TSM domain client node or identifyit by using a regular expression (example: prod-node). Click OK to validate. Repeat theoperation for any other TSM domain client node you wish to include in the monitoringprocess

In the Exclude Domain Client Nodes section, click Add and identify the TSM domain clientnode you do not want to monitor. Enter the name of the TSM domain client node oridentify it by using a regular expression (example:prod-node). Click OK to validate. Repeatthe operation for any other TSM domain client node you wish to exclude from themonitoring process

5. The Additional Domain Client Nodes (manual discovery) section allows you to add TSMdomain client nodes manually, when they are not automatically discovered:

Click Add and enter the name of the TSM domain client node you wish to add to themonitoring environment. Click OK to validate. Repeat the operation for each TSM domainclient node you want to monitor

(Optional) Enter a short description that will allow you to quickly identify the added TSMdomain client nodes.



BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Configuring JobsBy default, the IBM Spectrum Protect KM monitors all scheduled jobs that completed successfullyfor 24 hours and any other scheduled job for 72 hours. This monitoring duration can however bemodified to better suit your requirements.

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

To configure the monitoring of jobs1. From the Add Monitoring Configuration panel, select TSM Job from the Monitor Type list.

2. In the TSM Server Job panel, click Add.

Configuring TSM Jobs


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0




4. In the Monitoring Duration section:

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

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


Configuring LogsBMC TrueSight Operations Management - IBM Spectrum Protect Monitoring scans log files byreading the new log entries since the last data collection cycle. By default, only 500 KBytes ofdata is scanned for each log file during each data collection cycle. This log scan limit can howeverbe modified to better suit your requirements.

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


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

To configure the monitoring of logs1. From the Add Monitoring Configuration panel, select TSM Log from the Monitor Type list.

2. In the TSM Log Settings panel, click Add.

Customizing the Log Scan Limit


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0


localhost to apply these settings to all PATROL Agents installed on the TSM server

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

4. In the Log Scan Limit field, indicate the amount of data (in KBytes) that will be read by themonitoring solution during each data collection cycle (Default is 500 kBytes).

5. In the Actlog or Eventlog Query Limit field, indicate the maximum query limit (in minutes).By default the solution queries up to 300 minutes (5 hours) of actlog data.


Customizing the Log Filter

In the Warnings section:

Click Add

Select the type of regular expression. Include will select all matching lines; Excludewill remove all matching lines

In the Regular Expression field, enter the expression that will trigger a warning

Provide your warning filter with an Internal ID

Click OK to validate.

Expressions that Will Generate a Warning

In the Alarms section

Click Add

Select the type of regular expression. Include will select all matching lines; Exclude


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

will remove all matching lines

In the Regular Expression field, enter the expression that will trigger an alarm

Provide your alarm filter with an Internal ID

Click OK to validate.

Expressions that Will Generate an Alarm

7. In the Custom TSM Logs section, click Add.

Configuring Custom TSM Logs

8. In the Filename (Full Path) field, enter the full path to the TSM Log file to be monitored using"\" as a separator (example: \var\VRTStsm\log\engine_A.log). For Windows events, prefixthe filename with Events - (example: Events - Systems).

9. (Optional) Enter a brief description of the TSM log.

10. Click OK twice.

11. Click Save.


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Configuring Manual DrivesBy default, BMC TrueSight Operations Management - IBM Spectrum Protect Monitoring monitorsall the discovered manual drives for a local or remote TSM server. However, it is possible to applyfilters to specify whether or not specific manual drives will be monitored.

To configure the monitoring of manual drives1. From the Add Monitoring Configuration panel, select TSM Manual Drive from the Monitor

Type list.

2. In the TSM Server Manual Drive panel, click Add.

Configuring TSM Manual Drives


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0





In the Keep Only Manual Drives section, click Add and identify the TSM manual drive youwish to monitor. Enter the name of the TSM manual drive or identify it by using a regularexpression (example: prod-drive). Click OK to validate. Repeat the operation for any otherTSM manual drive you wish to include in the monitoring process

In the Exclude Manual Drives section, click Add and identify the TSM manual drive you donot want to monitor. Enter the name of the TSM manual drive or identify it by using aregular expression (example:prod-drive). Click OK to validate. Repeat the operation forany other TSM manual drive you wish to exclude from the monitoring process

5. The Additional Manual Drives (manual discovery) section allows you to add TSM manualdrives manually, when they are not automatically discovered:

Click Add and enter the name of the TSM manual drive you wish to add to the monitoringenvironment. Click OK to validate. Repeat the operation for each TSM manual drive youwant to monitor

(Optional) Enter a short description that will allow you to quickly identify the added TSMmanual drives.


Configuring Mount RequestsBy default, the IBM Spectrum Protect KM monitors all mount requests for 24 hours. Thismonitoring duration can however be modified to better suit your requirements.


To configure the monitoring of mount requests1. From the Add Monitoring Configuration panel, select TSM Mount Request from the Monitor

Type list.

2. In the TSM Server Mount Request panel, click Add.

Configuring TSM Mount Requests


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0




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


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


To configure the monitoring of processes1. From the Add Monitoring Configuration panel, select TSM Process from the Monitor Type

list.

2. In the TSM Server Process panel, click Add.

Configuring TSM Processes


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0




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


Configuring Storage PoolsBy default, BMC TrueSight Operations Management - IBM Spectrum Protect Monitoring monitorsall the discovered storage pools for a local or remote TSM server. However, it is possible to applyfilters to specify whether or not specific storage pools will be monitored.

To configure the monitoring of storage pools1. From the Add Monitoring Configuration panel, select TSM Storage Pool from the Monitor

Type list.

2. In the TSM Server Storage Pool panel, click Add.

Configuring TSM Storage Pools


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0





In the Keep Only Storage Pools section, click Add and identify the TSM storage pool youwish to monitor. Enter the name of the TSM storage pool or identify it by using a regularexpression (example: prod-pool). Click OK to validate. Repeat the operation for any otherTSM storage pool you wish to include in the monitoring process

In the Exclude Storage Pools section, click Add and identify the TSM storage pool you donot want to monitor. Enter the name of the TSM storage pool or identify it by using aregular expression (example:prod-pool). Click OK to validate. Repeat the operation for anyother TSM storage pool you wish to exclude from the monitoring process

5. The Additional Storage Pools (manual discovery) section allows you to add TSM storage poolsmanually, when they are not automatically discovered:

Click Add and enter the name of the TSM storage pool you wish to add to the monitoringenvironment. Click OK to validate. Repeat the operation for each TSM storage pool youwant to monitor

(Optional) Enter a short description that will allow you to quickly identify the added TSMstorage pools.


Blocking the Monitoring of ServersDuring maintenance operations on a system, the TSM server owner/administrator may need tostop the monitoring of some TSM servers. When this situation occurs, the administrator will justhave to:

1. Create an empty block file named TSM_block

2. Save this file either in the Remote Temp Directory Path. By default, this path is set to:

/var/tmp (UNIX/Linux)

C:\Windows\Temp\ (Windows)

The PATROL Agent monitoring this TSM server will detect the block file during the next discoverycycle and turn the server instance to TSM Setup (Monitoring Blocked).

To resume monitoring, simply delete the TSM_block file.

Reference Guide

67

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Introduction

This chapter provides statistical information about resources, operating status, and performancesmanaged by the IBM Spectrum Protect KM. It contains tables describing the attributes used in themonitoring solution, grouped by Monitor Types, and provides a brief description of eachattribute and its default settings.

Monitor Types

IBM Spectrum Protect KM

TSM Clients

TSM Client

TSM Daemons

TSM Daemon

TSM Databases

TSM Database

TSM Logs

TSM Log

TSM Domains

TSM Domain

TSM Jobs

TSM Job

TSM Mount Requests

TSM Mount Request

TSM Automated Libraries

TSM Automated Library

TSM Manual Drive

TSM Automated Drives

TSM Automated Drive

TSM Domain Client Node

TSM Storage Pools

TSM Storage Pool

TSM Processes

TSM Process

68

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Baselines and Key Performance Indicators

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

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

69

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

IBM Spectrum Protect KMAttributes

Name Description Units Recommended AlertConditions

Attribute Type

Login Status Monitors the status ofthe TSM KM logindetails (username/password) for theoperating system andDSMADMC.

If no valid username/password is detectedfor the operatingsystem or DSMADMC,this attribute will beset to Failure. If thereare any suspiciouscommand exits, thisattribute will be set toSuspicious.

0 = OK1 =Suspicious2 = Failure

Warning = 1Alarm = 2

Collection Status

Monitoring Mode Monitors the failovermode of the TSM KM.By default TSM KMruns in PermanentSingle-node Mode.

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

n/a Collection Status

Node Status Monitors the errormessages generated forthe IBM SpectrumProtect application onthe managed system.



Availability

70IBM Spectrum Protect KM

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM ClientsAttributes


AttributeTypeType

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

%PSL pconfig("REPLACE",

"/Runtime/TSM/<node-id>/

TSMClientCollectorExecTi

me", 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:



TSMClientCollectorWarn",

3600);

Seconds Warning > presetvalue orobservedmaximum(default)

CollectionStatus

71 TSM Clients

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM ClientAttributes


Attribute Type

Last Access ElapsedTime

Displays the timeelapsed since the lastcommunication fromthe client.

Hours None Statistics

Space Used Displays the amount ofspace used on theclient node.

Gigabytes(GB)

None Statistics

State Displays the state ofthe client.

0 = Running1 = Locked2 = NeverCommunicated-1 =Unknown

None Availability

Status Displays the clientstatus. The followingState to Statusmapping rule is used:

NeverCommunicated >FailureUnknown > FailureLocked > SuspiciousAll other states > OK

0 = OK1 =Suspicious 2 = Failure

Warning = 1Alarm =2

Availability

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

72TSM Client

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM DaemonsAttributes


Attribute Type

Exec Time Inactive standard attributemonitors the collector executiontime. To activate this attribute,use the PSL below, and restart thePATROL Agent:



TSMDaemonsCollectorExecT

ime", 1);




TSMDaemonCollectorWarn",

3600);

Seconds Warning:> presetvalue orobservedmaximum(default)

CollectionStatus

73 TSM Daemons

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM DaemonAttributes


Attribute Type

CPU Duration Displays the CPUseconds consumed bythe daemon.

Seconds None Statistics

CPU Utilization Displays thepercentage of CPU used by the daemon.

Percentage(%)

None Statistics

Memory Size Displays the coreimage size of thedaemon in the virtualmemory.

Kilobytes(KB)

None Statistics

Processes Count Displays the number ofdaemon processes/threads found.

Processes None Statistics

State Displays the state ofthe daemon asreported in thecommand executed bythe data collector.

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

None Availability

Status Monitors the status ofthe daemon. Thefollowing State toStatus mapping rule isused:

Nonexistent/NotResponding > FailureNot Running >FailureTerminated orStopped >Suspicious

0 = OK1 =Suspicious 2 = Failure

None Availability

74TSM Daemon

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0


Attribute Type

Growing or Unknown> SuspiciousAll other states > OK


75 TSM Daemon

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM DatabasesAttributes


Attribute Type

Exec Time Inactive standard parametermonitors the collector executiontime. To activate this parameter,use the PSL below, and restart thePATROL Agent:



TSMDatabaseCollectorExec

Time", 1);




TSMDatabaseCollectorWarn

", 3600);


CollectionStatus

76TSM Databases

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM DatabaseAttributes


Attribute Type

Backup Elapsed * Displays the elapsedtime since the lastsuccessful databasebackup.


Buffer Request

Count *Displays thecumulative number ofrequests for databasepages since the bufferpool was last reset (orsince the server waslast started).

Count None Statistics

Cache Hit Percent * Displays (as apercentage of the totalnumber of requests)the number of requestsfor a database pagesthat are already in thebuffer pool.

Percentage(%)

None Statistics

Cache Wait Percent

*Displays (as apercentage of the totalnumber of requests)the number of requestsfor database bufferpool pages where nopages are available,because all pages arein use.

Percentage(%)

None Statistics

File System Space

Used Percent *Monitors thepercentage of spaceused by the file systemwhere the databaseresides.

Percentage(%)

Warning = 95-98 Alarm > 98

Statistics

Log Consumed Size * Displays thecumulativeconsumption of the logspace used by theserver since the lastreset of this attribute.

Megabytes(MB)

None Statistics

77 TSM Database

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0


Attribute Type

Log Pool Used

Percent *Displays (as apercentage of allrecovery log bufferpool pages) thenumber of buffer poolpages used to writechanges to therecovery log after atransaction iscommitted.

Percentage(%)

None Statistics

Log Pool Wait

Percent *Set by TSMDatabaseCollector.Displays (as apercentage of allrecovery log bufferpool requests) thenumber of requests forbuffer pool pageswhere no pages areavailable because all

pages are in use.

Percentage(%)

None Statistics

Pool Hit Percent * Displays (as apercentage of the totalnumber of requests)the number of requestsfor database pagesthat are already in thebuffer pool.

Percentage(%)

None

Reorg Elapsed * Displays the elapsedtime since the lastdatabasereorganization.


Space Available Monitors the amountof assigned spaceremaining availablefor use by the serverdatabase.

Megabytes(MB)

Warning = 2-5Alarm < 2

Availability

Space Changed * Displays the databasepages (in megabytes)that have changedsince the last backup.

Megabytes(MB)

None Statistics

Space Changed

Percent *Displays thepercentage of databasepages that havechanged since the lastbackup.

Percentage(%)

None Statistics

Space Growth Rate Displays the growthrate of the space usedby the server database.

Megabytesper second(MB/s)

None Statistics

78TSM Database

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0


Attribute Type

Space MaxExtension

Displays the maximumamount the databasecan be extended by.

Megabytes(MB)

None Statistics

Space MaxReduction

Displays the maximumamount the databasecan be reduced by.

Megabytes(MB)

Warning: 4-8Alarm: less than 4

Statistics

Space Used Displays the amount ofassigned space usedby the serverdatabase.

Megabytes(MB)

None Statistics

Space Used Percent Monitors thepercentage of assignedspace used by theserver database.

The total assignedspace is the usedspace (Space Used)plus the availablespace (SpaceAvailable).

Percentage(%)

None Statistics

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


79 TSM Database

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM LogsAttributes


Attribute Type




TSMLogCollectorExecTime",

1);

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



TSMLogCollectorWarn",

3600);


CollectionStatus

80TSM Logs

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM LogAttributes


Attribute Type

Alarm MessageCount

Monitors the numberof alarm messages.

Count Alarm > 1 Statistics

File Space GrowthRate*

Displays the growthrate of the amount ofspace used by the logfile.

Kilobytes persecond (KB/s)

None Statistics

File Space Used* Displays the amount ofspace used by the logfile.

Kilobytes(KB)

None Statistics

File System SpaceUsed Percent*

Monitors thepercentage of spaceused by the file system(where the log fileresides).

Percentage(%)

Warning = 95-98Alarm: > 98

Statistics

Space Available* Monitors theavailable space for thelog file to use (this isalso the availablespace on the filesystem).

Megabytes(MB)

Warning = 2-5Alarm < 2

Availability

Space Used Percent* Monitors thepercentage of capacityused by the log file.

The total capacity isthe used space (LogSpace Used) plusavailable space (LogSpace Available).

Percentage(%)

Warning = 95-98Alarm: > 98

Statistics

Warning MessageCount

Monitors the numberof warning messages.

Count Warning > 1 Statistics

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


81 TSM Log

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM DomainsAttributes


Attribute Type

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



TSMDomainCollectorExecTi

me", 1);




TSMDomainCollectorWarn",

3600);


CollectionStatus

82TSM Domains

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM DomainAttributes


Attribute Type

Backup Elapsed Displays the elapsedtime since the lastbackup for thisdomain, regardless ofcompletion status ofthe backup.


Backup Throughput Displays thethroughput of the lastsuccessful backup forthis domain.

Gigabytesper second(GB/s)

None Statistics

Full BackupDuration

Displays the durationof the last successfulfull backup for thisdomain.


Full BackupElapsed

Displays the elapsedtime since the lastsuccessful full backupfor this domain.


Full Backup ObjectCount

Displays the number ofobjects backed up inthe last successful fullbackup for thisdomain.


Full Backup Size Displays the size of thelast successful fullbackup for thisdomain.

Gigabytes(GB)

None Statistics

Incremental BackupDuration

Displays the durationof the last successfulincremental backup forthis domain.


Incremental BackupElapsed

Displays the elapsedtime since the lastsuccessful incrementalbackup for thisdomain.


Incremental BackupObject Count

Displays the number ofobjects backed up inthe last successfulincremental backup forthis domain.


83 TSM Domain

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0


Attribute Type

Incremental BackupSize

Displays the size of thelast successfulincremental backup forthis domain.

Gigabytes(GB)

None Statistics

State Displays the state ofthe domain.

0 = Idle1 = Running2 = Runningin RestrictedWindow3 = NotStarted4 = Inactive-1 =Unknown

None Availability

Status Monitors the status ofthe domain. Thefollowing State toStatus mapping rule isused:

Running in restrictedwindow > FailureRunning for morethan 600 minutes >SuspiciousUnknown >SuspiciousAll other states > OK


None Availability

Successful BackupElapsed

Displays the elapsedtime since the lastsuccessful backup forthis domain.

hours None Statistics


84TSM Domain

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM JobsAttributes


Attribute Type

Active BackupCount

Displays the number ofactive backup jobscurrently discoveredand monitored.


Active Count Displays the number ofactive jobs currentlydiscovered andmonitored.


Active Non-BackupCount

Displays the number ofactive non-backup jobscurrently discoveredand monitored.


Exec Time Inactive standardparameter monitorsthe collectorexecution time. Toactivate thisparameter, use thePSL below, andrestart the PATROLAgent:

%PSL

pconfig("REPLA

CE", "/

Runtime/TSM/

<node-id>/

TSMJobCollecto

rExecTime",

1);

When activated itwill run everyminute and trigger awarning when thecollector runs formore than theobserved maximumtime. This maximumtime can beoverridden by apreset value(example: 3600seconds), using thePSL below:

Seconds Warning > preset value orobserved maximum(default)

Collection Status

85 TSM Jobs

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0


Attribute Type

%PSL

pconfig("REPLA

CE", "/

Runtime/TSM/

<node-id>/

TSMJobCollecto

rWarn", 3600);


86TSM Jobs

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM JobAttributes


Attribute Type

Duration Displays the durationof the job from thestart.


Error Count Monitors the numberof client node errorslogged in the serveractivity log during thisjob.

Count Warning when > 100 Statistics

NetworkThroughput

Displays thethroughput of the jobon the network.


None Statistics

Object Count Displays the number ofobjects inspected forthis job.


Object ExpiredCount

Displays the totalnumber of objects forthis job that haveexpired.


Object Failed Count Displays the totalnumber of objects forthis job that havefailed.

Count Warning when > 100 Statistics

Object ProcessedCount

Displays the totalnumber of objects forthis job that have beenprocessed.


Object ReboundCount

Displays the totalnumber of objects forthis job that have beenrebound.


Object UpdatedCount

Displays the totalnumber of objects forthis job that have beenupdated.


Size Displays the amount ofdata backed up for thejob.

Megabytes(MB)

None Statistics

State Displays the state ofthe job.

0 =Completed1 = Future2 = Pending

None Availability

87 TSM Job

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0


Attribute Type

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

Status Monitors the status ofthe job. The followingState to Status mappingrule is used:

Missed, Severed, orFailed > FailurePending for morethan 1 hour >SuspiciousStarted for morethan 5 hours >SuspiciousRestarted for morethan 5 hours >SuspiciousCompleted/Errors >SuspiciousStarted/Errors >SuspiciousRestarted/Errors >SuspiciousAll other states > OK



Availability

Throughput Displays thethroughput of the job.


None Statistics


88TSM Job

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM Mount RequestsAttributes


Attribute Type




TSMRequestCollectorExecT

ime", 1);




TSMRequestCollectorWarn"

, 3600);


CollectionStatus

89 TSM Mount Requests

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM Mount RequestAttributes


Attribute Type

Elapsed Displays the elapsedtime since the mountrequest was issued.

Minutes None Statistics

State Displays the state ofthe mount request asreported in thecommand executed bythe data collector.

0 =Completed1= Pending-1 =Unknown

None Availability

Status Monitors the status ofthe mount request. Thefollowing State toStatus mapping rule isused:

Pending for morethan 30 minutes >FailurePending or Unknown> SuspiciousAll other states > OK



Availability

Timeout Displays the timeremaining until themount request timesout.

Minutes Alarm = 0-30 Statistics


90TSM Mount Request

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM Automated LibrariesAttributes


Attribute Type




TSMLibraryCollectorExecT

ime", 1);




TSMLibraryCollectorWarn"

, 3600);


CollectionStatus

91 TSM Automated Libraries

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM Automated LibraryAttributes


Attribute Type

State Displays whether thepath for the automatedlibrary is online oroffline. It will notperform any remoteautomated library testcommand on thestorage agent.

0 = Online1 = Offline2 = PathOffline-1 =Unknown

None Availability

Status Monitors the status ofthe automated library.



Availability

Up Drive Count Displays the numberup / online state drivesin this robotic library.


Volume Count Displays the totalnumber of volumeloaded in thisautomated library.


Volume PrivateCount

Displays the number ofprivate volumes in theautomated library.


Volume ScratchCount

Displays the number ofscratch volumes in theautomated library.


Volume ScratchPercent

Monitors thepercentage of scratchvolume against thetotal number of volumeloaded in thisautomated library.

Percentage(%)

None Statistics


92TSM Automated Library

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM Manual DriveAttributes


Attribute Type

State Displays the state ofthe automated librarydrive. This isdetermined from theautomated librarydrive controlinformation.

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

None Availability

Status Monitors the status ofthe automated librarydrive.

0 = OK 1 =Suspicious2 = Failure


Availability

93 TSM Manual Drive

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM Automated DrivesAttributes


Attribute Type




TSMDriveCollectorExecTime

", 1);




TSMDriveCollectorWarn",

3600);


CollectionStatus

94TSM Automated Drives

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM Automated DriveAttributes


Attribute Type

State Displays the state ofthe automated librarydrive. This isdetermined from theautomated librarydrive controlinformation.

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

None Availability

Status Monitors the status ofthe automated librarydrive



Availability

95 TSM Automated Drive

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM Domain Client NodeAttributes


Attribute Type

Backup Throughput

Displays thethroughput of the lastsuccessful backup forthis client node.


None Statistics

Last Full BackupDuration

Displays the durationof the last successfulfull backup for thisclient node.


Last Full BackupObject Count

Displays the number ofobjects backed up inthe last successful fullbackup for this clientnode.


Last Full Backup Size

Displays the size of thelast successful fullbackup for this clientnode.

Megabytes(MB)

None Statistics

Last IncrementalBackup Duration

Displays the durationof the last successfulincremental backupfor this client node.


Last IncrementalBackup ObjectCount

Displays the number ofobjects backed up inthe last successfulincremental backupfor this client node.


Last IncrementalBackup Size

Displays the size of thelast successfulincremental backupfor this client node.

Megabytes(MB)

None Statistics


96TSM Domain Client Node

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM Storage PoolsAttributes


Attribute Type




TSMPoolCollectorExecTime"

, 1);




TSMPoolCollectorWarn",

3600);


CollectionStatus

97 TSM Storage Pools

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM Storage PoolAttributes


Attribute Type

Space Available Monitors the availablevolume space for thebackup data to use inthis storage pool.

Gigabytes(GB)

Warning < 1Alarm = 0

Availability

Space Growth Rate Displays the growthrate of the total volumespace used by thebackup data in thisstorage pool.

Gigabytesper second(GB/s)

None Statistics

Space LogicalPercent

Displays the logicaloccupancy of thestorage pool as apercentage of the totaloccupancy.

Percentage(%)

None Statistics

Space Migrated Displays the amount ofdata that has beenmigrated, if migrationis in progress. Ifmigration is not inprogress, this valueindicates the amountof data migratedduring the lastmigration.Note: This attribute isnot available for copystorage pools.

Gigabytes(GB)

None Statistics

Space MigrationPercent

Displays an estimateof the percentage ofdata in the storagepool that can bemigrated.Note: This attribute isnot available for copystorage pools.

Percentage(%)

None Statistics

98TSM Storage Pool

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0


Attribute Type

Space MigrationElapsed

Displays the amount oftime that has elapsedsince migration of thestorage pool began, ifmigration is active. Ifmigration is not active,this value indicates theamount of timerequired to completethe last migration.Note: This attribute isnot available for copystorage pools.


Space Reclaimable Displays the amount ofspace in the storagepool that isreclaimable.

Gigabytes(GB)

None Statistics

Space ReclaimablePercent

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

Percentage(%)

None Statistics

Space Used Displays the totalvolume space occupiedby the backup data inthis storage pool.

Gigabytes(GB)

None Statistics

Space Used Percent Monitors thepercentage of totaloccupied volume spaceagainst the totalvolume capacity of thisstorage pool (notincluding any scratchvolumes).

Percentage(%)

Warning > 95Alarm > 98

Statistics

Volumes ActiveCount

Displays the number ofactive volumes in thisstorage pool.

Active volumes areavailable disk volumeswith a status of"Online" or tapevolumes with a statusof "Filling", where datahas been written butthe volume is not yetfull.


99 TSM Storage Pool

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0


Attribute Type

Volume ActivePercent

Monitors thepercentage of activevolumes against thetotal number ofvolumes in this storagepool.

Percentage(%)

None Statistics

Volume AvailableCount

Displays the number ofvolumes assigned tothis storage pool.


Volume AvailablePercent

Monitors thepercentage ofavailable volumesagainst the totalnumber of volumes inthis storage pool.

Percentage(%)

None Statistics

Volume Count Displays the totalnumber of volumes inthis storage pool.


Volume EmptyCount

Displays the number ofempty volumes in thisstorage pool.

Empty is a possiblestatus for a tapevolume, indicating thatno data is stored onthat volume.


Volume Full Count Displays the number offull volumes in thisstorage pool.


Volume Full Percent Monitors thepercentage of fullvolumes against thetotal number ofvolumes in this storagepool.

Percentage(%)

None Statistics

Volume OfflineCount

Displays the number ofoffline volumes in thisstorage pool.

"Offline" is a possiblestatus for a diskvolume.


Volume PendingCount

Displays the number ofpending volumes inthis storage pool.


100TSM Storage Pool

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0


Attribute Type

"Pending" is a possiblestatus for a tapevolume, where all fileshave been deleted buta delay has beenplaced on the volumebefore reuse.


101 TSM Storage Pool

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM ProcessesAttributes


Attributes Type




TSMProcessCollectorExecT

ime", 1);




TSMProcessCollectorWarn"

, 3600);


CollectionStatus

102TSM Processes

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

TSM ProcessAttributes


Attribute Type

Duration Displays the durationof the process.


Item Count Displays the number ofitems found.


Size Displays the processsize.

Megabytes(MB)

None Statistics

State Displays the state ofthe process.

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

None Availability

Status Monitors the status ofthe process. Thefollowing State toStatus mapping rule isused:

Completed/Failure >FailureRunning/Errors orUnknown >SuspiciousRunning for morethan 10 hours >SuspiciousAll other states > OK.



Availability

Throughput Displays thethroughput of theprocess.


None Statistics


103 TSM Process

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Managing Baselines and KeyPerformance IndicatorsTo detect abnormalities on the monitored environment, BMC TrueSight Operations Managementcalculates baselines per attribute based on values collected over a specified period of time todetermine a normal operating range. When the collected values for these parameters are out ofrange, an alert is triggered. Some attributes are identified by default as Key PerformanceIndicators (identified with the icon) and automatically included in the base lining calculation.

Managing baselines

The baseline is the expected normal operating range for an attribute of a monitor. There are twobaselines: Baseline High and Baseline Low. Baseline High represents the point at which 95% ofthe weighted average of the historical values fall below this value for the selected time period; Baseline Low represents the point at which 90% of the weighted average of historical values forthe selected time period fall above this line.

Baselines are generated for KPI attributes that have an active abnormality thresholds.

Managing Key Performance Indicators

Starting from v9.5 of BPPM, attributes that have not been initially designated in the KM as KeyPerformance Indicators (KPIs) cannot be flagged as KPIs from BPPM/TrueSight. Although enablingbaseline is possible through the Options > Administration > Intelligent Event Thresholds featureavailable in the Infrastructure Management Server operator console, BMC does not recommenddoing it.

For more information, refer to the BMC TrueSight Operations Management documentation available f romdocs.bmc.com.

https://docs.bmc.com/docs/dashboard.action

104

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Index

- A -Abnormalities 103

Access

Permissions 13

User 13Add Monitor Types 26

Attributes

Active Backup Count 84

Active Count 84

Active Non-Backup Count 84

Alarm Message Count 80

Backup Elapsed 76, 82

Backup Throughput 82, 95

Buffer Request Count 76

Cache Hit Percent 76

Cache Wait Percent 76

CPU Duration 73

CPU Utilization 73

Duration 86, 102

Elapsed 89

Error Count 86

Exec Time 70, 72, 75, 79, 81, 84, 88, 90,93, 96, 101

File Space Growth Rate 80

File Space Used 80

File System Space Used Percent 76, 80

Full Backup Duration 82

Full Backup Elapsed 82

Full Backup Object Count 82

Full Backup Size 82

Incremental Backup Duration 82

Incremental Backup Elapsed 82

Incremental Backup Object Count 82

Incremental Backup Size 82

Item Count 102

Last Access Elapsed Time 71

Last Full Backup Duration 95

Last Full Backup Object Count 95

Last Full Backup Size 95

Last Incremental Backup Duration 95

Last Incremental Backup Object Count 95

Last Incremental Backup Size 95

Log Consumed Size 76

Log Pool User Percent 76

Log Pool Wait Percent 76

Login Status 69

Memory Size 73

Monitoring Mode 69

Network Throughput 86

Node Status 69

Object Count 86

Object Expired Count 86

Object Failed Count 86

Object Processed Count 86

Object Rebound Count 86

Object Updated Count 86

Pool Hit Percent 76

Processes Count 73

Reorg Elapsed 76

Size 86, 102

Space Available 76, 80, 97

Space Changed 76

Space Changed Percent 76

Space Growth Rate 76, 97

Space Logical Percent 97

Space Max Extension 76

Space Max Reduction 76

Space Migrated 97

Space Migration Elapsed 97

Space Migration Percent 97

Space Reclaimable 97

Space Reclaimable Percent 97

Space Used 71, 76, 97

Space Used Percent 76, 80, 97

State 73, 82, 86, 89, 91, 92, 94, 102

Status 71, 73, 82, 86, 89, 91, 92, 94, 102

Successful Backup Elapsed 82

Throughput 86, 102

Timeout 89

Up Drive Count 91

Volume Active Percent 97

Volume Available Count 97

Volume Available Percent 97

Volume Count 91, 97

Volume Empty Count 97

Volume Full Count 97

Volume Full Percent 97

Volume Offline Count 97

Volume Pending Count 97

Volume Private Count 91

Volume Scratch Count 91

105

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Attributes

Volume Scratch Percent 91

Volumes Active Count 97

Warning Message Count 80Automated Drive

Maximum Instances 33Automated Drives

Debug 32Automated Libraries

Debug 32Automated Library

Maximum Instances 33

- B -Baseline 67

Baselines

BMC ProactiveNet Performance Management 103

Generation 103

Manage 103

Requirements 103Block

Monitoring 65BMC PATROL

Changes 11BMC ProactiveNet Performance Management

Abnormalities 103

Baselines 103

Key Performance Indicators 103

KPI 103Business Value 10

- C -Changes 7

Client

Maximum Instances 33Clients

Debug 32Cluster Application 36

Component Installation package

creating 23

downloading 24Configure

Domains 52

Hostname 56

Jobs 56


Monitoring Duration 56

Mount Request 62

Multi-node monitoring mode 36

Overrides 40

Processes 63Configuring

monitor settings 26Connection

SSH 18

WMI 18

- D -Daemon

Maximum Instances 33Daemons

Debug 32Databases

Debug 32Debug

Automated Drives 32

Automated Libraries 32

Clients 32

Daemons 32

Databases 32

Directory Path 32

Domains 32

End Time 32

Jobs 32

Logs 32

Mount Requests 32

Processes 32

Server 32

Storage Pools 32Disk Space Requirements 18

Domain

Maximum Instances 33Domain Client Node

Maximum Instances 33Domains

Configure 52

Debug 32Downloading 24

Duration

Duration 62, 63

Monitoring 62, 63

106

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

- F -Failover Group Name 36

Features 9

Fixed Issues 7

- G -Generate

Baselines 103Goals 9

- I -IBM Spectrum Protect 11

Changes 11Importing the Monitoring Solution 22

Improvements 7

Installing 24

Installing the Monitoring Solution 21

Instances

Automated Drive 33

Automated Library 33

Client 33

Deamon 33

Domain 33

Domain Client Node 33

Job 33

Log 33

Manual Drive 33

Mount Request 33

Process 33

Storage Pool 33

- J -JAVA 18

Job

Maximum Instances 33Jobs

Active 56

Configure 56

Debug 32

Monitoring 56

- K -Key Concepts 9



Manage 103KPI 67


Manage 103

- L -Log

Maximum Instances 33Logs

Debug 32

- M -Maintenance 65

Manage

Baselines 103


KPI 103Manual Drive

Maximum Instances 33Monitor Settings

configuring 26Monitor Type

TSM Clients 70

TSM Daemons 72

TSM Databases 75

TSM Logs 79Monitor Types

IBM Spectrum Protect KM 67, 69

TSM Automated Drive 94

TSM Automated Drives 93

TSM Automated Libraries 90

TSM Automated Library 91

TSM Automatic Drive 67

TSM Automatic Library 67

TSM Client 67, 71

TSM Daemon 67, 73

TSM Database 67, 76

TSM Domain 67, 82

107

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

Monitor Types

TSM Domain Client Node 67, 95

TSM Domains 81

TSM Job 67, 86

TSM Jobs 67, 84

TSM Log 67, 80

TSM Manual Drive 67, 92

TSM Mount Request 67, 89

TSM Mount Requests 88

TSM Process 67, 102

TSM Processes 101

TSM Storage Pool 67, 97

TSM Storage Pools 96Monitoring

Block 65

Blocked 65

Configure 62, 63

Duration 62, 63

Remotely 18

Stop 65

Stopped 65Monitoring Duration

Jobs 56Monitoring Node Names 36

Mount Request

Configure 62


Monitoring Duration 62Mount Requests

Debug 32Multi-node monitoring mode

Configure 36

- O -Overrides

Configure 40

DSM_CONFIG File 40

DSM_DIR Directory 40

DSM_LOG Directory 40

Local Temp Directory 40

Node Status Warnings 40

Node Type 40

Remote Temp Directory 40

TSM Installation 40

TSM Server Discovery 40

- P -Package 23, 24

Process

Configure 63


Monitoring Duration 63Processes

Debug 32

- R -Reference Guide 67

Remote Connection

Settings 18Remote PATROL Agent Checking 36

Requirements

Security 13

Software 11

System 11

- S -Security

Requirements 13Server

Debug 32Software

Requirements 11SSH 18

SSH Host Key

Authentication 18Storage Pool

Maximum Instances 33Storage Pools

Debug 32Sudo 13

System

Requirements 11

- T -TSM Server Discovery

Overrides 40

108

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

IBM

Sp

ectr

um P

rote

ct M

onit

orin

g V

ersi

on 3

.1.0

0

- W -WMI 18

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 TrueSight environment. Sentry Software alsodevelops adapters for BMC Atrium Orchestrator that enables IT administrators toautomate the execution of common requests and tasks that occur in the daily course ofIT operations. Combined with BMC’s servers and network automation tools, theadapters allow IT administrators to implement provisioning and decommissioningworkflows that cover all layers of their IT infrastructure. Finally, Sentry Software designsconnectors that bring storage capacity metrics into BMC TrueSight Capacity Optimizationto ensure IT administrators that their storage infrastructure is properly sized for theircurrent 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

Documents

BMC TrueSight Operations Management - Tivoli Storage Manager … · 2018-03-27 · BMC TrueSight Operations Management - IBM Spectrum Protect Monitoring STORAGE MONITORING USER DOCUMENTATION