emc networker km for patrol 2.8 - sentry software · emc networker km for patrol storage monitoring...

EMC NetWorker KM for PATROL

STORAGE MONITORING

USER DOCUMENTATION

Version 2.8.02

February 2017

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

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

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

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

4

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Table of Contents.....................................................................................................................................................................................13Requirements

.......................................................................................................................................................................................13System Requirements

.......................................................................................................................................................................................13Software Requirements

.......................................................................................................................................................................................15Security Requirements

.......................................................................................................................................................................................19Disk Space Requirements

.....................................................................................................................................................................................20Getting the BMC Software Installation Utility

.....................................................................................................................................................................................20Packages

.....................................................................................................................................................................................20Extracting the Setup Files

.....................................................................................................................................................................................24Installing EMC NetWorker KM for PATROL

.....................................................................................................................................................................................35Uninstalling EMC NetWorker KM for PATROL

.....................................................................................................................................................................................40Loading/Unloading the KM

.......................................................................................................................................................................................40Loading the KM

......................................................................................................................................................................41Loading the KM on PATROL Console

......................................................................................................................................................................41Loading the KM on PATROL Central

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

.......................................................................................................................................................................................42Unloading the KM

......................................................................................................................................................................42Unloading the KM from the PATROL Agent

......................................................................................................................................................................43Unloading the KM from the PATROL Console

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

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

.......................................................................................................................................................................................44Configuring the KM User Account

.......................................................................................................................................................................................46Verifying Application Discovery

.......................................................................................................................................................................................46Checking the Instance Limits

.......................................................................................................................................................................................48Checking the Initial Setup of the KM

.......................................................................................................................................................................................48Restarting PATROL Agent and PATROL Console

.....................................................................................................................................................................................51Integrating with BMC Portal

.....................................................................................................................................................................................51Integrating with BMC TrueSight OM

.....................................................................................................................................................................................53Administering EMC Networker

.......................................................................................................................................................................................53Starting Server/Storage Node

.......................................................................................................................................................................................53Stopping Server/Storage Node

.......................................................................................................................................................................................53Administering Pending Requests

.......................................................................................................................................................................................54Administering Standalone Drives

5

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

.......................................................................................................................................................................................54Administering Jukebox Devices

.....................................................................................................................................................................................55Configuring the KM

.......................................................................................................................................................................................55Configuring Paths

.......................................................................................................................................................................................56Specifying the Node Type

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

.......................................................................................................................................................................................58Filtering Elements to Monitor

.......................................................................................................................................................................................60Configuring Monitoring Periods

.......................................................................................................................................................................................62Configuring the Save Clients Monitoring

.......................................................................................................................................................................................63Configuring the Node Status

.......................................................................................................................................................................................64Configuring the Elements Status

.......................................................................................................................................................................................65Configuring the Log Filter

.......................................................................................................................................................................................67Configuring the Log Scan Limit

.......................................................................................................................................................................................67Configuring Group Backup Restriction

.......................................................................................................................................................................................68Configuring Alert Acknowledgement

.......................................................................................................................................................................................70Configuring Date/Time Formats

.......................................................................................................................................................................................73Refreshing Parameters

.......................................................................................................................................................................................74Reloading Commands

.......................................................................................................................................................................................75Enabling the Debug Mode

.....................................................................................................................................................................................78Acknowledging Alerts

.....................................................................................................................................................................................79Generating Reports

.....................................................................................................................................................................................81Classes and Parameters

.......................................................................................................................................................................................83NSR_SERVER

.......................................................................................................................................................................................91NSR_CLIENT_CONTAINER

.......................................................................................................................................................................................93NSR_CLIENT

.......................................................................................................................................................................................96NSR_DAEMON_CONTAINER

.......................................................................................................................................................................................98NSR_DAEMON

.......................................................................................................................................................................................101NSR_DATABASE_CONTAINER

.......................................................................................................................................................................................104NSR_DATABASE

.......................................................................................................................................................................................106NSR_LOG_CONTAINER

.......................................................................................................................................................................................109NSR_LOG

.......................................................................................................................................................................................114NSR_POLICY_CONTAINER

.......................................................................................................................................................................................116NSR_POLICY

.......................................................................................................................................................................................121NSR_PCLIENT

.......................................................................................................................................................................................124NSR_JOB_CONTAINER

.......................................................................................................................................................................................128NSR_JOB

.......................................................................................................................................................................................132NSR_JCLIENT

6

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

.......................................................................................................................................................................................134NSR_MOUNT_CONTAINER

.......................................................................................................................................................................................136NSR_MOUNT

.......................................................................................................................................................................................138NSR_LIBRARY_CONTAINER

.......................................................................................................................................................................................140NSR_LIBRARY

.......................................................................................................................................................................................144NSR_LDEVICE

.......................................................................................................................................................................................147NSR_DEVICE_CONTAINER

.......................................................................................................................................................................................149NSR_DEVICE

.......................................................................................................................................................................................152NSR_POOL_CONTAINER

.......................................................................................................................................................................................154NSR_POOL

.......................................................................................................................................................................................158Managing Baselines and Key Performance Indicators

.....................................................................................................................................................................................161Troubleshooting

.....................................................................................................................................................................................164Where to Find Additional Help

Release Notes for v2.8.02

9

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Changes and ImprovementsNSR-146: The Sudo configuration in the sudoers file must be modified for Solaris, HP-UX, AIXand Linux to prevent NSR KM commands failures (see Security Requirements).

NSR-147: The KM has been improved to better perform in large environments.

NSR-155: EMC NetWorker KM for PATROL has been improved to support all PATROL Agent v10+ versions as well as TrueSight Operations Management v10.x.

Fixed IssuesNSR-140: The KM has been improved to avoid intermittent crashes of the PATROL Agent onNetWorker v7.x.

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

NSR-175: Invalid alarms were triggered on the NSRLoginStatus parameter (NSR_SERVER)when the KM was unable to check the active node.

NSR-176: The status report file of EMC NetWorker KM for PATROL is now suffixed with theAgent port number to avoid overwriting it when multiple virtual Agents are used.

NSR-178: On Windows systems, if the PATROL Agent installation path contained spaces,scripts calls and output redirection commands failed.

NSR-233: Upon new installations, NSR KM was not always able to perform a full discoveryafter a login configuration.

Overview

11

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

EMC NetWorker KM for PATROL monitors your EMC NetWorker application within a centralizedmanagement console to ensure its runs efficiently 24 hours a day.

The KM more especially monitors the:

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

All the information collected is grouped into application classes and displayed in the PATROLConsole. Alarms and warnings inform you when a suspicious behavior is detected; thus allowingyou to quickly and clearly identify peaks, troughs and trends in the performance of your backupresources.

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

Preparing for Installation

13

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

This chapter provides information about the tasks that must be performed before you startinstalling EMC NetWorker KM for PATROL. Make sure to carefully read the following sectionsrequirements:

Review the System, Software, Security and Disk Space requirements

Get the BMC Software Installation Utility

Download the Installation Packages

Extract the Setup Files

RequirementsSystem Requirements

Operating System Operating System Version

Oracle/Sun SolarisTM 8 and higher

HP-UX 11 and higher

IBM® AIXTM 5.1 and higher

Red Hat® Linux® 7.2

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

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

Software RequirementsSoftware Version

EMC NetWorker 6.1.x, 6.2, 7.0, 7.1.x, 7.2.x, 7.3.x, 7.4.x, 7.5.x, 7.6.x,8.0.x, 8.1.x, 8.2.x

BMC Software PATROL Agent 3.9.x, 9.x, 10.x

BMC Software PATROL Console 3.4.x, 3.5.x, 7.x

BMC Portal 2.3.x, 2.4.x, 2.5.x, 2.6.x, 2.7.x, 2.8.x

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

BMC TrueSight Operations Management 10.x

Networker v9.x will be supported by the coming soon version 2.9.x of NSR KM.

If the version of EMC NetWorker is upgraded (or downgraded) at a later date, you will need to reloadcommands for the EMC NetWorker KM for PATROL.

14Requirements

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Changes to EMC NetWorker

It is required to set-up a save group log file on all managed systems on Unix platforms. This filecan be used by the NSR KM to collect save group information efficiently. The save group log filecan be configured in EMC NetWorker using the steps below.

1. Open the EMC NetWorker Administrator GUI, and select Customize > Notifications

2. Select View > Details to see all details of a notification

3. Click Create and fill out the form as below:Name: NSR KM savegroup logging

Comment: Required notification for NSR KM

Action: cat >> /nsr/logs/savegrp.log

Event: Savegroup

Priority: Info, Warning, Critical, Emergency,

Notice, Waiting, Alert

4. Click Apply.

The NSR KM will process the contents of EMC NetWorker messages f ile (/nsr/logs/messages) in the absenceof above save group log f ile (/nsr/logs/savegrp.log).

The above save group log f ile set-up is not required on Windows managed nodes because it is one of thestandard EMC NetWorker log f iles.

The NSR KM will not maintain or recycle this save group log f ile. It is recommended to recycle the save grouplog f ile regularly.

Changes to BMC PATROL

To improve the performance of the NSR KM, the PATROL Agent tuning variable /AgentSetup/AgentTuning/pslInstructionMax should be increased to at least 5,000,000. This applies for all EMCNetWorker servers and storage nodes where the KM is installed. This adjustment will allow theKM data collectors to execute without incurring an internal scheduling delay.

This PATROL Agent tuning variable can be updated using wpconfig (on Microsoft Windows) orxpconfig (on Unix). Alternatively, you can use the following single line PSL command through thePATROL Console OS> prompt to update this tuning variable.

%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 NSR KM data collectors are in an inf inite loop. In this case you can setthe tuning variable to zero to disable this functionality.

15 Requirements

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

The KM stores all configuration information in the PATROL Agent configuration database(pconfig), under paths /NSR and /Runtime/NSR. PATROL Agent user (default: patrol) should beable to read and write to these pconfig variables at anytime. If Access Control List (ACL) is used tocontrol which users are authorized to connect to a PATROL Agent, please ensure that the modefor PATROL Agent user includes “C” in the PATROL Agent variable /AgentSetup/accessControlList.Please refer the PATROL Agent Reference Manual for more details.

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

Additional Software Requirements

Purpose Software Version

When running NSR KM with sudo useraccount on Solaris, HP-UX, AIX or Linuxmanaged nodes

Sudo (superuser do) 1.6.7 or later

When running NSR KM on Linux managednodes

Korn shell binary (/bin/ksh) Any

When running NSR KM on MicrosoftWindows x64 managed nodes

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

Any

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

Security RequirementsBy default, EMC NetWorker is installed and run as the root user (on Unix) or as administrator user(on Microsoft Windows). EMC NetWorker KM for PATROL needs to be run as a user account withadministrative privileges to read and execute EMC NetWorker application programs and filesystems. Login details of this user are configured in the NSR KM during the KM configuration. Thepassword is stored in the PATROL Agent in a DES encrypted format.

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

One of the following user accounts can be used for configuring the login details of the KM:

16Requirements

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

1. root user (Unix) or administrator user (Microsoft Windows)

2. a non-root user, such as patrol, with sudo privileges on EMC NetWorker to executeapplication programs and access the file systems (Unix only)

3. a non-root (Unix) or non-administrator (Microsoft Windows) account, such as patrol,configured in EMC NetWorker application to administer the EMC NetWorker application

Refer to the EMC NetWorker System Administrator’s Guide for details on how to set up this type of account.

Access Permissions

The NSR KM user needs “read & execute” permission to executable and library files under thepaths listed below. The EMC NetWorker installation path INSTALL_PATH is normally /nsr or /opt/networker (on Unix) or C:\Program Files\nsr (on MS Windows).

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)

C:\Windows\sysnative\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.

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

i=0; sudoers="";

foreach var (grep("^/Runtime/NSR/CommandControls/",pconfig("LIST")))

{

ctl=get(var);

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

17 Requirements

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

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

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

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

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

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

{

met="";

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

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

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

else

{

scmd=cmd;

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

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

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

}

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

}

}

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

The PATROL Agent user (normally patrol) needs “read & execute” permission to following pathsand files:

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)

To access f iles under above paths the relevant user needs “read & execute” permission to all parentdirectories.

If a monitored log file cannot be read by the PATROL Agent user, it will be copied to KM_TEMP pathusing the configured KM login account, and processed by the PATROL Agent user. On completion, thecopied log file will be removed. This may increase the file system usage under KM_TEMP temporarilyduring this activity.

On Windows platforms the EMC NetWorker installation is identified by checking the Windows

18Requirements

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Registry. Depending on whether you are using a 32/64-bit OS and/or 32/64-bit Application, theRegistry entries are stored in different locations:

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

Sudo User for Operating System Access

If a non-root user with sudo privileges is preferred as the NSR 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 NSR KM administration andreport menu commands using their sudo privileges. The NSR KM accepts any non-root user withthe following sudo configuration in the sudoers file. Please replace user1, user2, user3 withappropriate KM user name. The EMC NetWorker installation path INSTALL_PATH, referencedbelow is normally /nsr or /opt/networker and PATROL_HOME is the path where the PATROLAgent is installed (including the target, like /opt/bmc/Patrol3/Solaris29-sun4/).

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 :


19 Requirements

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


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






This non-root sudo user configured in the KM will be able to execute root equivalent commands byopening a shell window. To prevent this, ensure this user is only used within the KM and not madepublic for general use.

Entering the non-root sudo user with ‘Use Sudo’ option selected in to the KM 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 will expose the sudouser password.

Disk Space RequirementsEMC NetWorker KM for PATROL requires approximately:

3 MBytes disk space on each monitored PATROL Agent system

5 MBytes disk space on each PATROL Console system

400 KBytes disk space on each PATROL Central Console Server system

1 MBytes disk space on each PATROL Central Web Server system

The NSR KM is installed under the PATROL installation path.

When monitoring a standard installation of EMC NetWorker using NSR KM, the PATROL Agent willgenerate approximately 250 KBytes of history data per day. An enterprise installation of EMCNetWorker on a server with multiple storage nodes, clients, jukeboxes, and standalone deviceswill generate more history data (as per other KMs used by the PATROL Agent). These history datafiles are recycled by PATROL depending on the PATROL Agent history retention period.

During NSR KM data collection, it will use a temporary folder (KM_HOME/tmp) to store sometemporary files. These temporary files are removed at the end of the data collection cycle.Required space under this file system depends on the complexity of the EMC NetWorkerenvironment. If the available space for this folder is less than 10 MBytes, it can be changed to adifferent file system, which has sufficient disk space. This can be achieved by replacing thetemporary folder, KM_HOME/tmp, with a soft link pointing to a different file system, like /tmp.This new temporary folder should have read, write and execute permissions for both PATROLAgent user and the NSR KM login user.

20Getting the BMC Software Installation Utility

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Getting the BMC Software InstallationUtilityIn order to install EMC NetWorker KM for PATROL, you need the latest version of the BMCSoftware Installation Utility. You can download the latest Installation Utility from the BMCSoftware EPD (electronic product download) from: http://webapps.bmc.com/signon/content/logon.jsp on the BMC Software Website, or from the EMC NetWorkers KM for PATROL page onthe Sentry Software Website

Choose the appropriate package depending on the platform you plan to install EMC NetWorkerKM for PATROL on:

For UNIX/Linux systems: ins_ALL_<version>.tar

For Windows systems: ins_WINDOWS_<version>.exe

The packages are valid for all the PATROL components: Agent, Console, Console Server, etc.

Place the Installation Utility package in the same folder as the EMC NetWorker KM for PATROLpackages.

PackagesThe EMC NetWorker KM for PATROL packages are available on the Sentry Software Web site.

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

Extracting the Setup FilesLike most Knowledge Modules for PATROL, you need to install EMC NetWorker KM for PATROL onthe following components of your PATROL architecture:

Every managed system with a PATROL Agent

Every PATROL Console (Classic) that will show EMC NetWorker performance-relatedinformation and alerts

The Console Server

PATROL Central – Web Edition

Installing the KM

23

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Introduction

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

24

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Installing EMC NetWorker KM forPATROLInstalling EMC NetWorker KM for PATROL is an automated process managed by a wizard. Thewizard goes through the necessary steps to install EMC NetWorker KM for PATROL and all filesassociated with it. You are simply prompt for the product's folder location and the product/components to install.

Browse to the bmc_products folder where the files have been extracted (both EMC NetWorkerKM for PATROL and the Common Installer).

On Windows: Launch the setup.exe program

On UNIX: Launch the setup.sh script

To install EMC NetWorker KM for PATROL1. The welcome screen of the installer appears. Click Next to continue.

Installation Wizard - Welcome

25 Installing EMC NetWorker KM for PATROL

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

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

Installation Wizard - Reviewing License Agreement

26Installing EMC NetWorker KM for PATROL

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

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

Installation Wizard - Selecting Installation Options


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

4. Specify the BMC Software Products folder. See the BMC Software documentation for moreinformation about the BMC Software Products folder. Click Next to continue.

Installation Wizard - Selecting the Installation Directory


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

5. Select Default. Installing EMC NetWorker KM for PATROL does not require anycustomization. Click Next to continue.

Installation Wizard - Selecting an Installation Type

6. Select one or several of the following options:

Managed System to install EMC NetWorker KM for PATROL on a PATROL Agent.

Console Systems to install EMC NetWorker KM for PATROL on a PATROL Classic Console.

Common services to install EMC NetWorker KM for PATROL on the Console Server or onPATROL Central – Web Edition.

Click Next to continue.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Installation Wizard - Selecting Roles


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

7. Check the EMC NetWorker KM for PATROL box to install the KM (it should be selected bydefault). Click Next to continue.

Installation Wizard - Selecting Products and Components


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

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

Installation Wizard - Reviewing Installation Options


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

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

Installation Wizard - Installation Status


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

10. The wizard displays the installation results. Click View Log to display a detailed log of theinstallation procedure. Click Next and then Finish to exit the setup program.

Installation Wizard - Installation Results


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

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

Installation Wizard - Completing and closing the Installation Wizard


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Uninstalling EMC NetWorker KM forPATROLUninstalling EMC NetWorker KM for PATROL is an automated process managed by a wizard. Thewizard goes through the necessary steps to remove EMC NetWorker KM for PATROL and all filesassociated with it. You are simply prompt for the product's folder location and the product/components to uninstall.

To uninstall EMC NetWorker KM for PATROL1. Locate the Uninstall folder under the BMC products directory (typically under C:\Program

Files\BMC Software, or /opt/bmc):

On Windows systems, launch uninstall.exe

On UNIX, launch uninstall.sh

Un-install Wizard — Welcome Step

36Uninstalling EMC NetWorker KM for PATROL

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

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

Un-install Wizard — Specifying folder

37 Uninstalling EMC NetWorker KM for PATROL

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

3. To uninstall the KM, select EMC NetWorker KM for PATROL.

Un-install Wizard — Selecting Products and Components Directory


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

4. Click Start Uninstall.

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

39 Uninstalling EMC NetWorker KM for PATROL

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

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

Un-install Wizard — Status


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

6. A page displaying SUCCESS indicates that EMC NetWorker KM for PATROL is now uninstalled.

Un-install Wizard — Uninstall Results

Loading/Unloading the KMOnce installed the KM will have to be preloaded on one of the following PATROL consoles:

PATROL Console

PATROL Central

The PATROL Agent can also be configured to automatically preload the KM.

Loading the KMBefore loading the NSR KM:

1. Make sure you properly installed the KM on PATROL Console and PATROL Agent systems

2. Start the PATROL Console and update the connection to all PATROL Agent systems where theNSR KM is installed.

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

41 Loading/Unloading the KM

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Loading the KM on PATROL Console1. From the PATROL Console menu bar, choose File>Load KM...

2. Select the NSR_LOAD.kml file.

3. Click Open or OK.

4. The NSR KM will be loaded to the PATROL Console, and all connected PATROL Agents willstart discovering the EMC NetWorker environment. If the automatic discovery successfullyfinds the EMC NetWorker server/storage node installation, NSR_SETUP instance will beinstantiated,

This automatic discovery may take up to 5 minutes to instantiate the NSR_SETUP instance. Look for anyerror messages on the PATROL Console System Output Window (SOW) during the initial discovery.

If you want to save the new list of loaded files as the PATROL Console user preference:

1. From the PATROL Console menu bar, choose File > Save Configuration.

2. Load the NSR_LOAD.kml file on each PATROL Console.

3. Configure the KM.

Loading the KM on PATROL CentralTo load the KM on PATROL Central:

1. In the Console, right-click the Managed System and select Load Knowledge Modules... TheLoad Knowledge Modules wizard is displayed.

2. Select the managed systems where the NSR KM is to be loaded, and click Next>. The wizardwill display a list of all available .kml files for the managed systems you selected.

3. Select the NSR_LOAD.kml file for each managed system, click Next> and Finish.

The NSR KM will be loaded to the PATROL Central Console Server, and all connected selectedmanaged systems will start discovering the EMC NetWorker environment. If the automaticdiscovery successfully finds the EMC NetWorker installation, the NSR_SETUP instance will beinstantiated.

This automatic discovery may take up to 5 minutes to instantiate the NSR_SETUP instance. Look for anyerror messages on the PATROL Central System Output Window (SOW) during the initial discovery.

4. Load the NSR_LOAD.kml file on each PATROL Central Management Profile where the NSR KMis to be loaded.

5. Configure the KM.

42Loading/Unloading the KM

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Configuring PATROL Agent to Preload the KMIf you want EMC NetWorker KM for PATROL to operate all the time, without a PATROL Consoleconnection, you'll have to add it to the PATROL Agent configuration variable /AgentSetup/preloadedKMs.

To configure the PATROL Agent to preload the KM:

1. In the Console, right-click the EMC NetWorker icon > Configuration > Preloading.

2. Click Add to add the KM files to the list of preloaded KMs.

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

Unloading the KMThis section describes the procedures for unloading (not uninstalling) the EMC NetWorker KM forPATROL Agent, PATROL Console or PATROL Central Console. Read this section if you no longerwant to use some parts of the KM; if you want to completely uninstall the KM, refer to theuninstall procedure.

When the KM is unloaded:

from a PATROL Agent: PATROL stops monitoring the EMC NetWorkerd application on thatsystem when there is no connection to a PATROL Console with NSR KM loaded.

from a PATROL Console: the PATROL Console stops displaying and monitoring the EMCNetWorker application on any PATROL Console connected system.

Unloading the KM from the PATROL AgentTo unload the KM from the PATROL Agent:

1. In the Console, right-click the EMC NetWorker icon and select and select KM Commands >Configuration > Preloading

2. Click Remove.

3. Restart the PATROL Agent.

4. Repeat these steps on every PATROL Agent system (managed node) where the NSR KM is tobe unloaded.

You can also use the utility wpconf ig (on Microsoft Windows) or xpconf ig to unload the KM. You will thenhave to remove NSR_LOAD.kml f rom the PATROL Agent conf iguration variable /AgentSetup/preloadedKMs.

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

43 Loading/Unloading the KM

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

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

To unload the NSR KM completely or partially:

1. Remove the unwanted NSR KM application classes from the list of loaded application classes,as required. All NSR KM application classes start with NSR_.

With the PATROL Console for Unix:

From the PATROL Console main window choose Attributes> Application Classes...

Select a NSR KM application class to be removed and choose Edit>Delete.

Repeat for all classes to be removed.

With the PATROL Console for MS Windows:

From the PATROL Console tree view choose the KM tab and expand the folder ApplicationClasses.

Right-click on a NSR KM application class to be removed and choose Delete.

Repeat for all classes to be removed.

2. Select File>Save Configuration to save the modified list of loaded application classes as thePATROL Console user preference.

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

Unloading the KM from the PATROL Central ConsoleA KM can be unloaded from particular managed systems or for all systems across the monitoredenvironment. Application classes may be unloaded individually, or by selecting all classes atonce. This allows for a partial unloading of the KM to enable it to run as a reduced installation onsome or all of the managed systems.

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

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

2. Select the managed systems where the NetWorker KM is to be unloaded, and click Next>.

3. Select the application classes to be removed that starts with NSR_ for the appropriatemanaged systems, click Next> and Finish.

4. Repeat the above steps for each PATROL Central Management Profile where the NetWorkerKM is to be unloaded.

44Loading/Unloading the KM

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Performing Post-InstallationOperationsIt is recommended to perform post installation checks once the KM is installed and loaded on thePATROL Console to ensure it properly operates. Post-installation operations include:

Configuring the KM user account

Verifying:

the application discovery

the instance limits

the initial setup

Restarting the PATROL Agent and PATROL Console.

Configuring the KM User AccountA user account with administrative privileges must be configured in BMC PATROL to read andexecute EMC NetWorker application programs and file systems. Depending on the operatingsystems 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.

45 Performing Post-Installation Operations

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

To configure the KM User Account:1. In the Console, right-click the EMC NetWorker instance > Configuration > Login. The Login

Configuration dialog box is displayed:

Login Configuration dialog

2. To use:

the default PATROL Agent Account, check the Use Agent Default Account box. The logindetails entered in the Username and Password fields will then be ignored.

a different user account, enter the login details in the Username and Password fields

3. If a sudo user account is used:

check the Use Sudo box

click SUDO Binary File to verify the sudo binary file path

4. Click OK.

If the credentials are not valid, the NSRLoginStatus parameter will appear in “suspicious state”after the next data collection.

46Performing Post-Installation Operations

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Verifying Application DiscoveryTo verify the application discovery:

1. Check that the NSR_SETUP instance is actually named EMC NetWorker. If not, force a fulldiscovery by right-clicking the EMC NetWorker instance > KM Commands > Force Discovery

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

If EMC NetWorker is configured in a configured in a clustered environment, you'll have to enableMulti-node Mode monitoring.

Checking the Instance LimitsBy default, there is no limitation set for the available instances in EMC NetWorker KM forPATROL. To offer better performance, it is possible to limit the number of instances that will bedisplayed in the Console for each monitored elements.

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

47 Performing Post-Installation Operations

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

To modify the default configuration1. In the Console, right-click the KM main icon > KM Commands > Configuration> Instance Limits

Configuring the Default Instance Limits

2. Enter the number of instances to be displayed in the console for each monitored element

3. To disable the monitoring of a specific application class, enter 0 in the relevant field

4. Click OK.

48Performing Post-Installation Operations

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Checking the Initial Setup of the KMTo check the initial setup of the KM:

1. Check whether the discovered files and directory paths are correct, using the menu Configuration > Paths from the EMC NetWorker instance.

2. Check whether the discovered Node Type is correct using the menu Configuration > NodeType from the EMC NetWorker instance.

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

4. Under each container instance, open all detail parameters (text parameters with names inthe format NSR<Obj ect>Details), and check for error messages.

5. Check the new value of parameter NSRLoginStatus set after completion of all data collection.If either is not in OK state, open the annotation point to determine the cause of the error.

6. After the KM has been running for at least an hour:

Right-click the KM main icon > KM commands > KM Status from the EMC Storage Managerinstance. A report is displayed, detailing information on the managed system. Checkthrough the report for any warnings or alarms. If any errors are found during any of theabove steps (including any incorrect data in Infoboxes or any warnings or alarms in the KMStatus report), determine the cause(s) and take steps to resolve these errors. You mayneed to refer to the User Guide, or contact Technical Support, attaching the KM Statusreport.

If needed, click Save As Task to open the report in a task window. You could later save it asa text file or print it.

7. The KM installed on the storage node may monitor the same elements which are alreadymonitored through the server node. This may be unnecessary and can trigger duplicatealerts. You can disable these components on either server or storage node by setting theirinstance limit to 0 (zero), using the menu Configuration> Instance Limits.

Restarting PATROL Agent and PATROL ConsoleRestarting the PATROL Agent and PATROL Console is optional but often a good practice toconfirm that the NSR KM operates correctly after restarting the PATROL Agent and/or PATROLConsole.

In addition, the PATROL Agent restart will force all KM discoveries and data collections to startimmediately.

Integrating the KM

51

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Introduction

This section provides detailed information about the integration of EMC NetWorker KM forPATROL with BMC Framework.

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

2. Click on Configure tab.

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

4. Click Add.

5. Select Infrastructure Element, and click Next.

6. Select appropriate RSM, and click Next.

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

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

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

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

Integrating with BMC TrueSight OMNo specific integration steps need to be performed. To know how to use EMC NetWorker KM forPATROL in BMC TrueSight Operations Management, please refer to the TrueSight OperationsManagement - EMC NetWorker Monitoring documentation.

Monitoring your environment

53

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

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

Administering EMC NetWorkerEMC NetWorker KM for PATROL provides secure server administration menus, which can beexecuted by PATROL Console users, if they have appropriate privileges. They can moreespecially:

Start or stop the server/storage node

Administer:

pending requests

standalone drives

jukebox drives.

Starting Server/Storage NodeIn the Console, right-click the EMC NetWorker instance > KM Commands>Administration andselect Start Server / Storage Node.

Stopping Server/Storage NodeIn the Console, right-click the EMC NetWorker instance > KM Commands>Administration andselect Stop Server / Storage Node.

Administering Pending RequestsWhen a pending request appears, its parameter NSRRequestStatus is immediately set to alert(Warning or Alarm depending on the elapsed time). When a pending request appears on astandalone device, requested tape needs to be loaded in to the standalone device, andmounted. To perform this mount operation, right-click the pending request instance and select KM commands > Administration > Mount Tape.

54Administering EMC Networker

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Administering Standalone DrivesTo administer standalone drives, right-click the relevant drive instance and select one of thefollowing options:

Administration > Mount Tape

Administration > Unmount Tape

Administration > Enable Device

Administration > Disable Device

Administering Jukebox DevicesTo administer jukebox drives, right-click the Jukebox Device instance and select KM Commands >Administration > Enabled or Disabled.

Administration menus for mounting or unmounting tapes on jukebox devices are not available, wheremounting or unmounting tapes on devices are automatic.

55 Administering EMC Networker

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Configuring the KMThe configuration instructions provided in this section should be followed on all PATROL AgentSystems where EMC NetWorker KM for PATROL is installed.

Before configuring the KM, make sure:

the KM is loaded on the PATROL Console

the NSR_SETUP or EMC NetWorker instance is displayed in the Console.

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

Altering these paths may impact the operation of the KM.

To configure paths:

1. In the Console, right-click the EMC NetWorker instance > KM commands > Configuration >Paths

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

3. In the NSR section, verify and possibly modify the Installation Directory Path

4. In the Binary Paths and Library Paths sections:

From the list, select the paths to be removed

In the Path field, enter the new path(s) to be included. If several paths are to be entered,separate them with a colon (:).

5. Click OK.

If you want to rediscover the paths, empty all f ields, click OK, and restart the PATROL Agent.

56Configuring the KM

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

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

1. In the Console, right-click the EMC NetWorker instance > KM Commands > Configuration >Node Type

Configuring Node Type

2. Select the node type (Server or Storage Node).

3. Click OK.

Configuring the Multi-Node Monitoring ModeIf the NSR KM environment is installed in a cluster using Veritas Cluster Server, Veritas ClusterFile System, Oracle Solaris Cluster, or Microsoft Cluster, the NSR KM must be installed on all thecluster nodes to enable continuous monitoring and avoid single point of failure. To avoidduplicate alerts from multiple nodes, it is recommended to configure the solution to operate inmulti-node monitoring mode.

To configure the multi-node monitoring mode:

57 Configuring the KM

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

1. In the Console, right-click the EMC NetWorker instance > KM Commands Configuration >Monitoring Mode.

Configuring the Multi-Node Monitoring Mode

2. Select Multi-node Mode

3. Select the appropriate Cluster Application

4. Indicate the Failover Group Name. Leave this field blank if you previously selected VeritasCluster File System. The NSR KM will then monitor the entire cluster from the active mastersystem, which is identified by the vxdctl -c mode command. This method requires vxconfigdin enable mode with its clustered state active.

5. Enable remote PATROL Agent Checking to check the monitoring status of the other nodesand click OK

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

7. Click OK.

EMC NetWorker server will then be monitored through the online cluster node. The KM onoffline node will monitor in passive mode, until NetWorker is failed over. In the passive modethe KM will monitor only the NetWorker components that requires monitoring.

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.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Filtering Elements to MonitorBy default, the solution monitors all the elements discovered, which may represent an importantworkload to the agents and servers. Because the monitoring of some elements may be irrelevantfor various reasons, you can apply filters to indicate which elements will be monitored or not.

To filter elements to monitor:

1. In the Console, right-click one of the following instances depending on the elements thatyou wish to monitor:

Clients > KM Commands > Configuration> Clients to filter clients to be monitored

Daemons > KM Commands > Configuration > Daemons to filter daemons to be monitored

Databases > KM Commands > Configuration > Databases to filter databases to bemonitored

Logs > KM Commands > Configuration>Logs to filter logs to be monitored. Only the dailymessages file will be monitored on AIX and Microsoft Windows platforms since there is noASCII format system log file to monitor.

Groups > KM Commands > Configuration > Groups to filter groups to be monitored. Bydefault, only save groups that belong to these groups will be instantiated and monitored.You can however disable this direct relationship between monitored groups configurationand monitored save groups instances by running the following PSL through PATROLConsole: %PSL pconfig("REPLACE","/NSR/FilterJobByPolicy", false);

Group Client > KM Commands > Configuration > Group Client to filter group clients to bemonitored

Jukeboxes > KM Commands > Configuration > Jukeboxes to filter jukeboxes to bemonitored

Standalone Devices > KM Commands > Configuration > Standalone Devices to filterstandalone devices to be monitored

Volume Pools > KM Commands > Configuration > Volume Pools to filter volume pools to bemonitored

These menus are also available f rom the child instances.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Client Configuration dialog

The [ALL] entry ensures that all the elements found during PATROL discovery are instantiatedand monitored. When installed on a Storage Node, the default configuration monitors only thediscovered local jukeboxes and local standalone devices. This is covered by the [LOCAL] entry inthe default configuration on a Storage Node.

2. To enable elements for monitoring:

In the current configuration list, select the elements to enable

Select Enable

Click Update

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


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

3. To disable elements for monitoring:

In the current configuration list, select the elements to disable

Select Disable

Click Update

All jobs associated to disabled policies are not monitored.

Disabled instances will be instantiated in an OFFLINE state. Commands will not be executed, thus leavingparameters not set.

4. To delete elements for monitoring:

In the current configuration list, select the elements to delete

Select Delete

Click Update

5. To add a new element to monitor:

Type the name of the element (as it appears in the PATROL console) or a regularexpression to be monitored

If needed, enter a description

From the Status list, select Enable

Click Update.

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

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

Configuring Monitoring Periods

By default, EMC NetWorker KM for PATROL monitors all pending requests for 1day and all savegroups that completed successfully for 1 day and any other save group for 3 days . You canhowever modify these settings to better suit your requirements:

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


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Configuring the Save Groups Monitoring Periods1. In the Console, right-click the Save Groups instance > KM Commands > Configuration > Save

Groups

Save Group Filter Configuration dialog

2. Indicate how long the save groups in OK, Suspicious, and Failure status will be monitored. Ifyou:

decrease the monitoring period, older save groups will be destroyed on the next datacollection cycle

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


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

3. Click OK.

By default, all active save groups are exempted from ageing, i.e. save groups which are in one of the activestates (In Progress, or In Progress/Errors) will always be monitored.

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

Pending Requests

Pending Request Filter Configuration dialog

2. Indicate how long the pending requests will be monitored. If you decrease the monitoringperiod, older pending requests will be destroyed on the next data collection cycle

3. Click OK.

Configuring the Save Clients MonitoringBy default, only the failed save clients are monitored. This setting can however be modified toinclude successful save clients.

To configure the save clients monitoring:

1. Right-click the Save Groups icon > KM Commands > Configuration > Save Clients.

2. In the Monitored Save Clients dialog box, select the desired level of monitoring:

None: to disable the save clients monitoring feature

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

Succeed Only: to only monitor successful save clients


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

All: to monitor all the save clients

3. Click OK.

Configuring the Node StatusThe parameter NSRNodeStatus monitors the availability of all the configured daemons. If anyconfigured daemon is not running, this parameter will be set to “failure” (Alarm) state andseveral recovery actions will be initiated. If any command run by EMC NetWorker KM for PATROLreturns a server/storage node error message, this parameter will be set to“suspicious” (Warning) state.

To indicate which daemons will set the NSRNodeStatus parameter:

1. In the Console, right-click the EMC NetWorker instance > KM commands > Configuration >Node Status.

Node Status Configuration dialog


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

2. In the Monitored daemons list, select the daemons to be removed from the node statusfilter.

3. In the Daemon field, enter the daemons to be added to the node status filter. Multipledaemons may be entered at the same time, using a comma (,) as a separator.

4. Click Update.

To revert to the shipped default list of monitored daemons (as shown above), type “[default]” as a newdaemon for the list and click Update.

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

1. In the Console, right-click the instance for which you want to configure status and select >KM commands > Configuration > Instance Status

Client Status Configuration dialog


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

2. In the Warning Filter State Rules list, select the states that will not trigger a warning

3. If needed, apply a time condition to a specific state. For example, if you want to trigger awarning when the Unknown state of the Client instance lasts more than 120 minutes:

From the State list, select -1 (Unknown)

From the Condition list, select >

In the Minutes field, enter 120

4. In the Alarm Filter State Rules list, select the states that will not trigger an alarm

5. If needed, apply a time condition to a specific state. For example, if you want to trigger analarm when the Never Communicated state of the Clients instance lasts more than 240minutes:

From the State list, select 2 (Never Communicated)

From the Condition list, select >

In the Minutes field, enter 240

6. Click Update.

To revert to the default status mapping rule for either f ilter, select [default] f rom the list of states and clickUpdate.

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

Configuring the Log FilterA log error filter can be configured to specify the regular expressions that will generate a warningor an alarm. Each time the KM will find these expressions in a log file or in NSRLogText, the errormessage will be written to the NSRLogAlarmText or NSRLogWarningText parameter.

By default, the default log filter is configured to only monitor the EMC NetWorker progress andcompletion messages files and the system log file. If you enabled additional log files formonitoring, you will have to customize the log filter by adding appropriate expressions for thoselog files.

For more information about the possible error messages in the log f iles, refer to the EMC NetWorker SystemAdministrator’s Guide and the EMC NetWorker Error Message Guide.

To configure the log error filter:


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

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

Log Filter Configuration dialog

2. In the Warning Filter Expressions list, select the expressions that will not trigger a warning

3. In the Alarm Filter Expressions list, select the expressions that will not trigger an alarm

4. To add a new regular expression to the warning or alarm filter:

In the Expression field, indicate the regular expression to be included (e.g.: skipping)

Select Include

Regular expressions are case-sensitive.

5. To exclude a regular expression from the warning or alarm filter:

In the Expression field, indicate the regular expression to be excluded (e.g.: otlsol01). Youcan also limit the exclusion to a particular expression already listed by using standardwildcard syntax, such as “warning . otlsol01”.

Select Exclude


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

6. Click Update.

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

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

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

To customize the log scan limit:

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

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

3. Click OK.

Configuring Group Backup RestrictionNSR KM can be configured to trigger a warning when a group backup is started during a specificperiod of time:

1. In the Console, right-click:

the Groups instance > KM Commands > Configuration> Groups Backup Restriction to applythis customization to all group backups

a Group instance > KM Commands > Configuration> Group Backup Restriction to apply thiscustomization to a specific group


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Group Backup Restriction Window dialog

2. Select Enabled

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

4. Click OK.

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

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


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Configuring Log Alert Acknowledgement

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

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

Configuring Log Alert Acknowledgement

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

3. Click Ok.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Configuring Save Groups Alert Acknowledgment

To configure the save groups alert acknowledgement:

1. In the Console, right-click the Save Groups instance > KM Commands > Configuration > JobAlert Acknowledgement

Configuring Job Alert Acknowledgement

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

3. Click Ok.

Configuring Date/Time FormatsThe EMC NetWorker KM for PATROL uses EMC NetWorker commands to determine the date andtime of each save group and of each pending request (used for calculating the elapsed timesince the save group and the pending request were initiated). Depending on your local systemtime zone and date/time format, the application may return a different date/time format. If so,you'll have to customize the save group and pending request date/time format.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Customizing the Save Group Date/Time Format1. In the Console, right-click the Save Groups instance > KM Commands > Configuration > Save

Group Date/Time Format

Save Group Date/Time Format Configuration dialog

2. Indicate the expected Date/Time Format.

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

4. Click OK.

The new date/time format is then applied to all save groups.

To revert to the default settings, blank out the Date/Time f ield and/or the Time Zone f ield and click OK. TheTime zone f ield used will be the local time zone on the managed node.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Customizing the Pending Request Date/Time Format1. In the Console, right-click the Pending Requests instance > KM Commands > Configuration >

Pending Requests Date/Time Format

Pending Request Date/Time Format Configuration dialog

2. Indicate the expected Date/Time Format.

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

4. Click OK.

The new date/time format is then applied to all save groups.

To revert to the default settings, blank out the Date/Time f ield and/or the Time Zone f ield and click OK. TheTime zone f ield used will be the local time zone on the managed node.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Refreshing ParametersThis section describes how to manually refresh parameters of the EMC NetWorker KM forPATROL, without waiting for an automatic polling cycle.

Forcing All Discoveries1. Refresh the PATROL Agent process cache using the KM command Refresh Process Cache from

the main NSR KM container instance (labeled EMC NetWorker).

2. Force the discovery by selecting KM command Force Discovery from the main NSR KMcontainer instance.

These steps will also force discovery on application classes for any other KM loaded on the PATROL Agentas well as all application classes of the NSR KM.

Forcing All Data Collectors1. Refresh the PATROL Agent process cache using the KM command Refresh Process Cache from

the main NSR KM container instance (labeled EMC NetWorker).

2. All data collectors can be forced at the same time by using the KM command RefreshParameters from the main NSR KM container instance.

These steps will refresh all other data collectors def ined under the various application classes loaded on thePATROL Agent as well as refreshing the NSR KM data collectors.

Forcing Selected Data Collectors

This option is only available from a PATROL Developer Console.

1. Refresh the PATROL Agent process cache using the KM command Refresh Process Cache fromthe main NSR KM container instance (labeled EMC NetWorker).

2. Force a data collector to execute immediately as follows:

On PATROL Console for MS Windows

Right-click on the NSR KM container instance and choose Parameters without Icons...

Select the required data collector.

Click Update.

On PATROL Console for Unix

Right-click on the NSR KM container instance and choose Customize > Parameters...


Click on Options > Update.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

With the PATROL Central Operator Console

Right-click on the NSR KM instance and choose Properties

Click on the Parameter List tab


Click Update.

Forcing Full Data Collection for Save Groups

By default, the NSRSave GroupCollector only searches for new save groups started since the lastcollection cycle. However, it can be forced to search for all save groups within the monitoredtime period during the next collection cycle. Use the KM command Force Full Collection from thesave groups container instance (labeled Save Groups).

If the Save Groups container instance is not instantiated, this menu command cannot be accessed. ThePATROL Agent needs to be restarted to force a full data collection for save groups.

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


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

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

1. In the Console, right-click the EMC NetWorker instance > KM Commands > Configuration >Debug.

Enabling the Debug Mode


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

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

Object DebugSwitch

Application Classes Collector Parameters

Server NSR_SERVER NSRCreateDistributionNSRUpdateAgent

Database NSR_DATABASE_CONTAINERNSR_DATABASE

NSRDatabaseCollector

Log NSR_LOG_CONTAINERNSR_LOG

NSRLogCollector

Client NSR_CLIENT_CONTAINERNSR_CLIENT

NSRClientCollector

Jukebox/Device NSR_LIBRARY_CONTAINERNSR_LIBRARYNSR_LDEVICENSR_DEVICE_CONTAINERNSR_DEVICE

NSRJukeboxCollectorNSRDeviceCollector

Daemon NSR_DAEMON_CONTAINERNSR_DAEMON

NSRDaemonCollector

Volume Pool NSR_POOL_CONTAINERNSR_POOL

NSRPoolCollector

Group/SaveGroup/PendingRequest

NSR_POLICY_CONTAINERNSR_POLICYNSR_PCLIENTNSR_JOB_CONTAINERNSR_JOBNSR_JCLIENTNSR_MOUNT_CONTAINERNSR_MOUNT

NSRGroupCollectorNSRSaveGrpCollectorNSRRequestCollector

3. Set the Debug Options:

In the Debug End Time field, indicate the date and time after which debug information willno longer be logged.

In the Debug Path field, indicate where the debug file will be stored (by default:<PATROL_HOME>/lib/NSR/debug on Unix systems; %PATROL_HOME%\lib\NSR\debug onMicrosoft Windows systems). The debug folder must have at least 10MB of available diskspace and read, write and execute permissions for both PATROL Agent user and the NSRKM login user

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

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

PATROL Agent.

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


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

4. Select OK to start NSR KM debugging.

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

Disabling the Debug Mode

The debug switches will be turned off automatically when the debug duration is over. A tar/zipfile is then automatically created under <PATROL_HOME>/lib/NSR/ and can be sent to the BMCSupport for help. It is also recommended to check the SOW or NSR.log file, stored in<PATROL_HOME>/log, for any error. If you want to manually stop debugging:

1. Access the NSR KM Debug Configuration dialog.

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

3. Click OK.

Preparing the Debug Files for Sending to Sentry Software

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

Right-click in the NSR KM Debug Output window.

Select Save As and specify a location to save data.

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

Click Yes to compress the files into a:

nsr_km_debug_<date>_<time>.tar.Z file (Unix systems). This file could later be found in$PATROL_HOME/lib/NSR/

nsr_km_debug_<date>_<time>.zip file (Windows systems). This file could later be found in%PATROL_HOME%\lib\NSR\

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

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

Appending Output Data to Existing Files

If you want to gather output from several debug sessions:

1. Disable the debug mode.

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

3. Choose to Retain the debug files.

4. Start the next debug session.

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


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

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

Manually Acknowledging Log Alerts

When an error is detected in a monitored log file, it will appear under one of the textparameters NSRLogAlarmText or NSRLogWarningText. This will trigger an Alarm or a Warning onparameter NSRLogAlarmCount or NSRLogWarningCount, respectively.

To acknowledge log alerts:

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

2. Select:

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

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

All to acknowledge all alerts (Warnings and Alarms) at once without viewing

Manually Acknowledging Save Group Alerts

For a particular save group instance, if the NSRSaveGrpStatus has a value of 1=Suspicious or2=Failure, it will be set to alert with a status of Warning or Alarm respectively. These alerts canbe acknowledged using the KM command Acknowledgement > Alert from the relevant savegroup instance.

To acknowledge save group alerts:

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

2. Select:

Acknowledgement > Warnings to view and acknowledge alerts for all save groups with astatus of Warning.

Acknowledgement > Alarms to view and acknowledge alerts for all save groups with astatus of Alarm.

Acknowledgement > All to view and acknowledge all save group alerts (Warnings andAlarms) at once.

79 Generating Reports

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Generating ReportsFollowing is a list of reports available in the EMC NetWorker KM for PATROL.

Daemons > Reports > Daemon List - lists all running EMC NetWorker daemons

Databases > Reports > Database Backup Information - reports information about the previousindex database backups

Logs > Reports > Messages List - reports all recent messages logged

Pending Requests > Reports > Pending Requests - reports a list of all pending requests

<Jukebox instance> > Reports > Jukebox Contents - reports the contents of the selectedjukebox instance

<Volume Pool instance> > Reports > Volumes List - reports information on all volumes in theselected volume pool instance

To save the report as a task window click Save As Task. This task window can then be printed or saved as atext f ile.

Reference Guide

81

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

This chapter provides statistical information about resources, operating status, and performancesmanaged by EMC NetWorker KM for PATROL. It contains tables describing the parameters used inthe KM, grouped by Application Classes, and provides a brief description of each parameter andits default settings.

Classes and ParametersThis section lists the application classes of NSR KM. It gives you details on the icons thatrepresent the class, Infobox, parameters and the menu commands available for each applicationclass.

NSR_SERVER

NSR_CLIENT_CONTAINER

NSR_CLIENT

NSR_DAEMON_CONTAINER

NSR_DAEMON

NSR_DATABASE_CONTAINER

NSR_DATABASE

NSR_LOG_CONTAINER

NSR_LOG

NSR_POLICY_CONTAINER

NSR_POLICY

NSR_PCLIENT

NSR_JOB_CONTAINER

NSR_JOB

NSR_JCLIENT

NSR_MOUNT_CONTAINER

NSR_MOUNT

NSR_LIBRARY_CONTAINER

NSR_LIBRARY

NSR_LDEVICE

NSR_DEVICE_CONTAINER

NSR_DEVICE

NSR_POOL_CONTAINER

NSR_POOL

Baselines and Key Performance Indicators

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

82Classes and Parameters

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

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

Baselining

KPI

83 Classes and Parameters

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_SERVERIcon

Parameters

Name Description Units DefaultAlertConditions

Type

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

n/a n/a n/a

NSRAdministratorChange Monitors any change inNetWorker administratorconfiguration betweendiscovery cycles. It is set byNSR_SERVER application classdiscovery.

0 = No Change1 = Changed-1 = Unknown

Warning = 1

Availability

NSRClientCollector Collects EMC NetWorker clientrelated information. It sets allconsumer parameters inNSR_CLIENT_CONTAINER andNSR_CLIENT applicationclasses.By default, this collector isexecuted only on the server.

Polling Interval: 600 seconds

n/a n/a n/a

NSRCreateDistribution Is automatically activated atthe end of NSR KM debugging ifthe customer chooses to"prepare debug files for sendingto Sentry Software". It isdeactivated on completion.


n/a n/a n/a

NSRDaemonCollector Collects EMC NetWorkerdaemon related information. Itsets all consumer parametersin NSR_DAEMON_CONTAINERand NSR_DAEMON applicationclasses.


n/a n/a n/a


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type

NSRDatabaseCollector Collects EMC NetWorker indexdatabase related information. Itsets all consumer parametersin NSR_DATABASE_CONTAINERand NSR_DATABASE applicationclasses.By default, this collector isexecuted only on the server.


n/a n/a n/a

NSRDeviceCollector Collects EMC NetWorkerstandalone device relatedinformation. It sets allconsumer parameters inNSR_DEVICE_CONTAINER andNSR_DEVICE applicationclasses.


n/a n/a n/a

NSRGroupCollector Collects EMC NetWorker KM forPATROL group and group clientrelated information. It sets allconsumer parameters inNSR_POLICY_CONTAINER,NSR_POLICY, and NSR_PCLIENTapplication classes.By default, this collector isexecuted only on the server.


n/a n/a n/a

NSRJukeboxCollector Collects EMC NetWorkerjukebox and jukebox devicerelated information. It sets allconsumer parameters inNSR_LIBRARY_CONTAINER,NSR_LIBRARY, and NSR_LDEVICEapplication classes.


n/a n/a n/a

NSRLogCollector Collects information about theEMC NetWorker log file. It setsall consumer parameters inNSR_LOG_CONTAINER andNSR_LOG application classes.


n/a n/a n/a


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type

NSRLoginStatus* Monitors the status of the NSRKM login details (username/password) for the operatingsystem. It is set by NSR_SERVERapplication class discovery.If no valid username/passwordis detected for the operatingsystem, this parameter will beset to Failure state. If there areany suspicious command exits,this parameter will be set toSuspicious state.

If this status parameterchanges to warning or alarmstate, the recovery action willtrigger an event and annotatethe last data point.

0 = Ok1 = Suspicious2 = Failure

Warning = 1Alarm= 2

CollectionStatus

NSRMonitoringMode* Monitors failover mode of EMCNetWorker KM for PATROL. It isset by NSR_SERVER applicationclass discovery.

By default EMC NetWorker KMfor PATROL runs in PermanentSingle-node Mode. Multi-nodemonitoring can be configuredusing the KM command Configuration>Monitoring Modefrom the EMC NetWorker icon.

0 = PermanentSingle-node Mode 1 = TemporarySingle-node Mode2 = Active Multi-node Mode3 = Passive Multi-node Mode-1 = Unknown

None CollectionStatus

NSRMonitorRAP Collects the status of theNetWorker RAP (ResourceAllocation Protocol)monitorconfiguration. It is set byNSR_SERVER application classdiscovery.

0 = Enabled1 = Disabled-1 = Unknown

None Availability

NSRNodeStatus* Monitors error messages forthe EMC NetWorker applicationon this managed system. It isset by NSR_SERVER applicationclass discovery.


Warning = 1Alarm= 2

Availability


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type

If any of the EMC NetWorkerapplication daemons is notrunning, this parameter will beset to Failure state. The list ofcritical EMC NetWorkerdaemons can be customizedusing the KM command Configuration > Node Statusfrom the EMC NetWorker icon. Ifthere are any suspiciouscommand exits due to an errorfrom the server/storage node,this parameter will be set toSuspicious state.


NSRPoolCollector Collects information about theEMC NetWorker volume pools.It sets all consumer parametersin NSR_POOL_CONTAINER andNSR_POOL application classes.By default, this collector isexecuted only on the server.


n/a n/a n/a

NSRRequestCollector Collects information about theEMC NetWorker pendingrequests. It sets all consumerparameters inNSR_MOUNT_CONTAINER andNSR_MOUNT applicationclasses.By default, this collector isexecuted only on the server.


n/a n/a n/a

NSRSaveGrpCollector Collects information about EMCNetWorker backup/restore savegroups and save clients. It setsall consumer parameters inNSR_JOB_CONTAINER, NSR_JOB,and NSR_JCLIENT applicationclasses.By default, this collector isexecuted only on the server. Polling Interval: 300 seconds

n/a n/a n/a


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type

NSRServerSummary Set by NSR_SERVER Discovery,summarizes the serverinformation as reported incommands executed by thediscovery.

n/a n/a n/a

NSRUpdateAgent Is used by the NSR KM to set thePATROL Agent KM variableswhen the PATROL Console useris not authorized to update(ACL) any PATROL Agentvariables. It is activatedautomatically when the KMfails to update the PATROLAgent. Polling Interval: 300 seconds

n/a n/a n/a

* Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instance inTrueSight OM.

InfoBox

Name Description

Product Name Name of the Knowledge Module.

Product Version Version number of the Knowledge Module.

Product Release Date Release date of the Knowledge Module.

PATROL Agent Version Version number of the PATROL Agent installed on the managed system.

Application Name Name of the application monitored by this Knowledge Module.

Application Version Monitored application version number.

Server(s) Names of the discovered Servers.

Storage Node(s) Names of the discovered Storage Nodes.

Node Name(s) Name of the current managed system (node) as defined in EMCNetWorker.

Node Type Type of the node (Server or Storage Node).

Host Name Name of the host as configured on the PATROL Agent.

Platform Operating system platform as reported by PATROL Agent (HP, SOLARIS,AIX, or NT).

Operating System Operating system description as reported by PATROL Agent.

Installation Path EMC NetWorker software installation path.

Binary Path EMC NetWorker software binary paths used by NSR KM.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Name Description

Library Path EMC NetWorker software library paths used by NSR KM.

Monitoring Mode Monitoring mode of the Knowledge Module.

Monitoring Node Node currently monitoring EMC NetWorker.

Copyright Copyright (C) Sentry Software

Web Site www.bmc.com

Support [email protected]

Menu Commands

Function Description

Refresh Process Cache Forces the PATROL Agent to reload its process cache from the kernelprocess list.

Force Discovery Forces application discovery.

Refresh Parameters Forces an update of the application parameter values.

Reload Commands Forces a reload of commands used by NSR KM during the next fulldiscovery cycle. By default, all new commands are reloadedautomatically.

Administration > Start Server/Storage Node

Starts server/storage node daemons.

Administration > Stop Server/Storage Node

Stops server/storage node daemons.

Configuration > Login Accesses the Login Configuration dialog for viewing and entering NSRKM login details for the operating system.This user account should have privileges to execute EMC NetWorkeradministration commands and can use sudo privileges on UnixPATROL Agents.This user account will be used by NSR KM pre-discoveries, discoveries,data collectors, recovery actions, and InfoBoxes to execute operatingsystem commands. It will not be used by any KM commands.The password is encrypted and stored on the PATROL Agent using theBMC PATROL encryption function.

Configuration > Preloading Accesses Preloading Configuration dialog, which adds or removes theKM from PATROL Agent variable /AgentSetup/preloadedKMs.By preloading the NSR KM, the PATROL Agent will monitor the EMCNetWorker application without any PATROL Console connection.

Configuration > Monitoring Mode Accesses the Monitoring Mode Configuration dialog, which is used forenabling or disabling KM failover, when monitoring VCS clustered EMCNetWorker environment.

Configuration > Paths Accesses the Path Configuration dialog, which displays and sets allpaths used by NSR KM.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Paths are automatically discovered by the NSR KM server discovery.They are used as environment variables for executing various EMCNetWorker application commands. Altering these paths may impactthe operation of the KM.

Binary paths are used as environment variables:

$PATH (on Unix)

%PATH% (on MS Windows)

Library paths are used as environment variables:

$LD_LIBRARY_PATH (on Solaris)

$SHLIB_PATH (on HP-UX)

$LIBPATH (on AIX)

For details about other EMC NetWorker related paths, refer to the EMCNetWorker Administrator’s Guide.

Configuration > Node Type Accesses the Node Type dialog, which displays and sets the type of theEMC NetWorker application node.The NSR KM server/storage node discovery detects the type of the nodeautomatically; the type can either be Server or Storage Node. Theoperation of the KM depends on this node type.

Configuration > Node Status Accesses the Node Status Configuration dialog for viewing andmodifying the daemon names monitored for node status.The NSR KM checks for the existence of these daemons to determine thestatus of the node (parameter NSRNodeStatus). By default, thefollowing daemons are sought:

Type [default] to reset to the default configuration.

Configuration > Instance Limits Accesses the Instance Limits Configuration dialog to view and modifythe maximum number of NSR KM application instances allowed foreach application class.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Configuration > Debug Accesses the Debug Configuration dialog for enabling/disabling theNSR KM debug switches.By default, all KM debug messages are sent to a set of files and a taskwindow.

KM Status Generates a summary report containing information on the managedsystem.

About Displays information about the product and manufacturer.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_CLIENT_CONTAINERIcon

Parameters


Type

NSRClientDetails Set by NSRClientCollector.Displays all data returned to thestandard out from commandsexecuted by the data collector.

n/a n/a n/a

NSRClientCollectorExecTime Inactive standard parametermonitors the collector executiontime. To activate this parameter,use the PSL below, and restartthe PATROL Agent: %PSL pconfig("REPLACE",

"/Runtime/NSR/

NSRClientCollectorExecTim

e", 1);

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

"/Runtime/NSR/

NSRClientCollectorWarn",

3600);

seconds Warning >presetvalueorobservedmaximum(default)

CollectionStatus

InfoBox

Name Description

Collector Name Name of the data collector that sets variables and parameters underthis application instance.

Collector Last Start Date & time when the last data collection cycle started.

Collector Last End Date & time at the completion of the last data collection cycle.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Name Description

Collector Next Start Date & time when the next data collection cycle is expected to start.

Collector Status Data collector execution status (Idle or Running).

Menu Commands


Configuration > Clients Accesses the dialog for specifying which clients are to be monitored bythe NSR KM.By default, all clients configured on the server are monitored.Type [default] to reset to the default configuration.

Configuration > Clients Status Accesses the global configuration for determining the client status formonitored client instances.By default, following NSRClientState to NSRClientStatus mapping ruleis used:

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


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_CLIENTIcon

Parameters


Type

NSRClientIndexRecordCount* Set by NSRClientCollector.Displays the number of recordsfound in the index database forthis client.

count None Statistics

NSRClientIndexSpaceUsed Set by NSRClientCollector.Displays the index space usedby this client.

Kilobytes (KB) None Statistics

NSRClientIndexSpaceUsedPercent*

Set by NSRClientCollector.Displays the percentage of indexspace used by the client.

Percentage (%) None Statistics

NSRClientState Set by NSRClientCollector.Displays the state of the clientas reported in the commandexecuted by the data collector.

0 = Running1 = Not Running2 = Client Down-1 = Unknown

None Availability

NSRClientStatus Set by NSRClientCollector.Monitors the status of theclient. This status is determinedby the client status mappingrule defined in the KMcommand Configuration >Client(s) Status.

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


Warning = 1Alarm=2

Availability

NSRClientSummary Set by NSRClientCollector.Summarizes the clientinformation as reported incommands executed by the datacollector.

n/a n/a n/a

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


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


InfoBox

Name Description

Name Name of the EMC NetWorker client.

Description Description of the EMC NetWorker client.

Platform Hardware platform of the client.

Operating System Operating system of the client.

Architecture Platform architecture of the client.

CPU Type CPU Type of the client.

CPUs Number of CPUs in the client system.

Servers EMC NetWorker Servers, which can connect to the client.

Enabler in Use Displays whether the EMC NetWorker enabler code is configured forthe client.

Status Status of client connectivity from the current node.

Application Name of the application installed on the client, which responds to theconnection request.

Version Version number of the application installed on the client.

Aliases Aliases for the client.

IP Address IP address of this client.

ONC Program Number ONC program number of this client.

ONC Version Number ONC version number of this client.

ONC Transport ONC transport of this client.







EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Menu Commands


Configuration > Client Accesses the individual configuration for monitoring the selectedclient instance.This dialog allows the selected client instance to be enabled ordisabled for monitoring by the NSR KM.

Configuration >Client Status Accesses the individual configuration for determining client status forthe selected client instance.By default, the global NSRClientState to NSRClientStatus mapping ruleis used, as configured at the container level. Select [default] to revertto the client status mapping rule configured at the global/containerlevel.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_DAEMON_CONTAINERIcon

Parameters


Type

NSRDaemonDetails Set by NSRDaemonCollector.Displays all data returned to thestandard out from commandsexecuted by the data collector.

n/a n/a n/a

NSRDaemonCollectorExecTime Inactive standard parametermonitors the collector executiontime. To activate this parameter,use the PSL below, and restartthe Patrol Agent:%PSL pconfig("REPLACE",

"/Runtime/NSR/

NSRDaemonCollectorExecTim

e", 1);

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

"/Runtime/NSR/

NSRDaemonCollectorWarn",

3600);

seconds Warning >presetvalueorobservedmaximum(default)

CollectionStatus

InfoBox

Name Description





EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Name Description



Menu Commands


Reports > Daemon List Lists all running EMC NetWorker daemons.

Configuration > Daemons Accesses the dialog for specifying which daemons are to be monitoredby the NSR KM.By default following daemons are monitored.


Configuration > Daemons Status Accesses the global configuration for determining the daemon statusfor monitored daemon instances.By default following NSRDaemonState to NSRDaemonStatus mappingrule is used:

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


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_DAEMONIcon

Parameters


Type

NSRDaemonCPUDuration Set by NSRDaemonCollector.Displays the CPU secondsconsumed by the daemon.

seconds None Statistics

NSRDaemonCPUUtilization* Set by NSRDaemonCollector.Displays the percentage of CPUused by the daemon.

Percentage (%) None Statistics

NSRDaemonMemorySize* Set by NSRDaemonCollector.Displays the core image size ofthe daemon in the virtualmemory.

Kilobytes (KB) None Statistics

NSRDaemonProcessCount Set by NSRDaemonCollector.Displays the number of daemonprocesses/threads found.

processes None Statistics

NSRDaemonState Set by NSRDaemonCollector.Displays the state of thedaemon as reported in thecommand executed by the datacollector.

0 = Running1 = Sleeping2 = Waiting3 = Queued4 = Intermediate5 = Terminated6 = Stopped/Disabled7 = Growing8 = Nonexistent/Not Responding9 = Not Running-1 = Unknown

None Availability

NSRDaemonStatus Set by NSRDaemonCollector.Monitors the status of thedaemon. This status isdetermined by the daemonstatus mapping rule defined inthe KM command Configuration> Daemon(s) Status.


Warning = 1Alarm =2

Availability


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type


NSRDaemonSummary Set by NSRDaemonCollector.Summarizes the daemoninformation as reported bycommands executed by the datacollector.

n/a n/a n/a



InfoBox

Name Description

Name Name of the EMC NetWorker daemon.

Description Description of the EMC NetWorker daemon.

PID Process ID of the daemon.

PPID Parent process ID of the daemon.

Owner Owner of the daemon.

Status Status of the daemon as reported in the PATROL Agent process cache.

Command Command that started the daemon.







EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Menu Commands


Configuration > Daemon Accesses the individual configuration for monitoring the selecteddaemon instance.This dialog allows the selected daemon instance to be enabled ordisabled for monitoring by the NSR KM.

Configuration > Daemon Status Accesses the individual configuration for determining daemon statusfor the selected the daemon instance.By default, the global NSRDaemonState to NSRDaemonStatus mappingrule is used, as configured at the container level. Select [default] torevert to the daemon status mapping rule configured at the global/container level.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_DATABASE_CONTAINERIcon

Parameters


Type

NSRDatabaseBackupElapsed* Set by NSRDatabaseCollector.Displays the elapsed time sincethe last successful databasebackup.

The specified alarm ranges canbe enabled to allow the outputof the parameter to be activelymonitored. Then, if thisparameter changes to warningor alarm state, the recoveryaction will trigger an event.

hours None Statistics

NSRDatabaseDetails Set by NSRDatabaseCollector.Displays all data returned to thestandard out from commandsexecuted by the data collector.

n/a n/a n/a

NSRDatabaseCollectorExecTime Inactive standard parametermonitors the collector executiontime. To activate this parameter,use the PSL below, and restartthe Patrol Agent:%PSL pconfig("REPLACE",

"/Runtime/NSR/

NSRDatabaseCollectorExecT

ime", 1);

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

seconds Warning> presetvalue orobservedmaximum(default)

CollectionStatus


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type

%PSL pconfig("REPLACE",

"/Runtime/NSR/

NSRDatabaseCollectorWarn"

, 3600);

NSRDatabaseRetention Set by NSRDatabaseCollector.Displays the number of daysdata will be retained by thedatabase.

days n/a Statistics

InfoBox

Name Description

Last Backup Date & time when the index database was last backed up.

Last Backup Mode Backup mode of the last backup of the index database.

Last Backup Save Set ID Identifier of the last index database backup save set.

Last Backup Volume Label of the last index database backup volume.






Menu Commands


Reports > Database BackupInformation

Reports information about the previous index database backups.

Configuration > Databases Accesses the dialog for specifying which index databases are to bemonitored by the NSR KM.By default, the following database paths are monitored. Thesedatabase paths are relative to the EMC NetWorker installationdirectory (for example /NSR on Unix and C:\Program Files\NSR on MSWindows).


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02




EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_DATABASEIcon

Parameters


Type

NSRDatabaseFSSpaceUsedPercent*

Set by NSRDatabaseCollector.Monitors the percentage ofspace used by the file systemwhere the database resides.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.

Percentage (%) Alarm ifout of[0-100]rangeWarning: 95-98Alarm:98-100

Statistics

NSRDatabaseSpaceAvailable Set by NSRDatabaseCollector.Monitors the amount ofassigned space remainingavailable for use by the indexdatabase.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.

Megabytes (MB) Warning: 2-5Alarm ≤2

Availability

NSRDatabaseSpaceGrowthRate Set by NSRDatabaseCollector.Displays the growth rate of thespace used by the indexdatabase.

Megabytes persecond (MB/s)

None Statistics

NSRDatabaseSpaceUsed Set by NSRDatabaseCollector.Displays the amount ofassigned space used by theindex database.

Megabytes (MB) None Statistics

NSRDatabaseSpaceUsedPercent*

Set by NSRDatabaseCollector.Monitors the percentage ofassigned space used by theindex database.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.

Percentage (%) Alarm ifout of[0-100]rangeWarning: 95-98Alarm:98-100

Statistics


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type

Note that the total assignedspace is the used space(NSRDatabaseSpaceUsed) plusthe available space(NSRDatabaseSpaceAvailable).

NSRDatabaseSummary Set by NSRDatabaseCollector.Summarizes the databaseinformation as reported bycommands executed by the datacollector.

n/a None n/a



InfoBox

Name Description

Name Name of the EMC NetWorker index database.

Description Description of the EMC NetWorker index database.

Path Full file or directory path of the index database.

Last Purge Date & time when the index database was purged last.






Menu Commands


Configuration > Database Accesses the individual configuration for monitoring the selectedindex database instance.This dialog allows the selected database instance to be enabled ordisabled for monitoring by the NSR KM.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_LOG_CONTAINERIcon

Parameters


Type

NSRLogDetails Set by NSRLogCollector.Displays all data returned tothe standard out fromcommands executed by thedata collector.

n/a n/a n/a

NSRLogCollectorExecTime Inactive standard parametermonitors the collectorexecution time. To activate thisparameter, use the PSL below,and restart the Patrol Agent:%PSL pconfig("REPLACE",

"/Runtime/NSR/

NSRLogCollectorExecTime"

, 1);

When activated it will runevery minute and trigger awarning when the collectorruns for more than theobserved maximum time. Thismaximum time can beoverridden by a preset value(example: 3600 seconds), usingthe PSL below:%PSL pconfig("REPLACE",

"/Runtime/NSR/

NSRLogCollectorWarn",

3600);


CollectionStatus

InfoBox

Name Description



EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Name Description





Menu Commands


Reports > Messages List Reports all recent EMC NetWorker messages.

Configuration > Logs Accesses the dialog for specifying which log files are to be monitored bythe NSR KM.By default, the following log files are monitored. These log file paths arerelative to the EMC NetWorker installation directory (for example /nsr onUnix and C:\Program Files\nsr on MS Windows), unless the path is fullyqualified as for the system log on Solaris and HP-UX.


Configuration > Logs Filter Accesses the global configuration of the filter for expressions used fordetecting error messages in the monitored log file instances.By default, the following Included expressions are looked for in each logfile. If detected, the message containing the expression is added to theappropriate text parameter, unless the message also contains an Excludedexpression for the same filter.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02



Configuration > Logs Scan Limit Accesses the global configuration of the data scanning limit for monitoredlog file instances.By default, the log collector only scans 500 KB of new log data for eachmonitored log file during each data collection cycle.

Configuration > Logs AlertAcknowledgement

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


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_LOGIcon

Parameters


Type

NSRLogAlarmCount* Set by NSRLogCollector.Monitors the number of alarmmessages set in the parameter NSRLogAlarmText.

If this parameter changes toalarm state, the recovery actionwill trigger an event.

count Alarm ifout of[0-100]rangeAlarm:1-100

Statistics

NSRLogAlarmText Set by NSRLogCollector.Displays all alarm messages inthe log file which have not beenacknowledged. The filter usedby the data collector todetermine alarm messages canbe customized using the KMcommand Configuration > Log(s)Filter.

These alarm messages can beacknowledged automatically(default) or manually,depending on the configurationin the KM command Configuration > Log(s) AlertAcknowledgement. Manualacknowledgement is availableunder the KM sub-menuAcknowledgement.

n/a None n/a

NSRLogFSSpaceUsedPercent* Set by NSRLogCollector.Monitors the percentage ofspace used by the file system(where the log file resides).

Percentage (%) Alarm ifout of[0-100]rangeWarning= 95-98Alarm =98-100

Statistics


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type

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

NSRLogRendered This parameter, set by NSRLogCollector, monitorswhether raw log files arerendered in runtime.

This parameter is onlyavailable for NetWorker rawlog files.

0 = Yes1 = No-1 = Unknown

Warningif out of[0-1]rangeWarning= 1

Availability

NSRLogSpaceAvailable Set by NSRLogCollector.Monitors the available spacefor the log file to use (this isalso the available space on thefile system).If this parameter changes towarning or alarm state, therecovery action will trigger anevent.

Megabytes (MB) Warning= 2 - 5Alarm ≤2

Availability

NSRLogSpaceGrowthRate Set by NSRLogCollector.Displays the growth rate of theamount of space used by thelog file.

Kilobytes persecond (KB/s)

Warning= 2 to 5Alarm ≤2

Statistics

NSRLogSpaceUsed Set by NSRLogCollector.Displays the amount of spaceused by the log file.

Kilobytes persecond (KB/s)

None Statistics

NSRLogSpaceUsedPercent* Set by NSRLogCollector.Monitors the percentage ofcapacity used by the log file.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.Note that the total capacity isthe used space(NSRLogSpaceUsed) plusavailable space(NSRLogSpaceAvailable).

Percentage (%) Alarm ifout of[0-100]rangeWarning= 95-98 Alarm =98-100

Statistics

NSRLogSummary Set by NSRLogCollector.Summarizes the log fileinformation as reported bycommands executed by the datacollector.

n/a n/a n/a


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type

NSRLogText Set by NSRLogCollector.Displays all log text scanned bythe data collector during thelast collection cycle. The size ofthe data scanned by the datacollector is configured in theKM command Configuration >Log(s) Scan Limit.

n/a n/a n/a

NSRLogWarningCount* Set by NSRLogCollector.Monitors the number warningmessages set in the parameterNSRLogWarningText.If this parameter changes to awarning state, the recoveryaction will trigger an event.

count Alarm ifout of[0-100]rangeWarning: 1-100

Statistics

NSRLogWarningText Set by NSRLogCollector.Displays all warning messagesin the log file which have notbeen acknowledged. The filterused by the data collector todetermine warning messagescan be customized using the KMcommand Configuration > Log(s)Filter.

These warning messages can beacknowledged automatically(default) or manually,depending on the configurationin the KM command Configuration > Log(s) AlertAcknowledgement. Manualacknowledgement is availableunder the KM sub-menu

Acknowledgement.

n/a n/a n/a




EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

InfoBox

Name Description

Name Name of the EMC NetWorker log file.

Description Description of the EMC NetWorker log file.

Path Full file path of the log file.

Log File Modification Time Date & time when the log file was last modified.

Log File Size File size of the log file.

Total FS Space Total space used by the file system.

Available FS Space Space available for use by the file system.

FS Percent Used Percentage of the total file system space used.

Last Purge Date & time when the log file was last purged.







EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Menu Commands


Acknowledgement > Warnings Allows acknowledgement of warning messages detected on the selectedlog file instance.This dialog allows selective acknowledgement of "suspicious" errormessages detected in the log file and sent to the text parameter NSRLogWarningText.

Acknowledgement > Alarms Allows acknowledgement of alarm messages detected on the selectedlog file instance.This dialog allows selective acknowledgement of "failure" errormessages detected in the log file and sent to the text parameter NSRLogAlarmText.

Acknowledgement > All Allows acknowledgement of all alarm and warning messages detectedon the selected log file instance.This dialog allows acknowledgement of all error messages detected inthe log file and sent to the text parameter NSRLogWarningText orNSRLogAlarmText.

Configuration > Log Accesses the individual configuration for monitoring the selected logfile instance.This dialog allows the selected log file instance to enabled or disabledfor monitoring by the NSR KM.

Configuration > Log Filter Accesses the individual configuration of the log error filter for theselected log file instance.By default, the global log filter is used, as configured at the containerlevel.Type [default] to reset to the log filter configured at the global/container level.

Configuration > Log Scan Limit Accesses the individual configuration of the data scanning limit for theselected log file instance.By default, the global log file scanning limit is used, as configured atthe container level.

Configuration > Log AlertAcknowledgement

Accesses the individual configuration of the method ofacknowledgement for alerts on the selected log file instance.By default, the global method of log error acknowledgement is used, asconfigured at the container level.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_POLICY_CONTAINERIcon

Parameters


Type

NSRGroupDetails Set by NSRGroupCollector.Displays all data returned tothe standard out fromcommands executed by thedata collector.

n/a n/a n/a

NSRGroupCollectorExecTime Inactive standard parametermonitors the collectorexecution time. To activate thisparameter, use the PSL below,and restart the Patrol Agent: %PSL pconfig("REPLACE",

"/Runtime/NSR/

NSRGroupCollectorExecTim

e", 1);

When activated it will runevery minute and trigger awarning when the collectorruns for more than theobserved maximum time. Thismaximum time can beoverridden by a preset value(example: 3600 seconds), usingthe PSL below: %PSLpconfig("REPLACE", "/

Runtime/NSR/

NSRGroupCollectorWarn",

3600);


CollectionStatus


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

InfoBox

Name Description






Menu Commands


Configuration > Groups Accesses the dialog for specifying which groups are to be monitored bythe NSR KM.By default, all groups configured on the server are monitored.Type [default] to reset to the default configuration.

Configuration > Groups BackupRestriction

Accesses the global configuration to set a backup restriction windowfor all monitored group instances.By default, backup restriction is disabled.When the backup restriction window is defined and enabled using thisdialog, and if the group status mapping rule is configuredappropriately, an alert will be triggered if any backup activity isdetected during this restriction window.

Configuration > Groups Status Accesses the global configuration for determining the group status formonitored group instances.By default, the following NSRGroupState to NSRGroupStatus mappingrule is used:

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


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_POLICYIcon

Parameters


Type

NSRGroupBackupElapsed* Set by NSRGroupCollector.Displays the elapsed time sincethe last backup for this group,regardless of completion statusof the backup. This last backupis determined from themonitored save groups asconfigured in the KM command Configuration > Save Groupsfrom the Save Groups icon.



NSRGroupBackupSummary Set by NSRGroupCollector.Summarizes the last backup forthis group.

n/a None n/a

NSRGroupBackupThroughput* Set by NSRGroupCollector.Displays the throughput of thelast backup for this group.

Gigabytes persecond (GB/s)

None Statistics

NSRGroupFullBackupDuration

Set by NSRGroupCollector.Displays the duration of the lastsuccessful full backup for thisgroup.



EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type

NSRGroupFullBackupElapsed*

Set by NSRGroupCollector.Displays the elapsed time sincethe last successful full backupfor this group. This last backupis determined from themonitored save groups asconfigured in the KM command Configuration > Save Groupsfrom the Save Groups icon.



NSRGroupFullBackupFileCount

Set by NSRGroupCollector.Displays the number of filesbacked up in the last successfulfull backup for this group.


NSRGroupFullBackupSize Set by NSRGroupCollector.Displays the size of the lastsuccessful full backup for thisgroup.

Gigabytes (GB) None Statistics

NSRGroupIncrBackupDuration Set by NSRGroupCollector.Displays the duration of the lastsuccessful incremental backupfor this group.


NSRGroupIncrBackupElapsed* Set by NSRGroupCollector.Displays the elapsed time sincethe last successful incrementalbackup for this group. This lastbackup is determined from themonitored save groups asconfigured in the KM command Configuration > Save Groupsfrom the Save Groups icon.




EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type

NSRGroupIncrBackupFileCount

Set by NSRGroupCollector.Displays the number of filesbacked up in the last successfulincremental backup for thisgroup.


NSRGroupIncrBackupSize Set by NSRGroupCollector.Displays the size of the lastsuccessful incremental backupfor this group.


NSRGroupState Set by NSRGroupCollector.Displays the state of the group.If a backup restriction windowis defined in the KM command Configuration > Group (Groups)Backup Restriction, thisparameter will be set to Runningin Restricted Window if there isany activity during the specifiedperiod.

0 = Idle1 = Running2 = Running inRestrictedWindow3 = Cloning-1 = Unknown

None Availability

NSRGroupStatus Set by NSRGroupCollector.Monitors the status of thegroup. This status is determinedby the group status mappingrule defined in the KMcommand Configuration > Group(Groups) Status.If this status parameter changesto warning or alarm state, therecovery action will trigger anevent and annotate the last datapoint.


Warning = 1Alarm =2

Availability

NSRGroupSuccBackupElapsed*

Set by NSRGroupCollector.Displays the elapsed time sincethe last successful backup forthis group. This last backup isdetermined from the monitoredsave groups as configured in theKM command Configuration >Save Groups from the SaveGroups icon.The specified alarm ranges canbe enabled to allow the outputof the parameter to be activelymonitored. Then, if thisparameter changes to warningor alarm state, the recoveryaction will trigger an event.



EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type

NSRGroupSummary Set by NSRGroupCollector.Summarizes the groupinformation as reported bycommands executed by the datacollector.

n/a None n/a



InfoBox

Name Description

Name Name of the EMC NetWorker group.

Description Description of the EMC NetWorker group.

Autostart Auto start state of the group.

Start Time Start time of the group.

Interval Interval between save groups of this group in HH:MM format.

Parallelism Maximum number of concurrent sessions allowed for this group.

Client Retries Number of times failed clients of this group should be retried.

Clones Cloning setup for this group.

Clone Pool Volume pool name used for clone sessions.

Printer Printer on which the bootstrap save set information will be printed.

Status Current execution status of the group (Idle, Running, or Running inRestricted Window).

Last Backup Start Date & time when the last backup started for the group.

Last Backup End Date & time at the completion of the last backup for the group.

Last Backup Status Status of the last backup for the group.

Last Backup Save Group Name of the last backup for the group.

Last Full Backup Start Date & time when the last successful full backup started for the group.

Last Full Backup End Date & time at the completion of the last successful full backup for thegroup.

Last Full Backup Save Group Name of the last successful full backup for the group.

Last Incr Backup Start Date & time when the last successful incremental backup started forthe group.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Name Description

Last Incr Backup End Date & time at the completion of the last successful incrementalbackup for the group.

Last Incr Backup Save Group Name of the last successful incremental backup for the group.

Next Backup Date & time that the next backup will start for this group.






Menu Commands


Configuration > Group Accesses the individual configuration for monitoring the selectedgroup instance.This dialog allows the selected group instance to be enabled ordisabled for monitoring by the NSR KM.

Configuration > Groups BackupRestriction

Accesses the individual configuration for the backup restrictionwindow for the selected group instance.By default, the global backup restriction rule is used, as configured atthe container level.

Configuration > Groups Status Accesses the individual configuration for determining group status forthe selected group instance.By default, the global NSRGroupState to NSRGroupStatus mapping ruleis used, as configured at the container level. Select [default] to revert tothe group status mapping rule configured at the global/container level.

Configuration > Group Clients Accesses the dialog for specifying which group clients of the selectedgroup are to be monitored by the NSR KM.By default, all group clients of enabled groups are monitored. Type"[default]" to reset to the default configuration.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_PCLIENTIcon

Parameters


Type

NSRGClientBackupSummary Set by NSRGroupCollector.Summarizes the last backup forthis group client.

n/a n/a n/a

NSRGClientBackupThroughput*

Set by NSRGroupCollector.Displays the throughput of thelast backup for this groupclient.


None Statistics

NSRGClientFullBackupDuration

Set by NSRGroupCollector.Displays the duration of the lastsuccessful full backup for thisgroup client.


NSRGClientFullBackupFileCount

Set by NSRGroupCollector.Displays the number of filesbacked up in the last successfulfull backup for this group client.


NSRGClientFullBackupSize* Set by NSRGroupCollector.Displays the size of the lastsuccessful full backup for thisgroup client.


NSRGClientIncrBackupDuration

Set by NSRGroupCollector.Displays the duration of the lastsuccessful incremental backupfor this group client.


NSRGClientIncrBackupFileCount

Set by NSRGroupCollector.Displays the number of filesbacked up in the last successfulincremental backup for thisgroup client.


NSRGClientIncrBackupSize* Set by NSRGroupCollector.Displays the size of the lastsuccessful incremental backupfor this group client.



EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type

NSRGClientSummary Set by NSRGroupCollector.Summarizes the group clientinformation as reported bycommands executed by the datacollector.

n/a n/a n/a

NSRSaveSetIncludeList Set by NSRGroupCollector. Listsall files and file systemsincluded for backup for thisgroup client.

n/a n/a n/a



InfoBox

Name Description

Name Host name of the EMC NetWorker group client.

Description Description of the EMC NetWorker group client.

Group Names Names of the groups that the group client belongs to.

Schedule Name of the schedule used by the group client.

Browse Policy Browse policy of the group client.

Retention Policy Retention policy of the group client.

Directive Directive used by the group client.

Priority Backup priority of the group client.

Parallelism Maximum number of concurrent sessions allowed for this group client.

Storage Nodes Storage nodes used by this group client for backup sessions.

Clone Storage Nodes Storage nodes used by this group client for clone sessions.

Last Backup Start Date & time when the last backup started for the group client.

Last Backup End Date & time at the completion of the last backup for the group client.

Last Backup Status Status of the last backup for the group client.

Last Full Backup Save Group Name of the last successful full backup of the group client.

Last Full Backup Start Date & time when the last successful full backup started for the groupclient.

Last Full Backup End Date & time at the completion of the last successful full backup for thegroup client.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Name Description

Last Incr Backup Start Date & time when the last successful incremental backup started forthe group client.

Last Incr Backup End Date & time at the completion of the last successful incrementalbackup for the group client.

Last Backup Save Group Name of the last backup for the group client.

Last Incr Backup Save Group Name of the last successful incremental backup of the group client.






Menu Commands


Configuration > Group Client Accesses the individual configuration for monitoring the selectedgroup client instance.This dialog allows the selected group client instance to be enabled ordisabled for monitoring by the NSR KM.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_JOB_CONTAINERIcon

Parameters


Type

NSRSaveGrpActiveBackupCount*

Set by NSRSaveGrpCollector.Displays the number of activejobs currently discovered andmonitored.


NSRSaveGrpActiveCount* Set by NSRSaveGrpCollector.Displays the number of activejobs currently discovered andmonitored.


NSRSaveGrpActiveNonBackupCount*

Set by NSRSaveGrpCollector.Displays the number of activejobs currently discovered andmonitored.


NSRSaveGrpDetails Set by NSRSaveGrpCollector.Displays all data returned to thestandard out from commandsexecuted by the data collector.

n/a n/a n/a

NSRSaveGrpCollectorExecTime Inactive standard parametermonitors the collector executiontime. To activate this parameter,use the PSL below, and restartthe Patrol Agent:%PSL pconfig("REPLACE",

"/Runtime/NSR/

NSRSaveGrpCollectorExecTi

me", 1);

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

seconds Warning >presetvalue orobservedmaximum(default)

CollectionStatus


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type


"/Runtime/NSR/

NSRSaveGrpCollectorWarn",

3600);

NSRSaveGrpManualSaves Set by NSRSaveGrpCollector.Displays whether the manualsaves are enabled or disabled.

0 = Enabled1 = Disabled-1 = Unknown

None Availability




EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

InfoBox

Name Description






Menu Commands


Force Full Collection Allows the user to force the data collector for save groups to perform afull discovery during the next collection cycle.

Acknowledgement > Warnings Allows acknowledgement of warning alerts occurring on anymonitored save group instance.This dialog allows acknowledgement of any save group in a"suspicious" state (which sets the parameter NSRSaveGrpStatus toWarning).

Acknowledgement > Alarms Allows acknowledgement of alarms occurring on any monitored savegroup instance.This dialog allows acknowledgement of any save group in a "failure"state (which sets the parameter NSRSaveGrpStatus to Alarm).

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

Configuration > Save Groups Accesses the dialog for specifying which save groups are to bemonitored by the NSR KM.By default, all scheduled save groups on the server are monitoredaccording to the following conditions:

The age of a save group is calculated from the save group start time.The status of a save group is determined by the state of the save group(from the parameter NSRSaveGrpState) and the save group statusmapping rule, described below.

Configuration > Save GroupsStatus

Accesses the configuration dialog for determining the status for allmonitored job instances.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


By default following NSRSaveGrpState to NSRSaveGrpStatus mappingrule is used:

Select [default] to reset to the default save group status mapping rule.

Configuration > Save Groups AlertAcknowledgement

Accesses the configuration dialog for specifying the method used toacknowledge alerts triggered for NSRSaveGrpStatus. Alerts can eitherbe manually (default configuration) or automatically acknowledged.

Configuration > Save GroupsDate/Time Format

Accesses the configuration of date/time format and time zone formonitored save group instances.By default, the format used by EMC NetWorker for the date/time of apending request is set to DAY MON DD HH:MM:SS YYYY. The date/timeis then converted by the NSR KM using the system time zone on thePATROL Agent (system time zone is indicated by an empty field).To reset to the default date/time format, blank out the date/time field.To reset to the default time zone, blank out the time zone field.

Configuration > Save Clients Sets which save clients will be monitored. The possible values are:NoneFailed OnlySucceeded OnlyAll

By default, only the failed save clients are monitored.

Configuration > Save ClientsStatus

Indicates which states will trigger a warning or an alarm on the Statusparameter.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_JOBIcon

Parameters


Type

NSRSaveGrpDuration Set by NSRSaveGrpCollector.Displays the duration of thesave group from the start.


NSRSaveGrpFileCount Set by NSRSaveGrpCollector.Displays the number of filesbacked up for this save group.


NSRSaveGrpSize Set by NSRSaveGrpCollector.Displays the amount of databacked up for the save group.


NSRSaveGrpState Set by NSRSaveGrpCollector.Displays the state of the savegroup. This is determined usingthe save group completionstate and number of pending,succeeded & failed save sets.

0 = Completed1 = In Progress2 = Completed/Errors3 = In Progress/Errors4 = Aborted5 = Failed-1 = Unknown

None Availability

NSRSaveGrpStatus Set by NSRSaveGrpCollector.Monitors the status of the savegroup. This status isdetermined by the save groupstatus mapping rule defined inthe KM command Configuration> Save Groups Status.



Warning= 1Alarm =2

Availability


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type

NSRSaveGrpSummary Set by NSRSaveGrpCollector.Summarizes the save groupinformation as reported bycommands executed by thedata collector.

n/a n/a n/a

NSRSaveGrpText Set by NSRSaveGrpCollector.Displays all reported messagesrelated to this save group.

n/a n/a n/a

NSRSaveGrpThroughput* Set by NSRSaveGrpCollector.Displays the throughput of thissave group.


None Statistics

NSRSaveSetCount Set by NSRSaveGrpCollector.Displays total number of savesets in this save group.


NSRSaveSetFailedCount Set by NSRSaveGrpCollector.Displays number of failed savesets in this save group.


NSRSaveSetList Set by NSRSaveGrpCollector.Lists all savesets for this savegroup.

n/a n/a n/a

NSRSaveSetPendingCount Set by NSRSaveGrpCollector.Displays number of pendingsave sets in this save group.


NSRSaveSetSucceededCount Set by NSRSaveGrpCollector.Displays number of succeededsave sets in this save group.




InfoBox

Name Description

Save Group Save group details (<Group Name> @ <Save Group Start Time>).

Type Type of the save group (Backup, Restore, etc.).

Level Backup level of the save group (Full, Incr, etc.).

Status Status of the save group.

Completion Status Completion status of the save group.

Group Name Name of the group the save group belongs to.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Name Description

Start Date & time when the save group was initiated. This is interpretedusing the Save Group Date/Time Format defined in the KM menucommand.

End Date & time at the completion of the save group. This is interpretedusing the Save Group Date/Time Format defined in the KM menucommand.

Duration Duration of the save group.

Size Size of the data that has been written.

Files Number of files that have been written.

Pending Save Sets Number of pending savesets.

Succeeded Save Sets Number of succeeded savesets.

Failed Save Sets Number of failed savesets.

Clients Details Saveset(s) client(s) details for the save group.

Percent Completed Estimated percentage of the save group that has been completed incomparison with the last similar successful save group for the samegroup, group client, and level.

Time Remaining Remaining time of the save group in comparison with the last similarsuccessful save group.

Last Backup Start Date & time when the last similar successful backup started.

Last Backup End Date & time at the completion of the last similar successful backup.

Last Backup Save Group Name of the last similar successful backup.

Last Backup Duration Duration of the last similar successful backup.

Last Backup Size Amount of data written by the last similar successful backup.

Last Backup Files Number of files written by the last similar successful backup.







EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Menu Commands


Acknowledgement > Alert Allows acknowledgement of all warnings and alarms occurring on theselected save group instance.This dialog allows acknowledgement if the selected save groupinstance is in a "suspicious" or "failure" state (which sets theparameter NSRSaveGrpStatus to Warning or Alarm, respectively).


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_JCLIENTIcon

Parameters


Type

NSRSaveClientState Displays the state of the saveclient.

0 = Succeeded1 = Failed-1 = Unknown

None Availability

NSRSaveClientStatus Monitors the status of the saveclient.


Warning = 1Alarm =2

Availability

NSRSaveClientText Displays all reported messagesrelated to this save client.

n/a n/a n/a


InfoBox

Name Description

Client Name Name of the client.

Group Name Name of the group the save group belongs to.

Start Date & time when the save group was initiated. This is interpretedusing the Save Group Date/Time Format defined in the KM menucommand.

End Date & time at the completion of the save group. This is interpretedusing the Save Group Date/Time Format defined in the KM menucommand.

Status Status of the save group.







EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Menu Commands

There are no KM commands for this application class.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_MOUNT_CONTAINERIcon

Parameters


Type

NSRRequestDetails Set by NSRRequestCollector.Displays all data returned tothe standard out fromcommands executed by the datacollector.

n/a n/a n/a

NSRRequestCollectorExecTime Inactive standard parametermonitors the collectorexecution time. To activate thisparameter, use the PSL below,and restart the Patrol Agent:%PSL pconfig("REPLACE",

"/Runtime/NSR/

NSRRequestCollectorExecTi

me", 1);

When activated it will run everyminute and trigger a warningwhen the collector runs formore than the observedmaximum time. This maximumtime can be overridden by apreset value (example: 3600seconds), using the PSL below:%PSL pconfig("REPLACE",

"/Runtime/NSR/

NSRRequestCollectorWarn",

3600);

seconds Warning >presetvalue orobservedmaximum(default)

CollectionStatus

InfoBox


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Name Description






Menu Commands


Reports > Pending Requests Reports a list of all pending requests.

Configuration > Pending Requests Accesses the dialog for specifying which pending requests are to bemonitored by the NSR KM.By default, all pending requests aremonitored for 1 day. The age of a pending request is calculated fromthe pending request time. The status of a pending request isdetermined by the state of the pending request (from the parameter NSRRequestState) and the pending request status mapping rule,described below.

Configuration > Pending RequestsStatus

Accesses the configuration for determining the status for all monitoredpending request instances.By default, the following NSRRequestState to NSRRequestStatusmapping rule is used:

Select [default] to reset to the default pending request status mappingrule.

Configuration > Pending RequestsDate/Time Format

Accesses the configuration of the date/time format and time zone forall instantiated pending requests.By default, the format used by EMC NetWorker for the date/time of apending request is set to DAY MON DD HH:MM:SS YYYY. The date/timeis then converted by the NSR KM using the system time zone on thePATROL Agent (system time zone is indicated by an empty field).To reset to the default date/time format, blank out the date/time field.To reset to the default time zone, blank out the time zone field.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_MOUNTIcon

Parameters


Type

NSRRequestElapsed* Set by NSRRequestCollector.Displays the elapsed time sincethe pending request was issued.

minutes None Statistics

NSRRequestState Set by NSRRequestCollector.Displays the state of thepending request as reported inthe command executed by thedata collector.

0 = Completed1 = Pending-1 = Unknown

None Availability

NSRRequestStatus Set by NSRRequestCollector.Monitors the status of thepending request. This status isdetermined by the pendingrequest status mapping ruledefined in the KM command Configuration > PendingRequest(s) Status.



Warning = 1Alarm =2

Availability

NSRRequestSummary Set by NSRRequestCollector.Summarizes the pending requestinformation as reported bycommands executed by the datacollector.

n/a n/a n/a




EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

InfoBox

Name Description

Request Identifier assigned to the pending request by NSR KM (<Volume Pool/Volume> on <Server/Storage Node Name>.

Description Description of the pending request.

Purpose Purpose of the pending request.

Volume Requested volume label.

Volume Pool Volume pool of the requested media.

Volume Type Volume type of the requested media.

Mode Mode of the pending request (Write or Read).

Storage Node Host name of the storage node that issued the pending request.

Priority Priority of the pending request.

Number of Media Number of media required for the pending request.

Request Time Date & time that the pending request was issued. This is interpretedusing the Pending Request Date/Time Format defined in the KM menucommand.

Suggestion Last suggestion issued for the pending request.






Menu Commands

There are no KM commands for this application class.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_LIBRARY_CONTAINERIcon

Parameters


Type

NSRJukeboxDetails Set by NSRJukeboxCollector.Displays all data returned to thestandard out from commandsexecuted by the data collector.

n/a n/a n/a

NSRJukeboxCollectorExecTime Inactive standard parametermonitors the collector executiontime. To activate this parameter,use the PSL below, and restartthe Patrol Agent:%PSL pconfig("REPLACE",

"/Runtime/NSR/

NSRJukeboxCollectorExecTi

me", 1);


"/Runtime/NSR/

NSRJukeboxCollectorWarn",

3600);

Warning >preset value orobservedmaximum(default)

seconds CollectionStatus

InfoBox

Name Description





EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Name Description



Menu Commands


Configuration > Jukeboxes Accesses the dialog for specifying which jukeboxes are to be monitoredby the NSR KM.By default, all local and remote jukeboxes are monitored for a serverand all local jukeboxes are monitored for a storage node.Type [default] to reset to the default configuration.

Configuration > Jukeboxes Status Accesses the global configuration for determining the status formonitored jukebox instances.By default, the following NSRJukeboxState to NSRJukeboxStatusmapping rule is used:

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

Configuration > Jukeboxes AutoMedia Mgmt Status

Accesses the dialog for determining the status mapping rule.

Configuration > Jukebox DevicesStatus

Accesses the global configuration for determining the status formonitored jukebox device instances (configured under monitoredjukebox instances).By default, the following NSRJDeviceState to NSRJDeviceStatus mappingrule is used:

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


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_LIBRARYIcon

Parameters


Type

NSRJukeboxAutoMediaMgmtState Set by NSRJukeboxCollector.Displays the state of the jukeboxauto media managementconfiguration.

0 = Yes1 = No-1 = Unknown

None Availability

NSRJukeboxAutoMediaMgmtStatus

Set by NSRJukeboxCollector.Monitors the status of thejukebox auto mediamanagement configuration. Thisstatus is determined by thestatus mapping rule defined inthe KM command Configuration> Jukebox (Jukeboxes) AutoMedia Mgmt Status.



Warning = 1Alarm =2

Availability

NSRJukeboxCleaningLeftCount Set by NSRJukeboxCollector.Displays the number of uses lefton the cleaning tape loaded inthis jukebox.

count Warning = - 1

Statistics

NSRJukeboxState Set by NSRJukeboxCollector.Displays the jukebox state,which is derived from thejukebox resource. It will notperform any remote jukebox testcommand on the storage node.

0 = Running1 = Event Found2 = Service Mode3 = No EnabledJukebox Devices4 = Error-1 = Unknown

None Availability


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type

NSRJukeboxStatus Set by NSRJukeboxCollector.Monitors the status of thejukebox. This status isdetermined by the jukeboxstatus mapping rule defined inthe KM command Configuration> Jukebox (Jukeboxes) Status.



Warning = 1Alarm =2

Availability

NSRJukeboxSummary Set by NSRJukeboxCollector.Summarizes the jukeboxinformation as reported bycommands executed by the datacollector.

n/a n/a n/a

NSRJukeboxThroughput* Set by NSRJukeboxCollector.Displays the total throughput ofeach jukebox device during thelast backup save groups.


None Statistics

NSRJukeboxUpDriveCount Set by NSRJukeboxCollector.Displays the number up / onlinestate drives in this roboticlibrary.



NSRJukeboxVolumeAssignedCount

Set by NSRJukeboxCollector.Displays the number ofassigned volume loaded in thisjukebox. (Assigned volumes areregistered tape volumesassigned to a volume pool.)


NSRJukeboxVolumeCount Set by NSRJukeboxCollector.Displays the total number ofvolumes loaded in this jukebox.


NSRJukeboxVolumeEmptyCount

Set by NSRJukeboxCollector.Displays the number of emptyvolumes loaded in this jukebox.(Empty volume are tape volumeswith 0% used space.)



EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type

NSRJukeboxVolumeEmptyPercent*

Set by NSRJukeboxCollector.Monitors the percentage ofempty volumes against the totalnumber of volumes loaded inthis jukebox.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.

% Alarm ifout of[0-100]rangeWarning: 2-5Alarm:0-2

Statistics



InfoBox

Name Description

Name Name of the jukebox.

Description Description of the jukebox.

Model Model of the jukebox.

Storage Node Name of the remote host where the jukebox is connected.

Control Port Control port of the jukebox on the remote host.

Enabled Enabled state of the jukebox.

Status Status of the jukebox which is determined by the NSR KM.

Last Operation Last operation performed by EMC NetWorker on this jukebox.

Last Operation Message Message from the last operation on this jukebox.

Event Message Pending event message on this jukebox.

Number of Devices Number of jukebox devices configured on this jukebox.

Devices Devices configured on this jukebox.







EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Menu Commands


Reports > Jukebox Contents Reports the contents of the selected jukebox.

Configuration > Jukebox Accesses the individual configuration for monitoring the selectedjukebox instance.This dialog allows the selected jukebox instance to be enabled ordisabled for monitoring by the NSR KM.

Configuration > Jukebox Status Accesses the individual configuration for determining the status forthe selected jukebox instance.By default, the global NSRJukeboxState to NSRJukeboxStatus mappingrule is used, as configured at the container level. Select [default] torevert to the jukebox status mapping rule configured at the global/container level.

Configuration > Jukebox AutoMedia Mgmt Status

Accesses the dialog for determining the status mapping rule.

Configuration > Jukebox Devices Accesses the dialog for specifying which devices of the selectedjukebox are to be monitored by the NSR KM.By default, all jukebox devices of the selected jukebox are monitored.Type [default] to reset to the default configuration.

Configuration > Jukebox DevicesStatus

Accesses the configuration for determining status for the monitoreddevice instances on the selected jukebox instance.By default, the global NSRJDeviceState to NSRJDeviceeStatus mappingrule is used, as configured at the container level. Select [default] torevert to the device status mapping rule configured at the global/container level.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_LDEVICEIcon

Parameters


Type

NSRJDeviceSessionCount* Set by NSRJukeboxCollector.Displays the number ofsessions configured for thejukebox device.

sessions None Statistics

NSRJDeviceSessionMax* Set by NSRJukeboxCollector.Displays the maximumnumber of sessionsconfigured for the jukeboxdevice.


NSRJDeviceSessionTarget* Set by NSRJukeboxCollector.Displays the number of targetsessions configured for thejukebox device.


NSRJDeviceState Set by NSRJukeboxCollector.Displays the state of thejukebox device. This isdetermined from the jukeboxdevice control information.

0 = Idle1 = Mounted2 = Verify Label3 = Label4 = Eject5 = Read6 = Setting Up forWriting7 = Write 8 = CleaningRequired9 = Service Mode10 = Error11 = Disabled12 = Failure-1 = Unknown

None Availability


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type

NSRJDeviceStatus Set by NSRJukeboxCollector.Monitors the status of thejukebox device. This status isdetermined by the jukeboxdevice status mapping ruledefined in the KM command Configuration > JukeboxDevice(s) Status.


0 = Ok1 = Suspicious 2 = Failure

Warning= 1Alarm = 2

Availability

NSRJDeviceSummary Set by NSRJukeboxCollector.Summarizes the jukeboxdevice information asreported by commandsexecuted by the datacollector.

n/a n/a n/a

NSRJDeviceThroughput* Set by NSRJukeboxCollector.Displays the throughput of thejukebox device during the lastsave group.


None Statistics



InfoBox

Name Description

Name Name of the jukebox device.

Description Description of the device.

Path Device path of the device.

Type Volume type used in the device.

Storage Node Name of the remote host where the device is connected.

Enabled Enable state of the device.

Status Status of the device as determined by the NSR KM.

Read Only Displays whether the device is reserved only for read operations.

Jukebox Name Name of the jukebox where the device is located.

Operation Current operation performed by EMC NetWorker on this device.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Name Description

Message Current message on the device.

Volume Name Name of the volume mounted on the device.

Cleaning Required Displays whether the device requires cleaning.

Date Last Cleaned Date & time when the last cleaning was performed on the device.






Menu Commands


Administration > Enable Device Allows the selected jukebox device to be enabled.

Administration > Disable Device Allows the selected jukebox device to be disabled.

Configuration > Jukebox Device Accesses the individual configuration for monitoring the selectedjukebox device instance.This dialog allows the selected device instance to be enabled ordisabled for monitoring by the NSR KM.

Configuration > Jukebox DeviceStatus

Accesses the individual configuration for determining the jukeboxdevice status for the selected jukebox device instance.By default, the NSRJDeviceState to NSRJDeviceStatus mapping ruleconfigured at the parent level is used. (Note that if the mapping rulehas not been modified for the parent jukebox, then the default is theglobal mapping rule configured at the container level.) Select [default]to revert to the jukebox device status mapping rule configured at theparent instance level.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_DEVICE_CONTAINERIcon

Parameters


Type

NSRDeviceDetails Set by NSRDeviceCollector.Displays all data returned tostandard out from commandsexecuted by the data collector.

n/a n/a n/a

NSRDeviceCollectorExecTime Inactive standard parametermonitors the collector executiontime. To activate this parameter,use the PSL below, and restartthe Patrol Agent:%PSL pconfig("REPLACE",

"/Runtime/NSR/

NSRDeviceCollectorExecTim

e", 1);


"/Runtime/NSR/

NSRDeviceCollectorWarn",

3600);


CollectionStatus

InfoBox

Name Description





EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Name Description



Menu Commands


Configuration > StandaloneDevices

Accesses the dialog for specifying which standalone devices are to bemonitored by the NSR KM.By default, all local and remote standalone devices are monitored fora server and all local standalone devices are monitored for a storagenode. Type [default] to reset to the default configuration.

Configuration > StandaloneDevices Status

Accesses the global configuration for determining the status for allmonitored standalone device instances.By default, the following NSRDeviceState to NSRDeviceStatus mappingrule is used:

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


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_DEVICEIcon

Parameters


Type

NSRDeviceSessionCount* Set by NSRDeviceCollector.Displays the number of sessionsconfigured for the device.


NSRDeviceSessionMax* Set by NSRDeviceCollector.Displays the maximum numberof sessions configured for thedevice.


NSRDeviceSessionTarget* Set by NSRDeviceCollector.Displays the number of targetsessions configured for thedevice.


NSRDeviceState Set by NSRDeviceCollector.Displays the state of thestandalone device.

0 = Idle1 = Mounted2 = Verify Label3 = Label4 = Eject5 = Read6 = Setting Upfor Writing7 = Write8 = CleaningRequired9 = ServiceMode10 = Error11 = Disabled12 = Failure-1 = Unknown

None Availability

NSRDeviceStatus Set by NSRDeviceCollector.Monitors the status of thestandalone device. This status isdetermined by the standalonedevice status mapping ruledefined in the KM command Configuration > StandaloneDevice(s) Status.


Warning= 1Alarm = 2

Availability


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type


NSRDeviceSummary Set by NSRDeviceCollector.Summarizes the standalonedevice information as reportedby commands executed by thedata collector.

n/a n/a n/a

NSRDeviceThroughput* Set by NSRDeviceCollector.Displays the throughput of thestandalone device during thelast save group.


None Statistics



InfoBox

Name Description

Name Name of the standalone device.

Description Description of the device.

Path Device path of the device.

Type Volume type used in the device.

Storage Node Name of the device host where the device is connected.

Enabled Enable state of the device.

Status Status of the device.

Read Only Displays whether the device is reserved only for read operations.

Operation Current operation performed by EMC NetWorker on this device.

Message Current message on the device.

Volume Name Name of the volume mounted on the device.

Cleaning Required Displays whether the device requires cleaning.

Date Last Cleaned Date & time when the last cleaning was performed on the device.




EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Name Description




Menu Commands


Administration > Mount Tape Mounts the tape on the selected standalone device.

Administration > Unmount Tape Unmounts the tape on the selected standalone device.

Administration > Enable Device Allows the selected standalone device to be enabled.

Administration > Disable Device Allows the selected standalone device to be disabled.

Configuration > StandaloneDevice

Accesses the individual configuration for monitoring the selectedstandalone device instance.This dialog allows the selected standalone device instance to beenabled or disabled for monitoring by the NSR KM.

Configuration > StandaloneDevice Status

Accesses the individual configuration for determining device status forthe selected standalone device instance.By default, the global NSRDeviceState to NSRDeviceStatus mapping ruleis used, as configured at the container level. Select [default] to resumeto the standalone device status mapping rule configured at the global/container level.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_POOL_CONTAINERIcon

Parameters


Type

NSRPoolDetails Set by NSRPoolCollector.Displays all data returned to thestandard out from commandsexecuted by the data collector.

n/a n/a n/a

NSRPoolCollectorExecTime Inactive standard parametermonitors the collector executiontime. To activate this parameter,use the PSL below, and restartthe Patrol Agent:%PSL pconfig("REPLACE",

"/Runtime/NSR/

NSRPoolCollectorExecTime"

, 1);


"/Runtime/NSR/

NSRPoolCollectorWarn",

3600);


CollectionStatus

InfoBox

Name Description





EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Name Description



Menu Commands

KM Command Action

Configuration > Volume Pools Accesses the dialog for specifying which volume pools are to bemonitored by the NSR KM.By default, all volume pools configured on the server/storage node aremonitored, except for "NonFull" and "Offsite".Type [default] to reset to the default configuration.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_POOLIcon

Parameters


Type

NSRPoolSpaceAvailable* Set by NSRPoolCollector.Monitors the available volumespace for the backup data to usein this volume pool.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.

Gigabytes (GB) None Availability

NSRPoolSpaceGrowthRate Set by NSRPoolCollector.Displays the growth rate of thetotal volume space used by thebackup data in this volumepool.

Gigabytes persecond (GB/s)

None Statistics

NSRPoolSpaceUsed* Set by NSRPoolCollector.Displays the total volume spaceoccupied by the backup data inthis volume pool.


NSRPoolSpaceUsedPercent* Set by NSRPoolCollector.Monitors the percentage of totaloccupied volume space againstthe total volume capacity of thisvolume pool (not including anyscratch volume).If this parameter changes towarning or alarm state, therecovery action will trigger anevent.

Percentage (%) Alarm ifout of [0-100]rangeWarning:95-98Alarm:98-100

Statistics

NSRPoolSummary Set by NSRPoolCollector.Summarizes the volume poolinformation as reported bycommands executed by the datacollector.

n/a n/a n/a


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type

NSRVolumeActiveCount Set by NSRPoolCollector.Displays the number of activevolumes in this volume pool.(Active volumes are availabletape volumes where data can bewritten without anyintervention.)


NSRVolumeActivePercent* Set by NSRPoolCollector.Monitors the percentage ofactive volumes against the totalnumber of volumes in thisvolume pool.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.

Percentage (%) Alarm ifout of [0-100]rangeWarning:2-5Alarm: 0-2

Statistics

NSRVolumeAvailableCount Set by NSRPoolCollector.Displays the number of volumesassigned to this volume pool.


NSRVolumeAvailablePercent* Set by NSRPoolCollector.Monitors the percentage ofavailable volumes against thetotal number of volumes in thisvolume pool.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.

Percentage (%) Alarm ifout of [0-100]rangeWarning:2-5Alarm: 0-2

Statistics

NSRVolumeCount Set by NSRPoolCollector.Displays the total number ofvolumes in this volume pool.


NSRVolumeEmptyCount Set by NSRPoolCollector.Displays the number of emptyvolumes in this volume pool.(Empty volumes are availabletape volumes with no datastored on them.)


NSRVolumeFullCount Set by NSRPoolCollector.Displays the number of fullvolumes in this volume pool.("Full" is a possible status for atape volume.)


NSRVolumeFullPercent* Set by NSRPoolCollector.Monitors the percentage of fullvolumes against the totalnumber of volumes in thisvolume pool.

Percentage (%) Alarm ifout of [0-100]rangeWarning:95-98

Statistics


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Type


Alarm:98-100

NSRVolumeManualRecycleCount

Set by NSRPoolCollector.Displays the number of volumesin this volume pool, whichrequire manual recycling.("Manually-recyclable" volumeis a possible volume state set ontape volumes.)


NSRVolumeReadOnlyCount Set by NSRPoolCollector.Displays the number of readonly volumes in this volumepool. ("Read Only" is a possiblevolume flag set on tapevolumes.)




InfoBox

Name Description

Name Name of the volume pool.

Description Description of the pool.

Type Type of the pool.

Server Name of the EMC NetWorker server where the pool is defined.

Enabled Enable state of the pool.

Archive Only Displays whether the pool is reserved only for archive operations.

Groups Groups that are allowed to use the pool.

Clients Clients that are allowed to use the pool.

Save Sets Save sets that are allowed to use the pool.

Levels Backup levels that are allowed to use the pool.

Devices Devices that are allowed to use the pool.

Volume Type Preferred volume type for the pool.




EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Name Description




Menu Commands


Reports > Volumes List Reports all volumes in the volume pool.

Configuration > Volume Pool Accesses the configuration for monitoring the selected volume poolinstance.This dialog allows the selected volume pool instance to be enabled ordisabled for monitoring by the NSR KM.


EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

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

Managing baselines

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

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

Managing Key Performance Indicators

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

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

Additional Information andSupport

161 Troubleshooting

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

TroubleshootingRefer to the table below to diagnose any problems you may encounter when installing orrunning the EMC NetWorker KM for PATROL.

For any problem, look for error messages on the PATROL Console System Output Window (SOW). Mosterror messages are self -explanatory.

Most KM problems are reported in the KM Status Report, which can be viewed by selecting the KMcommand KM Status f rom the Legato NetWorker or NSR_SETUP icon. Run this report to diagnose anyproblems.

The NSR KM triggers PEM events for most severe problems. Each event triggered from the KM includes anExpert Advice, which provides details about the problem and some suggestions to resolve it.

Problem Possible Resolution

Unable to find NSR_LOAD.kml

Check that the Load KM browser is looking for *.kml files under PATROL_HOME/lib/

knowledge folder.

EMC NetWorker KM for PATROL files have not been installed correctly underthe PATROL installation directory on the PATROL Console.

NSR_SETUP icon does not appear after loading

Check whether this managed node is a supported EMC NetWorker node (server or storagenode), and it is configured properly.

Check that the version of EMC NetWorker is supported by EMC NetWorker KM for PATROL.

Check that there is no KM version mismatch between the PATROL Console and the PATROLAgent. Check the messages in the PATROL Console SOW to verify this.

Check whether the PATROL Agent tuning variable, /AgentSetup/AgentTuning/pslInstructionMax has been increased as suggested in Changes to BMC PATROL. Check themessages in the PATROL Console SOW.

Check whether the PATROL Agent user has necessary privileges added in the Agent’sAccess Control List (/AgentSetup/accessControlList) in order to read and write to theAgent Configuration Database.

Parameter NSRLoginStatus is in suspicious (warning) status

This parameter will also show a “suspicious” state if any command executedby NSR KM fails.

Check the annotation point on the first state change data point of this parameter to lookfor any failing commands. If an annotation point cannot be found, or if it is not up-to-date,check the KM Status Report, which can be viewed by selecting the KM command KMStatus from the EMC NetWorker icon. These errors are produced from the EMC NetWorkercommands executed by the NSR KM.

Check that the operating system user configured in the KM command Configuration >Login can execute all EMC NetWorker commands and access the EMC NetWorker files.

All/some KM objects disappear from the Console

Check whether there is a KM version mismatch between the PATROL Console and thePATROL Agent, possibly after an improper upgrade of the KM. Check the messages in thePATROL Console SOW to verify this.

162Troubleshooting

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Check that the NSR KM login details are still valid. Has the password changed on thesystem? Look for any error messages on the SOW, and check for additional information inthe last annotation point for parameter NSRLoginStatus.

Behavior of the NSR KM has notchanged inaccordance with theRelease Notes aftera KM upgrade

Check the version of the KM from the main InfoBox. If it has not changed, then theinstallation is not complete. Make sure both the PATROL Console and the PATROL Agentare uninstalled and installed correctly during the KM upgrade.

NSR KM takes a longtime to refreshthe parameters and application classes on the PATROL Console

Data collectors run according to their scheduling interval (polling cycle)defined in the KM. These intervals are defined for a standard environment withminimal resource impact. These intervals can be customized from the PATROLDeveloper Console to suit your environment. Refer to the PATROL Console UserGuide for more details.

Poor performance of the EMC NetWorker server/storage node after installing the KM

This happens if the NSR KM is installed on a heavily used system. Depending on the complexity of your EMC NetWorker environment, the NSR KM may consume more resources to interrogate the application and process the data. In such a complex environment, the NSR KM may require some fine tuning to optimize the available resources. Consider the following options:

Disable monitoring of unnecessary application instances. This can be achieved by usingthe appropriate KM command Configuration > <Component(s)>.

Increase the scheduling interval (polling cycle) for data collectors.

Deactivate unnecessary data collectors and associated application classes.

Deactivate unnecessary data collectors during selected time intervals, where there areno EMC NetWorker activity. For example, if the save group monitoring can be disabledbetween 9 am and 4 pm everyday, except weekends, then disable save group datacollector (NSRSaveGrpCollector) during this period, using following PSL through PATROLConsole:

%PSL pconfig("REPLACE","/NSR/NSRSaveGrpCollectorMode",

"0|32400|57600|0|0|||||||||||0|0");

Here the pconfig variable is named as: <collector name>Mode. The valuecontains following details, delimited by pipe (|):enabled (1)/disabled (0) data collection, default start/end times in number of seconds since midnight, start/end times for non-default daysstarting from Sunday through to Saturday.

Purge unnecessary information in EMC NetWorker index databases and log files.

If there are too many clients configured in EMC NetWorker, the NSRClientCollector andNSRGroupCollector may affect the overall performance. In such environment disable theNSRClientCollector, or set their instance limits to 0 (zero), using menu Configuration >Instance Limits.

Defining a "no command execution window" for all collectors will pause runningcommands at peak times or during NetWorker maintenance windows. This can be setusing the PSL below:

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

"23:59:00|120"); %PSL unset("/NSR_SERVER/noExecuteEnd");

The value of this permanent configuration variable is in format “<start time in HH:MM:SS24-hour clock>|<duration in seconds>”. The above “23:59:00|120” sets all collectors tosleep between 23:59:00 and 00:01:00 (2 minutes) every day before executing commands.

163 Troubleshooting

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02


Also this noExecutewindow supports multiple time windows:

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

["23:59:00|120","11:59:00|120"]);

Old active save groups are not removed from the console

By default, all active save groups are monitored, and they are exempted from ageing. It is possible to change this behaviour by using following PSL through PATROL Console:%PSL pconfig("REPLACE","/NSR/AgeActiveJobs", true);

Infinite Loop Errors(Error messages on the SOW reporting that some NSR KMdata collectors may be in an infinite loop)

Check the setting of the tuning variable /AgentSetup/AgentTuning/pslInstructionMax.

PATROL Agent uses the pre-configured tuning variable (/AgentSetup/AgentTuning/pslInstructionMax) to stop running PSL functions in an infiniteloop. When a PSL function reaches this maximum threshold, it reports thiserror, and puts the execution of this function to the back of the process queue.This will not only delay the data collector, it will also impact the performanceof the system.

To resolve this situation, the maximum number of instructions should beincreased to an optimum value. This depends on the complexity of yourenvironment. It is required that the default value of 500,000 should beincreased to at least 5,000,000 on a standard EMC NetWorker environment toenable the NSR KM data collectors to execute without impacting your system.

If this still does not resolve the problem, you can disable this functionality by setting the value of the tuning variable to zero.

Unable to turn onthe KM Debug

If you are unable to turn on the KM Debug following the method described in Debugging the KM, you turn the debug on by setting appropriate PATROL Agentconfiguration variable with a timestamp value. This timestamp valuedetermines when the debug should be turned off. For example, to turn on thedebug for 60 minutes from now, run the following PSL through PATROL Console:

%PSL pconfig("REPLACE","/NSR/<component>Debug",

time()+3600);

Where <component> is either server for debugging the server discovery orname of the collector component in lower case followed by Collector, likedaemonCollector for debugging daemon collector.

Old acknowledged save groups arestill kept in the pconfig database.

By default the KM stores all acknowledged save groups. Use the following PSL through PATROL Console to keep only the last <Number> of save groups:


"/NSR/NSR_JOB/jobAcknowledgementCapacity",

<Number>);

164Where to Find Additional Help

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Where to Find Additional HelpAdditional help for BMC PATROL can be found in the following locations:

PATROL Console User Guide

PATROL Console Online Help

Other PATROL Manuals and Guides

http://www.bmc.com/support_home

Additional help for EMC NetWorker can be found in the following locations:

EMC NetWorker Administrator’s Guide

EMC NetWorker Release Supplement

Other EMC NetWorker Documentation

http://www.emc.com/domains/legato/index.htm

Additional help for EMC NetWorker Knowledge Module for PATROL can be found on the SentryWebsite: www.sentrysoftware.com

165

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Index

- A -Abnormalities 158

Access

Operating System 15

Permissions 15Acknowledge

Log Alerts 78

Save Group Alerts 78Acknowledgement

Configure 68

Logs 68

Save Groups 68Adapter 51

Administer

Pending Requests 53

Standalone Drives 54

Symantec NetBackup 53Agent

PATROL 44Alert Acknowledgement 68

Configure 68

Logs 68

Save Groups 68Application Class

NSR_CLIENT 93

NSR_CLIENT_CONTAINER 91

NSR_DAEMON 98

NSR_DAEMON_CONTAINER 96

NSR_DATABASE 104

NSR_DATABASE_CONTAINER 101

NSR_DEVICE 149

NSR_DEVICE_CONTAINER 147

NSR_JCLIENT 132

NSR_JOB 128

NSR_JOB_CONTAINER 124

NSR_LDEVICE 144

NSR_LIBRARY 140

NSR_LIBRARY_CONTAINER 138

NSR_LOG_CONTAINER 106

NSR_MOUNT 136

NSR_MOUNT_CONTAINER 134

NSR_PCLIENT 121

NSR_POLICY 116

NSR_POLICY_CONTAINER 114

NSR_POOL 154

NSR_POOL_CONTAINER 152

NSR_SERVER 83

- B -Baselines

BMC ProactiveNet Performance Management 158

Generation 158

Manage 158

Requirements 158BMC

BMC Portal 51BMC PATROL

Changes 13BMC ProactiveNet

Integration 51BMC ProactiveNet Performance Management

Abnormalities 158

Baselines 158

Key Performance Indicators 158

KPI 158

- C -Changes

BMC PATROL 13

EMC NetWorker 13Check

Instance Limits 46Classes 81

Clients

Delete 58

Disable 58

Enable 58Command

Reload Commands 74Configure

Alert Acknowledgement 68

Failover Mode 56

Group Backup Restriction 67

KM User Account 44

Log Error Filter 65

Log Scan Limit 67

Monitoring Period 60

166

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Configure

Node Type 56

Paths 55

PATROL Agent 42Customize

Date/Time Format 70

Parameters 73

Pending Request Date/Time Format 70

Save Group Date/Time Format 70

- D -Daemons

Delete 58

Disable 58

Enable 58Data Collection

Force 73

Full 73Data Collectors

All 73

Force 73

Selected 73Databases

Delete 58

Disable 58

Enable 58Date/Time Format

Customize 70Debug

Mode 75Debugging

Disable 75

Enable 75Delete

Clients 58

Daemons 58

Databases 58

Group Client 58

Groups 58

Jukeboxes 58

Logs 58

Standalone Devices 58

Volume Pools 58Disable

Clients 58

Daemons 58

Databases 58

Debugging 75

Group Client 58

Groups 58

Jukeboxes 58

Logs 58


Volume Pools 58Discoveries

Force 73Discovery

Verify 46Disk Space

Requirements 19Display

Parameters 73

- E -EMC NetWorker

Changes 13Enable

Clients 58

Daemons 58

Databases 58

Debugging 75

Group Client 58

Groups 58

Jukeboxes 58

Logs 58


Volume Pools 58

- F -Failover Mode

Configure 56Files 20

ins_ALL_<version>.tar 20

ins_WINDOWS_<version>.exe 20

Setup 20

setup.exe 24

setup.sh 24

uninstall.exe 35

uninstall.sh 35Force

Data Collectors 73

Discoveries 73

167

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

- G -Generate

Baselines 158

Reports 79Group Backup Restriction

Configure 67Group Client

Delete 58

Disable 58

Enable 58Groups

Delete 58

Disable 58

Enable 58

- H -help 164

- I -InfoBox

Aliases 93

Application 93

Application Name 83

Application Version 83

Architecture 93

Archive Only 154

Autostart 116

Available FS Space 109

Binary Path 83

Browse Policy 121

Cleaning Required 144, 149

Client Name 132

Client Retries 116

Clients 154

Clients Details 128

Clone Pool 116

Clone Storage Nodes 121

Clones 116

Collector Last End 91, 93, 96, 98, 101, 104,106, 109, 114, 116, 121, 124, 128, 132, 134,136, 138, 140, 144, 147, 149, 152, 154

Collector Last Start 93, 96, 98, 101, 104,106, 109, 114, 116, 121, 124, 128, 132, 134,136, 138, 140, 144, 147, 149, 152, 154

Collector Name 91, 93, 96, 98, 101, 104,106, 109, 114, 116, 121, 124, 128, 132, 134,136, 138, 140, 144, 147, 149, 152, 154

Collector Next Start 91, 93, 96, 98, 101,104, 106, 109, 114, 116, 121, 124, 128, 132,134, 136, 138, 140, 144, 147, 149, 152, 154

Collector Status 91, 93, 96, 98, 101, 104,106, 109, 114, 116, 121, 124, 128, 132, 134,136, 138, 140, 144, 147, 149, 152, 154

Command 98

Completion Status 128

Control Port 140

Copyright 83

CPU Type 93

CPUs 93

Date Last Cleaned 144, 149

Description 93, 98, 104, 109, 116, 121,136, 140, 144, 149, 154

Devices 154

Directive 121

Duration 128

Enabled 140, 144, 149, 154

Enabler in Use 93

End 128, 132

Event Message 140

Failed Save Sets 128

Files 128

FS Percent Used 109

Group Name 128, 132

Group Names 121

Groups 154

Host Name 83

Installation Path 83

Interval 116

IP Address 93

Jukebox Name 144

Last Backup 101

Last Backup Duration 128

Last Backup End 116, 121, 128

Last Backup Files 128

Last Backup Mode 101

Last Backup Save Group 116, 121, 128

Last Backup Save Set ID 101

Last Backup Size 128

Last Backup Start 116, 121, 128

Last Backup Status 116, 121

Last Backup Volume 101

Last Full Backup End 116, 121

Last Full Backup Save Group 116, 121

168

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

InfoBox

Last Full Backup Start 116, 121

Last Incr Backup End 116, 121

Last Incr Backup Save Group 116, 121

Last Incr Backup Start 116, 121

Last Operation 140

Last Operation Message 140

Last Purge 109

Level 128

Levels 154

Library Path 83

Log File Modification Time 109

Log File Size 109

Message 144, 149

Mode 136

Model 140

Monitoring Mode 83

Monitoring Node 83

Name 93, 96, 98, 101, 104, 109, 116, 121,140, 144, 149, 154

Next Backup 116

Node Name(s) 83

Node Type 83

Number of Devices 140

Number of Media 136

ONC Program Number 93

ONC Transport 93

ONC Version Number 93

Operating System 83, 93

Operation 144, 149

Owner 98

Parallelism 116, 121

Path 104, 109, 144, 149

PATROL Agent Version 83

Pending Save Sets 128

Percent Completed 128

PID 98

Platform 83, 93

PPID 98

Printer 116

Priority 121, 136

Product Name 83

Product Release Date 83

Product Version 83

Purpose 136

Read Only 144, 149

Request 136

Request Time 136

Retention Policy 121

Save Group 128

Save Sets 154

Schedule 121

Server 154

Server(s) 83

Servers 93

Size 128

Start 128, 132

Start Time 116

Status 93, 98, 116, 128, 132, 140, 144,149

Storage Node 136, 140, 144, 149

Storage Node(s) 83

Storage Nodes 121

Succeeded Save Sets 128

Suggestion 136

Support 83

Time Remaining 128

Total FS Space 109

Type 128, 144, 149, 154

Version 93

Volume 136

Volume Name 144, 149

Volume Pool 136

Volume Type 136, 154

Web Site 83Install / Un-install 23, 35

BMC Software Installation Utility 20

Log 24

Packages 20

Procedure 24

Setup Files 20Installation Path

Unix 15

Windows 15Instance Limits

Check 46Instrumentation (WMI) Core

Requirements 13Integration

BMC ProactiveNet 51Introduction 23

- J -Jukeboxes

Delete 58

Disable 58

169

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Jukeboxes

Enable 58

- K -Key Performance Indicators


Manage 158KM

Configure 44

Initial Setup 48

Load 40, 41, 51

Preload 42

Preloaded 42, 43

Unload 42, 43

User Account 44KM command

Debug 75

Force Full Collection 73

Refresh Process Cache 73KM Debug

Troubleshooting 161KPI


Manage 158

- L -Load

KM 40, 41, 51

PATROL Central 41Log Alerts

Acknowledge 78Log Error Filter

Configure 65Log Scan Limit

Configure 67Logs

Delete 58

Disable 58

Enable 58

- M -Manage

Baselines 158

Key Performance Indicators 158

KPI 158Master Server

Configure 56Media Server

Configure 56Menu Commands

About 83

Acknowledgement 109, 124, 128

Administration 83, 144, 149

Alarms 109, 124

Alert 128

All 109, 124

Client 93

Client Status 93

Clients 91

Clients Status 91

Configuration 83, 91, 93, 96, 98, 104, 106,109, 114, 121, 124, 134, 138, 147, 154

Daemon 98

Daemon List 96

Daemon Status 98

Daemons 96

Daemons Status 96

Database 104

Database Backup Information 101

Databases 101

Debug 83

Disable Device 144, 149

Enable Device 144, 149

Force Discovery 83

Force Full Collection 124

Group Client 121

Groups 114

Groups Backup Restriction 114

Groups Status 114

Instance Limits 83

Jukebox 140

Jukebox Auto Media Mgmt Status 140

Jukebox Contents 140

Jukebox Device 144

Jukebox Device Status 144

Jukebox Devices 140

Jukebox Devices Status 138, 140

Jukebox Status 140

Jukeboxes 138

Jukeboxes Auto Media Mgmt Status 138

Jukeboxes Status 138

KM Status 83

170

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Menu Commands

Log 109

Log Alert Acknowledgement 109

Log Filter 109

Log Scan Limit 109

Login 83

Logs 106

Logs Alert Acknowledgement 106

Logs Filter 106

Logs Scan Limit 106

Messages List 106

Monitoring Mode 83

Mount Tape 149

Node Status 83

Node Type 83

Paths 83

Pending Request Date/Time Format 134

Pending Requests 134

Pending Requests Status 134

Preloading 83

Refresh Parameters 83

Refresh Process Cache 83

Reload Commands 83

Reports 96, 101, 106, 134, 140, 154

Save Groups 124

Save Groups Alert Acknowledgement 124

Save Groups Date/Time Format 124

Save Groups Status 124

SaveSet Error Event Contents 124

Standalone Device 149

Standalone Device Status 149


Standalone Devices Status 147

Start Server/Storage Node 83

Stop Server/Storage Node 83

Unmount Tape 149

Volume List 154

Volume Pool 154

Warnings 109, 124Monitoring

Save Clients 62Monitoring Period

Configure 60

Pending Requests 60

Save Groups 60MS Windows Management

Requirements 13MS Windows Scripting Host

Requirements 13

- N -Node Type

Configure 56

Master Server 56

Media Server 56NSR_CLIENT

Application Class 93NSR_CLIENT_CONTAINER

Application Class 91NSR_DAEMON

Application Class 98NSR_DAEMON_CONTAINER

Application Class 96NSR_DATABASE

Application Class 104NSR_DATABASE_CONTAINER

Application Class 101NSR_DEVICE

Application Class 149NSR_DEVICE_CONTAINER

Application Class 147NSR_JCLIENT

Application Class 132NSR_JOB

Application Class 128NSR_JOB_CONTAINER

Application Class 124NSR_LDEVICE

Application Class 144NSR_LIBRARY

Application Class 140NSR_LIBRARY_CONTAINER

Application Class 138NSR_LOAD

Troubleshooting 161NSR_LOG_CONTAINER

Application Class 106NSR_MOUNT

Application Class 136NSR_MOUNT_CONTAINER

Application Class 134NSR_PCLIENT

Application Class 121NSR_POLICY

Application Class 116NSR_POLICY_CONTAINER

171

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

NSR_POLICY_CONTAINER

Application Class 114NSR_POOL

Application Class 154NSR_POOL_CONTAINER

Application Class 152NSR_SERVER

Application Class 83NSR_SETUP

Troubleshooting 161NSRLoginStatus

Troubleshooting 161

- O -Operating System

Access 15

AIX 15

HP-UX 15

Solaris 15Operating Systems

Linux 20, 24, 35

Unix 20, 35

Windows 20, 24, 35Options

Common services 24

Console Systems role 24

Managed System 24

View Log 24

- P -Parameter

NSRLoginStatus 44Parameters 81

Customize 73

Display 73

ExtraFilesList 83

NSRAdministratorChange 83

NSRClientCollector 83

NSRClientDetails 91

NSRClientIndexRecordCount 93

NSRClientIndexSpaceUsed 93

NSRClientIndexSpaceUsedPercent 93

NSRClientState 93

NSRClientStatus 93

NSRClientSummary 93

NSRCreateDistribution 83

NSRDaemonCollector 83

NSRDaemonCPUDuration 98

NSRDaemonCPUUtilization 98

NSRDaemonDetails 96

NSRDaemonMemorySize 98

NSRDaemonProcessCount 98

NSRDaemonState 98

NSRDaemonStatus 98

NSRDaemonSummary 98

NSRDatabaseBackupElapsed 101

NSRDatabaseCollector 83

NSRDatabaseDetails 101

NSRDatabaseFSSpaceUsedPercent 104

NSRDatabaseRetention 101

NSRDatabaseSpaceAvailable 104

NSRDatabaseSpaceGrowthRate 104

NSRDatabaseSpaceUsed 104

NSRDatabaseSpaceUsedPercent 104

NSRDatabaseSummary 104

NSRDeviceCollector 83

NSRDeviceDetails 147

NSRDeviceSessionCount 149

NSRDeviceSessionMax 149

NSRDeviceSessionTarget 149

NSRDeviceState 149

NSRDeviceStatus 149

NSRDeviceSummary 149

NSRDeviceThroughput 149

NSRGClientBackupSummary 121

NSRGClientBackupThroughput 121

NSRGClientFullBackupDuration 121

NSRGClientFullBackupFileCount 121

NSRGClientFullBackupSize 121

NSRGClientIncrBackupDuration 121

NSRGClientIncrBackupFileCount 121

NSRGClientIncrBackupSize 121

NSRGClientSummary 121

NSRGroupBackupElapsed 116

NSRGroupBackupSummary 116

NSRGroupBackupThroughput 116

NSRGroupCollector 83

NSRGroupDetails 114

NSRGroupFullBackupDuration 116

NSRGroupFullBackupElapsed 116

NSRGroupFullBackupFileCount 116

NSRGroupFullBackupSize 116

NSRGroupIncrBackupDuration 116

NSRGroupIncrBackupElapsed 116

NSRGroupIncrBackupFileCount 116

172

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Parameters 81

NSRGroupIncrBackupSize 116

NSRGroupState 116

NSRGroupStatus 116

NSRGroupSuccBackupElapsed 116

NSRGroupSummary 116

NSRJDeviceState 144

NSRJDeviceStatus 144

NSRJDeviceSummary 144

NSRJDeviceThroughput 144

NSRJukeboxAutoMediaMgmtState 140

NSRJukeboxAutoMediaMgmtStatus 140

NSRJukeboxCleaningLeftCount 140

NSRJukeboxCollector 83

NSRJukeboxDetails 138

NSRJukeboxState 140

NSRJukeboxStatus 140

NSRJukeboxSummary 140

NSRJukeboxThroughput 140

NSRJukeboxUpDriveCount 140

NSRJukeboxVolumeAssignedCount 140

NSRJukeboxVolumeCount 140

NSRJukeboxVolumeEmptyCount 140

NSRJukeboxVolumeEmptyPercent 140

NSRLogAlarmCount 109

NSRLogAlarmText 109

NSRLogCollector 83

NSRLogDetails 106

NSRLogFSSpaceUsedPercent 109

NSRLoginStatus 83

NSRLogRendered 109

NSRLogSpaceAvailable 109

NSRLogSpaceGrowthRate 109

NSRLogSpaceUsed 109

NSRLogSpaceUsedPercent 109

NSRLogSummary 109

NSRLogText 109

NSRLogWarningCount 109

NSRLogWarningText 109

NSRMonitoringMode 83

NSRMonitorRAP 83

NSRNodeStatus 83

NSRPoolCollector 83

NSRPoolDetails 152

NSRPoolSpaceAvailable 154

NSRPoolSpaceGrowthRate 154

NSRPoolSpaceUsed 154

NSRPoolSpaceUsedPercent 154

NSRPoolSummary 154

NSRRequestCollector 83

NSRRequestDetails 134

NSRRequestElapsed 136

NSRRequestState 136

NSRRequestStatus 136

NSRRequestSummary 136

NSRSaveClientState 132

NSRSaveClientStatus 132

NSRSaveClientText 132

NSRSaveGrpActiveBackupCount 124

NSRSaveGrpActiveCount 124

NSRSaveGrpActiveNonBackupCount 124

NSRSaveGrpCollector 83

NSRSaveGrpDetails 124

NSRSaveGrpDuration 128

NSRSaveGrpFileCount 128

NSRSaveGrpManualSaves 124

NSRSaveGrpSize 128

NSRSaveGrpState 128

NSRSaveGrpStatus 128

NSRSaveGrpSummary 128

NSRSaveGrpText 128

NSRSaveGrpThroughput 128

NSRSaveSetCount 128

NSRSaveSetFailedCount 128

NSRSaveSetIncludeList 121

NSRSaveSetList 128

NSRSaveSetPendingCount 128

NSRSaveSetSucceededCount 128

NSRServerSummary 83

NSRUpdateAgent 83

NSRVolumeActiveCount 154

NSRVolumeActivePercent 154

NSRVolumeAvailableCount 154

NSRVolumeAvailablePercent 154

NSRVolumeCount 154

NSRVolumeEmptyCount 154

NSRVolumeFullCount 154

NSRVolumeFullPercent 154

NSRVolumeManualRecycleCount 154

NSRVolumeReadOnlyCount 154

Refresh 73Paths

Binary 55

Configure 55

Debug Directory 55

Home Directory 55

Library 55

Netbackup Installation 55

173

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Paths

NetBackup Log Directory 55

Temp Directory 55PATROL

Agent 44

PATROL Agent 13, 42

PATROL Agent system 19

PATROL Central Console 42, 43

PATROL Central Console Server system 19

PATROL Central Web Server system 19

PATROL Console 13, 42, 43

PATROL Console system 19PATROL Agent

Configure 42

Restart 48PATROL Console 41

Restart 48Pending Request Date/Time Format

Customize 70Pending Requests

Administer 53

Configure 60

Monitoring Period 60Permissions

Access 15Platform

Upgrade 74Platforms

Unix 44Poor performance

Troubleshooting 161Portal 13

Preload

KM 42Preloaded

KM 42, 43

- R -Refresh

Parameters 73Release Notes 9

Reports

Daemon List 79

Database Backup Information 79

Generate 79

Jukebox Contents 79

Messages List 79

Pending Requests 79

Volumes List 79Requirements

Disk Space 19

Instrumentation (WMI) Core 13

MS Windows Management 13

MS Windows Scripting Host 13

Security 15

Software 13

Sudo 13Restart

PATROL Agent 48

PATROL Console 48

- S -Save Clients 124

All 62

Failed 62

Monitoring 62

None 62

Succeeded 62Save Clients Status 124

Save Group Alerts

Acknowledge 78Save Group Date/Time Format

Customize 70Save Groups 73

Configure 60

Monitoring Period 60Security

Requirements 15Server/Storage Node

Start 53

Stop 53Setup

Check 48

Initial 48

KM 48Software

Instrumentation (WMI) Core 13

MS Windows Management 13

MS Windows Scripting Host 13

Requirements 13

Sudo 13Standalone Devices

Delete 58

Disable 58

174

EMC

Net

Wor

ker

KM

fo

r P

ATR

OL

Ver

sion

2.8

.02

Standalone Devices

Enable 58Standalone Drives

Administer 54Start

Server/Storage Node 53Stop

Server/Storage Node 53Sudo 44

Requirements 13

User 15Symantec NetBackup

Administer 53

- T -Troubleshooting

KM Debug 161

NSR_LOAD 161

NSR_SETUP 161

NSRLoginStatus 161

Poor performance 161

- U -Unix 44

Installation Path 15Unload

KM 42, 43Upgrade

Platform 74

- V -Verify

Application Discovery 46Volume Pools

Delete 58

Disable 58

Enable 58

- W -Windows

Installation Path 15

Registry 15

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

emc networker km for patrol 2.8 - sentry software · emc networker km for patrol storage monitoring...

Documents