symantec netbackup for patrol version 2.8 - sentry … · nbu_daemon ... loaded media. nbu-424:...
TRANSCRIPT
Symantec NetBackup KM forPATROL
STORAGE MONITORING
USER DOCUMENTATION
Version 2.8.04
September 2015
Contacting BMC Software
You can access the BMC Software Web site at http://www.bmc.com. From this Web site, you canobtain information about the company, its products, corporate offices, special events, and careeropportunities.
United States and Canada
Address BMC Software, Inc.2101 CityWest Blvd. Houston TX77042-2827
Telephone 1 (713) 918 8800 or 1 (800) 841 2031 (Toll Free)
Copyright 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.
All other trademarks belong to their respective companies.
BMC Software considers information included in this documentation to be proprietary andconfidential. Your use of this information is subject to the terms and conditions of the applicableEnd User License Agreement for the product and the proprietary and restricted rights noticesincluded in this documentation.
Restricted Rights Legend
U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVEDUNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any dataand computer software by the U.S. Government is subject to restrictions, as applicable, set forthin FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, andDFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC Software,Inc., 2101 CityWest Blvd., Houston, TX 77042-2827, USA. Any contract notices should be sent to thisaddress.
2
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Customer Support
You can obtain technical support by using the Support page on the BMC Software Web site or bycontacting Customer Support by telephone or e-mail.
Support Web Site
You can obtain technical support from BMC Software 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this Web site, you can:
Read overviews about support services and programs that BMC Software offers
Find the most current information about BMC Software products
Search a database for problems similar to yours and possible solutions
Order or download product documentation
Report a problem or ask a question
Subscribe to receive e-mail notices when new product versions are released
Find worldwide BMC Software support center locations and contact information, including e-mail addresses, fax numbers, and telephone numbers
You can also access product documents and search the Knowledge Base for help with an issue at http://www.sentrysoftware.com
Support by Telephone or E-mail
In the United States and Canada, if you need technical support and do not have access to theWeb, call 800 537 1813. Outside the United States and Canada, please contact your local supportcenter for assistance. To find telephone and email contact information for the BMC Softwaresupport center that services your location, refer to the Contact Customer Support section of theSupport page on the BMC Software Web site at http://www.bmc.com/support_home.
3
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
4
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Table of Contents.....................................................................................................................................................................................13Requirements
.......................................................................................................................................................................................13System Requirements
.......................................................................................................................................................................................14Software Requirements
.......................................................................................................................................................................................17Security Requirements
.......................................................................................................................................................................................22Disk Space Requirements
.....................................................................................................................................................................................23Getting the BMC Software Installation Utility
.....................................................................................................................................................................................24Packages
.....................................................................................................................................................................................24Extracting the Setup Files
.....................................................................................................................................................................................27Installing Symantec NetBackup KM for PATROL
.....................................................................................................................................................................................39Uninstalling Symantec NetBackup KM for PATROL
.....................................................................................................................................................................................44Upgrading the Platform
.....................................................................................................................................................................................44Loading/Unloading the KM
.......................................................................................................................................................................................45Loading the KM
......................................................................................................................................................................45Loading the KM on PATROL Console
......................................................................................................................................................................45Loading the KM on PATROL Central
......................................................................................................................................................................46Configuring the PATROL Agent to Preload the KM
.......................................................................................................................................................................................47Unloading the KM
......................................................................................................................................................................47Unloading the KM from the PATROL Agent
......................................................................................................................................................................48Unloading the KM from the PATROL Console
......................................................................................................................................................................48Unloading the KM from the PATROL Central Console
.....................................................................................................................................................................................49Performing Post-Installation Operations
.......................................................................................................................................................................................49Configuring the KM User Account
.......................................................................................................................................................................................51Verifying Application Discovery
.......................................................................................................................................................................................51Checking the Instance Limits
.......................................................................................................................................................................................53Checking the Initial Setup
.......................................................................................................................................................................................53Restarting PATROL Agent and PATROL Console
.....................................................................................................................................................................................56Integrating with BMC Portal
.....................................................................................................................................................................................56Integrating with BMC ProactiveNet Performance Management 8.5.x and 8.6.x
.......................................................................................................................................................................................57Creating and Importing an Adapter for a BMC PATROL KM
.......................................................................................................................................................................................58Updating an Adapter for a BMC PATROL KM
.......................................................................................................................................................................................58Importing and Customizing Thresholds
.......................................................................................................................................................................................59Managing Baselines and Key Performance Indicators
5
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
.....................................................................................................................................................................................63Administering Symantec NetBackup
.......................................................................................................................................................................................63Starting Master/Media Server
.......................................................................................................................................................................................64Stopping Master Media Server
.......................................................................................................................................................................................64Assigning, Denying, or Resubmitting Mount Requests
.......................................................................................................................................................................................65Bringing Standalone Drives Online or Offline
.......................................................................................................................................................................................65Bringing Robotic Drives Online or Offline
.....................................................................................................................................................................................66Configuring the KM
.......................................................................................................................................................................................66Configuring Paths
.......................................................................................................................................................................................67Specifying the Node Type
.......................................................................................................................................................................................67Configuring the Multi-Node Monitoring Mode
.......................................................................................................................................................................................69Filtering Elements to Monitor
.......................................................................................................................................................................................71Configuring Monitoring Periods
.......................................................................................................................................................................................74Configuring the Elements Status
.......................................................................................................................................................................................76Configuring the Node Status
.......................................................................................................................................................................................77Configuring Mount Requests Date/Time Format
.......................................................................................................................................................................................78Configuring the Log Filter
.......................................................................................................................................................................................80Configuring the Log Scan Limit
.......................................................................................................................................................................................81Configuring Jobs Erroneous Exit Status Filter
.......................................................................................................................................................................................82Configuring Policy Backup Restriction
.......................................................................................................................................................................................83Configuring Alert Acknowledgement
.......................................................................................................................................................................................84Refreshing Parameters
.......................................................................................................................................................................................86Reloading Commands
.......................................................................................................................................................................................86Enabling the Debug Mode
.....................................................................................................................................................................................90Acknowledging Alerts
.....................................................................................................................................................................................91Generating Reports
.....................................................................................................................................................................................94Classes and Parameters
.......................................................................................................................................................................................95NBU_CLIENT_CONTAINER
.......................................................................................................................................................................................97NBU_CLIENT
.......................................................................................................................................................................................98NBU_DAEMON_CONTAINER
.......................................................................................................................................................................................101NBU_DAEMON
.......................................................................................................................................................................................103NBU_DATABASE_CONTAINER
.......................................................................................................................................................................................105NBU_DATABASE
.......................................................................................................................................................................................108NBU_DEVICE
.......................................................................................................................................................................................110NBU_DEVICE_CONTAINER
.......................................................................................................................................................................................112NBU_DPOOL
.......................................................................................................................................................................................114NBU_DVOLUME
6
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
.......................................................................................................................................................................................116NBU_JOB_CONTAINER
.......................................................................................................................................................................................119NBU_JOB
.......................................................................................................................................................................................123NBU_LDEVICE
.......................................................................................................................................................................................125NBU_LIBRARY_CONTAINER
.......................................................................................................................................................................................127NBU_LIBRARY
.......................................................................................................................................................................................130NBU_LOG_CONTAINER
.......................................................................................................................................................................................132NBU_LOG
.......................................................................................................................................................................................135NBU_MOUNT
.......................................................................................................................................................................................138NBU_MOUNT_CONTAINER
.......................................................................................................................................................................................140NBU_PCLIENT
.......................................................................................................................................................................................143NBU_POLICY_CONTAINER
.......................................................................................................................................................................................144NBU_POLICY
.......................................................................................................................................................................................150NBU_POOL_CONTAINER
.......................................................................................................................................................................................151NBU_POOL
.......................................................................................................................................................................................155NBU_SERVER
.......................................................................................................................................................................................162NBU_STORAGE_CONTAINER
.......................................................................................................................................................................................164NBU_STORAGE
.....................................................................................................................................................................................167Troubleshooting
.....................................................................................................................................................................................170Impact on Resources
.....................................................................................................................................................................................171Customer Support
Release Notes for v2.8.04
8
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
What's NewNBU-356: Two new parameters NBUMediaLoadedEmptyCount andNBUMediaLoadedEmptyPercent have been added to the NBU_POOL application class, tomonitor the number of empty media loaded to a robotic library and its percentage out allloaded media.
NBU-424: Symantec NetBackup KM for PATROL now supports Symantec NetBackup v7.6.
NBU-425: Symantec NetBackup KM for PATROL now supports Windows 2012.
Changes and ImprovementsNBU-355: To avoid redundancy, the NBUMediaEmptyCount parameter of the NBU_POOLapplication class has been removed since the NBUMediaUnassignedCount parameter nowreads the correct empty media count.
Fixed IssuesNBU-342: A compatibility issue prevented the KM to operate when the PATROL Agentv9.0.20i was run with the PATROL Config Cache support.
NBU-357: False alerts were triggered on the NBUClientStatus parameter when the KM failedto ping the NetBackup client.
NBU-358: On Windows systems, if the PATROL Agent installation path contained spaces,custom KM scripts and commands with output redirection failed.
NBU-359: No statistics were collected for the library media on Linux platforms.
NBU-364: Scripts and commands used by NetBackup KM now support bash shell platforms.
NBU-369: A permission denied message was displayed when NetBackup KM generatedreports if the KM temporary files could not be created with the provided credentials.
NBU-377: Alerts were sometimes not triggered for missing NetBackup daemons.
NBU-386: False alerts were triggered on the NBUDatabaseBackupElapsed parameter whenthe last catalog database backup could not be found.
NBU-387: Alarms were triggered on the NBUDPoolUpDownStatus and NBUNodeStatusparameters even though no disk pools were configured on the NetBackup Media Server.
NBU-436: The NBULibraryMediaScratchPercent and NBULibraryMediaAvailablePercentparameters were not properly calculated and occasionally exceeded 100%.
NBU-443: The Sudo configuration in the sudoers file is modified for Solaris, HP-UX, AIX andLinux to prevent NetBackup commands failures (see Security Requirements).
NBU-487: Clients were not discovered correctly on Symantec NetBackup v7.6. The relevantcommand has been modified to fully support the new Symantec NetBackup version.
NBU-493: Full and incremental domain level backup summary parameters were not setcorrectly, preventing the product to properly monitor backups at the policy and policy clientlevels.
NBU-501: The status report file of Symantec NetBackup KM for PATROL is now suffixed withthe Agent port number to avoid overwriting it when multiple virtual Agents are used.
NBU-502: The NBULoginStatus parameter was in warning due to an incorrect configurationvariable used while checking the active cluster node.
9
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBU-503: The Microsoft Cluster active node was not properly detected when the KM wasoperating in multi-node monitoring mode.
NBU-516: The main discovery cycle was irregular due to an asynchronous default KMdiscovery interval. It is now reduced to 30 seconds to avoid such irregularity.
Overview
11
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Symantec NetBackup KM for PATROL monitors your Symantec NetBackup application within acentralized management console to ensure its runs efficiently 24 hours a day.
The KM more especially monitors the:
Server availability: status, memory and CPU time consumption, etc.
Jobs: status, duration, data throughput and time elapsed since last backup, comparativestatistics, etc.
Log Files: size, content, growth rate, file system space utilization, etc.
Robotic libraries and drives: library and drive status, throughput, loaded mediaidentification, etc.
Disk storage and volume pools: space utilization, status, count, etc.
Catalog database: space utilization, file system monitoring, time since the last databasebackup, etc.
Client: connectivity, metrics from the last successful backup, etc.
All the information collected is grouped into application classes and displayed in the PATROLConsole. Alarms and warnings inform you when a suspicious behavior is detected; thus allowingyou to quickly and clearly identify peaks, troughs and trends in the performance of your backupresources.
Refer to the Reference Guide for more information about the application classes.
Preparing for Installation
13
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
This chapter provides information about the tasks that must be performed before you startinstalling Symantec NetBackup KM for PATROL. Make sure to carefully read the followingsections 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, 11
HP-UX 11.00, 11.11, 11iv2, 11iv
IBM® AIXTM 5.1, 5.2, 5.3, 6.1
Red Hat® Linux® 7.2
Microsoft® Windows® 2003, 2008, 2008 R2, 2012
If the operating system is upgraded (or downgraded) at a later date, you will need to reload commandsfor the NetBackup KM. Refer to Upgrading the Platform.
14Requirements
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Software RequirementsSymantec NetBackup KM for PATROL supports:
Software Version
Symantec NetBackup™ 5.0, 5.1, 6.0, 6.5, 7, 7.1, 7.5, 7.6
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
BMC TrueSight Operations Management 10
If the operating system is upgraded (or downgraded) at a later date, you will need to reload commandsfor the NetBackup KM. Refer to Upgrading the Platform.
If you're running the NetBackup KM with sudo user account, or on AIX, LINUX, or MicrosoftWindows x64 managed nodes, please verify these additional software requirements:
Purpose Software Version
When running NBU KM with sudo useraccount on Solaris, HP-UX, AIX or Linuxmanaged nodes
Sudo (superuser do) 1.6.7 or later
When running NBU KM on AIX managednodes
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 registry keysfrom PATROL Agent. Access the above patch site from the managed node to obtain the correct patchfor that platform.
15 Requirements
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
If Korn Shell cannot be installed, create soft link f rom /bin/ksh to /bin/bash, using: ln –s /bin/bash /bin/ksh.
16Requirements
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Changes Required
No changes need to be done to Symantec NetBackup to use Symantec NetBackup KM forPATROL.
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 isinstalled. This adjustment will allow the data collectors to execute without incurring an internalscheduling 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 ofthe following single line PSL command through the PATROL Console OS> prompt to update thistuning 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 be insuf f icient. In such situations, error messages will appear on the PATROL Console SystemOutput Window (SOW) reporting that some NetBackup KM data collectors are in an inf inite loop. In thiscase you can set the tuning variable to 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) shouldbe able to read and write to these pconfig variables at anytime. If Access Control List (ACL) isused to control which users are authorized to connect to a PATROL Agent, please make sure thatthe mode for PATROL Agent user includes “C” in the PATROL Agent variable “/AgentSetup/accessControlList”. Please refer the PATROL Agent Ref erence Manual for more details.
To support bash shell platforms when ksh is not installed
To collect Pool stats when ksh was not installed on UNIX/Linux servers, you need to create a softlink for /bin/ksh to /bin/bash:
ln –s /bin/bash /bin/ksh
17 Requirements
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Security RequirementsA user account with administrative privileges must be configured in BMC PATROL to read andexecute Symantec NetBackup application programs and access file systems. Depending on theoperating systems used, several options will be available.
The following user accounts can be used:
On Unix platforms:
a root user
a non-root user, such as patrol, that has sudo privileges on Symantec NetBackup toexecute application programs and access file systems
a non-root account, such as patrol, configured in Symantec NetBackup application toadminister the Symantec NetBackup application.
On Windows platforms:
an administrator user
a non-administrator account, such as patrol, configured in Symantec NetBackup applicationto administer the Symantec NetBackup application. Refer to the Symantec NetBackupSystem Administrator’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 userdo not expire using the utility nbac_cron.
The user login details are configured in the KM. The password is stored in the PATROL Agent in aDES encrypted format.
The encrypted password can be viewed by any user who has access to the PATROL Agent configurationvariables (pconfig). This user could then execute PSL statements using the encrypted password throughthe PATROL Console. This can be prevented by setting up an appropriate Access Control List (ACL) forusers. Please refer to the PATROL Agent Reference Manual for details on how to set up an ACL.
18Requirements
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Access Permissions
The NetBackup KM user needs “read & execute” permission to executable and library files underthe paths listed below. The Symantec NetBackup installation path INSTALL_PATH, referenced inthe tables below is normally /usr/openv or /opt/VRTSnetbp (on Unix) or C:\Program Files\Veritas (on Microsoft 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 executepermissions to the following cluster commands:
/opt/VRTSvcs/bin/hagrp (in Veritas Cluster Server)
vxdctl (in Veritas Cluster File System)
/usr/cluster/bin/clrg (in Oracle Solaris Cluster)
The NetBackup KM includes some scripts which should be executable by the PATROL Agent userand the NetBackup KM user. These scripts are stored under KM_HOME path, normallyPATROL_HOME/lib/NBU.
19 Requirements
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
To list all OS commands used by the NetBackup KM, execute the following PSL code from thePATROL Console, 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 the copiedlog file will be removed. This may increase the file system usage under KM_TEMP temporarily duringthis activity.
20Requirements
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
On Windows platforms the Symantec NetBackup installation is identified by checking theMicrosoft Windows Registry: HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\
The configured login user should have sufficient privileges to run regedit command on themanaged node.
Sudo User for Operating System Access
If a non-root user with sudo privileges is preferred as the KM user, configure the account as asudoer through the visudo utility using code appropriate for your platform as detailed below.This user should be able to execute NetBackup commands and OS commands listed in above.
The code below also applies to all non-root users who may execute NetBackup KMadministration and report menu commands using their sudo privileges. The KM accepts any non-root user with the following sudo configuration in the sudoers file. Please replace user1, user2,user3 with appropriate KM user names. The Symantec NetBackup installation pathINSTALL_PATH, referenced below is normally /usr/openv or /opt/VRTSnetbp and PATROL_HOMEis 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 NetBackup commands.To prevent unauthorized access, ensure this user is only used within the KM and not made public forgeneral use.
Entering the non-root sudo user with ‘Use Sudo’ option selected in to the login configuration dialog,before updating the sudoers file, will generate sudo errors. Also if the sudo user is configureddifferently, the KM may run sudo commands using incorrect sudo settings, which may expose the sudouser password.
On Solaris
User_Alias NBUKMUSERS = user1, user2, user3
Defaults:NBUKMUSERS !lecture,!authenticate,!requiretty,\
env_keep+="PATH LD_LIBRARY_PATH INSTALL_PATH KM_HOME KM_TEMP",env_reset
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/*,\
PATROL_HOME/lib/NBU/*,PATROL_HOME/bin/*
21 Requirements
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
user1, user2, user3 must be replaced with username(s) used by the KM; INSTALL_PATH andPATROL_HOME with the relevant paths.
On HP-UX
User_Alias NBUKMUSERS = user1, user2, user3
Defaults:NBUKMUSERS !lecture,!authenticate,!requiretty,\
env_keep+="PATH SHLIB_PATH INSTALL_PATH KM_HOME KM_TEMP",env_reset
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/*,\
PATROL_HOME/lib/NBU/*,PATROL_HOME/bin/*
user1, user2, user3 must be replaced with username(s) used by the KM; INSTALL_PATH andPATROL_HOME with the relevant paths.
On AIX & Linux
User_Alias NBUKMUSERS = user1, user2, user3
Defaults:NBUKMUSERS !lecture,!authenticate,!requiretty,\
env_keep+="PATH LIBPATH INSTALL_PATH KM_HOME KM_TEMP",env_reset
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/*,\
PATROL_HOME/lib/NBU/*,PATROL_HOME/bin/*
user1, user2, user3 must be replaced with username(s) used by the KM; INSTALL_PATH andPATROL_HOME with the relevant paths.
22Requirements
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 willgenerate approximately 500 KBytes of history data per day. An enterprise installation ofSymantec NetBackup on a master server with multiple media servers, clients, robotic libraries,and standalone drives will generate more history data (as per other KMs used by the PATROLAgent). These history data files are recycled by PATROL depending on the PATROL Agent historyretention period.
During execution, the KM creates and maintains temporary files under KM_HOME, KM_TEMPand KM_DEBUG paths. By default they are all under PATROL_HOME/lib/NBU, wherePATROL_HOME path is normally opt/bmc/Patrol3/ (on Unix) or C:\Program Files (x86)\BMCSoftware\Patrol3\ (on Microsoft 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.
23 Requirements
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Getting the BMC Software InstallationUtilityIn order to install Symantec NetBackup KM for PATROL, you need the latest version of the BMCSoftware Installation Utility. You can download the latest Installation Utility from the BMCSoftware EPD (electronic product download) from: http://webapps.bmc.com/signon/content/logon.jsp on the BMC Software Website, or from the Symantec NetBackup KM for PATROL pageon the Sentry Software Website
Choose the appropriate package depending on the platform you plan to install SymantecNetBackup KM for PATROL on:
For UNIX/Linux systems: ins_ALL_<version>.tar
For Windows systems: ins_WINDOWS_<version>.exe
The packages are valid for all the PATROL components: Agent, Console, Console Server, etc.
Place the Installation Utility package in the same folder as the Symantec NetBackup KM forPATROL packages.
24Getting the BMC Software Installation Utility
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
PackagesThe Symantec NetBackup KM for PATROL packages are available on the Sentry Software Website.
There are two packages, each of which can be used to install the KM on every PATROLcomponent (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 forPATROL on the 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
26
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 bySymantec NetBackup KM for PATROL.
27
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Installing Symantec NetBackup KMfor PATROLInstalling Symantec NetBackup KM for PATROL is an automated process managed by a wizard.The wizard goes through the necessary steps to install Symantec NetBackup KM for PATROL andall files associated with it. You are simply prompt for the product's folder location and theproduct/components to install.
Browse to the bmc_products folder where the files have been extracted (both SymantecNetBackup KM for 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 Alert
28Installing Symantec NetBackup KM for PATROL
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
2. The welcome screen of the installer appears. Click Next to continue.
Installation Wizard - Step 2: Welcome
29 Installing Symantec NetBackup KM for PATROL
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
3. Read the license agreement, click the Accept option and then click Next to continue.
Installation Wizard - Step 3: Reviewing License Agreement
30Installing Symantec NetBackup KM for PATROL
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
4. Select Install the products on this computer now and click Next to continue.
Installation Wizard - Step 4: Selecting Installation Options
31 Installing Symantec NetBackup KM for PATROL
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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
32Installing Symantec NetBackup KM for PATROL
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
6. Select Default. Installing Symantec NetBackup KM for PATROL does not require anycustomization. Click Next to continue.
Installation Wizard - Step 6: Selecting an Installation Type
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 oron PATROL Central – Web Edition.
Click Next to continue.
33 Installing Symantec NetBackup KM for PATROL
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Installation Wizard - Step 7: Selecting Roles
Select as many options as required.
34Installing Symantec NetBackup KM for PATROL
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
8. Check the Symantec NetBackup KM for PATROL box to install the KM (it should be selectedby default). Click Next to continue.
Installation Wizard - Step 8: Selecting Products and Components
35 Installing Symantec NetBackup KM for PATROL
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
9. Review the installation parameters and click Start Install to launch the installationprocedure.
Installation Wizard - Step 9: Reviewing Installation Options
36Installing Symantec NetBackup KM for PATROL
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
10. The setup program displays the actions performed and indicates the percentage ofcompletion.Once the installation complete, click Next to view the installation results.
Installation Wizard - Step 10: Installation Status
37 Installing Symantec NetBackup KM for PATROL
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
11. The wizard displays the installation results.Click View Log to display a detailed log of the installation procedure. Click Next and thenFinish to exit the setup program.
Installation Wizard - Step 11: Installation Results
12. Click the Finish button to complete and close the installation wizard.
38Installing Symantec NetBackup KM for PATROL
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Installation Wizard - Step 12: Completing 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 button allows you to stop the installation procedure.
39 Installing Symantec NetBackup KM for PATROL
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Uninstalling Symantec NetBackup KMfor PATROLUninstalling Symantec NetBackup KM for PATROL is an automated process managed by a wizard.The wizard goes through the necessary steps to remove Symantec NetBackup KM for PATROL andall files associated with it. You are simply prompt for the product's folder location and theproduct/components to 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 — Welcome Step
40Uninstalling Symantec NetBackup KM for PATROL
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
2. Specify the BMC Software products folder. See the BMC Software documentation for moreinformation about the BMC Software products folder.
Un-install Wizard — Specifying folder
41 Uninstalling Symantec NetBackup KM for PATROL
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
3. To uninstall the KM, select Symantec NetBackup KM for PATROL.
Un-install Wizard — Selecting Products and Components Directory
42Uninstalling Symantec NetBackup KM for PATROL
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
4. Click Start Uninstall.
Un-install Wizard — Reviewing Selected Products & components and start uninstalling
43 Uninstalling Symantec NetBackup KM for PATROL
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
5. A page displays the list of products/components processed and the percentage ofcompletion. Click Next to continue.
Un-install Wizard — Status
44Uninstalling Symantec NetBackup KM for PATROL
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 forthe NetBackup 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.
45 Loading/Unloading the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 ConsoleTo 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 willstart discovering the Symantec NetBackup environment. If the automatic discovery successfullyfinds the Symantec NetBackup master/media server installation, the NBU_SETUP instance will beinstantiated.
The automatic discovery may take up to 5 minutes to instantiate the NBU_SETUP instance.Look for any error messages on the PATROL Console System Output Window (SOW) during the initialdiscovery.
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 CentralTo load the KM on PATROL Central:
1. In the Console, right-click the Managed System and select Load Knowledge Modules... TheLoad Knowledge Modules wizard is displayed
2. 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 connectedselected managed systems will start discovering the Symantec NetBackup environment. If theautomatic discovery successfully finds the Symantec NetBackup master/media server
46Loading/Unloading the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
installation, the NBU_SETUP instance will be instantiated.
This automatic discovery may take up to 5 minutes to instantiate the NBU_SETUP instance. Look for anyerror messages on the PATROL Central System Output Window (SOW) during the initial discovery.
5. Load the NBU_LOAD.kml file on each PATROL Central Management Profile where NetBackupKM is to be loaded.
6. Configure the KM.
Configuring the PATROL Agent to Preload the KMIf you want Symantec NetBackup KM for PATROL to operate all the time, without a PATROLConsole connection, 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 f iles f rom the preloaded KMs list.
47 Loading/Unloading the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Unloading the KMThis section describes the procedures for unloading (not uninstalling) the NetBackup KM fromthe PATROL Agent, PATROL Console or PATROL Central Console. Read this section if you nolonger want to use some parts of the KM; if you want to completely uninstall the KM, refer tothe 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 AgentTo 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 NetBackupKM is to be unloaded.
You can also use the utility wpconf ig (on Microsoft Windows) or xpconf ig to unload the KM. You willthen have to remove NBU_LOAD.kml f rom the PATROL Agent conf iguration variable /AgentSetup/preloadedKMs.
The KM cannot be partially unloaded from the PATROL Agent using the above steps. If you need to unloadsome parts of the KM from the PATROL Agent, refer to the PATROL Agent Reference Manual.
48Loading/Unloading the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Unloading the KM from the PATROL ConsoleApplication classes are unloaded individually. This allows for a partial unloading of the KM toenable it to run as a reduced installation.
To unload the NetBackup KM completely or partially:
1. Remove the unwanted application classes that starts with NBU_ in the list of loadedapplication classes 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 beunloaded.
Unloading the KM from the PATROL Central ConsoleA KM can be unloaded from particular managed systems or for all systems across the monitoredenvironment. Application classes may be unloaded individually, or by selecting all classes atonce. This allows for a partial unloading of the KM to enable it to run as a reduced installation onsome or all of the managed systems.
To completely or partially unload the 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 appropriatemanaged systems, click Next> and Finish.
4. Repeat the above steps for each PATROL Central Management Profile where the NetBackupKM is to be unloaded.
49 Loading/Unloading the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Performing Post-InstallationOperationsIt is recommended to perform post installation checks once the KM is installed and loaded onthe PATROL Console to ensure it properly operates. Post-installation operations include:
Configuring the KM user account
Verifying:
the application discovery
the instance limits
the initial setup
Restarting the PATROL Agent and PATROL Console.
Configuring the KM User AccountA user account with administrative privileges must be configured in BMC PATROL to read andexecute Symantec NetBackup application programs and file systems. Depending on theoperating 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 toadminister the Symantec NetBackup application.
On Windows platforms, you can use the following user accounts:
50Performing Post-Installation Operations
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
an administrator user
a non-administrator account, such as patrol, configured in Symantec NetBackup applicationto administer 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”after the next data collection.
51 Performing Post-Installation Operations
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Verifying Application DiscoveryTo verify the application discovery:
1. Check that the NBU_SETUP instance is actually named Symantec NetBackup. If not, force afull discovery by right-clicking the NBU_SETUP instance > KM Commands > Force Discovery
2. Check that the application class instances are actually instantiated. The initial data collectionmay take some time depending on the complexity of your environment (up to one hour). Ifneeded, force a data collection by right-clicking the Symantec NetBackup instance > KMCommands > Refresh Parameters.
If Symantec NetBackup master/media server is configured in a clustered environment, you'llhave to enable Multi-node Mode monitoring.
Checking the Instance LimitsSymantec NetBackup KM for PATROL automatically sets the number of instances that will bedisplayed in the Console for each monitored elements. This configuration, set to offer maximumperformance, can however 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.
52Performing Post-Installation Operations
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
To modify the default configuration
1. In the Console, right-click the KM main icon > Configuration> Instance Limits
Configuring the Default Instance Limits
2. Enter the number of instances to be displayed in the console for each monitored element
3. To disable the monitoring of a specific application class, enter 0 in the relevant field
4. Click OK.
53 Performing Post-Installation Operations
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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> NodeType from the Symantec NetBackup instance.
3. Check the InfoBoxes and Parameters of all the NetBackup KM instances and verify that theyare properly set.
4. Under each container instance, open all detail parameters (text parameters with names inthe format NBU<Object>Details), and check for error messages.
5. Check the new value of NBULoginStatus set after completion of all data collection. If eitheris not in OK state, open the annotation point to determine the cause of the error.
6. After the KM has been running for at least an hour:
Right-click the KM main icon > KM commands > KM Status from the Symantec NetBackupinstance. A report is displayed, detailing information on the managed system. Checkthrough the report for any warnings or alarms. If any errors are found during any of theabove steps (including any incorrect data in Infoboxes or any warnings or alarms in the KMStatus report), determine the cause(s) and take steps to resolve these errors. You mayneed to refer to the User Guide, or contact Technical Support, attaching the KM Statusreport.
If needed, click Save As Task to open the report in a task window. You could later save it asa text file or print it.
7. The KM installed on the master server may monitor the same storage, disk pools, diskvolumes, robotic libraries & drives which are already monitored through the media servers.This may be unnecessary and can trigger duplicate alerts. You can disable these componentson either master server or media server by setting their instance limit to 0 (zero), using themenu Configuration> Instance Limits.
Restarting PATROL Agent and PATROL ConsoleRestarting the PATROL Agent and PATROL Console is optional but often a good practice toconfirm that the NetBackup KM operates correctly after restarting the PATROL Agent and/orPATROL Console.
In addition, the PATROL Agent restart will force all KM discoveries and data collections to startimmediately.
54Performing Post-Installation Operations
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Integrating the KM
56
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 ProactiveNetPerformance Management 8.5.x and8.6.xOverviewTo integrate a BMC PATROL KM into BMC ProactiveNet Performance Management 8.5.x or 8.6.x,you need to create a specific adapter. An adapter for BMC PATROL facilitates pulling ofperformance data from existing BMC PATROL solutions into BMC ProactiveNet. Using an Adapter,you can import BMC PATROL application classes (provided in a Knowledge Module –KM) intoBMC ProactiveNet. The Adapter periodically synchronizes the performance data collected bythese application classes into BMC ProactiveNet.
57 Integrating with BMC ProactiveNet PerformanceManagement 8.5.x and 8.6.x
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Creating and Importing an Adapter for a BMCPATROL KM
Creating an Adapter for a BMC PATROL KM
1. Open the BMC ProactiveNet Administration Console. The BMC ProactiveNet Administration Console
is displayed as shown in the following figure:
2. Right-click the Adapters folder and select Import Monitor Type and Add Adapter > BMCPATROL.
3. In the Configuration tab, enter the required information:
In the Instance Name field, enter a name for this instance of the Adapter that will performthe integration of the ‘targeted KM’ into BMC ProactiveNet.
Select the Agent where this instance of the Adapter will be executed
Enter the Integration Service Agent hostname or IP address
Enter the Integration Service Agent Port. The default port is 3182.
Enter the required credential to connect to the Integration Service Agent
4. Click Next to continue
5. Click Next to let the system load the BMC PATROL application classes.
6. Select the application classes to import
Unselecting will delete the application classes that have already been imported during a previousoperation. Application classes ready to be deleted are marked with a red x.
7. Click Next to start the import process. The system displays a summary of the application classimport, click Next to continue.
8. Select the application classes you wish to auto-synchronize with the Integration ServiceAgent.
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 toconfirm. The Adapter has been added to the Adapters folder of the Administration Console.
14. To see the class instances that have been imported by the Adapter, expand the Adaptersfolder, 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.
58Integrating with BMC ProactiveNet PerformanceManagement 8.5.x and 8.6.x
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 beencreated based on the previous version of the KM
3. Close
4. Resume the entire Creating an Adapter for a BMC PATROL KM procedure
For complete and detailed information on these procedures, please refer to the BMC ProactiveNetdocumentation available f rom 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
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 properlyinterpreted.
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 notproperly converted 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 BMC
59 Integrating with BMC ProactiveNet PerformanceManagement 8.5.x and 8.6.x
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
ProactiveNet Operator Console, while instance-level thresholds are displayed in the AbsoluteInstance Thresholds panel.
Managing Baselines and Key PerformanceIndicatorsIn order to facilitate the detection of abnormalities on your monitored environment, BMCProactiveNet calculates baselines per parameter (metrics or attributes) based on valuescollected over a specified period of time to determine a normal operating range. When thecollected values for these parameters are out of range, an alert is triggered.
Some parameters are identified by default as Key Performance Indicators and thereforeautomatically included in the base lining calculation.
Managing baselines
The baseline is the expected normal operating range for a metric or attribute of a monitor.
The baseline is calculated by collecting the values for a monitor’s attributes and metrics over aspecified time period and establishing a low baseline value (consisting of the 10th percentile ofall the values for a given time period) and a high baseline value (consisting of the 90th percentileof all the values for a given time period), taking a weighted average of these values over time. Ahigher weight is given to the latest data being factored into the baseline average. The accuracyof the baseline improves over time.
Requirements for baseline generation
For baselines to be generated for an attribute, that abnormality threshold means that thethreshold exists and is not suppressed. Additionally, if the Key Performance Indicator (KPI) mode is active, only those attributes thathave an active abnormality threshold and are also KPI attributes will have baselines generatedfor them.
Absolute thresholds (with "outside baseline") or signature thresholds do not satisfy these requirements.
Managing Key Performance Indicators
The KPI attribute of a parameter can be activated or deactivated manually through the BMCProactiveNet Administration Console. In this KM, some parameters or attributes have beendesignated as important indicators of performance (KPIs). We do not recommend that these
60Integrating with BMC ProactiveNet PerformanceManagement 8.5.x and 8.6.x
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
default settings are modified.
However, advanced users may activate or deactivate KPIs from the BMC ProactiveNetAdministration Console.
To add or remove Key Performance Indicator (KPI) attributes for a monitor 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 removeKPI attributes. A list of attributes for the selected monitor type is displayed.
3. In the KPI column for the attributes that you want to add or remove as Key PerformanceIndicators:
select the KPI check box to add the corresponding attribute as a KPI
deselect the KPI check box to remove the corresponding attribute from the KPIs for thatmonitor type
For complete and detailed information on this procedure, please refer to the BMC ProactiveNetdocumentation available f rom BMC Web site.
Parameters for which the system by default calculates baselines as well as parametersconsidered as KPIs are respectively identified by the following icons:
Baselining
KPI
61 Integrating with BMC ProactiveNet PerformanceManagement 8.5.x and 8.6.x
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Monitoring your Environment
63
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Symantec NetBackup KM for PATROL helps ensure the availability, maximum performance, andintegrity of 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 moreespecially:
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 Server
64Administering Symantec NetBackup
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 Server
Assigning, Denying, or Resubmitting MountRequestsWhen 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 allmount requests at once.
65 Administering Symantec NetBackup
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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
2. Select one of the following options:
Online Drive
Offline Drive
3. Click Yes to confirm your choice.
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
2. Select one of the following options:
Online Drive
Offline Drive
3. Click Yes to confirm your choice.
66Administering Symantec NetBackup
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Configuring the KMThe configuration instructions provided in this section should be followed on all PATROL AgentSystems where 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 informationcan however 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.
67 Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Specifying the Node TypeYou may have to manually indicate the type of node monitored if the discovery fails to recognizeit:
1. In the Console, right-click the 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,Veritas Cluster File System or Oracle Solaris Cluster, the NetBackup KM must be installed on allthe cluster nodes to enable continuous monitoring and avoid single point of failure. To avoidduplicate alerts from multiple nodes, it is recommended to configure the solution to operate inmulti-node monitoring mode.
To configure the multi-node monitoring mode:
68Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 VeritasCluster File System. The NetBackup KM will then monitor the entire cluster from the activemaster system, which is identified by the vxdctl -c mode command. This method requiresvxconfigd in enable mode with its clustered state active.
5. Enable remote PATROL Agent Checking to check the monitoring status of the other nodesand click OK
6. Indicate all the information required to communicate with the remote PATROL Agent(authentication server, protocol, port number, and credentials)
7. Click OK.
Symantec NetBackup will then be monitored through the master or online node. The othernodes, which are standing by for a failover, will be in passive multi-node mode and only theSymantec NetBackup components will be monitored.
If a managed node is unable to determine the system which should be in Active Multi-node Mode, it willchange to Temporary Single-node Mode.
69 Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Filtering Elements to MonitorBy default, the solution monitors all the elements discovered, which may represent animportant workload to the agents and servers. Because the monitoring of some elements maybe irrelevant for various reasons, you can apply filters to indicate which elements will bemonitored or not:
1. In the Console, right-click one of the following instances depending on the elements thatyou wish to monitor:
Clients > KM Commands > Configuration> Clients to filter clients to be monitored
Daemons > KM Commands > Configuration>Daemons to filter daemons to be monitored
Databases > KM Commands Configuration>Databases to filter databases to 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 noASCII format system log file to monitor.
Policies > KM Commands > Configuration>Policies to filter policies to be monitored.Please note that policy monitoring is disabled on media servers and in passive multi-nodemode and that only the backup/restore jobs of the monitored policies will be monitored.
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 to bemonitored
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 be monitored
Disk Volume > KM Commands > Configuration > Disk Volumes to filter disk volumes to bemonitored
These menus are also available f rom the child instances.
70Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Client Configuration dialog
The [ALL] entry ensures that all the elements found during PATROL discovery are instantiatedand monitored.
2. To enable elements for monitoring:
In the current configuration list, select the elements to enable
Select Enable
Click Update
A log f ilter will have to be conf igured if you enable log f iles for monitoring.
71 Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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, thusleaving parameters not set.
4. To delete elements for monitoring:
In the current configuration list, select the elements to delete
Select Delete
Click Update
5. To add a new element to monitor:
Type the name of the element to be monitored
If needed, enter a description
From the Status list, select Enable
Click Update.
To revert to the default monitoring conf iguration, type “[default]” as a new entry and click Update.
6. Resume the procedure for all the application classes for which you wish to apply monitoringfilters.
Configuring Monitoring PeriodsBy default, Symantec NetBackup KM for PATROL monitors all mount requests for 1day and allscheduled jobs that completed successfully for 1 day and any other scheduled job for 3 days . Youcan however modify these settings to better suit your requirements:
Increasing the monitoring period may affect the performance of the application.
72Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 collectioncycle
increase the monitoring period, you'll have to force a full data collection to ensure all jobsare instantiated. To force data collection, right-click the Jobs instance > KM Commands >
73 Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Force Full Collection
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 theinitial discovery cycle. Initially discovering and monitoring inactive jobs may impact theperformance of the application.
5. Select Ignore Alerting for Child Jobs if you do not want to be notified when a job failureoccurs on 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 monitoringperiod, older mount requests will be destroyed on the next data collection cycle
3. Click OK.
74Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Configuring the Elements StatusThe status of an element is determined by the State parameter and by the status mapping rule.This mapping rule indicates which states will trigger a warning or an alarm on the Statusparameter. It can be configured as follows:
1. In the Console, right-click one of the instance for which you want to configure status andselect > KM commands > Configuration > Instance Status
Daemon Status Configuration dialog
75 Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
2. In the Warning Filter State Rules list, select the states that will not trigger a warning
3. If needed, apply a time condition to a specific state. For example, if you want to trigger awarning when the Growing state of the Daemon instance lasts more than 600 minutes:
From the State list, select 7 (Growing)
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 analarm when 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 f ilter, select [default] f rom the list of states and clickUpdate.
7. Resume the procedure for all the application classes for which you wish to apply monitoringfilters.
When a NetBackup client is not installed on the same network as the master server, theNBUClientStatus parameter can trigger false alarm when the KM fails to ping the client. Anadditional script is available to avoid this situation. Use the following scripts when someNetBackupd clients cannot be pinged from the master server:
On UNIX/Linux Master serverscd $PATROL_HOME/lib/NBU
mv NBU_client_status.sh NBU_client_status_ping.sh
mv NBU_client_status_no_ping.sh NBU_client_status.sh
On Microsoft Windows Master serverscd %PATROL_HOME%\lib\NBU
ren NBU_client_status.cmd NBU_client_status_ping.cmd
ren NBU_client_status_no_ping.cmd NBU_client_status.cmd
76Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 thenode status
3. In the Daemon field, list the daemons to be used to determine the node status. The Daemonlist must 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:
77 Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 beinitiated.
Configuring Mount Requests Date/TimeFormatThe NetBackup KM uses Symantec NetBackup commands to determine the date and time of eachmount request (used for calculating the elapsed time since the mount request was issued).Depending on your local system time zone and date/time format, the application may return adifferent 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/Time Format Configuration dialog
78Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 f ield and/or the Time Zone f ield and click OK.The Time zone f ield used will be the local time zone on the managed node.
Configuring the Log FilterA log error filter can be configured to specify the regular expressions that will generate awarning or an alarm. Each time the KM will find these expressions in a log file or in NBULogText,the error message will be written to the NBULogAlarmText or NBULogWarningText parameter.By default, the default log filter is configured for the daily Symantec Netbackup messages fileand the system log file. If you enabled additional log files for monitoring, you will have tocustomize the log filter by adding appropriate expressions for those log files.
For more information about the possible error messages, refer to the Symantec NetBackup SystemAdministrator’s Guide and the Symantec NetBackup Troubleshooting Guide.
To configure the log error filter:
79 Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
1. In the Console, right-click the Logs instance > KM Commands > Configuration > Logs Filter
Log Filter Configuration dialog
2. In the Warning Filter Expressions list, select the expressions that will not trigger a warning
3. In the Alarm Filter Expressions list, select the expressions that will not trigger an alarm
4. To add a new regular expression to the warning or alarm filter:
In the Expression field, indicate the regular expression to be included (e.g.: skipping)
Select Include
Regular expressions are case-sensitive.
5. To exclude a regular expression from the warning or alarm filter:
In the Expression field, indicate the regular expression to be excluded (e.g.: otlsol01). Youcan also limit the exclusion to a particular expression already listed by using standardwildcard syntax, such as “skipping . otlsol06”.
Select Exclude
80Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
6. Click Update.
To revert to the default settings for either f ilter, type [default] as a new error expression for that f ilter,and click Update. If you revert to the default settings when accessed from the log instance level, the settingswill revert to the parent or container instance level. To revert to the shipped default settings (as shownabove), access this dialog from the log container instance. From this level you will also have the option toreset the conf iguration of any modif ied child instances.
Configuring the Log Scan LimitThe NetBackup KM scans log files by reading the new log entries since the last data collectioncycle. By default, only 500 Kbytes of data is scanned for each log file during each data collectioncycle. This log scan 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:
1. In the Console, right-click the Log(s) instance > KM Commands > Configuration Log(s) ScanLimit
Customizing the Log Scan Limit
81 Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 reportedby Symantec 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 movingor removing the keyword [ALL] in the Job Exit Status Filter.
To configure the exit status filter:
1. In the Console, right-click the Jobs instance > KM Commands > Configuration > Jobs ExitStatus
Configuring the Job Exit 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 to
82Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Error 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 specificperiod of time:
1. In the Console, right-click:
the Policies instance > KM Commands > Configuration> Policies Backup Restriction to applythis customization to all policies
a Policy instance > KM Commands > Configuration> Policy Backup Restriction to apply thiscustomization to a specific policy
Policy Backup Restriction Window dialog
2. Select Enabled
3. Indicate the Restriction Start and End Time. The restriction window must at least last 5minutes.
4. Click OK.
83 Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Configuring Alert AcknowledgementBy default, alerts will automatically be acknowledged unless you modified the settings to allowmanual acknowledgement.
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 changethe default behavior:
1. In the Console, right-click the Log(s) instance > KM Commands > Configuration> Log(s) AlertAcknowledgement
Configuring Log Alert Acknowledgement
2. Indicate whether the warning and alarm messages will be manually or automaticallyacknowledged
3. Click OK.
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 toconfigure the job alert acknowledgement as follows:
84Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
1. In the Console, right-click the Jobs instance > KM Commands > Configuration > Job AlertAcknowledgement
Configuring Job Alert Acknowledgement
2. Indicate whether the warning and alarm messages will be manually or automaticallyacknowledged
3. Click OK.
Refreshing ParametersThis section describes how to manually refresh parameters without waiting for an automaticpolling cycle.
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:
85 Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 applicationclasses loaded on the PATROL Agent will then be refreshed.
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 PATROL 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 PATROL Console for Unix
Right-click on the NetBackup KM instance and choose Customize > Parameters...
Select the required data collector.
Click Options > Update.
With the PATROL Central Operator Console
Right-click on the NetBackup KM instance and choose Properties
Click on the Parameter List tab
Select the required data collector.
Click Update.
Forcing Full Data Collection for Jobs
By default, the NBUJobCollector only searches for new jobs started since the last collectioncycle. However, it can be forced to search for all jobs within the monitored time period duringthe next collection 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 PATROLAgent needs to be restarted to force a full data collection for jobs.
86Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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-click the Symantec NetBackup instance > KM Commands > Reload Commands.
Enabling the Debug ModeWhen you encounter an issue and wish to report it to Sentry Software, you will be asked toenable the Debug Mode and provide the debug output to the Sentry Software support team.
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:
87 Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Enabling the Debug Mode
88Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 willno longer 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 diskspace and read, write and execute permissions for both PATROL Agent user and theNetBackup KM login user
Select Send to File(s) to write all debug messages in a file or set of files.
Select Send to Task Window to view the debug messages as they occur in the NBU DebugOutput window. Before selecting this option, make sure the PATROL Console is connectedto the PATROL Agent.
Select Both (Recommended) to send the debug messages both to a file and task window.
89 Configuring the KM
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 is then automatically created under <PATROL_HOME>/lib/NBU/ and can be sent to theBMC Support for help. It is also recommended to check the SOW or NBU.log file, stored in<PATROL_HOME>/log, for any error.
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 retainor delete them.
If the compressed f ile is not created successfully, you can create it manually by including all f iles and sub-directories under $PATROL_HOME/lib/NBU/ (on Unix) or %PATROL_HOME%\lib\NBU\ (on Microsoft Windows).
Appending Output Data to Existing Files
If you want to gather output from several debug sessions:
1. Disable the debug mode
2. Click No when asked to prepare the files for sending
3. Choose to Retain the debug files.
4. Start the next debug session.
5. Choose to append the output data to existing files.
90Acknowledging Alerts
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Acknowledging AlertsBy default, alerts are acknowledged automatically. If you modified the alert acknowledgementdefault settings, 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 NBULogAlarmCountor NBULogWarningCount.
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 willbe set to alert with a status of Warning or Alarm respectively. These alerts can be acknowledgedusing the menu 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
91 Generating Reports
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 > DriveCleaning Statistics - reports the drive cleaning statistics on the current master/media server
<Robotic Library instance> > Reports > Robotic Library Contents - reports the contents of theselected 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 atext file or print them.
Reference Guide
93
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Introduction
This chapter provides statistical information about resources, operating status, andperformances managed by Symantec NetBackup KM for PATROL. It contains tables describing theparameters used in the KM, grouped by Application Classes, and provides a brief description ofeach parameter and its default settings.
94Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Classes and ParametersThis section lists the application classes of NetBackup KM. It gives you details on the icons thatrepresent the class, Infobox, parameters and the menu commands available for each applicationclass. There are 16 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
95 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Baselines and Key Performance Indicators
Some parameters are identified by default as Key Performance Indicators (KPIs) and thereforeautomatically included in the base lining calculation. To learn more about auto baselining andKPIs, please refer to the Managing Baselines and Key Performance Indicators chapter.
In this guide, parameters flagged as KPIs and included by default in the baseline calculationprocess are respectively identified by the following icons:
Baselining
KPI
NBU_CLIENT_CONTAINERIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
NBUClientCollectorExecTime
Inactive standard parameter monitorsthe collector execution time. Toactivate this parameter, use the PSLbelow, and restart the PATROL Agent:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBUClientCollectorExecTime",1);
When activated it will run everyminute and trigger a warning when thecollector runs for more than theobserved maximum time. Thismaximum time can be overridden by apreset value (example: 3600 seconds),using the PSL below:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBUClientCollectorWarn",3600);
Seconds Warning:> presetvalue orobservedmaximum(default)
CollectionStatus
NBUClientDetails Set by NBUClientCollector. Displaysall data returned to the standardout from commands executed by thedata collector.
n/a n/a n/a
96Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
InfoBox
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 thisapplication instance.
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 NBUKM. By default, all clients configured on the master server are monitored.
Configuration > ClientsStatus
Accesses the global configuration for determining the client status formonitored client instances.By default, following NBUClientState to NBUClientStatus mapping rule is used:
97 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBU_CLIENTIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
NBUClientState Set by NBUClientCollector. Displaysthe state of the client as reported inthe command executed by the datacollector.
0 =Running1 =Connection Refused2 = AccessDenied3 = ClientDown-1 =Unknown
None Availability
NBUClientStatus Set by NBUClientCollector.Monitors the status of the client.This status is determined by theclient status mapping rule definedin the KM command Configuration >Client(s) Status. If this statusparameter changes to warning oralarm state, the recovery actionwill trigger an event and annotatethe last data point.
0 = OK1 =Suspicious2 = Failure
Warning = 1Alarm = 2
Availability
NBUClientSummary Set by NBUClientCollector.Summarizes the client informationas reported in commands executedby the data collector.
n/a None n/a
InfoBox
Name Description
Application Name of the application installed on the client that responds to the connectionrequest.
Collector Last End Date & time when the last data collection cycle completed.
Collector Last Start Date & time when the last data collection cycle started.
98Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Collector Name Name of the data collector that sets variables and parameters under thisapplication instance.
Collector Next Start Date & time when the next data collection cycle is expected to start.
Collector Status Data collector execution status (Idle or Running).
Description Description of the Symantec NetBackup client.
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
Function Description
Configuration > Client Sets the client instance to be enabled or disabled for monitoring by the NBUKM.
Configuration > ClientStatus
Accesses the individual configuration for determining client status for theselected client instance. By default, the global NBUClientState toNBUClientStatus mapping rule is used, as configured at the container level.
NBU_DAEMON_CONTAINERIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
NBUDaemonDetails Set by NBUDaemonCollector.Displays all data returned to thestandard out from commandsexecuted by the data collector.
n/a n/a n/a
99 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBUDaemonCollectorExecTime
Inactive standard parameter monitorsthe collector execution time. Toactivate this parameter, use the PSLbelow, and restart the PATROL Agent:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBUDaemonCollectorExecTime", 1);
When activated it will run everyminute and trigger a warning when thecollector runs for more than theobserved maximum time. Thismaximum time can be overridden by apreset value (example: 3600 seconds),using the PSL below:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBUDaemonCollectorWarn",3600);
Seconds Warning> presetvalue orobservedmaximum(default)
CollectionStatus
100Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
InfoBox
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 thisapplication instance.
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
Reports > Daemon List Lists all running Symantec NetBackup daemons.
Configuration > Daemons
Accesses the dialog for specifying which daemons are to be monitored by theNBU KM.By default the following daemons are monitored.
Configuration > Daemons Status
Accesses the global configuration for determining the daemon status formonitored daemon instances.By default the following NBUDaemonState to NBUDaemonStatus mapping ruleis used:
101 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBU_DAEMONIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
NBUDaemonCPUDuration
Set by NBUDaemonCollector.Displays the CPU secondsconsumed by the daemon.
Seconds None Statistics
NBUDaemonCPUUtilization*
Set by NBUDaemonCollector.Displays the percentage of CPUused by the daemon.
Percentage(%)
None Statistics
NBUDaemonMemorySize*
Set by NBUDaemonCollector.Displays the core image size of thedaemon in the virtual memory.
Kilobytes(KB)
None Statistics
NBUDaemonProcessCount
Set by NBUDaemonCollector.Displays the number of daemonprocesses/threads found.
Processes None Statistics
102Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBUDaemonState Set by NBUDaemonCollector.Displays the state of the daemon asreported in the command executedby the data collector.
0 =Running1 =Sleeping2 =Waiting3 = Queued4 =Intermediate5 =Terminated6 =Stopped/Disabled7 =Growing8 =Nonexistent/NotResponding9 = NotRunning-1 =Unknown
None Availability
NBUDaemonStatus Set by NBUDaemonCollector.Monitors the status of the daemon.This status is determined by thedaemon status mapping ruledefined in the KM command Configuration>Daemon(s) Status. Ifthis status parameter changes towarning or alarm state, therecovery action will trigger an eventand annotate the last data point.
0 = OK1 =Suspicious2 = Failure
Warning = 1Alarm = 2
Availability
NBUDaemonSummary Set by NBUDaemonCollector.Summarizes the daemoninformation as reported bycommands executed by the datacollector.
n/a n/a n/a
For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators.
* Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instancein BPPM.
InfoBox
Name Description
Collector Last End Date & time when the last data collection cycle completed.
103 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 thisapplication instance.
Collector Next Start Date & time when the next data collection cycle is expected to start.
Collector Status Data collector execution status (Idle or Running).
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
Function Description
Configuration > Daemon Sets the daemon instance to be enabled or disabled for monitoring by the NBUKM.
Configuration > DaemonStatus
Accesses the individual configuration for determining daemon status for theselected the daemon instance. By default, the global NBUDaemonState toNBUDaemonStatus mapping rule is used, as configured at the container level.
NBU_DATABASE_CONTAINERIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
104Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBUDatabaseBackupElapsed*
Set by NBUDatabaseCollector.Displays the elapsed time since thelast successful database backup.The specified alarm ranges can beenabled to allow the output of theparameter to be actively monitored.Then, if this parameter changes towarning or alarm state, therecovery action will trigger anevent.
Hours Alarm: -1Warning: 24and over
Statistics
NBUDatabaseCollectorExecTime
Inactive standard parameter monitorsthe collector execution time. Toactivate this parameter, use the PSLbelow, and restart the PATROL Agent:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBUDatabaseCollectorExecTime", 1);
When activated it will run everyminute and trigger a warning when thecollector runs for more than theobserved maximum time. Thismaximum time can be overridden by apreset value (example: 3600 seconds),using the PSL below:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBUDatabaseCollectorWarn",3600);
Seconds Warning:> presetvalue orobservedmaximum(default)
CollectionStatus
NBUDatabaseDetails Displays all data returned to thestandard out from commandsexecuted by the data collector.
n/a n/a n/a
NBUDatabaseStatus Set by NBUDatabaseCollector.Monitors the status of theNetBackup database (NBDB). If thisstatus parameter changes towarning or alarm state, therecovery action will trigger anevent and annotate the last datapoint.
0 = OK1 =Suspicious2 = Failure
Warning = 1Alarm = 2
availability
For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators.
* Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instancein BPPM.
InfoBox
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.
105 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Collector Name Name of the data collector that sets variables and parameters under thisapplication instance.
Collector Next Start Date & time when the next data collection cycle is expected to start.
Collector Status Data collector execution status (Idle or Running).
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
Function Description
Reports > DatabaseBackup Information
Reports information about the last catalog database backup.
Configuration > Database
Accesses the dialog for specifying which catalog databases are to be monitoredby the NBU KM.By default, following database paths are monitored. These database paths arerelative to Symantec NetBackup installation directory (for example /usr/openvon HP-UX).
NBU_DATABASEIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
106Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBUDatabaseFSSpaceUsedPercent*
Set by NBUDatabaseCollector.Monitors the percentage of spaceused by the file system where thedatabase resides. If this parameterchanges to warning or alarm state,the recovery action will trigger anevent.
Percentage(%)
Warning:95- 98Alarm: 98-100
Statistics
NBUDatabaseSpaceAvailable
Set by NBUDatabaseCollector.Monitors the amount of assignedspace remaining available for useby the catalog database. If thisparameter changes to warning oralarm state, the recovery actionwill trigger an event.
Megabytes Warning: 2-5Alarm: 0-2
Availability
NBUDatabaseSpaceGrowthRate
Set by NBUDatabaseCollector.Displays the growth rate of thespace used by the catalogdatabase.
Megabytesperseconds(MB/s)
None Statistics
NBUDatabaseSpaceUsed Set by NBUDatabaseCollector.Displays the amount of assignedspace used by the catalogdatabase.
Megabytes None Statistics
NBUDatabaseSpaceUsedPercent*
Set by NBUDatabaseCollector.Monitors the percentage ofassigned space used by the catalogdatabase. If this parameterchanges to warning or alarm state,the recovery action will trigger anevent.
Percentage(%)
Warning:95- 98Alarm: 98-100
Statistics
NBUDatabaseSummary Set by NBUDatabaseCollector.Summarizes the databaseinformation as reported bycommands executed by the datacollector.
n/a n/a n/a
For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators.
* Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instancein BPPM.
InfoBox
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 thisapplication instance.
Collector Next Start Date & time when the next data collection cycle is expected to start.
107 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Collector Status Data collector execution status (Idle or Running).
Description Description of the Symantec NetBackup catalog database.
Last Purge Date & time when the catalog database was last purged.
Name Name of the Symantec NetBackup catalog database.
Path Full file path of the catalog database.
Menu Commands
Function Description
Configuration > Database
Sets the database instance to be enabled or disabled for monitoring by the NBUKM.
108Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBU_DEVICEIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
NBUDriveState Set by NBUDriveCollector. Displaysthe state of the standalone drive.This is determined from thestandalone drive controlinformation.
0 = Idle1 =Mounted2 = In Use3 =Pending4 = Down-1 =Unknown
None Availability
NBUDriveStatus Set by NBUDriveCollector. Monitorsthe status of the standalone drive.This status is determined by thestandalone drive status mappingrule defined in the KM command Configuration> Standalone Drive(s)Status.
If this status parameter changes towarning or alarm state, therecovery action will trigger anevent and annotate the last datapoint.
0 = OK1 =Suspicious2 = Failure
Warning = 1Alarm = 2
Availability
NBUDriveSummary Set by NBUDriveCollector.Summarizes the standalone driveinformation as reported bycommands executed by the datacollector.
n/a n/a n/a
NBUDriveThroughput*
Set by NBUDriveCollector. Displaysthe throughput of the standalonedrive during the last backupactivity.
Megabytesper second(MB/s)
None Statistics
For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators.
* Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instancein BPPM.
109 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
InfoBox
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 thisapplication instance.
Collector Next Start Date & time when the next data collection cycle is expected to start.
Collector Status Data collector execution status (Idle or Running).
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 thisdrive.
110Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Menu Commands
Function Description
Reports > Drive CleaningStatistics
Reports the drive cleaning statistics on the current master/media server.
Configuration > Standalone Drives
Accesses the dialog for specifying which standalone drives are to be monitoredby the NBU KM.By default, all local and remote standalone drives are monitored for a masterserver and all local standalone drives are monitored for a media server.
Configuration > Standalone Drives Status
Accesses the global configuration for determining the status for monitoredstandalone drive instances.By default, the following NBUDriveState to NBUDriveStatus mapping rule isused:
NBU_DEVICE_CONTAINERIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
NBUDriveCollectorExecTime
Inactive standard parameter monitorsthe collector execution time. Toactivate this parameter, use the PSLbelow, and restart the PATROL Agent:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBUDriveCollectorExecTime",1);
seconds Warning > presetvalue orobservedmaximum(default)
CollectionStatus
111 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
When activated it will run everyminute and trigger a warning when thecollector runs for more than theobserved maximum time. Thismaximum time can be overridden by apreset value (example: 3600 seconds),using the PSL below:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBUDriveCollectorWarn",3600);
NBUDriveDetails Set by NBUDriveCollector. Displaysall data returned to the standardout from commands executed bythe data collector.
n/a n/a n/a
InfoBox
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 thisapplication instance.
Collector Next Start Date & time when the next data collection cycle is expected to start.
Collector Status Data collector execution status (Idle or Running).
112Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Menu Commands
Function Description
Reports > Drive CleaningStatistics
Reports the drive cleaning statistics on the current master/media server.
Configuration > Standalone Drives
Accesses the dialog for specifying which standalone drives are to be monitoredby the NBU KM. By default, all local and remote standalone drives aremonitored for a master server and all local standalone drives are monitoredfor a media server.
Configuration > Standalone Drives Status
Accesses the global configuration for determining the status for monitoredstandalone drive instances.By default, the following NBUDriveState to NBUDriveStatus mapping rule isused:
NBU_DPOOLIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
NBUDPoolSummary Set by NBUStorageCollector.Summarizes the disk poolinformation as reported bycommands executed by the datacollector.
n/a n/a n/a
NBUDPoolUpDownState Set by NBUStorageCollector.Displays the up/down state of thedisk pool.
0 = Down1 = Up-1 =Unknown
None Availability
113 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBUDPoolUpDownStatus
Set by NBUStorageCollector.Monitors the up/down status of thedisk pool. This status is determinedby the disk pool status mappingrule defined in the KM commandConfiguration>Disk Pool(s) Status.
If this status parameter changes towarning or alarm state, therecovery action will trigger anevent and annotate the last datapoint.
0 = OK1 =Suspicious2 = Failure
Warning = 1Alarm = 2
Availability
NBUDPoolVolumeCount*
Set by NBUStorageCollector.Displays the number of volumes inthe disk pool.
count None Statistics
For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators.
* Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instancein BPPM.
InfoBox
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 thisapplication instance.
Collector Next Start Date & time when the next data collection cycle is expected to start.
Collector Status Data collector execution status (Idle or Running).
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.
114Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Menu Commands
Function Description
Configuration > DiskPool
Accesses the configuration for monitoring the selected disk pool instance.This dialog allows the selected disk pool instance to be enabled or disabled formonitoring by the NBU KM.
Configuration > DiskPool Up/Down Status
Accesses the individual configuration for determining disk pool up/downstatus for the selected disk pool instance.By default, the global NBUDPoolUpDownState to NBUDPoolUpDownStatusmapping rule is used, as configured at the container level.
Configuration > DiskVolumes
Accesses the dialog for specifying which disk volumes of the selected disk poolare to be monitored by the NBU KM. By default, all disk volumes of the selecteddisk pool are monitored.
Configuration > DiskVolumes Up/DownStatus
Accesses the configuration for determining up/down status for the monitoreddisk volume instances on the selected disk pool instance. By default, the global NBUDVolumeUpDownState to NBUDVolumeUpDownStatus mapping rule isused, as configured at the container level.
NBU_DVOLUMEIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
NBUDVolumeReadStreamCount*
Set by NBUStorageCollector. Displays thenumber of current read steams for thedisk volume
Count None Statistics
NBUDVolumeSpaceAvailable*
Set by NBUStorageCollector. Monitors theavailable disk volume space for thebackup data to use.
If this parameter changes to warning oralarm state, the recovery action willtrigger an event.
Gigabytes(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.
Gigabytesperseconds(GB/s)
None Statistics
115 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBUDVolumeSpaceUsed*
Set by NBUStorageCollector. Displays thedisk space occupied by the backup datain this disk volume.
Percentage(%)
None Statistics
NBUDVolumeSpaceUsedPercent
Set by NBUStorageCollector. Monitors thepercentage of occupied disk spaceagainst the capacity of this disk volume.
If this parameter changes to warning oralarm state, the recovery action willtrigger an event.
Percentage(%)
Warning:95-98Alarm: 98-100
Statistics
NBUDVolumeSummary
Set by NBUStorageCollector. Summarizesthe disk volume information as reportedby commands executed by the datacollector.
n/a None n/a
NBUDVolumeUpDownState
Set by NBUStorageCollector. Displays theup/down state of the disk volume.
0 = Down1 = Up-1 =Unknown
None Availability
NBUDVolumeUpDownStatus
Set by NBUStorageCollector. Monitors theup/down status of the disk volume. Thisstatus is determined by the disk volumestatus mapping rule defined in the KMcommand Configuration>Disk Volume(s)Status.
If this 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
NBUDVolumeWriteStreamCount*
Set by NBUStorageCollector. Displays thenumber of current write steams for thedisk volume
Count None Statistics
For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators.
* Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instancein BPPM.
InfoBox
Name Description
Collector Last End Date & time when the last data collection cycle completed.
Collector LastStart
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 NextStart
Date & time when the next data collection cycle is expected to start.
116Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Collector Status Data collector execution status (Idle or Running).
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.
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
Function Description
Configuration > Disk Volume
Sets the disk volume instance to be enabled or disabled for monitoring by the NBU KM.
Configuration >Disk Volume Up/Down Status
Accesses the individual configuration for determining disk volume up/down status forthe selected disk volume instance.By default, the global NBUDVolumeUpDownState to NBUDVolumeUpDownStatusmapping rule is used, as configured at the container level.
NBU_JOB_CONTAINERIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
117 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBUJobActiveBackupCount*
Set by NBUJobCollector. Displaysthe number of active backup jobscurrently discovered andmonitored.
Count None Statistics
NBUJobActiveBackupReduction
Set by NBUJobCollector. Displaysthe reduction in number of activebackup jobs since the lastcollection cycle.
Count None Statistics
NBUJobActiveCount* Set by NBUJobCollector. Displaysthe number of active jobs currentlydiscovered and monitored.
Count None Statistics
NBUJobActiveNonBackupCount*
Set by NBUJobCollector. Displaysthe number of active non-backupjobs currently discovered andmonitored.
Count None Statistics
NBUJobCollectorExecTime
Inactive standard parameter monitorsthe collector execution time. Toactivate this parameter, use the PSLbelow, and restart the PATROL Agent:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBUJobCollectorExecTime", 1);
When activated it will run everyminute and trigger a warning when thecollector runs for more than theobserved maximum time. Thismaximum time can be overridden by apreset value (example: 3600 seconds),using the PSL below:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBUJobCollectorWarn", 3600);
Seconds Warning > presetvalue orobservedmaximum(default)
CollectionStatus
NBUJobDetails Set by NBUJobCollector. Displaysall data returned to the standardout from commands executed bythe data collector.
n/a n/a n/a
NBUJobQueuedBackupCount
Set by NBUJobCollector. Displaysthe number of backup jobs in"Queued" state.Units: count
Count None Statistics
NBUJobQueuedBackupReduction
Set by NBUJobCollector. Displaysthe reduction in number of queuedbackup jobs since the lastcollection cycle.
Count None Statistics
For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators.
* Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instancein BPPM.
InfoBox
118Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 thisapplication instance.
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
Force Full Collection Allows the user to force the data collector for jobs to perform a full discoveryduring the next collection cycle.
Acknowledgement > Warnings
Allows acknowledgement of warning alerts occurring on any monitored jobinstance.This dialog allows acknowledgement of any job in a "suspicious" state (whichsets the parameter 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 setsthe parameter NBUJobStatus to Alarm).
Acknowledgement > All Allows acknowledgement of all warnings and alarms occurring on anymonitored job instance.This dialog allows acknowledgement of any job in a "suspicious" or "failure"state (which sets the parameter NBUJobStatus to Warning or Alarm,respectively.
Configuration > Jobs Accesses the dialog for specifying which jobs are to be monitored by the NBUKM.By default, all scheduled jobs on the master server are monitored according tothe following conditions:
The age of a job is calculated from the job start time. The status of a job isdetermined by the state of the job (from the parameter NBUJobState) and the jobstatus mapping rule, described below.
Configuration > Jobs ExitStatus Filter
Accesses the configuration for erroneous and failure exit status codes for allbackup and restore jobs. This filter is used for setting the parameter NBUJobState to "6=Error" and 10=Failed respectively, when a backup or restorejob returns a non-zero exit status. The exit status codes are mapped toparameter NBUJobState as shown below:
119 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
The default filter includes [ALL] in the failure filter and exit status code "1" inthe erroneous filter. [ALL] is a keyword used for deciding the state for all otherexit status codes not listed in the filters.
Type [default] to reset the filters to shipped default configuration.
Configuration > JobsStatus
Accesses the configuration for determining the status for all monitored jobinstances.By default, the following NBUJobState to NBUJobStatus mapping rule is used:
Configuration > JobsAlert Acknowledgement
Accesses the global configuration of the method of acknowledgement for alertson monitored job instances.By default, the job alerts are manually acknowledged. Using this menu you canchange this so the job collector automatically acknowledges previous jobalerts (warnings or alarms) when it detects new errors.
NBU_JOBIcon
Parameters
Jobs Monitoring is disabled on media servers and in passive multi-node mode.
Name Description Units Default AlertConditions
BPPM Type
NBUJobDuration Set by NBUJobCollector. Displaysthe duration of the job from thestart.
Seconds None Statistics
NBUJobFileCount Set by NBUJobCollector. Displaysthe number of files backed up forthis job.
Count None Statistics
120Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBUJobSize Set by NBUJobCollector. Displaysthe amount of data backed up forthe job.
Megabytes(MB)
None Statistics
NBUJobState Set by NBUJobCollector. Displaysthe state of the job. This isdetermined using the jobcompletion state, job exit statuscode, last job operation, and theerroneous exit status filter.
The erroneous exit status filter canbe customized using the KM menu Configuration>Jobs Erroneous ExitStatus. If the exit status code isincluded in the erroneous exitstatus filter, 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. Monitorsthe status of the job. This status isdetermined by the job statusmapping rule defined in the KMcommand Configuration>JobsStatus.
If this status parameter changes towarning or alarm state, therecovery action will trigger anevent and annotate the last datapoint.
0 = OK1 =Suspicious2 = Failure
Warning = 1Alarm = 2
Availability
NBUJobSummary Set by NBUJobCollector.Summarizes the job information asreported by commands executed bythe data collector.
n/a n/a n/a
NBUJobText Set by NBUJobCollector. Displaysall reported messages related tothis job.
n/a n/a n/a
NBUJobThroughput* Set by NBUJobCollector. Displaysthe throughput of this job.
Megabytesperseconds(MB/s)
None Statistics
For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators.
* Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instancein BPPM.
121 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
InfoBox
Name Description
Attempt Number of attempts of the job.
Client Host name of the policy client associated with the job.
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 thisapplication instance.
Collector Next Start Date & time when the next data collection cycle is expected to start.
Collector Status Data collector execution status (Idle or Running).
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.
Percent Completed Estimated percentage of the job that has been completed in comparison withthe last similar 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.
122Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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
Function Description
Acknowledgement > Alert Sets the job instance is in a "suspicious" or "failure" state (which sets theparameter NBUJobStatus to Warning or Alarm, respectively).
123 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBU_LDEVICEIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
NBURDriveState Set by NBULibraryCollector.Displays the state of the roboticdrive. This is determined from therobotic drive control information.
0 = Idle1 =Mounted2 = In Use3 =Pending4 = Invalid5 = Down6 =Missing-1 =Unknown
None Availability
NBURDriveStatus Set by NBULibraryCollector.Monitors the status of the roboticdrive. This status is determined bythe robotic drive status mappingrule defined in the KM command Configuration>Robotic Drive(s)Status.
If this status parameter changes towarning or alarm state, therecovery action will trigger anevent and annotate the last datapoint.
0 = OK1 =Suspicious2 = Failure
Warning = 1Alarm = 2
Availability
NBURDriveSummary Set by NBULibraryCollector.Summarizes the robotic driveinformation as reported bycommands executed by the datacollector.
n/a n/a n/a
NBURDriveThroughput*
Set by NBULibraryCollector.Displays the throughput of therobotic drive during the lastbackup activity.
Megabytesperseconds(MB/s)
None Statistics
For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators.
124Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
* Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instancein BPPM.
InfoBox
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 thisapplication instance.
Collector Next Start Date & time when the next data collection cycle is expected to start.
Collector Status Data collector execution status (Idle or Running).
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 tothis drive.
Menu Commands
Function Description
Administration > OnlineDrive
Allows the selected robotic drive to be brought online.
Administration > OfflineDrive
Allows the selected robotic drive to be taken offline.
125 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Configuration > RoboticDrive
Sets the drive instance to be enabled or disabled for monitoring by the NBUKM.
Configuration > RoboticDrive Status
Accesses the individual configuration for determining the drive status for theselected robotic drive instance.By default, the NBURDriveState to NBURDriveStatus mapping rule configured atthe parent level is used. (Note that if the mapping rule has not been modifiedfor the parent robotic library, then the default is the global mapping ruleconfigured at the container level.)
NBU_LIBRARY_CONTAINERIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
NBULibraryCollectorExecTime
Inactive standard parameter monitorsthe collector execution time. Toactivate this parameter, use the PSLbelow, and restart the PATROL Agent:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBULibraryCollectorExecTime",1);
When activated it will run everyminute and trigger a warning when thecollector runs for more than theobserved maximum time. Thismaximum time can be overridden by apreset value (example: 3600 seconds),using the PSL below:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBULibraryCollectorWarn",3600);
seconds Warning > presetvalue orobservedmaximum(default)
CollectionStatus
NBULibraryDetails Set by NBULibraryCollector.Displays all data returned to thestandard out from commandsexecuted by the data collector.
n/a n/a n/a
InfoBox
Name Description
126Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 thisapplication instance.
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
Reports > Drive CleaningStatistics
Reports the drive cleaning statistics on the current master/media server.
Configuration > RoboticLibraries
Accesses the dialog for specifying which robotic libraries are to be monitoredby the NBU KM.By default, all local and remote robotic libraries are monitored for a masterserver and all local robotic libraries are monitored for a media server.
Configuration > RoboticLibraries Status
Accesses the global configuration for determining the status for monitoredrobotic library instances.By default, the following NBULibraryState to NBULibraryStatus mapping rule isused:
Configuration > RoboticDrives
Accesses the dialog for specifying which drives of the selected robotic libraryare to be monitored by the NBU KM. By default, all robotic drives of the selectedrobotic library are monitored.
Configuration > RoboticDrives Status
Accesses the global configuration for determining the status for monitoredrobotic drive instances (configured under monitored robotic library instances).By default, the following NBURDriveState to NBURDriveStatus mapping rule isused:
127 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBU_LIBRARYIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
NBULibraryMediaAssignedCount
Set by NBULibraryCollector.Displays the number of assignedmedia loaded in this roboticlibrary. (Assigned media are tapemedia assigned to a non-scratchvolume pool.)
count None Statistics
NBULibraryMediaAvailableCount
Set by NBULibraryCollector.Displays the number of mediaavailable to use in this roboticlibrary. This includes unassignedand scratch media.
count None Statistics
NBULibraryMediaAvailablePercent*
Set by NBULibraryCollector.Monitors the percentage ofavailable media against the totalnumber of media loaded in thisrobotic library.
If this parameter changes towarning or alarm state, therecovery action will trigger anevent.
Percentage(%)
Warning:between 2and 5Alarm: 2 orless
Statistics
NBULibraryMediaCleaningLeft
Set by NBULibraryCollector.Monitors the number of cleaningleft on the cleaning media availablein this robotic library.
If this parameter changes towarning or alarm state, therecovery action will trigger anevent.
count Warning: 2or lessAlarm: 0
Statistics
NBULibraryMediaCount
Set by NBULibraryCollector.Displays the total number of medialoaded in this robotic library.
count None Statistics
128Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBULibraryMediaScratchCount
Set by NBULibraryCollector.Displays the number of scratchmedia loaded in this roboticlibrary. (Scratch media are tapemedia assigned to the scratchvolume pool.)
count None Statistics
NBULibraryMediaScratchPercent*
Set by NBULibraryCollector.Monitors the percentage of scratchmedia against the total number ofmedia loaded in this roboticlibrary.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.
Percentage(%)
None Statistics
NBULibraryMediaUnassignedCount
Set by NBULibraryCollector.Displays the number of unassignedmedia loaded in this roboticlibrary.(Unassigned media are tape medianot assigned to a volume pool.)
count None Statistics
NBULibraryMediaUnassignedPercent*
Set by NBULibraryCollector.Monitors the percentage ofunassigned media against the totalnumber of media loaded in thisrobotic library.
If this parameter changes towarning or alarm state, therecovery action will trigger anevent.
Percentage(%)
None Statistics
NBULibraryState Set by NBULibraryCollector.Displays whether the inquiry for therobotic library is valid or invalid. Itwill not perform any remote roboticlibrary test command on the mediaserver.
0 = Online1 = Remote2 = Offline3 = Invalid-1 =Unknown
None Availability
NBULibraryStatus Set by NBULibraryCollector.Monitors the status of the roboticlibrary. This status is determinedby the robotic library statusmapping rule defined in the KMcommand Configuration> RoboticLibrary (Libraries) Status.
If this status parameter changes towarning or alarm state, therecovery action will trigger an eventand annotate the last data point.
0 = OK1 =Suspicious2 = Failure
Warning = 1Alarm = 2
Availability
129 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBULibrarySummary Set by NBULibraryCollector.Summarizes the robotic libraryinformation as reported bycommands executed by the datacollector.
n/a None n/a
NBULibraryThroughput*
Set by NBULibraryCollector.Displays the total throughput ofeach robotic library drive duringthe last backup activities within thelast hour.
Megabytesper second(MB/s)
None Statistics
NBULibraryUpDriveCount
Set by NBULibraryCollector.Displays the number up / onlinestate drives in this robotic library.
If this parameter changes towarning or alarm state, therecovery action will trigger anevent.
count None Statistics
For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators.
* Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instancein BPPM.
InfoBox
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 thisapplication instance.
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
Reports > RoboticLibrary Contents
Reports the contents of the selected robotic library.
Configuration > RoboticLibrary
Sets the robotic library instance to be enabled or disabled for monitoring bythe NBU KM.
Configuration > RoboticLibrary Status
Accesses the individual configuration for determining the status for theselected robotic library instance. By default, the global NBULibraryState toNBULibraryStatus mapping rule is used, as configured at the container level.
130Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Configuration > RoboticDrives
Accesses the dialog for specifying which drives of the selected robotic libraryare to be monitored by the NBU KM. By default, all robotic drives of the selectedrobotic library are monitored.
Configuration > RoboticDrives Status
Accesses the configuration for determining status for the monitored driveinstances on the selected robotic library instance. By default, the global NBURDriveState to NBURDriveStatus mapping rule is used, as configured at thecontainer level.
NBU_LOG_CONTAINERIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
NBULogCollectorExecTime
Inactive standard parameter monitorsthe collector execution time. Toactivate this parameter, use the PSLbelow, and restart the PATROL Agent:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBULogCollectorExecTime", 1);
When activated it will run everyminute and trigger a warning when thecollector runs for more than theobserved maximum time. Thismaximum time can be overridden by apreset value (example: 3600 seconds),using the PSL below:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBULogCollectorWarn", 3600);
seconds Warning > presetvalue orobservedmaximum(default)
CollectionStatus
NBULogDetails Set by NBUDatabaseCollector.Summarizes the databaseinformation as reported bycommands executed by the datacollector.
n/a n/a n/a
InfoBox
Name Description
Collector Last End Date & time when the last data collection cycle completed.
131 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 thisapplication instance.
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
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 theNBU KM.By default, the following log files are monitored. These log file paths arerelative to the Symantec NetBackup installation directory (for example /usr/openv on HP-UX), unless the path is fully qualified as for the system log onSolaris and HP-UX.
Configuration > LogsFilter
Accesses the global configuration of the filter for expressions used fordetecting error messages in the monitored log file instances.By default, the following "Included" expressions are looked for in each log file.If detected, the message containing the expression is added to the appropriatetext parameter, unless the message also contains an "Excluded" expression forthe same filter.
132Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Configuration > LogsScan Limit
Accesses the global configuration of the data scanning limit for monitored logfile instances.By default, the log collector scans 500 KBytes of new log data for eachmonitored log file during each data collection cycle.
Configuration > LogsAlert Acknowledgement
Accesses the global configuration of the method of acknowledgement for alertson monitored log file instances.By default, the log collector automatically acknowledges previous log alerts(warnings or alarms) when it detects new errors.
NBU_LOGIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
NBULogAlarmCount* Set by NBULogCollector. Monitorsthe number of alarm messages setin the parameter NBULogAlarmText.
If this parameter changes to alarmstate, the recovery action willtrigger an event.
count Alarm: morethan orequal 1
Statistics
NBULogAlarmText Set by NBULogCollector. Displaysall alarm messages in the log filewhich have not been acknowledged.The filter used by the data collectorto determine alarm messages canbe customized using the KMcommand Configuration>Log(s)Filter.
These alarm messages can beacknowledged automatically(default) or manually, dependingon the configuration in the KMcommand Configuration > Log(s)Alert Acknowledgement. Manualacknowledgement is availableunder the KM sub-menuAcknowledgement.
n/a None n/a
133 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBULogFSSpaceUsedPercent*
Set by NBULogCollector. Monitorsthe percentage of space used by thefile system (where the log fileresides).
If this parameter changes towarning or alarm state, therecovery action will trigger anevent.
Percentage(%)
Warning:between 95and 98Alarm : 98 and over
Statistics
NBULogSpaceAvailable Set by NBULogCollector. Monitorsthe available space for the log fileto use (this is also the availablespace on the file system).If this parameter changes towarning or alarm state, therecovery action will trigger anevent.
Megabytes(MB)
Warning:between 2and 5Alarm: 2 orless
Availability
NBULogSpaceGrowthRate
Set by NBULogCollector. Displaysthe growth rate of the amount ofspace used by the log file.
Kilobytesper second(KB/s)
None Statistics
NBULogSpaceUsed Set by NBULogCollector. Displaysthe amount of space used by the logfile.
Kilobytes(KB)
None Statistics
NBULogSpaceUsedPercent*
Set by NBULogCollector. Monitorsthe percentage of capacity used bythe log file. The total capacity is theused space (NBULogSpaceUsed)plus available space(NBULogSpaceAvailable). If thisparameter changes to warning oralarm state, the recovery actionwill trigger an event.
Percentage(%)
Warning:between 95and 98Alarm: 98and over
Statistics
NBULogSummary Set by NBULogCollector.Summarizes the log file informationas reported by commands executedby the data collector.
n/a None n/a
NBULogText Set by NBULogCollector. Displaysall log text scanned by the datacollector during the last collectioncycle. The size of the data scannedby the data collector is configuredin the KM command Configuration>Log(s) Scan Limit.
n/a None n/a
NBULogWarningCount* Set by NBULogCollector. Monitorsthe number warning messages setin the parameter NBULogWarningText.
count Warning:more thanor equal to1
Statistics
134Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
If this parameter changes to awarning state, the recovery actionwill trigger an event.
NBULogWarningText Set by NBULogCollector. Displaysall warning messages in the log filewhich have not been acknowledged.The filter used by the data collectorto determine warning messages canbe customized using the KMcommand Configuration>Log(s)Filter.
These warning messages can beacknowledged automatically(default) or manually, dependingon the configuration set throughthe KM commandConfiguration>Log(s) AlertAcknowledgement. Manualacknowledgement is availableunder the KM sub-menuAcknowledgement.
n/a None n/a
For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators.
* Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instancein BPPM.
InfoBox
Name Description
Available FS Space Space available for use by the file system.
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 thisapplication instance.
Collector Next Start Date & time when the next data collection cycle is expected to start.
Collector Status Data collector execution status (Idle or Running).
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 ModificationTime
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.
135 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Total FS Space Total space used by the file system.
Menu Commands
Function Description
Acknowledgement > Warnings
Allows acknowledgement of warning messages detected on the selected log fileinstance.This dialog allows selective acknowledgement of "suspicious" error messagesdetected in the log file and sent to the text parameter NBULogWarningText.
Acknowledgement > Alarms
Allows acknowledgement of alarm messages detected on the selected log fileinstance.This dialog allows selective acknowledgement of "failure" error messagesdetected in the log file and sent to the text parameter NBULogAlarmText.
Acknowledgement >All Allows acknowledgement of all alarm and warning messages detected on theselected log file instance.This dialog allows acknowledgement of all error messages detected in the logfile and sent to the text parameter NBULogWarningText or NBULogAlarmText.
Configuration > Log Accesses the individual configuration for monitoring the selected log fileinstance.This dialog allows the selected log file instance to enabled or disabled formonitoring by the NBU KM.
Configuration > LogFilter
Accesses the individual configuration of the log error filter for the selected logfile 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 theselected log file instance.By default, the global log file scanning limit is used, as configured at thecontainer level.
Configuration > Log AlertAcknowledgement
Accesses the individual configuration of the method of acknowledgement foralerts on the selected log file instance.By default, the global method of log error acknowledgement is used, asconfigured at the container level.
NBU_MOUNTIcon
136Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Parameters
Mount Requests Monitoring is disabled on media servers and in passive multi-node mode.
Name Description Units Default AlertConditions
BPPM Type
NBURequestElapsed* Set by NBURequestCollector.Displays the elapsed time since themount request was issued.
minutes None Statistics
NBURequestState Set by NBURequestCollector.Displays the state of the mountrequest as reported in thecommand executed by the datacollector.
0 =Completed1 =Pending-1 =Unknown
None Availability
NBURequestStatus Set by NBURequestCollector,monitors the status of the mountrequest. This status is determinedby the mount request statusmapping rule defined in the KMcommand Configuration>MountRequest(s) Status.
If this status parameter changes towarning or alarm state, therecovery action will trigger anevent and annotate the last datapoint.
0 = OK1 =Suspicious2 = Failure
Warning = 1Alarm = 2
Availability
NBURequestSummary Set by NBURequestCollector.Summarizes the pending requestinformation as reported bycommands executed by the datacollector.
n/a n/a n/a
For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators.
* Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instancein BPPM.
InfoBox
Name Description
Barcode Barcode of the requested media.
Client Name of the policy client the pending request belongs to.
Collector Last End Date & time when the last data collection cycle completed.
Collector Last Start Date & time when the last data collection cycle started.
137 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Collector Name Name of the data collector that sets variables and parameters under thisapplication instance.
Collector Next Start Date & time when the next data collection cycle is expected to start.
Collector Status Data collector execution status (Idle or Running).
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 thePending Request 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.
138Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Menu Commands
Function Description
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_CONTAINERIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
BURequestCollectorExecTime
Inactive standard parameter monitorsthe collector execution time. Toactivate this parameter, use the PSLbelow, and restart the PATROL Agent:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBURequestCollectorExecTime", 1);
When activated it will run everyminute and trigger a warning when thecollector runs for more than theobserved maximum time. Thismaximum time can be overridden by apreset value (example: 3600 seconds),using the PSL below:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBURequestCollectorWarn",3600);
seconds Warning > presetvalue orobservedmaximum(default)
CollectionStatus
NBURequestDetails Set by NBURequestCollector.Displays all data returned to thestandard out from commandsexecuted by the data collector.
n/a n/a n/a
InfoBox
139 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 thisapplication instance.
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
Administration > AssignAll
Assigns all instantiated mount requests to their requested drives.
Administration > DenyAll
Denies all instantiated mount requests.
Administration > Resubmit All
Resubmits all instantiated mount requests.
Reports > PendingRequests
Reports a list of all pending mount requests.All report KM commands require a user account, which will be used forexecuting the menu command. Note the command will fail if the user does nothave privileges to execute the appropriate Symantec NetBackup command.
Configuration > MountRequests
Accesses the dialog for specifying which mount requests are to be monitoredby the NBU KM.By default, all mount requests are monitored for 1 day from the time they areissued.
Configuration > MountRequests Status
Accesses the configuration for determining the status for all monitored mountrequest instances.By default, the following NBURequestState to NBURequestStatus mapping ruleis used:
Configuration > MountRequest Date/TimeFormat
Accesses the configuration of the date/time format and time zone for allinstantiated mount requests.By default, the format used by Symantec NetBackup for the date/time of amount request is set to "MO/DD/YY HH:MM:SS". The date/time is then convertedby the NBU KM using the system time zone on the PATROL Agent (system timezone is indicated by an empty field).
140Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBU_PCLIENTIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
NBUFileExcludeList Set by NBUPolicyCollector. Lists allfiles and file systems excluded frombackup for this policy client.
n/a n/a n/a
NBUFileIncludeList Set by NBUPolicyCollector. Lists allfiles and file systems included forbackup for this policy client.
n/a n/a n/a
NBUPClientBackupSummary
Set by NBUPolicyCollector.Summarizes the last backup for thispolicy client.
n/a n/a n/a
NBUPClientBackupThroughput*
Set by NBUPolicyCollector. Displaysthe throughput of the last backupfor this policy client.
Megabytesper second(MB/s)
None Statistics
NBUPClientFullBackupDuration
Set by NBUPolicyCollector. Displaysthe duration of the last successfulfull backup for this policy client.
seconds None Statistics
NBUPClientFullBackupFileCount
Set by NBUPolicyCollector. Displaysthe number of files backed up in thelast successful full backup for thispolicy client.
count None Statistics
NBUPClientFullBackupSize*
Set by NBUPolicyCollector. Displaysthe size of the last successful fullbackup for this policy client.
Megabytes(MB)
None Statistics
NBUPClientIncrBackupDuration
Set by NBUPolicyCollector. Displaysthe duration of the last successfulincremental backup for this policyclient.
seconds None Statistics
NBUPClientIncrBackupFileCount
Set by NBUPolicyCollector. Displaysthe number of files backed up in thelast successful incremental backupfor this policy client.
count None Statistics
141 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBUPClientIncrBackupSize*
Set by NBUPolicyCollector. Displaysthe size of the last successfulincremental backup for this policyclient.
Megabytes(MB)
None Statistics
NBUPClientSummary Set by NBUPolicyCollector.Summarizes the policy clientinformation as reported bycommands executed by the datacollector.
n/a n/a n/a
For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators.
* Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instancein BPPM.
InfoBox
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 thisapplication instance.
Collector Next Start Date & time when the next data collection cycle is expected to start.
Collector Status Data collector execution status (Idle or Running).
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 policyclient.
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 thepolicy 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 policyclient.
Name Host name of the Symantec NetBackup policy client.
Operating System Operating system of the policy client.
142Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Policy Name Name of the policy that the policy client belongs to.
Priority Priority of the policy client.
143 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Menu Commands
Function Description
Configuration > PolicyClient
Sets the policy client instance to be enabled or disabled for monitoring by theNBU KM.
NBU_POLICY_CONTAINERIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
NBUPolicyCollectorExecTime
Inactive standard parameter monitorsthe collector execution time. Toactivate this parameter, use the PSLbelow, and restart the PATROL Agent:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBUPolicyCollectorExecTime",1);
When activated it will run everyminute and trigger a warning when thecollector runs for more than theobserved maximum time. Thismaximum time can be overridden by apreset value (example: 3600 seconds),using the PSL below:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBUPolicyCollectorWarn",3600);
seconds Warning > presetvalue orobservedmaximum(default)
CollectionStatus
NBUPolicyDetails Set by NBUPolicyCollector. Displaysall data returned to the standardout from commands executed by thedata collector.
n/a n/a n/a
InfoBox
Name Description
144Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 thisapplication instance.
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 > Policies Sets which policies are to be monitored by the NBU KM. By default, all policiesconfigured on the master server are monitored.
Configuration > PoliciesBackup Restriction
Accesses the global configuration to set a backup restriction window for allmonitored policy instances. By default, backup restriction is disabled.When the backup restriction window is defined and enabled using this dialog,and if the policy status mapping rule is configured appropriately, an alert willbe triggered if any backup activity is detected during this restriction window.
Configuration > PoliciesStatus
Accesses the global configuration for determining the policy status formonitored policy instances.By default, the following NBUPolicyState to NBUPolicyStatus mapping rule isused:
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_POLICYIcon
145 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Parameters
Name Description Units Default AlertConditions
BPPM Type
NBUPolicyBackupElapsed*
Set by NBUPolicyCollector. Displaysthe elapsed time since the lastbackup for this policy, regardlessof completion status of the backup.This last backup is determinedfrom 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, therecovery action will trigger anevent.
hours None Statistics
NBUPolicyBackupSummary
Set by NBUPolicyCollector.Summarizes the last backup for thispolicy.
n/a n/a n/a
NBUPolicyBackupThroughput*
Set by NBUPolicyCollector. Displaysthe throughput of the last backupfor this policy.
Gigabytesper second(GB/s)
None Statistics
NBUPolicyFullBackupDuration
Set by NBUPolicyCollector. Displaysthe duration of the last successfulfull backup for this policy.
seconds None Statistics
NBUPolicyFullBackupElapsed*
Set by NBUPolicyCollector. Displaysthe elapsed time since the lastsuccessful full backup for thispolicy. This last backup isdetermined from the monitoredjobs as configured in the KMcommand Configuration>Jobs fromthe Jobs icon.
The specified alarm ranges can beenabled to allow the output of theparameter to be actively monitored.Then, if this parameter changes towarning or alarm state, therecovery action will trigger anevent.
hours None Statistics
NBUPolicyFullBackupFileCount
Set by NBUPolicyCollector. Displaysthe number of files backed up in thelast successful full backup for thispolicy.
count None Statistics
146Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBUPolicyFullBackupSize
Set by NBUPolicyCollector. Displaysthe size of the last successful fullbackup for this policy.
Gigabytes(GB)
None Statistics
NBUPolicyIncrBackupDuration
Set by NBUPolicyCollector. Displaysthe duration of the last successfulincremental backup for this policy.
seconds None Statistics
NBUPolicyIncrBackupElapsed*
Set by NBUPolicyCollector. Displaysthe elapsed time since the lastsuccessful incremental backup forthis policy. This last backup isdetermined from the monitoredjobs as configured in the KMcommand Configuration>Jobs fromthe Jobs icon.
The specified alarm ranges can beenabled to allow the output of theparameter to be actively monitored.Then, if this parameter changes towarning or alarm state, therecovery action will trigger anevent.
hours None Statistics
NBUPolicyIncrBackupFileCount
Set by NBUPolicyCollector. Displaysthe number of files backed up in thelast successful incremental backupfor this policy.
count None Statistics
NBUPolicyIncrBackupSize
Set by NBUPolicyCollector. Displaysthe size of the last successfulincremental backup for this policy.
Gigabytes(GB)
None Statistics
NBUPolicyState Set by NBUPolicyCollector. Displaysthe state of the policy.
If a backup restriction window isdefined in the KM command Configuration> Policy (Policies)Backup Restriction, this parameterwill be set to Running in RestrictedWindow if there is any activityduring the specified period.
0 = Idle1 =Running2 =Running inRestrictedWindow3 = NotStarted4 =Inactive-1 =Unknown
None Availability
NBUPolicyStatus Set by NBUPolicyCollector.Monitors the status of the policy.This status is determined by thepolicy status mapping rule definedin the KM command Configuration>Policy (Policies) Status.
0 = OK1 =Suspicious2 = Failure
Warning = 1Alarm = 2
Availability
147 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
If this status parameter changes towarning or alarm state, therecovery action will trigger anevent and annotate the last datapoint.
NBUPolicySuccBackupElapsed*
Set by NBUPolicyCollector. Displaysthe elapsed time since the lastsuccessful backup for this policy.This last backup is determinedfrom 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, therecovery action will trigger anevent.
hours None Statistics
NBUPolicySummary Set by NBUPolicyCollector.Summarizes the policy informationas reported by commands executedby the data collector.
n/a None n/a
For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators.
* Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instancein BPPM.
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.
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 thisapplication instance.
Collector Next Start Date & time when the next data collection cycle is expected to start.
Collector Status Data collector execution status (Idle or Running).
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.
148Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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 thepolicy.
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 RestrictedWindow).
Type Type of the policy.
Volume Pool Volume pool of the policy.
Menu Commands
Function Description
Reports > PolicySchedule
Displays the schedule of the selected policy instance.
Configuration > Policy Accesses the individual configuration for monitoring the selected policyinstance.This dialog allows the selected policy instance to be enabled or disabled formonitoring by the NBU KM.
Configuration > PolicyBackup Restriction
Accesses the individual configuration for the backup restriction window for theselected policy instance.By default, the global backup restriction rule is used, as configured at thecontainer level.
Configuration > PolicyStatus
Accesses the individual configuration for determining policy status for theselected policy instance.By default, the global NBUPolicyState to NBUPolicyStatus mapping rule is used,as configured at the container level. Select [default] to revert to the policystatus mapping rule configured at the global/container level.
Configuration > PolicyClients
Accesses the dialog for specifying which policy clients of the selected policyare to be monitored by the NBU KM.
149 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
By default, all policy clients of enabled policies are monitored. Type "[default]"to reset to the default configuration.
150Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBU_POOL_CONTAINERIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
NBUPoolCollectorExecTime
Inactive standard parameter monitorsthe collector execution time. Toactivate this parameter, use the PSLbelow, and restart the PATROL Agent:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBUPoolCollectorExecTime",1);
When activated it will run everyminute and trigger a warning when thecollector runs for more than theobserved maximum time. Thismaximum time can be overridden by apreset value (example: 3600 seconds),using the PSL below:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBUPoolCollectorWarn",3600);
seconds Warning > presetvalue orobservedmaximum(default)
CollectionStatus
NBUPoolDetails Set by NBUPoolCollector. Displaysall data returned to the standardout from commands executed bythe data collector.
n/a n/a n/a
151 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
InfoBox
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 thisapplication instance.
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 > VolumePools
Sets which volume pools are to be monitored by the NBU KM. By default, allvolume pools configured on the master/media server are monitored, except for"None" (the default pool shipped with the Symantec NetBackup application).
Reports > AvailableMedia
Reports all available media across all volume pools.
NBU_POOLIcon
Parameters
Pool monitoring is disable on media servers and in passive multi-node mode
Name Description Units Default AlertConditions
BPPM Type
NBUMediaActiveCount
Set by NBUPoolCollector. Displaysthe number of active media in thisvolume pool. Active media areavailable tape media with a statusof Active, where data has beenwritten but the media is not yet full.
count None Statistics
152Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBUMediaActivePercent*
Set by NBUPoolCollector. Monitorsthe percentage of active mediaagainst the total number of mediain this volume pool.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.
Percentage(%)
Warning: 2-5Alarm: 0-2
Statistics
NBUMediaCount Set by NBUPoolCollector. Displaysthe total number of media in thisvolume pool.
count None Statistics
NBUMediaFrozenCount
Set by NBUPoolCollector. Displaysthe number of frozen media in thisvolume pool. Frozen is a possiblestatus for a tape media.
count None Statistics
NBUMediaFullCount Set by NBUPoolCollector. Displaysthe number of full media in thisvolume pool. Full is a possiblestatus for a tape media.
count None Statistics
NBUMediaFullPercent*
Set by NBUPoolCollector. Monitorsthe percentage of full mediaagainst the total number of mediain this volume pool.
If this parameter changes towarning or alarm state, therecovery action will trigger anevent.
Percentage(%)
Warning:95-98Alarm: 98-100
Statistics
NBUMediaLoadedCount
Set by NBUPoolCollector. Displaysthe number of media in this volumepool, currently loaded to a roboticlibrary.
count None Statistics
NBUMediaLoadedEmptyCount
Set by NBUPoolCollector. Displaysthe number of empty media in thisvolume pool, currently loaded to arobotic library.
count None Statistics
NBUMediaLoadedEmptyPercent
Set by NBUPoolCollector. Monitorsthe percentage of empty mediaagainst the total number of emptymedia in this volume pool.
Percentage(%)
Warning:2-5Alarm:0-2
Statistics
NBUMediaReadOnlyCount
Set by NBUPoolCollector. Displaysthe number of media in this volumepool, currently read-only. A mediaturns read-only when it hasreached the maximum allowedmounts.
count None Statistics
153 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBUMediaScratchCount
Set by NBUPoolCollector. Displaysthe number of scratch media in thisvolume pool. The parameter isvisible and set only for scratchvolume pools.
count Warning: 0-2Alarm = 0
Statistics
NBUMediaSuspendedCount
Set by NBUPoolCollector. Displaysthe number of suspended media inthis volume pool. Suspended is apossible status for a tape media.
count None Statistics
NBUMediaUnassignedCount
Set by NBUPoolCollector. Displaysthe number of media in unassignedstate in this volume pool.
count None Statistics
NBUMediaUnassignedPercent*
Set by NBUPoolCollector. Monitorsthe percentage of unassignedmedia against the total number ofmedia in this volume pool.If this parameter changes towarning or alarm state, therecovery action will trigger anevent.
Percentage(%)
None Statistics
NBUMediaUnknownCount
Set by NBUPoolCollector. Displaysthe number of media in unknownstate in this volume pool.
count None Statistics
NBUPoolSpaceAvailable*
Set by NBUPoolCollector. Monitorsthe available media space for thebackup data to use amongst theassigned media in this volumepool.
If this parameter changes towarning or alarm state, therecovery action will trigger anevent.
Gigabytes(GB)
None Availability
NBUPoolSpaceGrowthRate
Set by NBUPoolCollector. Displaysthe growth rate of the total mediaspace used by the backup data inthis volume pool.
Gigabytesper second(GB/s)
None Statistics
NBUPoolSpaceUsed* Set by NBUPoolCollector. Displaysthe total media space occupied bythe backup data in this volumepool.
Gigabytes(GB)
None Statistics
NBUPoolSpaceUsedPercent*
Set by NBUPoolCollector. Monitorsthe percentage of total occupiedmedia space against the totalmedia capacity of this volume pool(not including any scratch media).If this parameter changes towarning or alarm state, therecovery action will trigger anevent.
Percentage(%)
Warning:95-98Alarm: 98-100
Statistics
154Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBUPoolSummary Set by NBUPoolCollector.Summarizes the volume poolinformation as reported bycommands executed by the datacollector.
n/a n/a n/a
For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators.
* Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instancein BPPM.
InfoBox
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 thisapplication instance.
Collector Next Start Date & time when the next data collection cycle is expected to start.
Collector Status Data collector execution status (Idle or Running).
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 thispool.
155 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Menu Commands
Function Description
Reports > Media List Reports all volumes in the volume pool.
Configuration > VolumePool
Sets the volume pool instance to be enabled or disabled for monitoring by theNBU KM.
NBU_SERVERIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
ExtraFilesList Pushes the NetBackup KM libraryfiles to the PATROL Agent during the"Commit" operation.
n/a None n/a
NBUClientCollector Collects Symantec NetBackup clientrelated information. It sets allconsumer parameters in the NBU_CLIENT_CONTAINER andNBU_CLIENT application classes.By default, this collector isexecuted only on the master server.
Poll Time: 600 seconds
n/a None n/a
NBUCreateDistribution Is automatically activated at theend of NetBackup KM debugging ifthe customer chooses to "preparedebug files for sending to SentrySoftware". It is deactivated oncompletion.
Poll Time: 300 seconds
n/a None n/a
156Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBUDaemonCollector Collects Symantec NetBackupdaemon related information. It setsall consumer parameters in the NBU_DAEMON_CONTAINER andNBU_DAEMON application classes.
Poll Time: 300 seconds
n/a None n/a
NBUDatabaseCollector Collects Symantec NetBackupcatalog database relatedinformation. It sets all consumerparameters in the NBU_DATABASE_CONTAINER andNBU_DATABASE applicationclasses. By default, this collector isexecuted only on the master server.
Poll Time: 1800 seconds
n/a None n/a
NBUDriveCollector Collects Symantec NetBackupstandalone drive relatedinformation. It sets all consumerparameters in the NBU_DEVICE_CONTAINER andNBU_DEVICE application classes.
Poll Time: 600 seconds
n/a None n/a
NBUJobCollector Collects Symantec NetBackupbackup/restore activity relatedinformation. It sets all consumerparameters in the NBU_JOB_CONTAINER andNBU_JOB application classes. Bydefault, this collector is executedonly on the master server.
Poll Time: 300 seconds
n/a None n/a
NBULibraryCollector Collects Symantec NetBackuprobotic library and robotic driverelated information. It sets allconsumer parameters in the NBU_LIBRARY_CONTAINER,NBU_LIBRARY, and NBU_LDEVICEapplication classes.
Poll Time: 600 seconds
n/a None n/a
NBULogCollector Collects Symantec NetBackup logfile related information. It sets allconsumer parameters in the NBU_LOG_CONTAINER andNBU_LOG application classes.
Poll Time: 1800 seconds
n/a None n/a
157 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBULoginStatus* Monitors the status of theNetBackup KM login details(username/password) for theoperating system. It is set by the NBU_SERVER application classdiscovery. If no valid username/password is detected for theoperating system, this parameterwill be set to Failure state. If thereare any suspicious commands, thisparameter will be set to Suspiciousstate.
If this status parameter changes towarning or alarm state, therecovery action will trigger anevent and annotate the last datapoint.
0 = OK1 =Suspicious2 = Failure
Warning = 1Alarm = 2
CollectionStatus
NBUMonitoringMode* Monitors failover mode of theNetBackup KM. It is set by the NBU_SERVER application classdiscovery.By default NetBackup KM runs inPermanent Single-node Mode butmulti-node monitoring can beconfigured. For more details referto Configuring Multi-NodeMonitoring Mode.
0 =PermanentSingle-node Mode1 =TemporarySingle-nodeMode 2 = ActiveMulti-nodeMode3 = PassiveMulti-nodeMode-1 =Unknown
None CollectionStatus
NBUNodeStatus* Monitors error messages for theSymantec NetBackup applicationon this managed system. It is set bythe NBU_SERVER application classdiscovery.If any of the Symantec NetBackupapplication daemons is notrunning, this parameter will be setto Failure state. The list of criticalSymantec NetBackup daemons canbe customized using the KMcommand Configuration>NodeStatus from the SymantecNetBackup icon. If there are anysuspicious commands due to anerror from the master/mediaserver, this parameter will be set toSuspicious state.
0 = OK1 =Suspicious2 = Failure
Warning = 1Alarm = 2
Availability
158Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
If this status parameter changes towarning or alarm state, therecovery action will trigger anevent and annotate the last datapoint.
NBUPolicyCollector Collects Symantec NetBackuppolicy and policy client relatedinformation. It sets all consumerparameters in the NBU_POLICY_CONTAINER,NBU_POLICY, and NBU_PCLIENTapplication classes.By default, this collector isexecuted only on the master server.
Poll Time: 900 seconds
n/a n/a n/a
NBUPoolCollector Collects Symantec NetBackupvolume pool related information. Itsets all consumer parameters in NBU_POOL_CONTAINER andNBU_POOL application classes.By default, this collector isexecuted only on the master server.
Poll Time: 1800 seconds
n/a n/a n/a
NBURequestCollector Collects Symantec NetBackuppending request relatedinformation. It sets all consumerparameters in the NBU_MOUNT_CONTAINER andNBU_MOUNT application classes.By default, this collector isexecuted only on the master server.
Poll Time: 300 seconds
n/a n/a n/a
NBUStorageCollector Collects Symantec NetBackupstorage pool related information. Itsets all consumer parameters inthe NBU_STORAGE_CONTAINER,NBU_STORAGE, NBU_DPOOL andNBU_DVOLUME applicationclasses. By default, this collector isexecuted only on the master server.
Poll Time:1800 seconds
n/a n/a n/a
NBUUpdateAgent Is used by the NetBackup KM to setthe PATROL Agent KM variableswhen the PATROL Console user isnot authorized to update (ACL) anyPATROL Agent variables. It isactivated automatically when theKM fails to update the PATROLAgent.
n/a n/a n/a
159 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Poll Time: 300 seconds
* Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instancein BPPM.
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, or NT).
Product Name Name of the Knowledge Module.
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
Function Description
Refresh Process Cache Forces the PATROL Agent to reload its process cache from the kernel processlist.
160Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
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. Bydefault, all new commands are reloaded automatically.
Administration > StartMaster Server
Starts master server daemons.
Administration > StopMaster Server
Stops master server daemons.
Administration > StartMedia Server
Starts media server daemons.
Administration > StopMedia Server
Stops media server daemons.
Configuration > Login Accesses the Login Configuration dialog for viewing and entering NBU KM logindetails for the operating system.This user account should have privileges to execute Symantec NetBackupadministration commands and can use sudo privileges on Unix PATROL Agents.This user account will be used by NBU KM pre-discoveries, discoveries, datacollectors, recovery actions, and InfoBoxes to execute operating systemcommands. It will not be used by any KM commands.The password is encrypted and stored on the PATROL Agent using the BMCPATROL encryption function.
Configuration > Preloading
Accesses the Preloading Configuration dialog, which adds or removes the KMfrom PATROL Agent variable "/AgentSetup/preloadedKMs". By preloading theNBU KM, the PATROL Agent will monitor the Symantec NetBackup applicationwithout any PATROL Console connection.
Configuration > Monitoring Mode
Accesses the Failover Mode Configuration dialog, which is used for enabling ordisabling KM failover, when monitoring clustered Symantec NetBackupenvironment.
Configuration > Paths Accesses the Path Configuration dialog, which displays and sets all paths usedby NBU KM.Paths are automatically discovered by the NBU KM server discovery. They areused as environment variables for executing various Symantec NetBackupapplication commands. Altering these paths may impact the operation of theKM.
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.
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 isused for setting PATH environment variable. The KM discovers and set thisautomatically. This menu can be used, if the discovered paths are incorrect.
Library Paths are the Application and operating system library path, which isused for setting the following environment variables:
LD_LIBRARY_PATH (on Solaris)SHLIB_PATH (on HP-UX)
161 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
LIBPATH (on AIX)The KM discovers and set this automatically. This menu can be used, if thediscovered paths are incorrect.
Log Directory Path: The log path where NetBackup maintains the dailymessages logs.
Node Type Accesses the Node Type dialog, which displays and sets the type of theSymantec NetBackup application node.The NBU KM master/media server discovery detects the type of the nodeautomatically; the type can either be Master Server or Media Server. Theoperation of the KM depends on this node type.
Node Status Accesses the Node Status Configuration dialog for viewing and modifying thedaemon names monitored for node status.The NBU KM checks for the existence of these daemons to determine the statusof the node (parameter NBUNodeStatus). By default, the following daemons aresought:
Instance Limits Accesses the Instance Limits Configuration dialog to view and modify themaximum number of NBU KM application instances allowed for eachapplication class.
Debug Accesses the Debug Configuration dialog for enabling/disabling the NBU KMdebug switches. By default, all KM debug messages are sent to a set of files anda task window.
KM Status Generates a summary report containing information on the managed system.
About Displays information about the product and manufacturer.
162Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBU_STORAGE_CONTAINERIcon
Parameters
Name Description Units Default AlertConditions
BPPM Type
NBUStorageCollectorExecTime
Inactive standard parameter monitorsthe collector execution time. Toactivate this parameter, use the PSLbelow, and restart the PATROL Agent:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBUStorageCollectorExecTime", 1);
When activated it will run everyminute and trigger a warning when thecollector runs for more than theobserved maximum time. Thismaximum time can be overridden by apreset value (example: 3600 seconds),using the PSL below:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBUStorageCollectorWarn",3600);
seconds Warning > presetvalue orobservedmaximum(default)
CollectionStatus
NBUStorageDetails Set by NBUStorageCollector.Displays all data returned to thestandard out from commandsexecuted by the data collector.
n/a n/a n/a
For detailed information about Baselining and KPI, see Managing Baselines and Key Performance Indicators.
* Parameters marked with an asterisk are used by default when visualizing the corresponding monitor instancein BPPM.
InfoBox
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.
163 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Collector Name Name of the data collector that sets variables and parameters under thisapplication instance.
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 > Storages Accesses the dialog for specifying which storages are to be monitored by theNBU KM. By default, all local and remote storages are monitored for a masterserver and all local storages are monitored for a media server.
Configuration > StoragesUp/Down Status
Accesses the global configuration for determining the up/down status formonitored storage instances.
By default, the following NBUStorageUpDownState toNBUStorageUpDownStatus mapping rule is used:
Configuration > DiskPools
Sets which disk pools of the selected storage are to be monitored by the NBUKM. By default, all disk pools of the selected storage are monitored.
Configuration > DiskPools Up/Down Status
Accesses the global configuration for determining the up/down status formonitored disk pool instances.
By default, the following NBUDPoolUpDownState to NBUDPoolUpDownStatusmapping rule is used:
Configuration > DiskVolumes
Accesses the dialog for specifying which disk volumes of the selected disk poolare to bemonitored by the NBU KM. By default, all disk volumes of the selected disk poolaremonitored.
Configuration > DiskVolumes Up/DownStatus
Accesses the global configuration for determining the up/down status formonitored disk volume instances.
By default, the following NBUDVolumeUpDownState toNBUDVolumeUpDownStatus mapping rule is used:
164Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
NBU_STORAGEIcon
Parameters
Storage monitoring is disabled in passive multi-node mode
Name Description Units Default AlertConditions
BPPM Type
NBUStorageSummary Set by NBUStorageCollector.Summarizes the storageinformation as reported bycommands executed by the datacollector.
n/a n/a n/a
NBUStorageUpDownState
Set by NBUStorageCollector.Displays the up/down state of thestorage.
0 = Down1 = Up-1 =Unknown
None Availability
NBUStorageUpDownStatus
Set by NBUStorageCollector.Monitors the up/down status of thestorage. This status is determinedby the storage status mapping ruledefined in the KM commandConfiguration>Storage(s) Status.
If this status parameter changes towarning or alarm state, therecovery action will trigger an eventand annotate the last data point.
0 = OK1 =Suspicious2 = Failure
Warning = 1Alarm = 2
Availability
InfoBox
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 thisapplication instance.
Collector Next Start Date & time when the next data collection cycle is expected to start.
Collector Status Data collector execution status (Idle or Running).
165 Classes and Parameters
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Description Description of the storage.
Storage Server Type Type of the storage server.
Storage Server Name of the host where the storage is attached to.
Up/Down State Up/down status of the storage.
Menu Commands
Function Description
Configuration > Storage Sets the storage instance to be enabled or disabled for monitoring by the NBUKM.
Configuration > StorageUp/Down Status
Accesses the individual configuration for determining storage up/down statusfor the selected storage instance.By default, the global NBUStorageUpDownState to NBUStorageUpDownStatusmapping rule is used, as configured at the container level.
Configuration > DiskPools
Sets which disk pools of the selected storage are to be monitored by the NBUKM. By default, all disk pools of the selected storage are monitored.
Configuration > DiskPools Up/Down Status
Accesses the configuration for determining up/down status for the monitoreddisk pool instances on the selected storage instance.By default, the global NBUDPoolUpDownState to NBUDPoolUpDownStatusmapping rule is used, as configured at the container level.
Configuration > DiskVolumes
Accesses the dialog for specifying which disk volumes of the selected disk poolare to be monitored by the NBU KM. By default, all disk volumes of the selecteddisk pool are monitored.
Configuration > DiskVolumes Up/DownStatus
Accesses the configuration for determining up/down status for the monitoreddisk volume instances on the selected storage instance.By default, the global NBUDVolumeUpDownState toNBUDVolumeUpDownStatus mapping rule is used, as configured at thecontainer level.
Additional Information
167 Troubleshooting
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
TroubleshootingThe table below will help you diagnose any problems you may encounter when installing orrunning Symantec 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 selectingthe menu KM Status from the Symantec NetBackup or NBU_SETUP icon. Run this report todiagnose any problems.
The NetBackup KM triggers PEM events for most severe problems. Each event triggered fromthe KM includes an Expert Advice, which provides details about the problem and somesuggestions to resolve 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/knowledgefolder.
Symantec NetBackup KM for PATROL files have not been installed correctly underthe PATROL installation directory on the PATROL Console.
NBU_SETUPicon does notappear after loading
Check whether this managed node is a supported Symantec NetBackup node (master server ormedia server), and it is configured properly.
Check that the version of Symantec NetBackup is supported by the Symantec NetBackup KM forPATROL.
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/pslInstructionMaxhas been increased as suggested in section Changes to BMC PATROL. Check the messages in thePATROL 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 NBULoginStatusis in suspicious (warning)status
This parameter will also show a “suspicious” state if any command executed byNetBackup KM fails.
Check the annotation point on the first state change data point of this parameter to look for anyfailing commands. If an annotation point cannot be found, or if it is not up-to-date, check the KMStatus Report, which can be viewed by selecting the menu KM Status from the SymantecNetBackup icon. These errors are produced from the Symantec NetBackup commands executedby the NetBackup KM.
Check that the operating system user configured in the menu Configuration>Login can executeall NetBackup commands and access the NetBackup files.
All/some KM objectsdisappear from theConsole
Check whether there is a KM version mismatch between the PATROL Console and the PATROLAgent, possibly after an improper upgrade of the KM. Check the messages in the PATROLConsole 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.
168Troubleshooting
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
All/some KM application instances donot appear
Check that the KM instance limits have not been exceeded. Look for any error messages on theSOW, 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. These errorsare also displayed in the KM Status Report, which can be viewed by selecting the menu KMStatus 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 KMhasnot changed in accordancewith theRelease Notesaftera KM upgrade
Check the version of the KM from the main InfoBox. If it has not changed, then the installation isnot complete. Make sure both the PATROL Console and the PATROL Agent are uninstalled andinstalled correctly during the KM upgrade
NetBackup KMtakes a longtime torefresh the parametersand applicationclasses on the PATROL Console
Data collectors run according to their scheduling interval (polling cycle) defined inthe KM. These intervals are defined for a standard environment with minimalresource impact. These intervals can be customized from the PATROL DeveloperConsole to suit your environment. Refer to the PATROL Console User Guide for moredetails.
Poorperformance of theSymantec NetBackup master/mediaserver after installingthe KM
This happens if the NetBackup KM is installed on a heavily used system. Dependingon the complexity of your Symantec NetBackup environment, the NetBackup KM mayconsume more resources to interrogate the application and process the data. Insuch a complex environment, the NetBackup KM may require some fine tuning tooptimize the available resources. Consider the 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 9 amand 4 pm everyday, except weekends, then disable job data collector (NBUJobCollector) duringthis 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 containsfollowing details, delimited by pipe (|):enabled (1)/disabled (0) data collection,default start/end times in number of seconds since midnight, start/end times fornon-default days starting from Sunday through to Saturday.
The JOB_TEXT command which sets display only text parameter NBUJobText, can be disabled toimprove the performance using the PSL below:
%PSL pconfig("REPLACE", "/Runtime/NBU/NBU_JOB/jobCollectText", 0);
169 Troubleshooting
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
%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 inHH:MM:SS 24-hour clock>|<duration in seconds>”. The above “23:59:00|120” setsall collectors to sleep between 23:59:00 and 00:01:00 (2 minutes) every day beforeexecuting 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 NBUClientCollector andNBUPolicyCollector may affect the overall performance. In such environment disable theNBUClientCollector, or set their instance limits to 0 (zero), using menu Configuration> InstanceLimits.
Also refer to Infinite Loop Errors for a possible PATROL internal scheduling delaywhich may impact the performance of the KM.
Old active jobsare not removedfrom the console
By default, all active jobs are monitored, and they are exempted from ageing. It ispossible to change this behavior by Including Active Jobs in the menuConfiguration>Jobs from Jobs container.
Infinite LoopErrors(Error messageson the SOWreporting that some NetBackup KM data collectorsmay be in aninfinite 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 PSLfunction reaches this maximum threshold, it reports this error, and puts theexecution of this function to the back of the process queue. This will not only delaythe data collector, it will also impact the performance of the system.
To resolve this situation, the maximum number of instructions should be increasedto an optimum value. This depends on the complexity of your environment. It isrequired that the default value of 500,000 should be increased to at least 5,000,000on a standard Symantec NetBackup environment to enable the NetBackup KM datacollectors to execute without impacting your system.
If this still does not resolve the problem, you can disable this functionality bysetting the value of the tuning variable to zero (0).
Unable to turnon 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 Agentconfiguration variable with a timestamp value. This timestamp value determineswhen the debug should be turned off. For example, to turn on the debug for 60minutes from now, run the following PSL through PATROL Console:
170Troubleshooting
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
%PSL pconfig("REPLACE","/Runtime/NBU/<component>Debug",
time()+3600);
Where <Component> is either server for debugging the server discovery or name ofthe collector component in lower case followed by “Collector”, like daemonCollector for debugging daemon collector.
Oldacknowledged jobs are stillkept in the pconfig database.
By default the KM stores all acknowledged jobs. Use the following PSL throughPATROL Console to keep only the last <Number> of jobs:
%PSL pconfig("REPLACE",
"/Runtime/NBU/NBU_JOB/jobAcknowledgementCapacity",
<Number>);
Prefer adifferent job instancelabel
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 ForceFull Collection from the Jobs container instance to recreate the job instances.
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 yourNetBackup KM configuration. As you increase data collection frequency, increase the number ofinstances monitored by the KM or add functionality through customization, your CPU andmemory usage will increase.
When monitoring a standard installation of Symantec NetBackup using NetBackup KM, thePATROL Agent will consume between 5MBytes and 10MBytes of additional system memory. Anenterprise installation of Symantec NetBackup Master Server with multiple Media Servers,Clients, Storage Servers and Storage Units can consume more memory (as per other KMs used bythe PATROL Agent). The memory usage of NetBackup KM can be reduced by:
171 Impact on Resources
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
• 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, ifthe regular housekeeping is followed on all Symantec NetBackup systems.
Network Traffic
Under normal conditions, the NetBackup KM generates minimal network traffic. Most of the datais kept on the managed node. The amount of network traffic that it generates depends on thenumber of PATROL Consoles that are connected to the PATROL Agent and the frequency of datacollection.
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"Before Contacting 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 email notices when new product versions are released
Find worldwide BMC Software support center locations and contact information, includingemail addresses, 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 theWeb, call 800 537 1813. Outside the United States and Canada, please contact your local supportcenter for assistance. To find telephone and email contact information for the BMC Software
172Customer Support
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
support center that services your location, refer to the Contact Customer Support section of theSupport page on the BMC Software 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 CustomerSupport can 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, and service pack or other maintenance level, such as:
PUT or PTF
system hardware configuration
serial numbers
related software (database, application, and communication) including type, version, andservice
pack or maintenance
level
Sequence of events leading to the problem
Commands and options that you used
Messages received (and the time and date that you received them)
product error messages
messages from the operating system, such as "file system full"
messages from related software
173
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Index
- A -Abnormalities 59
Access
Executable Files 17
Files 17
Library Files 17
Paths 17
Permissions 17Acknowledge
Alarm 90
Alerts 90
Job Alerts 90
Log Alerts 90
Mount Request 64
Warning 90Acknowledgement
Configure 83
Job 83
Log 83Adapter 56
Add 57, 58
Create 57
Update 58Administer
Symantec NetBackup 63Administration
Robotic Drives 65
Standalone Drives 65Agent
PATROL 49AIX 17
Alarm
Acknowledge 90Alarm Filter State Rules 74
Alert Acknowledgement 83
Configure 83
Job 83
Log 83Alerts
Acknowledge 90Application Class
NBU_CLIENT 97
NBU_CLIENT_CONTAINER 95
NBU_DAEMON 101
NBU_DAEMON_CONTAINER 98
NBU_DATABASE 105
NBU_DATABASE_CONTAINER 103
NBU_DEVICE 108, 123
NBU_DEVICE_CONTAINER 110
NBU_DPOOL 112
NBU_DVOLUME 114
NBU_JOB 119
NBU_JOB_CONTAINER 116
NBU_LIBRARY 127
NBU_LIBRARY_CONTAINER 125
NBU_LOG 132
NBU_LOG_CONTAINER 130
NBU_MOUNT 135
NBU_MOUNT_CONTAINER 138
NBU_PCLIENT 140
NBU_POLICY 144
NBU_POLICY_CONTAINER 143
NBU_POOL 151
NBU_POOL_CONTAINER 150
NBU_SERVER 155
NBU_STORAGE 164
NBU_STORAGE_CONTAINER 162Available Media
Reports 150
- B -Baselines
BMC ProactiveNet Performance Management 59
Generation 59
Manage 59
Requirements 59BMC
BMC Portal 56
BMC ProactiveNet Performance ManagementPortal 14
BMC Software PATROL Agent 14
BMC Software PATROL Console 14
Requirements 14BMC PATROL
Changes 14
pslInstructionMax 14BMC ProactiveNet
Integration 56
174
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
BMC ProactiveNet Performance Management
Abnormalities 59
Baselines 59
Key Performance Indicators 59
KPI 59
- C -Changes 8
Check
Instance Limits 51Classes 94
Clients
Delete 69
Disable 69
Enable 69
Status Configuration 74Cluster
Configure 67Clustering Application 67
Commands
Reload 86Configure
Alert Acknowledgement 83
Cluster 67
Jobs Exit Status Filter 81
KM User Account 49
Log Error Filter 78
Log Scan Limit 80
Monitoring Period 71
Multi-Node Monitoring Mode 67
Node Status 76
Node Type 67
Paths 66
PATROL Agent 46
Policy Backup Restriction 82Customize
Monitored Mount Requests 77
Mount Request Date/Time Format 77
Mount Request Status 77
Mount Requests 77
- D -Daemons
Delete 69
Disable 69
Enable 69
Status Configuration 74Data Collection for Jobs
Force 84Data Collectors
Force 84Databases
Delete 69
Disable 69
Enable 69Debug
Disable 86
Enable 86
End 86
Files 86
Path 86Delete
Clients 69
Daemons 69
Databases 69
Logs 69
Policies 69
Policy Clients 69
Robotic Drives 69
Robotic Libraries 69
Standalone Drives 69
Storages 69
Volume Pools 69Disable
Clients 69
Daemons 69
Databases 69
Debug 86
Logs 69
Policies 69
Policy Clients 69
Robotic Drives 69
Robotic Libraries 69
Standalone Drives 69
Storages 69
Volume Pools 69Discoveries
Force 84Discovery
Verify 51Disk Space
Requirements 22
175
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
- E -Enable
Clients 69
Daemons 69
Databases 69
Debug 86
Logs 69
Policies 69
Policy Clients 69
Robotic Drives 69
Robotic Libraries 69
Standalone Drives 69
Storages 69
Volume Pools 69
- F -Failover Group Name 67
Files 24
ins_ALL_<version>.tar 23
ins_WINDOWS_<version>.exe 23
Setup 24
setup.exe 27
setup.sh 27
uninstall.exe 39
uninstall.sh 39Filtering Options
Clients 69
Daemons 69
Databases 69
Logs 69
Policies 69
Policy Clients 69
Robotic Drives 69
Robotic Libraries 69
Standalone Drives 69
Storages 69
Volume Pools 69Force
All Data Collectors 84
All Discoveries 84
Full Data Collection for Jobs 84
Selected Data Collectors 84
- G -Generate
Baselines 59
- H -HP-UX 17
- I -Improvement 8
InfoBox
Active 144
Application 97
Application Name 155
Application Version 155
Attempt 119
Available FS Space 132
Barcode 135
Binary Path 155
Client 119, 135
Collector Last End 95, 97, 98, 101, 103,105, 108, 110, 112, 114, 116, 119, 123, 125,127, 130, 132, 135, 138, 140, 143, 144, 150,151, 162, 164
Collector Last Start 95, 97, 98, 101, 103,105, 108, 110, 112, 114, 116, 119, 123, 125,127, 130, 132, 135, 138, 140, 143, 144, 150,151, 162, 164
Collector Name 95, 97, 98, 101, 103, 105,108, 110, 112, 114, 116, 119, 123, 125, 127,130, 132, 135, 138, 140, 143, 144, 150, 151,162, 164
Collector Next Start 95, 97, 98, 101, 103,105, 108, 110, 112, 114, 116, 119, 123, 125,127, 130, 132, 135, 138, 140, 143, 144, 150,151, 162, 164
Collector Status 95, 97, 98, 101, 103, 105,108, 110, 112, 114, 116, 119, 123, 125, 127,130, 132, 135, 138, 140, 143, 144, 150, 151,162, 164
Command 101
Completion Status 119
Control 108, 123
Copyright 155
Density 135
176
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
InfoBox
Description 97, 101, 105, 108, 112, 114,123, 132, 135, 140, 144, 151, 164
Device Host 108, 123
Disk Media ID 114
Disk Pool Name 114
Disk Type 114
Drive Index 108, 123
Duration 119
End 119
Exit Status 119
External Media ID 135
Files 119
Free Space 114
FS Percent Used 132
Group 151
Hardware 97, 140
High Watermark 112
Host Name 151, 155
Installation Path 97, 155
Job ID 119, 135
Job PID 119
Job Type 135
Keyword 144
Last Backup 105
Last Backup Duration 119
Last Backup End 119, 140, 144
Last Backup Files 119
Last Backup Job ID 105, 119, 140, 144
Last Backup Mode 105
Last Backup Size 119
Last Backup Start 119, 140, 144
Last Backup Status 140, 144
Last Full Backup End 140, 144
Last Full Backup Job ID 140, 144
Last Full Backup Start 140, 144
Last Incr Backup End 144
Last Incr Backup End Time 140
Last Incr Backup Job ID 140, 144
Last Incr Backup Start 140, 144
Last Purge 105, 132
Library Path 155
Log File Modification Time 132
Log File Size 132
Low Watermark 112
Master Server(s) 155
Max Jobs/Policy 144
Media ID 108, 123
Media Server 119, 135
Media Server(s) 155
Mode 135
Monitoring Mode 155
Monitoring Node 155
Multiple Data Stream 144
Name 97, 101, 105, 108, 112, 114, 123,132, 140, 144, 151
Node Name(s) 155
Node Type 155
Number of Read Mounts 114
Number of Write Mounts 114
Operating System 97, 140, 155
Operation 119
Owner 101, 119
Path 105, 108, 123, 132
PATROL Agent Version 155
Percent Completed 119
PID 101
Platform 155
Policy Name 119, 135, 140
Policy Type 119
PPID 101
Priority 119, 140, 144
Product Name 155
Product Release Date 155
Product Version 155
Raw Size 112
Recorded Media ID 135
Request ID 108, 123, 135
Request Time 135
Residence 144
Robot Drive Number 123
Robot Number 123
Robot Type 123
Schedule 119
Schedule End 119
Schedule Start 119
Schedule Type 119
Serial Number 108, 123
Size 119
Start 119
Status 97, 101, 108, 119, 123, 144
Storage Server 112, 114, 164
Storage Server Type 112, 164
Storage Unit 119, 135
Subtype 119
Support 155
Time Remaining 119
Total Capacity 114
177
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
InfoBox
Total FS Space 132
Type 108, 119, 123, 144
Up/Down State 112, 114, 164
Usable Size 112
Used Percent 114
User 108, 123, 135, 151
Version 97
Volume Group 135
Volume Pool 144
Web Site 155Install / Un-install 26, 39
BMC Software Installation Utility 23
Log 27
Packages 24
Procedure 27
Setup Files 24Instance Limits
Check 51Integration
BMC ProactiveNet 56Integration Service Agent 57
Introduction 26
Issues
Fixed 8
- J -Job Alerts
Acknowledge 90Jobs
Configure 71
Monitoring Period 71
Status Configuration 74Jobs Exit Status Filter
Configure 81
- K -Key Performance Indicators
BMC ProactiveNet Performance Management 59
Manage 59KM
Configure 49
Initial Setup 53
Load 45, 56
Preload 46
Preloaded 47, 48
Unload 47, 48
User Account 49KPI
BMC ProactiveNet Performance Management 59
Manage 59
- L -Linux 17
Load
KM 45, 56
PATROL Central 45Log Alerts
Acknowledge 90Log Error Filter
Configure 78Log Scan Limit
Configure 80Logs
Delete 69
Disable 69
Enable 69
- M -Manage
Baselines 59
Key Performance Indicators 59
KPI 59Managed Node
Status Configuration 74Master Server
Configure 67Master/Media Server
Start 63
Stop 64Media Server
Configure 67Menu Commands
About 155
Acknowledgement 116, 119, 132
Administration 123, 135, 138, 155
Alarms 116, 132
Alert 119
All 116, 132
Assign 135
178
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Menu Commands
Assign All 138
Client 97
Client Status 97
Clients 95
Clients Status 95
Configuration 95, 97, 98, 101, 103, 105,108, 110, 112, 114, 116, 127, 130, 132, 138,140, 143, 144, 150, 151, 162, 164
Daemon 101
Daemon List 98
Daemon Status 101
Daemons 98
Daemons Status 98
Database 105
Database Backup Information 103
Databases 103
Debug 155
Deny 135
Deny All 138
Disk Pool 112
Disk Pool Up/Down Status 112
Disk Pools 164
Disk Pools Up/Down Status 162, 164
Disk Volume 114
Disk Volume Up/Down Status 114
Disk Volumes 112
Disk Volumes Up/Down Status 112, 162,164
Drive Cleaning Statistics 108, 110, 125
Force Discovery 155
Force Full Collection 116
Instance Limits 155
Jobs 116
Jobs Alert Acknowledgement 116
Jobs Erroneous Exit Status 116
Jobs Status 116
KM Status 155
Log 132
Log Alert Acknowledgement 132
Log Filter 132
Log Scan Limit 132
Login 155
Logs 130
Logs Alert Acknowledgement 130
Logs Filter 130
Logs Scan Limit 130
Media List 151
Messages List 130
Monitoring Mode 155
Mount Request Date/Time Format 138
Mount Requests 138
Mount Requests Status 138
Node Status 155
Node Type 155
Offline Drive 123
Online Drive 123
Paths 155
Pending Requests 138
Policies 143
Policies Backup Restriction 143
Policies Status 143
Policy 144
Policy Backup Restriction 144
Policy Client 140
Policy Clients 144
Policy Schedule 144
Policy Status 144
Preloading 155
Refresh Parameters 155
Refresh Process Cache 155
Reload Commands 155
Reports 98, 103, 108, 110, 125, 127, 130,138, 144, 151
Resubmit 135
Resubmit All 138
Robotic Drive 123
Robotic Drive Status 123
Robotic Drives 127
Robotic Drives Status 125, 127
Robotic Libraries 125
Robotic Libraries Status 125
Robotic Library 127
Robotic Library Contents 127
Robotic Library Status 127
Standalone Drives 108, 110
Standalone Drives Status 108, 110
Start Master Server 155
Start Media Server 155
Stop Master Server 155
Stop Media Server 155
Storage 164
Storage Up/Down Status 164
Storages 162
Storages Up/Down Status 162
Volume Pool 151
Volume Pools 150
Warnings 116, 132
179
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Monitor Type 57
Monitored Mount Requests
Customize 77Monitoring Period
Configure 71
Jobs 71
Mount Requests 71Mount Request
Acknowledge 64Mount Request Date/Time Format
Customize 77Mount Request Status
Customize 77Mount Requests
Configure 71
Customize 77
Monitoring Period 71
Status Configuration 74Multi-Node Monitoring Mode
Configure 67
- N -NBU_CLIENT
Application Class 97NBU_CLIENT_CONTAINER
Application Class 95NBU_DAEMON
Application Class 101NBU_DAEMON_CONTAINER
Application Class 98NBU_DATABASE
Application Class 105NBU_DATABASE_CONTAINER
Application Class 103NBU_DEVICE
Application Class 108, 123NBU_DEVICE_CONTAINER
Application Class 110NBU_DPOOL
Application Class 112NBU_DVOLUME
Application Class 114NBU_JOB
Application Class 119NBU_JOB_CONTAINER
Application Class 116NBU_LIBRARY
Application Class 127NBU_LIBRARY_CONTAINER
Application Class 125NBU_LOG
Application Class 132NBU_LOG_CONTAINER
Application Class 130NBU_MOUNT
Application Class 135NBU_MOUNT_CONTAINER
Application Class 138NBU_PCLIENT
Application Class 140NBU_POLICY
Application Class 144NBU_POLICY_CONTAINER
Application Class 143NBU_POOL
Application Class 151NBU_POOL_CONTAINER
Application Class 150NBU_SERVER
Application Class 155NBU_STORAGE
Application Class 164NBU_STORAGE_CONTAINER
Application Class 162New features 8
Node Status
Configure 76Node Type
Configure 67
Master Server 67
Media Server 67
- O -Operating Systems
Linux 23, 24, 27, 39
Unix 23, 24, 39
Windows 23, 24, 27, 39Options
Common services 27
Console Systems role 27
Managed System 27
View Log 27Oracle Solaris Cluster 67
Overview 11
180
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
- P -Parameter
NBULoginStatus 49Parameters 94
BURequestCollectorExecTime 138
ExtraFilesList 155
NBUClientCollector 155
NBUClientCollectorExecTime 95
NBUClientDetails 95
NBUClientState 97
NBUClientStatus 97
NBUClientSummary 97
NBUCreateDistribution 155
NBUDaemonCollector 155
NBUDaemonCollectorExecTime 98
NBUDaemonCPUDuration 101
NBUDaemonCPUUtilization 101
NBUDaemonDetails 98
NBUDaemonMemorySize 101
NBUDaemonProcessCount 101
NBUDaemonState 101
NBUDaemonStatus 101
NBUDaemonSummary 101
NBUDatabaseBackupElapsed 103, 105
NBUDatabaseCollector 155
NBUDatabaseCollectorExecTime 103
NBUDatabaseDetails 103
NBUDatabaseFSSpaceUsedPercent 105
NBUDatabaseSpaceAvailable 105
NBUDatabaseSpaceGrowthRate 105
NBUDatabaseSpaceUsed 105
NBUDatabaseSpaceUsedPercent 105
NBUDatabaseStatus 103
NBUDatabaseSummary 105
NBUDPoolSummary 112
NBUDPoolUpDownState 112
NBUDPoolUpDownStatus 112
NBUDPoolVolumeCount 112
NBUDriveCollector 155
NBUDriveCollectorExecTime 110
NBUDriveDetails 110
NBUDriveState 108
NBUDriveStatus 108
NBUDriveSummary 108
NBUDriveThroughput 108
NBUDVolumeReadStreamCount 114
NBUDVolumeSpaceAvailable 114
NBUDVolumeSpaceGrowthRate 114
NBUDVolumeSpaceUsed 114
NBUDVolumeSpaceUsedPercent 114
NBUDVolumeSummary 114
NBUDVolumeUpDownState 114
NBUDVolumeUpDownStatus 114
NBUDVolumeWriteStreamCount 114
NBUFileExcludeList 140
NBUFileIncludeList 140
NBUJobActiveBackupCount 116
NBUJobActiveBackupReduction 116
NBUJobActiveCount 116
NBUJobActiveNonBackupCount 116
NBUJobCollector 155
NBUJobCollectorExecTime 116
NBUJobDetails 116
NBUJobDuration 119
NBUJobFileCount 119
NBUJobQueuedBackupCount 116
NBUJobQueuedBackupReduction 116
NBUJobSize 119
NBUJobState 119
NBUJobStatus 119
NBUJobSummary 119
NBUJobText 119
NBUJobThroughput 119
NBULibraryCollector 155
NBULibraryCollectorExecTime 125
NBULibraryDetails 125
NBULibraryMediaAssignedCount 127
NBULibraryMediaAvailableCount 127
NBULibraryMediaAvailablePercent 127
NBULibraryMediaCleaningLeft 127
NBULibraryMediaCount 127
NBULibraryMediaScratchCount 127
NBULibraryMediaScratchPercent 127
NBULibraryMediaUnassignedCount 127
NBULibraryMediaUnassignedPercent 127
NBULibraryState 127
NBULibraryStatus 127
NBULibrarySummary 127
NBULibraryThroughput 127
NBULibraryUpDriveCount 127
NBULogAlarmCount 132
NBULogAlarmText 132
NBULogCollector 155
NBULogCollectorExecTime 130
NBULogDetails 130
181
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Parameters 94
NBULogFSSpaceUsedPercent 132
NBULoginStatus 155
NBULogSpaceAvailable 132
NBULogSpaceGrowthRate 132
NBULogSpaceUsed 132
NBULogSpaceUsedPercent 132
NBULogSummary 132
NBULogText 132
NBULogWarningCount 132
NBULogWarningText 132
NBUMediaActiveCount 151
NBUMediaActivePercent 151
NBUMediaCount 151
NBUMediaFrozenCount 151
NBUMediaFullCount 151
NBUMediaFullPercent 151
NBUMediaLoadedCount 151
NBUMediaLoadedEmptyCount 151
NBUMediaLoadedEmptyPercent 151
NBUMediaReadOnlyCount 151
NBUMediaScratchCount 151
NBUMediaSuspendedCount 151
NBUMediaUnassignedCount 151
NBUMediaUnassignedPercent 151
NBUMediaUnknownCount 151
NBUMonitoringMode 155
NBUNodeStatus 155
NBUPClientBackupSummary 140
NBUPClientBackupThroughput 140
NBUPClientFullBackupDuration 140
NBUPClientFullBackupFileCount 140
NBUPClientFullBackupSize 140
NBUPClientIncrBackupDuration 140
NBUPClientIncrBackupFileCount 140
NBUPClientIncrBackupSize 140
NBUPClientSummary 140
NBUPolicyBackupElapsed 144
NBUPolicyBackupSummary 144
NBUPolicyBackupThroughput 144
NBUPolicyCollector 155
NBUPolicyCollectorExecTime 143
NBUPolicyDetails 143
NBUPolicyFullBackupDuration 144
NBUPolicyFullBackupElapsed 144
NBUPolicyFullBackupFileCount 144
NBUPolicyFullBackupSize 144
NBUPolicyIncrBackupDuration 144
NBUPolicyIncrBackupElapsed 144
NBUPolicyIncrBackupFileCoun 144
NBUPolicyIncrBackupSize 144
NBUPolicyState 144
NBUPolicyStatus 144
NBUPolicySuccBackupElapsed 144
NBUPolicySummary 144
NBUPoolCollector 155
NBUPoolCollectorExecTime 150
NBUPoolDetails 150
NBUPoolSpaceAvailable 151
NBUPoolSpaceGrowthRate 151
NBUPoolSpaceUsed 151
NBUPoolSpaceUsedPercent 151
NBUPoolSummary 151
NBURDriveState 123
NBURDriveStatus 123
NBURDriveSummary 123
NBURDriveThroughput 123
NBURequestCollector 155
NBURequestDetails 138
NBURequestElapsed 135
NBURequestState 135
NBURequestStatus 135
NBURequestSummary 135
NBUStorageCollector 155
NBUStorageCollectorExecTime 162
NBUStorageDetails 162
NBUStorageSummary 164
NBUStorageUpDownState 164
NBUStorageUpDownStatus 164
NBUUpdateAgent 155
Refresh 84Paths
Binary 66
Configure 66
Debug Directory 66
Home Directory 66
Library 66
Netbackup Installation 66
NetBackup Log Directory 66
Temp Directory 66PATROL
Agent 49
PATROL Agent 47
PATROL Agent system 22
PATROL Central Console 47, 48
PATROL Central Console Server system 22
PATROL Central Web Server system 22
PATROL Console 47, 48
182
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
PATROL
PATROL Console system 22PATROL Agent
Configure 46
Restart 53PATROL Console 45
Restart 53Permissions
Access 17Platform
Upgrade 44Platforms
Unix 49Policies
Delete 69
Disable 69
Enable 69Policy Backup Restriction
Configure 82Policy Clients
Delete 69
Disable 69
Enable 69Preload
KM 46Preloaded
KM 47, 48Prepare
Debug Files 86ProactiveNet 57
PW Commands 58
- R -Refresh
Parameters 84Release Notes 8
Reload
Commands 86remote PATROL Agent Checking 67
Reports
Available Media 150Requirements
Additional 14
BMC ProactiveNet Performance ManagementPortal 14
BMC Software PATROL Agent 14
BMC Software PATROL Console 14
Disk Space 22
Security 17
Software 14
Symantec NetBackup™ 14
System 13Restart
PATROL Agent 53
PATROL Console 53Robotic Drives
Administration 65
Delete 69
Disable 69
Enable 69
Status Configuration 74Robotic Libraries
Delete 69
Disable 69
Enable 69
Status Configuration 74
- S -Security
Requirements 17Setup
Check 53
Initial 53
KM 53Solaris 17
Standalone Drives
Administration 65
Delete 69
Disable 69
Enable 69
Status Configuration 74Start
Master/Media Server 63Status Configuration
Clients 74
Daemons 74
Jobs 74
Managed Node 74
Mount Requests 74
Robotic Drives 74
Robotic Libraries 74
Standalone Drives 74Stop
Master/Media Server 64
183
Sym
ante
c N
etB
acku
p K
M f
or
PA
TRO
L V
ersi
on 2
.8.0
4
Storages
Delete 69
Disable 69
Enable 69Sudo 49
User 17Support
Customer Support 171
Email 171
Technical 171
Telephone 171
Web Site 171Symantec NetBackup
Administer 63System
HP-UX 13
IBM AIX 13
Microsoft Windows 13
Oracle Solaris 13
Red Hat Linux 13
Requirements 13
- T -Thresholds
Customize 58
Import 58Troubleshooting 167
- U -Unix 49
Unload
KM 47, 48Upgrade
Platform 44
- V -Verify
Application Discovery 51Veritas Cluster File System 67
Veritas Cluster Server 67
Volume Pools
Delete 69
Disable 69
Enable 69
- W -Warning
Acknowledge 90Warning Filter State Rules 74
What's new 8
About Sentry Software™Sentry Software, a strategic Technology Alliance Partner of BMC Software, providescomprehensive multi-platform monitoring solutions that enable management of thehardware and software aspects of all servers and SANs and covering up to 100 % ofcustom applications within the BMC ProactiveNet Performance Managementenvironment. Sentry Software also develops adapters for BMC Atrium Orchestrator thatenables IT administrators to automate the execution of common requests and tasksthat occur in the daily course of IT operations. Combined with BMC’s servers andnetwork automation tools, the adapters allow IT administrators to implementprovisioning and decommissioning workflows that cover all layers of their ITinfrastructure. Finally, Sentry Software designs connectors that bring storage capacitymetrics into BMC TrueSight Capacity Optimization to ensure IT administrators that theirstorage infrastructure is properly sized for their current and future needs.
Like us on Facebook:facebook.com/sentrysoftware
Follow us on Twitter:
twitter.com/sentrysoftware
LEARN MORE
To learn more about our solutions, please visit :www.sentrysoftware.com/solutions
© BMC Software, Inc. All rights reserved.
ABOUT MARKETZONE DIRECT PRODUCTS
The BMC MarketZone Directprogram sells and supportsthird-party products thatcomplement and/or augment BMCsolutions. MarketZone Directproducts are available under BMClicense and support terms.
About BMC Software™BMC Software helps leading companies around the world put technology at the forefrontof business transformation, improving the delivery and consumption of digital services.From mainframe to cloud to mobile, BMC delivers innovative IT management solutionsthat have enabled more than 20,000 customers to leverage complex technology intoextraordinary business performance—increasing their agility and exceeding anythingthey previously thought possible. For more information about BMC Software, visit
www.bmc.com.
Bus ines s thrives when IT runs s marter,fas ter and s tronger. That’s why the mos tdemanding IT organizations in the worldrely on BMC Software acros s dis tributed,mainframe, virtual and cloudenvironments . Recognized as the leader inBus ines s Service Management, BMC offersa comprehens ive approach and unifiedplatform that helps IT organizations cutcos t , reduce ris k and drive bus ines sprofit . For the four fis cal quarters endedSeptember 30,2011, BMC revenue wasapproximately $2.2 billion.
BUSINESS RUNS ON I.T .
I.T . RUNS ON BMC SOFT WARE