Symantec NetBackup for PATROL Version 2.8 · Symantec NetBackup KM for PATROL NBU_DAEMON ... In...

User Documentation July 2013

Symantec NetBackup KM forPATROLVersion 2.8.03

Contacting BMC SoftwareYou can access the BMC Software Web site at http://www.bmc.com/. From this Web site, you can obtaininformation about the company, its products, corporate offices, special events, and career opportunities.

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 RESERVED UNDERTHE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data andcomputer software by the U.S. Government is subject to restrictions, as applicable, set forth in FARSection 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101CityWest Blvd., Houston, TX 77042-2827, USA. Any contract notices should be sent to this address.

2

Version 2.8.03

Symantec NetBackup 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, call800 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 Support canbegin 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, and service

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

messages from the operating system, such as "file system full"

3

Version 2.8.03


http://www.bmc.com/support_home



Table of Contents 4

Version 2.8.03


Table of Contents...........................................................................................................................8Release Notes for v2.8.03

...........................................................................................................................10Overview

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

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

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

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

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

..................................................................................................................20Disk Space Requirements

...........................................................................................................................21Getting the BMC Software Installation Utility

...........................................................................................................................22Packages

...........................................................................................................................22Extracting the Setup Files

...........................................................................................................................22Installing the KM

...........................................................................................................................23Installing Symantec NetBackup KM for PATROL

...........................................................................................................................35Uninstalling Symantec NetBackup KM for PATROL

...........................................................................................................................40Upgrading the Platform

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

..................................................................................................................41Loading the KM

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

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

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

..................................................................................................................43Unloading the KM

..............................................................................................................43Unloading the KM from the PATROL Agent

..............................................................................................................44Unloading the KM from the PATROL Console

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

...........................................................................................................................45Performing Post-Installation Operations

..................................................................................................................45Configuring the KM User Account

..................................................................................................................47Verifying Application Discovery

..................................................................................................................47Checking the Instance Limits

..................................................................................................................49Checking the Initial Setup

..................................................................................................................49Restarting PATROL Agent and PATROL Console

...........................................................................................................................50Integrating the KM

...........................................................................................................................50Integrating with BMC Portal

Table of Contents 5

Version 2.8.03


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

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

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

..................................................................................................................51Importing and Customizing Thresholds

..................................................................................................................52Managing Baselines and Key Performance Indicators

...........................................................................................................................54Monitoring your Environment

...........................................................................................................................54Administering Symantec NetBackup

..................................................................................................................54Starting Master/Media Server

..................................................................................................................55Stopping Master Media Server

..................................................................................................................55Assigning, Denying, or Resubmitting Mount Requests

..................................................................................................................56Bringing Standalone Drives Online or Offline

..................................................................................................................56Bringing Robotic Drives Online or Offline

...........................................................................................................................57Configuring the KM

..................................................................................................................57Configuring Paths

..................................................................................................................58Specifying the Node Type

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

..................................................................................................................60Filtering Elements to Monitor

..................................................................................................................62Configuring Monitoring Periods

..................................................................................................................65Configuring the Elements Status

..................................................................................................................67Configuring the Node Status

..................................................................................................................68Configuring Mount Requests Date/Time Format

..................................................................................................................69Configuring the Log Filter

..................................................................................................................7 0Configuring the Log Scan Limit

..................................................................................................................7 1Configuring Jobs Erroneous Exit Status Filter

..................................................................................................................7 2Configuring Policy Backup Restriction

..................................................................................................................7 3Configuring Alert Acknowledgement

..................................................................................................................7 5Refreshing Parameters

..................................................................................................................7 6Reloading Commands

..................................................................................................................7 7Enabling the Debug Mode

...........................................................................................................................80Acknowledging Alerts

...........................................................................................................................81Generating Reports

...........................................................................................................................81Reference Guide

...........................................................................................................................82Classes and Parameters

..................................................................................................................83NBU_CLIENT_CONTAINER

..................................................................................................................85NBU_CLIENT

..................................................................................................................86NBU_DAEMON_CONTAINER

Table of Contents 6

Version 2.8.03


..................................................................................................................89NBU_DAEMON

..................................................................................................................91NBU_DATABASE_CONTAINER

..................................................................................................................92NBU_DATABASE

..................................................................................................................95NBU_DEVICE

..................................................................................................................97NBU_DEVICE_CONTAINER

..................................................................................................................99NBU_DPOOL

..................................................................................................................101NBU_DVOLUME

..................................................................................................................103NBU_JOB_CONTAINER

..................................................................................................................106NBU_JOB

..................................................................................................................109NBU_LDEVICE

..................................................................................................................111NBU_LIBRARY_CONTAINER

..................................................................................................................112NBU_LIBRARY

..................................................................................................................115NBU_LOG_CONTAINER

..................................................................................................................117NBU_LOG

..................................................................................................................120NBU_MOUNT

..................................................................................................................122NBU_MOUNT_CONTAINER

..................................................................................................................123NBU_PCLIENT

..................................................................................................................126NBU_POLICY_CONTAINER

..................................................................................................................127NBU_POLICY

..................................................................................................................132NBU_POOL_CONTAINER

..................................................................................................................133NBU_POOL

..................................................................................................................136NBU_SERVER

..................................................................................................................142NBU_STORAGE_CONTAINER

..................................................................................................................144NBU_STORAGE

...........................................................................................................................145Additional Information

...........................................................................................................................145Troubleshooting

...........................................................................................................................149Impact on Resources

...........................................................................................................................149Customer Support

8Release Notes for v2.8.03

Version 2.8.03


Release Notes for v2.8.03

What's NewJob Configuration: Child jobs, typically retry jobs, are now created under their parent jobs withthe job status alerts snoozed by default. This reduces the amount of events triggered for a jobfailure. It is also possible to trigger alerts for the child job failures by changing the settings in thejob configuration menu.

New Report: The Available Media report is added to Volume Pools to report on all availablemedia.

NBUDatabaseStatus: New parameter added to check the availability of NetBackup database(NBDB).

Inactive standard parameters labelled <collector>ExecTime were added to monitor theperformance of each collector. Please refer to the Reference Guide for detailed information.

A 'no command execution window' can be defined for the KM to avoid running NetBackupcommands during regular maintenance window everyday. Please refer the Troubleshooting sectionof this guide for detailed information.

Three new parameters added to the NBU_JOB_CONTAINER application class:

NBUJobActiveBackupReduction displays the reduction in number of active backup jobs(NBUJobActiveBackupCount) between collection cycles.

NBUJobQueuedBackupCount displays the number of backup jobs in 'Queued' state.

NBUJobQueuedBackupReduction displays the reduction in number of queued backup jobs(NBUJobQueuedBackupCount) between collection cycles.

Changes and ImprovementsErroneous Exit Status filter: the filter is changed to support both failure and erroneous filters.They are used for setting NBUJobState to Failed (10) or Error (6) state respectively.

NBUDatabaseCollector: The collector now searches all backup jobs in the NetBackup database todetermine the last database backup and set NBUDatabaseElapsed. Previous versions weresearching only in the new backup jobs since the last job collection cycle. The alert conditions onNBUDatabaseElapsed are also turned back on to trigger alerts if there are no database backupsfound or if they are too old.

Two new states added to parameter NBUPolicyState:

Inactive policy is monitored by setting NBUPolicyState to “Inactive”.

Next backup of each active policy is calculated and if jobs were not started as per the schedule,NBUPolicyState will be set to “Not Started”.

Two new states added to parameter NBURDriveState to trigger alarms throughNBURDriveStatus:

When robotic drives change to AVR mode, they will be alerted by setting NBURDriveState to“Invalid”

If a previously discovered robotic drive is missing, NBURDiveState will be set to “Missing”.


Version 2.8.03


All configuration menu (KM commands) support regular expressions. For example, the Policyconfiguration menu can be used for disabling all “test” policies, which will also stop monitoring theirjobs.

Backup job report is stored and shared between collectors to avoid rerunning bpdbjobs command.This reduces the number of commands executed by the job collector and improves the performanceconsiderably, especially at large NetBackup sites.

Robotic libraries and drives discovery commands are shared and optimized for performance.

Collectors are synchronized to reduce the load on the agent while using the data as they becomeavailable.

Unnecessary debug messages are removed.

Faster KM failover in clustered NetBackup environment. The server discovery interval is reducedfrom 5 minutes to 40 seconds, which speeds up detecting server level changes as well as clusteredNetBackup server failover.

The KM Status report now provides collector/discovery collection time information as well asadditional performance details. This report is stored under PATROL_HOME/lib/NBU/km_status.txt onall managed nodes.

NBUJobCollector has been significantly optimized to perform job collection more rapidly.

Fixed IssuesA syntax error message was displayed when loading NetBackup KM for PATROL on a managedsystem.


Version 2.8.03


On Unix platforms, daemon collector command & arguments are modified to return only the relevantdaemon lines from the process list. This corrects an error in setting the parameters for ProcessCount, Memory Size, CPU Utilization & CPU Duration.

Incorrect border alarm on NBULibraryMediaScratchCount triggered alerts when there are more100 scratch media. The border alarms are now removed to stop the inappropriate event. Also theborder alert on NBULibraryMediaAvailablePercent is removed to stop alerting when the value isunknown.

An error in a script made the KM fail to calculate the scratch count affecting NBULibraryScratchCount & NBULibraryScratchPercent parameters.

Duplicate client instances were created when clients were configured with short hostname and fullyqualified hostnames. The client collector now takes the first occurrence of such clients and ignoresthe other duplicates.

In clustered NetBackup systems, passive nodes run as media server and change to master duringfailover. The KM did not detect this node type change without an Agent restart. Node changes arenow applied during the next collection cycle and all collectors are refreshed immediately.

Error reading “Failed to obtain lock on SOWLogWriteLock” was repeatedly displayed in the SystemOutput Window and NBU.log on Windows managed nodes. This error is now corrected and the log fileNBU.log is rotated successfully.

When disabling monitored components using the KM configuration menus it disables all instanceswith the same label, but under different parent. This affects policy clients, robotic drives, disk pools& volumes.

If any of the commands used by the KM failed to return a required field, the KM failed to process theremaining fields in the command output. The missing field are now ignored.

Configuration menu changes at the container level did not take effect without an Agent restart.

When upgrading KM from v2.7.x to v2.8.x, some of the instance level KM configuration data storedin the PATROL configuration were not upgraded.

In clustered NetBackup servers, when a cluster node failed to report the cluster status, the KMchanged to “Temporary Single-node Mode” without checking the KM status on the other clusternodes. The KM now checks the remote node status prior to changing monitoring mode.

Backup Job Report: Long command output lines prevented the report to be properly processed. Thescript has been modified to handle long command lines.

The syntax error in NBU_Drive_stats.sh affecting the drive stats collection has been fixed.

Overview

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

The KM more especially monitors the:

11Overview

Version 2.8.03


Server availability: status, memory and CPU time consumption, etc.

Jobs: status, duration, data throughput and time elapsed since last backup, comparative statistics,etc.

Log Files: size, content, growth rate, file system space utilization, etc.

Robotic libraries and drives: library and drive status, throughput, loaded media identification,etc.

Disk storage and volume pools: space utilization, status, count, etc.

Catalog database: space utilization, file system monitoring, time since the last database backup,etc.

Client: connectivity, metrics from the last successful backup, etc.

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 installingSymantec NetBackup KM for PATROL. Make sure to carefully read the following sections requirements:

Review the System, Software, Security and Disk Space Requirements

Get the BMC Software Installation Utility

Download the Installation Packages

Extract the Setup Files

RequirementsBefore installing the NetBackup KM, verify the:

System requirements

Software requirements

Security requirements

Disk space requirements.

System RequirementsSymantec NetBackup KM for PATROL supports the following operating systems:

Operating System Version

Oracle SolarisTM 8, 9, 10

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

IBM® AIXTM 5.1, 5.2, 5.3, 6.1

Red Hat® Linux® 7.2

12Preparing for Installation

Version 2.8.03


Microsoft® Windows® 2003, 2008, 2008 R2

If the operating system is upgraded (or downgraded) at a later date, you will need to reloadcommands for the NetBackup KM. Refer to Upgrading the Platform.


Version 2.8.03


Software RequirementsSymantec NetBackup KM for PATROL supports:

Software Version

Symantec NetBackup™ 5.0, 5.1, 6.0, 6.5, 7, 7.1, 7.5

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

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

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

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

If the operating system is upgraded (or downgraded) at a later date, you will need to reloadcommands for the NetBackup KM. Refer to Upgrading the Platform.

If you're running the NetBackup KM with sudo user account, or on AIX, LINUX, or Microsoft Windows x64managed nodes, please verify these additional software requirements:

Purpose Software Version

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

Sudo (superuser do) 1.6.7 or later

When running NBU KM on AIX managed nodes Default ncargs value for processing bpdbjobsoutput may not be sufficient.

Check this attribute using:lsattr -EH -l sys0 | grep ncargs

If the value is below 16, increase it using:chdev -l sys0 -a ncargs=16

Any

When running NBU KM on Linux managed nodes

Korn shell binary (/bin/ksh) Any

When running NBU KM on Microsoft Windows x64 managed nodes

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

Any

The Microsoft Windows x64 Reg.exe patch, KB948698 is required to allow access to 64-bit registrykeys from PATROL Agent. Access the above patch site from the managed node to obtain the correctpatch for that platform.

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

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


Version 2.8.03


Changes Required

No changes need to be done to Symantec NetBackup to use Symantec NetBackup KM for PATROL.

Some changes must however be made to BMC PATROL to improve the performance of SymantecNetBackup KM for PATROL. The PATROL Agent tuning variable “/AgentSetup/AgentTuning/pslInstructionMax” should be disabled by setting it to 0 (zero) or increased to at least 5,000,000.

This applies for all Symantec NetBackup master servers and media servers where the KM is installed.This adjustment will allow the data collectors to execute without incurring an internal scheduling delay.

This PATROL Agent tuning variable can be updated using wpconfig (on Microsoft Windows), xpconfig(on Unix) or PATROL Configuration Manager (PCM). Alternatively, you can use one of the followingsingle line PSL command through the PATROL Console OS> prompt to update this tuning variable.

To disable the tuning variable:

%PSL pconfig("REPLACE",

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

To set to at least 5,000,000:

%PSL v="/AgentSetup/AgentTuning/pslInstructionMax";

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

In large Symantec NetBackup 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 W indow (SOW)reporting that some NetBackup KM data collectors are in an infinite loop. In this case you can set the tuning variableto zero to disable this functionality .

The KM stores all configuration information in the PATROL Agent configuration database (pconfig),under the /NBU and /Runtime/NBU paths. 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 make sure that the mode for PATROL Agentuser includes “C” in the PATROL Agent variable “/AgentSetup/accessControlList”. Please refer the PATROL Agent Reference Manual for more details.


Version 2.8.03


Security RequirementsA user account with administrative privileges must be configured in BMC PATROL to read and executeSymantec NetBackup application programs and access file systems. Depending on the operating systemsused, several options will be available.

The following user accounts can be used:

On Unix platforms:

a root user

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

a non-root account, such as patrol, configured in Symantec NetBackup application to administerthe Symantec NetBackup application.

On Windows platforms:

an administrator user

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

Users added to NBU_Admin user group in VxSS. Please make sure the credentials of this user donot expire using the utility nbac_cron.

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

The encrypted password can be viewed by any user who has access to the PATROL Agentconfiguration variables (pconfig). This user could then execute PSL statements using the encryptedpassword through the PATROL Console. This can be prevented by setting up an appropriate AccessControl List (ACL) for users. Please refer to the PATROL Agent Reference Manual for details on howto set up an ACL.


Version 2.8.03


Access Permissions

The NetBackup KM user needs “read & execute” permission to executable and library files under thepaths listed below. The Symantec NetBackup installation path INSTALL_PATH, referenced in the tablesbelow is normally /usr/openv or /opt/VRTSnetbp (on Unix) or C:\Program Files\Veritas (onMicrosoft Windows).

Executable and Library Files accessed by the NetBackup KM User

Unix Microsoft Windows

INSTALL_PATH/netbackup INSTALL_PATH\NetBackup

INSTALL_PATH/netbackup/bin INSTALL_PATH\NetBackup\bin

INSTALL_PATH/netbackup/bin/admincmd INSTALL_PATH\NetBackup\bin\admincmd

INSTALL_PATH/netbackup/bin/goodies INSTALL_PATH\NetBackup\bin\goodies

INSTALL_PATH/volmgr/bin INSTALL_PATH\Volmgr\bin

INSTALL_PATH/volmgr/bin/goodies INSTALL_PATH\Volmgr\bin\goodie

INSTALL_PATH/lib C:\Program Files\Common Files\VERITAS Shared

/usr/openwin/lib INSTALL_PATH\NetBackup\lib

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

/opt/VRTSvcs/bin/hagrp (in Veritas Cluster Server)

vxdctl (in Veritas Cluster File System)

/usr/cluster/bin/clrg (in Oracle Solaris Cluster)

The NetBackup KM includes some scripts which should be executable by the PATROL Agent user and theNetBackup KM user. These scripts are stored under KM_HOME path, normally PATROL_HOME/lib/NBU.


Version 2.8.03


To list all OS commands used by the NetBackup 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/NBU/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));

Paths and Files Accessed by PATROL Agent User

Unix Microsoft Windows

INSTALL_PATH/netbackup/db INSTALL_PATH\NetBackup\db

INSTALL_PATH/volmgr/database INSTALL_PATH\Volmgr\database

INSTALL_PATH/var INSTALL_PATH\NetBackup\var

INSTALL_PATH/netbackup/db/error/ daily_messages.log

INSTALL_PATH\NetBackup\db\error\log_date

/var/adm/messages (on Solaris)

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

/var/log/messages (on Linux)

If a monitored log file cannot be read by the PATROL Agent user, it will be copied to KM_TEMP pathusing the configured 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.


Version 2.8.03


On Windows platforms the Symantec NetBackup installation is identified by checking the MicrosoftWindows Registry: HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\

The configured login user should have sufficient privileges to run regedit command on the managednode.

Sudo User for Operating System Access

If a non-root user with sudo privileges is preferred as the KM user, configure the account as a sudoerthrough the visudo utility using code appropriate for your platform as detailed below. This user shouldbe able to execute NetBackup commands and OS commands listed in above.

The code below also applies to all non-root users who may execute NetBackup KM administration andreport menu commands using their sudo privileges. The KM accepts any non-root user with thefollowing sudo configuration in the sudoers file. Please replace user1, user2, user3 with appropriate KMuser names. The Symantec NetBackup installation path INSTALL_PATH, referenced below is normally /usr/openv or /opt/VRTSnetbp and PATROL_HOME is the path where the PATROL Agent is installed(including the target, like /opt/bmc/Patrol3/Solaris29-sun4/).

This non-root sudo user configured in the KM will be able to execute Symantec NetBackupcommands. To prevent unauthorized access, ensure this user is only used within the KM and notmade public for general use.

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

On SolarisUser_Alias NBUKMUSERS = user1, user2, user3

Defaults:NBUKMUSERS !lecture,!authenticate,\

env_keep+="SHLIB_PATH INSTALL_PATH KM_HOME KM_TEMP",env_reset

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

INSTALL_PATH/netbackup/bin/*,\

INSTALL_PATH/netbackup/bin/admincmd/*,\

INSTALL_PATH/netbackup/bin/goodies/*,\

INSTALL_PATH/volmgr/bin/*,\

INSTALL_PATH/volmgr/bin/goodies/*,\

INSTALL_PATH/db/bin/*,\

PATROL_HOME/lib/NBU/*,PATROL_HOME/bin/*

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


Version 2.8.03


On HP-UXUser_Alias NBUKMUSERS = user1, user2, user3












On AIX & LinuxUser_Alias NBUKMUSERS = user1, user2, user3













Version 2.8.03


Disk Space RequirementsSymantec NetBackup KM for PATROL requires approximately:

• 2.5 MBytes of available disk space on each monitored PATROL Agent system

• 3.5 MBytes of available disk space on each PATROL Console system

• 600 KBytes of available disk space on each PATROL Central Console Server system

• 1.4 MBytes of available disk space on each PATROL Central Web Server system

It is installed under the PATROL installation path.

When monitoring a standard installation of Symantec NetBackup, the PATROL Agent will generateapproximately 500 KBytes of history data per day. An enterprise installation of Symantec NetBackup on amaster server with multiple media servers, clients, robotic libraries, and standalone drives will generatemore history data (as per other KMs used by the PATROL Agent). These history data files are recycledby PATROL depending on the PATROL Agent history retention period.

During execution, the KM creates and maintains temporary files under KM_HOME, KM_TEMP andKM_DEBUG paths. By default they are all under PATROL_HOME/lib/NBU, where PATROL_HOME pathis normally opt/bmc/Patrol3/ (on Unix) or C:\Program Files (x86)\BMC Software\Patrol3\ (onMicrosoft Windows).

If the location of the KM_TEMP or KM_DEBUG is not suitable, it can be changed using theConfiguration>Paths menu from the main instance. These folder should have read, write andexecute permissions for both the PATROL Agent user and the KM login user.


Version 2.8.03


Getting the BMC Software Installation UtilityIn order to install Symantec NetBackup 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 (electronicproduct download) from: http://webapps.bmc.com/signon/content/logon.jsp on the BMC SoftwareWebsite, or from the Symantec NetBackup KM for PATROL page on the Sentry Software Website

Choose the appropriate package depending on the platform you plan to install Symantec NetBackup 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 Symantec NetBackup KM for PATROLpackages.

http://webapps.bmc.com/signon/content/logon.jsp

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


Version 2.8.03


PackagesThe Symantec NetBackup KM for PATROL packages are available on the Sentry Software Web site.

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

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

Every managed system with a PATROL Agent

Every PATROL Console (Classic) that will show Symantec NetBackup performance-relatedinformation and alerts

The Console Server

PATROL Central – Web Edition

Installing the KM

Introduction

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

http://www.sentrysoftware.com

23Installing the KM

Version 2.8.03


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

Browse to the bmc_products folder where the files have been extracted (both Symantec NetBackup KMfor PATROL and the Common Installer).

On Windows: Launch the setup.exe program

On UNIX: Launch the setup.sh script

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

Installation Wizard - Step 1: Windows Security A lert

24Installing the KM

Version 2.8.03


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

Installation Wizard - Step 2: Welcom e

25Installing the KM

Version 2.8.03


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

Installation Wizard - Step 3: Rev iewing License A greem ent

26Installing the KM

Version 2.8.03


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

Installation Wizard - Step 4: Selecting Installation Options

27Installing the KM

Version 2.8.03


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 Wizard - Step 5: Selecting the Installation Directory

28Installing the KM

Version 2.8.03


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

Installation Wizard - Step 6: Selecting an Installation Ty pe

7. Select one or several of the following options:

Managed System to install Symantec NetBackup KM for PATROL on a PATROL Agent.

Console Systems role to install Symantec NetBackup KM for PATROL on a PATROL ClassicConsole.

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

Click Next to continue.

29Installing the KM

Version 2.8.03


Installation Wizard - Step 7: Selecting Roles

Select as many options as required.

30Installing the KM

Version 2.8.03


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

Installation Wizard - Step 8: Selecting Products and Com ponents

31Installing the KM

Version 2.8.03


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

Installation Wizard - Step 9: Rev iewing Installation Options

32Installing the KM

Version 2.8.03


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 Wizard - Step 10: Installation Status

33Installing the KM

Version 2.8.03


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

Installation Wizard - Step 11: Installation Results

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

34Installing the KM

Version 2.8.03


Installation Wizard - Step 12: Com pleting and closing the Installation Wizard

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.

35Installing the KM

Version 2.8.03


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

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

Software, or /opt/bmc):

On Windows systems, launch uninstall.exe

On UNIX, launch uninstall.sh

Un-install Wizard — Welcom e Step

36Installing the KM

Version 2.8.03


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

Un-install Wizard — Specify ing folder

37Installing the KM

Version 2.8.03


3. To uninstall the KM, select Symantec NetBackup KM for PATROL.

Un-install Wizard — Selecting Products and Com ponents Directory

38Installing the KM

Version 2.8.03


4. Click Start Uninstall.

Un-install Wizard — Rev iewing Selected Products & com ponents and start uninstalling

39Installing the KM

Version 2.8.03


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

Un-install Wizard — Status

40Installing the KM

Version 2.8.03


6. A page displaying SUCCESS indicates that Symantec NetBackup KM for PATROL is nowuninstalled.

Un-install Wizard — Uninstall Results

Upgrading the PlatformIf you upgrade (or downgrade) your operating system or Symantec NetBackup, the commands for theNetBackup KM need to be reloaded.

Use the menu Reload Commands from the Symantec NetBackup instance.

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.

41Installing the KM

Version 2.8.03


Loading the KMBefore loading the NetBackup KM:

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

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

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

Loading the KM on PATROL Console

To load the KM on a PATROL Console:

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

2. Select the NBU_LOAD.kml file

3. Click Open or OK.

The NetBackup KM will be loaded to the PATROL Console, and all connected PATROL Agents will startdiscovering the Symantec NetBackup environment. If the automatic discovery successfully finds theSymantec NetBackup master/media server installation, the NBU_SETUP instance will be instantiated.

The automatic discovery may take up to 5 minutes to instantiate the NBU_SETUP instance. Look for any errormessages on the PATROL Console System Output W indow (SOW) during the initial discovery .

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

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

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

3. Configure the KM.

Loading the KM on PATROL Central

To load the KM on PATROL Central:

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

2. Click Next

3. Select the managed systems where the NetBackup KM is to be loaded, and click Next >. Thewizard will display a list of all available .kml files for the managed systems you selected.

4. Select the NBU_LOAD.kml file for each managed system, click Next > and Finish.

The NetBackup KM will be loaded to the PATROL Central Console Server, and all connected selectedmanaged systems will start discovering the Symantec NetBackup environment. If the automaticdiscovery successfully finds the Symantec NetBackup master/media server installation, the NBU_SETUPinstance will be instantiated.

42Installing the KM

Version 2.8.03


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

5. Load the NBU_LOAD.kml file on each PATROL Central Management Profile where NetBackup KM isto be loaded.

6. Configure the KM.

Configuring the PATROL Agent to Preload the KM

If you want Symantec NetBackup KM for PATROL to operate all the time, without a PATROL Consoleconnection, you'll have to add it to the PATROL Agent configuration variable /AgentSetup/preloadedKMs.

To configure the PATROL Agent to preload the KM:

1. In the Console, right-click the KM main icon > Configuration > Preloading.

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

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

43Installing the KM

Version 2.8.03


Unloading the KMThis section describes the procedures for unloading (not uninstalling) the NetBackup KM from thePATROL Agent, PATROL Console or PATROL Central Console. Read this section if you no longer want touse some parts of the KM; if you want to completely uninstall the KM, refer to the uninstall procedure.

When the KM is unloaded:

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

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

Unloading the KM from the PATROL Agent

To unload the KM from the PATROL Agent:

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

2. Click Remove

3. Restart the PATROL Agent.

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

You can also use the utility wpconfig (on Microsoft W indows) or xpconfig to unload the KM. You will then have toremove NBU_LOAD.kml from the PATROL Agent configuration variable /AgentSetup/preloadedKMs.

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

44Installing the KM

Version 2.8.03


Unloading the KM from the PATROL Console

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

To unload the NetBackup KM completely or partially:

1. Remove the unwanted application classes that starts with NBU_ in the list of loaded applicationclasses as described below:

With the PATROL Console for Unix:

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

Select a NetBackup 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 NetBackup 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 NetBackup 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. Thisallows for a partial unloading of the KM to enable it to run as a reduced installation on some or all of themanaged systems.

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

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

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

3. Select the application classes to be removed that starts with NBU_ for the appropriate managedsystems, click Next> and Finish.

4. Repeat the above steps for each PATROL Central Management Profile where the NetBackup KM is tobe unloaded.

45Installing the KM

Version 2.8.03


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 and executeSymantec NetBackup application programs and file systems. Depending on the operating systems used,several options will be available.

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

a root user

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

a non-root account, such as patrol, configured in Symantec NetBackup application to administer theSymantec NetBackup application.

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

46Installing the KM

Version 2.8.03


an administrator user

a non-administrator account, such as patrol, configured in Symantec NetBackup application toadminister the Symantec NetBackup application.

To configure the KM User Account:1. In the Console, right-click the Symantec NetBackup 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 NBULoginStatus parameter will appear in “suspicious state” afterthe next data collection.

47Installing the KM

Version 2.8.03


Verifying Application DiscoveryTo verify the application discovery:

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

2. Check that the application class instances are actually instantiated. The initial data collection maytake some time depending on the complexity of your environment (up to one hour). If needed,force a data collection by right-clicking the Symantec NetBackup instance > KM Commands >Refresh Parameters.

If Symantec NetBackup master/media server is configured in a clustered environment, you'll have to enable Multi-node Mode monitoring.

Checking the Instance LimitsSymantec NetBackup KM for PATROL automatically sets the number of instances that will be displayed inthe Console for each monitored elements. This configuration, set to offer maximum performance, canhowever be modified to better suit your environment.

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

48Installing the KM

Version 2.8.03


To modify the default configuration

1. In the Console, right-click the KM main icon > Configuration> Instance Limits

Configuring the Default Instance Lim its

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.

49Installing the KM

Version 2.8.03


Checking the Initial SetupTo 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 Symantec NetBackup instance.

2. Check whether the discovered Node Type is correct using the menu Configuration> Node Typefrom the Symantec NetBackup instance.

3. Check the InfoBoxes and Parameters of all the NetBackup KM instances and verify that they areproperly set.

4. Under each container instance, open all detail parameters (text parameters with names in theformat NBU<Object>Details), and check for error messages.

5. Check the new value of NBULoginStatus set after completion of all data collection. If either is notin 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 Symantec NetBackupinstance. A report is displayed, detailing information on the managed system. Check through thereport 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 UserGuide, 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 as atext file or print it.

7. The KM installed on the master server may monitor the same storage, disk pools, disk volumes,robotic libraries & drives which are already monitored through the media servers. This may beunnecessary and can trigger duplicate alerts. You can disable these components on either masterserver or media server by setting their instance limit to 0 (zero), using the menu Configuration>Instance Limits.

Restarting PATROL Agent and PATROL ConsoleRestarting the PATROL Agent and PATROL Console is optional but often a good practice to confirm thatthe NetBackup 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.

50Installing the KM

Version 2.8.03


Integrating the KM

This section provides detailed information about the integration of NetBackup KM into the BMCFramework.

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. The Adapterperiodically synchronizes the performance data collected by these application classes into BMCProactiveNet.

Creating and Importing an Adapter for a BMC PATROL KM

Creating an Adapter for a BMC PATROL KM

1. Open the BMC ProactiveNet Administration Console. The BMC ProactiveNet Administration Consoleis 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 perform theintegration of the ‘targeted KM’ into BMC ProactiveNet.

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

Enter the Integration Service Agent hostname or IP address

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

51Integrating the KM

Version 2.8.03


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. TheAdapter 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 intoBMC ProactiveNet to enable the update of a single KM independently.

Updating an Adapter for a BMC PATROL KM1. Delete the Adapter instance

2. Go through the Add an Adapter wizard to actually delete the monitor types that had been createdbased 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

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


Version 2.8.03


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__NBU_ 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 Absolute InstanceThresholds panel.

Managing Baselines and Key Performance IndicatorsIn order to facilitate the detection of abnormalities on your monitored environment, BMC ProactiveNetcalculates baselines per parameter (metrics or attributes) based on values collected over a specifiedperiod of time to determine a normal operating range. When the collected values for these parametersare 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 a specifiedtime period and establishing a low baseline value (consisting of the 10th percentile of all the values for agiven time period) and a high baseline value (consisting of the 90th percentile of all the values for agiven time period), taking a weighted average of these values over time. A higher weight is given to thelatest data being factored into the baseline average. The accuracy of the baseline improves over time.

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 an


Version 2.8.03


active 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 BMC ProactiveNetAdministration Console. In this KM, some parameters or attributes have been designated as importantindicators of performance (KPIs). We do not recommend that these default settings 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. TheKPI 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 Performance Indicators:

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 that monitortype

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


Version 2.8.03


Monitoring your Environment

Symantec NetBackup KM for PATROL helps ensure the availability, maximum performance, and integrityof your backup servers, thereby protecting associated data sets.

Administering Symantec NetBackupSymantec NetBackup KM for PATROL provides secure server administration menus, which can beexecuted by PATROL Console users, if they have appropriate privileges. They can more especially:

start or stop the master/media server

assign, deny, or resubmit mount requests

bring standalone or robotic drives online or offline.

Starting the Master/Media ServerIn the Console, right-click the Symantec NetBackup instance > KM Commands>Administrationand select Start Master Server or Start Media Server depending on the server that you wish tostart.

Starting the Master/Media Serv er

55Monitoring your Environment

Version 2.8.03


Stopping Master Media ServerIn the Console, right-click the Symantec NetBackup instance > KM Commands and select StopMaster Server or Stop Media Server depending on the server that you wish to stop.

Stopping the Master/Media Serv er

Assigning, Denying, or Resubmitting Mount RequestsWhen a mount request appears, its parameter NBURequestElapsed is immediately set to alert(Warning or Alarm depending on the elapsed time). The mount request can be assigned, denied, or re-submitted using the menus from the mount request instance:

1. In the Console, right-click the Mount Request instance > KM Commands > Administration

2. Select one of the following options:

Assign

Deny

Resubmit

3. Click Yes to confirm your choice.

A similar menu is available at the Mount Requests instance level to perform any of these actions on all mountrequests at once.


Version 2.8.03


Bringing Standalone Drives Online or OfflineTo bring a standalone drive offline or offline:

1. In the Console, right-click the Standalone Drive instance > KM Commands


Online Drive

Offline Drive


Bringing Robotic Drives Online or OfflineTo bring a robotic drive offline or offline:

1. In the Console, right-click the Robotic Library Drive instance > KM Commands


Online Drive

Offline Drive



Version 2.8.03


Configuring the KMThe configuration instructions provided in this section should be followed on all PATROL Agent Systemswhere Symantec NetBackup KM for PATROL is installed.

Before configuring the KM, make sure:

the KM is loaded on the PATROL Console

the NBU_SETUP or Symantec NetBackup 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 Symantec NetBackup instance > KM commands >Configuration > Paths

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

3. In the NetBackup section, verify and possibly modify the Installation and the Log DirectoryPaths

4. In the Binary Paths and Library Paths sections:

From the list, select the paths to be removed

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

5. Click OK.

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


Version 2.8.03


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 Symantec NetBackup instance > KM Commands Configuration> Node Type

2. Select the node type (Master or Media Server)

3. Click OK.

Configuring the Multi-Node Monitoring ModeIf the Symantec NetBackup environment is installed in a cluster using Veritas Cluster Server, VeritasCluster File System or Oracle Solaris Cluster, the NetBackup KM must be installed on all the clusternodes to enable continuous monitoring and avoid single point of failure. To avoid duplicate alerts frommultiple nodes, it is recommended to configure the solution to operate in multi-node monitoring mode.

To configure the multi-node monitoring mode:


Version 2.8.03


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

Configuring the Multi-Node Monitoring Mode

2. Select Multi-node Mode

3. Select the appropriate Clustering Application

4. Indicate the Failover Group Name. Leave this field blank if you previously selected Veritas ClusterFile System. The NetBackup KM will then monitor the entire cluster from the active master system,which is identified by the vxdctl -c mode command. This method requires vxconfigd in enablemode with its clustered state active.

5. Enable remote PATROL Agent Checking to check the monitoring status of the other nodes andclick OK

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

7. Click OK.

Symantec NetBackup will then be monitored through the master or online node. The other nodes, whichare standing by for a failover, will be in passive multi-node mode and only the Symantec NetBackupcomponents will be monitored.

If a managed node is unable to determine the system which should be in A ctive Multi-node Mode, it will change toTemporary Single-node Mode.


Version 2.8.03


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:

1. In the Console, right-click one of the following instances depending on the elements that you wishto monitor:

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

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

Databases > KM Commands Configuration>Databases to filter databases to be monitored

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

Policies > KM Commands > Configuration>Policies to filter policies to be monitored. Policymonitoring is disabled on media servers and in passive multi-node mode.

Policy > KM commands > Configuration > Policy Clients to filter policy clients to bemonitored.

Robotic Libraries > KM Commands > Configuration > Robotic Libraries to filter roboticlibraries to be monitored

Robotic Drive > KM Commands > Configuration>Robotic Drives to filter robotic drives tobe monitored

Standalone Drives > KM Commands > Configuration > Standalone Drives to filterstandalone drives to be monitored

Volume Pools > KM Commands > Configuration>Volume Pools to filter robotic volumepools to be monitored

Storages > KM Commands > Configuration > Storages to filter storages to be monitored

Disk Pool > KM Commands > Configuration > Disk Pools to filter disk pools to bemonitored

Disk Volume > KM Commands > Configuration > Disk Volumes to filter disk volumes to bemonitored

These menus are also available from the child instances.


Version 2.8.03


Client Configuration dialog

The [ALL] entry ensures that all the elements found during PATROL discovery are instantiated andmonitored.

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


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 leav ing 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 PeriodsBy default, Symantec NetBackup KM for PATROL monitors all mount requests for 1day and all scheduledjobs that completed successfully for 1 day and any other scheduled job 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.03


Configuring the Jobs Monitoring Period

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

Job Filter Configuration dialog

2. Indicate how long the jobs in OK, Suspicious, and Failure status will be monitored. If you:

decrease the monitoring period, older jobs will be destroyed on the next data collection cycle

increase the monitoring period, you'll have to force a full data collection to ensure all jobs areinstantiated. To force data collection, right-click the Jobs instance > KM Commands > ForceFull Collection


Version 2.8.03


3. Select Keep Monitoring Active Jobs Indefinitely if you want to endlessly monitor active jobs

4. Select Ignore Inactive Jobs initially if you want the inactive jobs not to be created in the initialdiscovery cycle. Initially discovering and monitoring inactive jobs may impact the performance of theapplication.

5. Select Ignore Alerting for Child Jobs if you do not want to be notified when a job failure occurson child jobs.

6. Click OK.

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

Mount Requests

Mount Request Filter Configuration Dialog

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

3. Click OK.


Version 2.8.03


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. It canbe configured as follows:

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

Daem on Status Configuration dialog

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 a warningwhen the Growing state of the Daemon instance lasts more than 600 minutes:

From the State list, select 7 (Growing)


Version 2.8.03


From the Condition list, select >

In the Minutes field, enter 600

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 Not Running state of the Daemon instance lasts more than 30 minutes:

From the State list, select 9 (Not Running)

From the Condition list, select >

In the Minutes field, enter 30

6. Click Update.

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

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


Version 2.8.03


Configuring the Node StatusNetBackup KM allows you to choose which daemons will be used to determine the node status:

1. In the Console, right-click the Symantec NetBackup instance > KM Commands >Configuration > Node Status.

Configuring Node Status

2. In the Monitored daemons list, select the daemons that won't be used to determine the nodestatus

3. In the Daemon field, list the daemons to be used to determine the node status. The Daemon listmust be comma-delimited.

4. To use default settings, type [default] in the Daemon field

5. Click Update.

The NUBNodeStatus parameter will then be set to:

Suspicious if any command run by the NetBackup KM returns a master/media server errormessage

Failure if any configured daemon is not running. Several recovery actions will then be initiated.


Version 2.8.03


Configuring Mount Requests Date/Time FormatThe NetBackup KM uses Symantec NetBackup commands to determine the date and time of each mountrequest (used for calculating the elapsed time since the mount request was issued). Depending on yourlocal system time zone and date/time format, the application may return a different date/time format.

To customize the mount request date/time format:

1. In the Console, right-click the Mount Requests instance > KM Commands > Configuration >Mount Request Date/Time Format

Mount Request Date/Tim e Form at 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 mount requests.

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


Version 2.8.03


Configuring the Log FilterA log error filter can be configured to specify the regular expressions that will generate a warning or analarm. Each time the KM will find these expressions in a log file or in NBULogText, the error messagewill be written to the NBULogAlarmText or NBULogWarningText parameter. By default, the defaultlog filter is configured for the daily Symantec Netbackup messages file and the system log file. If youenabled additional log files for monitoring, you will have to customize the log filter by adding appropriateexpressions for those log files.

For more information about the possible error messages, refer to the Symantec NetBackup System Administrator’sGuide and the Symantec NetBackup Troubleshooting Guide.

To configure the log error filter:

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

Log Filter Configuration dialog


Version 2.8.03


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). You canalso limit the exclusion to a particular expression already listed by using standard wildcard syntax,such as “skipping . otlsol06”.

Select Exclude

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 tothe parent or container instance level. To revert to the shipped default settings (as shown above), access this dialogfrom the log container instance. From this level you will also have the option to reset the configuration of anymodified child instances.

Configuring the Log Scan LimitThe NetBackup 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 (NBULogCollector),the KM, and the PATROL Agent.

To customize the log scan limit:


Version 2.8.03


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

Custom izing the Log Scan Lim it

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

3. Click OK.

Configuring Jobs Exit Status FilterThe NBUJobState parameter is set according to the completion state and the exit status reported bySymantec NetBackup. or completed jobs, it is set to:

completed if the job completes with exit status 0 (zero)

Aborted if the exit status code is 150 (terminated by administrator)

Failed if the exit status is included in the Failure filter

Error if the exit status is included in the Erroneous filter

By default, all other exit status codes are set to Failed. This settings can be modified by moving orremoving the keyword [ALL] in the Job Exit Status Filter.

To configure the exit status filter:


Version 2.8.03


1. In the Console, right-click the Jobs instance > KM Commands > Configuration > Jobs ExitStatus

Configuring the Job Ex it Status

2. Select the exit status codes from the current filters, which should be removed, if any

3. Enter exit status code to be added to the erroneous or failure filter, which will set NBUJobState toError or Failed respectively. Multiple comma (,) delimited codes or a range using a hyphen (-) canbe entered at the same time.

4. Click Update.5. Once all required changes are made click Close to load the filters.

These filters will apply to all jobs from the next job collection cycle (NBUJobCollector).

Configuring Policy Backup RestrictionNetBackup KM can be configured to trigger a warning when a backup is started during a specific periodof time:

1. In the Console, right-click:

the Policies instance > KM Commands > Configuration> Policies Backup Restriction toapply this customization to all policies

a Policy instance > KM Commands > Configuration> Policy Backup Restriction to applythis customization to a specific policy


Version 2.8.03


Policy Backup Restriction Window dialog

2. Select Enabled

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

4. Click OK.

Configuring Alert AcknowledgementBy default, alerts will automatically be acknowledged unless you modified the settings to allow manualacknowledgement.

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

Configuring Logs Alert Acknowledgement

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


Version 2.8.03


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

Configuring Log A lert A cknowledgem ent

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

3. Click OK.

Configuring Jobs Alert Acknowledgement

By default, the alerts triggered on the NBUJobStatus parameter for the completed jobs are notacknowledged. If you want these alerts to be automatically acknowledged, you'll have to configure thejob alert acknowledgement as follows:


Version 2.8.03


1. In the Console, right-click the Jobs instance > KM Commands > Configuration > Job AlertAcknowledgement

Configuring Job A lert A cknowledgem ent

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

3. Click OK.

Refreshing ParametersThis section describes how to manually refresh parameters without waiting for an automatic pollingcycle.

Forcing All Discoveries

To force all discoveries, right-click the Symantec NetBackup instance and select:

Refresh Process Cache to refresh the PATROL Agent process cache

Force Discovery.

The discovery will then be forced on all the KMs loaded on the PATROL Agent and on all the KMapplications classes.

Forcing All Data Collectors

To force all data collectors, right-click the Symantec NetBackup instance and select:

Refresh Process Cache to refresh the PATROL Agent process cache

Refresh parameters to force all data collectors at the same time.

The NetBackup KM data collectors and all the data collectors defined under the application classesloaded on the PATROL Agent will then be refreshed.


Version 2.8.03


Forcing Selected Data Collectors

This option is only available from a PATROL Developer Console.

1. Right-click the Symantec NetBackup instance and select Refresh Process Cache to refresh thePATROL Agent process cache .

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

With the PA TROL Console for MS Windows

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

Select the required data collector.

Click Update.

With the PA TROL Console for Unix

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


Click Options > Update.

With the PA TROL Central Operator Console

Right-click on the NetBackup KM instance and choose Properties

Click on the Parameter List tab


Click Update.

Forcing Full Data Collection for Jobs

By default, the NBUJobCollector only searches for new jobs started since the last collection cycle.However, it can be forced to search for all jobs within the monitored time period during the nextcollection cycle.

To force full data collection for jobs, right-click the Jobs instance and select Force Full Collection.

If the Jobs container instance is not instantiated, this menu command cannot be accessed. The PATROL Agent needsto be restarted to force a full data collection for jobs.

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


Version 2.8.03


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

Enabling the Debug Mode

1. In the Console, right-click the Symantec NetBackup instance > KM Commands > Configuration> Debug. The NetBackup KM Debug Configuration dialog will be displayed:

Enabling the Debug Mode


Version 2.8.03


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

Object Debug Switch Application Classes Collector Parameters

Server NBU_SERVER NBUCreateDistributionNBUUpdateAgent

Database NBU_DATABASE_CONTAINERNBU_DATABASE

NBUDatabaseCollector

Log NBU_LOG_CONTAINERNBU_LOG

NBULogCollector

Client NBU_CLIENT_CONTAINERNBU_CLIENT

NBUClientCollector

Robotic Library/Drive NBU_LIBRARY_CONTAINERNBU_LIBRARYNBU_LDEVICENBU_DEVICE_CONTAINERNBU_DEVICE

NBULibraryCollectorNBUDriveCollector

Daemon NBU_DAEMON_CONTAINERNBU_DAEMON

NBUDaemonCollector

Volume Pool NBU_POOL_CONTAINER NBUPoolCollector

Backup NBU_POLICY_CONTAINERNBU_POLICYNBU_PCLIENTNBU_JOB_CONTAINERNBU_JOBNBU_MOUNT_CONTAINERNBU_MOUNT

NBUPolicyCollectorNBUJobCollectorNBURequestCollector

Disk Storage / Pool / Volume NBU_STORAGE_CONTAINERNBU_STORAGENBU_DPOOLNBU_DVOLUME

NBUStorageCollector

3. Set the Debug Options:

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

In the Debug Path field, indicate where the debug file will be stored (by default:<PATROL_HOME>/lib/NBU/debug on Unix systems; %PATROL_HOME%\lib\NBU\debug onMicrosoft Windows systems). The debug folder must have at least 10MB of available disk spaceand read, write and execute permissions for both PATROL Agent user and the NetBackup 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 NBU DebugOutput window. Before selecting this option, make sure the PATROL Console is connected to thePATROL Agent.

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

4. Click OK first to start NetBackup 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 end time is reached. A tar/zip file


Version 2.8.03


is then automatically created under <PATROL_HOME>/lib/NBU/ and can be sent to the BMC Support forhelp. It is also recommended to check the SOW or NBU.log file, stored in <PATROL_HOME>/log, for anyerror.

To manually stop debugging:

1. Access the NetBackup 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 NBU 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:

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

nbu_km_debug_<date>_<time>.zip file (Windows systems). This file could later be foundin %PATROL_HOME%\lib\NBU\

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 f iles and sub-directoriesunder $PATROL_HOME/lib/NBU/ (on Unix ) or %PATROL_HOME%\lib\NBU\ (on Microsoft W indows).

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


Acknowledging Alerts

By default, alerts are acknowledged automatically. If you modified the alert acknowledgement defaultsettings, you'll have to manually acknowledge alerts.

Manually Acknowledging Log Alerts

When an error is detected in a monitored log file, it will either appear in NBULogAlarmText orNBULogWarningText and will respectively trigger an Alarm or a Warning on NBULogAlarmCount orNBULogWarningCount.

To acknowledge 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 NBULogWarningTextparameter

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

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

Manually Acknowledging Job Alerts

For a particular job instance, if the NBUJobStatus has a value of 1=Suspicious or 2=Failure, it will beset to alert with a status of Warning or Alarm respectively. These alerts can be acknowledged using themenu Acknowledgement > Alert from the relevant job instance.

To acknowledge job alerts:

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

2. Select:

Acknowledgement > Warnings to view and acknowledge alerts for all jobs with a status ofWarning.

Acknowledgement > Alarms to view and acknowledge alerts for all jobs with a status ofAlarm.

Acknowledgement > All to view and acknowledge all job alerts (Warnings and Alarms) atonce


Version 2.8.03


Generating ReportsFollowing is a list of reports available in Symantec NetBackup KM for PATROL.

Daemons > Reports > Daemon List - lists all running Symantec NetBackup daemons

Databases > Reports > Database Backup Information - reports information about the lastcatalog database backup

Logs > Reports > Messages List - reports all messages logged in the past 24 hours

Mount Requests > Reports > Pending Requests - reports a list of all mount requests

<Policy instance> > Reports > Policy Schedule - displays the schedule for the selected policyinstance

Robotic Libraries > Reports > Drive Cleaning Statistics or Standalone Drives > Reports >Drive Cleaning Statistics - reports the drive cleaning statistics on the current master/media server

<Robotic Library instance> > Reports > Robotic Library Contents - reports the contents ofthe selected robotic library instance

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

Volume Pools > Reports > Available Media - reports all available media across all volume pools.

Reports can be saved as a task window by clicking Save As Task. You could then save them as a textfile or print them.

Reference Guide

Introduction

This chapter provides statistical information about resources, operating status, and performancesmanaged by Symantec NetBackup 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.

82Reference Guide

Version 2.8.03


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

NBU_SERVER

NBU_CLIENT_CONTAINER

NBU_CLIENT

NBU_DAEMON_CONTAINER

NBU_DAEMON

NBU_DATABASE_CONTAINER

NBU_DATABASE

NBU_LOG_CONTAINER

NBU_LOG

NBU_POLICY_CONTAINER

NBU_POLICY

NBU_PCLIENT

NBU_JOB_CONTAINER

NBU_JOB

NBU_MOUNT_CONTAINER

NBU_MOUNT

NBU_LIBRARY_CONTAINER

NBU_LIBRARY

NBU_LDEVICE

NBU_DEVICE_CONTAINER

NBU_DEVICE

NBU_POOL_CONTAINER

NBU_POOL

NBU_STORAGE_CONTAINER

NBU_STORAGE

NBU_DPOOL

NBU_DVOLUME

83Reference Guide

Version 2.8.03


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 process arerespectively identified by the following icons:

Baselining

KPI

NBU_CLIENT_CONTAINER

Icon

Parameters

Name Description Units DefaultAlertConditions

BPPM Type

NBUClientCollectorExecTime

Inactive standard parameter monitorsthe collector execution time. Toactivate this parameter, use the PSLbelow, and restart the PATROLAgent:

%PSL pconfig("REPLACE", "/Runtime/NBU/NBUClientCollectorExecTime", 1);

When activated it will run everyminute and trigger a warning whenthe collector runs for more than theobserved maximum time. Thismaximum time can be overridden by apreset value (example: 3600seconds), using the PSL below:

%PSL pconfig("REPLACE", "/Runtime/NBU/NBUClientCollectorWarn", 3600);

seconds Warning:> presetvalue orobservedmaximum(default)

CollectionStatus

NBUClientDetails Set by NBUClientCollector. Displays alldata returned to the standard out fromcommands executed by the datacollector.

n/a n/a n/a

InfoBox

84Reference Guide

Version 2.8.03


Name Description

Collector Last End Date & time when the last data collection cycle completed.

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

Collector Name Name of the data collector that sets variables and parameters under this applicationinstance.

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

Function Description

Configuration > Clients Accesses the dialog for specifying which clients are to be monitored by the NBU KM. Bydefault, all clients configured on the master server are monitored.

Configuration > ClientsStatus

Accesses the global configuration for determining the client status for monitored clientinstances.By default, following NBUClientState to NBUClientStatus mapping rule is used:

85Reference Guide

Version 2.8.03


NBU_CLIENT

Icon

Parameters


BPPM Type

NBUClientState Set by NBUClientCollector. Displays thestate of the client as reported in thecommand executed by the datacollector.

0 = Running1 =ConnectionRefused2 = AccessDenied3 = ClientDown-1 =Unknown

None Availability

NBUClientStatus Set by NBUClientCollector. Monitors thestatus of the client. This status isdetermined by the client status mappingrule defined in the KM command Configuration > Client(s) Status. Ifthis status parameter changes towarning or alarm state, the recoveryaction will trigger an event and annotatethe last data point.

0 = OK1 =Suspicious2 = Failure

Warning = 1Alarm = 2

Availability

NBUClientSummary Set by NBUClientCollector. Summarizesthe client information as reported incommands executed by the datacollector.

n/a None n/a

InfoBox

Name Description

Application Name of the application installed on the client that responds to the connection request.






Description Description of the Symantec NetBackup client.

86Reference Guide

Version 2.8.03


Hardware Hardware platform of the client.

Installation Path Installation path of the application on the client.

Name Name of the Symantec NetBackup client.

Operating System Operating system of the client.

Status Status of client connectivity from the current node.

Version Version number of the application installed on the client.

Menu Commands


Configuration > Client Sets the client instance to be enabled or disabled for monitoring by the NBU KM.

Configuration > ClientStatus

Accesses the individual configuration for determining client status for the selected clientinstance. By default, the global NBUClientState to NBUClientStatus mapping rule isused, as configured at the container level.

NBU_DAEMON_CONTAINER

Icon

Parameters


BPPM Type

NBUDaemonDetails Set by NBUDaemonCollector. Displays alldata returned to the standard out fromcommands executed by the datacollector.

n/a n/a n/a

NBUDaemonCollectorExecTime


%PSL pconfig("REPLACE", "/Runtime/NBU/NBUDaemonCollectorExecTime", 1);

seconds Warning> presetvalue orobservedmaximum(default)

Collection Status

87Reference Guide

Version 2.8.03



%PSL pconfig("REPLACE", "/Runtime/NBU/NBUDaemonCollectorWarn", 3600);

88Reference Guide

Version 2.8.03


InfoBox

Name Description






Menu Commands


Reports > Daemon List Lists all running Symantec NetBackup daemons.

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

Configuration > DaemonsStatus

Accesses the global configuration for determining the daemon status for monitoreddaemon instances.By default the following NBUDaemonState to NBUDaemonStatus mapping rule isused:

89Reference Guide

Version 2.8.03


NBU_DAEMON

Icon

Parameters


BPPM Type

NBUDaemonCPUDuration Set by NBUDaemonCollector. Displaysthe CPU seconds consumed by thedaemon.

seconds None Statistics

NBUDaemonCPUUtilization*

Set by NBUDaemonCollector. Displaysthe percentage of CPU used by thedaemon.

% None Statistics

NBUDaemonMemorySize*

Set by NBUDaemonCollector. Displaysthe core image size of the daemon in thevirtual memory.

KB None Statistics

NBUDaemonProcessCount

Set by NBUDaemonCollector. Displaysthe number of daemon processes/threads found.

processes None Statistics

NBUDaemonState Set by NBUDaemonCollector. Displaysthe state of the daemon as reported inthe command executed by the datacollector.

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

None Availability

90Reference Guide

Version 2.8.03


NBUDaemonStatus Set by NBUDaemonCollector. Monitorsthe status of the daemon. This status isdetermined by the daemon statusmapping rule defined in the KMcommand Configuration>Daemon(s)Status. If this status parameterchanges to warning or alarm state, therecovery action will trigger an event andannotate the last data point.



Availability

NBUDaemonSummary Set by NBUDaemonCollector.Summarizes the daemon information asreported by commands executed by thedata collector.

n/a n/a n/a

For detailed information about B a se lining and KP I, see Managing Baselines and Key Performance Indicators.

* Parameters marked with an asterisk are used by default when v isualizing the corresponding monitor instance in BPPM.

InfoBox

Name Description






Command Command that started the daemon.

Description Description of the Symantec NetBackup daemon.

Name Name of the Symantec NetBackup daemon.

Owner Owner of the daemon.

PID Process ID of the daemon.

PPID Parent process ID of the daemon.

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

Menu Commands


Configuration > Daemon Sets the daemon instance to be enabled or disabled for monitoring by the NBU KM.

Configuration > DaemonStatus

Accesses the individual configuration for determining daemon status for the selected thedaemon instance. By default, the global NBUDaemonState to NBUDaemonStatusmapping rule is used, as configured at the container level.

91Reference Guide

Version 2.8.03


NBU_DATABASE_CONTAINER

Icon

Parameters


BPPM Type

NBUDatabaseBackupElapse

d*

Set by NBUDatabaseCollector. Displaysthe elapsed time since the lastsuccessful database backup. Thespecified alarm ranges can be enabled toallow the output of the parameter to beactively monitored. Then, if thisparameter changes to warning or alarmstate, the recovery action will trigger anevent.

hours Alarm: -1Warning: 24and over

Statistics

NBUDatabaseCollectorExecTime


%PSL pconfig("REPLACE", "/Runtime/NBU/NBUDatabaseCollectorExecTime",1);


%PSL pconfig("REPLACE", "/Runtime/NBU/NBUDatabaseCollectorWarn",3600);

seconds Warning:> presetvalue orobservedmaximum(default)

Collection Status

NBUDatabaseDetails Displays all data returned to thestandard out from commands executedby the data collector.

n/a n/a n/a

NBUDatabaseStatus Set by NBUDatabaseCollector. Monitorsthe status of the NetBackup database(NBDB). If this status parameterchanges to warning or alarm state, therecovery action will trigger an event andannotate the last data point.



availability


92Reference Guide

Version 2.8.03



InfoBox

Name Description






Last Backup Job ID Identifier of the last catalog database backup job.

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

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

Menu Commands


Reports > Database BackupInformation

Reports information about the last catalog database backup.

Configuration > Database Accesses the dialog for specifying which catalog databases are to be monitored by theNBU KM.By default, following database paths are monitored. These database paths are relative toSymantec NetBackup installation directory (for example /usr/openv on HP-UX).

NBU_DATABASE

Icon

93Reference Guide

Version 2.8.03


Parameters


BPPM Type

NBUDatabaseFSSpaceUsed

Percent*

Set by NBUDatabaseCollector. Monitorsthe percentage of space used by the filesystem where the database resides. Ifthis parameter changes to warning oralarm state, the recovery action willtrigger an event.

% Warning: 95-98Alarm: 98-100

Statistics

NBUDatabaseSpaceAvailable

Set by NBUDatabaseCollector. Monitorsthe amount of assigned space remainingavailable for use by the catalogdatabase. If this parameter changes towarning or alarm state, the recoveryaction will trigger an event.

MB Warning: 2-5Alarm: 0-2

Availability

NBUDatabaseSpaceGrowthRate

Set by NBUDatabaseCollector. Displaysthe growth rate of the space used bythe catalog database.

MB/s None Statistics

NBUDatabaseSpaceUsed Set by NBUDatabaseCollector. Displaysthe amount of assigned space used bythe catalog database.

MB None Statistics

NBUDatabaseSpaceUsedPe

rcent*

Set by NBUDatabaseCollector. Monitorsthe percentage of assigned space usedby the catalog database. If thisparameter changes to warning or alarmstate, the recovery action will trigger anevent.


Statistics

NBUDatabaseSummary Set by NBUDatabaseCollector.Summarizes the database information asreported by commands executed by thedata collector.

n/a n/a n/a



InfoBox

Name Description






Description Description of the Symantec NetBackup catalog database.

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

94Reference Guide

Version 2.8.03


Name Name of the Symantec NetBackup catalog database.

Path Full file path of the catalog database.

Menu Commands


Configuration > Database Sets the database instance to be enabled or disabled for monitoring by the NBU KM.

95Reference Guide

Version 2.8.03


NBU_DEVICE

Icon

Parameters


BPPM Type

NBUDriveState Set by NBUDriveCollector. Displays thestate of the standalone drive. This isdetermined from the standalone drivecontrol information.

0 = Idle1 =Mounted2 = In Use3 = Pending4 = Down-1 =Unknown

None Availability

NBUDriveStatus Set by NBUDriveCollector. Monitors thestatus of the standalone drive. Thisstatus is determined by the standalonedrive status mapping rule defined in theKM command Configuration>Standalone Drive(s) Status.

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



Availability

NBUDriveSummary Set by NBUDriveCollector. Summarizesthe standalone drive information asreported by commands executed by thedata collector.

n/a n/a n/a

NBUDriveThroughput* Set by NBUDriveCollector. Displays thethroughput of the standalone driveduring the last backup activity.




InfoBox

Name Description



96Reference Guide

Version 2.8.03





Control Control mode for the drive.

Description Description of the drive.

Device Host Name of the remote host where the drive is connected.

Drive Index Unique index assigned to the drive.

Media ID Media identifier of the media mounted on this drive.

Name Name of the standalone drive.

Path Device path of the drive.

Request ID ID of the pending request, if this drive is assigned to a pending request .

Serial Number Serial number of the drive.

Status Status of the drive as determined by the NBU KM.

Type Media type used in the drive.

User User ID of the person or application whose request is currently assigned to this drive.

97Reference Guide

Version 2.8.03


Menu Commands


Reports > Drive CleaningStatistics

Reports the drive cleaning statistics on the current master/media server.

Configuration > StandaloneDrives

Accesses the dialog for specifying which standalone drives are to be monitored by the NBUKM.By default, all local and remote standalone drives are monitored for a master server and alllocal standalone drives are monitored for a media server.

Configuration > StandaloneDrives Status

Accesses the global configuration for determining the status for monitored standalonedrive instances.By default, the following NBUDriveState to NBUDriveStatus mapping rule is used:

NBU_DEVICE_CONTAINER

Icon

Parameters


BPPM Type

NBUDriveCollectorExecTime Inactive standard parameter monitorsthe collector execution time. Toactivate this parameter, use the PSLbelow, and restart the PATROLAgent:

%PSL pconfig("REPLACE", "/Runtime/NBU/NBUDriveCollectorExecTime", 1);


seconds Warning > presetvalue orobservedmaximum(default)

Collection Status

98Reference Guide

Version 2.8.03


%PSL pconfig("REPLACE", "/Runtime/NBU/NBUDriveCollectorWarn", 3600);

NBUDriveDetails Set by NBUDriveCollector. Displays alldata returned to the standard out fromcommands executed by the datacollector.

n/a n/a n/a

InfoBox

Name Description






99Reference Guide

Version 2.8.03


Menu Commands




Configuration > StandaloneDrives

Accesses the dialog for specifying which standalone drives are to be monitored by the NBUKM. By default, all local and remote standalone drives are monitored for a master serverand all local standalone drives are monitored for a media server.

Configuration > StandaloneDrives Status

Accesses the global configuration for determining the status for monitored standalonedrive instances.By default, the following NBUDriveState to NBUDriveStatus mapping rule is used:

NBU_DPOOL

Icon

Parameters


BPPM Type

NBUDPoolSummary Set by NBUStorageCollector.Summarizes the disk pool information asreported by commands executed by thedata collector.

n/a n/a n/a

NBUDPoolUpDownState Set by NBUStorageCollector. Displaysthe up/down state of the disk pool.

0 = Down1 = Up-1 =Unknown

None Availability

NBUDPoolUpDownStatus Set by NBUStorageCollector. Monitorsthe up/down status of the disk pool.This status is determined by the diskpool status mapping rule defined in theKM command Configuration>Disk Pool(s)Status.



Availability

100Reference Guide

Version 2.8.03



NBUDPoolVolumeCount* Set by NBUStorageCollector. Displaysthe number of volumes in the disk pool.

count None Statistics



InfoBox

Name Description






Description Description of the disk pool.

High Watermark High watermark for the volumes in disk pool.

Low Watermark Low watermark for the volumes in disk pool.

Name Name of the disk pool

Raw Size Raw disk size of the disk pool.

Storage Server Type Type of the storage server.

Storage Server Name of the host where the disk pool is attached to.

Up/Down State Up/down status of the disk pool (1 – Up, 0 – Down).

Usable Size Usable disk size of the disk pool.

101Reference Guide

Version 2.8.03


Menu Commands


Configuration > Disk Pool Accesses the configuration for monitoring the selected disk pool instance.This dialog allows the selected disk pool instance to be enabled or disabled for monitoringby the NBU KM.

Configuration > Disk PoolUp/Down Status

Accesses the individual configuration for determining disk pool up/down status for theselected disk pool instance.By default, the global NBUDPoolUpDownState to NBUDPoolUpDownStatus mappingrule is used, as configured at the container level.

Configuration > DiskVolumes

Accesses the dialog for specifying which disk volumes of the selected disk pool are to bemonitored by the NBU KM. By default, all disk volumes of the selected disk pool aremonitored.

Configuration > DiskVolumes Up/Down Status

Accesses the configuration for determining up/down status for the monitored disk volumeinstances on the selected disk pool instance. By default, the global NBUDVolumeUpDownState to NBUDVolumeUpDownStatus mapping rule is used,as configured at the container level.

NBU_DVOLUME

Icon

Parameters


BPPM Type

NBUDVolumeReadSt

reamCount*

Set by NBUStorageCollector. Displays thenumber of current read steams for the diskvolume


NBUDVolumeSpaceAvailable*

Set by NBUStorageCollector. Monitors theavailable disk volume space for the backup datato use.

If this parameter changes to warning or alarmstate, the recovery action will trigger an event.

GB Warning:between 0and ≤ 1Alarm:between 1and 0

Availability

NBUDVolumeSpaceGrowthRate

Set by NBUStorageCollector. Displays thegrowth rate of the disk space used by thebackup data in this disk volume.

GB/s None Statistics

NBUDVolumeSpaceU

sed*

Set by NBUStorageCollector. Displays the diskspace occupied by the backup data in this diskvolume.

% None Statistics

NBUDVolumeSpaceU

sedPercent

Set by NBUStorageCollector. Monitors thepercentage of occupied disk space against thecapacity of this disk volume.


Statistics

102Reference Guide

Version 2.8.03


If this parameter changes to warning or alarmstate, the recovery action will trigger an event.

NBUDVolumeSummary

Set by NBUStorageCollector. Summarizes thedisk volume information as reported bycommands executed by the data collector.

n/a None n/a

NBUDVolumeUpDownState

Set by NBUStorageCollector. Displays the up/down state of the disk volume.


None Availability

NBUDVolumeUpDownStatus

Set by NBUStorageCollector. Monitors the up/down status of the disk volume. This status isdetermined by the disk volume status mappingrule defined in the KM commandConfiguration>Disk Volume(s) Status.

If this status parameter changes to warning oralarm state, the recovery action will trigger anevent and annotate the last data point.



Availability

NBUDVolumeWriteSt

reamCount*

Set by NBUStorageCollector. Displays thenumber of current write steams for the diskvolume




InfoBox

Name Description



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



Description Description of the disk volume.

Disk Media ID Media ID of the disk.

Disk Pool Name Name of the disk pool the volume belongs to.

Disk Type Type of the disk.

Free Space Free disk space in the volume.

Name Name of the disk volume.

Number of ReadMounts

Number of read mounts of the disk volume.

Number of WriteMounts

Number of write mounts of the disk volume.

Storage Server Name of the host where the disk volume is attached to.

103Reference Guide

Version 2.8.03


Total Capacity Total disk capacity of the disk volume.

Up/Down State Up/down status of the disk volume (1 – Up, 0 – Down).

Used Percent Percentage of used disk space.

Menu Commands


Configuration > DiskVolume

Sets the disk volume instance to be enabled or disabled for monitoring by the NBU KM.

Configuration > DiskVolume Up/DownStatus

Accesses the individual configuration for determining disk volume up/down status for the selecteddisk volume instance.By default, the global NBUDVolumeUpDownState to NBUDVolumeUpDownStatus mappingrule is used, as configured at the container level.

NBU_JOB_CONTAINER

Icon

Parameters


BPPM Type

NBUJobActiveBackupCount

*

Set by NBUJobCollector. Displays thenumber of active backup jobs currentlydiscovered and monitored.


NBUJobActiveBackupReduction

Set by NBUJobCollector. Displays thereduction in number of active backupjobs since the last collection cycle.


NBUJobActiveCount* Set by NBUJobCollector. Displays thenumber of active jobs currentlydiscovered and monitored.


NBUJobActiveNonBackupCo

unt*

Set by NBUJobCollector. Displays thenumber of active non-backup jobscurrently discovered and monitored.


NBUJobCollectorExecTime Inactive standard parameter monitorsthe collector execution time. Toactivate this parameter, use the PSLbelow, and restart the PATROLAgent:

%PSL pconfig("REPLACE", "/Runtime/NBU/NBUJobCollectorExecTime", 1);


Collection Status

104Reference Guide

Version 2.8.03



%PSL pconfig("REPLACE", "/Runtime/NBU/NBUJobCollectorWarn", 3600);

NBUJobDetails Set by NBUJobCollector. Displays alldata returned to the standard out fromcommands executed by the datacollector.

n/a n/a n/a

NBUJobQueuedBackupCount

Set by NBUJobCollector. Displays thenumber of backup jobs in "Queued"state.Units: count


NBUJobQueuedBackupReduction

Set by NBUJobCollector. Displays thereduction in number of queued backupjobs since the last collection cycle.




InfoBox

Name Description






Menu Commands


Force Full Collection Allows the user to force the data collector for jobs to perform a full discovery during thenext collection cycle.

Acknowledgement > Warnings

Allows acknowledgement of warning alerts occurring on any monitored job instance.This dialog allows acknowledgement of any job in a "suspicious" state (which sets theparameter NBUJobStatus to Warning).

Acknowledgement > Alarms Allows acknowledgement of alarms occurring on any monitored job instance.This dialog allows acknowledgement of any job in a "failure" state (which sets theparameter NBUJobStatus to Alarm).

Acknowledgement > All Allows acknowledgement of all warnings and alarms occurring on any monitored jobinstance.

105Reference Guide

Version 2.8.03


This dialog allows acknowledgement of any job in a "suspicious" or "failure" state (whichsets the parameter NBUJobStatus to Warning or Alarm, respectively.

Configuration > Jobs Accesses the dialog for specifying which jobs are to be monitored by the NBU KM.By default, all scheduled jobs on the master server are monitored according to thefollowing conditions:

The age of a job is calculated from the job start time. The status of a job is determined bythe state of the job (from the parameter NBUJobState) and the job status mapping rule,described below.

Configuration > Jobs ExitStatus Filter

Accesses the configuration for erroneous and failure exit status codes for all backup andrestore jobs. This filter is used for setting the parameter NBUJobState to "6=Error" and10=Failed respectively, when a backup or restore job returns a non-zero exit status. Theexit status codes are mapped to parameter NBUJobState as shown below:

The default filter includes [ALL] in the failure filter and exit status code "1" in the erroneousfilter. [ALL] is a keyword used for deciding the state for all other exit status codes notlisted in the filters.

Type [default] to reset the filters to shipped default configuration.

Configuration > Jobs Status Accesses the configuration for determining the status for all monitored job instances.By default, the following NBUJobState to NBUJobStatus mapping rule is used:

Configuration > Jobs AlertAcknowledgement

Accesses the global configuration of the method of acknowledgement for alerts onmonitored job instances.By default, the job alerts are manually acknowledged. Using this menu you can change thisso the job collector automatically acknowledges previous job alerts (warnings or alarms)when it detects new errors.

106Reference Guide

Version 2.8.03


NBU_JOB

Icon

Parameters

Jobs Monitoring is disabled on media servers and in passive multi-node mode.


BPPM Type

NBUJobDuration Set by NBUJobCollector. Displays theduration of the job from the start.


NBUJobFileCount Set by NBUJobCollector. Displays thenumber of files backed up for this job.


NBUJobSize Set by NBUJobCollector. Displays theamount of data backed up for the job.

MB None Statistics

NBUJobState Set by NBUJobCollector. Displays thestate of the job. This is determinedusing the job completion state, job exitstatus code, last job operation, and theerroneous exit status filter.

The erroneous exit status filter can becustomized using the KM menu Configuration>Jobs Erroneous ExitStatus. If the exit status code isincluded in the erroneous exit statusfilter, it will be set to Errors.

0 =Completed1 = Queued2 =Mounting3 = InProgress4 = InProgress/Error5 =Requeued6 = Error7 = Aborted8 =Suspended9 =Incomplete10 = Failed-1 =Unknown

None Availability

NBUJobStatus Set by NBUJobCollector. Monitors thestatus of the job. This status isdetermined by the job status mappingrule defined in the KM command Configuration>Jobs Status.




Availability

107Reference Guide

Version 2.8.03


NBUJobSummary Set by NBUJobCollector. Summarizes thejob information as reported bycommands executed by the datacollector.

n/a n/a n/a

NBUJobText Set by NBUJobCollector. Displays allreported messages related to this job.

n/a n/a n/a

NBUJobThroughput* Set by NBUJobCollector. Displays thethroughput of this job.




InfoBox

Name Description

Attempt Number of attempts of the job.

Client Host name of the policy client associated with the job.






Completion Status Completion status of the job.

Duration Duration of the job.

End Date & time when the job completed.

Exit Status Exit status code of the job.

Files Number of files that have been written for the job.

Job ID Identifier assigned to the job by Symantec NetBackup.

Job PID Process ID of the job.

Last Backup Duration Duration of the last similar successful backup.

Last Backup End Date & time when the last similar successful backup completed.

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

Last Backup Job ID Job ID of the last similar successful backup.

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

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

Media Server Host name of the media server associated with the job.

Operation Last operation performed by the job.

Owner Owner of the job.

108Reference Guide

Version 2.8.03


Percent Completed Estimated percentage of the job that has been completed in comparison with the lastsimilar successful job for the same policy, policy client, and schedule.

Policy Name Name of the policy used by the job.

Policy Type Type of the policy used by the job.

Priority Priority of the job.

Schedule End Schedule end time.

Schedule Start Schedule start time.

Schedule Type Type of the schedule used by the job.

Schedule Name of the schedule used by the job.

Size Amount of data that has been written for the job.

Start Date & time when the job was initiated.

Status Status of the job as determined by the NBU KM.

Storage Unit Name of the storage unit that the job is using.

Subtype Subtype of the schedule used by the job.

Time Remaining Remaining time of the job in comparison with the last similar successful job.

Type Type of the job.

Menu Commands


Acknowledgement > Alert Sets the job instance is in a "suspicious" or "failure" state (which sets the parameter NBUJobStatus to Warning or Alarm, respectively).

109Reference Guide

Version 2.8.03


NBU_LDEVICE

Icon

Parameters


BPPM Type

NBURDriveState Set by NBULibraryCollector. Displays thestate of the robotic drive. This isdetermined from the robotic drivecontrol information.

0 = Idle1 =Mounted2 = In Use3 = Pending4 = Invalid5 = Down6 = Missing-1 =Unknown

None Availability

NBURDriveStatus Set by NBULibraryCollector. Monitors thestatus of the robotic drive. This status isdetermined by the robotic drive statusmapping rule defined in the KMcommand Configuration>RoboticDrive(s) Status.




Availability

NBURDriveSummary Set by NBULibraryCollector. Summarizesthe robotic drive information as reportedby commands executed by the datacollector.

n/a n/a n/a

NBURDriveThroughput* Set by NBULibraryCollector. Displays thethroughput of the robotic drive duringthe last backup activity.




InfoBox

Name Description


110Reference Guide

Version 2.8.03






Control Control mode for the drive.

Description Description of the drive.

Device Host Name of the remote host where the drive is connected.

Drive Index Unique index assigned to the drive.

Media ID Media identifier of the media mounted on this drive.

Name Name of the robotic drive.

Path Device path of the drive.

Request ID ID of the pending request, if this drive is assigned to a pending request .

Robot Drive Number Unique number assigned to the robotic drive within the robotic library.

Robot Number Unique number assigned to the robotic library where the drive is located.

Robot Type Type of the robotic library where the drive is located.

Serial Number Serial number of the drive.

Status Status of the drive as determined by the NBU KM.

Type Media type used in the drive.

User User ID of the person or application whose request is currently assigned to this drive.

Menu Commands


Administration > OnlineDrive

Allows the selected robotic drive to be brought online.

Administration > OfflineDrive

Allows the selected robotic drive to be taken offline.

Configuration > RoboticDrive

Sets the drive instance to be enabled or disabled for monitoring by the NBU KM.

Configuration > RoboticDrive Status

Accesses the individual configuration for determining the drive status for the selectedrobotic drive instance.By default, the NBURDriveState to NBURDriveStatus mapping rule configured at theparent level is used. (Note that if the mapping rule has not been modified for the parentrobotic library, then the default is the global mapping rule configured at the containerlevel.)

111Reference Guide

Version 2.8.03



Icon

Parameters


BPPM Type

NBULibraryCollectorExecTime


%PSL pconfig("REPLACE", "/Runtime/NBU/NBULibraryCollectorExecTime", 1);


%PSL pconfig("REPLACE", "/Runtime/NBU/NBULibraryCollectorWarn", 3600);


Collection Status

NBULibraryDetails Set by NBULibraryCollector. Displays alldata returned to the standard out fromcommands executed by the datacollector.

n/a n/a n/a

InfoBox

Name Description






112Reference Guide

Version 2.8.03


Menu Commands




Configuration > RoboticLibraries

Accesses the dialog for specifying which robotic libraries are to be monitored by the NBUKM.By default, all local and remote robotic libraries are monitored for a master server and alllocal robotic libraries are monitored for a media server.

Configuration > RoboticLibraries Status

Accesses the global configuration for determining the status for monitored robotic libraryinstances.By default, the following NBULibraryState to NBULibraryStatus mapping rule is used:

Configuration > RoboticDrives

Accesses the dialog for specifying which drives of the selected robotic library are to bemonitored by the NBU KM. By default, all robotic drives of the selected robotic library aremonitored.

Configuration > RoboticDrives Status

Accesses the global configuration for determining the status for monitored robotic driveinstances (configured under monitored robotic library instances).By default, the following NBURDriveState to NBURDriveStatus mapping rule is used:

NBU_LIBRARY

Icon

Parameters


BPPM Type

113Reference Guide

Version 2.8.03


NBULibraryMediaAssignedC

ount

Set by NBULibraryCollector. Displays thenumber of assigned media loaded in thisrobotic library. (Assigned media are tapemedia assigned to a non-scratch volumepool.)


NBULibraryMediaAvailableC

ount

Set by NBULibraryCollector. Displays thenumber of media available to use in thisrobotic library. This includes unassignedand scratch media.


NBULibraryMediaAvailableP

ercent*

Set by NBULibraryCollector. Monitors thepercentage of available media againstthe total number of media loaded in thisrobotic library.

If this parameter changes to warning oralarm state, the recovery action willtrigger an event.

% Warning:between 2and 5Alarm: 2 orless

Statistics

NBULibraryMediaCleaningLe

ft

Set by NBULibraryCollector. Monitors thenumber of cleaning left on the cleaningmedia available in this robotic library.


count Warning: 2 orlessAlarm: 0

Statistics

NBULibraryMediaCount Set by NBULibraryCollector. Displays thetotal number of media loaded in thisrobotic library.


NBULibraryMediaScratchCo

unt

Set by NBULibraryCollector. Displays thenumber of scratch media loaded in thisrobotic library. (Scratch media are tapemedia assigned to the scratch volumepool.)


NBULibraryMediaScratchPer

cent*

Set by NBULibraryCollector. Monitors thepercentage of scratch media against thetotal number of media loaded in thisrobotic library.If this parameter changes to warning oralarm state, the recovery action willtrigger an event.

% None Statistics

NBULibraryMediaUnassigne

dCount

Set by NBULibraryCollector. Displays thenumber of unassigned media loaded inthis robotic library.(Unassigned media are tape media notassigned to a volume pool.)


NBULibraryMediaUnassigne

dPercent*

Set by NBULibraryCollector. Monitors thepercentage of unassigned media againstthe total number of media loaded in thisrobotic library.


% None Statistics

NBULibraryState Set by NBULibraryCollector. Displayswhether the inquiry for the roboticlibrary is valid or invalid. It will notperform any remote robotic library testcommand on the media server.

0 = Online1 = Remote2 = Offline3 = Invalid-1 =Unknown

None Availability

114Reference Guide

Version 2.8.03


NBULibraryStatus Set by NBULibraryCollector. Monitors thestatus of the robotic library. This statusis determined by the robotic librarystatus mapping rule defined in the KMcommand Configuration> RoboticLibrary (Libraries) Status.




Availability

NBULibrarySummary Set by NBULibraryCollector. Summarizesthe robotic library information asreported by commands executed by thedata collector.

n/a None n/a

NBULibraryThroughput* Set by NBULibraryCollector. Displays thetotal throughput of each robotic librarydrive during the last backup activitieswithin the last hour.


NBULibraryUpDriveCount Set by NBULibraryCollector. Displays thenumber up / online state drives in thisrobotic library.





InfoBox

Name Description






Menu Commands


Reports > Robotic LibraryContents

Reports the contents of the selected robotic library.

Configuration > RoboticLibrary

Sets the robotic library instance to be enabled or disabled for monitoring by the NBU KM.

115Reference Guide

Version 2.8.03


Configuration > RoboticLibrary Status

Accesses the individual configuration for determining the status for the selected roboticlibrary instance. By default, the global NBULibraryState to NBULibraryStatusmapping rule is used, as configured at the container level.

Configuration > RoboticDrives

Accesses the dialog for specifying which drives of the selected robotic library are to bemonitored by the NBU KM. By default, all robotic drives of the selected robotic library aremonitored.

Configuration > RoboticDrives Status

Accesses the configuration for determining status for the monitored drive instances on theselected robotic library instance. By default, the global NBURDriveState toNBURDriveStatus mapping rule is used, as configured at the container level.

NBU_LOG_CONTAINER

Icon

Parameters


BPPM Type

NBULogCollectorExecTime Inactive standard parameter monitorsthe collector execution time. Toactivate this parameter, use the PSLbelow, and restart the PATROLAgent:

%PSL pconfig("REPLACE", "/Runtime/NBU/NBULogCollectorExecTime", 1);


%PSL pconfig("REPLACE", "/Runtime/NBU/NBULogCollectorWarn", 3600);


Collection Status

NBULogDetails Set by NBUDatabaseCollector.Summarizes the database information asreported by commands executed by thedata collector.

n/a n/a n/a

InfoBox

Name Description


116Reference Guide

Version 2.8.03






Menu Commands


Reports > Messages List Reports all Symantec NetBackup messages logged in the past 24 hours.

Configuration > Logs Accesses the dialog for specifying which log files are to be monitored by the NBU KM.By default, the following log files are monitored. These log file paths are relative to theSymantec NetBackup installation directory (for example /usr/openv on HP-UX), unless thepath is fully qualified as for the system log on Solaris and HP-UX.

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. If detected,the message containing the expression is added to the appropriate text parameter, unlessthe message also contains an "Excluded" expression for the same filter.

Configuration > Logs ScanLimit

Accesses the global configuration of the data scanning limit for monitored log file instances.By default, the log collector scans 500 KBytes of new log data for each monitored log fileduring each data collection cycle.

117Reference Guide

Version 2.8.03


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 (warnings oralarms) when it detects new errors.

NBU_LOG

Icon

Parameters


BPPM Type

NBULogAlarmCount* Set by NBULogCollector. Monitors thenumber of alarm messages set in theparameter NBULogAlarmText.

If this parameter changes to alarmstate, the recovery action will trigger anevent.

count Alarm: morethan or equal1

Statistics

NBULogAlarmText Set by NBULogCollector. Displays allalarm messages in the log file whichhave not been acknowledged. The filterused by the data collector to determinealarm messages can be customized usingthe KM command Configuration>Log(s) Filter.

These alarm messages can beacknowledged automatically (default) ormanually, depending on theconfiguration in the KM command Configuration > Log(s) AlertAcknowledgement. Manualacknowledgement is available under theKM sub-menu Acknowledgement.

n/a None n/a

NBULogFSSpaceUsedPerce

nt*

Set by NBULogCollector. Monitors thepercentage of space used by the filesystem (where the log file resides).


% Warning:between 95and 98Alarm : 98 and over

Statistics

NBULogSpaceAvailable Set by NBULogCollector. Monitors theavailable space for the log file to use(this is also the available space on thefile system).If this parameter changes to warning oralarm state, the recovery action willtrigger an event.

MB Warning:between 2and 5Alarm: 2 orless

Availability

118Reference Guide

Version 2.8.03


NBULogSpaceGrowthRate Set by NBULogCollector. Displays thegrowth rate of the amount of spaceused by the log file.

KB/s None Statistics

NBULogSpaceUsed Set by NBULogCollector. Displays theamount of space used by the log file.

KB None Statistics

NBULogSpaceUsedPercent*

Set by NBULogCollector. Monitors thepercentage of capacity used by the logfile. The total capacity is the used space(NBULogSpaceUsed) plus available space(NBULogSpaceAvailable). If thisparameter changes to warning or alarmstate, the recovery action will trigger anevent.

% Warning:between 95and 98Alarm: 98 andover

Statistics

NBULogSummary Set by NBULogCollector. Summarizes thelog file information as reported bycommands executed by the datacollector.

n/a None n/a

NBULogText Set by NBULogCollector. Displays all logtext scanned by the data collectorduring the last collection cycle. The sizeof the data scanned by the datacollector is configured in the KMcommand Configuration>Log(s)Scan Limit.

n/a None n/a

NBULogWarningCount* Set by NBULogCollector. Monitors thenumber warning messages set in theparameter NBULogWarningText.

If this parameter changes to a warningstate, the recovery action will trigger anevent.

count Warning:more than orequal to 1

Statistics

NBULogWarningText Set by NBULogCollector. Displays allwarning messages in the log file whichhave not been acknowledged. The filterused by the data collector to determinewarning messages can be customizedusing the KM command Configuration>Log(s) Filter.

These warning messages can beacknowledged automatically (default) ormanually, depending on theconfiguration set through the KMcommand Configuration>Log(s)Alert Acknowledgement. Manualacknowledgement is available under theKM sub-menu Acknowledgement.

n/a None n/a



InfoBox

Name Description

119Reference Guide

Version 2.8.03


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






Description Description of the Symantec NetBackup log file.

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

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

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

Log File Size File size of the log file.

Name Name of the Symantec NetBackup log file.

Path Full file path of the log file.

Total FS Space Total space used by the file system.

Menu Commands


Acknowledgement > Warnings

Allows acknowledgement of warning messages detected on the selected log file instance.This dialog allows selective acknowledgement of "suspicious" error messages detected inthe log file and sent to the text parameter NBULogWarningText.

Acknowledgement > Alarms Allows acknowledgement of alarm messages detected on the selected log file instance.This dialog allows selective acknowledgement of "failure" error messages detected in thelog file and sent to the text parameter NBULogAlarmText.

Acknowledgement >All Allows acknowledgement of all alarm and warning messages detected on the selected logfile instance.This dialog allows acknowledgement of all error messages detected in the log file and sentto the text parameter NBULogWarningText or NBULogAlarmText.

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 for monitoring by theNBU KM.

Configuration > Log Filter Accesses the individual configuration of the log error filter for the selected log file instance.By default, the global log filter is used, as configured at the container level.

Configuration > Log ScanLimit

Accesses the individual configuration of the data scanning limit for the selected log fileinstance.By default, the global log file scanning limit is used, as configured at the container level.

Configuration > Log AlertAcknowledgement

Accesses the individual configuration of the method of acknowledgement for alerts on theselected log file instance.By default, the global method of log error acknowledgement is used, as configured at thecontainer level.

120Reference Guide

Version 2.8.03


NBU_MOUNT

Icon

Parameters

Mount Requests Monitoring is disabled on media servers and in passive multi-node mode.


BPPM Type

NBURequestElapsed* Set by NBURequestCollector. Displaysthe elapsed time since the mountrequest was issued.

minutes None Statistics

NBURequestState Set by NBURequestCollector. Displaysthe state of the mount request asreported in the command executed bythe data collector.

0 =Completed1 = Pending-1 =Unknown

None Availability

NBURequestStatus Set by NBURequestCollector, monitorsthe status of the mount request. Thisstatus is determined by the mountrequest status mapping rule defined inthe KM command Configuration>Mount Request(s)Status.




Availability

NBURequestSummary Set by NBURequestCollector.Summarizes the pending requestinformation as reported by commandsexecuted by the data collector.

n/a n/a n/a



InfoBox

Name Description

Barcode Barcode of the requested media.

Client Name of the policy client the pending request belongs to.

121Reference Guide

Version 2.8.03







Density Density of the requested media.

Description Description of the pending request.

External Media ID Requested media identifier as recorded on the media cartridge or canister.

Job ID ID of the job the pending request belongs to.

Job Type Type of the job the pending request belongs to (Backup or Restore).

Media Server Host name of the media server that issued the pending request.

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

Policy Name Name of the policy the pending request belongs to.

Recorded Media ID Requested media identifier as recorded in the media label.

Request ID Full name assigned for the pending request.

Request Time Date & time when the pending request was issued. This is interpreted using the PendingRequest Date/Time Format defined in the KM menu command.

Storage Unit Name of the storage unit that the media should be mounted on.

User User ID of the person or application the pending request belongs to.

Volume Group Volume group of the requested media.

122Reference Guide

Version 2.8.03


Menu Commands


Administration > Assign Assigns the selected pending request to its requested drive.

Administration > Deny Denies the selected pending request.

Administration > Resubmit Resubmits the selected pending request.

NBU_MOUNT_CONTAINER

Icon

Parameters


BPPM Type

BURequestCollectorExecTime


%PSL pconfig("REPLACE", "/Runtime/NBU/NBURequestCollectorExecTime", 1);


%PSL pconfig("REPLACE", "/Runtime/NBU/NBURequestCollectorWarn", 3600);


Collection Status

NBURequestDetails Set by NBURequestCollector. Displays alldata returned to the standard out fromcommands executed by the datacollector.

n/a n/a n/a

InfoBox

Name Description


123Reference Guide

Version 2.8.03






Menu Commands


Administration > Assign All Assigns all instantiated mount requests to their requested drives.

Administration > Deny All Denies all instantiated mount requests.

Administration > ResubmitAll

Resubmits all instantiated mount requests.

Reports > Pending Requests Reports a list of all pending mount requests.All report KM commands require a user account, which will be used for executing the menucommand. Note the command will fail if the user does not have privileges to execute theappropriate Symantec NetBackup command.

Configuration > MountRequests

Accesses the dialog for specifying which mount requests are to be monitored by the NBUKM.By default, all mount requests are monitored for 1 day from the time they are issued.

Configuration > MountRequests Status

Accesses the configuration for determining the status for all monitored mount requestinstances.By default, the following NBURequestState to NBURequestStatus mapping rule isused:

Configuration > MountRequest Date/Time Format

Accesses the configuration of the date/time format and time zone for all instantiatedmount requests.By default, the format used by Symantec NetBackup for the date/time of a mount requestis set to "MO/DD/YY HH:MM:SS". The date/time is then converted by the NBU KM using thesystem time zone on the PATROL Agent (system time zone is indicated by an empty field).

NBU_PCLIENT

Icon

124Reference Guide

Version 2.8.03


Parameters


BPPM Type

NBUFileExcludeList Set by NBUPolicyCollector. Lists all filesand file systems excluded from backupfor this policy client.

n/a n/a n/a

NBUFileIncludeList Set by NBUPolicyCollector. Lists all filesand file systems included for backup forthis policy client.

n/a n/a n/a

NBUPClientBackupSummary Set by NBUPolicyCollector. Summarizesthe last backup for this policy client.

n/a n/a n/a

NBUPClientBackupThroughp

ut*

Set by NBUPolicyCollector. Displays thethroughput of the last backup for thispolicy client.


NBUPClientFullBackupDurati

on

Set by NBUPolicyCollector. Displays theduration of the last successful fullbackup for this policy client.


NBUPClientFullBackupFileCo

unt

Set by NBUPolicyCollector. Displays thenumber of files backed up in the lastsuccessful full backup for this policyclient.


NBUPClientFullBackupSize*

Set by NBUPolicyCollector. Displays thesize of the last successful full backup forthis policy client.

MB None Statistics

NBUPClientIncrBackupDurat

ion

Set by NBUPolicyCollector. Displays theduration of the last successfulincremental backup for this policy client.


NBUPClientIncrBackupFileC

ount

Set by NBUPolicyCollector. Displays thenumber of files backed up in the lastsuccessful incremental backup for thispolicy client.


NBUPClientIncrBackupSize*

Set by NBUPolicyCollector. Displays thesize of the last successful incrementalbackup for this policy client.

MB None Statistics

NBUPClientSummary Set by NBUPolicyCollector. Summarizesthe policy client information as reportedby commands executed by the datacollector.

n/a n/a n/a



InfoBox

Name Description



125Reference Guide

Version 2.8.03





Description Description of the Symantec NetBackup policy client.

Hardware Hardware platform of the policy client.

Last Backup End Date & time when the last backup completed for the policy client.

Last Backup Job ID Job ID of the last backup for the policy client.

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

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

Last Full Backup End Date & time when the last successful full backup completed for the policy client.

Last Full Backup Job ID Job ID of the last successful full backup of the policy client.

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

Last Incr Backup End Date & time when the last successful incremental backup completed for the policy client.

Last Incr Backup Job ID Job ID of the last successful incremental backup of the policy client.

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

Name Host name of the Symantec NetBackup policy client.

Operating System Operating system of the policy client.

Policy Name Name of the policy that the policy client belongs to.

Priority Priority of the policy client.

126Reference Guide

Version 2.8.03


Menu Commands


Configuration > Policy Client Sets the policy client instance to be enabled or disabled for monitoring by the NBU KM.

NBU_POLICY_CONTAINER

Icon

Parameters


BPPM Type

NBUPolicyCollectorExecTime


%PSL pconfig("REPLACE", "/Runtime/NBU/NBUPolicyCollectorExecTime", 1);


%PSL pconfig("REPLACE", "/Runtime/NBU/NBUPolicyCollectorWarn", 3600);


Collection Status

NBUPolicyDetails Set by NBUPolicyCollector. Displays alldata returned to the standard out fromcommands executed by the datacollector.

n/a n/a n/a

InfoBox

Name Description



127Reference Guide

Version 2.8.03





Menu Commands


Configuration > Policies Sets which policies are to be monitored by the NBU KM. By default, all policies configuredon the master server are monitored.

Configuration > PoliciesBackup Restriction

Accesses the global configuration to set a backup restriction window for all monitoredpolicy instances. By default, backup restriction is disabled.When the backup restriction window is defined and enabled using this dialog, and if thepolicy status mapping rule is configured appropriately, an alert will be triggered if anybackup activity is detected during this restriction window.

Configuration > PoliciesStatus

Accesses the global configuration for determining the policy status for monitored policyinstances.By default, the following NBUPolicyState to NBUPolicyStatus mapping rule is used:

Configuration > PoliciesClients

Accesses the dialog for specifying which policy clients of the selected policy are to bemonitored by the NBU KM.By default, all policy clients of enabled policies are monitored. Type "[default]" to reset tothe default configuration.

NBU_POLICY

Icon

Parameters


BPPM Type

128Reference Guide

Version 2.8.03


NBUPolicyBackupElapsed*

Set by NBUPolicyCollector. Displays theelapsed time since the last backup forthis policy, regardless of completionstatus of the backup. This last backup isdetermined from the monitored jobs asconfigured in the KM command Configuration>Jobs from the Jobsicon.

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

NBUPolicyBackupSummary Set by NBUPolicyCollector. Summarizesthe last backup for this policy.

n/a n/a n/a

NBUPolicyBackupThroughpu

t*

Set by NBUPolicyCollector. Displays thethroughput of the last backup for thispolicy.


NBUPolicyFullBackupDuratio

n

Set by NBUPolicyCollector. Displays theduration of the last successful fullbackup for this policy.


NBUPolicyFullBackupElapse

d*

Set by NBUPolicyCollector. Displays theelapsed time since the last successful fullbackup for this policy. This last backup isdetermined from the monitored jobs asconfigured in the KM command Configuration>Jobs from the Jobsicon.



NBUPolicyFullBackupFileCou

nt

Set by NBUPolicyCollector. Displays thenumber of files backed up in the lastsuccessful full backup for this policy.


NBUPolicyFullBackupSize

Set by NBUPolicyCollector. Displays thesize of the last successful full backup forthis policy.

GB None Statistics

NBUPolicyIncrBackupDurati

on

Set by NBUPolicyCollector. Displays theduration of the last successfulincremental backup for this policy.


NBUPolicyIncrBackupElapse

d*

Set by NBUPolicyCollector. Displays theelapsed time since the last successfulincremental backup for this policy. Thislast backup is determined from themonitored jobs as configured in the KMcommand Configuration>Jobs fromthe Jobs icon.



129Reference Guide

Version 2.8.03


NBUPolicyIncrBackupFileCo

unt

Set by NBUPolicyCollector. Displays thenumber of files backed up in the lastsuccessful incremental backup for thispolicy.


NBUPolicyIncrBackupSize

Set by NBUPolicyCollector. Displays thesize of the last successful incrementalbackup for this policy.

GB None Statistics

NBUPolicyState Set by NBUPolicyCollector. Displays thestate of the policy.

If a backup restriction window is definedin the KM command Configuration>Policy (Policies) BackupRestriction, this parameter will be setto Running in Restricted Window if thereis any activity during the specifiedperiod.

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

None Availability

NBUPolicyStatus Set by NBUPolicyCollector. Monitors thestatus of the policy. This status isdetermined by the policy status mappingrule defined in the KM command Configuration> Policy (Policies)Status.




Availability

NBUPolicySuccBackupElaps

ed*

Set by NBUPolicyCollector. Displays theelapsed time since the last successfulbackup for this policy. This last backup isdetermined from the monitored jobs asconfigured in the KM command Configuration>Jobs from the Jobsicon.



NBUPolicySummary Set by NBUPolicyCollector. Summarizesthe policy information as reported bycommands executed by the datacollector.

n/a None n/a



InfoBox

Name Description

Active Status of the policy (yes or no).

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

130Reference Guide

Version 2.8.03






Description Description of the Symantec NetBackup policy.

Keyword Keyword phrase used by the policy to associate all its backups.

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

Last Backup Job ID Job ID of the last backup for the policy.

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

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

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

Last Full Backup Job ID Job ID of the last successful full backup for the policy.

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

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

Last Incr Backup Job ID Job ID of the last successful incremental backup for the policy.

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

Max Jobs/Policy Maximum number of concurrent jobs allowed for the policy.

Multiple Data Stream Whether the multiple data streaming is allowed for this policy (yes or no).

Name Name of the Symantec NetBackup policy.

Next Backup Schedule Name of the next backup schedule.

Next Backup Date & time of the next scheduled backup.

Priority Priority of the policy.

Residence Label of the storage unit used by the policy.

Status Current execution status of the policy (Idle, Running, or Running in Restricted Window).

Type Type of the policy.

Volume Pool Volume pool of the policy.

Menu Commands


Reports > Policy Schedule Displays the schedule of the selected policy instance.

Configuration > Policy Accesses the individual configuration for monitoring the selected policy instance.This dialog allows the selected policy instance to be enabled or disabled for monitoring bythe NBU KM.

Configuration > PolicyBackup Restriction

Accesses the individual configuration for the backup restriction window for the selectedpolicy instance.

131Reference Guide

Version 2.8.03


By default, the global backup restriction rule is used, as configured at the container level.

Configuration > PolicyStatus

Accesses the individual configuration for determining policy status for the selected policyinstance.By default, the global NBUPolicyState to NBUPolicyStatus mapping rule is used, asconfigured at the container level. Select [default] to revert to the policy status mappingrule configured at the global/container level.

Configuration > PolicyClients

Accesses the dialog for specifying which policy clients of the selected policy are to bemonitored by the NBU KM.By default, all policy clients of enabled policies are monitored. Type "[default]" to reset tothe default configuration.

132Reference Guide

Version 2.8.03


NBU_POOL_CONTAINER

Icon

Parameters


BPPM Type

NBUPoolCollectorExecTime Inactive standard parameter monitorsthe collector execution time. Toactivate this parameter, use the PSLbelow, and restart the PATROLAgent:

%PSL pconfig("REPLACE", "/Runtime/NBU/NBUPoolCollectorExecTime", 1);


%PSL pconfig("REPLACE", "/Runtime/NBU/NBUPoolCollectorWarn", 3600);


Collection Status

NBUPoolDetails Set by NBUPoolCollector. Displays alldata returned to the standard out fromcommands executed by the datacollector.

n/a n/a n/a

133Reference Guide

Version 2.8.03


InfoBox

Name Description






Menu Commands


Configuration > VolumePools

Sets which volume pools are to be monitored by the NBU KM. By default, all volume poolsconfigured on the master/media server are monitored, except for "None" (the default poolshipped with the Symantec NetBackup application).

Reports > Available Media Reports all available media across all volume pools.

NBU_POOL

Icon

Parameters

Pool monitoring is disable on media servers and in passive multi-node mode


BPPM Type

NBUMediaActiveCount Set by NBUPoolCollector. Displays thenumber of active media in this volumepool. Active media are available tapemedia with a status of Active, wheredata has been written but the media isnot yet full.


NBUMediaActivePercent*

Set by NBUPoolCollector. Monitors thepercentage of active media against thetotal number of media in this volumepool.


Statistics

134Reference Guide

Version 2.8.03



NBUMediaCount Set by NBUPoolCollector. Displays thetotal number of media in this volumepool.


NBUMediaEmptyCount Set by NBUPoolCollector. Displays thenumber of full media in this volume pool.Empty media are available tape mediawith a status Active and no data storedon them.


NBUMediaFrozenCount Set by NBUPoolCollector. Displays thenumber of frozen media in this volumepool. Frozen is a possible status for atape media.


NBUMediaFullCount Set by NBUPoolCollector. Displays thenumber of full media in this volume pool.Full is a possible status for a tape media.


NBUMediaFullPercent* Set by NBUPoolCollector. Monitors thepercentage of full media against thetotal number of media in this volumepool.


% Warning:95-98Alarm: 98-100

Statistics

NBUMediaLoadedCount Set by NBUPoolCollector. Displays thenumber of media in this volume pool,currently loaded to a robotic library.


NBUMediaReadOnlyCount

Set by NBUPoolCollector. Displays thenumber of media in this volume pool,currently read-only. A media turns read-only when it has reached the maximumallowed mounts.


NBUMediaScratchCount Set by NBUPoolCollector. Displays thenumber of scratch media in this volumepool. The parameter is visible and setonly for scratch volume pools.

count Warning: 0-2Alarm = 0

Statistics

NBUMediaSuspendedCount

Set by NBUPoolCollector. Displays thenumber of suspended media in thisvolume pool. Suspended is a possiblestatus for a tape media.


NBUMediaUnassignedCount

Set by NBUPoolCollector. Displays thenumber of media in unassigned state inthis volume pool.


NBUMediaUnassignedPerce

nt*

Set by NBUPoolCollector. Monitors thepercentage of unassigned media againstthe total number of media in this volumepool.If this parameter changes to warning oralarm state, the recovery action willtrigger an event.

% None Statistics

NBUMediaUnknownCount

Set by NBUPoolCollector. Displays thenumber of media in unknown state in thisvolume pool.


135Reference Guide

Version 2.8.03


NBUPoolSpaceAvailable* Set by NBUPoolCollector. Monitors theavailable media space for the backupdata to use amongst the assigned mediain this volume pool.


GB None Availability

NBUPoolSpaceGrowthRate Set by NBUPoolCollector. Displays thegrowth rate of the total media spaceused by the backup data in this volumepool.


NBUPoolSpaceUsed* Set by NBUPoolCollector. Displays thetotal media space occupied by thebackup data in this volume pool.

GB None Statistics

NBUPoolSpaceUsedPercent

*

Set by NBUPoolCollector. Monitors thepercentage of total occupied mediaspace against the total media capacityof this volume pool (not including anyscratch media). If this parameterchanges to warning or alarm state, therecovery action will trigger an event.


Statistics

NBUPoolSummary Set by NBUPoolCollector. Summarizesthe volume pool information as reportedby commands executed by the datacollector.

n/a n/a n/a



InfoBox

Name Description






Description Description of the pool.

Group Name of the operating system user group allowed to use volumes in this pool.

Host Name Name of the host that will be permitted to request and use volumes in this pool.

Name Name of the volume pool.

User User ID of the person or application who is permitted to use volumes in this pool.

136Reference Guide

Version 2.8.03


Menu Commands


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

Configuration > Volume Pool Sets the volume pool instance to be enabled or disabled for monitoring by the NBU KM.

NBU_SERVER

Icon

Parameters


BPPM Type

ExtraFilesList Pushes the NetBackup KM library files tothe PATROL Agent during the "Commit"operation.

n/a None n/a

NBUClientCollector Collects Symantec NetBackup clientrelated information. It sets all consumerparameters in the NBU_CLIENT_CONTAINER andNBU_CLIENT application classes. Bydefault, this collector is executed onlyon the master server.

Poll Time: 600 seconds

n/a None n/a

NBUCreateDistribution Is automatically activated at the end ofNetBackup KM debugging if the customerchooses to "prepare debug files forsending to Sentry Software". It isdeactivated on completion.


n/a None n/a

NBUDaemonCollector Collects Symantec NetBackup daemonrelated information. It sets all consumerparameters in the NBU_DAEMON_CONTAINER andNBU_DAEMON application classes.

n/a None n/a

137Reference Guide

Version 2.8.03



NBUDatabaseCollector Collects Symantec NetBackup catalogdatabase related information. It sets allconsumer parameters in the NBU_DATABASE_CONTAINER andNBU_DATABASE application classes.By default, this collector is executedonly on the master server.


n/a None n/a

NBUDriveCollector Collects Symantec NetBackupstandalone drive related information. Itsets all consumer parameters in the NBU_DEVICE_CONTAINER andNBU_DEVICE application classes.


n/a None n/a

NBUJobCollector Collects Symantec NetBackup backup/restore activity related information. Itsets all consumer parameters in the NBU_JOB_CONTAINER and NBU_JOBapplication classes. By default, thiscollector is executed only on the masterserver.


n/a None n/a

NBULibraryCollector Collects Symantec NetBackup roboticlibrary and robotic drive relatedinformation. It sets all consumerparameters in the NBU_LIBRARY_CONTAINER,NBU_LIBRARY, and NBU_LDEVICEapplication classes.


n/a None n/a

NBULogCollector Collects Symantec NetBackup log filerelated information. It sets all consumerparameters in the NBU_LOG_CONTAINER and NBU_LOGapplication classes.


n/a None n/a

NBULoginStatus* Monitors the status of the NetBackup KMlogin details (username/password) forthe operating system. It is set by the NBU_SERVER application classdiscovery. If no valid username/password is detected for the operatingsystem, this parameter will be set toFailure state. If there are any suspiciouscommands, this parameter will be set toSuspicious state.




Collection Status

138Reference Guide

Version 2.8.03


NBUMonitoringMode* Monitors failover mode of the NetBackupKM. It is set by the NBU_SERVERapplication class discovery.By default NetBackup KM runs inPermanent Single-node Mode but multi-node monitoring can be configured. Formore details refer to Configuring Multi-Node Monitoring Mode.

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

None Collection Status

NBUNodeStatus* Monitors error messages for theSymantec NetBackup application on thismanaged system. It is set by the NBU_SERVER application classdiscovery.If any of the Symantec NetBackupapplication daemons is not running, thisparameter will be set to Failure state.The list of critical Symantec NetBackupdaemons can be customized using theKM command Configuration>NodeStatus from the Symantec NetBackupicon. If there are any suspiciouscommands due to an error from themaster/media server, this parameter willbe set to Suspicious state.




Availability

NBUPolicyCollector Collects Symantec NetBackup policy andpolicy client related information. It setsall consumer parameters in the NBU_POLICY_CONTAINER,NBU_POLICY, and NBU_PCLIENTapplication classes.By default, this collector is executedonly on the master server.


n/a n/a n/a

NBUPoolCollector Collects Symantec NetBackup volumepool related information. It sets allconsumer parameters in NBU_POOL_CONTAINER andNBU_POOL application classes.By default, this collector is executedonly on the master server.


n/a n/a n/a

NBURequestCollector Collects Symantec NetBackup pendingrequest related information. It sets allconsumer parameters in the NBU_MOUNT_CONTAINER andNBU_MOUNT application classes.By default, this collector is executedonly on the master server.

n/a n/a n/a

139Reference Guide

Version 2.8.03



NBUStorageCollector Collects Symantec NetBackup storagepool related information. It sets allconsumer parameters in the NBU_STORAGE_CONTAINER,NBU_STORAGE, NBU_DPOOL andNBU_DVOLUME application classes. Bydefault, this collector is executed onlyon the master server.

Poll Time:1800 seconds

n/a n/a n/a

NBUUpdateAgent Is used by the NetBackup KM to set thePATROL Agent KM variables when thePATROL Console user is not authorizedto update (ACL) any PATROL Agentvariables. It is activated automaticallywhen the KM fails to update the PATROLAgent.


n/a n/a n/a


InfoBox

Name Description

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

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

Binary Path Symantec NetBackup software binary paths used by NBU KM.

Copyright Copyright (C) Sentry Software.

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

Installation Path Symantec NetBackup software installation path.

Library Path Symantec NetBackup software library paths used by NBU KM.

Master Server(s) Names of the discovered Master Servers.

Media Server(s) Names of the discovered Media Servers.

Monitoring Mode Monitoring mode of the Knowledge Module.

Monitoring Node Node currently monitoring Symantec NetBackup.

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

Node Type Type of node (Master Server or Media Server).

Operating System Operating system description as reported by PATROL Agent.

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

Platform Operating system platform as reported by the PATROL Agent (HP, SOLARIS, RS6000, orNT).

Product Name Name of the Knowledge Module.

140Reference Guide

Version 2.8.03


Product Release Date Release date of the Knowledge Module.

Product Version Version number of the Knowledge Module.

Support [email protected]

Web Site www.bmc.com

Menu Commands


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 Reloads commands used by the NBU KM during the next full discovery cycle. By default, allnew commands are reloaded automatically.

Administration > StartMaster Server

Starts master server daemons.

Administration > StopMaster Server

Stops master server daemons.

Administration > Start MediaServer

Starts media server daemons.

Administration > Stop MediaServer

Stops media server daemons.

Configuration > Login Accesses the Login Configuration dialog for viewing and entering NBU KM login detailsfor the operating system.This user account should have privileges to execute Symantec NetBackup administrationcommands and can use sudo privileges on Unix PATROL Agents.This user account will be used by NBU KM pre-discoveries, discoveries, data collectors,recovery actions, and InfoBoxes to execute operating system commands. It will not beused by any KM commands.The password is encrypted and stored on the PATROL Agent using the BMC PATROLencryption function.

Configuration > Preloading Accesses the Preloading Configuration dialog, which adds or removes the KM fromPATROL Agent variable "/AgentSetup/preloadedKMs". By preloading the NBU KM,the PATROL Agent will monitor the Symantec NetBackup application without any PATROLConsole connection.

Configuration > MonitoringMode

Accesses the Failover Mode Configuration dialog, which is used for enabling ordisabling KM failover, when monitoring clustered Symantec NetBackup environment.

Configuration > Paths Accesses the Path Configuration dialog, which displays and sets all paths used by NBUKM.Paths are automatically discovered by the NBU KM server discovery. They are used asenvironment variables for executing various Symantec NetBackup application commands.Altering these paths may impact the operation of the KM.

KM paths are used as environment variables and internally:

KM_HOME keeps all KM scripts.

KM_TEMP is used for creating KM temporary files.

KM_DEBUG is used for creating KM debug files.

141Reference Guide

Version 2.8.03


Installation Path is the application installation path discovered by the KM. Thisinformation can be overridden through the KM command

Binary Paths are the Application and operating system binary path, which is used forsetting PATH environment variable. The KM discovers and set this automatically. Thismenu can be used, if the discovered paths are incorrect.

Library Paths are the Application and operating system library path, which is used forsetting the following environment variables:

LD_LIBRARY_PATH (on Solaris)SHLIB_PATH (on HP-UX)LIBPATH (on AIX)

The KM discovers and set this automatically. This menu can be used, if the discoveredpaths are incorrect.

Log Directory Path: The log path where NetBackup maintains the daily messageslogs.

Node Type Accesses the Node Type dialog, which displays and sets the type of the SymantecNetBackup application node.The NBU KM master/media server discovery detects the type of the node automatically;the type can either be Master Server or Media Server. The operation of the KM dependson this node type.

Node Status Accesses the Node Status Configuration dialog for viewing and modifying the daemonnames monitored for node status.The NBU KM checks for the existence of these daemons to determine the status of thenode (parameter NBUNodeStatus). By default, the following daemons are sought:

Instance Limits Accesses the Instance Limits Configuration dialog to view and modify the maximumnumber of NBU KM application instances allowed for each application class.

Debug Accesses the Debug Configuration dialog for enabling/disabling the NBU KM debugswitches. 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.

142Reference Guide

Version 2.8.03


NBU_STORAGE_CONTAINER

Icon

Parameters


BPPM Type

NBUStorageCollectorExecTime


%PSL pconfig("REPLACE", "/Runtime/NBU/NBUStorageCollectorExecTime", 1);


%PSL pconfig("REPLACE", "/Runtime/NBU/NBUStorageCollectorWarn", 3600);


Collection Status

NBUStorageDetails Set by NBUStorageCollector. Displays alldata returned to the standard out fromcommands executed by the datacollector.

n/a n/a n/a



InfoBox

Name Description





143Reference Guide

Version 2.8.03



Menu Commands


Configuration > Storages Accesses the dialog for specifying which storages are to be monitored by the NBU KM. Bydefault, all local and remote storages are monitored for a master server and all localstorages are monitored for a media server.

Configuration > StoragesUp/Down Status

Accesses the global configuration for determining the up/down status for monitoredstorage instances.

By default, the following NBUStorageUpDownState to NBUStorageUpDownStatusmapping rule is used:

Configuration > Disk Pools Sets which disk pools of the selected storage are to be monitored by the NBU KM. Bydefault, all disk pools of the selected storage are monitored.

Configuration > Disk PoolsUp/Down Status

Accesses the global configuration for determining the up/down status for monitored diskpool instances.

By default, the following NBUDPoolUpDownState to NBUDPoolUpDownStatusmapping rule is used:




Accesses the global configuration for determining the up/down status for monitored diskvolume instances.

By default, the following NBUDVolumeUpDownState toNBUDVolumeUpDownStatus mapping rule is used:

144Reference Guide

Version 2.8.03


NBU_STORAGE

Icon

Parameters

Storage monitoring is disabled in passive multi-node mode


BPPM Type

NBUStorageSummary Set by NBUStorageCollector. Summarizesthe storage information as reported bycommands executed by the datacollector.

n/a n/a n/a

NBUStorageUpDownState Set by NBUStorageCollector. Displaysthe up/down state of the storage.


None Availability

NBUStorageUpDownStatus Set by NBUStorageCollector. Monitorsthe up/down status of the storage. Thisstatus is determined by the storagestatus mapping rule defined in the KMcommand Configuration>Storage(s)Status.




Availability

InfoBox

Name Description






Description Description of the storage.

Storage Server Type Type of the storage server.

145Reference Guide

Version 2.8.03


Storage Server Name of the host where the storage is attached to.

Up/Down State Up/down status of the storage.

Menu Commands


Configuration > Storage Sets the storage instance to be enabled or disabled for monitoring by the NBU KM.

Configuration > Storage Up/Down Status

Accesses the individual configuration for determining storage up/down status for theselected storage instance.By default, the global NBUStorageUpDownState to NBUStorageUpDownStatusmapping rule is used, as configured at the container level.

Configuration > Disk Pools Sets which disk pools of the selected storage are to be monitored by the NBU KM. Bydefault, all disk pools of the selected storage are monitored.

Configuration > Disk PoolsUp/Down Status

Accesses the configuration for determining up/down status for the monitored disk poolinstances on the selected storage instance.By default, the global NBUDPoolUpDownState to NBUDPoolUpDownStatus mappingrule is used, as configured at the container level.




Accesses the configuration for determining up/down status for the monitored disk volumeinstances on the selected storage instance.By default, the global NBUDVolumeUpDownState to NBUDVolumeUpDownStatusmapping rule is used, as configured at the container level.

Additional Information

TroubleshootingThe table below will help you diagnose any problems you may encounter when installing or runningSymantec NetBackup KM for PATROL. Here are some troubleshooting tips:

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

Most KM problems are reported in the KM Status Report, which can be viewed by selecting themenu KM Status from the Symantec NetBackup or NBU_SETUP icon. Run this report to diagnoseany problems.

The NetBackup KM triggers PEM events for most severe problems. Each event triggered from theKM includes an Expert Advice, which provides details about the problem and some suggestions toresolve it.

Problem Possible Resolution

Unable to find NBU_LOAD.kml

Check that the Load KM browser is looking for *.kml files under PATROL_HOME/lib/knowledge folder.

146Additional Information

Version 2.8.03


Symantec NetBackup KM for PATROL files have not been installed correctly under the PATROLinstallation directory on the PATROL Console.

NBU_SETUPicon does not appear after loading

Check whether this managed node is a supported Symantec NetBackup node (master serveror media server), and it is configured properly.

Check that the version of Symantec NetBackup is supported by the Symantec NetBackup KMfor PATROL.

Check that there is no KM version mismatch between the PATROL Console and the PATROLAgent. Check the messages in the PATROL Console SOW to verify this.

Check whether the PATROL Agent tuning variable,/AgentSetup/AgentTuning/pslInstructionMax has been increased as suggested in section 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’s AccessControl List (/AgentSetup/accessControlList) in order to read and write to the AgentConfiguration Database.

Parameter NBULoginStatus is in suspicious (warning) status

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

Check the annotation point on the first state change data point of this parameter to look forany failing commands. If an annotation point cannot be found, or if it is not up-to-date,check the KM Status Report, which can be viewed by selecting the menu KM Status fromthe Symantec NetBackup icon. These errors are produced from the Symantec NetBackupcommands executed by the NetBackup KM.

Check that the operating system user configured in the menu Configuration>Login canexecute all NetBackup commands and access the NetBackup files.

All/some KM objects disappear from the Console

Check whether there is a KM version mismatch between the PATROL Console and thePATROL Agent, possibly after an improper upgrade of the KM. Check the messages in thePATROL Console SOW to verify this.

Check that the NetBackup KM login details are still valid. Has the password changed on thesystem? Look for any error messages on the SOW, and check for additional information in thelast annotation point for parameter NBULoginStatus.

All/some KM application instances do not appear

Check that the KM instance limits have not been exceeded. Look for any error messages onthe SOW, and increase the instance limits for affected objects using the menu Configuration>Instance Limits.

Check the messages in the PATROL Console SOW for suggestions for the new limit. Theseerrors are also displayed in the KM Status Report, which can be viewed by selecting themenu KM Status from the Symantec NetBackup icon.

Check whether the main instance, Symantec NetBackup, is in offline state. None of the datacollectors will be executed until the main instance is created in online state. The main instanceis created in offline state until the initial discovery is complete. Also if the KM is configured tofailover in a VCS clustered Symantec NetBackup environment the main container will becreated in offline state on all nodes where the service group is offline.

Behavior of the NetBackup KM hasnot changed in accordance withtheRelease Notesaftera KM upgrade

Check the version of the KM from the main InfoBox. If it has not changed, then theinstallation is not complete. Make sure both the PATROL Console and the PATROL Agent areuninstalled and installed correctly during the KM upgrade

NetBackup KMtakes a long timetorefresh the parameters and

Data collectors run according to their scheduling interval (polling cycle) defined in the KM. Theseintervals are defined for a standard environment with minimal resource impact. These intervalscan be customized from the PATROL Developer Console to suit your environment. Refer to thePATROL Console User Guide for more details.


Version 2.8.03


applicationclasses on the PATROL Console

Poorperformance of the Symantec NetBackup master/mediaserver after installingthe KM

This happens if the NetBackup KM is installed on a heavily used system. Depending on thecomplexity of your Symantec NetBackup environment, the NetBackup KM may consume moreresources to interrogate the application and process the data. In such a complex environment,the NetBackup KM may require some fine tuning to optimize the available resources. Considerthe following options:

Disable monitoring of unnecessary application instances. This can be achieved by using theappropriate menu 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 are noSymantec NetBackup activity. For example, if the job monitoring can be disabled between 9am and 4 pm everyday, except weekends, then disable job data collector(NBUJobCollector) during this period, using following PSL through PATROL Console:

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

"0|32400|57600|0|0|||||||||||0|0");

Here the pconfig variable is named as: <collector name>Mode. The value contains followingdetails, delimited by pipe (|):enabled (1)/disabled (0) data collection, default start/end times innumber of seconds since midnight, start/end times for non-default days starting from Sundaythrough to Saturday.

The JOB_TEXT command which sets display only text parameter NBUJobText, can bedisabled to improve the performance using the PSL below:

%PSL pconfig("REPLACE", "/Runtime/NBU/NBU_JOB/jobCollectText", 0);

%PSL unset("/NBU_JOB/jobCollectText");

As part of collection, the collector compares each job against previous similar backup tocalculate the progress data. In addition the last backup info is shared under NBU_POLICYparameters (NBUPolicy*Backup*) to monitor the success at the policy level. This functionalitycan also be disabled to speed up the collector, using the PSL below:

%PSL pconfig("REPLACE", "/Runtime/NBU/NBU_JOB/jobCollectLastBackupStats", 0);

%PSL unset("/NBU_JOB/jobCollectLastBackupStats");

Defining a "no command execution window" for all collectors will pause running commands atpeak times or during NetBackup maintenance windows. This can be set using the PSL below:

%PSL pconfig("REPLACE", "/Runtime/NBU/noExecuteWindow", "23:59:00|120");

%PSL unset("/NBU_SERVER/noExecuteEnd");

The value of this permanent configuration variable is in format “<start time in HH:MM:SS 24-hour clock>|<duration in seconds>”. The above “23:59:00|120” sets all collectors to sleepbetween 23:59:00 and 00:01:00 (2 minutes) every day before executing commands.

Also this noExecutewindow supports multiple time windows:%PSL pconfig("REPLACE", "/Runtime/NBU/noExecuteWindow", ["23:59:00|120","11:59:00|120"]);

Purge unnecessary information in Symantec NetBackup catalog databases and log files.

If there are too many clients configured in Symantec NetBackup, the NBUClientCollectorand NBUPolicyCollector may affect the overall performance. In such environment disablethe NBUClientCollector, or set their instance limits to 0 (zero), using menuConfiguration> Instance Limits.

Also refer to Infinite Loop Errors for a possible PATROL internal scheduling delay which mayimpact the performance of the KM.

Old active jobsare not removedfrom

By default, all active jobs are monitored, and they are exempted from ageing. It is possible tochange this behavior by Including Active Jobs in the menu Configuration>Jobs from Jobscontainer.


Version 2.8.03


the console

Infinite LoopErrors(Error messageson the SOWreporting that some NetBackup KM data collectorsmay 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 this function tothe back of the process queue. This will not only delay the data collector, it will also impact theperformance 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 that thedefault value of 500,000 should be increased to at least 5,000,000 on a standard SymantecNetBackup environment to enable the NetBackup KM data collectors to execute withoutimpacting your system.

If this still does not resolve the problem, you can disable this functionality by setting the valueof the tuning variable to zero (0).

Unable to turn on the KM Debug

If you are unable to turn on the KM Debug following the method described in Debugging the KM, you turn the debug on by setting appropriate PATROL Agent configuration variable with atimestamp value. This timestamp value determines when the debug should be turned off. Forexample, to turn on the debug for 60 minutes from now, run the following PSL through PATROL Console:

%PSL pconfig("REPLACE","/Runtime/NBU/<component>Debug",

time()+3600);

Where <Component> is either server for debugging the server discovery or name of thecollector component in lower case followed by “Collector”, like daemonCollector fordebugging daemon collector.

Oldacknowledged jobs are still keptin the pconfig database.

By default the KM stores all acknowledged jobs. Use the following PSL through PATROL Consoleto keep only the last <Number> of jobs:

%PSL pconfig("REPLACE",

"/Runtime/NBU/NBU_JOB/jobAcknowledgementCapacity",

<Number>);

Prefer a different job instance label

By default the job instances are labeled as:<policy>:<policy client> @ <date/time>

This label can be changed to include job ID as in one of the following formats:Format 1: <job id>Format 2: <job id>: <policy client> @ <date/time>Format 3: <job id>: <policy>:<policy client> @ <date/time>

Use the following PSL through PATROL Console to modify the job instance label:%PSL pconfig("REPLACE","/Runtime/NBU/labelByJobID",

<Format Number>);

Where <Format Number> is either 1, 2, or 3 as described above. Use the menu Force FullCollection from the Jobs container instance to recreate the job instances.


Version 2.8.03


Impact on ResourcesThis section describes:

• CPU and memory usage of the KM

• Network traffic generated by the KM

CPU and Memory Usage

CPU and memory usage will depend on the size and complexity of your environment and your NetBackupKM configuration. As you increase data collection frequency, increase the number of instancesmonitored by the KM or add functionality through customization, your CPU and memory usage willincrease.

When monitoring a standard installation of Symantec NetBackup using NetBackup KM, the PATROL Agentwill consume between 5MBytes and 10MBytes of additional system memory. An enterprise installation ofSymantec NetBackup Master Server with multiple Media Servers, Clients, Storage Servers and StorageUnits can consume more memory (as per other KMs used by the PATROL Agent). The memory usage ofNetBackup KM can be reduced by:

• disabling monitoring unnecessary component instances (by using the configuration menu)

• disabling unwanted components (by setting their instance limits to 0)

• disabling unwanted collectors (by using the PATROL Configuration Manager)

• increasing the collector scheduling interval (by using the PATROL Configuration Manager)

• decreasing the instance limits to limit the number of instances created by the collectors

The data collectors in NetBackup KM uses Symantec NetBackup command line interface to obtainSymantec NetBackup information. Most of the performance degradation is associated with thesecommand executions and amount of data returned. It may improve the overall performance, if theregular housekeeping is followed on all Symantec NetBackup systems.

Network Traffic

Under normal conditions, the NetBackup KM generates minimal network traffic. Most of the data is kepton the managed node. The amount of network traffic that it generates depends on the number ofPATROL Consoles that are connected to the PATROL Agent and the frequency of data collection.

Customer SupportYou can obtain technical support by using the Support page on the BMC Software Web site or bycontacting Customer Support by telephone or email. 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://



Version 2.8.03


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 email notices when new product versions are released

Find worldwide BMC Software support center locations and contact information, including emailaddresses, fax and telephone numbers

Support by Telephone or Email

In the United States and Canada, if you need technical support and do not have access to the Web, call800 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)

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, and service

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

messages from the operating system, such as "file system full"

messages from related software



Index 151

Version 2.8.03


Index

- A -Abnormalities 52

Access

Executable Files 15

Files 15

Library Files 15

Paths 15

Permissions 15Acknowledge

Alarm 80

Alerts 80

Job Alerts 80

Log Alerts 80

Mount Request 55

Warning 80Acknowledgement

Configure 73

Job 73

Log 73Adapter 50

Add 50, 51

Create 50

Update 51Administer

Symantec NetBackup 54Administration

Robotic Drives 56

Standalone Drives 56Agent

PATROL 45AIX 15

Alarm

Acknowledge 80Alarm Filter State Rules 65

Alert Acknowledgement 73

Configure 73

Job 73

Log 73Alerts

Acknowledge 80Application Class

NBU_CLIENT 85

NBU_CLIENT_CONTAINER 83

NBU_DAEMON 89

NBU_DAEMON_CONTAINER 86

NBU_DATABASE 92

NBU_DATABASE_CONTAINER 91

NBU_DEVICE 95, 109

NBU_DEVICE_CONTAINER 97

NBU_DPOOL 99

NBU_DVOLUME 101

NBU_JOB 106

NBU_JOB_CONTAINER 103

NBU_LIBRARY 112

NBU_LIBRARY_CONTAINER 111

NBU_LOG 117

NBU_LOG_CONTAINER 115

NBU_MOUNT 120

NBU_MOUNT_CONTAINER 122

NBU_PCLIENT 123

NBU_POLICY 127

NBU_POLICY_CONTAINER 126

NBU_POOL 133

NBU_POOL_CONTAINER 132

NBU_SERVER 136

NBU_STORAGE 144

NBU_STORAGE_CONTAINER 142Available Media

Reports 132

- B -Baselines

BMC ProactiveNet Performance Management 52

Generation 52

Manage 52

Requirements 52BMC

BMC Portal 50

BMC ProactiveNet Performance ManagementPortal 13

BMC Software PATROL Agent 13

BMC Software PATROL Console 13

Requirements 13BMC PATROL

Changes 13

pslInstructionMax 13BMC ProactiveNet

Integration 50

Index 152

Version 2.8.03


BMC ProactiveNet Performance Management

Abnormalities 52

Baselines 52

Key Performance Indicators 52

KPI 52

- C -Changes 8

Check

Instance Limits 47Classes 82

Clients

Delete 60

Disable 60

Enable 60

Status Configuration 65Cluster

Configure 58Clustering Application 58

Commands

Reload 76Configure

Alert Acknowledgement 73

Cluster 58

Jobs Exit Status Filter 71

KM User Account 45

Log Error Filter 69

Log Scan Limit 70

Monitoring Period 62

Multi-Node Monitoring Mode 58

Node Status 67

Node Type 58

Paths 57

PATROL Agent 42

Policy Backup Restriction 72Customize

Monitored Mount Requests 68

Mount Request Date/Time Format 68

Mount Request Status 68

Mount Requests 68

- D -Daemons

Delete 60

Disable 60

Enable 60

Status Configuration 65Data Collection for Jobs

Force 75Data Collectors

Force 75Databases

Delete 60

Disable 60

Enable 60Debug

Disable 77

Enable 77

End 77

Files 77

Path 77Delete

Clients 60

Daemons 60

Databases 60

Logs 60

Policies 60

Policy Clients 60

Robotic Drives 60

Robotic Libraries 60

Standalone Drives 60

Storages 60

Volume Pools 60Disable

Clients 60

Daemons 60

Databases 60

Debug 77

Logs 60

Policies 60

Policy Clients 60

Robotic Drives 60



Storages 60

Volume Pools 60Discoveries

Force 75Discovery

Verify 47Disk Space

Requirements 20

Index 153

Version 2.8.03


- E -Enable

Clients 60

Daemons 60

Databases 60

Debug 77

Logs 60

Policies 60

Policy Clients 60

Robotic Drives 60



Storages 60

Volume Pools 60

- F -Failover Group Name 58

Files 22

ins_ALL_<version>.tar 21

ins_WINDOWS_<version>.exe 21

Setup 22

setup.exe 23

setup.sh 23

uninstall.exe 35

uninstall.sh 35Filtering Options

Clients 60

Daemons 60

Databases 60

Logs 60

Policies 60

Policy Clients 60

Robotic Drives 60



Storages 60

Volume Pools 60Force

All Data Collectors 75

All Discoveries 75

Full Data Collection for Jobs 75

Selected Data Collectors 75

- G -Generate

Baselines 52

- H -HP-UX 15

- I -Improvement 8

InfoBox

Active 127

Application 85

Application Name 136

Application Version 136

Attempt 106

Available FS Space 117

Barcode 120

Binary Path 136

Client 106, 120

Collector Last End 83, 85, 86, 89, 91, 92,95, 97, 99, 101, 103, 106, 109, 111, 112, 115,117, 120, 122, 123, 126, 127, 132, 133, 142,144

Collector Last Start 83, 85, 86, 89, 91, 92,95, 97, 99, 101, 103, 106, 109, 111, 112, 115,117, 120, 122, 123, 126, 127, 132, 133, 142,144

Collector Name 83, 85, 86, 89, 91, 92, 95,97, 99, 101, 103, 106, 109, 111, 112, 115,117, 120, 122, 123, 126, 127, 132, 133, 142,144

Collector Next Start 83, 85, 86, 89, 91, 92,95, 97, 99, 101, 103, 106, 109, 111, 112, 115,117, 120, 122, 123, 126, 127, 132, 133, 142,144

Collector Status 83, 85, 86, 89, 91, 92, 95,97, 99, 101, 103, 106, 109, 111, 112, 115,117, 120, 122, 123, 126, 127, 132, 133, 142,144

Command 89

Completion Status 106

Control 95, 109

Copyright 136

Density 120

Index 154

Version 2.8.03


InfoBox

Description 85, 89, 92, 95, 99, 101, 109,117, 120, 123, 127, 133, 144

Device Host 95, 109

Disk Media ID 101

Disk Pool Name 101

Disk Type 101

Drive Index 95, 109

Duration 106

End 106

Exit Status 106

External Media ID 120

Files 106

Free Space 101

FS Percent Used 117

Group 133

Hardware 85, 123

High Watermark 99

Host Name 133, 136

Installation Path 85, 136

Job ID 106, 120

Job PID 106

Job Type 120

Keyword 127

Last Backup 92

Last Backup Duration 106

Last Backup End 106, 123, 127

Last Backup Files 106

Last Backup Job ID 92, 106, 123, 127

Last Backup Mode 92

Last Backup Size 106

Last Backup Start 106, 123, 127

Last Backup Status 123, 127

Last Full Backup End 123, 127

Last Full Backup Job ID 123, 127

Last Full Backup Start 123, 127

Last Incr Backup End 127

Last Incr Backup End Time 123

Last Incr Backup Job ID 123, 127

Last Incr Backup Start 123, 127

Last Purge 92, 117

Library Path 136

Log File Modification Time 117

Log File Size 117

Low Watermark 99

Master Server(s) 136

Max Jobs/Policy 127

Media ID 95, 109

Media Server 106, 120

Media Server(s) 136

Mode 120

Monitoring Mode 136

Monitoring Node 136

Multiple Data Stream 127

Name 85, 89, 92, 95, 99, 101, 109, 117,123, 127, 133

Node Name(s) 136

Node Type 136

Number of Read Mounts 101

Number of Write Mounts 101

Operating System 85, 123, 136

Operation 106

Owner 89, 106

Path 92, 95, 109, 117

PATROL Agent Version 136

Percent Completed 106

PID 89

Platform 136

Policy Name 106, 120, 123

Policy Type 106

PPID 89

Priority 106, 123, 127

Product Name 136

Product Release Date 136

Product Version 136

Raw Size 99

Recorded Media ID 120

Request ID 95, 109, 120

Request Time 120

Residence 127

Robot Drive Number 109

Robot Number 109

Robot Type 109

Schedule 106

Schedule End 106

Schedule Start 106

Schedule Type 106

Serial Number 95, 109

Size 106

Start 106

Status 85, 89, 95, 106, 109, 127

Storage Server 99, 101, 144

Storage Server Type 99, 144

Storage Unit 106, 120

Subtype 106

Support 136

Time Remaining 106

Total Capacity 101

Index 155

Version 2.8.03


InfoBox

Total FS Space 117

Type 95, 106, 109, 127

Up/Down State 99, 101, 144

Usable Size 99

Used Percent 101

User 95, 109, 120, 133

Version 85

Volume Group 120

Volume Pool 127

Web Site 136Install / Un-install 22, 35

BMC Software Installation Utility 21

Log 23

Packages 22

Procedure 23

Setup Files 22Instance Limits

Check 47Integration

BMC ProactiveNet 50Integration Service Agent 50

Introduction 22

Issues

Fixed 8

- J -Job Alerts

Acknowledge 80Jobs

Configure 62


Status Configuration 65Jobs Exit Status Filter

Configure 71

- K -Key Performance Indicators


Manage 52KM

Configure 45

Initial Setup 49

Load 41, 50

Preload 42

Preloaded 43, 44

Unload 43, 44

User Account 45KPI


Manage 52

- L -Linux 15

Load

KM 41, 50

PATROL Central 41Log Alerts

Acknowledge 80Log Error Filter

Configure 69Log Scan Limit

Configure 70Logs

Delete 60

Disable 60

Enable 60

- M -Manage

Baselines 52

Key Performance Indicators 52

KPI 52Managed Node

Status Configuration 65Master Server

Configure 58Master/Media Server

Start 54

Stop 55Media Server

Configure 58Menu Commands

About 136

Acknowledgement 103, 106, 117

Administration 109, 120, 122, 136

Alarms 103, 117

Alert 106

All 103, 117

Assign 120

Index 156

Version 2.8.03


Menu Commands

Assign All 122

Client 85

Client Status 85

Clients 83

Clients Status 83

Configuration 83, 85, 86, 89, 91, 92, 95,97, 99, 101, 103, 112, 115, 117, 122, 123,126, 127, 132, 133, 142, 144

Daemon 89

Daemon List 86

Daemon Status 89

Daemons 86

Daemons Status 86

Database 92

Database Backup Information 91

Databases 91

Debug 136

Deny 120

Deny All 122

Disk Pool 99

Disk Pool Up/Down Status 99

Disk Pools 144

Disk Pools Up/Down Status 142, 144

Disk Volume 101

Disk Volume Up/Down Status 101

Disk Volumes 99

Disk Volumes Up/Down Status 99, 142, 144

Drive Cleaning Statistics 95, 97, 111

Force Discovery 136

Force Full Collection 103

Instance Limits 136

Jobs 103

Jobs Alert Acknowledgement 103

Jobs Erroneous Exit Status 103

Jobs Status 103

KM Status 136

Log 117

Log Alert Acknowledgement 117

Log Filter 117

Log Scan Limit 117

Login 136

Logs 115

Logs Alert Acknowledgement 115

Logs Filter 115

Logs Scan Limit 115

Media List 133

Messages List 115

Monitoring Mode 136

Mount Request Date/Time Format 122

Mount Requests 122

Mount Requests Status 122

Node Status 136

Node Type 136

Offline Drive 109

Online Drive 109

Paths 136

Pending Requests 122

Policies 126

Policies Backup Restriction 126

Policies Status 126

Policy 127

Policy Backup Restriction 127

Policy Client 123

Policy Clients 127

Policy Schedule 127

Policy Status 127

Preloading 136

Refresh Parameters 136

Refresh Process Cache 136

Reload Commands 136

Reports 86, 91, 95, 97, 111, 112, 115, 122,127, 133

Resubmit 120

Resubmit All 122

Robotic Drive 109

Robotic Drive Status 109

Robotic Drives 112

Robotic Drives Status 111, 112


Robotic Libraries Status 111

Robotic Library 112

Robotic Library Contents 112

Robotic Library Status 112

Standalone Drives 95, 97

Standalone Drives Status 95, 97

Start Master Server 136

Start Media Server 136

Stop Master Server 136

Stop Media Server 136

Storage 144

Storage Up/Down Status 144

Storages 142

Storages Up/Down Status 142

Volume Pool 133

Volume Pools 132

Warnings 103, 117Monitor Type 50

Index 157

Version 2.8.03


Monitored Mount Requests

Customize 68Monitoring Period

Configure 62

Jobs 62

Mount Requests 62Mount Request

Acknowledge 55Mount Request Date/Time Format

Customize 68Mount Request Status

Customize 68Mount Requests

Configure 62

Customize 68


Status Configuration 65Multi-Node Monitoring Mode

Configure 58

- N -NBU_CLIENT

Application Class 85NBU_CLIENT_CONTAINER

Application Class 83NBU_DAEMON

Application Class 89NBU_DAEMON_CONTAINER

Application Class 86NBU_DATABASE

Application Class 92NBU_DATABASE_CONTAINER

Application Class 91NBU_DEVICE

Application Class 95, 109NBU_DEVICE_CONTAINER

Application Class 97NBU_DPOOL

Application Class 99NBU_DVOLUME

Application Class 101NBU_JOB

Application Class 106NBU_JOB_CONTAINER

Application Class 103NBU_LIBRARY

Application Class 112


Application Class 111NBU_LOG

Application Class 117NBU_LOG_CONTAINER

Application Class 115NBU_MOUNT

Application Class 120NBU_MOUNT_CONTAINER

Application Class 122NBU_PCLIENT

Application Class 123NBU_POLICY

Application Class 127NBU_POLICY_CONTAINER

Application Class 126NBU_POOL

Application Class 133NBU_POOL_CONTAINER

Application Class 132NBU_SERVER

Application Class 136NBU_STORAGE

Application Class 144NBU_STORAGE_CONTAINER

Application Class 142New features 8

Node Status

Configure 67Node Type

Configure 58

Master Server 58

Media Server 58

- O -Operating Systems

Linux 21, 22, 23, 35

Unix 21, 22, 35

Windows 21, 22, 23, 35Options

Common services 23

Console Systems role 23

Managed System 23

View Log 23Oracle Solaris Cluster 58

Overview 10

Index 158

Version 2.8.03


- P -Parameter

NBULoginStatus 45Parameters 82

BURequestCollectorExecTime 122

ExtraFilesList 136

NBUClientCollector 136

NBUClientCollectorExecTime 83

NBUClientDetails 83

NBUClientState 85

NBUClientStatus 85

NBUClientSummary 85

NBUCreateDistribution 136

NBUDaemonCollector 136

NBUDaemonCollectorExecTime 86

NBUDaemonCPUDuration 89

NBUDaemonCPUUtilization 89

NBUDaemonDetails 86

NBUDaemonMemorySize 89

NBUDaemonProcessCount 89

NBUDaemonState 89

NBUDaemonStatus 89

NBUDaemonSummary 89

NBUDatabaseBackupElapsed 91, 92

NBUDatabaseCollector 136

NBUDatabaseCollectorExecTime 91

NBUDatabaseDetails 91

NBUDatabaseFSSpaceUsedPercent 92

NBUDatabaseSpaceAvailable 92

NBUDatabaseSpaceGrowthRate 92

NBUDatabaseSpaceUsed 92

NBUDatabaseSpaceUsedPercent 92

NBUDatabaseStatus 91

NBUDatabaseSummary 92

NBUDPoolSummary 99

NBUDPoolUpDownState 99

NBUDPoolUpDownStatus 99

NBUDPoolVolumeCount 99

NBUDriveCollector 136

NBUDriveCollectorExecTime 97

NBUDriveDetails 97

NBUDriveState 95

NBUDriveStatus 95

NBUDriveSummary 95

NBUDriveThroughput 95

NBUDVolumeReadStreamCount 101

NBUDVolumeSpaceAvailable 101

NBUDVolumeSpaceGrowthRate 101

NBUDVolumeSpaceUsed 101

NBUDVolumeSpaceUsedPercent 101

NBUDVolumeSummary 101

NBUDVolumeUpDownState 101

NBUDVolumeUpDownStatus 101

NBUDVolumeWriteStreamCount 101

NBUFileExcludeList 123

NBUFileIncludeList 123

NBUJobActiveBackupCount 103

NBUJobActiveBackupReduction 103

NBUJobActiveCount 103

NBUJobActiveNonBackupCount 103

NBUJobCollector 136

NBUJobCollectorExecTime 103

NBUJobDetails 103

NBUJobDuration 106

NBUJobFileCount 106

NBUJobQueuedBackupCount 103

NBUJobQueuedBackupReduction 103

NBUJobSize 106

NBUJobState 106

NBUJobStatus 106

NBUJobSummary 106

NBUJobText 106

NBUJobThroughput 106

NBULibraryCollector 136

NBULibraryCollectorExecTime 111

NBULibraryDetails 111

NBULibraryMediaAssignedCount 112

NBULibraryMediaAvailableCount 112

NBULibraryMediaAvailablePercent 112

NBULibraryMediaCleaningLeft 112

NBULibraryMediaCount 112

NBULibraryMediaScratchCount 112

NBULibraryMediaScratchPercent 112

NBULibraryMediaUnassignedCount 112

NBULibraryMediaUnassignedPercent 112

NBULibraryState 112

NBULibraryStatus 112

NBULibrarySummary 112

NBULibraryThroughput 112

NBULibraryUpDriveCount 112

NBULogAlarmCount 117

NBULogAlarmText 117

NBULogCollector 136

NBULogCollectorExecTime 115

NBULogDetails 115

Index 159

Version 2.8.03


Parameters 82

NBULogFSSpaceUsedPercent 117

NBULoginStatus 136

NBULogSpaceAvailable 117

NBULogSpaceGrowthRate 117

NBULogSpaceUsed 117

NBULogSpaceUsedPercent 117

NBULogSummary 117

NBULogText 117

NBULogWarningCount 117

NBULogWarningText 117

NBUMediaActiveCount 133

NBUMediaActivePercent 133

NBUMediaCount 133

NBUMediaEmptyCount 133

NBUMediaFrozenCount 133

NBUMediaFullCount 133

NBUMediaFullPercent 133

NBUMediaLoadedCount 133

NBUMediaReadOnlyCount 133

NBUMediaScratchCount 133

NBUMediaSuspendedCount 133

NBUMediaUnassignedCount 133

NBUMediaUnassignedPercent 133

NBUMediaUnknownCount 133

NBUMonitoringMode 136

NBUNodeStatus 136

NBUPClientBackupSummary 123

NBUPClientBackupThroughput 123

NBUPClientFullBackupDuration 123

NBUPClientFullBackupFileCount 123

NBUPClientFullBackupSize 123

NBUPClientIncrBackupDuration 123

NBUPClientIncrBackupFileCount 123

NBUPClientIncrBackupSize 123

NBUPClientSummary 123

NBUPolicyBackupElapsed 127

NBUPolicyBackupSummary 127

NBUPolicyBackupThroughput 127

NBUPolicyCollector 136

NBUPolicyCollectorExecTime 126

NBUPolicyDetails 126

NBUPolicyFullBackupDuration 127

NBUPolicyFullBackupElapsed 127

NBUPolicyFullBackupFileCount 127

NBUPolicyFullBackupSize 127

NBUPolicyIncrBackupDuration 127

NBUPolicyIncrBackupElapsed 127

NBUPolicyIncrBackupFileCoun 127

NBUPolicyIncrBackupSize 127

NBUPolicyState 127

NBUPolicyStatus 127

NBUPolicySuccBackupElapsed 127

NBUPolicySummary 127

NBUPoolCollector 136

NBUPoolCollectorExecTime 132

NBUPoolDetails 132

NBUPoolSpaceAvailable 133

NBUPoolSpaceGrowthRate 133

NBUPoolSpaceUsed 133

NBUPoolSpaceUsedPercent 133

NBUPoolSummary 133

NBURDriveState 109

NBURDriveStatus 109

NBURDriveSummary 109

NBURDriveThroughput 109

NBURequestCollector 136

NBURequestDetails 122

NBURequestElapsed 120

NBURequestState 120

NBURequestStatus 120

NBURequestSummary 120

NBUStorageCollector 136

NBUStorageCollectorExecTime 142

NBUStorageDetails 142

NBUStorageSummary 144

NBUStorageUpDownState 144

NBUStorageUpDownStatus 144

NBUUpdateAgent 136

Refresh 75Paths

Binary 57

Configure 57

Debug Directory 57

Home Directory 57

Library 57

Netbackup Installation 57

NetBackup Log Directory 57

Temp Directory 57PATROL

Agent 45

PATROL Agent 43

PATROL Agent system 20

PATROL Central Console 43, 44

PATROL Central Console Server system 20

PATROL Central Web Server system 20

PATROL Console 43, 44

PATROL Console system 20

Index 160

Version 2.8.03


PATROL Agent

Configure 42

Restart 49PATROL Console 41

Restart 49Permissions

Access 15Platform

Upgrade 40Platforms

Unix 45Policies

Delete 60

Disable 60

Enable 60Policy Backup Restriction

Configure 72Policy Clients

Delete 60

Disable 60

Enable 60Preload

KM 42Preloaded

KM 43, 44Prepare

Debug Files 77ProactiveNet 50

PW Commands 51

- R -Refresh

Parameters 75Release Notes 8

Reload

Commands 76remote PATROL Agent Checking 58

Reports

Available Media 132Requirements

Additional 13

BMC ProactiveNet Performance ManagementPortal 13

BMC Software PATROL Agent 13

BMC Software PATROL Console 13

Disk Space 20

Security 15

Software 13

Symantec NetBackup™ 13

System 11Restart

PATROL Agent 49

PATROL Console 49Robotic Drives

Administration 56

Delete 60

Disable 60

Enable 60

Status Configuration 65Robotic Libraries

Delete 60

Disable 60

Enable 60

Status Configuration 65

- S -Security

Requirements 15Setup

Check 49

Initial 49

KM 49Solaris 15

Standalone Drives

Administration 56

Delete 60

Disable 60

Enable 60

Status Configuration 65Start

Master/Media Server 54Status Configuration

Clients 65

Daemons 65

Jobs 65

Managed Node 65

Mount Requests 65

Robotic Drives 65


Standalone Drives 65Stop

Master/Media Server 55Storages

Delete 60

Index 161

Version 2.8.03


Storages

Disable 60

Enable 60Sudo 45

User 15Support

Customer Support 149

Email 149

Technical 149

Telephone 149

Web Site 149Symantec NetBackup

Administer 54System

HP-UX 11

IBM AIX 11

Microsoft Windows 11

Oracle Solaris 11

Red Hat Linux 11

Requirements 11

- T -Thresholds

Customize 51

Import 51Troubleshooting 145

- U -Unix 45

Unload

KM 43, 44Upgrade

Platform 40

- V -Verify

Application Discovery 47Veritas Cluster File System 58

Veritas Cluster Server 58

Volume Pools

Delete 60

Disable 60

Enable 60

- W -Warning

Acknowledge 80Warning Filter State Rules 65

What's new 8

About BMC® SoftwareBMC Software, Inc. NYSE:BMC, is a leading provider of enterprise managementsolutions that empower companies to manage their IT infrastructure from abusiness perspective. Delivering Business Service Management, BMC Softwaresolutions span enterprise systems, applications, databases, and servicemanagement. Founded in 1980, BMC Software has offices worldwide and fiscal2004 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 key monitoring solutions specifically designed to expand thecapabilities of BMC Performance Manager, thus enabling up to 100% coverage ofany infrastructure. Sentry Software specializes in single solutions for multi-platform monitoring of hardware, custom applications or any IT component, andblackout windows. Sentry Software products are deployed in 45 countries acrossthe globe and lead the list of BMC Software’s third-party product sales. For more

information about Sentry Software, please visit www.sentrysoftware.net.

223453

Symantec NetBackup for PATROL Version 2.8 · Symantec NetBackup KM for PATROL NBU_DAEMON ... In...

Documents

Transcript of Symantec NetBackup for PATROL Version 2.8 · Symantec NetBackup KM for PATROL NBU_DAEMON ... In...