TrueSight Operations Management - EMC NetWorker Monitoring

TrueSight Operations Management -EMC NetWorker Monitoring

STORAGE MONITORING

USER DOCUMENTATION

Version 3.0.00

August 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

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

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

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

http://www.bmc.com/support_home


http://www.sentrysoftware.com


4

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

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

.....................................................................................................................................................................................9Business Value

.....................................................................................................................................................................................10Requirements

.......................................................................................................................................................................................10System Requirements

.......................................................................................................................................................................................10Software Requirements

.......................................................................................................................................................................................12Security Requirements

.......................................................................................................................................................................................17Remote Monitoring Requirements

.....................................................................................................................................................................................18Installing the Monitoring Solution

.......................................................................................................................................................................................19Importing the Monitoring Solution into TrueSight

.......................................................................................................................................................................................20Creating the Installation Package

.......................................................................................................................................................................................21Downloading the Installation Package

.......................................................................................................................................................................................21Installing the Package

.....................................................................................................................................................................................23Configuring Monitor Settings

.......................................................................................................................................................................................25Configuring EMC NetWorker KM

......................................................................................................................................................................26Configuring NetWorker Server Monitoring

..........................................................................................................................................................................27Configuring the User Account

..........................................................................................................................................................................28Configuring the NetWorker Server Discovery Overrides (Optional)

..........................................................................................................................................................................30Enabling the Debug Mode

..........................................................................................................................................................................31Configuring the Remote Connection Settings

..........................................................................................................................................................................32Configuring the Maximum Number of Instances

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

.......................................................................................................................................................................................36Configuring Other Monitor Types

......................................................................................................................................................................37Configuring NetWorker Clients

......................................................................................................................................................................39Configuring NetWorker Daemons

......................................................................................................................................................................41Configuring NetWorker Groups

......................................................................................................................................................................43Configuring NetWorker Jukeboxes

......................................................................................................................................................................45Configuring NetWorker Group Clients

......................................................................................................................................................................47Configuring NetWorker Jukebox Devices

......................................................................................................................................................................49Configuring NetWorker Logs (Scan Limit)

......................................................................................................................................................................50Configuring NetWorker Pending Requests

......................................................................................................................................................................53Configuring NetWorker Save Groups

......................................................................................................................................................................55Configuring NetWorker Standalone Devices

5

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

......................................................................................................................................................................57Configuring NetWorker Storage Nodes

......................................................................................................................................................................59Configuring NetWorker Volume Pools

.......................................................................................................................................................................................61Blocking the Monitoring of Servers

.....................................................................................................................................................................................64EMC NetWorker KM

.....................................................................................................................................................................................65NetWorker Client

.....................................................................................................................................................................................66NetWorker Clients

.....................................................................................................................................................................................67NetWorker Daemon

.....................................................................................................................................................................................68NetWorker Daemons

.....................................................................................................................................................................................69NetWorker Database

.....................................................................................................................................................................................70NetWorker Databases

.....................................................................................................................................................................................71NetWorker Group

.....................................................................................................................................................................................73NetWorker Groups

.....................................................................................................................................................................................74NetWorker Group Client

.....................................................................................................................................................................................75NetWorker Jukebox

.....................................................................................................................................................................................77NetWorker Jukeboxes

.....................................................................................................................................................................................78NetWorker Jukebox Device

.....................................................................................................................................................................................80NetWorker Log

.....................................................................................................................................................................................81NetWorker Logs

.....................................................................................................................................................................................82NetWorker Storage Nodes

.....................................................................................................................................................................................83NetWorker Storage Node

.....................................................................................................................................................................................84NetWorker Pending Requests

.....................................................................................................................................................................................85NetWorker Pending Request

.....................................................................................................................................................................................86NetWorker Save Client

.....................................................................................................................................................................................87NetWorker Save Group

.....................................................................................................................................................................................89NetWorker Save Groups

.....................................................................................................................................................................................90NetWorker Standalone Device

.....................................................................................................................................................................................92NetWorker Standalone Devices

.....................................................................................................................................................................................93NetWorker Volume Pools

.....................................................................................................................................................................................94NetWorker Volume Pool

.....................................................................................................................................................................................96Managing Baselines and Key Performance Indicators

Release Notes for v3.0.00

7

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

What's NewNSR-196: EMC NetWorker KM now fully supports EMC NetWorker v9.x.

NSR-241: EMC NetWorker KM can now monitor consecutive backups at save set level undereach group client (see Configuring Save Groups for detailed information).

NSR-259: EMC NetWorker KM now supports remote NetWorker server monitoring.

NSR-296: The monitoring of remote servers can be blocked from the remote node, to avoidunnecessary alerts and notifications (see Blocking the Remote Monitoring of an EMCNetWorker Server for detailed information).

Changes and ImprovementsNSR-153: The status of the EMC NetWorker storage nodes is now monitored from theNetWorker server through NetWorker Media Server monitor type.

Fixed IssuesNSR-247: On UNIX/Linux platforms, standalone device instance labels are now correctlyprefixed with the storage node name.

NSR-253: EMC NetWorker KM now properly takes user-configured log scan limit into account.

Key Concepts

9

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

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 TrueSight Operations Management - EMC NetWorkerMonitoring, may also be made as EMC NetWorker KM.

User Goals and FeaturesEMC NetWorker KM enables you to monitor the following in your environment:

Server availability: status of all the processes.

Log files: monitoring of the daemon.log and messages files, size, etc.

Pending Media Events: monitoring of the media mount requests

Bootstrap Messages: bootstrap settings verification, recommendations, etc.

Client Indexes: number of entries, utilization as a percentage and index size.

Devices: status of mounted volumes and history of volume mounts.

Save Groups and Save Sets: status, progress, size and duration

Business ValueTrueSight Operations Management - EMC NetWorker Monitoring provides current and historicalinformation through a centralized console so you can easily view and manage your entire EMCNetWorker environment. The product collects and brings critical performance data and usefulmetrics into the TrueSight Operations Management environment and enables Backup andStorage Administrators to be warned whenever a problem occurs in their EMC NetWorkerenvironment.

TrueSight Operations Management - EMC NetWorker Monitoring:

Detects backup and restore errors

Monitors Storage/Library availability

Detects abnormalities around backups and performances

Helps to analyze trends on storage capacity

Helps to identify bottlenecks and optimize the backup system performance.

10Requirements

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

RequirementsBefore installing the EMC NetWorker KM, verify the:

system requirements

software requirements

security requirements

remote monitoring requirements.

System RequirementsTrueSight Operations Management - EMC NetWorker Monitoring supports the followingoperating systems:

Operating System Operating System Version

Oracle/Sun SolarisTM 8.0 and higher

HP-UX 11 and higher

IBM® AIXTM 5.1 and higher

Red Hat® Linux® 7.2 and higher

Microsoft® Windows® 2003 and higher

Software RequirementsEMC NetWorker KM supports:

Software Version

EMC NetWorker 8.x and higher

BMC Software PATROL Agent Any version

BMC Software PATROL Console Any version

BMC Portal 2.3 and higher

BMC ProactiveNet Performance Manager 9.5 and higher

BMC TrueSight Operations Management 10 and higher

Java 1.8 or higher

11 Requirements

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Additional Software Requirements

If you are running the EMC NetWorker KM with sudo user account, or on AIX, LINUX, or MicrosoftWindows x64 managed nodes, please verify these additional software requirements:

Purpose Software Version

When running EMC NetWorker KM withsudo user account on Solaris, HP-UX, AIX orLinux managed nodes

Sudo (superuser do) 1.6.7 or later

When running EMC NetWorker KM on Linuxmanaged nodes

Korn shell binary (/bin/ksh) Any

When running EMC NetWorker KM onMicrosoft Windows 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 from the managed node to obtain the correct patch forthat platform.

Changes to BMC PATROL

To improve the performance of the EMC NetWorker KM, the PATROL Agent tuning variable /AgentSetup/AgentTuning/pslInstructionMax should be disabled by setting it to 0 (zero) orincreased to at least 5,000,000. This applies for all EMC NetWorker servers and storage nodeswhere the KM is installed. This adjustment will allow the KM data collectors to execute withoutincurring an internal scheduling delay.

This PATROL Agent tuning variable can be updated using wpconfig (on Microsoft Windows) orxpconfig (on UNIX)or PATROL Configuration Manager (PCM). Alternatively, you can use thefollowing single line PSL command through the PATROL Console OS> prompt to update thistuning variable.

To disable the pslInstructionMax variable %PSL pconfig("REPLACE",

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

To set the tuning variable to at 5,000,000:%PSL v="/AgentSetup/AgentTuning/pslInstructionMax";

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

In large EMC NetWorker systems, the value of 5,000,000 for the tuning variable pslInstructionMax may stillbe insuf f icient. In such situations, error messages will appear on the PATROL Console System OutputWindow (SOW) reporting that some EMC NetWorker KM data collectors are in an inf inite loop. In this caseyou can set the tuning variable to zero to disable this functionality.

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

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

12Requirements

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

The KM stores all configuration information in the PATROL Agent configuration database(pconfig), under the /NSR/<node-id> and /Runtime/NSR/<node-id> paths. PATROL Agent user(default: patrol) should be able to read and write to these pconfig variables at anytime. If AccessControl List (ACL) is used to control which users are authorized to connect to a PATROL Agent,please ensure that the mode for PATROL Agent user includes “C” in the PATROL Agent variable /AgentSetup/accessControlList. Please refer the PATROL Agent Ref erence Manual for moredetails.

To support bash shell platforms when ksh is not installed

To collect NetWorker stats when ksh was not installed on UNIX/Linux servers, you need to createa soft link for /bin/ksh to /bin/bash:

ln –s /bin/bash /bin/ksh

Security RequirementsA user account with administrative privileges must be configured in BMC PATROL to read andexecute EMC NetWorker 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 EMC NetWorker to executeapplication programs and access file systems

a non-root account, such as patrol, configured in the EMC NetWorker application toadminister the EMC NetWorker application.

On Windows platforms:

an administrator user

a non-administrator account, such as patrol, configured in the EMC NetWorker applicationto administer the EMC NetWorker application. Refer to the EMC NetWorker SystemAdministrator’s Guide for details on how to set up this type of account.

The user login details are configured in the KM. The password is encrypted and stored in thePATROL Agent.

Access Permissions

The EMC NetWorker KM user needs “read & execute” permission to executable and library filesunder the paths listed below. The EMC NetWorker installation path INSTALL_PATH is normally:

13 Requirements

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

/nsr or /opt/nsr or /opt/networker (on Unix)

C:\Program Files\nsr (on MS Windows).

Executable and Library Files accessed by the EMC NetWorker KM User

Unix Microsoft Windows

INSTALL_PATH/bin INSTALL_PATH\bin

INSTALL_PATH/lib

/usr/bin

/usr/sbin

/usr/sbin/nsr

/usr/lib/nsr

/etc/LGTOuscsi

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)

cluster (in Microsoft Cluster)

The EMC NetWorker KM includes some scripts which should be executable by the PATROL Agentuser and the NetWorker KM user. These scripts are stored under KM_HOME path, normallyPATROL_HOME/lib/NSR.

14Requirements

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

To list all OS commands used by the EMC NetWorker KM, execute the following PSL code fromthe PATROL Console, using PSL Task menu, after installing and loading the KM.

foreach var (grep("^/Runtime/NSR/.*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

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Paths and Files Accessed by PATROL Agent User

Unix Microsoft Windows

INSTALL_PATH/res INSTALL_PATH\res

INSTALL_PATH/index INSTALL_PATH\index

INSTALL_PATH/mm INSTALL_PATH\mm

INSTALL_PATH/logs/daemon.log INSTALL_PATH\logs\daemon.log

INSTALL_PATH/logs/messages INSTALL_PATH\logs\messages

INSTALL_PATH/logs/summary INSTALL_PATH\logs\summary

INSTALL_PATH\logs\savegrp.log

/var/adm/messages (on Solaris)

/var/adm/syslog/syslog.log (on HP-UX)

On Windows platforms the EMC NetWorker installation is identified by checking the MicrosoftWindows Registry. Depending on whether you are using a 32/64-bit OS and/or 32/64-bitApplication, the Registry entries are stored in different locations:

“HKEY_LOCAL_MACHINE\SOFTWARE\Legato\NetWorker\” and “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Legato\NetWorker\”.

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 KM user, configure the account as asudoer through the visudo utility using code appropriate for your platform as detailed below.This user should be able to execute NetWorker commands and OS commands.

The code below also applies to all non-root users who may execute EMC NetWorker KMadministration and report menu commands using their sudo privileges. The EMC NetWorker KMaccepts any non-root user with the following sudo configuration in the sudoers file. Pleasereplace user1, user2, user3 with appropriate KM user name. The EMC NetWorker installation pathINSTALL_PATH, referenced below is normally /nsr, /opt/nsr or /opt/networker andPATROL_HOME is the path where the PATROL Agent is installed (including the target, like /opt/bmc/Patrol3/Solaris29-sun4/).

16Requirements

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

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

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

On Solaris:

User_Alias NSRKMUSERS = user1, user2, user3

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

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

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

/usr/sbin/nsr/*,/etc/LGTOuscsi/*\

INSTALL_PATH/bin/*,\

PATROL_HOME/lib/NSR/*,PATROL_HOME/bin/*

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

On HP-UX:



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






On AIX and Linux :



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






17 Requirements

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Remote Monitoring RequirementsRemote monitoring is required for all servers or appliances on which no PATROL Agent can beinstalled. This feature is also interesting if you lack resources or time to deploy a PATROL Agentand EMC NetWorker KM on several servers since it allows to monitor multiple hosts from oneagent.

Remote monitoring is not possible from a UNIX/Linux PATROL Agent system to a Windows-basedNetWorker server.

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

JAVA

EMC NetWorker KM requires Java 1.8 or higher and a Java Runtime Environment (JRE) to beinstalled on the same system that runs the PATROL Agent.

The KM will automatically detect the JRE path if it has been installed in the default location orunder the BMC PATROL Agent installation path. If it has been installed in a different location, youwill have to set JAVA_HOME for the Patrol Agent default account before starting the PATROLAgent.

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

SSH/WMI Connection

An SSH (UNIX/Linux platforms) or a WMI (Windows platforms) connection is required to monitorremote NetWorker servers. When using an SSH connection, the SSH host key authenticationmust be disabled on the remote host.

Disabling the SSH Host Key Authentication

SSH host key authentication is enabled by default on most NetWorker 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/SymantecNetBackupKM_Downloads.asp

http://www.sentrysoftware.com/Products/SymantecNetBackupKM_Downloads.asp

18Installing the Monitoring Solution

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Installing the Monitoring SolutionOnce the latest version of the solution has been loaded into TrueSight Presentation Server,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 Presentation Server from the server where they want to install the package,download it and launch the installation.

This section describes the different steps to follow to install EMC NetWorker KM:

Importing EMC NetWorker KM into TrueSight Presentation

Creating the Installation Package

Downloading the Installation Package

Installing the Package

19 Installing the Monitoring Solution

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Importing the Monitoring Solution intoTrueSightThe TrueSight Central Monitoring Repository includes the current versions of TrueSightOperations Management - EMC NetWorker Monitoring that you can use with BMC TrueSight. Ifthe version available in the Repository does not correspond to the latest one, you will have tomanually import it:

1. Log on to the TrueSight Console.

2. From the navigation pane, select Administration > Repository.

3. Click the Installation Components tab.

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. Click Import.

6. Select Single solution.

7. Browse to the .zip source file.

8. Click Import.

The selected archive file is imported to the repository.

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

20Installing the Monitoring Solution

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

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

1. Log on to the TrueSight Console.


3. Click the Deployable Packages tab.

4. Click Create Deployable Package.

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

6. Select the solution(s) to be included in the package, specify their version, and click Next.

7. Specify the Installation Directory and click Next.

8. Provide the PATROL 3.x Product Directory and click Next.

9. Specify the BMC Product Startup Information and click Next.

10. Provide the following information:

Name: Enter a unique name for the package.

(Optional) Description: Enter a description of the package.

Format: Select a file compression format for the package.

9. Click Save.

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

21 Installing the Monitoring Solution

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

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.

1. Log on to the TrueSight Console from the computer on which the PATROL Agent is installedor to be installed.


3. Click the Deployable Packages tab.

4. (Optional) To filter the list of installation packages, select an operating system .

5. Click the action menu for the installation package required and click Download.

6. Save the installation package.

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

1. Download the installation package.

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

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

Configuring After Installation

23 Configuring Monitor Settings

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Configuring Monitor SettingsThe configuration of Monitor Types is performed through policies. Policies enable administratorsto deploy configurations on PATROL Agents and monitoring solutions, such as EMC NetWorkerKM in an automated way. Policies are designed to define and configure monitoring criteria andapply them to selected PATROL Agents. The configuration criteria are automatically pushed tothe PATROL Agents on which the policy is applied. When a monitoring policy is applied to aPATROL Agent, the device is automatically added to the list of monitored devices.

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

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

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

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

Step 1 - Define the General Properties

Property Description

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

Description (Optional) A brief description about the policy.

Associated UserGroup

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

Share with UserGroup

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

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

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

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

24Configuring Monitor Settings

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

1. Select a property.

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

3. Specify a value for the selected property.

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

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

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

Step 3 - Select the EMC NetWorker Monitor Type1. Click the Monitoring tab.

2. Click Add Monitoring Configuration.

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

From the Monitoring Solution menu, select EMC NetWorker.

From the Version menu, select the required version.

The Monitor Profile is automatically selected.

Select the Monitor Type. IMPORTANT: The EMC NetWorker KM monitor type must becreated first. You will then be able to configure the monitoring of any other monitor types:

Monitor Type Description

EMC NetWorker KM To set the general settings of EMC NetWorker KM (credentials, debugmode, instances, multi-node mode, etc.)

NetWorker Client Enables access to the filtering options to select the clients that will bemonitored.

NetWorker Daemon Enables access to the filtering options to select the daemons that will bemonitored.

NetWorker Group To:enable access to the filtering options to select the groups that will bemonitored.set backup restrictions.

NetWorker Group Client Enables access to the filtering options to select the group clients that willbe monitored.

NetWorker Jukebox Enables access to the filtering options to select the jukeboxes that will bemonitored.

NetWorker JukeboxDevices

Enables access to the filtering options to select the jukebox devices thatwill be monitored.

NetWorker Log Enables access the to log scan limit settings.

NetWorker PendingRequest

To indicate:how long the pending requests will be monitored.the date/time format used in NetWorker pending request messages.


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Monitor Type Description

NetWorker Save Group To indicate:how long the save groups in OK, Suspicious, and Failure status will bemonitoredwhich saved clients will be monitored (None, Failed only, SucceededOnly, All)

NetWorker StandaloneDevice

Enables access to the filtering options to select the standalone devicesthat will be monitored.

NetWorker Storage Node Enables access to the filtering options to select the storage nodes thatwill be monitored.

NetWorker Volume Pools Enables access to the filtering options to select the volume pools that willbe monitored.

4. Click Save to apply the new EMC NetWorker Monitor Type configurations to the selectedPATROL Agent(s).

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

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

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

action button and click Edit.

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

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

5. Customize the configuration.

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

Configuring EMC NetWorker KMBefore using EMC NetWorker KM, you will have to configure its general settings. This section willlearn you how to:

configure NetWorker server monitoring

configure the user account

enable the debug mode

configure the remote connection settings

configure the maximum number of instances

configure the multi-node monitoring mode

configure the NetWorker server discovery overrides (Optional).

Once you have created and configured the EMC NetWorker KM Monitor Type, you can create andcustomize other Monitor Types according to the component(s) you wish to monitor.


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Configuring NetWorker Server MonitoringSpecify the options that will constitute the NetWorker Monitoring Settings.

1. Create or edit a policy

2. From the Add Monitoring Configuration panel, click Add to add and configure the NetWorkerserver you wish to monitor:

Adding a NetWorker Server to the Monitoring Environment

2. In the NetWorker Server section, identify the server that you wish to monitor. For:

local monitoring:

enter localhost to apply the settings to all PATROL Agents installed on NetWorkerServers and Storage Nodes

(Optional) Select the System Type installed on the specified NetWorker server.

remote monitoring: provide the Hostname, IP address or FQDN of a specific NetWorkerserver to remotely monitor it from the PATROL Agent. You will then have to configure theremote monitoring settings.

3. Click the Create a Device in the Console option if you want the NetWorker server to appearas a separate device in TrueSight.

4. Configure the User Account you wish to use to monitor the specified NetWorker server.

5. Define the Device Advanced Settings:

the debug mode

the maximum number of instances

the multi-node monitoring mode

the NetWorker Server discovery overrides (Optional).

6. Click OK to validate.


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Configuring the User Account

A user account with administrative privileges must be configured in TrueSight OperationsManagement to read and execute EMC NetWorker application programs and file systems.Depending on the operating systems used, several options will be available.

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

a root user

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

a non-root account, such as patrol, configured in the EMC NetWorker application toadminister the EMC NetWorker application.

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

an administrator user

a non-administrator account, such as patrol, configured in the EMC NetWorker application toadminister the EMC NetWorker application.

For more information, refer to Security Requirements.

To configure the user account1. From the Add Monitoring Configuration panel, Add or Edit the NetWorker Monitoring

Settings.

2. Scroll down to the NetWorker Credentials section.

Configuring NetWorker Credentials

3. Set the NetWorker Credentials:

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


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

(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. Scroll down to the Advanced section if you need to configure:

the debug mode

the remote connection settings



the NetWorker Server discovery overrides (Optional).


Configuring the NetWorker Server Discovery Overrides (Optional)

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

Altering these paths may impact the operation of EMC NetWorker KM.

To configure NetWorker server discovery overrides1. From the Add Monitoring Configuration panel, Add or Edit the NetWorker Monitoring

Settings.

2. Scroll down to the Discovery Overrides section.

Configuring NetWorker Discovery Overrides


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

3. Specify the NetWorker Discovery Overrides options:

NetWorker installation Path: Provide the path to the directory where the NetWorkersoftware is installed. By default, EMC NetWorker KM automatically locates the NetWorkersoftware installation directory if you have installed the solution with the defaultrecommended settings. If you have chosen to install the solution in a custom directory,you are required to provide its location.

Remote Temp Directory Path: Provide the path to the directory where the temporary filesare saved on remote nodes (Default is /var/temp for UNIX/Linux or C:\Windows\Temp forWindows).

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

Node Type: Select the node type (Server or Storage Node).

Node Status Daemons: Specify the critical NetWorker node daemons in order to detect thenode status. Daemons names must be comma-delimited.

4. Scroll down to the Advanced section if you need to configure:

the debug mode

the remote connection settings





True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Enabling the Debug Mode

When 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. From the Add Monitoring Configuration panel, Add or Edit the NetWorker Monitoring

Settings.

2. Scroll down to the Debug Mode section.

Configuring the Debug Mode


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

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

4. In the Options section, indicate:

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

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


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

Configuring the 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.

To configure the remote connection settings1. From the Add Monitoring Configuration panel, Add or Edit the NetWorker Monitoring

Settings.

2. Scroll down to the Remote Connection Settings section.

Configuring the Remote Connection Settings

3. Enter the required values in the available fields:

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.



True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Configuring the Maximum Number of Instances

By default, there is no limitation set for the allowed number of instances in TrueSight OperationsManagement - EMC NetWorker Monitoring. It is however possible to limit the maximum numberof instances that will be displayed in the Console for each monitored elements.

Since monitoring large number of instances may impact the performance of the solution, it isrecommended to only monitor critical elements in large environments.

To configure the maximum number of instances1. From the Add Monitoring Configuration panel, Add or Edit the NetWorker Monitoring

Settings.

2. Scroll down to the Maximum Number of Instances section.

Configuring the Maximum Number of Instances

3. For each monitored element, indicate the maximum number of instances to be displayed, orenter 0 in the relevant field to disable the monitoring of a specific element.



True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Configuring the Multi-Node Monitoring Mode

If the NetWorker environment is installed in a cluster using Veritas Cluster Server, VeritasCluster File System, Oracle Solaris Cluster, or Microsoft Cluster, the EMC NetWorker KM must beinstalled on all the cluster nodes to enable continuous monitoring and avoid single point offailure. To avoid duplicate alerts from multiple nodes, it is recommended to configure thesolution to operate in multi-node monitoring mode.

Monitoring in multi-node mode is supported only when monitoring locally, by installing the PATROLAgent on each NetWorker server in the cluster.

To configure the multi-node monitoring mode1. From the Add Monitoring Configuration panel, Add or Edit the NetWorker Monitoring

Settings.

2. Scroll down to the Multi-node Monitoring Mode section.

Configuring the Multi-node Mode

3. Check the Enable Multi-node Monitoring Mode box.

4. Configure the Multi-node Mode:

Select the appropriate Cluster Application

Indicate the Failover Group Name. Leave this field blank if you previously selected VeritasCluster File System. Then the EMC NetWorker KM will monitor the entire cluster from the


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

active master system, which is identified by “vxdctl -c mode” command. This methodrequires 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

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

5. In the Remote Agent panel, click Add to identify the monitoring node.

Identifying the Monitoring Node

In the Monitoring Node Name filed, enter the cluster node used for multi-node modefailover

Select the Protocol you wish to use to connect to the PATROL Agent on that node

Enter the Port number you wish to use to connect to the PATROL Agent on that node

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

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

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

Click OK to validate.


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

EMC NetWorker will then be monitored through the active or online node. The other nodes,which are standing by for a failover, will be in passive multi-node mode and only the local EMCNetWorker 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. It will reset as soon as it detects a system in Active Multi-nodeMode. If multiple managed nodes in a cluster runs in Single-node Mode or Temporary Single-node Mode,duplicate events may be triggered from shared components (clients, groups, save groups, pending requests,jukeboxes, devices, volume pools and storage nodes).


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Configuring Other Monitor TypesOnce the EMC NetWorker KM monitor type is properly configured, you can create and customizethe following Monitor Types, according to the component(s) you wish to monitor.

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

Configuring NetWorker Clients

Configuring NetWorker Daemons

Configuring NetWorker Groups

Configuring NetWorker Group Clients

Configuring NetWorker Jukeboxes

Configuring NetWorker Jukebox Devices

Configuring NetWorker Logs (Scan Limit)

Configuring NetWorker Pending Requests

Configuring NetWorker Save Groups

Configuring NetWorker Standalone Devices

Configuring NetWorker Storage Nodes

Configuring NetWorker Volume Pools


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Configuring NetWorker ClientsBy default, the solution monitors all the NetWorker clients discovered, which may represent animportant workload for the Agents and the TrueSight OM servers. Because the monitoring ofsome NetWorker clients may be irrelevant for various reasons, you can apply filters to specifythe NetWorker clients that will be monitored or discarded.

To configure NetWorker clients1. From the Add Monitoring Configuration panel, select NetWorker Client from the Monitor

Type list.

2. In the NetWorker Server Clients panel, click Add.

Filtering NetWorker Clients


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

3. In the Hostname field, enter:

localhost to apply these settings to all PATROL Agents installed on EMC NetWorker Servers

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

4. Configure the Filtering options:

In the Keep Only Clients... section, click Add and identify the NetWorker client you wish tomonitor. Enter the name of the NetWorker client or identify it by using a regularexpression (example: prod-client*). Click OK to validate. Repeat the operation for anyother NetWorker client you wish to include in the monitoring process.

In the Exclude Clients... section, click Add and identify the NetWorker client you do notwant to monitor. Enter the name of the NetWorker client or identify it by using a regularexpression (example: test-client*). Click OK to validate. Repeat the operation for anyother NetWorker client you wish to exclude from the monitoring process.

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

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

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



True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Configuring NetWorker DaemonsBy default, the solution monitors all the NetWorker daemons discovered, which may representan important workload for the Agents and the TrueSight OM servers. Because the monitoring ofsome NetWorker daemons may be irrelevant for various reasons, you can apply filters to specifythe NetWorker daemons that will be monitored or discarded.

To configure NetWorker daemons1. From the Add Monitoring Configuration panel, select NetWorker Daemon from the Monitor

Type list.

2. In the NetWorker Server Daemons panel, click Add.

Filtering NetWorker Daemons


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00





In the Keep Only Daemons... section, click Add and identify the NetWorker daemon youwish to monitor. Enter the name of the NetWorker daemon or identify it by using a regularexpression (example: prod-daemon*). Click OK to validate. Repeat the operation for anyother NetWorker daemon you wish to include in the monitoring process.

In the Exclude Daemons... section, click Add and identify the NetWorker daemon you donot want to monitor. Enter the name of the NetWorker daemon or identify it by using aregular expression (example: test-daemon*). Click OK to validate. Repeat the operationfor any other NetWorker daemon you wish to exclude from the monitoring process.

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

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

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



True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Configuring NetWorker GroupsBy default, the solution monitors all the NetWorker groups discovered, which may represent animportant workload for the Agents and the TrueSight OM servers. Because the monitoring ofsome NetWorker groups may be irrelevant for various reasons, you can apply filters to specifythe NetWorker groups that will be monitored or discarded.

To configure NetWorker groups1. From the Add Monitoring Configuration panel, select NetWorker Group from the Monitor

Type list.

2. In the NetWorker Server Groups panel, click Add.

Filtering NetWorker Daemons


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00





In the Keep Only Groups... section, click Add and identify the NetWorker group you wish tomonitor. Enter the name of the NetWorker group or identify it by using a regularexpression (example: prod-group*). Click OK to validate. Repeat the operation for anyother NetWorker group you wish to include in the monitoring process.

In the Exclude Groups... section, click Add and identify the NetWorker group you do notwant to monitor. Enter the name of the NetWorker group or identify it by using a regularexpression (example: test-group*). Click OK to validate. Repeat the operation for anyother NetWorker group you wish to exclude from the monitoring process.

5. The Additional Groups (manual discovery) allows you to add NetWorker groups manually,when they are not automatically discovered:

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

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

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

Check the Enable Backup Restriction Window box

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



True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Configuring NetWorker JukeboxesBy default, the solution monitors all the NetWorker jukeboxes discovered, which may representan important workload for the Agents and the TrueSight OM servers. Because the monitoring ofsome NetWorker jukeboxes may be irrelevant for various reasons, you can apply filters to specifythe NetWorker jukeboxes that will be monitored or discarded.

To configure NetWorker jukeboxes1. From the Add Monitoring Configuration panel, select NetWorker Jukebox from the Monitor

Type list.

2. In the NetWorker Server Jukeboxes panel, click Add.

Filtering NetWorker Jukeboxes


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00





In the Keep Only Jukeboxes... section, click Add and identify the NetWorker jukebox youwish to monitor. Enter the name of the NetWorker jukebox or identify it by using a regularexpression (example: prod-jukebox*). Click OK to validate. Repeat the operation for anyother NetWorker jukebox you wish to include in the monitoring process.

In the Exclude Jukeboxes... section, click Add and identify the NetWorker jukebox you donot want to monitor. Enter the name of the NetWorker jukebox or identify it by using aregular expression (example: test-jukebox*). Click OK to validate. Repeat the operation forany other NetWorker jukebox you wish to exclude from the monitoring process.

5. The Additional Jukeboxes (manual discovery) allows you to add NetWorker jukeboxesmanually, when they are not automatically discovered:

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

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



True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Configuring NetWorker Group ClientsBy default, the solution monitors all the NetWorker group clients discovered, which mayrepresent an important workload for the Agents and the TrueSight OM servers. Because themonitoring of some NetWorker group clients may be irrelevant for various reasons, you canapply filters to specify the NetWorker group clients that will be monitored or discarded.

To configure NetWorker group clients1. From the Add Monitoring Configuration panel, select NetWorker Group Client from the

Monitor Type list.

2. In the NetWorker Server Group Clients panel, click Add.

Filtering NetWorker Group Clients


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00





In the Keep Only Group Clients... section, click Add and identify the NetWorker groupclient you wish to monitor. Enter the name of the NetWorker group client or identify it byusing a regular expression (example: prod-groupclient*). Click OK to validate. Repeat theoperation for any other NetWorker group client you wish to include in the monitoringprocess.

In the Exclude Group Clients... section, click Add and identify the NetWorker group clientyou do not want to monitor. Enter the name of the NetWorker group client or identify it byusing a regular expression (example: test-groupclient*). Click OK to validate. Repeat theoperation for any other NetWorker group client you wish to exclude from the monitoringprocess.

5. The Additional Group Clients (manual discovery) allows you to add NetWorker group clientsmanually, when they are not automatically discovered:

Click Add and enter the name of the NetWorker group client you wish to add to themonitoring environment. Click OK to validate. Repeat the operation for each NetWorkergroup client you want to monitor.

(Optional) Enter a short description that will allow you to quickly identify the addedNetWorker group client.



True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Configuring NetWorker Jukebox DevicesBy default, the solution monitors all the NetWorker jukebox devices discovered, which mayrepresent an important workload for the Agents and the TrueSight OM servers. Because themonitoring of some NetWorker jukebox devices may be irrelevant for various reasons, you canapply filters to specify the NetWorker jukebox devices that will be monitored or discarded.

To configure NetWorker jukebox devices1. From the Add Monitoring Configuration panel, select NetWorker Jukebox Device from the

Monitor Type list.

2. In the NetWorker Server Jukebox Devices panel, click Add.

Filtering NetWorker Jukebox Devices


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00





In the Keep Only Jukebox Devices... section, click Add and identify the NetWorker jukeboxdevice you wish to monitor. Enter the name of the NetWorker jukebox device or identify itby using a regular expression (example: prod-jukeboxdevice*). Click OK to validate.Repeat the operation for any other NetWorker jukebox device you wish to include in themonitoring process.

In the Exclude Jukebox Devices... section, click Add and identify the NetWorker jukeboxdevice you do not want to monitor. Enter the name of the NetWorker jukebox device oridentify it by using a regular expression (example: test-jukeboxdevice*). Click OK tovalidate. Repeat the operation for any other NetWorker jukebox device you wish toexclude from the monitoring process.

5. The Additional Jukebox Devices (manual discovery) allows you to add NetWorker jukeboxdevices manually, when they are not automatically discovered:

Click Add and enter the name of the NetWorker jukebox device you wish to add to themonitoring environment. Click OK to validate. Repeat the operation for each NetWorkerjukebox device you want to monitor.

(Optional) Enter a short description that will allow you to quickly identify the addedNetWorker jukebox device.



True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Configuring NetWorker Logs (Scan Limit)TrueSight Operations Management - EMC NetWorker Monitoring scans log files by reading thenew log entries since the last data collection cycle. By default, only 500 KBytes of data is scannedfor each log file during each data collection cycle. This log scan limit can however be modified tobetter suit your requirements.

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

To configure NetWorker logs (scan limit)1. From the Add Monitoring Configuration panel, select NetWorker Log from the Monitor Type

list.

2. In the NetWorker Server Logs panel, click Add.

Configuring NetWorker Logs




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



True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Configuring NetWorker Pending RequestsBy default, the EMC NetWorker KM monitors all mount requests for 24 hours. This monitoringduration can however be modified to better suit your requirements.

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

To configure NetWorker pending requests1. From the Add Monitoring Configuration panel, select NetWorker Pending Request from the

Monitor Type list.

2. In the NetWorker Server Pending Requests panel, click Add.

Configuring NetWorker Pending Requests


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00


localhost to apply these settings to all PATROL Agents installed on EMC NetWorker servers


4. In the Pending Request Configuration section, indicate how many hours the pendingrequests will be monitored.

5. If the date/time format returned by EMC NetWorker commands is different from your localsystem time zone, you will have to configure it in the Date/Time Format Configurationsection:

Indicate the Expected Format. Refer to the table below to know the valid formats:

Format Description

Default Date/Time Format Leave blank.

EPOCH Set EPOCH, if the time format is the number ofseconds that have elapsed since 00:00:00GMT January 1, 1970

Year Formats

YY Two digit figureExample: 12 for the year 2012

YYYY Four digit figureExample: 2012

Month Formats

MO Two digit figureExample: 02 for February

MONTH Month full name Example: February

MON Three character nameExample: Feb

Date Formats

DD Two digit figureExample: 05

Day Formats

DAYFULL Day full name Example: Friday

DAY Three character nameExample: Fri

Hour Formats

HH Two digit figure

Minute Formats

MM Two digit figure

Second Formats


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Format Description

SS Two digit figure

Time Formats

[blank] Time is in 24-hour format

PM Time is in 12-hour format; am/pm isdisplayedExample: 10:15:00pm

P.M Time is in 12-hour format; a.m/p.m isdisplayedExample: 10:15:00p.m

Indicate a PSL-compatible Time Zone String (e.g.: NZDT, NZST, EDT, EST, GMT-1200, etc.)



True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Configuring NetWorker Save GroupsBy default, the EMC NetWorker KM monitors all save groups that completed successfully for 24hours and any other save groups for 72 hours. This monitoring duration can however be modifiedto better suit your requirements.

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

To configure save groups1. From the Add Monitoring Configuration panel, select NetWorker Save Group from the

Monitor Type list.

2. In the NetWorker Server Save Groups panel, click Add.

Configuring NetWorker Save Groups


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00


localhost to apply these settings to all PATROL Agents installed on the EMC NetWorkerservers


4. In the Monitoring Duration section:

Indicate how many hours the save groups in OK, Suspicious, and Failure status will bemonitored

Select Keep Monitoring Active Save Groups Indefinitely if you prefer to endlessly monitoractive save groups

5. In the Monitored Save Sets dialog box, select the desired level of monitoring:

None: to disable the save clients monitoring feature

Failed Only (default): to only monitor failed save groups

Succeed Only: to only monitor successful save groups

All: to monitor all the save groups.



True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Configuring NetWorker Standalone DevicesBy default, the solution monitors all the NetWorker Standalone Devices discovered, which mayrepresent an important workload for the Agents and the TrueSight OM servers. Because themonitoring of some NetWorker standalone devices may be irrelevant for various reasons, youcan apply filters to specify the NetWorker standalone devices that will be monitored ordiscarded.

To configure NetWorker standalone devices1. From the Add Monitoring Configuration panel, select NetWorker Standalone Device from

the Monitor Type list.

2. In the NetWorker Standalone Devices panel, click Add.

Filtering NetWorker Standalone Devices


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00





In the Keep Only Standalone Devices... section, click Add and identify the NetWorkerstandalone device you wish to monitor. Enter the name of the NetWorker standalonedevice or identify it by using a regular expression (example: prod-sdevice*). Click OK tovalidate. Repeat the operation for any other NetWorker standalone device you wish toinclude in the monitoring process.

In the Exclude Standalone Devices... section, click Add and identify the NetWorkerstandalone device you do not want to monitor. Enter the name of the NetWorkerstandalone device or identify it by using a regular expression (example: test-sdevice*).Click OK to validate. Repeat the operation for any other NetWorker standalone device youwish to exclude from the monitoring process.

5. The Additional Standalone Devices (manual discovery) allows you to add NetWorkerstandalone devices manually, when they are not automatically discovered:

Click Add and enter the name of the NetWorker standalone device you wish to add to themonitoring environment. Click OK to validate. Repeat the operation for each NetWorkerstandalone device you want to monitor.

(Optional) Enter a short description that will allow you to quickly identify the addedNetWorker standalone device.



True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Configuring NetWorker Storage NodesBy default, the solution monitors all the NetWorker storage nodes discovered, which mayrepresent an important workload for the Agents and the TrueSight OM servers. Because themonitoring of some NetWorker storage nodes may be irrelevant for various reasons, you canapply filters to specify the NetWorker storage nodes that will be monitored or discarded.

To configure NetWorker storage nodes1. From the Add Monitoring Configuration panel, select NetWorker Storage Nodes from the

Monitor Type list.

2. In the NetWorker Storage Nodes panel, click Add.

Filtering NetWorker Storage Nodes


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00





In the Keep Only Storage Nodes... section, click Add and identify the NetWorker storagenode you wish to monitor. Enter the name of the NetWorker storage node or identify it byusing a regular expression (example: prod-node*). Click OK to validate. Repeat theoperation for any other NetWorker storage node you wish to include in the monitoringprocess.

In the Exclude Storage Nodes... section, click Add and identify the NetWorker storagenode you do not want to monitor. Enter the name of the NetWorker storage node oridentify it by using a regular expression (example: test-node*). Click OK to validate.Repeat the operation for any other NetWorker storage node you wish to exclude from themonitoring process.

5. The Additional Storage Nodes (manual discovery) allows you to add NetWorker storagenodes manually, when they are not automatically discovered:

Click Add and enter the name of the NetWorker storage node you wish to add to themonitoring environment. Click OK to validate. Repeat the operation for each NetWorkerstorage node you want to monitor.

(Optional) Enter a short description that will allow you to quickly identify the addedNetWorker storage node.



True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Configuring NetWorker Volume PoolsBy default, the solution monitors all the NetWorker volume pools discovered, which mayrepresent an important workload for the Agents and the TrueSight OM servers. Because themonitoring of some NetWorker volume pools may be irrelevant for various reasons, you canapply filters to specify the NetWorker volume pools that will be monitored or discarded.

To configure NetWorker volume pools1. From the Add Monitoring Configuration panel, select NetWorker Volume Pools from the

Monitor Type list.

2. In the NetWorker Volume Pools panel, click Add.

Filtering NetWorker Volume Pools


True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00





In the Keep Only Volume Pools... section, click Add and identify the NetWorker volumepool you wish to monitor. Enter the name of the NetWorker volume pool or identify it byusing a regular expression (example: prod-pool*). Click OK to validate. Repeat theoperation for any other NetWorker volume pools you wish to include in the monitoringprocess.

In the Exclude Volume Pools... section, click Add and identify the NetWorker volume poolyou do not want to monitor. Enter the name of the NetWorker volume pool or identify itby using a regular expression (example: test-pool*). Click OK to validate. Repeat theoperation for any other NetWorker volume pool you wish to exclude from the monitoringprocess.

5. The Additional Volume Pools (manual discovery) allows you to add NetWorker volume poolsmanually, when they are not automatically discovered:

Click Add and enter the name of the NetWorker volume pool you wish to add to themonitoring environment. Click OK to validate. Repeat the operation for each NetWorkervolume pool you want to monitor.

(Optional) Enter a short description that will allow you to quickly identify the addedNetWorker volume pool.



True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Blocking the Monitoring of EMC NetWorkerServersDuring maintenance operations on a system, the EMC NetWorker server owner/administratormay need to stop the monitoring of some EMC NetWorker servers. When this situation occurs,the administrator will just have to:

1. Create an empty block file named NSR_block

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

/var/tmp (UNIX/Linux)

C:\Windows\Temp\ (Windows)

The PATROL Agent monitoring this EMC NetWorker server will detect the block file during thenext discovery cycle and turn the server instance to EMC NetWorker Setup (Monitoring Blocked).

To resume monitoring, simply delete the NSR_block file.

Reference Guide

63

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Introduction

This chapter provides statistical information about resources, operating status, and performancesmanaged by the EMC NetWorker KM. It contains tables describing the attributes used in the KM,grouped by Monitor Types, and provides a brief description of each attribute and its defaultsettings.

64

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

EMC NetWorker KMAttributes

Name Description Units Recommended AlertConditions

Type

AdministratorChange

Monitors any changein NetWorkeradministratorconfiguration betweendiscovery cycles.

0 = NoChange1 = Changed-1 =Unknown

Warning = 1 Availability

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

0 = OK1 =Suspicious2 = Failure

Warning = 1Alarm = 2

Collection Status

Monitor RAP Collects the status ofthe NetWorker RAP(Resource AllocationProtocol) monitorconfiguration.

0 = Enabled1 = Disabled-1 =Unknown

None Availability

Monitoring Mode Monitors the failovermode of EMCNetWorker KM forPATROL.

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

None Collection Status

Node Status Monitors errormessages for the EMCNetWorker applicationon this managedsystem.



Availability

65 EMC NetWorker KM

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker ClientAttributes


Type

Index Record Count Displays the number ofrecords found in theindex database for thisclient.

Count None Statistics

Index Space Used Displays the indexspace used by thisclient.

Kilobytes(KB)

None Statistics

Index Space UsedPercent

Displays thepercentage of indexspace used by theclient.

Percentage(%)

None Statistics

State Displays the state ofthe client as reportedin the commandexecuted by the datacollector.

0 = Running1 = NotRunning2 = ClientDown-1 =Unknown

None Availability

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

Not Running >Failure

Client Down >Failure

Unknown > Failure

All other states > OK



Availability

66NetWorker Clients

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker ClientsAttributes


Type

Exec Time This is a standard parameterwhich monitors the collectorexecution time.It will run every minute andtrigger a warning when thecollector runs for more thanthe observed maximum time.This maximum time can beoverridden by a preset value(example: 3600 seconds),using the PSL below:

%PSL pconfig("REPLACE", "/Runtime/NSR/<node-id>/NSRClientCollectorWarn", 3600);

Seconds Warning > presetvalue or observedmaximum (default)

Collection Status

67 NetWorker Clients

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker DaemonAttributes


Type

CPU Duration Displays the CPUseconds consumed bythe daemon.

Seconds None Statistics

CPU Utilization Displays thepercentage of CPU usedby 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:

Not Running >FailureTerminated, Stopped> SuspiciousGrowing, Unknown >SuspiciousAll other states > OK



Availability

68NetWorker Daemon

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker DaemonsAttributes

Name Description Units RecommendedAlert Conditions

Type

ExecTime

This is a standard parameter whichmonitors the collector execution time.It will run every minute and trigger awarning when the collector runs for morethan the observed maximum time. Thismaximum time can be overridden by apreset value (example: 3600 seconds),using the PSL below:

%PSL pconfig("REPLACE", "/Runtime/NSR/<node-id>/NSRDaemonCollectorWarn", 3600);

Seconds Warning > presetvalue orobservedmaximum(default)

Collection Status

69 NetWorker Daemons

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker DatabaseAttributes


Type

Filesystem Space

Used Percent

Monitors thepercentage of spaceused by the file systemwhere the databaseresides.

Percentage(%)

Alarm if out of [0-100]rangeWarning: 95-98Alarm: 98-100

Statistics

Space Available Monitors the amount ofassigned spaceremaining available foruse by the indexdatabase.

Megabytes(MB)

Warning: 2-5Alarm ≤ 2

Availability

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

Megabytesper second(MB/s)

None Statistics

Space Used Percent Monitors thepercentage of assignedspace used by the indexdatabase.

Percentage(%)


Statistics

Space Used Displays the amount ofassigned space used bythe index database.

Megabytes(MB)

None Statistics

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

70NetWorker Database

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker DatabasesAttributes


Type

Backup

Elapsed

Displays the elapsed time since the lastsuccessful database backup.

Hours None Statistics

Exec Time This is a standard parameter whichmonitors the collector execution time.It will run every minute and trigger awarning when the collector runs for morethan the observed maximum time. Thismaximum time can be overridden by apreset value (example: 3600 seconds), usingthe PSL below:

%PSL pconfig("REPLACE", "/Runtime/

NSR/<node-id>/

NSRDatabaseCollectorWarn", 3600);

Seconds Warning >preset valueor observedmaximum(default)

Collection Status


71 NetWorker Databases

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker GroupAttributes


Type

Backup Elapsed Displays the elapsedtime since the lastbackup for this group,regardless of thebackup completionstatus.


Backup Throughput Displays the lastbackup throughput forthis group.

Gigabytesper second(GB/s)

None Statistics

Full Backup

Duration

Displays the durationof the last successfulfull backup for thisgroup.


Full Backup Elapsed Displays the timeelapsed since the lastsuccessful full backupfor this group.


Full Backup File

Count

Displays the number offiles backed up in thelast successful fullbackup for this group.


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

Gigabytes(GB)

None Statistics

Incremental Backup

Duration

Displays the durationof the last successfulincremental backup forthis group.


Incremental Backup

Elapsed

Displays the elapsedtime since the lastsuccessful incrementalbackup for this group.


Incremental Backup

File Count

Displays the number offiles backed up in thelast successfulincremental backup forthis group.


Incremental Backup

Size

Displays the size of thelast successfulincremental backup forthis group.

Gigabytes(GB)

None Statistics

72NetWorker Group

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00


Type

State Displays the state ofthe group.

0 = Idle1 = Running2 = Runningin RestrictedWindow3 = Cloning-1 =Unknown

None Availability

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

Running inRestricted Window >FailureRunning for morethan 600 minutes >SuspiciousCloning for morethan 600 minutes >SuspiciousUnknown >SuspiciousAll other states > OK



Availability

Successful Backup

Elapsed

Displays the timeelapsed since the lastsuccessful backup forthis group.



73 NetWorker Group

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker GroupsAttributes


Type

Exec Time This is a standard parameter whichmonitors the collector execution time.It will run every minute and trigger awarning when the collector runs for morethan the observed maximum time. Thismaximum time can be overridden by apreset value (example: 3600 seconds),using the PSL below:


NSR/<node-id>/

NSRGroupCollectorWarn", 3600);

Seconds

Warning >preset value orobservedmaximum(default)

Collection Status

74NetWorker Groups

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker Group ClientAttributes


Type

Backup Throughput Displays the lastbackup throughput forthis group client.


None Statistics

Last Full Backup

Duration

Displays the durationof the last successfulfull backup for thisgroup client.


Last Full Backup File

Count

Displays the number offiles backed up in thelast successful fullbackup for this groupclient.


Last Full Backup

Size

Displays the size of thelast successful fullbackup for this groupclient.

Megabytes(MB)

None Statistics

Last Incremental

Backup Duration

Displays the durationof the last successfulincremental backup forthis group client.


Last IncrementalBackup File Count

Displays the number offiles backed up in thelast successfulincremental backup forthis group client.


Last Incremental

Backup Size

Displays the size of thelast successfulincremental backup forthis group client.

Megabytes(MB)

None Statistics


75 NetWorker Group Client

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker JukeboxAttributes


Type

Auto MediaManagement State

Displays the state ofthe jukebox auto mediamanagementconfiguration.

0 = Yes1 = No-1 =Unknown

None Availability

Auto MediaManagement Status

Monitors the status ofthe jukebox auto mediamanagementconfiguration.



Availability

Cleaning Left Count Displays the number ofuses left on thecleaning tape loaded inthis jukebox.

count Warning = - 1 Statistics

State Displays the jukeboxstate, which is derivedfrom the jukeboxresource. It will notperform any remotejukebox test commandon the storage node.

0 = Running1 = EventFound2 = ServiceMode3 = NoEnabledJukeboxDevices4 = Error-1 =Unknown

None Availability

Status Monitors the status ofthe jukebox.



Availability

Throughput Displays the totalthroughput of eachjukebox device duringthe last backup savegroups.


None Statistics

Up Drive Count Displays the number up/ online state drives inthis robotic library.


76NetWorker Jukebox

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00


Type

Volume Assigned

Count

Displays the number ofassigned volumeloaded in this jukebox.(Assigned volumes areregistered tapevolumes assigned to avolume pool.)


Volume Count Displays the totalnumber of volumesloaded in this jukebox.


Volume Empty Count

Displays the number ofempty volumes loadedin this jukebox. (Emptyvolumes are tapevolumes with 0% usedspace.)


Volume Empty

Percent

Monitors thepercentage of emptyvolumes against thetotal number ofvolumes loaded in thisjukebox.

Percentage(%)


Statistics


77 NetWorker Jukebox

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker JukeboxesAttributes


Type



NSR/<node-id>/

NSRJukeboxCollectorWarn", 3600);

Seconds


Collection Status

78NetWorker Jukeboxes

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker Jukebox DeviceAttributes


Type

Session Count Displays the number ofsessions configuredfor the jukebox device.

Sessions None Statistics

Session Maximum Displays the maximumnumber of sessionsconfigured for thejukebox device.


Session Target Displays the number oftarget sessionsconfigured for thejukebox device.


State Displays the state ofthe jukebox device.This is determinedfrom the jukeboxdevice controlinformation.

0 = Idle1 = Mounted2 = VerifyLabel3 = Label4 = Eject5 = Read6 = SettingUp forWriting 7 = Write 8 = CleaningRequired9 = ServiceMode10 = Error11 =Disabled12 = Failure-1 =Unknown

None Availability

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

Disabled, Failed, orUnknown > FailureError for more than60 minutes > FailureCleaning Requiredfor more than 60minutes > Failure

0 = OK1 =Suspicious 2 = Failure


Availability

79 NetWorker Jukebox Device

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00


Type

Error or CleaningRequired >SuspiciousRead for more than600 minutes >SuspiciousWrite for more than600 minutes >SuspiciousAll other states > Ok.

Throughput Displays thethroughput of thejukebox device duringthe last save group.


None Statistics


80NetWorker Jukebox Device

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker LogAttributes


Type

Alarm MessageCount

Monitors the numberof alarm messages.

Count Alarm if out of [0-100] rangeAlarm when ≥ 1

Statistics

Files Space Used Displays the amount ofspace used by the logfile.

Kilobytesper second(KB/s)

None Statistics

Files Space GrowthRate

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

Kilobytesper second(KB/s)

None Statistics

Filesystem Space

Used Percent

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

Percentage(%)

Alarm if out of [0-100] rangeWarning = 95-98Alarm = 98-100

Statistics

Space Available Monitors the availablespace to be used forthe log file. It alsocorresponds to thespace available on thefile system.

Megabytes(MB)

Warning = 2 - 5Alarm ≤ 2

Availability

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

Percentage(%)

Alarm if out of [0-100] rangeWarning = 95-98 Alarm = 98-100

Statistics

Warning MessageCount

Monitors the numberof warning messages.

Count Alarm if out of [0-100] rangeWarning: 1-100

Statistics


81 NetWorker Log

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker LogsAttributes


Type



NSR/<node-id>/NSRLogCollectorWarn",

3600);

Seconds


Collection Status

82NetWorker Logs

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker Storage NodesAttributes

Name Description Units Default AlertConditions

Type

Exec Time This is a standard parameter whichmonitors the collector execution time.It will run every minute and trigger awarning when the collector runs formore than the observed maximumtime. This maximum time can beoverridden by a preset value(example: 3600 seconds), using thePSL below:

%PSL pconfig("REPLACE", "/

Runtime/NSR/<node-id>/

NSRStorageNodeCollectorWarn",

3600);

Seconds Warning > presetvalue orobservedmaximum(default)

CollectionStatus

83 NetWorker Storage Nodes

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker Storage NodeAttributes

Name Description Units DefaultAlertConditions

Type

Device Count Displays the number of devicesconnected to the storage node.


Library Count Displays the number oflibraries connected to thestorage node.


State Displays the state of the mediaserver as reported in thecommand executed by the datacollector.

0 = Running1 = NotConfigured2 = Not Enabled3 = Not Ready-1 = Unknown

None Availability

Status Monitors the status of themedia server.

0 = OK1 = Suspicious2 = Failure

Warning= 1Alarm =2

Availability

84NetWorker Storage Node

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker Pending RequestsAttributes


Type

ExecTime

This is a standard parameter whichmonitors the collector execution time.It will run every minute and trigger awarning when the collector runs formore than the observed maximum time.This maximum time can be overriddenby a preset value (example: 3600seconds), using the PSL below:



NSRRequetCollectorWarn", 3600);

Seconds


Collection Status

85 NetWorker Pending Requests

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker Pending RequestAttributes


Type

Elapsed Displays the elapsedtime since the pendingrequest was issued.

Minutes None Statistics

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

0 =Completed1 = Pending-1 =Unknown

None Availability

Status Monitors the status ofthe pending request.The following State toStatus mapping rule isused:

Pending for morethan 30 minutes >FailurePending >SuspiciousUnknown >SuspiciousCompleted > OK.



Availability


86NetWorker Pending Request

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker Save ClientAttributes


Type

State Displays the state of thesave client.

0 =Succeeded1 = Failed-1 =Unknown

None Availability

Backup Status Monitors the status ofthe save client.



Availability

87 NetWorker Save Client

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker Save GroupAttributes


Type

Duration Displays the durationof the save group fromthe start.


File Count Displays the number offiles backed up for thissave group.


Size Displays the amount ofdata backed up for thesave group.

Megabytes(MB)

None Statistics

State Displays the state ofthe save group. This isdetermined using thesave group completionstate and the numberof pending, succeeded& failed save sets.

0 =Completed1 = Queued2 = InProgress3 = InProgress/Errors4 =Requeued 5 =Completed/Errors6 = Aborted7 = Failed -1 =Unknown

None Availability

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

Aborted or Failed >FailureCompleted/Errors orIn Progress/Errors >SuspiciousUnknown >SuspiciousIn Progress for morethan 300 minutes >SuspiciousAll other states > OK.



Availability

88NetWorker Save Group

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00


Type

Throughput Displays thethroughput of this savegroup.


None Statistics


89 NetWorker Save Group

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker Save GroupsAttributes


Type

ActiveBackupCount

Displays the number of active backupjobs currently discovered andmonitored.


ActiveCount

Displays the number of active jobscurrently discovered and monitored.


ActiveNon-BackupCount

Displays the number of active non-backup jobs currently discovered andmonitored.


ExecTime

This is a standard parameter whichmonitors the collector executiontime.It will run every minute and triggera warning when the collector runsfor more than the observedmaximum time. This maximum timecan be overridden by a preset value(example: 3600 seconds), using thePSL below:



NSRSaveGrpCollectorWarn",

3600);

Seconds


Collection Status

ManualSaves

Displays whether the manual savesare enabled or disabled.

None 0 = Enabled1 = Disabled-1 = Unknown

Availability

90NetWorker Save Groups

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker Standalone DeviceAttributes


Type

Session Count Displays thenumber ofsessionsconfigured forthe device.

Sessions

None Statistics

Session Maximum Displays themaximumnumber ofsessionsconfigured forthe device.

Sessions

None Statistics

Session Target Displays thenumber oftargetsessionsconfigured forthe device.

Sessions

None Statistics

State Displays thestate of thestandalonedevice.

0 = Idle1 =Mounted2 =VerifyLabel3 =Label4 = Eject5 =Read6 =SettingUp forWriting7 =Write8 =CleaningRequired9 =ServiceMode10 =Error

None Availability

91 NetWorker Standalone Device

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00


Type

11 =Disabled12 =Failure-1 =Unknown

Status Monitors thestatus of thestandalonedevice.

0 = OK1 =Suspicious2 =Failure


Availability

Throughput Displays thethroughput ofthestandalonedevice duringthe last savegroup.

Megabytes persecond(MB/s)

None Statistics


92NetWorker Standalone Device

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker Standalone DevicesAttributes


Type

ExecTime

This is a standard parameterwhich monitors the collectorexecution time.It will run every minute andtrigger a warning when thecollector runs for more than theobserved maximum time. Thismaximum time can beoverridden by a preset value(example: 3600 seconds), usingthe PSL below



NSRDeviceCollectorWarn",

3600);

Seconds


Collection Status

93 NetWorker Standalone Devices

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker Volume PoolsAttributes


Type

ExecTime

This is a standard parameter whichmonitors the collector executiontime.It will run every minute and trigger awarning when the collector runs formore than the observed maximumtime. This maximum time can beoverridden by a preset value(example: 3600 seconds), using thePSL below



NSRPoolCollectorWarn", 3600);

Seconds Warning >preset value orobservedmaximum(default)

Collection Status

94NetWorker Volume Pools

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker Volume PoolAttributes


Type

Space Available Monitors the availablevolume space for thebackup data to use inthis volume pool.If this parameterchanges to warning oralarm state, therecovery action willtrigger an event.

Gigabytes(GB)

None Availability

Space Growth Rate Displays the growthrate of the totalvolume space used bythe backup data in thisvolume pool.

Gigabytesper second(GB/s)

None Statistics

Space Used Displays the totalvolume spaceoccupied by thebackup data in thisvolume pool.

Gigabytes(GB)

None Statistics

Space Used Percent Monitors thepercentage of totaloccupied volumespace against the totalvolume capacity ofthis volume pool (notincluding any scratchvolume).

Percentage(%)


Statistics

Volume Active Count

Displays the number ofactive volumes in thisvolume pool. (Activevolumes are availabletape volumes wheredata can be writtenwithout anyintervention.)


Volume Active

Percent

Monitors thepercentage of activevolumes against thetotal number ofvolumes in this volumepool

Percentage(%)


Statistics

Volume Available

Count

Displays the number ofvolumes assigned tothis volume pool.


95 NetWorker Volume Pool

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00


Type

Volume Available

Percent

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

Percentage(%)


Statistics

Volume Count Displays the totalnumber of volumes inthis volume pool.


Volume Empty Count

Displays the number ofempty volumes in thisvolume pool. (Emptyvolumes are availabletape volumes with nodata stored on them.)


Volume Full Count Displays the number offull volumes in thisvolume pool. ("Full" isa possible status for atape volume.)


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

Percentage(%)


Statistics

Volume Manual

Recycle Count

Displays the number ofvolumes in this volumepool, which requiremanual recycling.("Manually-recyclable" volume isa possible volumestate set on tapevolumes.)


Volume Read Only

Count

Displays the number ofread only volumes inthis volume pool.("Read Only" is apossible volume flagset on tape volumes.)



96NetWorker Volume Pool

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

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 Performance

Indicators (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

97

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Index

- A -Abnormalities 96

Access

Permissions 12

User 12Attributes

Active Backup Count 89

Active Count 89

Active Non-Backup Count 89

Administrator Change 64

Alarm Message Count 80

Auto Media Management State 75

Auto Media Management Status 75

Backup Elapsed 70, 71

Backup Throughput 71, 74

Cleaning Left Count 75

CPU Duration 67

CPU Utilization 67

Device Count 83

Duration 87

Elapsed 85

Exec Time 66, 68, 70, 73, 77, 81, 82, 84,93

File Count 87

File Space Growth Rate 80

File Space Used 80

Filesystem Space Used Percent 69, 80

Full Backup Duration 71

Full Backup Elapsed 71

Full Backup File Count 71

Full Backup Size 71

Incremental Backup Duration 71

Incremental Backup Elapsed 71

Incremental Backup File Count 71

Incremental Backup Size 71

Index Record Count 65

Index Space Used 65

Index Space Used Percent 65

Last Full Backup Duration 74

Last Full Backup File Count 74

Last Full Backup Size 74

Last Incremental Backup Duration 74

Last Incremental Backup File Count 74

Last Incremental Backup Size 74

Library Count 83

Login Status 64

Manual Saves 89

Memory Size 67

Monitor RAP 64

Monitoring Mode 64

Node Status 64

Process Count 67

Session Count 78, 90

Session Maximum 78, 90

Session Target 78, 90

Size 87

Space Available 69, 80, 92, 94

Space Growth Rate 69, 92, 94

Space Used 69, 92, 94

Space Used Percent 69, 80, 92, 94

State 65, 67, 71, 75, 78, 83, 85, 86, 87, 90

Status 65, 67, 71, 75, 78, 83, 85, 86, 87,90

Successful Backup Elapsed 71

Throughput 75, 78, 87, 90

Up Drive Count 75

Volume Active Count 92, 94

Volume Active Percent 92, 94

Volume Assigned Count 75

Volume Available Count 92, 94

Volume Available Percent 92, 94

Volume Count 75, 92, 94

Volume Empty Count 75, 92, 94

Volume Empty Percent 75

Volume Full Count 92, 94

Volume Full Percent 92, 94

Volume Manual Recycle Count 92, 94

Volume Read Only Count 92, 94

Warning Message Count 80Automated Drives

Debug 30Automated Libraries

Debug 30

- B -Baseline 63

Baselines

BMC ProactiveNet Performance Management 96

98

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

Baselines

Generation 96

Manage 96

Requirements 96Block

Monitoring 61BMC PATROL

Changes 10BMC ProactiveNet Performance Management

Abnormalities 96

Baselines 96

Key Performance Indicators 96

KPI 96Business Value 9

- C -Clients

Debug 30Cluster Application 33

Component Installation package

creating 20

downloading 21Configure

Groups 41

Maximum Instances 32

Multi-node monitoring mode 33

Overrides 28Configuring

monitor settings 23Connection

Remote 31

- D -Daemons

Debug 30Databases

Debug 30Debug

Automated Drives 30

Automated Libraries 30

Clients 30

Daemons 30

Databases 30

Directory Path 30

Domains 30

End Time 30

Jobs 30

Logs 30

Mount Requests 30

Processes 30

Server 30

Storage Pools 30Domains

Debug 30Downloading 21

- F -Failover Group Name 33

Features 9

- G -Generate

Baselines 96Goals 9

Groups

Configure 41

- I -Importing the Monitoring Solution 19

Installing 21

Installing the Monitoring Solution 18

Instances

Client 32

Daemon 32

Database 32

Group 32

Group Client 32

Jukebox 32

Jukebox Device 32

Log 32

Pending Request 32

Save Group 32

Standalone Device 32

Volume Pool 32

- J -Jobs

Debug 30

99

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

- K -Key Concepts 9



Manage 96KPI 63


Manage 96

- L -Logs

Debug 30

- M -Maintenance 61

Manage

Baselines 96


KPI 96Monitor Settings

configuring 23Monitor Type

EMC NetWorker KM 64

NetWorker Client 65

NetWorker Daemon 67

NetWorker Database 69

NetWorker Databases 70

NetWorker Group 71

NetWorker Group Client 74

NetWorker Jukebox 75

NetWorker Jukebox Device 78

NetWorker Log 80

NetWorker Pending Request 85

NetWorker Save Client 86

NetWorker Save Group 87

NetWorker Save Groups 89

NetWorker Standalone Device 90

NetWorker Volume Pool 92, 94Monitor Types

Add 23

EMC NetWorker KM 63

NetBackup Clients 66

NetWorker Client 63

NetWorker Daemon 63

NetWorker Daemons 68

NetWorker Database 63

NetWorker Databases 63

NetWorker Group 63

NetWorker Group Client 63

NetWorker Groups 73, 77

NetWorker Jukebox 63

NetWorker Jukebox Device 63

NetWorker Log 63

NetWorker Logs 81

NetWorker Pending Request 63

NetWorker Pools 93

NetWorker Requests 84

NetWorker Save Client 63

NetWorker Save Group 63

NetWorker Save Groups 63

NetWorker Volume Pool 63Monitoring

Block 61

Stop 61Monitoring Node Names 33

Mount Requests

Debug 30Multi-node monitoring mode

Configure 33

- N -NetWorker Clients

Configuration 37

Filtering 37

Manual Discovery 37NetWorker Daemons

Configuration 39

Filtering 39

Manual Discovery 39NetWorker Group Clients

Configuration 45

Filtering 45

Manual Discovery 45NetWorker Jukebox Devices

Configuration 47

Filtering 47

Manual Discovery 47NetWorker Jukeboxes

Configuration 43

100

True

Sigh

t O

pera

tion

s M

anag

em

ent

- E

MC

Net

Wor

ker

Mon

itor

ing

Ver

sion

3.0

.00

NetWorker Jukeboxes

Filtering 43

Manual Discovery 43NetWorker Logs

Configuration 49

Scan Limit 49NetWorker Pending Requests

Configuration 50

Date/Time Format 50

Monitoring Duration 50

Time Zone String 50NetWorker Save Groups

Configuration 53

Duration 53

Save Sets 53NetWorker Standalone Devices

Configuration 55

Filtering 55

Manual Discovery 55NetWorker Storage Nodes

Configuration 57

Filtering 57

Manual Discovery 57NetWorker Volume Pools

Configuration 59

Filtering 59

Manual Discovery 59

- O -Overrides

Configure 28

TSM Server Discovery 28

- P -Package 20, 21

Policy

Create 23

Edit 23Processes

Debug 30

- R -Reference Guide 63

Release Notes 7

Remote Connection

Max Connections 31

Settings 31

Timeout 31Remote PATROL Agent Checking 33

Requirements

Security 12

Software 10

System 10

- S -Scan Limit

Configuration 49

Logs 49Security

Requirements 12Server

Debug 30Software

Requirements 10Storage Pools

Debug 30Sudo 12, 27

System

Requirements 10

- T -Tivoli Storage Manager

Changes 10TSM Server Discovery

Overrides 28

- U -UNIX 27

User Account

Configure 27

patrol 27

Privileges 27

Sudo 27

- W -Windows 27

About Sentry Software™Sentry Software, a strategic Technology Alliance Partner of BMC Software, providescomprehensive multi-platform monitoring solutions that enable management of thehardware and software aspects of all servers and SANs and covering up to 100 % ofcustom applications within the BMC TrueSight environment. Sentry Software alsodevelops adapters for BMC Atrium Orchestrator that enables IT administrators toautomate the execution of common requests and tasks that occur in the daily course ofIT operations. Combined with BMC’s servers and network automation tools, theadapters allow IT administrators to implement provisioning and decommissioningworkflows that cover all layers of their IT infrastructure. Finally, Sentry Software designsconnectors that bring storage capacity metrics into BMC TrueSight Capacity Optimizationto ensure IT administrators that their storage infrastructure is properly sized for theircurrent and future needs.

Like us on Facebook:facebook.com/sentrysoftware

Follow us on Twitter:

twitter.com/sentrysoftware

LEARN MORE

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

© BMC Software, Inc. All rights reserved.

ABOUT MARKETZONE DIRECT PRODUCTS

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

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

www.bmc.com.

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

BUSINESS RUNS ON I.T .

I.T . RUNS ON BMC SOFT WARE

http://facebook.com/sentrysoftware

http://twitter.com/sentrysoftware

http://twitter.com/sentrysoftware

http://facebook.com/sentrysoftware

Documents

TrueSight Operations Management - EMC NetWorker Monitoring