emc networker km for patrol 2.8 - sentry software · bmc proactivenet performance management...

User Documentation January 2013

EMC NetWorker KM forPATROLVersion 2.8.00

Contacting BMC SoftwareYou 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 Outside United States and Canada

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

Telephone (01) 713 918 8800

Telephone 713 918 8800 or 800 841 2031

Fax (01) 713 918 8000

Fax 713 918 8000

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

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

IBM is a registered trademark of International Business Machines Corporation.

DB2 is a registered trademark of International Business Machines Corporation.

Oracle is a registered trademark, and the Oracle product names are registered trademarks ortrademarks of Oracle Corporation.

All other trademarks belong to their respective companies.

BMC Software considers information included in this documentation to be proprietary and confidential.Your use of this information is subject to the terms and conditions of the applicable End User LicenseAgreement for the product and the proprietary and restricted rights notices included in thisdocumentation.

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 forth inFAR 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 this

2

Version 2.8.00

EMC NetWorker KM for PATROL

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. To expedite your inquiry, please see "BeforeContacting BMC Software."

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

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 center forassistance. To find telephone and email contact information for the BMC Software support center thatservices your location, refer to the Contact Customer Support section of the Support page on the BMCSoftware Web site at http://www.bmc.com/support_home.

Before Contacting BMC Software

Before you contact BMC Software, have the following information available so that Customer Supportcan begin working on your problem immediately:

· Product information

· product name

· product version (release number)

· license number and password (trial or permanent)

· Operating system and environment information machine type operating system type, version, andservice pack or other maintenance level such as:

§ PUT or PTF

§ system hardware configuration

§ serial numbers

§ related software (database, application, and communication) including type, version, andservice

§ pack or maintenance

§ level

· Sequence of events leading to the problem

· Commands and options that you used

· Messages received (and the time and date that you received them)

§ product error messages

3

Version 2.8.00


Table of Contents 4

Version 2.8.00


Table of Contents...........................................................................................................................9Release Notes for v2.8.00

...........................................................................................................................11Overview

...........................................................................................................................11Preparing for Installation

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

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

..................................................................................................................12Software Requirements

..................................................................................................................14Security Requirements

..................................................................................................................17Disk Space Requirements

...........................................................................................................................18Getting the BMC Software Installation Utility

...........................................................................................................................18Packages

...........................................................................................................................18Extracting the Setup Files

...........................................................................................................................19Installing the KM

...........................................................................................................................19Installing EMC NetWorker KM for PATROL

...........................................................................................................................31Uninstalling EMC NetWorker KM for PATROL

...........................................................................................................................37Loading/Unloading the KM

..................................................................................................................37Loading the KM

..............................................................................................................38Preparing to Load the KM

..............................................................................................................38Loading the KM on PATROL Console

..............................................................................................................38Loading the KM on PATROL Central

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

..................................................................................................................39Unloading the KM

..............................................................................................................39Unloading the KM from the PATROL Agent

..............................................................................................................39Unloading the KM from the PATROL Console

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

...........................................................................................................................41Performing Post-Installation Operations

..................................................................................................................41Configuring the KM User Account

..................................................................................................................43Verifying Application Discovery

..................................................................................................................43Checking the Instance Limits

..................................................................................................................45Checking the Initial Setup of the KM

..................................................................................................................45Restarting PATROL Agent and PATROL Console

...........................................................................................................................46Integrating the KM

...........................................................................................................................46Integrating with BMC Portal

Table of Contents 5

Version 2.8.00


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

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

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

..................................................................................................................47Importing and Customizing Thresholds

..................................................................................................................48Managing Baselines and Key Performance Indicators

...........................................................................................................................50Monitoring your environment

...........................................................................................................................50Administering EMC Networker

..................................................................................................................50Starting Server/Storage Node

..................................................................................................................50Stopping Server/Storage Node

..................................................................................................................50Administering Pending Requests

..................................................................................................................51Administering Standalone Drives

..................................................................................................................51Administering Jukebox Devices

...........................................................................................................................51Configuring the KM

..................................................................................................................51Configuring Paths

..................................................................................................................52Specifying the Node Type

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

..................................................................................................................53Filtering Elements to Monitor

..................................................................................................................55Configuring Monitoring Periods

..................................................................................................................57Configuring the Save Clients Monitoring

..................................................................................................................58Configuring the Node Status

..................................................................................................................59Configuring the Elements Status

..................................................................................................................60Configuring the Log Filter

..................................................................................................................62Configuring the Log Scan Limit

..................................................................................................................62Configuring Group Backup Restriction

..................................................................................................................63Configuring Alert Acknowledgement

..................................................................................................................65Configuring Date/Time Formats

..................................................................................................................68Enabling the Debug Mode

...........................................................................................................................71Using the KM

..................................................................................................................71Acknowledging Alerts

..................................................................................................................72Generating Reports

..................................................................................................................72Reloading Commands

..................................................................................................................72Refreshing Parameters

...........................................................................................................................73Reference Guide

...........................................................................................................................74Classes and Parameters

..................................................................................................................75NSR_SERVER

..................................................................................................................80NSR_CLIENT_CONTAINER

Table of Contents 6

Version 2.8.00


..................................................................................................................81NSR_CLIENT

..................................................................................................................83NSR_DAEMON_CONTAINER

..................................................................................................................85NSR_DAEMON

..................................................................................................................87NSR_DATABASE_CONTAINER

..................................................................................................................89NSR_DATABASE

..................................................................................................................91NSR_LOG_CONTAINER

..................................................................................................................93NSR_LOG

..................................................................................................................97NSR_POLICY_CONTAINER

..................................................................................................................98NSR_POLICY

..................................................................................................................102NSR_PCLIENT

..................................................................................................................104NSR_JOB_CONTAINER

..................................................................................................................106NSR_JOB

..................................................................................................................109NSR_JCLIENT

..................................................................................................................110NSR_MOUNT_CONTAINER

..................................................................................................................111NSR_MOUNT

..................................................................................................................113NSR_LIBRARY_CONTAINER

..................................................................................................................114NSR_LIBRARY

..................................................................................................................117NSR_LDEVICE

..................................................................................................................120NSR_DEVICE_CONTAINER

..................................................................................................................121NSR_DEVICE

..................................................................................................................123NSR_POOL_CONTAINER

..................................................................................................................124NSR_POOL

...........................................................................................................................127Additional Information and Support

...........................................................................................................................127Troubleshooting

...........................................................................................................................129Where to Find Additional Help

EMC Networker KM for PATROL v.2.8.00

9Release Notes for v2.8.00

Version 2.8.00


Release Notes for v2.8.00

What's New

· Fully compatible with BMC ProactiveNet Central Monitoring Administration, a feature supported byBMC ProactiveNet Performance Management version 9.0.00.

· Now supports Microsoft Cluster.

· Save groups monitoring: Save groups can now be monitored at the client level if EMCNetWorker v.7.6 or higher is used. By default, only the failed save clients are monitored but thissetting can be modified through the new KM command Save clients.

· In order to easily identify which step the initial discovery is processing, the setup icon now reflectsthe successive phases:

§ Upgrading: this information is only available for PATROL Classic Console.

§ Loading: indicates that commands are being loaded.

§ Initializing: indicates that KM paths are being initialized.

§ Discovering: indicates that the monitored application is being monitored.

§ Cleaning: indicates that the temp files are being cleaned.

§ Validating: indicates the application paths are being checked.

· The NSRDatabaseRetention parameter was added to the NSR_DATABASE_CONTAINERapplication class to indicate the number of days data will be retained by the database.

· New parameters were added to the NSR_LDEVICE application class:

§ NSRJDeviceSessionCount: displays the number of sessions configured for the jukeboxdevice.

§ NSRJDeviceSessionMax: Displays the number of maximum sessions configured for thejukebox device.

§ NSRJDeviceSessionTarget: displays the number of target sessions configured for thejukebox device.

· New parameters were added to the NSR_DEVICE application class:

§ NSRDeviceSessionCount: displays the number of sessions configured for the device.

§ NSRDeviceSessionMax: displays the maximum number of sessions configured for thedevice.

§ NSRDeviceSessionTarget: displays the number of target sessions configured for the device.

10Release Notes for v2.8.00

Version 2.8.00


· The new state 2=Service Mode was added to the NSRJukeboxState parameter. When thisstate is reached, a warning is triggered on the NSRJukeboxStatus parameter.

Changes and Improvements· All collectors are now automatically refreshed as soon as the KM configuration and the initial

discovery are complete.

· The default number of instances of Application Classes has been removed. This information canbe defined by the user through the Instance Limits menu if required.

· Logs:The default log scan limit was increased to 500 KBytes.

· When one or more required paths are missing, the setup instance label will now indicate whichpaths are missing. A message will also be displayed in the System Output Window.

· Client and policy monitoring is now enabled by default with an instance limit set to 50.

· The NSRRemoveTempFiles parameter was removed since the temporary files are now createdand removed by default by the agent user.

· The NSRSaveSetErrorFound parameter and the associated KM Command Save Set ErrorEvent Contents were removed.

· All previous pconfig variables available under /NSR are now split to /NSR and /Runtime/NSRwhile upgrading the KM.

· Debug Mode:

§ The time during which the debug information is logged can now be set by the user.

§ The KM-related messages that are sent to the System Output Window (SOW) are also loggedto the NSR.log file available under <PATROL_HOME>/log.

· The polling interval for the server discovery has been reduced from 5 minutes to 40 seconds tosooner detectserver-level changes and failures.

· The KM failover time has been reduced to sooner detect node issues.

· The NSRDatabaseBackupElapsed parameter was moved from the NSR_DATABASEapplication class to the NSR_DATABASE_CONTAINER application class to avoid duplicate events.

· The infobox elements Last Backup Save Set ID, Last Backup Mode, and Last Backup weremoved to the NSR_DATABASE_CONTAINER application class.

· The mminfo query used for the bootstrap record was modified to improve the KM performance.

Fixed Issues· With some Windows platforms the Debug KM Command was prompting for an OS login to turn

the debug on.

· The NSRDaemonState parameter was set to "Not Running" when the PATROL Agent could notfork processes, which resulted in invalid alarms on the NSRDaemonStatus parameter.

· The NSRSaveGrpText parameter was not properly set on Windows and did not include theclient success details.

11Overview

Version 2.8.00


Overview

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 PATROL Console.Alarms and warnings inform you when a suspicious behavior is detected; thus allowing you to quicklyand clearly identify peaks, troughs and trends in the performance of your backup resources.

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

Preparing for Installation

This chapter provides information about the tasks that must be performed before you start installingEMC NetWorker KM for PATROL. Make sure to carefully read the following sections requirements:

· Review the requirements

· Get the BMC Software Installation Utility

· Download the Installation Packages

· Extract the Setup Files

RequirementsPrior to install EMC NetWorker KM for PATROL, make sure that the following elements are installedand properly configured:

· PATROL Agent, version 3.4.11 or higher (see BMC PATROL documentation)

· PATROL Console (see BMC PATROL documentation)

System RequirementsOperating System Operating System Version

Oracle SolarisTM 8, 9, 10

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

12Preparing for Installation

Version 2.8.00


IBM® AIXTM 5.1, 5.2, 5.3, 6.1

Red Hat® Linux® 7.2

Microsoft® Windows® 2003, 2008, 2008 R2

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

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

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

BMC 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

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

Changes to EMC NetWorker

It is recommended to set-up a save group log file on all managed systems on Unix platforms. Thisfile can 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 loggingComment: Required notification for NSR KMAction: cat >> /nsr/logs/savegrp.logEvent: SavegroupPriority: Info, Warning, Critical, Emergency,Notice, Waiting, Alert

4. Click Apply.

The NSR KM will process the contents of EMC NetWorker messages file (/nsr/logs/messages) in the absence of abovesave group log file (/nsr/logs/savegrp.log).

The above save group log file set-up is not required on Windows managed nodes because it is one of the standard EMCNetWorker log files.

The NSR KM will not maintain or recycle this save group log file. It is recommended to recycle the save group log fileregularly.


Version 2.8.00


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 allEMC NetWorker 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 still beinsufficient. In such situations, error messages will appear on the PATROL Console System Output Window (SOW)reporting that some NSR KM data collectors are in an infinite loop. In this case you can set the tuning variable to zeroto disable this functionality.

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 be able to readand write to these pconfig variables at anytime. If Access Control List (ACL) is used to control whichusers are authorized to connect to a PATROL Agent, please ensure that the mode for PATROL Agentuser includes “C” in the PATROL Agent variable /AgentSetup/accessControlList. Please refer thePATROL Agent Reference Manual for more details.

You cannot copy or distribute these KM configuration variables between managed nodes, because they may not havethe same value for each managed node. For example, the KM user login details may not be the same for all managednodes. Also some of these variables, like installation paths, are set automatically during the initial discovery.

Additional Software Requirements

Purpose Software Version

When running NSR KM with sudo user account onSolaris, HP-UX, AIX or Linux managed nodes

Sudo (superuser do) 1.6.7 or later

When running NSR KM on Linux managed nodes Korn shell binary (/bin/ksh) Any

When running NSR KM on Microsoft Windows x64managed 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.


Version 2.8.00


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 file systems.Login details of this user are configured in the NSR KM during the KM configuration. The password isstored 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:

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

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

3. a non-root (Unix) or non-administrator (Microsoft Windows) account, such as patrol, configuredin 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 the pathslisted 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 execute permissionsto the following cluster commands:


Version 2.8.00


· /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 Agent userand 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-"," ="); 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 paths andfiles:

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/lic/logs/lgtomd.log INSTALL_PATH\logs\savegrp.log

/var/adm/messages (on Solaris)

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


Version 2.8.00


To access files under above paths the relevant user needs “read & execute” permission to all parent directories.

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 WindowsRegistry. 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. Thisuser 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 with thefollowing sudo configuration in the sudoers file. Please replace user1, user2, user3 with appropriateKM user name. The EMC NetWorker installation path INSTALL_PATH, referenced below is normally /nsr or /opt/networker and PATROL_HOME is the path where the PATROL Agent is installed(including the target, like /opt/bmc/Patrol3/Solaris29-sun4/).

On Solaris:

User_Alias NSRKMUSERS = user1, user2, user3Defaults:NSRKMUSERS !lecture,!authenticate,\env_keep+="LD_LIBRARY_PATH INSTALL_PATH KM_HOME \KM_TEMP",env_resetNSRKMUSERS 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_HOME with therelevant paths.

On HP-UX:

User_Alias NSRKMUSERS = user1, user2, user3Defaults:NSRKMUSERS !lecture,!authenticate,\env_keep+="SHLIB_PATH INSTALL_PATH KM_HOME \KM_TEMP",env_resetNSRKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\/usr/sbin/nsr/*,/etc/LGTOuscsi/*\INSTALL_PATH/bin/*,\PATROL_HOME/lib/NSR/*,PATROL_HOME/bin/*


Version 2.8.00



On AIX:

User_Alias NSRKMUSERS = user1, user2, user3Defaults:NSRKMUSERS !lecture,!authenticate,\env_keep+="LIBPATH INSTALL_PATH KM_HOME \KM_TEMP",env_resetNSRKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\/usr/sbin/nsr/*,/etc/LGTOuscsi/*\INSTALL_PATH/bin/*,\PATROL_HOME/lib/NSR/*,PATROL_HOME/bin/*


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 devices willgenerate more history data (as per other KMs used by the PATROL Agent). These history data filesare 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. Requiredspace under this file system depends on the complexity of the EMC NetWorker environment. If theavailable space for this folder is less than 10 MBytes, it can be changed to a different file system,which has sufficient disk space. This can be achieved by replacing the temporary folder, KM_HOME/tmp, with a soft link pointing to a different file system, like /tmp. This new temporary folder should


Version 2.8.00


have read, write and execute permissions for both PATROL Agent user and the NSR KM login user.

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

Choose the appropriate package depending on the platform you plan to install EMC NetWorker KMfor 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.

Downloading from Sentry Software Web site

· For Windows systems: nsr_WINDOWS_2600.exe

· For UNIX and Linux systems: senemc_UNIX_2600.tar

The EMC NetWorker KM for PATROL packages are designed for use with the BMC Software Installation

Utility (formerly known as Thorium). They need to be merged with the latest available version of theBMC Software Installation Utility. Please see instructions.

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

· Every managed system with a PATROL Agent

· Every PATROL Console (Classic) that will show EMC NetWorker performance-related informationand alerts

· The Console Server

· PATROL Central – Web Edition

19Installing the KM

Version 2.8.00


Installing the KM

Introduction

This section describes the installation procedure for EMC NetWorker KM for PATROL on any PATROLcomponent (Agents, Consoles, Console Server, etc.). As the setup is based on the BMC SoftwareInstallation Utility, this procedure applies to all operating systems supported by EMC NetWorker KMfor PATROL.

Installing EMC NetWorker KM for PATROLInstalling EMC NetWorker KM for PATROL is an automated process managed by a wizard. The wizardgoes through the necessary steps to install EMC NetWorker KM for PATROL and all files associatedwith it. You are simply prompt for the product's folder location and the product/components toinstall.

Browse to the bmc_products folder where the files have been extracted (both EMC NetWorker KM forPATROL and the Common Installer).

20Installing the KM

Version 2.8.00


· On Windows: Launch the setup.exe program

· On UNIX: Launch the setup.sh script

To install EMC NetWorker KM for PATROL1. Allow the perl.exe program to listen on this port: Click Allow access.

Installation W izard - Step 1: W indow s Security Alert

21Installing the KM

Version 2.8.00


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

Installation W izard - Step 2: W elcome

22Installing the KM

Version 2.8.00


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

Installation W izard - Step 3: Review ing License Agreement

23Installing the KM

Version 2.8.00


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

Installation W izard - Step 4: Selecting Installation Options

24Installing the KM

Version 2.8.00


5. Specify the BMC Software products folder. See the BMC Software documentation for moreinformation about the BMC Software products folder. Click Next to continue.

Installation W izard - Step 5: Selecting the Installation Directory

25Installing the KM

Version 2.8.00


6. Select Default. Installing EMC NetWorker KM for PATROL does not require any customization.Click Next to continue.

Installation W izard - Step 6: Selecting an Installation Type

7. Select one or several of the following options:

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

§ Console Systems role to install EMC NetWorker KM for PATROL on a PATROL ClassicConsole.

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

Click Next to continue.

26Installing the KM

Version 2.8.00


Installation W izard - Step 7: Selecting Roles

Select as many options as required.

27Installing the KM

Version 2.8.00


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

Installation W izard - Step 8: Selecting Products and Components

28Installing the KM

Version 2.8.00


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

Installation W izard - Step 9: Review ing Installation Options

29Installing the KM

Version 2.8.00


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

Installation W izard - Step 10: Installation Status

30Installing the KM

Version 2.8.00


11. The wizard displays the installation results.Click View Log to display a detailed log of the installation procedure. Click Next and thenFinish to exit the setup program.

Installation W izard - Step 11: Installation Results

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

31Installing the KM

Version 2.8.00


Installation W izard - Step 12: Completing and closing the Installation W izard

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

Uninstalling EMC NetWorker KM for PATROLUninstalling 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

32Installing the KM

Version 2.8.00


Un-install W izard — W elcome Step

33Installing the KM

Version 2.8.00


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

Un-install W izard — Specifying folder

34Installing the KM

Version 2.8.00


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

Un-install W izard — Selecting Products and Components Directory

35Installing the KM

Version 2.8.00


4. Click Start Uninstall to run the un-installation program.

Un-install W izard — Review ing Selected Products & components and start uninstalling

36Installing the KM

Version 2.8.00


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

Un-install W izard — Status

37Installing the KM

Version 2.8.00


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

Un-installation W izard — 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 KM

This section provides instructions to load EMC NetWorker KM for PATROL on Microsoft Windows andUnix platforms.

Before you load the NSR KM, you must install the KM on PATROL Console and PATROL Agentsystems.

38Installing the KM

Version 2.8.00


Preparing to Load the KM

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

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

Loading the KM on PATROL Console

1. From the PATROL Console menu bar, choose File>Load KM...

2. Select the NSR_LOAD.kml file, and click Open or OK. The NSR KM will be loaded to thePATROL Console, and all connected PATROL Agents will start discovering the EMC NetWorkerenvironment. If the automatic discovery successfully finds the EMC NetWorker server/storagenode installation, NSR_SETUP instance will be instantiated,

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

4. Select File>Save Configuration to save the new list of loaded KM files as the PATROL Consoleuser preference.

5. Repeat the above steps on each PATROL Console.

Loading the KM on PATROL Central

1. Right click on the PATROL Main Map, and choose Load Knowledge Modules... A wizard boxwill display a list of all managed systems.

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.

If you cannot find the NSR_LOAD.kml file in the wizard list for any system you selected, then the KM has not beeninstalled on that system.

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 automatic discoverysuccessfully finds the EMC Networker installation, the NSR_SETUP instance will be instantiated.

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

5. Repeat the above steps for each PATROL Central Management Profile where NSR KM is to beunloaded.

39Installing the KM

Version 2.8.00


Configuring PATROL Agent to Preload the KM

To configure PATROL Agent to preload the KM:

1. In order to enable EMC NetWorker KM for PATROL to operate all the time, without a PATROLConsole connection, the KM should be added to the PATROL Agent configuration variable /AgentSetup/preloadedKMs. This can be achieved on the EMC NetWorker instance by usingthe menu Configuration>Preloading.

2. Select Add to add the KM files to the list of preloaded KMs. If the NSR KM is successfully addedto the list, an acknowledgement will be displayed.

The same menu is used to remove the NSR KM files from the preloaded KMs list.

Unloading the KMThis section describes the procedures for unloading (not uninstalling) the NSR KM from the PATROLAgent, PATROL Console or PATROL Central Console. The intention is that this section is only used ifyou no longer want to use some parts of the KM, though there may be circumstances where you maywish to fully unload the KM without uninstalling the files.

When the NSR KM is unloaded from a PATROL Agent, PATROL stops monitoring the EMC NetWorkerapplication on that system when there is no connection to a PATROL Console with NSR KM loaded.

When the NSR KM is unloaded from PATROL Console, the PATROL Console stops displaying andmonitoring the EMC NetWorker application on any PATROL Console connected system.

Unloading the KM from the PATROL Agent

To unload the KM from the PATROL Agent:

1. Remove the NSR KM from the list of preloaded KMs using the menu Configuration>Preloading from the EMC NetWorker instance. Alternatively, using theutility wpconfig (on Microsoft Windows) or xpconfig (on Unix), remove NSR_LOAD.kml fromthe PATROL Agent configuration variable /AgentSetup/preloadedKMs.

2. Restart the PATROL Agent.

3. Repeat these steps on every PATROL Agent system (managed node) where the NSR KM is to beunloaded.

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

Unloading the KM from the PATROL Console

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

To unload the NSR KM completely or partially:

40Installing the KM

Version 2.8.00


1. Remove the unwanted NSR KM application classes from the list of loaded application classes, asrequired. 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 Console

A KM can be unloaded from particular managed systems or for all systems across the monitoredenvironment. Application classes may be unloaded individually, or by selecting all classes at once.This allows for a partial unloading of the KM to enable it to run as a reduced installation on some orall 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>.

A list is displayed showing all the loaded application classes on each of the selected managedsystems. All NetWorker KM application classes start with “NSR_”.

3. Select the NetWorker KM application classes to be removed for the appropriate managedsystems, click Next> and Finish.

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

41Installing the KM

Version 2.8.00


Performing Post-Installation OperationsIt 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 operating systemsused, 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 to administerthe 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.

42Installing the KM

Version 2.8.00


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.

43Installing the KM

Version 2.8.00


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

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 for PATROL. Tooffer better performance, it is possible to limit the number of instances that will be displayed in theConsole 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.

44Installing the KM

Version 2.8.00


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.

45Installing the KM

Version 2.8.00


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 in theformat NSR<Object>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. Check throughthe report for any warnings or alarms. If any errors are found during any of the above steps(including any incorrect data in Infoboxes or any warnings or alarms in the KM Status report),determine the cause(s) and take steps to resolve these errors. You may need to refer to the User Guide, or contact Technical Support, attaching the KM Status report.

§ 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 duplicate alerts.You can disable these components on either server or storage node by setting their instance limitto 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 to confirmthat the NSR KM operates correctly after restarting the PATROL Agent and/or PATROL Console.

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

46Installing the KM

Version 2.8.00


Integrating the KM

Introduction

This section provides detailed information about the integration of EMC NetWorker KM for PATROLwith BMC ProactiveNet Performance Management.

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

2. Click on Configure tab.

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

4. Click Add.

5. Select Infrastructure Element, and click Next.

6. Select appropriate RSM, and click Next.

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

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

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

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

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

OverviewTo integrate a BMC PATROL KM into BMC ProactiveNet Performance Management 8.5.x or 8.6.x, youneed to create a specific adapter. An adapter for BMC PATROL facilitates pulling of performance datafrom existing BMC PATROL solutions into BMC ProactiveNet. Using an Adapter, you can import BMCPATROL application classes (provided in a Knowledge Module –KM) into BMC ProactiveNet. TheAdapter periodically synchronizes the performance data collected by these application classes intoBMC ProactiveNet.

Creating and Importing an Adapter for a BMC PATROL KM

Creating an Adapter for a BMC PATROL KM1. Open the BMC ProactiveNet Administration Console. The BMC ProactiveNet Administration

Console is displayed as shown in the following figure:

2. Right-click the Adapters folder and select Import Monitor Type and Add Adapter > BMCPATROL.

3. In the Configuration tab, enter the required information:

· In the Instance Name field, enter a name for this instance of the Adapter that will performthe integration of the ‘targeted KM’ into BMC ProactiveNet.

· Select the Agent where this instance of the Adapter will be executed

47Integrating the KM

Version 2.8.00


· Enter the Integration Service Agent hostname or IP address

· Enter the Integration Service Agent Port. The default port is 3182.

· Enter the required credential to connect to the Integration Service Agent

4. Click Next to continue

5. Click Next to let the system load the BMC PATROL application classes.

6. Select the application classes to import

Unselecting will delete the application classes that have already been imported during a previousoperation. Application classes ready to be deleted are marked with a red x.

7. Click Next to start the import process. The system displays a summary of the application classimport, click Next to continue.

8. Select the application classes you wish to auto-synchronize with the Integration Service Agent.

9. Click Next to continue

10. Set the Filter details if need.

11. Click Next to continue.

12. Set the Auto-sync poll scheduling, if needed.

13. Click Next to continue. The system displays a summary of your settings, click Finish to confirm.The Adapter has been added to the Adapters folder of the Administration Console.

14. To see the class instances that have been imported by the Adapter, expand the Adapters folder,right-click the Adapter and select Details.

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

Updating an Adapter for a BMC PATROL KM

Updating an Adapter1. Delete the Adapter instance

2. Go through the Add an Adapter wizard to actually delete the monitor types that had beencreated based on the previous version of the KM

3. Close

4. Resume the entire Creating an Adapter for a BMC PATROL KM procedure

For complete and detailed information on these procedures, please refer to the BMC ProactiveNet documentationavailable from BMC Web site.

Importing and Customizing Thresholds1. Launch the BMC ProactiveNet PW Commands. On Windows 2008, you need to run the PW

Commands as Administrator.

2. Execute the following command line:pw adapter -type patrol -get_thresholds <file name> -pproxy_host <hostname|ipaddress> -pproxy_port <port_number>] [-pproxy_user <username>] [-pproxy_passwd <password>] -i -v

where-get_thresholds <file name> = File name with absolute path at which thresholds

will be imported-pproxy_host <hostname|ipaddress> = Host name or IP Address of Patrol Proxy Server

-pproxy_port <port_number> = Port at which Patrol Proxy Agent communicates with Patrol


Version 2.8.00


Proxy Server -pproxy_user <username> = User name of Patrol Proxy user -pproxy_passwd <password> = Password to authenticate Patrol Proxy user -i = import Instance level thresholds -v = run in "verbose" mode, producing extra lines of output during extraction and conversion processes

The command has produced a text file with all the parameter threshold settings.

3. Open the file in a text editor. Check that the global thresholds have been properly interpreted.

4. Then go to the # INSTANCE LEVEL THRESHOLDS section of the file.

5. Uncomment all instance level thresholds for the _PATROL__NSR_ prefixed instances.

Search the file for the 'NOT_IMPLEMENTED' occurrences to detect thresholds that were not properlyconverted by the PATROL Adapter.

6. Save the file.

7. Execute the following command:pw threshold loadpatrolthreshold [<thresholdfilename> [-v]]where: <thresholdfilename> is a thresholds file name. If no file path is specified then the default '<Installation Directory>/pw/tmp/' is used -v enables the Verbose mode

Class-level thresholds can be displayed using the Absolute Global Thresholds panel in the BMCProactiveNet Operator Console, while instance-level thresholds are displayed in the AbsoluteInstance Thresholds panel.

Managing Baselines and Key Performance IndicatorsIn order to facilitate the detection of abnormalities on your monitored environment, BMCProactiveNet calculates baselines per parameter (metrics or attributes) based on values collectedover a specified period of time to determine a normal operating range. When the collected values forthese parameters are out of range, an alert is triggered.

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

Managing baselines

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

The baseline is calculated by collecting the values for a monitor’s attributes and metrics over aspecified time period and establishing a low baseline value (consisting of the 10th percentile of all thevalues for a given time period) and a high baseline value (consisting of the 90th percentile of all thevalues for a given time period), taking a weighted average of these values over time. A higher weightis given to the latest data being factored into the baseline average. The accuracy of the baselineimproves over time.


Version 2.8.00


Requirements for baseline generation

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

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

Managing Key Performance Indicators

The KPI attribute of a parameter can be activated or deactivated manually through the BMCProactiveNet Administration Console. In this KM, some parameters or attributes have beendesignated as important indicators of performance (KPIs). We do not recommend that these defaultsettings are modified.

However, advanced users may activate or deactivate KPIs from the BMC ProactiveNet AdministrationConsole.

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

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

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

3. In the KPI column for the attributes that you want to add or remove as Key PerformanceIndicators:

· select the KPI check box to add the corresponding attribute as a KPI

· deselect the KPI check box to remove the corresponding attribute from the KPIs for thatmonitor type

For complete and detailed information on this procedure, please refer to the BMC ProactiveNet documentation availablefrom BMC Web site.

Parameters for which the system by default calculates baselines as well as parameters considered asKPIs are respectively identified by the following icons:

· Baselining

· KPI

50Monitoring your environment

Version 2.8.00


Monitoring your environment

EMC NetWorker KM for PATROL helps ensure the availability, maximum performance, and integrity ofyour backup servers, thereby protecting associated data sets.

Administering EMC NetworkerEMC NetWorker KM for PATROL provides secure server administration menus, which can be executedby PATROL Console users, if they have appropriate privileges. They can more especially:

· 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, and mounted. Toperform this mount operation, right-click the pending request instance and select KM commands >Administration > Mount Tape.


Version 2.8.00


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

· 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, where mounting orunmounting tapes on devices are automatic.

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 information canhowever 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


Version 2.8.00


§ 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 fields, click OK, and restart the PATROL Agent.

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

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

2. Select the node type

3. Click OK.

Configuring the Multi-Node Monitoring ModeIf the NSR KM environment is installed in a cluster using Veritas Cluster Server, Veritas Cluster FileSystem, Oracle Solaris Cluster, or Microsoft Cluster, the NSR KM must be installed on all the clusternodes to enable continuous monitoring and avoid single point of failure. To avoid duplicate alertsfrom multiple nodes, it is recommended to configure the solution to operate in multi-node monitoringmode.

To configure the multi-node monitoring mode:

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

Configuring the Multi-Node Monitoring Mode


Version 2.8.00


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 vxconfigd inenable 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 on offlinenode will monitor in passive mode, until NetWorker is failed over. In the passive mode the KM willmonitor 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 will change toTemporary Single-node Mode.

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 irrelevant forvarious 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 that youwish to monitor:

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

§ Daemons > KM Commands > Configuration > Daemons to filter daemons to bemonitored

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

§ Logs > KM Commands > Configuration>Logs to filter logs to be monitored. Only thedaily messages 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. Youcan however disable this direct relationship between monitored groups configuration andmonitored save groups instances by running the following PSL through PATROL Console: %PSLpconfig("REPLACE","/NSR/FilterJobByPolicy", false);

§ Group Client > KM Commands > Configuration > Group Client to filter group clients tobe monitored

§ 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 poolsto be monitored


Version 2.8.00


These menus are also available from the child instances.

Client Configuration dialog

The [ALL] entry ensures that all the elements found during PATROL discovery are instantiated andmonitored. When installed on a Storage Node, the default configuration monitors only the discoveredlocal jukeboxes and local standalone devices. This is covered by the [LOCAL] entry in the defaultconfiguration 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 filter will have to be configured if you enable log files for monitoring.


Version 2.8.00


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 leaving parametersnot set.

4. To delete elements for monitoring:

§ In the current configuration list, select the elements to delete

§ Select Delete

§ Click Update

5. To add a new element to monitor:

§ Type the name of the element to be monitored

§ If needed, enter a description

§ From the Status list, select Enable

§ Click Update.

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

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

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 can howevermodify these settings to better suit your requirements:

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


Version 2.8.00


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


Version 2.8.00


3. Click OK.

By default, all active save groups are exempted from ageing, i.e. save groups which are in one of the active states (InProgress, 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

· All: to monitor all the save clients.

3. Click OK.


Version 2.8.00


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 and severalrecovery actions will be initiated. If any command run by EMC NetWorker KM for PATROL returns aserver/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


Version 2.8.00


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

3. In the Daemon field, enter the daemons to be added to the node status filter. Multiple daemonsmay 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 new daemon for thelist and click Update.

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

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

Client Status Configuration dialog


Version 2.8.00


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 an alarmwhen the Never Communicated state of the Clients instance lasts more than 240 minutes:

§ 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 filter, select [default] from the list of states and click Update.

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

Configuring the Log FilterA log error filter can be configured to specify the regular expressions that will generate a warning oran 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 for monitoring,you will have to customize the log filter by adding appropriate expressions for those log files.

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

To configure the log error filter:


Version 2.8.00


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

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 standard wildcardsyntax, such as “warning . otlsol01”.

§ Select Exclude


Version 2.8.00


6. Click Update.

To revert to the default settings for either filter, type [default] as a new error expression for that filter, and clickUpdate. If you revert to the default settings when accessed from the log instance level, the settings will revert to theparent or container instance level. To revert to the shipped default settings (as shown above), access this dialog fromthe log container instance. From this level you will also have the option to reset the configuration of any modified childinstances.

Configuring the Log Scan LimitThe NSR KM scans log files by reading the new log entries since the last data collection cycle. Bydefault, only 500 Kbytes of data is scanned for each log file during each data collection cycle. This logscan 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)Scan Limit

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 toapply this customization to all group backups

§ a Group instance > KM Commands > Configuration> Group Backup Restriction toapply this customization to a specific group


Version 2.8.00


Group Backup Restriction W indow 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 settings toallow 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.


Version 2.8.00


Configuring Log Alert Acknowledgement

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

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

Configuring Log Alert Acknow ledgement

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

3. Click Ok.


Version 2.8.00


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 >Job Alert Acknowledgement

Configuring Job Alert Acknow ledgement

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 and timeof each save group and of each pending request (used for calculating the elapsed time since thesave group and the pending request were initiated). Depending on your local system time zone anddate/time format, the application may return a different date/time format. If so, you'll have tocustomize the save group and pending request date/time format.


Version 2.8.00


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 field and/or the Time Zone field and click OK. The Time zonefield used will be the local time zone on the managed node.


Version 2.8.00


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 field and/or the Time Zone field and click OK. The Time zonefield used will be the local time zone on the managed node.


Version 2.8.00


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

Enabling the Debug Mode

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

Enabling the Debug Mode


Version 2.8.00


2. Select On for the debug switch(es) you want to enable. The table below shows the applicationclasses 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_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 NSR KMlogin 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 tothe PATROL Agent.

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

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/zip file isthen automatically created under <PATROL_HOME>/lib/NSR/ and can be sent to the BMC Supportfor help. It is also recommended to check the SOW or NSR.log file, stored in <PATROL_HOME>/log,


Version 2.8.00


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 foundin %PATROL_HOME%\lib\NSR\

· Click No if you do not want to compress the files. You will then be asked if you want to retain ordelete them.

If the compressed file is not created successfully, you can create it manually by including all files and sub-directoriesunder $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.


Version 2.8.00


Using the KMThis section describes all the features available for EMC NetWorker KM for PATROL.

Acknowledging AlertsBy default, alerts are acknowledged automatically. They can however be acknowledged manually ifyou do not want to wait for the automatic cycle. Manual acknowledgement will also be required ifyou 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 text parameters 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 can beacknowledged using the KM command Acknowledgement > Alert from the relevant save groupinstance.

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.


Version 2.8.00


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 theprevious index 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 inthe selected 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 a text file.

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.

Refreshing ParametersThis section describes how to manually refresh parameters of the EMC NetWorker KM for PATROL,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 KM containerinstance.

These steps will also force discovery on application classes for any other KM loaded on the PATROL Agent as well as allapplication 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 Refresh Parametersfrom the main NSR KM container instance.

These steps will refresh all other data collectors defined under the various application classes loaded on the PATROLAgent as well as refreshing the NSR KM data collectors.


Version 2.8.00


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.

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 monitored timeperiod during the next collection cycle. Use the KM command Force Full Collection from the savegroups container instance (labeled Save Groups).

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

Reference Guide

Introduction

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 and itsdefault settings.

74Reference Guide

Version 2.8.00


Classes and ParametersThis section lists the application classes of NSR KM. It gives you details on the icons that representthe class, Infobox, parameters and the menu commands available for each application class. Thereare 13 main application classes and 10 “container” classes.

· 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_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 and KPIs,please refer to the Managing Baselines and Key Performance Indicators chapter.

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

· Baselining

· KPI

75Reference Guide

Version 2.8.00


NSR_SERVER

Icon

Parameters

Name Description Units Default AlertConditions

BPPMType

ExtraFilesList Is used for pushing NSR KM libraryfiles to the PATROL Agent during the"Commit" operation.

n/a n/a n/a

NSRAdministratorChange Monitors any change in NetWorkeradministrator configuration 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 application classes.By default, this collector is executedonly on the server.

Polling Interval: 600 seconds

n/a n/a n/a

NSRCreateDistribution Is automatically activated at the endof NSR KM debugging if thecustomer chooses to "prepare debugfiles for sending to Sentry Software".It is deactivated on completion.


n/a n/a n/a

NSRDaemonCollector Collects EMC NetWorker daemonrelated information. It sets allconsumer parameters inNSR_DAEMON_CONTAINER andNSR_DAEMON application classes.


n/a n/a n/a

NSRDatabaseCollector Collects EMC NetWorker indexdatabase related information. It setsall consumer parameters inNSR_DATABASE_CONTAINER andNSR_DATABASE application classes.By default, this collector is executedonly on the server.


n/a n/a n/a

76Reference Guide

Version 2.8.00


NSRDeviceCollector Collects EMC NetWorker standalonedevice related information. It sets allconsumer parameters inNSR_DEVICE_CONTAINER andNSR_DEVICE application classes.


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 is executedonly on the server.


n/a n/a n/a

NSRJukeboxCollector Collects EMC NetWorker jukebox andjukebox device related information.It sets all consumer parameters inNSR_LIBRARY_CONTAINER,NSR_LIBRARY, and NSR_LDEVICEapplication classes.


n/a n/a n/a

NSRLogCollector Collects information about the EMCNetWorker log file. It sets allconsumer parameters inNSR_LOG_CONTAINER andNSR_LOG application classes.


n/a n/a n/a

NSRLoginStatus* Monitors the status of the NSR KMlogin details (username/password)for the operating system. It is set byNSR_SERVER application classdiscovery.If no valid username/password isdetected for the operating system,this parameter will be set to Failurestate. If there are any suspiciouscommand exits, this parameter willbe set to Suspicious state.

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

0 = Ok1 = Suspicious2 = Failure

Warning= 1Alarm =2

CollectionStatus

NSRMonitoringMode* Monitors failover mode of EMCNetWorker KM for PATROL. It is setby NSR_SERVER application classdiscovery.

By default EMC NetWorker KM forPATROL runs in Permanent Single-node Mode. Multi-node monitoringcan be configured using the KMcommand 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

77Reference Guide

Version 2.8.00


NSRMonitorRAP Collects the status of the NetWorkerRAP (Resource Allocation Protocol)monitor configuration. It is set byNSR_SERVER application classdiscovery.

0 = Enabled1 = Disabled-1 = Unknown

None Availability

NSRNodeStatus* Monitors error messages for the EMCNetWorker application on thismanaged system. It is set byNSR_SERVER application classdiscovery.If any of the EMC NetWorkerapplication daemons is not running,this parameter will be set to Failurestate. The list of critical EMCNetWorker daemons can becustomized using the KM command Configuration > Node Statusfrom the EMC NetWorker icon. Ifthere are any suspicious commandexits due to an error from theserver/storage node, this parameterwill be set to Suspicious state.



Warning= 1Alarm =2

Availability

NSRPoolCollector Collects information about the EMCNetWorker volume pools. It sets allconsumer parameters inNSR_POOL_CONTAINER andNSR_POOL application classes. Bydefault, this collector is executedonly on the server.


n/a n/a n/a

NSRRequestCollector Collects information about the EMCNetWorker pending requests. It setsall consumer parameters inNSR_MOUNT_CONTAINER andNSR_MOUNT application classes.By default, this collector is executedonly on the server.


n/a n/a n/a

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

n/a n/a n/a

NSRServerSummary Set by NSR_SERVER Discovery,summarizes the server informationas reported in commands executedby the discovery.

n/a n/a n/a

78Reference Guide

Version 2.8.00


NSRUpdateAgent Is used by the NSR KM to set thePATROL Agent KM variables whenthe PATROL Console user is notauthorized to update (ACL) anyPATROL Agent variables. It isactivated automatically when the KMfails to update the PATROL Agent. 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 in BPPM.

InfoBox

Name Description

Product Name Name of the Knowledge Module.

Product Version Version number of the Knowledge Module.

Product Release Date Release date of the Knowledge Module.

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 EMC NetWorker.

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

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.

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

79Reference Guide

Version 2.8.00


Function Description

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

Force Discovery Forces application discovery.

Refresh Parameters Forces an update of the application parameter values.

Reload Commands Forces a reload of commands used by NSR KM during the next full discoverycycle. By default, all new commands are reloaded automatically.

Administration > Start Server/StorageNode

Starts server/storage node daemons.

Administration > Stop Server/StorageNode

Stops server/storage node daemons.

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

Configuration > Preloading Accesses Preloading Configuration dialog, which adds or removes the KM fromPATROL Agent variable /AgentSetup/preloadedKMs.By preloading the NSR KM, the PATROL Agent will monitor the EMC NetWorkerapplication 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 EMC NetWorkerenvironment.

Configuration > Paths Accesses the Path Configuration dialog, which displays and sets all paths usedby NSR KM.Paths are automatically discovered by the NSR KM server discovery. They areused as environment variables for executing various EMC NetWorker applicationcommands. Altering these paths may impact the 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 EMC NetWorkerAdministrator’s Guide.

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

Configuration > Node Status Accesses the Node Status Configuration dialog for viewing and modifying thedaemon names monitored for node status.

80Reference Guide

Version 2.8.00


The NSR KM checks for the existence of these daemons to determine the status ofthe node (parameter NSRNodeStatus). By default, the following daemons aresought:

Type [default] to reset to the default configuration.

Configuration > Instance Limits Accesses the Instance Limits Configuration dialog to view and modify themaximum number of NSR KM application instances allowed for each applicationclass.

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

KM Status Generates a summary report containing information on the managed system.

About Displays information about the product and manufacturer.

NSR_CLIENT_CONTAINER

Icon

Parameters


BPPMType

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

n/a n/a n/a

81Reference Guide

Version 2.8.00


InfoBox

Name Description

Collector Name Name of the data collector that sets variables and parameters under thisapplication instance.

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

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

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

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

Menu Commands


Configuration > Clients Accesses the dialog for specifying which clients are to be monitored by the NSRKM.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 for monitoredclient instances.By default, following NSRClientState to NSRClientStatus mapping rule isused:

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

NSR_CLIENT

Icon

Parameters

Name Description Units DefaultAlertConditions

BPPMType

82Reference Guide

Version 2.8.00


NSRClientIndexRecordCount* Set by NSRClientCollector.Displays the number of records foundin the index database for this client.

count None Statistics

NSRClientIndexSpaceUsed Set by NSRClientCollector.Displays the index space used bythis client.

KB None Statistics

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

% None Statistics

NSRClientState Set by NSRClientCollector.Displays the state of the client asreported in the command executedby the data collector.

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

None Availability

NSRClientStatus Set by NSRClientCollector.Monitors the status of the client. Thisstatus is determined by the clientstatus mapping rule defined in theKM command Configuration >Client(s) Status.



Warning= 1Alarm =2

Availability

NSRClientSummary Set by NSRClientCollector.Summarizes the client information asreported in commands executed bythe data collector.

n/a n/a n/a

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


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 for the client.

Status Status of client connectivity from the current node.

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

83Reference Guide

Version 2.8.00


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.






Menu Commands


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

Configuration >Client Status Accesses the individual configuration for determining client status for the selectedclient instance.By default, the global NSRClientState to NSRClientStatus mapping rule isused, as configured at the container level. Select [default] to revert to the clientstatus mapping rule configured at the global/container level.

NSR_DAEMON_CONTAINER

Icon

Parameters


BPPMType

84Reference Guide

Version 2.8.00


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

n/a n/a n/a

InfoBox

Name Description






Menu Commands


Reports > Daemon List Lists all running EMC NetWorker daemons.

Configuration > Daemons Accesses the dialog for specifying which daemons are to be monitored by the NSRKM.By default following daemons are monitored.


Configuration > Daemons Status Accesses the global configuration for determining the daemon status formonitored daemon instances.By default following NSRDaemonState to NSRDaemonStatus mapping rule isused:

85Reference Guide

Version 2.8.00


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

NSR_DAEMON

Icon

Parameters


BPPMType

NSRDaemonCPUDuration Set by NSRDaemonCollector.Displays the CPU seconds consumedby the daemon.

seconds None Statistics

NSRDaemonCPUUtilization* Set by NSRDaemonCollector.Displays the percentage of CPU usedby the daemon.

% None Statistics

NSRDaemonMemorySize* Set by NSRDaemonCollector.Displays the core image size of thedaemon in the virtual memory.

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 the daemon asreported in the command executedby the data collector.

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

None Availability

86Reference Guide

Version 2.8.00


NSRDaemonStatus Set by NSRDaemonCollector.Monitors the status of the daemon.This status is determined by thedaemon status mapping rule definedin the KM command Configuration> Daemon(s) Status.



Warning= 1Alarm =2

Availability

NSRDaemonSummary Set by NSRDaemonCollector.Summarizes the daemon informationas reported by commands executedby the data collector.

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.






Menu Commands


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

Configuration > Daemon Status Accesses the individual configuration for determining daemon status for theselected the daemon instance.

87Reference Guide

Version 2.8.00


By default, the global NSRDaemonState to NSRDaemonStatus mapping ruleis used, as configured at the container level. Select [default] to revert to thedaemon status mapping rule configured at the global/container level.

NSR_DATABASE_CONTAINER

Icon

Parameters


BPPMType

NSRDatabaseBackupElapsed* Set by NSRDatabaseCollector.Displays the elapsed time since thelast successful database backup.

The specified alarm ranges can beenabled to allow the output of theparameter to be actively monitored.Then, if this parameter changes towarning or alarm state, the recoveryaction will trigger an event.

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

NSRDatabaseRetention Set by NSRDatabaseCollector.Displays the number of days data willbe retained by the database.

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.



88Reference Guide

Version 2.8.00





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 be monitored by the NSRKM.By default, the following database paths are monitored. These database paths are relative tothe EMC NetWorker installation directory (for example /NSR on Unix and C:\Program Files\NSR on MS Windows).


89Reference Guide

Version 2.8.00


NSR_DATABASE

Icon

Parameters


BPPMType

NSRDatabaseFSSpaceUsedPercent*

Set by NSRDatabaseCollector.Monitors the percentage of spaceused by the file system where thedatabase resides.If this parameter changes to warningor alarm state, the recovery actionwill trigger an event.

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

Statistics

NSRDatabaseSpaceAvailable Set by NSRDatabaseCollector.Monitors the amount of assignedspace remaining available for use bythe index database.If this parameter changes to warningor alarm state, the recovery actionwill trigger an event.

MB Warning:2-5Alarm ≤2

Availability

NSRDatabaseSpaceGrowthRate Set by NSRDatabaseCollector.Displays the growth rate of the spaceused by the index database.

MB/s None Statistics

NSRDatabaseSpaceUsed Set by NSRDatabaseCollector.Displays the amount of assignedspace used by the index database.

MB None Statistics

NSRDatabaseSpaceUsedPercent* Set by NSRDatabaseCollector.Monitors the percentage of assignedspace used by the index database.If this parameter changes to warningor alarm state, the recovery actionwill trigger an event.Note that the total assigned space isthe used space(NSRDatabaseSpaceUsed) plus theavailable space(NSRDatabaseSpaceAvailable).

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

Statistics

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

n/a None n/a


90Reference Guide

Version 2.8.00



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 selected index databaseinstance.This dialog allows the selected database instance to be enabled or disabled formonitoring by the NSR KM.

91Reference Guide

Version 2.8.00


NSR_LOG_CONTAINER

Icon

Parameters


BPPMType

NSRLogDetails Set by NSRLogCollector. Displaysall data returned to the standard outfrom commands executed by thedata collector.

n/a n/a n/a

InfoBox

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 by the NSR KM.By default, the following log files are monitored. These log file paths are relative to theEMC NetWorker installation directory (for example /nsr on Unix and C:\Program Files\nsron MS Windows), unless the path is fully qualified as for the system log on Solaris andHP-UX.

92Reference Guide

Version 2.8.00



Configuration > Logs Filter Accesses the global configuration of the filter for expressions used for detecting errormessages in the monitored log file instances.By default, the following Included expressions are looked for in each log file. Ifdetected, the message containing the expression is added to the appropriate textparameter, unless the message also contains an Excluded expression for the samefilter.


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

Configuration > Logs AlertAcknowledgement

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

93Reference Guide

Version 2.8.00


NSR_LOG

Icon

Parameters


BPPMType

NSRLogAlarmCount* Set by NSRLogCollector. Monitorsthe number of alarm messages setin the parameter NSRLogAlarmText.

If this parameter changes to alarmstate, the recovery action will triggeran event.

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

Statistics

NSRLogAlarmText Set by NSRLogCollector. Displaysall alarm messages in the log filewhich have not been acknowledged.The filter used by the data collectorto determine alarm messages can becustomized using the KM commandConfiguration > Log(s) Filter.

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

n/a None n/a

NSRLogFSSpaceUsedPercent* Set by NSRLogCollector. Monitorsthe percentage of space used by thefile system (where the log fileresides).

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

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

Statistics

NSRLogRendered This parameter, set by NSRLogCollector, monitorswhether raw log files are rendered inruntime.

0 = Yes1 = No-1 = Unknown

Warning ifout of [0-1] rangeWarning= 1

Availability

94Reference Guide

Version 2.8.00


This parameter is onlyavailable for NetWorker rawlog files.

NSRLogSpaceAvailable Set by NSRLogCollector. Monitorsthe available space for the log file touse (this is also the available spaceon the file system).If this parameter changes towarning or alarm state, the recoveryaction will trigger an event.

MB Warning= 2 - 5Alarm ≤ 2

Availability

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

KB/s Warning= 2 to 5Alarm ≤ 2

Statistics

NSRLogSpaceUsed Set by NSRLogCollector. Displaysthe amount of space used by the logfile.

KB/s None Statistics

NSRLogSpaceUsedPercent* Set by NSRLogCollector. Monitorsthe percentage of capacity used bythe log file.If this parameter changes towarning or alarm state, the recoveryaction will trigger an event.Note that the total capacity is theused space (NSRLogSpaceUsed)plus available space(NSRLogSpaceAvailable).

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

Statistics

NSRLogSummary Set by NSRLogCollector.Summarizes the log file informationas reported by commands executedby the data collector.

n/a n/a n/a

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

n/a n/a n/a

NSRLogWarningCount* Set by NSRLogCollector. Monitorsthe number warning messages set inthe parameter NSRLogWarningText.If this parameter changes to awarning state, the recovery actionwill trigger an event.

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

Statistics

NSRLogWarningText Set by NSRLogCollector. Displaysall warning messages in the log filewhich have not been acknowledged.The filter used by the data collectorto determine warning messages canbe customized using the KMcommand Configuration > Log(s)Filter.

n/a n/a n/a

95Reference Guide

Version 2.8.00


These warning messages can beacknowledged automatically(default) or manually, depending onthe configuration in the KMcommand Configuration > Log(s)Alert Acknowledgement. Manualacknowledgement is available underthe KM sub-menu

Acknowledgement.



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.






96Reference Guide

Version 2.8.00


Menu Commands


Acknowledgement > Warnings Allows acknowledgement of warning messages detected on the selected log fileinstance.This dialog allows selective acknowledgement of "suspicious" error messagesdetected in the log file and sent to the text parameter NSRLogWarningText.

Acknowledgement > Alarms Allows acknowledgement of alarm messages detected on the selected log fileinstance.This dialog allows selective acknowledgement of "failure" error messages detectedin the log file and sent to the text parameter NSRLogAlarmText.

Acknowledgement > All Allows acknowledgement of all alarm and warning messages detected on theselected log file instance.This dialog allows acknowledgement of all error messages detected in the log fileand sent to the text parameter NSRLogWarningText or NSRLogAlarmText.

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

Configuration > Log Filter Accesses the individual configuration of the log error filter for the selected log fileinstance.By default, the global log filter is used, as configured at the container level.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 the selected logfile instance.By default, the global log file scanning limit is used, as configured at the containerlevel.

Configuration > Log AlertAcknowledgement

Accesses the individual configuration of the method of acknowledgement for alertson the selected log file instance.By default, the global method of log error acknowledgement is used, as configuredat the container level.

97Reference Guide

Version 2.8.00


NSR_POLICY_CONTAINER

Icon

Parameters


BPPMType

NSRGroupDetails Set by NSRGroupCollector.Displays all data returned to thestandard out from commandsexecuted by the data collector.

n/a n/a n/a

InfoBox

Name Description






Menu Commands


Configuration > Groups Accesses the dialog for specifying which groups are to be monitored by the NSRKM.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 window for allmonitored group instances.By default, backup restriction is disabled.When the backup restriction window is defined and enabled using this dialog, andif the group status mapping rule is configured appropriately, an alert will betriggered if any backup activity is detected during this restriction window.

Configuration > Groups Status Accesses the global configuration for determining the group status for monitoredgroup instances.By default, the following NSRGroupState to NSRGroupStatus mapping rule isused:

98Reference Guide

Version 2.8.00


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

NSR_POLICY

Icon

Parameters


BPPMType

NSRGroupBackupElapsed* Set by NSRGroupCollector.Displays the elapsed time since thelast backup for this group, regardlessof completion status of the backup.This last backup is determined fromthe monitored save groups asconfigured in the KM command Configuration > Save Groupsfrom the Save Groups icon.



NSRGroupBackupSummary Set by NSRGroupCollector.Summarizes the last backup for thisgroup.

n/a None n/a

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

GB/s None Statistics

NSRGroupFullBackupDuration Set by NSRGroupCollector.Displays the duration of the lastsuccessful full backup for this group.


99Reference Guide

Version 2.8.00


NSRGroupFullBackupElapsed* Set by NSRGroupCollector.Displays the elapsed time since thelast successful full backup for thisgroup. This last backup is determinedfrom the monitored save groups asconfigured in the KM command Configuration > Save Groupsfrom the Save Groups icon.



NSRGroupFullBackupFileCount Set by NSRGroupCollector.Displays the number of files backedup in the last successful full backupfor this group.


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

GB None Statistics

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


NSRGroupIncrBackupElapsed* Set by NSRGroupCollector.Displays the elapsed time since thelast successful incremental backup forthis group. This last backup isdetermined from the monitored savegroups as configured in the KMcommand Configuration > SaveGroups from the Save Groups icon.



NSRGroupIncrBackupFileCount Set by NSRGroupCollector.Displays the number of files backedup in the last successful incrementalbackup for this group.


NSRGroupIncrBackupSize Set by NSRGroupCollector.Displays the size of the lastsuccessful incremental backup for thisgroup.

GB None Statistics

NSRGroupState Set by NSRGroupCollector.Displays the state of the group.If a backup restriction window isdefined in the KM command Configuration > Group (Groups)Backup Restriction, this parameterwill be set to Running in RestrictedWindow if there is any activity duringthe specified period.

0 = Idle1 = Running2 = Running inRestricted Window3 = Cloning-1 = Unknown

None Availability

100Reference Guide

Version 2.8.00


NSRGroupStatus Set by NSRGroupCollector.Monitors the status of the group. Thisstatus is determined by the groupstatus mapping rule defined in theKM command Configuration >Group (Groups) Status.If this status parameter changes towarning or alarm state, the recoveryaction will trigger an event andannotate the last data point.


Warning= 1Alarm =2

Availability

NSRGroupSuccBackupElapsed* Set by NSRGroupCollector.Displays the elapsed time since thelast successful backup for this group.This last backup is determined fromthe monitored save groups asconfigured in the KM command Configuration > Save Groupsfrom the Save Groups icon.The specified alarm ranges can beenabled to allow the output of theparameter to be actively monitored.Then, if this parameter changes towarning or alarm state, the recoveryaction will trigger an event.


NSRGroupSummary Set by NSRGroupCollector.Summarizes the group information asreported by commands executed bythe data collector.

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

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

101Reference Guide

Version 2.8.00


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

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 for the group.

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

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 selected group instance.This dialog allows the selected group instance to be enabled or disabled formonitoring by the NSR KM.

Configuration > Groups BackupRestriction

Accesses the individual configuration for the backup restriction window for theselected group instance.By default, the global backup restriction rule is used, as configured at thecontainer level.

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

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

102Reference Guide

Version 2.8.00


NSR_PCLIENT

Icon

Parameters


BPPMType

NSRGClientBackupSummary Set by NSRGroupCollector.Summarizes the last backup for thisgroup client.

n/a n/a n/a

NSRGClientBackupThroughput* Set by NSRGroupCollector.Displays the throughput of the lastbackup for this group client.


NSRGClientFullBackupDuration Set by NSRGroupCollector.Displays the duration of the lastsuccessful full backup for this groupclient.


NSRGClientFullBackupFileCount Set by NSRGroupCollector.Displays the number of files backedup in the last successful full backupfor this group client.


NSRGClientFullBackupSize* Set by NSRGroupCollector.Displays the size of the last successfulfull backup for this group client.

MB None Statistics

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


NSRGClientIncrBackupFileCount Set by NSRGroupCollector.Displays the number of files backedup in the last successful incrementalbackup for this group client.


NSRGClientIncrBackupSize* Set by NSRGroupCollector.Displays the size of the last successfulincremental backup for this groupclient.

MB None Statistics

NSRGClientSummary Set by NSRGroupCollector.Summarizes the group clientinformation as reported by commandsexecuted by the data collector.

n/a n/a n/a

NSRSaveSetIncludeList Set by NSRGroupCollector. Lists allfiles and file systems included forbackup for this group client.

n/a n/a n/a

103Reference Guide

Version 2.8.00




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 group client.

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

Last Incr Backup Start Date & time when the last successful incremental backup started for the groupclient.

Last Incr Backup End Date & time at the completion of the last successful incremental backup for thegroup 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.






104Reference Guide

Version 2.8.00


Menu Commands


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

NSR_JOB_CONTAINER

Icon

Parameters


BPPMType

NSRSaveGrpActiveBackupCount* Set by NSRSaveGrpCollector. Displaysthe number of active jobs currentlydiscovered and monitored.


NSRSaveGrpActiveCount* Set by NSRSaveGrpCollector. Displaysthe number of active jobs currentlydiscovered and monitored.


NSRSaveGrpActiveNonBackupCount*

Set by NSRSaveGrpCollector. Displaysthe number of active jobs currentlydiscovered and monitored.


NSRSaveGrpDetails Set by NSRSaveGrpCollector. Displaysall data returned to the standard outfrom commands executed by the datacollector.

n/a n/a n/a

NSRSaveGrpManualSaves Set by NSRSaveGrpCollector. Displayswhether the manual saves areenabled or disabled.

0 = Enabled1 = Disabled-1 = Unknown

None Availability



105Reference Guide

Version 2.8.00


InfoBox

Name Description






Menu Commands


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

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

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

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

Configuration > Save Groups Accesses the dialog for specifying which save groups are to be monitored by theNSR KM.By default, all scheduled save groups on the server are monitored according tothe following conditions:

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

Configuration > Save Groups Status Accesses the configuration dialog for determining the status for all monitored jobinstances.By default following NSRSaveGrpState to NSRSaveGrpStatus mapping rule isused:

106Reference Guide

Version 2.8.00


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 to acknowledgealerts triggered for NSRSaveGrpStatus. Alerts can either be manually (defaultconfiguration) or automatically acknowledged.

Configuration > Save Groups Date/Time Format

Accesses the configuration of date/time format and time zone for monitored savegroup instances.By default, the format used by EMC NetWorker for the date/time of a pendingrequest is set to DAY MON DD HH:MM:SS YYYY. The date/time is thenconverted by the NSR KM using the system time zone on the PATROL 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 tothe default time zone, blank out the time zone field.

Configuration > Save Clients Sets which save clients will be monitored. The possible values are:· None· Failed Only· Succeeded Only· AllBy default, only the failed save clients are monitored.

Configuration > Save Clients Status Indicates which states will trigger a warning or an alarm on the Statusparameter.

NSR_JOB

Icon

Parameters


BPPMType

NSRSaveGrpDuration Set by NSRSaveGrpCollector.Displays the duration of the savegroup from the start.


NSRSaveGrpFileCount Set by NSRSaveGrpCollector.Displays the number of files backedup for this save group.


107Reference Guide

Version 2.8.00


NSRSaveGrpSize Set by NSRSaveGrpCollector.Displays the amount of data backedup for the save group.

MB None Statistics

NSRSaveGrpState Set by NSRSaveGrpCollector.Displays the state of the save group.This is determined using the savegroup completion state and numberof pending, succeeded & failed savesets.

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 is determined bythe save group status mapping ruledefined in the KM commandConfiguration > Save GroupsStatus.



Warning= 1Alarm = 2

Availability

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

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 this savegroup.


NSRSaveSetCount Set by NSRSaveGrpCollector.Displays total number of save sets inthis save group.


NSRSaveSetFailedCount Set by NSRSaveGrpCollector.Displays number of failed save setsin 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 pending savesets in this save group.


NSRSaveSetSucceededCount Set by NSRSaveGrpCollector.Displays number of succeeded savesets in this save group.




108Reference Guide

Version 2.8.00


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.

Start Date & time when the save group was initiated. This is interpreted using the SaveGroup Date/Time Format defined in the KM menu command.

End Date & time at the completion of the save group. This is interpreted using theSave Group Date/Time Format defined in the KM menu command.

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 in comparisonwith the last similar successful save group for the same group, group client, andlevel.

Time Remaining Remaining time of the save group in comparison with the last similar successfulsave 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.






109Reference Guide

Version 2.8.00


Menu Commands


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

NSR_JCLIENT

Icon

Parameters


BPPMType

NSRSaveClientState Displays the state of the save client. 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 interpreted using the SaveGroup Date/Time Format defined in the KM menu command.

End Date & time at the completion of the save group. This is interpreted using theSave Group Date/Time Format defined in the KM menu command.

Status Status of the save group.

110Reference Guide

Version 2.8.00







Menu Commands

There are no KM commands for this application class.

NSR_MOUNT_CONTAINER

Icon

Parameters


BPPMType

NSRRequestDetails Set by NSRRequestCollector. Displaysall data returned to the standard outfrom commands executed by thedata collector.

n/a n/a n/a

InfoBox

Name Description






111Reference Guide

Version 2.8.00


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 be monitored bythe NSR KM.By default, all pending requests are monitored for 1 day. The age ofa pending request is calculated from the pending request time. The status of apending request is determined by the state of the pending request (from theparameter NSRRequestState) and the pending request status mapping rule,described below.

Configuration > Pending RequestsStatus

Accesses the configuration for determining the status for all monitored pendingrequest instances.By default, the following NSRRequestState to NSRRequestStatus mappingrule is used:

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

Configuration > Pending RequestsDate/Time Format

Accesses the configuration of the date/time format and time zone for allinstantiated pending requests.By default, the format used by EMC NetWorker for the date/time of a pendingrequest is set to DAY MON DD HH:MM:SS YYYY. The date/time is thenconverted by the NSR KM using the system time zone on the PATROL 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 tothe default time zone, blank out the time zone field.

NSR_MOUNT

Icon

Parameters


BPPMType

NSRRequestElapsed* Set by NSRRequestCollector.Displays the elapsed time since thepending request was issued.

minutes None Statistics

112Reference Guide

Version 2.8.00


NSRRequestState Set by NSRRequestCollector.Displays the state of the pendingrequest as reported in the commandexecuted by the data collector.

0 = Completed1 = Pending-1 = Unknown

None Availability

NSRRequestStatus Set by NSRRequestCollector.Monitors the status of the pendingrequest. This status is determined bythe pending request status mappingrule defined 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



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 interpreted using thePending Request Date/Time Format defined in the KM menu command.

Suggestion Last suggestion issued for the pending request.




113Reference Guide

Version 2.8.00




Menu Commands

There are no KM commands for this application class.

NSR_LIBRARY_CONTAINER

Icon

Parameters


BPPMType

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

n/a n/a n/a

InfoBox

Name Description






Menu Commands


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

114Reference Guide

Version 2.8.00


Configuration > Jukeboxes Status Accesses the global configuration for determining the status for monitored jukeboxinstances.By default, the following NSRJukeboxState to NSRJukeboxStatus mappingrule is used:

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

Configuration > Jukeboxes Auto MediaMgmt Status

Accesses the dialog for determining the status mapping rule.

Configuration > Jukebox DevicesStatus

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

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

NSR_LIBRARY

Icon

Parameters


BPPMType

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

0 = Yes1 = No-1 = Unknown

None Availability

115Reference Guide

Version 2.8.00


NSRJukeboxAutoMediaMgmtStatus Set by NSRJukeboxCollector.Monitors the status of the jukeboxauto media managementconfiguration. This status isdetermined by the status mappingrule defined in the KM command Configuration > Jukebox(Jukeboxes) Auto Media MgmtStatus.



Warning= 1Alarm =2

Availability

NSRJukeboxCleaningLeftCount Set by NSRJukeboxCollector.Displays the number of uses left onthe cleaning tape loaded in thisjukebox.

count Warning= - 1

Statistics

NSRJukeboxState Set by NSRJukeboxCollector.Displays the jukebox state, which isderived from the jukebox resource. Itwill not perform any remote jukeboxtest command on the storage node.

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

None Availability

NSRJukeboxStatus Set by NSRJukeboxCollector.Monitors the status of the jukebox.This status is determined by thejukebox status mapping rule definedin the KM command Configuration> Jukebox (Jukeboxes) Status.



Warning= 1Alarm =2

Availability

NSRJukeboxSummary Set by NSRJukeboxCollector.Summarizes the jukebox informationas reported by commands executedby the data collector.

n/a n/a n/a

NSRJukeboxThroughput* Set by NSRJukeboxCollector.Displays the total throughput of eachjukebox device during the lastbackup save groups.


NSRJukeboxUpDriveCount Set by NSRJukeboxCollector.Displays the number up / online statedrives in this robotic library.

If this parameter changes to warningor alarm state, the recovery actionwill trigger an event.


NSRJukeboxVolumeAssignedCount Set by NSRJukeboxCollector.Displays the number of assignedvolume loaded in this jukebox.(Assigned volumes are registeredtape volumes assigned to a volumepool.)


116Reference Guide

Version 2.8.00


NSRJukeboxVolumeCount Set by NSRJukeboxCollector.Displays the total number of volumesloaded in this jukebox.


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


NSRJukeboxVolumeEmptyPercent*

Set by NSRJukeboxCollector.Monitors the percentage of emptyvolumes against the total number ofvolumes loaded in this jukebox.If this parameter changes to warningor alarm state, the recovery actionwill trigger an event.

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






117Reference Guide

Version 2.8.00


Menu Commands


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

Configuration > Jukebox Accesses the individual configuration for monitoring the selected jukeboxinstance.This dialog allows the selected jukebox instance to be enabled or disabled formonitoring by the NSR KM.

Configuration > Jukebox Status Accesses the individual configuration for determining the status for the selectedjukebox instance.By default, the global NSRJukeboxState to NSRJukeboxStatus mapping ruleis used, as configured at the container level. Select [default] to revert to thejukebox status mapping rule configured at the global/container level.

Configuration > Jukebox Auto MediaMgmt Status

Accesses the dialog for determining the status mapping rule.

Configuration > Jukebox Devices Accesses the dialog for specifying which devices of the selected jukebox are to bemonitored 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 monitored deviceinstances on the selected jukebox instance.By default, the global NSRJDeviceState to NSRJDeviceeStatus mapping ruleis used, as configured at the container level. Select [default] to revert to thedevice status mapping rule configured at the global/container level.

NSR_LDEVICE

Icon

Parameters


BPPMType

NSRJDeviceSessionCount* Set by NSRJukeboxCollector.Displays the number of sessionsconfigured for the jukebox device.

sessions None Statistics

NSRJDeviceSessionMax* Set by NSRJukeboxCollector.Displays the maximum number ofsessions configured for the jukeboxdevice.


118Reference Guide

Version 2.8.00


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


NSRJDeviceState Set by NSRJukeboxCollector.Displays the state of the jukeboxdevice. This is determined from thejukebox device controlinformation.

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

None Availability

NSRJDeviceStatus Set by NSRJukeboxCollector.Monitors the status of the jukeboxdevice. This status is determinedby the jukebox device statusmapping rule defined in the KMcommand Configuration >Jukebox Device(s) Status.

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

0 = Ok1 = Suspicious 2 = Failure

Warning =1Alarm = 2

Availability

NSRJDeviceSummary Set by NSRJukeboxCollector.Summarizes the jukebox deviceinformation as reported bycommands executed by the datacollector.

n/a n/a n/a

NSRJDeviceThroughput* Set by NSRJukeboxCollector.Displays the throughput of thejukebox device during the last savegroup.




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.

119Reference Guide

Version 2.8.00


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.

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 selected jukebox deviceinstance.This dialog allows the selected device instance to be enabled or disabled formonitoring by the NSR KM.

Configuration > Jukebox Device Status Accesses the individual configuration for determining the jukebox device status forthe selected jukebox device instance.By default, the NSRJDeviceState to NSRJDeviceStatus mapping ruleconfigured at the parent level is used. (Note that if the mapping rule has not beenmodified for the parent jukebox, then the default is the global mapping ruleconfigured at the container level.) Select [default] to revert to the jukebox devicestatus mapping rule configured at the parent instance level.

120Reference Guide

Version 2.8.00


NSR_DEVICE_CONTAINER

Icon

Parameters


BPPMType

NSRDeviceDetails Set by NSRDeviceCollector.Displays all data returned to standardout from commands executed by thedata collector.

n/a n/a n/a

InfoBox

Name Description






Menu Commands


Configuration > Standalone Devices Accesses the dialog for specifying which standalone devices are to be monitoredby the NSR KM.By default, all local and remote standalone devices are monitored for a server andall local standalone devices are monitored for a storage node. Type [default] toreset to the default configuration.

Configuration > Standalone DevicesStatus

Accesses the global configuration for determining the status for all monitoredstandalone device instances.By default, the following NSRDeviceState to NSRDeviceStatus mapping ruleis used:

121Reference Guide

Version 2.8.00


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

NSR_DEVICE

Icon

Parameters


BPPMType

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


NSRDeviceSessionMax* Set by NSRDeviceCollector.Displays the maximum number ofsessions configured for the device.


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


NSRDeviceState Set by NSRDeviceCollector.Displays the state of the standalonedevice.

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

None Availability

122Reference Guide

Version 2.8.00


NSRDeviceStatus Set by NSRDeviceCollector.Monitors the status of the standalonedevice. This status is determined bythe standalone device status mappingrule defined in the KM command Configuration > StandaloneDevice(s) Status.



Warning =1Alarm = 2

Availability

NSRDeviceSummary Set by NSRDeviceCollector.Summarizes the standalone deviceinformation as reported bycommands executed by the datacollector.

n/a n/a n/a

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




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.




123Reference Guide

Version 2.8.00




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 > Standalone Device Accesses the individual configuration for monitoring the selected standalonedevice instance.This dialog allows the selected standalone device instance to be enabled ordisabled for monitoring by the NSR KM.

Configuration > Standalone DeviceStatus

Accesses the individual configuration for determining device status for the selectedstandalone device instance.By default, the global NSRDeviceState to NSRDeviceStatus mapping rule isused, as configured at the container level. Select [default] to resume to thestandalone device status mapping rule configured at the global/container level.

NSR_POOL_CONTAINER

Icon

Parameters


BPPMType

NSRPoolDetails Set by NSRPoolCollector. Displaysall data returned to the standard outfrom commands executed by the datacollector.

n/a n/a n/a

InfoBox

Name Description

124Reference Guide

Version 2.8.00







Menu Commands

KM Command Action

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

NSR_POOL

Icon

Parameters


BPPMType

NSRPoolSpaceAvailable* Set by NSRPoolCollector. Monitorsthe available volume space for thebackup data to use in this volumepool.If this parameter changes to warningor alarm state, the recovery actionwill trigger an event.

GB None Availability

NSRPoolSpaceGrowthRate Set by NSRPoolCollector. Displaysthe growth rate of the total volumespace used by the backup data in thisvolume pool.

GB/s None Statistics

NSRPoolSpaceUsed* Set by NSRPoolCollector. Displaysthe total volume space occupied bythe backup data in this volume pool.

GB None Statistics

125Reference Guide

Version 2.8.00


NSRPoolSpaceUsedPercent* Set by NSRPoolCollector. Monitorsthe percentage of total occupiedvolume space against the totalvolume capacity of this volume pool(not including any scratch volume).If this parameter changes to warningor alarm state, the recovery actionwill trigger an event.

% 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

NSRVolumeActiveCount Set by NSRPoolCollector. Displaysthe number of active volumes in thisvolume pool. (Active volumes areavailable tape volumes where datacan be written without anyintervention.)


NSRVolumeActivePercent* Set by NSRPoolCollector. Monitorsthe percentage of active volumesagainst the total number of volumesin this volume pool.If this parameter changes to warningor alarm state, the recovery actionwill trigger an event.


Statistics

NSRVolumeAvailableCount Set by NSRPoolCollector. Displaysthe number of volumes assigned tothis volume pool.


NSRVolumeAvailablePercent* Set by NSRPoolCollector. Monitorsthe percentage of available volumesagainst the total number of volumesin this volume pool.If this parameter changes to warningor alarm state, the recovery actionwill trigger an event.


Statistics

NSRVolumeCount Set by NSRPoolCollector. Displaysthe total number of volumes in thisvolume pool.


NSRVolumeEmptyCount Set by NSRPoolCollector. Displaysthe number of empty volumes in thisvolume pool. (Empty volumes areavailable tape volumes with no datastored on them.)


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


NSRVolumeFullPercent* Set by NSRPoolCollector. Monitorsthe percentage of full volumesagainst the total number of volumesin this volume pool.If this parameter changes to warningor alarm state, the recovery actionwill trigger an event.


Statistics

126Reference Guide

Version 2.8.00


NSRVolumeManualRecycleCount Set by NSRPoolCollector. Displaysthe number of volumes in this volumepool, which require manual recycling.("Manually-recyclable" volume is apossible volume state set on tapevolumes.)


NSRVolumeReadOnlyCount Set by NSRPoolCollector. Displaysthe number of read only volumes inthis volume pool. ("Read Only" is apossible volume 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.






Menu Commands


Reports > Volumes List Reports all volumes in the volume pool.

127Reference Guide

Version 2.8.00


Configuration > Volume Pool Accesses the configuration for monitoring the selected volume pool instance.This dialog allows the selected volume pool instance to be enabled or disabled formonitoring by the NSR KM.

Additional Information and Support

TroubleshootingRefer to the table below to diagnose any problems you may encounter when installing or running theEMC NetWorker KM for PATROL.

For any problem, look for error messages on the PATROL Console System Output Window (SOW). Most error messagesare self-explanatory.

Most KM problems are reported in the KM Status Report, which can be viewed by selecting the KM command KM Statusfrom the Legato NetWorker or NSR_SETUP icon. Run this report to diagnose any problems.

The NSR KM triggers PEM events for most severe problems. Each event triggered from the KM includes an ExpertAdvice, 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 under the PATROLinstallation 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 orstorage node), and it is configured properly.

· Check that the version of EMC NetWorker is supported by EMC NetWorker KM forPATROL.

· Check that there is no KM version mismatch between the PATROL Console and thePATROL Agent. 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 the messages 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 tothe Agent Configuration Database.

Parameter NSRLoginStatus is in suspicious (warning) status

This parameter will also show a “suspicious” state if any command executed by NSR KMfails.

128Additional Information and Support

Version 2.8.00


· Check the annotation point on the first state change data point of this parameter tolook for any failing commands. If an annotation point cannot be found, or if it is notup-to-date, check the KM Status Report, which can be viewed by selecting the KMcommand KM Status from the EMC NetWorker icon. These errors are produced fromthe EMC NetWorker commands 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 NetWorkerfiles.

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 inthe PATROL Console SOW to verify this.

· 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 additionalinformation in the last annotation point for parameter NSRLoginStatus.

Behavior of the NSR KM has not changedin accordance 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 PATROLAgent are 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 theKM. These intervals are defined for a standard environment with minimal resourceimpact. These intervals can be customized from the PATROL Developer Console to suityour environment. Refer to the PATROL Console User Guide 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 byusing the 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 throughPATROL Console:

%PSL pconfig("REPLACE","/NSR/NSRSaveGrpCollectorMode","0|32400|57600|0|0|||||||||||0|0");

Here the pconfig variable is named as: <collector name>Mode. The value containsfollowing 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 days starting fromSunday 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 NSRClientCollectorand NSRGroupCollector may affect the overall performance. In such environmentdisable the NSRClientCollector, or set their instance limits to 0 (zero), using menuConfiguration > Instance Limits.

Old active save groups are not removed from the

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:

129Additional Information and Support

Version 2.8.00


console %PSL pconfig("REPLACE","/NSR/AgeActiveJobs", true);

Infinite Loop Errors(Error messages on the SOW reporting that some NSR KM datacollectors 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 infinite loop. When a PSL functionreaches this maximum threshold, it reports this error, and puts the execution of thisfunction to the back of the process queue. This will not only delay the data collector, itwill also impact the performance of the system.

To resolve this situation, the maximum number of instructions should be increased to anoptimum value. This depends on the complexity of your environment. It is required thatthe default value of 500,000 should be increased to at least 5,000,000 on a standardEMC NetWorker environment to enable the NSR KM data collectors to execute withoutimpacting 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 Debuggingthe KM, you turn the debug on by setting appropriate PATROL Agent configurationvariable with a timestamp value. This timestamp value determines when the debugshould be turned off. For example, to turn on the debug for 60 minutes from now, runthe following PSL through PATROL Console:

%PSL pconfig("REPLACE","/NSR/<Component>Debug",time()+3600);

Where <Component> is either Server for debugging the server discovery or name of thecollector component followed by Collector, like DaemonCollector for debuggingdaemon collector.

Old acknowledged save groups are still 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:

%PSL pconfig("REPLACE","/NSR/NSR_JOB/JobAcknowledgementCapacity",<Number>);

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

Index 130

Version 2.8.00


Index

- A -Abnormalities 48

Access

Operating System 14

Permissions 14Acknowledge

Log Alerts 71

Save Group Alerts 71Acknowledgement

Configure 63

Logs 63

Save Groups 63Adapter 46

Add 46, 47

Create 46

Update 47Administer

Pending Requests 50

Standalone Drives 51

Symantec NetBackup 50Agent

PATROL 41Alert Acknowledgement 63

Configure 63

Logs 63

Save Groups 63Application Class

NSR_CLIENT 81

NSR_CLIENT_CONTAINER 80

NSR_DAEMON 85

NSR_DAEMON_CONTAINER 83

NSR_DATABASE 89

NSR_DATABASE_CONTAINER 87

NSR_DEVICE 121

NSR_DEVICE_CONTAINER 120

NSR_JCLIENT 109

NSR_JOB 106

NSR_JOB_CONTAINER 104

NSR_LDEVICE 117

NSR_LIBRARY 114

NSR_LIBRARY_CONTAINER 113

NSR_LOG_CONTAINER 91

NSR_MOUNT 111

NSR_MOUNT_CONTAINER 110

NSR_PCLIENT 102

NSR_POLICY 98

NSR_POLICY_CONTAINER 97

NSR_POOL 124

NSR_POOL_CONTAINER 123

NSR_SERVER 75

- B -Baselines

BMC ProactiveNet Performance Management 48

Generation 48

Manage 48

Requirements 48BMC

BMC Portal 46BMC PATROL

Changes 12BMC ProactiveNet

Integration 46BMC ProactiveNet Performance Management

Abnormalities 48

Baselines 48

Key Performance Indicators 48

KPI 48

- C -Changes

BMC PATROL 12

EMC NetWorker 12Check

Instance Limits 43Classes 74

Clients

Delete 53

Disable 53

Enable 53Command

Reload Commands 72Configure

Alert Acknowledgement 63

Failover Mode 52

Group Backup Restriction 62

KM User Account 41

Index 131

Version 2.8.00


Configure

Log Error Filter 60

Log Scan Limit 62

Monitoring Period 55

Node Type 52

Paths 51

PATROL Agent 39Customize

Date/Time Format 65

Parameters 72

Pending Request Date/Time Format 65

Save Group Date/Time Format 65

- D -Daemons

Delete 53

Disable 53

Enable 53Data Collection

Force 72

Full 72Data Collectors

All 72

Force 72

Selected 72Databases

Delete 53

Disable 53

Enable 53Date/Time Format

Customize 65Debug

Mode 68Debugging

Disable 68

Enable 68Delete

Clients 53

Daemons 53

Databases 53

Group Client 53

Groups 53

Jukeboxes 53

Logs 53

Standalone Devices 53

Volume Pools 53Disable

Clients 53

Daemons 53

Databases 53

Debugging 68

Group Client 53

Groups 53

Jukeboxes 53

Logs 53


Volume Pools 53Discoveries

Force 72Discovery

Verify 43Disk Space

Requirements 17Display

Parameters 72

- E -EMC NetWorker

Changes 12Enable

Clients 53

Daemons 53

Databases 53

Debugging 68

Group Client 53

Groups 53

Jukeboxes 53

Logs 53


Volume Pools 53

- F -Failover Mode

Configure 52Files 18

ins_ALL_<version>.tar 18

ins_WINDOWS_<version>.exe 18

Setup 18

setup.exe 19

setup.sh 19

uninstall.exe 31

uninstall.sh 31Force

Index 132

Version 2.8.00


Force

Data Collectors 72

Discoveries 72

- G -Generate

Baselines 48

Reports 72Group Backup Restriction

Configure 62Group Client

Delete 53

Disable 53

Enable 53Groups

Delete 53

Disable 53

Enable 53

- H -help 129

- I -InfoBox

Aliases 81

Application 81

Application Name 75

Application Version 75

Architecture 81

Archive Only 124

Autostart 98

Available FS Space 93

Binary Path 75

Browse Policy 102

Cleaning Required 117, 121

Client Name 109

Client Retries 98

Clients 124

Clients Details 106

Clone Pool 98

Clone Storage Nodes 102

Clones 98

Collector Last End 80, 81, 83, 85, 87, 89,91, 93, 97, 98, 102, 104, 106, 109, 110, 111,113, 114, 117, 120, 121, 123, 124

Collector Last Start 81, 83, 85, 87, 89, 91,93, 97, 98, 102, 104, 106, 109, 110, 111,113, 114, 117, 120, 121, 123, 124

Collector Name 80, 81, 83, 85, 87, 89, 91,93, 97, 98, 102, 104, 106, 109, 110, 111,113, 114, 117, 120, 121, 123, 124

Collector Next Start 80, 81, 83, 85, 87,89, 91, 93, 97, 98, 102, 104, 106, 109, 110,111, 113, 114, 117, 120, 121, 123, 124

Collector Status 80, 81, 83, 85, 87, 89,91, 93, 97, 98, 102, 104, 106, 109, 110, 111,113, 114, 117, 120, 121, 123, 124

Command 85

Completion Status 106

Control Port 114

Copyright 75

CPU Type 81

CPUs 81

Date Last Cleaned 117, 121

Description 81, 85, 89, 93, 98, 102, 111,114, 117, 121, 124

Devices 124

Directive 102

Duration 106

Enabled 114, 117, 121, 124

Enabler in Use 81

End 106, 109

Event Message 114

Failed Save Sets 106

Files 106

FS Percent Used 93

Group Name 106, 109

Group Names 102

Groups 124

Host Name 75

Installation Path 75

Interval 98

IP Address 81

Jukebox Name 117

Last Backup 87

Last Backup Duration 106

Last Backup End 98, 102, 106

Last Backup Files 106

Last Backup Mode 87

Last Backup Save Group 98, 102, 106

Last Backup Save Set ID 87

Last Backup Size 106

Last Backup Start 98, 102, 106

Last Backup Status 98, 102

Last Backup Volume 87

Index 133

Version 2.8.00


InfoBox

Last Full Backup End 98, 102

Last Full Backup Save Group 98, 102

Last Full Backup Start 98, 102

Last Incr Backup End 98, 102

Last Incr Backup Save Group 98, 102

Last Incr Backup Start 98, 102

Last Operation 114

Last Operation Message 114

Last Purge 93

Level 106

Levels 124

Library Path 75

Log File Modification Time 93

Log File Size 93

Message 117, 121

Mode 111

Model 114

Monitoring Mode 75

Monitoring Node 75

Name 81, 83, 85, 87, 89, 93, 98, 102,114, 117, 121, 124

Next Backup 98

Node Name(s) 75

Node Type 75

Number of Devices 114

Number of Media 111

ONC Program Number 81

ONC Transport 81

ONC Version Number 81

Operating System 75, 81

Operation 117, 121

Owner 85

Parallelism 98, 102

Path 89, 93, 117, 121

PATROL Agent Version 75

Pending Save Sets 106

Percent Completed 106

PID 85

Platform 75, 81

PPID 85

Printer 98

Priority 102, 111

Product Name 75

Product Release Date 75

Product Version 75

Purpose 111

Read Only 117, 121

Request 111

Request Time 111

Retention Policy 102

Save Group 106

Save Sets 124

Schedule 102

Server 124

Server(s) 75

Servers 81

Size 106

Start 106, 109

Start Time 98

Status 81, 85, 98, 106, 109, 114, 117,121

Storage Node 111, 114, 117, 121

Storage Node(s) 75

Storage Nodes 102

Succeeded Save Sets 106

Suggestion 111

Support 75

Time Remaining 106

Total FS Space 93

Type 106, 117, 121, 124

Version 81

Volume 111

Volume Name 117, 121

Volume Pool 111

Volume Type 111, 124

Web Site 75Install / Un-install 19, 31

BMC Software Installation Utility 18

Log 19

Packages 18

Procedure 19

Setup Files 18Installation Path

Unix 14

Windows 14Instance Limits

Check 43Instrumentation (WMI) Core

Requirements 12Integration

BMC ProactiveNet 46Integration Service Agent 46

Introduction 19

Index 134

Version 2.8.00


- J -Jukeboxes

Delete 53

Disable 53

Enable 53

- K -Key Performance Indicators


Manage 48KM

Configure 41

Initial Setup 45

Load 37, 38, 46

Preload 39

Preloaded 39, 40

Prepare to Load 38

Unload 39, 40

User Account 41KM command

Debug 68

Force Full Collection 72

Refresh Process Cache 72KM Debug

Troubleshooting 127KPI


Manage 48

- L -Load

KM 37, 38, 46

PATROL Central 38

Prepare 38Log Alerts

Acknowledge 71Log Error Filter

Configure 60Log Scan Limit

Configure 62Logs

Delete 53

Disable 53

Enable 53

- M -Manage

Baselines 48

Key Performance Indicators 48

KPI 48Master Server

Configure 52Media Server

Configure 52Menu Commands

About 75

Acknowledgement 93, 104, 106

Administration 75, 117, 121

Alarms 93, 104

Alert 106

All 93, 104

Client 81

Client Status 81

Clients 80

Clients Status 80

Configuration 75, 80, 81, 83, 85, 89, 91,93, 97, 102, 104, 110, 113, 120, 124

Daemon 85

Daemon List 83

Daemon Status 85

Daemons 83

Daemons Status 83

Database 89

Database Backup Information 87

Databases 87

Debug 75

Disable Device 117, 121

Enable Device 117, 121

Force Discovery 75

Force Full Collection 104

Group Client 102

Groups 97

Groups Backup Restriction 97

Groups Status 97

Instance Limits 75

Jukebox 114

Jukebox Auto Media Mgmt Status 114

Jukebox Contents 114

Jukebox Device 117

Index 135

Version 2.8.00


Menu Commands

Jukebox Device Status 117

Jukebox Devices 114

Jukebox Devices Status 113, 114

Jukebox Status 114

Jukeboxes 113

Jukeboxes Auto Media Mgmt Status 113

Jukeboxes Status 113

KM Status 75

Log 93

Log Alert Acknowledgement 93

Log Filter 93

Log Scan Limit 93

Login 75

Logs 91

Logs Alert Acknowledgement 91

Logs Filter 91

Logs Scan Limit 91

Messages List 91

Monitoring Mode 75

Mount Tape 121

Node Status 75

Node Type 75

Paths 75

Pending Request Date/Time Format 110

Pending Requests 110

Pending Requests Status 110

Preloading 75

Refresh Parameters 75

Refresh Process Cache 75

Reload Commands 75

Reports 83, 87, 91, 110, 114, 124

Save Groups 104

Save Groups Alert Acknowledgement 104

Save Groups Date/Time Format 104

Save Groups Status 104

SaveSet Error Event Contents 104

Standalone Device 121

Standalone Device Status 121


Standalone Devices Status 120

Start Server/Storage Node 75

Stop Server/Storage Node 75

Unmount Tape 121

Volume List 124

Volume Pool 124

Warnings 93, 104Monitor Type 46

Monitoring

Save Clients 57Monitoring Period

Configure 55

Pending Requests 55

Save Groups 55MS Windows Management

Requirements 12MS Windows Scripting Host

Requirements 12

- N -Node Type

Configure 52

Master Server 52

Media Server 52NSR_CLIENT

Application Class 81NSR_CLIENT_CONTAINER

Application Class 80NSR_DAEMON

Application Class 85NSR_DAEMON_CONTAINER

Application Class 83NSR_DATABASE

Application Class 89NSR_DATABASE_CONTAINER

Application Class 87NSR_DEVICE

Application Class 121NSR_DEVICE_CONTAINER

Application Class 120NSR_JCLIENT

Application Class 109NSR_JOB

Application Class 106NSR_JOB_CONTAINER

Application Class 104NSR_LDEVICE

Application Class 117NSR_LIBRARY

Application Class 114NSR_LIBRARY_CONTAINER

Application Class 113NSR_LOAD

Troubleshooting 127NSR_LOG_CONTAINER

Application Class 91

Index 136

Version 2.8.00


NSR_MOUNT

Application Class 111NSR_MOUNT_CONTAINER

Application Class 110NSR_PCLIENT

Application Class 102NSR_POLICY

Application Class 98NSR_POLICY_CONTAINER

Application Class 97NSR_POOL

Application Class 124NSR_POOL_CONTAINER

Application Class 123NSR_SERVER

Application Class 75NSR_SETUP

Troubleshooting 127NSRLoginStatus

Troubleshooting 127

- O -Operating System

Access 14

AIX 14

HP-UX 14

Solaris 14Operating Systems

Linux 18, 19, 31

Unix 18, 31

Windows 18, 19, 31Options

Common services 19

Console Systems role 19

Managed System 19

View Log 19

- P -Parameter

NSRLoginStatus 41Parameters 74

Customize 72

Display 72

ExtraFilesList 75

NSRAdministratorChange 75

NSRClientCollector 75

NSRClientDetails 80

NSRClientIndexRecordCount 81

NSRClientIndexSpaceUsed 81

NSRClientIndexSpaceUsedPercent 81

NSRClientState 81

NSRClientStatus 81

NSRClientSummary 81

NSRCreateDistribution 75

NSRDaemonCollector 75

NSRDaemonCPUDuration 85

NSRDaemonCPUUtilization 85

NSRDaemonDetails 83

NSRDaemonMemorySize 85

NSRDaemonProcessCount 85

NSRDaemonState 85

NSRDaemonStatus 85

NSRDaemonSummary 85

NSRDatabaseBackupElapsed 87

NSRDatabaseCollector 75

NSRDatabaseDetails 87

NSRDatabaseFSSpaceUsedPercent 89

NSRDatabaseRetention 87

NSRDatabaseSpaceAvailable 89

NSRDatabaseSpaceGrowthRate 89

NSRDatabaseSpaceUsed 89

NSRDatabaseSpaceUsedPercent 89

NSRDatabaseSummary 89

NSRDeviceCollector 75

NSRDeviceDetails 120

NSRDeviceSessionCount 121

NSRDeviceSessionMax 121

NSRDeviceSessionTarget 121

NSRDeviceState 121

NSRDeviceStatus 121

NSRDeviceSummary 121

NSRDeviceThroughput 121

NSRGClientBackupSummary 102

NSRGClientBackupThroughput 102

NSRGClientFullBackupDuration 102

NSRGClientFullBackupFileCount 102

NSRGClientFullBackupSize 102

NSRGClientIncrBackupDuration 102

NSRGClientIncrBackupFileCount 102

NSRGClientIncrBackupSize 102

NSRGClientSummary 102

NSRGroupBackupElapsed 98

NSRGroupBackupSummary 98

NSRGroupBackupThroughput 98

NSRGroupCollector 75

Index 137

Version 2.8.00


Parameters 74

NSRGroupDetails 97

NSRGroupFullBackupDuration 98

NSRGroupFullBackupElapsed 98

NSRGroupFullBackupFileCount 98

NSRGroupFullBackupSize 98

NSRGroupIncrBackupDuration 98

NSRGroupIncrBackupElapsed 98

NSRGroupIncrBackupFileCount 98

NSRGroupIncrBackupSize 98

NSRGroupState 98

NSRGroupStatus 98

NSRGroupSuccBackupElapsed 98

NSRGroupSummary 98

NSRJDeviceState 117

NSRJDeviceStatus 117

NSRJDeviceSummary 117

NSRJDeviceThroughput 117

NSRJukeboxAutoMediaMgmtState 114

NSRJukeboxAutoMediaMgmtStatus 114

NSRJukeboxCleaningLeftCount 114

NSRJukeboxCollector 75

NSRJukeboxDetails 113

NSRJukeboxState 114

NSRJukeboxStatus 114

NSRJukeboxSummary 114

NSRJukeboxThroughput 114

NSRJukeboxUpDriveCount 114

NSRJukeboxVolumeAssignedCount 114

NSRJukeboxVolumeCount 114

NSRJukeboxVolumeEmptyCount 114

NSRJukeboxVolumeEmptyPercent 114

NSRLogAlarmCount 93

NSRLogAlarmText 93

NSRLogCollector 75

NSRLogDetails 91

NSRLogFSSpaceUsedPercent 93

NSRLoginStatus 75

NSRLogRendered 93

NSRLogSpaceAvailable 93

NSRLogSpaceGrowthRate 93

NSRLogSpaceUsed 93

NSRLogSpaceUsedPercent 93

NSRLogSummary 93

NSRLogText 93

NSRLogWarningCount 93

NSRLogWarningText 93

NSRMonitoringMode 75

NSRMonitorRAP 75

NSRNodeStatus 75

NSRPoolCollector 75

NSRPoolDetails 123

NSRPoolSpaceAvailable 124

NSRPoolSpaceGrowthRate 124

NSRPoolSpaceUsed 124

NSRPoolSpaceUsedPercent 124

NSRPoolSummary 124

NSRRequestCollector 75

NSRRequestDetails 110

NSRRequestElapsed 111

NSRRequestState 111

NSRRequestStatus 111

NSRRequestSummary 111

NSRSaveClientState 109

NSRSaveClientStatus 109

NSRSaveClientText 109

NSRSaveGrpActiveBackupCount 104

NSRSaveGrpActiveCount 104

NSRSaveGrpActiveNonBackupCount 104

NSRSaveGrpCollector 75

NSRSaveGrpDetails 104

NSRSaveGrpDuration 106

NSRSaveGrpFileCount 106

NSRSaveGrpManualSaves 104

NSRSaveGrpSize 106

NSRSaveGrpState 106

NSRSaveGrpStatus 106

NSRSaveGrpSummary 106

NSRSaveGrpText 106

NSRSaveGrpThroughput 106

NSRSaveSetCount 106

NSRSaveSetFailedCount 106

NSRSaveSetIncludeList 102

NSRSaveSetList 106

NSRSaveSetPendingCount 106

NSRSaveSetSucceededCount 106

NSRServerSummary 75

NSRUpdateAgent 75

NSRVolumeActiveCount 124

NSRVolumeActivePercent 124

NSRVolumeAvailableCount 124

NSRVolumeAvailablePercent 124

NSRVolumeCount 124

NSRVolumeEmptyCount 124

NSRVolumeFullCount 124

NSRVolumeFullPercent 124

NSRVolumeManualRecycleCount 124

NSRVolumeReadOnlyCount 124

Index 138

Version 2.8.00


Parameters 74

Refresh 72Paths

Binary 51

Configure 51

Debug Directory 51

Home Directory 51

Library 51

Netbackup Installation 51

NetBackup Log Directory 51

Temp Directory 51PATROL

Agent 41

PATROL Agent 12, 39

PATROL Agent system 17

PATROL Central Console 39, 40

PATROL Central Console Server system 17

PATROL Central Web Server system 17

PATROL Console 12, 39

PATROL Console system 17PATROL Agent

Configure 39

Requirements 11

Restart 45PATROL Console 38

Requirements 11

Restart 45Pending Request Date/Time Format

Customize 65Pending Requests

Administer 50

Configure 55

Monitoring Period 55Permissions

Access 14Platform

Upgrade 72Platforms

Unix 41Poor performance

Troubleshooting 127Portal 12

Preload

KM 39Preloaded

KM 39, 40ProactiveNet 46

PW Commands 47

- R -Refresh

Parameters 72Release Notes 9

Reports

Daemon List 72

Database Backup Information 72

Generate 72

Jukebox Contents 72

Messages List 72

Pending Requests 72

Volumes List 72Requirements

Disk Space 17

Instrumentation (WMI) Core 12

MS Windows Management 12

MS Windows Scripting Host 12

PATROL Agent 11

PATROL Console 11

Security 14

Software 11, 12

Sudo 12Restart

PATROL Agent 45

PATROL Console 45

- S -Save Clients 104

All 57

Failed 57

Monitoring 57

None 57

Succeeded 57Save Clients Status 104

Save Group Alerts

Acknowledge 71Save Group Date/Time Format

Customize 65Save Groups 72

Configure 55

Monitoring Period 55Security

Requirements 14Server/Storage Node

Start 50

Index 139

Version 2.8.00


Server/Storage Node

Stop 50Setup

Check 45

Initial 45

KM 45Software

Instrumentation (WMI) Core 12

MS Windows Management 12

MS Windows Scripting Host 12

Requirements 11, 12

Sudo 12Standalone Devices

Delete 53

Disable 53

Enable 53Standalone Drives

Administer 51Start

Server/Storage Node 50Stop

Server/Storage Node 50Sudo 41

Requirements 12

User 14Symantec NetBackup

Administer 50

- T -Thresholds

Customize 47

Import 47Troubleshooting

KM Debug 127

NSR_LOAD 127

NSR_SETUP 127

NSRLoginStatus 127

Poor performance 127

- U -Unix 41

Installation Path 14Unload

KM 39, 40Upgrade

Platform 72

- V -Verify

Application Discovery 43Volume Pools

Delete 53

Disable 53

Enable 53

- W -Windows

Installation Path 14

Registry 14

About BMC® SoftwareBMC Software, Inc. NYSE:BMC, is a leading provider of enterprise management solutionsthat empower companies to manage their IT infrastructure from a business perspective.Delivering Business Service Management, BMC Software solutions span enterprisesystems, applications, databases, and service management. Founded in 1980, BMCSoftware has offices worldwide and fiscal 2004 revenues of more than $1.4 billion. For

more information about BMC Software, visit www.bmc.com.

About Sentry Software™Sentry Software, a strategic Technology Alliance Partner of BMC Software, provides keymonitoring solutions specifically designed to expand the capabilities of BMCPerformance Manager, thus enabling up to 100% coverage of any infrastructure. SentrySoftware specializes in single solutions for multi-platform monitoring of hardware,custom applications or any IT component, and blackout windows. Sentry Softwareproducts are deployed in 45 countries across the globe and lead the list of BMCSoftware’s third-party product sales. For more information about Sentry Software,

please visit www.sentrysoftware.net.

emc networker km for patrol 2.8 - sentry software · bmc proactivenet performance management...

Documents