BMC TrueSight Operations Management - Tivoli Storage ... · PDF file9 BMC TrueSight Operations...

BMC TrueSight OperationsManagement - Tivoli StorageManager Monitoring

STORAGE MONITORING

USER DOCUMENTATION

Version 3.0.00

January 2017

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 -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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 -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

http://www.bmc.com/support_home


http://www.sentrysoftware.com


4

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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

.....................................................................................................................................................................................27Configuring Monitor Settings

.......................................................................................................................................................................................29Configuring the Tivoli Storage Manager Solution

......................................................................................................................................................................301. Configuring Tivoli Storage Manager Servers Monitoring

......................................................................................................................................................................312. Configuring the User Account

......................................................................................................................................................................333. Configuring Advanced Settings

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

..........................................................................................................................................................................35Configuring Remote Connection Settings

..........................................................................................................................................................................36Configuring the Maximum Number of Instances

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

......................................................................................................................................................................42Enabling the Debug Mode

.......................................................................................................................................................................................45Configuring Other Monitor Types

......................................................................................................................................................................45Configuring Automated Drives

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

......................................................................................................................................................................47Configuring Clients

......................................................................................................................................................................48Configuring Daemons

......................................................................................................................................................................49Configuring Domains

......................................................................................................................................................................50Configuring Domain Client Nodes

......................................................................................................................................................................51Configuring Jobs

......................................................................................................................................................................52Configuring Logs

......................................................................................................................................................................53Configuring Manual Drives

5

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

......................................................................................................................................................................54Configuring Mount Requests

......................................................................................................................................................................55Configuring Processes

......................................................................................................................................................................56Configuring Storage Pools

......................................................................................................................................................................57Filtering Elements to Monitor

.....................................................................................................................................................................................61Tivoli Storage Manager KM

.....................................................................................................................................................................................62TSM Clients

.....................................................................................................................................................................................63TSM Client

.....................................................................................................................................................................................64TSM Daemons

.....................................................................................................................................................................................65TSM Daemon

.....................................................................................................................................................................................67TSM Databases

.....................................................................................................................................................................................68TSM Database

.....................................................................................................................................................................................71TSM Logs

.....................................................................................................................................................................................72TSM Log

.....................................................................................................................................................................................73TSM Domains

.....................................................................................................................................................................................74TSM Domain

.....................................................................................................................................................................................76TSM Jobs

.....................................................................................................................................................................................78TSM Job

.....................................................................................................................................................................................80TSM Mount Requests

.....................................................................................................................................................................................81TSM Mount Request

.....................................................................................................................................................................................82TSM Automated Libraries

.....................................................................................................................................................................................83TSM Automated Library

.....................................................................................................................................................................................84TSM Manual Drive

.....................................................................................................................................................................................85TSM Automated Drives

.....................................................................................................................................................................................86TSM Automated Drive

.....................................................................................................................................................................................87TSM Domain Client Node

.....................................................................................................................................................................................88TSM Storage Pools

.....................................................................................................................................................................................89TSM Storage Pool

.....................................................................................................................................................................................93TSM Processes

.....................................................................................................................................................................................94TSM Process

.....................................................................................................................................................................................95Managing Baselines and Key Performance Indicators

Release Notes for v3.0.00

7

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

What's NewTSM-14: BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring nowsupports multiple TSM server monitoring on local and remote hosts.

Changes and ImprovementsTSM-14: The overall performance of the Tivoli Storage Manager KM has been significantlyimproved.

TSM-155: Tivoli Storage Manager KM now fully supports the monitoring of librariescontrolled by ACSLS (StorageTek Automated Cartridge System Library Software).

TSM-371: Tivoli Storage Manager KM has been improved to support all PATROL Agent v10+versions and prevent failures due to a compatibility error.

Fixed IssuesTSM-380: The default actlog query limit has been modified to allow querying all actlogmessages since the last collection cycle (default: 300 minutes).

Key Concepts

9

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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

User Goals and Features

Business Value

Requirements

Note that for convenience and brevity, reference to BMC TrueSight Operations Management - Tivoli StorageManager Monitoring, may also be made as Tivoli Storage Manager KM.

User Goals and FeaturesTivoli Storage Manager 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 -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

Business ValueBMC TrueSight Operations Management - Tivoli Storage Manager Monitoring provides currentand historical information through a centralized console so you can easily view and manage yourentire Tivoli Storage Manager environment. The product collects and brings critical performancedata and useful metrics into the BMC TrueSight Operations Management environment andenables SAN Administrators to be warned whenever a problem occurs in their Tivoli StorageManager environment.

BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring:

Detects backup and restore errors

Ensures maximum data protection and maximum availability

Measures jobs progress

Helps diagnosing server problems

Analyzes trend

Detects disk or tapes space shortages

Ensures backups are successful

Helps identify bottlenecks and optimize backup domains.

11 Business Value

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

RequirementsBefore installing the Tivoli Storage Manager KM, verify the:

software requirements

system requirements

security requirements

remote monitoring requirements.

System RequirementsOperating System Operating System Version

Sun® microsystems SolarisTM 8, 9, 10, 11

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

IBM® AIXTM 5.1, 5.2, 5.3, 6.1

Red Hat® Linux® 7.2

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

Software RequirementsThe Tivoli Storage Manager KM supports the following platforms:

Software Version

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

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

BMC Software PATROL Agent 3.4.20, 3.5.x, 3.6.x, 3.7.x, 3.8.x, 3.9.x, 9.x, 10.x

BMC ProactiveNet Performance Manager 8.x, 8.5.x, 8.6.x, 9.x

BMC TrueSight Operations Management 10.x

Java 1.6 or higher

12Requirements

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

If you're running the Tivoli Storage Manager KM on LINUX, or Microsoft Windows x64 managednodes, please verify these additional software requirements:

Purpose Software Version

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

Sudo (superuser do) 1.6.7 or later

When running Tivoli StorageManager KM on AIX managednodes

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 Tivoli StorageManager KM on Linux managednodes

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

Any

When running Tivoli StorageManager 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

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



13 Requirements

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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

The following user accounts can be used:

On Unix platforms:

a root user

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

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

On Windows platforms:

an administrator user

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

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

Access Permissions

The Tivoli Storage Manager 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

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

14Requirements

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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

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

The Tivoli Storage Manager KM includes some scripts which should be executable by the PATROLAgent user and the Tivoli Storage Manager KM user. These scripts are stored under KM_HOMEpath, normally PATROL_HOME/lib/TSM.

To list all OS commands used by the Tivoli Storage Manager 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 -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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 Tivoli Storage Manager installation is identified by checking theregistry sub-keys under HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\.

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

Sudo User for Operating System Access

If a non-root user with sudo privileges is preferred as the Tivoli Storage Manager 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 Tivoli Storage Manager KMadministration and report menu commands using their sudo privileges. The Tivoli StorageManager KM accepts any non-root user with the following sudo configuration in the sudoers file.Please replace user1, user2, user3 with appropriate KM user name. The Tivoli Storage Managerinstallation 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 -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

On Solaris:

User_Alias TSMKMUSERS = user1, user2, user3

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

env_keep+="PATH LD_LIBRARY_PATH INSTALL_PATH KM_HOME KM_TEMP \

DSM_CONFIG DSM_DIR DSM_LOG",env_reset

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

INSTALL_PATH/server/bin/*,\

INSTALL_PATH/client/ba/bin/*,\

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

env_keep+="PATH LD_LIBRARY_PATH INSTALL_PATH KM_HOME KM_TEMP

\DSM_CONFIG DSM_DIR DSM_LOG",env_reset

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

On HP-UX:










On AIX & Linux:










Admin Interface User Access

BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring requires that anadministrator account (standard administrator with no other privileges) be added to the TivoliStorage Manager server for use by PATROL and the Tivoli Storage Manager KM.

17 Requirements

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

This account is used to query the configuration details and resource utilization of the serverthrough the Tivoli Storage Manager Administrative Client interface (DSMADMC). No changes aremade by this user on the Tivoli Storage Manager server - the Tivoli Storage Manager KM operatesin “read-only” mode for normal operation.

The suggested name for this DSMADMC user account is patrol and it can be created as part of theconfiguration procedure described in Configuring the KM User Accounts. Alternatively, the useraccount can be set up directly in TSM Server, and the details simply entered during KMconfiguration in the same way that the OS login details are entered. The password is stored inthe PATROL Agent 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 Tivoli Storage Manager KM, execute the followingPSL code from the PATROL Console, using “PSL Task” menu, after installing and loading the KM.

i=0;

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

{

ctl=pconfig("GET", var);

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

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

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

old_host=host;

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

if(host!=old_host)

{

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

i=0;

}

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

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

}

18Requirements

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

Disk Space RequirementsBMC TrueSight Operations Management - Tivoli Storage Manager 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 Tivoli Storage Manager KM is installed under the PATROL installation path.

When monitoring a standard installation of Tivoli Storage Manager, the PATROL Agent willgenerate approximately 500 KBytes of history data per day. An enterprise installation of TivoliStorage Manager on a server with multiple storage agents, clients, automated libraries, andmanual drives will generate more history data (as per other KMs used by the PATROL Agent).These history data files are recycled by PATROL depending on the PATROL Agent historyretention period.

During execution, the Tivoli Storage Manager KM creates and maintains temporary files under KM_HOME, KM_TEMP and KM_DEBUG paths. By default they are all under PATROL_HOME/lib/TSM, where PATROL_HOME path is normally /opt/bmc/Patrol3/ (on Unix) or C:\Program Files(x86)\BMC Software\Patrol3\ (on Microsoft Windows). Please make sure you have 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 theConfiguration > Paths menu from the main instance. These folder should have read, write andexecute permissions for both the PATROL Agent user and the KM login user.

Remote Monitoring RequirementsRemote monitoring is required for all servers on which no PATROL Agent can be installed. Thisfeature is also interesting if you lack resources or time to deploy a PATROL Agent and TivoliStorage Manager KM on several servers since it allows to monitor multiple hosts from onePATROL Agent.

Remote monitoring is not possible f rom a UNIX/Linux PATROL Agent system to a Windows-based TSMserver.

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

19 Requirements

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

JAVA

BMC TrueSight Operations Management - Tivoli Storage Manager Monitoring requires Java 1.6 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,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.

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.

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

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

Installing the Monitoring Solution

21

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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 Tivoli Storage Manager KM:

Importing Tivoli Storage Manager 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 -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

Importing the Monitoring Solutioninto Central AdministrationThe TrueSight Central Monitoring Repository includes the current versions of BMC TrueSightOperations Management - Tivoli Storage Manager 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.net/Products/index.asp

23 Importing the Monitoring Solution into CentralAdministration

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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 -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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 -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

You configure monitoring of Tivoli Storage Manager KM when you create a policy. A policy is atemplate containing the configuration of a PATROL Agent. A policy can be assigned to one ormore PATROL Agents using a unique tag (Central Monitoring Administration tag), and a PATROLAgent can be assigned one or more policies with different priorities.

If you have not already added the Central Monitoring Administration tag to your PATROL Agentsduring the solution installation, then you must manually assign the tag after you have configuredthe policy. For details, see Adding Central Monitoring Administration Tags.

27

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

Configuring Monitor SettingsWhen you create a policy, you can configure monitor types. The Add Monitor Types dialog boxpresents configuration fields for compatible BMC PATROL monitoring solutions that are locatedin the Central Monitoring Repository.

To configure the Monitor Type settings

To add a monitor type:

1. Log on to Central Monitoring Administration.

2. In the Navigation pane, click the Policies drawer and select a policy view (e.g. All).

3. Click Add .

4. Configure the policy general settings and click Next.

5. In the Monitoring Policy Configuration window, click Add .

6. From the Monitoring Solution menu, select Tivoli Storage Manager.

7. From the Version menu, select the required version.

28Configuring Monitor Settings

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

8. From the Monitor Type menu, select the required monitor:

Monitor Type Description

Tivoli Storage Manager KM To set the general settings of Tivoli Storage Manager KM (credentials, debugmode, instances, multi-node mode, etc.)

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

TSM Automated Library Enables access to the filtering options to select the automated librarieselements that will be monitored.

TSM Client Enables access to the filtering options to select the clients elements that willbe monitored.

TSM Daemon Enables access to the filtering options to select the daemons elements thatwill be monitored.

TSM Domain To:enable access to the filtering options to select the domains elements thatwill be monitoredset backup restrictions.

TSM Domain Client Node Enables access to the filtering options to select the domain client nodeselements that will be monitored.

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

TSM Manual Drive Enables access to the filtering options to select the manual drives elementsthat will be monitored.

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

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

TSM Storage Pool Enables access to the filtering options to select the storage pools elementsthat will be monitored.

29 Configuring Monitor Settings

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

Configuring the Tivoli Storage ManagerSolutionBefore using Tivoli Storage Manager KM, you'll have to configure its general settings. This sectionwill learn you how to:

Specify the Tivoly Storage Manager servers to be monitored.

Configure the user account.

Configure the remote connection settings.

Possibly configure the advanced settings (Discovery Overrides, debug mode, number ofinstances, and multi-node monitoring mode).


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

1. Configuring Tivoli Storage Manager Servers MonitoringTo specify the remote or local Tivoli Storage Manager server or the Tivoli Storage Managerappliance to be monitored:

1. Create a new monitor type.

2. From the Monitor Type menu, select Tivoli Storage Manager KM.

3. In the TSM Server section:

TSM Server Configuration

Enter the TSM server instance ID for the Tivoli Storage Manager server instance

Enter the Hostname, IP Address, or FQDN of the Tivoli Storage Manager server to bemonitored

Specify whether the Tivoli Storage Manager server is a UNIX/Linux or Windows system

Check Create a Device in the Console if you want the Tivoli Storage Manager server toappear as a separate device in TrueSight OM

4. You will then have to configure the user account to be used.


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

2. Configuring the User AccountAn operating system login as well as a TSM Admin Client login must be configured in BMCTrueSight Operations Management to monitor a Tivoli Storage Manager server. Refer to the Security Requirements chapter for detailed information about login requirement.

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

a root user

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

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

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

an administrator user

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


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

To configure the user account1. Specify the Tivoli Storage Manager Server to be monitored

2. Locate the TSM Credentials section:

3. To use:

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

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

(UNIX Only) If the user account has sudo privileges, check the Use Sudo box and indicatethe sudo binary file path (by default: /usr/local/bin/sudo)

4. (UNIX Only) If the user account has sudo privileges, check the Use Sudo box and indicate thesudo binary file path (by default: /usr/local/bin/sudo).

5. Specify the TSM Admin Client User ID and Password.

6. Indicate the DSMADMC file path on the PATROL Agent system. By default, the solutionsearches for the default TSM Backup Admin Client installation path.

7. Click Add to List.

8. (Optional) You can now configure advanced settings.


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

3. Configuring Advanced SettingsOnce the Tivoli Storage Manager server to be monitored and the account to be used arespecified, you can configure the following advanced settings:

The TSM server discovery overrides

The remote connection settings

The maximum number of instances

The multi-node monitoring mode

The debug mode

Configuring TSM Server Discovery Overrides (Optional)

The solution automatically discovers the Tivoli Storage Manager installation path, the DSM_DIRand DSM_LOG directory paths, the DSM_CONFIG file path, the temporary directory path used byTivoli Storage Manager KM, the node type, and the node status. This information can however beoverridden.

To configure TSM server discovery overrides1. Specify the Tivoli Storage Manager server to be monitored and the user account to be used.

2. In the Advanced Settings section, click the Discovery Overrides button.

Accessing Advanced Settings


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

3. The Discovery Overrides dialog is displayed.

Configuring Discovery Overrides Options

4. Provide the following information:

the TSM Installation path

the DSM_DIR Directory path

the DSM_CONFIG File path

the DSM_LOG Directory path

the Remote Temp Directory path

the Local Temp Directory path

The DSM_CONFIG f ile will contain the .opt f ile that specif ies the TSM server instance ID and the requiredconnection setting used by the TSM Admin Client to connect to the TSM server instance.

5. Configure the Node Type: Select the the Node Type (Server or Storage Agent).

6. Provide the Node Status Alarms and Warnings: Enter the regular expressions to determinethe Node Status in Alarm or Warning status. This regular expression will be used on theresult from DSMADMC command: "query status" on the TSM server.

7. Click Close.


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

Configuring Remote Connection SettingsIf you configured the monitoring of a remote host, you may want to specify the time after whichthe connection to the remote node will timeout or the maximum number of simultaneousconnections allowed to the remote node. This configuration is possible through the AdvancedSettings options.

To configure the remote connection settings1. Specify the Tivoli Storage Manager server to be monitored and the user account to be used.

2. In the Advanced Settings section, click the Advanced button.


3. The Advanced dialog is displayed.

Advanced Settings Options


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

4. In the Remote Connection Settings section, click Connection Settings.

5. Provide the required values:

Configuring Connection Settings

Connection Timeout (in Seconds): Enter the number of seconds after which the connectionto the remote node will timeout.

Maximum Connections: Enter the maximum number of simultaneous connections allowedto the remote node.

6. Click Close on all pop-ups.

7. Click Add to List in the main window.

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

Configuring the Maximum Number of Instances

By default, the solution monitors all the elements discovered, which may represent an importantworkload to the agents and servers. Because the monitoring of some elements may be irrelevantfor various reasons, you can configure the maximum number of instances to be monitored.

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

To configure the maximum number of instances1. Specify the Tivoli Storage Manager server to be monitored and the user account to be used.




BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00




BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

4. In the Maximum Number of Instances section, click Instance Max.

5. For each monitored element, indicate the maximum number of instances to be displayed:

Configuring Maximum Number of Instances

6. Enter 0 in the relevant field to disable the monitoring of a specific element.



Configuring the Multi-Node Monitoring Mode

If the Tivoli Storage Manager environment is installed in a cluster using Veritas Cluster Server,Veritas Cluster File System, Oracle Solaris Cluster or Microsoft Cluster, Tivoli Storage Manager KMmust be installed on all the cluster nodes to enable continuous monitoring and avoid single pointof failure. To avoid duplicate alerts from multiple nodes, it is recommended to configure thesolution to operate in multi-node monitoring mode.


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

To configure the multi-node monitoring mode1. Specify the Tivoli Storage Manager server to be monitored and the user account to be used.






BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

4. In the Multi-node Monitoring Mode section, click Multi-node Mode Config...

5. Configure the multi-node mode:

Configuring Multi-node Mode

6. Select the appropriate Cluster Application: Veritas Cluster Server, Veritas Cluster FileSystem, Oracle Solaris Cluster or Microsoft Cluster.

Indicate the Failover Group Name. Leave this field blank if you previously selected VeritasCluster File System. Then the Tivoli Storage Manager KM will monitor the entire clusterfrom the active master system, which is identified by the “vxdctl -c mode” command. Thismethod requires vxconfigd in enable mode with its clustered state active.

In the Monitoring Node Names field, name all the nodes where the solution is installed.The list must be delimited by commas.

7. (Optional) Allow the solution to check the monitoring mode of the remote PATROL Agents. Ifthe Remote PATROL Agent Checking is disabled, the solution will monitor actively throughactive master system or on the node where failover group is online and will not check themonitoring status of the other nodes through PATROL Agent:

Check the Enable Remote PATROL Agent Checking box.

Click the Remote Agent button. The following dialog box is displayed:


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

Configuring Remote Agent Settings

In the Monitoring Node Name field, indicate the cluster node used for multi-node modefailover

Indicate all the information required to communicate with the remote PATROL Agent(protocol, port number, and credentials)

In the Number of Attempts field, indicate how many times the solution will try tocommunicate with the remote PATROL Agent before failing over

Enter the timeout between attempts, in seconds

Click Add to List

Resume the procedure for all the nodes previously listed


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00



Tivoli Storage Manager will then be monitored through the active or online node. The othernodes, which are standing by for a failover, will be in passive multi-node mode and only the localTivoli Storage Manager components will be monitored.

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

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. Specify the Tivoli Storage Manager server to be monitored and the user account to be used.




BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00




BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

4. In the Debug Mode section, click Debug.

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

Configuring Debug Settings

5. In the Options section, indicate:

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

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

7. Click Close on all pop-ups

8. Click Add to the List in the main window.

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


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

Configuring Other Monitor TypesConfiguring Automated DrivesBy default, BMC TrueSight Operations Management - Tivoli Storage Manager Monitoringmonitors all the discovered automated drives for a local or remote TSM server. However, it ispossible to apply filters to specify whether or not specific drives will be monitored.

To configure the monitoring of automated drives1. Add or edit a monitor type and select TSM Automated Drive as a Monitor Type.

Configuring Automated Drives Monitoring

2. In the Hostname field, enter:

localhost to apply these settings to all PATROL Agents installed on Tivoli Storage Managerservers

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

3. (Optional) In the Filtering (automatically discovered), click Filtering to specify the drives thatwill be monitored.

4. (Optional) In the Additional Automated Drives (manual discovery), click Manual Add to addspecific drives you wish to monitor.


6. Click Add.

7. Finally, Update the policy.


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

Configuring Automated LibrariesBy default, BMC TrueSight Operations Management - Tivoli Storage Manager Monitoringmonitors all the discovered 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. Add or edit a monitor type and select TSM Automated Library as a Monitor Type.

Configuring Automated Libraries Monitoring




3. (Optional) In the Filtering (automatically discovered), click Filtering to specify the librariesthat will be monitored.

4. (Optional) In the Additional Automated Libraries (manual discovery), click Manual Add toadd specific libraries you wish to monitor.


6. Click Add.



BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

Configuring ClientsBy default, BMC TrueSight Operations Management - Tivoli Storage Manager Monitoringmonitors all the discovered clients for a local or remote TSM server. However, it is possible toapply filters to specify whether or not specific clients will be monitored.

To configure the monitoring of clients1. Add or edit a monitor type and select TSM Client as a Monitor Type.

Configuring Clients Monitoring




3. (Optional) In the Filtering (automatically discovered), click Filtering to specify the clients thatwill be monitored.

4. (Optional) In the Additional Clients (manual discovery), click Manual Add to add specificclients you wish to monitor.


6. Click Add.



BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

Configuring DaemonsBy default, BMC TrueSight Operations Management - Tivoli Storage Manager Monitoringmonitors all the discovered daemons for a local or remote TSM server. However, it is possible toapply filters to specify whether or not specific daemons will be monitored.

To configure the monitoring of daemons1. Add or edit a monitor type and select TSM Daemon as a Monitor Type.

Configuring Daemons Monitoring




3. (Optional) In the Filtering (automatically discovered), click Filtering to specify the daemonsthat will be monitored.

4. (Optional) In the Additional Daemons (manual discovery), click Manual Add to add specificdaemons you wish to monitor.


6. Click Add.



BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

Configuring DomainsBy default, BMC TrueSight Operations Management - Tivoli Storage Manager Monitoringmonitors all the discovered domains for a local or remote TSM server. However, it is possible toapply filters to specify whether or not specific domains will be monitored.

To configure the monitoring of domains1. Add or edit a monitor type and select TSM Domain as a Monitor Type.

Configuring Domains Monitoring





BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

3. (Optional) In the Filtering (automatically discovered), click Filtering to specify the domainsthat will be monitored.

4. (Optional) In the Additional Domains (manual discovery), click Manual Add to add specificdomains you wish to monitor.

5. 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 box

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

6. Click Add to list.

7. Click Add.

Configuring Domain Client NodesBy default, BMC TrueSight Operations Management - Tivoli Storage Manager Monitoringmonitors all the discovered domain client nodes for a local or remote TSM server. However, it ispossible to apply filters to specify whether or not specific domain client nodes will bemonitored.

To configure the monitoring of domain client nodes1. Add or edit a monitor type and select TSM Domain Client Nodes as a Monitor Type.

Configuring domain client nodes Monitoring


localhost to apply these settings to all PATROL Agents installed on Tivoli Storage Manager


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

servers


3. (Optional) In the Filtering (automatically discovered), click Filtering to specify the domainclient nodes that will be monitored.

4. (Optional) In the Additional Domain Client Nodes (manual discovery), click Manual Add toadd specific domain client nodes you wish to monitor.


6. Click Add.


Configuring JobsBy default, the Tivoli Storage Manager KM monitors all scheduled jobs that completedsuccessfully for 24 hours and any other scheduled job for 72 hours. This monitoring duration canhowever be modified to better suit your requirements.

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

To configure jobs1. Add or edit a monitor type and select TSM Job as a Monitor Type.

Configuring Tivoli Storage Manager Server Jobs




BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00


3. In the Monitoring Duration section:

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

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

5. Click Add to List

6. Click Add.


Configuring LogsBMC TrueSight Operations Management - Tivoli Storage Manager 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.

To customize the log scan limit1. Add or edit a monitor type

2. Select TSM Log as a Monitor Type.

Configuring the Logs Monitoring


localhost to apply these settings to all PATROL Agents installed on TSM Servers



BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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 Query Limit field, indicate the maximum query limit (in minutes). By defaultthe solution queries up to 300 minutes (5 hours) of actlog data.


7. Click Add.


Configuring Manual DrivesBy default, BMC TrueSight Operations Management - Tivoli Storage Manager Monitoringmonitors all the discovered manual drives for a local or remote TSM server. However, it ispossible to apply filters to specify whether or not specific drives will be monitored.

To configure the monitoring of manual drives1. Add or edit a monitor type and select TSM Manual Drive as a Monitor Type.

Configuring Manual Drives Monitoring





BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

3. (Optional) In the Filtering (automatically discovered), click Filtering to specify the drives thatwill be monitored.

4. (Optional) In the Additional Manual Drives (manual discovery), click Manual Add to addspecific drives you wish to monitor.


6. Click Add.


Configuring Mount RequestsBy default, the Tivoli Storage Manager 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. Add or edit a monitor type and select TSM Mount Request as a Monitor Type.

Configuring Mount Requests Monitoring




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


5. Click Add.


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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


To configure the monitoring of processes1. Add or edit a monitor type and select TSM Process as a Monitor Type.

Configuring Processes Monitoring




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


5. Click Add.


BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

Configuring Storage PoolsBy default, BMC TrueSight Operations Management - Tivoli Storage Manager Monitoringmonitors all the discovered storage pools for a local or remote TSM server. However, it ispossible to apply filters to specify whether or not specific storage pools will be monitored.

To configure the monitoring of storage pools1. Add or edit a monitor type and select TSM Storage Pool as a Monitor Type.

Configuring Storage Pools Monitoring




3. (Optional) In the Filtering (automatically discovered), click Filtering to specify the storagepools that will be monitored.

4. (Optional) In the Additional Storage Pools (manual discovery), click Manual Add to addspecific storage pools you wish to monitor.


6. Click Add.



BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

Filtering Elements to MonitorFiltering options are available for the following monitor types: TSM Automated Drive, TSMAutomated Library, TSM Client, TSM Daemon, TSM Domain, TSM Domain Client Node, TSMManual Drive, and TSM Storage Pool.

To filter elements to monitor1. Add or edit a monitor type

2. Select the Monitor Type for which you wish to apply filters.


localhost to apply these settings to all PATROL Agents installed on Tivoli Storage ManagerServers


4. Indicate which elements will be monitored:

Click the Filtering button

In the Keep Only... section, indicate the regular expression for the element to bemonitored and click Add to List

In the Exclude... section, indicate the regular expression for the element not to bemonitored and click Add To List

Resume procedure to keep and/or exclude as many elements as required

Click Close

5. If needed, manually add elements to be monitored:

Click the Manual Add button

Indicate the element to be monitored and click Add to List

Resume procedure to add as many elements as required

Click Close


7. Click Add.


Reference Guide

59

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

Introduction

This chapter provides statistical information about resources, operating status, and performancesmanaged by the Tivoli Storage Manager KM. It contains tables describing the attributes used inthe monitoring solution, grouped by Monitor Types, and provides a brief description of eachattribute and its default settings.

Monitor Types

Tivoli Storage Manager KM

TSM Clients

TSM Client

TSM Daemons

TSM Daemon

TSM Databases

TSM Database

TSM Logs

TSM Log

TSM Domains

TSM Domain

TSM Jobs

TSM Job

TSM Mount Requests

TSM Mount Request

TSM Automated Libraries

TSM Automated Library

TSM Manual Drive

TSM Automated Drives

TSM Automated Drive

TSM Domain Client Node

TSM Storage Pools

TSM Storage Pool

TSM Processes

TSM Process

60

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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

61

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

Tivoli Storage Manager 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 Tivoli StorageManager applicationon the managedsystem.



Availability

62Tivoli Storage Manager KM

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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

63 TSM Clients

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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.

64TSM Client

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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

65 TSM Daemons

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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

66TSM Daemon

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00


Attribute Type

Growing or Unknown> SuspiciousAll other states > OK


67 TSM Daemon

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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

68TSM Databases

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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

69 TSM Database

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00


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

70TSM Database

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00


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


71 TSM Database

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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

72TSM Logs

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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


73 TSM Log

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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

74TSM Domains

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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.


75 TSM Domain

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00


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


76TSM Domain

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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

77 TSM Jobs

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00


Attribute Type

%PSL

pconfig("REPLA

CE", "/

Runtime/TSM/

<node-id>/

TSMJobCollecto

rWarn", 3600);


78TSM Jobs

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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

79 TSM Job

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00


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


80TSM Job

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

TSM Mount RequestsAttributes


Attribute Type




TSMRequestCollectorExecT

ime", 1);




TSMRequestCollectorWarn"

, 3600);


CollectionStatus

81 TSM Mount Requests

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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


82TSM Mount Request

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

TSM Automated LibrariesAttributes


Attribute Type




TSMLibraryCollectorExecT

ime", 1);




TSMLibraryCollectorWarn"

, 3600);


CollectionStatus

83 TSM Automated Libraries

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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


84TSM Automated Library

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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

85 TSM Manual Drive

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

TSM Automated DrivesAttributes


Attribute Type




TSMDriveCollectorExecTime

", 1);




TSMDriveCollectorWarn",

3600);


CollectionStatus

86TSM Automated Drives

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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

87 TSM Automated Drive

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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


88TSM Domain Client Node

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

TSM Storage PoolsAttributes


Attribute Type




TSMPoolCollectorExecTime"

, 1);




TSMPoolCollectorWarn",

3600);


CollectionStatus

89 TSM Storage Pools

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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

90TSM Storage Pool

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00


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.


91 TSM Storage Pool

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00


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.


92TSM Storage Pool

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00


Attribute Type

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


93 TSM Storage Pool

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

TSM ProcessesAttributes


Attributes Type




TSMProcessCollectorExecT

ime", 1);




TSMProcessCollectorWarn"

, 3600);


CollectionStatus

94TSM Processes

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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


95 TSM Process

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

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

96

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

Index

- A -Abnormalities 95

Access

Permissions 13

User 13Add Monitor Types 27

Attributes

Active Backup Count 76

Active Count 76

Active Non-Backup Count 76

Alarm Message Count 72

Backup Elapsed 68, 74

Backup Throughput 74, 87

Buffer Request Count 68

Cache Hit Percent 68

Cache Wait Percent 68

CPU Duration 65

CPU Utilization 65

Duration 78, 94

Elapsed 81

Error Count 78

Exec Time 62, 64, 67, 71, 73, 76, 80, 82,85, 88, 93

File Space Growth Rate 72

File Space Used 72

File System Space Used Percent 68, 72

Full Backup Duration 74

Full Backup Elapsed 74

Full Backup Object Count 74

Full Backup Size 74

Incremental Backup Duration 74

Incremental Backup Elapsed 74

Incremental Backup Object Count 74

Incremental Backup Size 74

Item Count 94

Last Access Elapsed Time 63

Last Full Backup Duration 87

Last Full Backup Object Count 87

Last Full Backup Size 87

Last Incremental Backup Duration 87

Last Incremental Backup Object Count 87

Last Incremental Backup Size 87

Log Consumed Size 68

Log Pool User Percent 68

Log Pool Wait Percent 68

Login Status 61

Memory Size 65

Monitoring Mode 61

Network Throughput 78

Node Status 61

Object Count 78

Object Expired Count 78

Object Failed Count 78

Object Processed Count 78

Object Rebound Count 78

Object Updated Count 78

Pool Hit Percent 68

Processes Count 65

Reorg Elapsed 68

Size 78, 94

Space Available 68, 72, 89

Space Changed 68

Space Changed Percent 68

Space Growth Rate 68, 89

Space Logical Percent 89

Space Max Extension 68

Space Max Reduction 68

Space Migrated 89

Space Migration Elapsed 89

Space Migration Percent 89

Space Reclaimable 89

Space Reclaimable Percent 89

Space Used 63, 68, 89

Space Used Percent 68, 72, 89

State 65, 74, 78, 81, 83, 84, 86, 94

Status 63, 65, 74, 78, 81, 83, 84, 86, 94

Successful Backup Elapsed 74

Throughput 78, 94

Timeout 81

Up Drive Count 83

Volume Active Percent 89

Volume Available Count 89

Volume Available Percent 89

Volume Count 83, 89

Volume Empty Count 89

Volume Full Count 89

Volume Full Percent 89

Volume Offline Count 89

Volume Pending Count 89

Volume Private Count 83

Volume Scratch Count 83

97

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

Attributes

Volume Scratch Percent 83

Volumes Active Count 89

Warning Message Count 72Automated Drive

Maximum Instances 36Automated Drives

Debug 42Automated Libraries

Debug 42Automated Library

Maximum Instances 36

- B -Baseline 59

Baselines

BMC ProactiveNet Performance Management 95

Generation 95

Manage 95

Requirements 95BMC PATROL

Changes 11BMC ProactiveNet Performance Management

Abnormalities 95

Baselines 95

Key Performance Indicators 95

KPI 95Business Value 10

- C -Changes 7

Client

Maximum Instances 36Clients

Debug 42Cluster Application 38

Component Installation package

creating 23

downloading 24Configuration

Tivoli Storage Manager Settings 29Configure

Domains 49

Hostname 51

Jobs 51


Monitoring Duration 51

Mount Request 54

Multi-node monitoring mode 38

Overrides 33

Processes 55Configuring

monitor settings 27Connection

SSH 18

WMI 18Connection Timeout 35

- D -Daemon

Maximum Instances 36Daemons

Debug 42Databases

Debug 42Debug

Automated Drives 42

Automated Libraries 42

Clients 42

Daemons 42

Databases 42

Directory Path 42

Domains 42

End Time 42

Jobs 42

Logs 42

Mount Requests 42

Processes 42

Server 42

Storage Pools 42Domain

Maximum Instances 36Domain Client Node

Maximum Instances 36Domains

Configure 49

Debug 42Downloading 24

Duration

Duration 54, 55

Monitoring 54, 55

98

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

- F -Failover Group Name 38

Features 9

Filtering Options

TSM Automated Drive 57

TSM Automated Library 57

TSM Client 57

TSM Daemon 57

TSM Domain 57

TSM Domain Client Node 57

TSM Manual Drive 57

TSM Storage Pool 57Filters



TSM Client 57

TSM Daemon 57

TSM Domain 57

TSM Domain Client Node 57

TSM Manual Drive 57

TSM Storage Pool 57Fixed Issues 7

- G -Generate

Baselines 95Goals 9

- I -Importing the Monitoring Solution 22

Improvements 7

Installation

configuring 26Installing 24

Installing the Monitoring Solution 21

Instances

Automated Drive 36

Automated Library 36

Client 36

Deamon 36

Domain 36

Domain Client Node 36

Job 36

Log 36

Manual Drive 36

Mount Request 36

Process 36

Storage Pool 36

- J -JAVA 18

Job

Maximum Instances 36Jobs

Active 51

Configure 51

Debug 42

Monitoring 51

- K -Key Concepts 9



Manage 95KPI 59


Manage 95

- L -Log

Maximum Instances 36Logs

Debug 42

- M -Manage

Baselines 95


KPI 95Manual Drive

Maximum Instances 36Maximum Connections 35

Monitor Settings

configuring 27

99

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

Monitor Type

TSM Clients 62

TSM Daemons 64

TSM Databases 67

TSM Logs 71Monitor Types

Tivoli Storage Manager KM 59, 61


TSM Automated Drives 85

TSM Automated Libraries 82


TSM Automatic Drive 59

TSM Automatic Library 59

TSM Client 59, 63

TSM Daemon 59, 65

TSM Database 59, 68

TSM Domain 59, 74

TSM Domain Client Node 59, 87

TSM Domains 73

TSM Job 59, 78

TSM Jobs 59, 76

TSM Log 59, 72

TSM Manual Drive 59, 84

TSM Mount Request 59, 81

TSM Mount Requests 80

TSM Process 59, 94

TSM Processes 93

TSM Storage Pool 59, 89

TSM Storage Pools 88Monitoring

Configure 54, 55

Duration 54, 55

Remotely 18Monitoring Duration

Jobs 51Monitoring Node Names 38

Mount Request

Configure 54


Monitoring Duration 54Mount Requests

Debug 42Multi-node monitoring mode

Configure 38

- O -Overrides

Configure 33

DSM_CONFIG File 33

DSM_DIR Directory 33

DSM_LOG Directory 33

Local Temp Directory 33

Node Status Warnings 33

Node Type 33

Remote Temp Directory 33

TSM Installation 33

TSM Server Discovery 33

- P -Package 23, 24

Process

Configure 55


Monitoring Duration 55Processes

Debug 42

- R -Reference Guide 59

Remote Connection

Settings 18Remote Connection Settings

Connection Timeout 35

Maximum Connections 35Remote PATROL Agent Checking 38

Requirements

Security 13

Software 11

System 11

- S -Security

Requirements 13Server

Debug 42Software

Requirements 11SSH 18

SSH Host Key

Authentication 18Storage Pool

100

BM

C Tr

ueSi

ght

Ope

rati

ons

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

3.0

.00

Storage Pool

Maximum Instances 36Storage Pools

Debug 42Sudo 13, 31

System

Requirements 11

- T -Tivoli Storage Manager

Changes 11Tivoli Storage Manager Settings 29

TSM Server Discovery

Overrides 33

- U -UNIX 31

User Account

Configure 31

patrol 31

Privileges 31

Sudo 31

- W -Windows 31

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

BMC TrueSight Operations Management - Tivoli Storage ... · PDF file9 BMC TrueSight Operations...

Documents

Transcript of BMC TrueSight Operations Management - Tivoli Storage ... · PDF file9 BMC TrueSight Operations...