Veritas NetBackup KM for PATROL Version 3.1

Veritas NetBackup KM for PATROL

STORAGE MONITORING

USER DOCUMENTATION

Version 3.1.01

February 2017

http://sentrysoftware.com/Solutions/Storage_solution.asp

http://www.sentrysoftware.com

Contacting BMC Software

You can access the BMC Software Web site at http://www.bmc.com. From this Web site, you canobtain information about the company, its products, corporate offices, special events, and careeropportunities.

United States and Canada

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

Telephone 1 (713) 918 8800 or 1 (800) 841 2031 (Toll Free)

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

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

All other trademarks belong to their respective companies.

BMC Software considers information included in this documentation to be proprietary andconfidential. Your use of this information is subject to the terms and conditions of the applicableEnd User License Agreement for the product and the proprietary and restricted rights noticesincluded in this documentation.

Restricted Rights Legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVEDUNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any dataand computer software by the U.S. Government is subject to restrictions, as applicable, set forthin FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, andDFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC Software,Inc., 2101 CityWest Blvd., Houston, TX 77042-2827, USA. Any contract notices should be sent to thisaddress.

2

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Customer Support

You can obtain technical support by using the Support page on the BMC Software Web site or bycontacting Customer Support by telephone or e-mail.

Support Web Site

You can obtain technical support from BMC Software 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this Web site, you can:

Read overviews about support services and programs that BMC Software offers

Find the most current information about BMC Software products

Search a database for problems similar to yours and possible solutions

Order or download product documentation

Report a problem or ask a question

Subscribe to receive e-mail notices when new product versions are released

Find worldwide BMC Software support center locations and contact information, including e-mail addresses, fax numbers, and telephone numbers

You can also access product documents and search the Knowledge Base for help with an issue at http://www.sentrysoftware.com

Support by Telephone or E-mail

In the United States and Canada, if you need technical support and do not have access to the Web,call 800 537 1813. Outside the United States and Canada, please contact your local support centerfor assistance. To find telephone and email contact information for the BMC Software supportcenter that services your location, refer to the Contact Customer Support section of the Supportpage on the BMC Software Web site at http://www.bmc.com/support_home.

3

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

http://www.bmc.com/support_home




4

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

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

.......................................................................................................................................................................................14Software Requirements

.......................................................................................................................................................................................17Security Requirements

.......................................................................................................................................................................................23Disk Space Requirements

.......................................................................................................................................................................................24Remote Monitoring Requirements

.....................................................................................................................................................................................26Getting the BMC Software Installation Utility

.....................................................................................................................................................................................27Packages

.....................................................................................................................................................................................27Extracting the Setup Files

.....................................................................................................................................................................................30Installing Veritas NetBackup KM for PATROL

.....................................................................................................................................................................................41Uninstalling Veritas NetBackup KM for PATROL

.....................................................................................................................................................................................47Loading/Unloading the KM

.......................................................................................................................................................................................47Loading the KM

......................................................................................................................................................................47Loading the KM on PATROL Console

......................................................................................................................................................................48Loading the KM on PATROL Central

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

.......................................................................................................................................................................................49Unloading the KM

......................................................................................................................................................................49Unloading the KM from the PATROL Agent

......................................................................................................................................................................50Unloading the KM from the PATROL Console

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

.....................................................................................................................................................................................51Performing Post-Installation Operations

.......................................................................................................................................................................................52Configuring NetBackup Nodes Monitoring

.......................................................................................................................................................................................53Configuring the KM User Account

.......................................................................................................................................................................................56Verifying Application Discovery

.......................................................................................................................................................................................56Verifying the Instance Limits

.......................................................................................................................................................................................58Verifying the Initial Setup

.......................................................................................................................................................................................58Restarting PATROL Agent and PATROL Console

.....................................................................................................................................................................................60Integrating with BMC Portal

.....................................................................................................................................................................................60Integrating with BMC TrueSight OM

.....................................................................................................................................................................................62Administering Veritas NetBackup

.......................................................................................................................................................................................62Starting Master/Media Server

.......................................................................................................................................................................................63Stopping Master/Media Server

5

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

.......................................................................................................................................................................................64Bringing Standalone Drives Online or Offline

.......................................................................................................................................................................................64Bringing Robotic Drives Online or Offline

.....................................................................................................................................................................................65Configuring the KM

.......................................................................................................................................................................................65Configuring Paths

.......................................................................................................................................................................................66Specifying the Node Type

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

.......................................................................................................................................................................................68Filtering Elements to Monitor

.......................................................................................................................................................................................71Blocking the Remote Monitoring

.......................................................................................................................................................................................71Configuring Monitoring Periods

.......................................................................................................................................................................................74Configuring the Elements Status

.......................................................................................................................................................................................76Configuring the Node Status

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

.......................................................................................................................................................................................80Configuring the Log Filter

.......................................................................................................................................................................................82Configuring the Log Scan Limit

.......................................................................................................................................................................................83Configuring Jobs Erroneous Exit Status Filter

.......................................................................................................................................................................................85Configuring Policy Backup Restriction

.......................................................................................................................................................................................86Configuring Alert Acknowledgement

.......................................................................................................................................................................................88Forcing the Classic Mode

.......................................................................................................................................................................................89Refreshing Parameters

.......................................................................................................................................................................................90Reloading Commands

.......................................................................................................................................................................................91Enabling the Debug Mode

.....................................................................................................................................................................................94Acknowledging Alerts

.....................................................................................................................................................................................95Generating Reports

.....................................................................................................................................................................................98NBU_CLIENT_CONTAINER

.....................................................................................................................................................................................100NBU_CLIENT

.....................................................................................................................................................................................102NBU_DAEMON_CONTAINER

.....................................................................................................................................................................................104NBU_DAEMON

.....................................................................................................................................................................................107NBU_DATABASE_CONTAINER

.....................................................................................................................................................................................110NBU_DATABASE

.....................................................................................................................................................................................112NBU_DEVICE_CONTAINER

.....................................................................................................................................................................................114NBU_DEVICE

.....................................................................................................................................................................................117NBU_DPOOL

.....................................................................................................................................................................................120NBU_DVOLUME

.....................................................................................................................................................................................123NBU_JOB_CONTAINER

.....................................................................................................................................................................................126NBU_JOB

6

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

.....................................................................................................................................................................................129NBU_LDEVICE

.....................................................................................................................................................................................132NBU_LIBRARY_CONTAINER

.....................................................................................................................................................................................134NBU_LIBRARY

.....................................................................................................................................................................................138NBU_LOG_CONTAINER

.....................................................................................................................................................................................140NBU_LOG

.....................................................................................................................................................................................144NBU_MAIN

.....................................................................................................................................................................................145NBU_MEDIASERVER_CONTAINER

.....................................................................................................................................................................................147NBU_MEDIASERVER

.....................................................................................................................................................................................150NBU_MOUNT_CONTAINER

.....................................................................................................................................................................................152NBU_MOUNT

.....................................................................................................................................................................................154NBU_PCLIENT

.....................................................................................................................................................................................157NBU_POLICY_CONTAINER

.....................................................................................................................................................................................159NBU_POLICY

.....................................................................................................................................................................................164NBU_POOL_CONTAINER

.....................................................................................................................................................................................166NBU_POOL

.....................................................................................................................................................................................170NBU_SERVER

.....................................................................................................................................................................................177NBU_STORAGE_CONTAINER

.....................................................................................................................................................................................179NBU_STORAGE

.....................................................................................................................................................................................181Managing Baselines and Key Performance Indicators

.....................................................................................................................................................................................183Troubleshooting

.....................................................................................................................................................................................187Impact on Resources

Release Notes for v3.1.01

8

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

What's NewNBU-720: Veritas NetBackup KM for PATROL has been improved to support all PATROL Agentv10+ versions and prevent failures due to a compatibility error.

Changes and ImprovementsNBU-748: The overall performance of the Veritas NetBackup KM for PATROL has beenimproved.

Fixed IssuesNBU-729: Remote NetBackup Nodes did not appear as separate devices in TrueSight evenwhen the option Create a separate device in TrueSight had been selected. To solve thisissue, the I2D Device Mapping configuration variable (/NBU/disableI2D) is now set to 0 bydefault.

NBU-747: When installing NetBackup KM on an AIX platform, the error “UnsupportedPATROL Agent platform (RS6000)” was displayed in the System Output Window (SOW) andcaused the KM to be disabled.

Overview

10

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Veritas NetBackup KM for PATROL monitors your Veritas NetBackup environment within acentralized management console to ensure it runs efficiently 24 hours a day.

The KM more especially monitors the:

Clients: state and status

Daemons: processor utilization, memory size, number of processes found, state and status

Catalog databases: space utilization, state and status

Devices: state and status, throughput of the standalone drive during the last backup activity

Disk pools: up/down state and status, number of volumes

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

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

Media Server availability: status of local or remote media server.

Mounts: elapsed time, state and status

Policy clients: files and file systems excluded from and included in backup, throughput, fullbackup and incremental backup information

Policies: elapsed time, throughput, full backup and incremental backup information

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

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

Disk storage and volume pools: space utilization, status, count, 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

12

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

Review the System, Software, Security, Disk Space, and remote monitoring requirements

Get the BMC Software Installation Utility

Download the Installation Packages

Extract the Setup Files

13

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

RequirementsSystem RequirementsVeritas 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® 2008, 2008 R2, 2012

Since version 3.0.00 of NetBackup KM, commands reloading is not required if the operating system isupgraded (or downgraded) at a later date.

14Requirements

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Software RequirementsVeritas NetBackup KM for PATROL supports:

Software Version

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

Veritas NetBackup™ 7.7

BMC Software PATROL Agent 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 Management 9.x

BMC TrueSight Operations Management 10

Since version 3.0.00 of NetBackup KM, commands reloading is not required if the operating system isupgraded (or downgraded) at a later date.

15 Requirements

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

If you are 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).Alternatively a soft link from /bin/ksh to /bin/bash will be needed.

Any

When running NBU KM on MicrosoftWindows x64 managed nodes

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

Any

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

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

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

16Requirements

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Changes Required

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

Some changes must however be made to BMC PATROL to improve the performance of VeritasNetBackup 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 Veritas 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 pslInstructionMax variable %PSL pconfig("REPLACE",

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

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

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

In large Veritas NetBackup systems, the value of 5,000,000 for the tuning variable “pslInstructionMax” maystill be insuf f icient. In such situations, error messages will appear on the PATROL Console System OutputWindow (SOW) reporting that some NetBackup KM data collectors are in an inf inite loop. In this case youcan 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/<node-id> and /Runtime/NBU/<node-id> paths. PATROL Agent user(default: patrol) should be able to read and write to these pconfig variables at anytime. If AccessControl List (ACL) is used to control which users are authorized to connect to a PATROL Agent,please make sure that the mode for PATROL Agent user includes “C” in the PATROL Agentvariable “/AgentSetup/accessControlList”. Please refer the PATROL Agent Ref erence Manual formore details.

To support bash shell platforms when ksh is not installed

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

ln –s /bin/bash /bin/ksh

17 Requirements

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

a non-root account, such as patrol, configured in Veritas NetBackup application toadminister the Veritas NetBackup application.

On Windows platforms:

an administrator user

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

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

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

18Requirements

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Access Permissions

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

Executable and Library Files accessed by the NetBackup KM User

Unix Microsoft Windows

INSTALL_PATH/netbackup INSTALL_PATH\NetBackup

INSTALL_PATH/netbackup/bin INSTALL_PATH\NetBackup\bin

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

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

INSTALL_PATH/volmgr/bin INSTALL_PATH\Volmgr\bin

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

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)

cluster (in Microsoft 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

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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.

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(osp=="") { osp=trim(nthargf(grep("OSPlatform",ctl),"2-","=","="), " "); }

fields=lines(ntharg(var,"1-","/"));

old_host=host;

host=(fields == 5)? ntharg(var,"3","/") : "localhost";

if(host!=old_host)

{

if((osp!="WINDOWS") && sudoers) { printf("\n\nCommands used with sudo:\n%s",sort(sudoers)); }

printf("\n\nOn %s:\n\n", host);

i=0; sudoers=""; osp="";

}

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

{

met="";

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

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

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

else

{

scmd=cmd;

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

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

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

}

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

}

}

if((osp!="WINDOWS") && sudoers) { printf("\n\nCommands used with sudo:\n%s",sort(sudoers)); }

20Requirements

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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)

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

The configured login user should have sufficient privileges to run regedit command on themanaged node.

21 Requirements

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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 Veritas NetBackup installation path INSTALL_PATH,referenced below is normally /usr/openv or /opt/VRTSnetbp and PATROL_HOME is the pathwhere 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 Veritas NetBackup commands. Toprevent unauthorized access, ensure this user is only used within the KM and not made public forgeneral use.

Entering the non-root sudo user with ‘Use Sudo’ option selected 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

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. PATROL_HOME paths are only required for local monitoring.

22Requirements

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

On HP-UX



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









On AIX & Linux



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









23 Requirements

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Disk Space RequirementsVeritas 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 Veritas NetBackup, the PATROL Agent will generateapproximately 500 KBytes of history data per day. An enterprise installation of Veritas NetBackupon a master server with multiple media servers, clients, robotic libraries, and standalone driveswill generate more history data (as per other KMs used by the PATROL Agent). These history datafiles are recycled by PATROL depending on the PATROL Agent history retention period.

During execution, the KM creates and maintains temporary files under KM_TEMP andKM_DEBUG paths. By default they are all under PATROL_HOME/lib/NBU, where PATROL_HOMEpath is normally /opt/bmc/Patrol3/ (on Unix) or C:\Program Files (x86)\BMC Software\Patrol3\(on Microsoft Windows). Please make sure you have sufficient space under KM_TEMP andKM_DEBUG paths.

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

24Requirements

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

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

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

JAVA

NetBackup KM requires Java 1.6 or higher and a Java Runtime Environment (JRE) to be installedon the same system that runs the PATROL Agent.

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

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

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

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

25 Requirements

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NetBackup CLI User Account

A NetBackup CLI user is required to monitor NetBackup appliances. To create a NetBackup useraccount:

1. Open an SSH session on the NetBackup appliance

2. Log on as admin

3. Enter the following command: Main > Manage > NetBackupCLI > Create UserNamewhere UserName is the name to be used for the new user.

4. Enter a password for this new user account

5. A confirmation message appears stating the new user account was created successfully.

This user should have the privileges to execute NetBackup and OS commands as described in the Security Requirements section. The following sudo settings are therefore required on aNetBackup appliance:

# Added for NetBackup KM

User_Alias NBUKMUSERS = UserName

Defaults:NBUKMUSERS !lecture,!authenticate,\

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

SSH/WMI Connection

An SSH (UNIX/Linux platforms) or a WMI (Windows platforms) connection is required to monitorremote NetBackup servers and appliances. When using an SSH connection, the SSH host keyauthentication must be disabled on the remote host.

Disabling the SSH Host Key Authentication

SSH host key authentication is enabled by default on most NetBackup servers and appliances. To

disable it:

1. Open the global SSH configuration file (ssh_config) stored in the /etc/ssh/ directory on theremote host

2. Add the line StrictHostKeyChecking no

3. Save the file.

26Requirements

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Getting the BMC Software InstallationUtilityIn order to install Veritas 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 Veritas NetBackup KM for PATROL page onthe Sentry Software Website.

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

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

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

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

27 Getting the BMC Software Installation Utility

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

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

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

Every managed system with a PATROL Agent

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

The Console Server

PATROL Central – Web Edition

For remote monitoring, there is no need to install the PATROL Agent and Knowledge Module onthe remote NetBackup server(s).


Installing the KM

29

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Introduction

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

30

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

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

On Windows: Launch the setup.exe program

On UNIX: Launch the setup.sh script

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

Installation Wizard - Welcome

31 Installing Veritas NetBackup KM for PATROL

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

Installation Wizard - Reviewing License Agreement

32Installing Veritas NetBackup KM for PATROL

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

Installation Wizard - Selecting Installation Options


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

Installation Wizard - Selecting the Installation Directory


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

Installation Wizard - Selecting an Installation Type


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

6. Select one or several of the following options:

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

Console Systems to install Veritas NetBackup KM for PATROL on a PATROL Classic Console.

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

Click Next to continue.

Installation Wizard - Selecting Roles


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

7. Check the Veritas NetBackup KM for PATROL box to install the KM (it should be selected bydefault). Click Next to continue.Select the Java Runtime Environment program if you want to install it along with the KM (thisoption is only provided when you have previously downloaded the package).Click Next to continue.

Installation Wizard - Selecting Products and Components


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

Installation Wizard - Reviewing Installation Options


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

Installation Wizard - Installation Status


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

Installation Wizard - Installation Results


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

Installation Wizard - Completing and closing the Installation Wizard


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Uninstalling Veritas NetBackup KMfor PATROLUninstalling Veritas NetBackup KM for PATROL is an automated process managed by a wizard.The wizard goes through the necessary steps to remove Veritas NetBackup KM for PATROL and allfiles associated with it. You are simply prompt for the product's folder location and the product/components to uninstall.

To uninstall Veritas 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

42Uninstalling Veritas NetBackup KM for PATROL

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

43 Uninstalling Veritas NetBackup KM for PATROL

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

Un-install Wizard — Selecting Products and Components Directory


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

4. Click Start Uninstall.

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


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

Un-install Wizard — Status


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

Un-install Wizard — Uninstall Results


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

PATROL Console

PATROL Central

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

Loading the KMBefore loading the 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 Veritas NetBackup environment. If the automatic discovery successfullyfinds the Veritas 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 anyerror messages on the PATROL Console System Output Window (SOW) during the initial discovery.

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

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

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

3. Configure the KM.

48Loading/Unloading the KM

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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 Veritas NetBackup environment. If theautomatic discovery successfully finds the Veritas NetBackup master/media server 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 Veritas NetBackup KM for PATROL to operate all the time, without a PATROL Consoleconnection, you'll have to add it to the PATROL Agent configuration variable /AgentSetup/preloadedKMs.

To configure the PATROL Agent to preload the KM:

1. In the Console, right-click the Veritas NetBackup 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.

49 Loading/Unloading the KM

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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 to the uninstall procedure.

When the KM is unloaded:

from a PATROL Agent: PATROL stops monitoring the Veritas 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 VeritasNetBackup 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 Veritas 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 will thenhave 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.

50Loading/Unloading the KM

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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.

51 Loading/Unloading the KM

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

Configuring NetBackup Nodes

Configuring the KM user account

Verifying:

the application discovery

the instance limits

the initial setup

Restarting the PATROL Agent and PATROL Console.

52Performing Post-Installation Operations

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Configuring NetBackup Nodes MonitoringNetBackup KM allows you to monitor several NetBackup master and media servers, andNetBackup appliances with one PATROL agent. The configuration procedure is as follows:

1. Right-click the Veritas NetBackup main instance > Configuration > NetBackup Nodes.

Configuring NetBackup Nodes Monitoring

2. Specify the NetBackup server details:

Node ID: Enter a ID for the NetBackup node. This information is only required if a unique IDcannot be generated using the hostname provided.

(Required) Hostname/IP Address/FQDN: Enter the hostname, IP address, or FQDN of thenode to be monitored.

(Required) System Type: Specify whether the NetBackup node is a UNIX/Linux or Windows

53 Performing Post-Installation Operations

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

system.

(Required) Status: Select Enable to start the NetBackup node monitoring; Disable to stopit.

3. Check the Create a separate device in TrueSight box if you want the NetBackup nodes toappear as a separate device in TrueSight OM.

4. Click Update.

A NetBackup Setup node instance appears in the PATROL Console but the monitoring will notstart until the appropriate credentials are entered using the Configuration > Login KM Command.

Configuring the KM User AccountA user account with administrative privileges must be configured in BMC PATROL to read andexecute Veritas NetBackup application programs and file systems. Depending on the operatingsystems used, several options will be available.

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

a root user

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

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

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

an administrator user

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


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

To configure the KM User Account:1. In the Console, right-click the host instance > KM Commands > 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 and leavethe Username and Password fields empty

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


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

4. If you are monitoring a remote host, click Remote Connection Settings:

Remote Connection Settings

Connection Timeout (in Seconds): Enter the number of seconds after which the connectionto the remote node will timeout.

Maximum Connections: Enter the maximum number of simultaneous connections allowedto the remote node.

Click Accept.

5. Click OK.

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


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Verifying Application DiscoveryTo verify the application discovery:

1. Check that the NetBackup Setup instance changes to display the server type. If not, checkthe message in the NetBackup Setup instance and in the PATROL Console System OutputWindow (SOW). You can force a full discovery by right-clicking the NetBackup 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 server instance > KM Commands >Refresh Parameters.

If Veritas NetBackup master/media server is configured in a clustered environment, you willhave to enable Multi-node Mode monitoring.

Verifying the Instance LimitsBy default, Veritas NetBackup KM for PATROL monitors all the elements discovered, which mayrepresent an important workload to the PATROL agents and console. Because the monitoring ofsome elements may be irrelevant for various reasons, you can apply filters to indicate whichelements will be monitored or not.

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


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

To modify the default configuration

1. In the Console, right-click the monitored node > KM Commands > Configuration> InstanceLimits

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.


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Verifying the Initial SetupTo check the initial setup of the KM:

1. Check for any errors on the PATROL Console System Output Window (SOW) or in the NBU.logfile available in PATROL_HOME/log

2. Check whether the discovered files and directory paths are correct, using the menu Configuration > Paths from the server instance.

3. Refer to the label of the server instance to check whether the discovered Node Type iscorrect using the menu Configuration > Node Type from the server instance.

4. Check the InfoBoxes and Parameters of all the NetBackup KM instances and verify that theyare properly set.

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

6. Check the new value of NBULoginStatus set after completion of all data collection. If either isnot in OK state, open the annotation point to determine the cause of the error.

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

Right-click the server instance > KM commands > KM Status from the Veritas 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.

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

Integrating the KM

60

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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 TrueSightOperations ManagementNo specific integration steps need to be performed. To know how to use Veritas NetBackup KMfor PATROL in BMC TrueSight Operations Management, please refer to the TrueSight OperationsManagement - Veritas Backup Monitoring documentation.

Monitoring your Environment

62

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

Administering Veritas NetBackupVeritas 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 server instance > KM Commands > Administration and select StartMaster Server or Start Media Server depending on the server that you wish to start.

Starting the Master/Media Server

63 Administering Veritas NetBackup

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

Stopping the Master/Media Server

64Administering Veritas NetBackup

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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.

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

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


Online Drive

Offline Drive


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

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


Online Drive

Offline Drive


65 Administering Veritas NetBackup

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

Before configuring the KM, make sure:

the KM is loaded on the PATROL Console

the Veritas 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 server 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, the Log, and theRemote Temp Directory (remote nodes only) Paths

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.

66Configuring the KM

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

At that time, the Multi-node monitoring mode feature cannot be used if one or more cluster nodes aremonitored remotely.

To configure the multi-node monitoring mode:

67 Configuring the KM

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

Configuring the Multi-Node Monitoring Mode

2. Select Multi-node Mode

3. Select the appropriate Cluster Application

4. Indicate the Failover Group Name. Leave this field blank if you previously selected VeritasCluster File System. The 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.

Veritas NetBackup will then be monitored through the master or online node. The other nodes,which are standing by for a failover, will be in passive multi-node mode and only the VeritasNetBackup 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.


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

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

Media Server > KM Commands > Configuration > Media Server to filter media servers to bemonitored

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.


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Client Configuration dialog

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


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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.

3. To disable elements for monitoring:

In the current configuration list, select the elements to disable

Select Disable

Click Update

All jobs associated to disabled policies are not monitored.

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

4. To delete elements for monitoring:

In the current configuration list, select the elements to delete

Select Delete

Click Update

5. To add a new element to monitor:

Type the name of the element 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.


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Blocking the Remote Monitoring of a NetBackup ServerThe server owner/administrator may want to stop the monitoring of a remote NetBackup serverwhen performing maintenance work on this server. The monitoring can be blocked from therelevant NetBackup server and will not require making any changes from the monitoring PATROLAgent system(s). The administrator will just have to create a file named NBU_block under theRemote Temp Directory Path. By default, this path is set to /var/tmp (on UNIX/Linux) or C:\Windows\Temp (on Windows).

The PATROL Agent monitoring this NetBackup server will detect the block file during the nextdiscovery cycle and turn the server instance to NetBackup Setup (Monitoring Blocked).

To resume monitoring, the administrator will just have to delete the NBU_block file.

Configuring Monitoring PeriodsBy default, Veritas NetBackup KM for PATROL monitors all mount requests for 1 day, 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.


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Configuring the Jobs Monitoring Period

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

Job Filter Configuration dialog


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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 will have to force a full data collection to ensure alljobs are instantiated. To force data collection, right-click the Jobs instance > KM Commands> 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.


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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 the status andselect > KM commands > Configuration > Instance Status

Daemon Status Configuration dialog


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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, the NBUClientStatus 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 someNetBackup 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


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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 server instance > KM Commands > Configuration > Node Status.

Configuring Node Status


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

2. In the Monitored daemons list, select the daemons that will not 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:

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.


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Configuring Mount Requests Date/TimeFormatThe NetBackup KM uses Veritas 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 RequestsDate/Time Format

Mount Request Date/Time Format Configuration dialog


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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. TheTime zone f ield used will be the local time zone on the managed node.


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Configuring the Log FilterA log error filter can be configured to specify the regular expressions that will generate a warningor an alarm. Each time the KM will find these expressions in a log file or in NBULogText, the errormessage will be written to the NBULogAlarmText or NBULogWarningText parameter. By default,the default log filter is configured for the daily Veritas NetBackup messages file and the systemlog file. If you enabled additional log files for monitoring, you will have to customize the logfilter by adding appropriate expressions for those log files.

For more information about the possible error messages, refer to the Veritas NetBackup SystemAdministrator’s Guide and the Veritas NetBackup Troubleshooting Guide.

To configure the log error filter:

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

Log Filter Configuration dialog


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

6. Click Update.

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


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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), theKM, and the PATROL Agent.

To customize the log scan limit:

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

Customizing the Log Scan Limit

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

3. Click OK.


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Configuring Jobs Exit Status FilterThe NBUJobState parameter is set according to the completion state and the exit status reportedby Veritas NetBackup. The parameter 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 setting can be modified by moving orremoving 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 Filter

Configuring the Job Exit Status


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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 Error or Failed respectively. Multiple comma (,) delimited codes or a rangeusing a hyphen (-) can be 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).


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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 should at least last 5minutes.

4. Click OK.


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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 Agent ifthe 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


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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 will have toconfigure the job alert acknowledgement as follows:

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

Configuring Job Alert Acknowledgement

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

3. Click OK.


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Forcing the Classic ModeVeritas NetBackup KM for PATROL can either be configured from a BMC PATROL Console (ClassicMode) or BMC TrueSight Operations Management. When the KM is installed on a PATROL Agent,which is managed by Central Monitoring Administration (CMA), all the KM configuration menusare disabled in the PATROL Console. To configure NetBackup KM from a PATROL Console, youneed to force the KM to run in Classic Mode.

This will disconnect NetBackup KM from receiving configuration from Central MonitoringAdministration. Any monitoring that was configured in CMA and used by the PATROL Agent willbe removed and replaced by the configuration made from the PATROL Console. However, thiswill not delete the policies created in CMA from the configuration.

Any configuration for NetBackup KM received from Central Monitoring Administration will be ignored.

To force the KM to run in Classic Mode:

1. In the PATROL Console, right-click the Veritas NetBackup icon > KM commands > Configuration> Force Classic Configuration Mode

Forcing Classic Mode - Force Classic Configuration Mode


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

2. Check Force the KM to run in Classic mode and click OK.

NetBackup KM will now start running in Classic Mode, enabling you to use the KM Configurationmenus.

To conf igure the KM in TrueSight OM, follow the above procedure and uncheck Force the KM to run inClassic mode. All conf igurations made through the PATROL Console will then be ignored.

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 server 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 server instance and select:

Refresh Process Cache to refresh the PATROL Agent process cache

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

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

Forcing Selected Data Collectors

This option is only available from a PATROL Developer Console.


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

1. Right-click the server instance and select Refresh Process Cache to refresh the PATROL Agentprocess cache .

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

With the PATROL Console for MS Windows

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

Select the required data collector.

Click Update.

With the PATROL Console for Unix

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


Click Options > Update.

With the PATROL Central Operator Console

Right-click on the server instance and choose Properties

Click on the Parameter List tab


Click Update.

Forcing Full Data Collection for Jobs

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

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

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

Reloading CommandsAll new commands are reloaded automatically but some situations may require a manualcommands reload. To do so, in the Console, right-click the server instance > KM Commands >Reload Commands.


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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 server instance > KM Commands > Configuration > Debug. TheNetBackup KM Debug Configuration dialog is displayed:

Enabling the Debug Mode


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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

Media Server NBU_MEDIASERVER_CONTAINERNBU_MEDIASERVER

NBUMediaServerCollector

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/Linux systems; %PATROL_HOME%\lib\NBU\debug on Microsoft Windows systems). The debug folder must have at least 10MB ofavailable disk space and read, write and execute permissions for both PATROL Agent userand the NetBackup 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.


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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 for <node-id> 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_<node-id>_<date>_<time>.tar.Z file (UNIX/Linux systems). This file couldlater be found in $PATROL_HOME/lib/NBU/

nbu_km_debug_<node-id>_<date>_<time>.zip file (Windows systems). This file could laterbe found in %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/Linux) or %PATROL_HOME%\lib\NBU\ (on MicrosoftWindows).


Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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.

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 > Log Alert 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 of

95 Acknowledging Alerts

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Warning.

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

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

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

Databases > Reports > Database Backup Information - reports information about the last catalogdatabase 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 volumepools.

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

97

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Introduction

This chapter provides statistical information about resources, operating status, and performancesmanaged by Veritas NetBackup KM for PATROL. It contains tables describing the parameters usedin the KM, grouped by Application Classes, and provides a brief description of each parameterand its default settings.

98

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_CLIENT_CONTAINERIcon

Parameters

Name Description Units Default AlertConditions

Type

NBUClientCollectorExecTime

This is a standard parameter whichmonitors the collector execution time.

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

%PSL pconfig("REPLACE", "/Runtime/NBU/<node-id>/NBUClientCollectorExecTime", 0);

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

99 NBU_CLIENT_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

InfoBox

Name Description

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

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

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

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:

100NBU_CLIENT_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_CLIENTIcon

Parameters


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. Monitorsthe status of the client. This statusis determined by the client statusmapping rule defined in the KMcommand Configuration > Client(s)Status. If this status parameterchanges to warning or alarm state,the recovery action will trigger anevent and annotate the last datapoint.

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

101 NBU_CLIENT

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

InfoBox

Name Description

Name Name of the Veritas NetBackup client.

Description Description of the Veritas NetBackup client.

Hardware Hardware platform of the client.

Operating System Operating system of the client.

Status Status of client connectivity from the current node.

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

Version Version number of the application installed on the client.

Installation Path Installation path of the application on the client.






Menu Commands


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.

102NBU_CLIENT

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_DAEMON_CONTAINERIcon

Parameters


Type

NBUDaemonCollectorExecTime



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

Seconds Warning> presetvalue orobservedmaximum(default)

CollectionStatus

NBUDaemonDetails Set by NBUDaemonCollector.Displays all data returned to thestandard out from commandsexecuted by the data collector.

n/a n/a n/a

103 NBU_DAEMON_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

InfoBox

Name Description






Menu Commands


Reports > Daemon List Lists all running Veritas 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:

104NBU_DAEMON

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_DAEMONIcon

Parameters


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

105 NBU_DAEMON

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


Type

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.Default mapping rule is:

Nonexistent/Not Responding > Failure

Not Running > Failure

Terminated, Stopped, Disabled >Suspicious

Growing, Unknown > Suspicious

All other states > OK

If this status parameter changes towarning or alarm state, therecovery action will trigger an eventand annotate the last data point.



Availability

NBUDaemonSummary Set by NBUDaemonCollector.Summarizes the daemoninformation as reported bycommands executed by the datacollector.

n/a n/a n/a

106NBU_DAEMON

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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 instance inTrueSight OM.

InfoBox

Name Description

Name Name of the Veritas NetBackup daemon.

Description Description of the Veritas NetBackup daemon.

PID Process ID of the daemon.

PPID Parent process ID of the daemon.

Owner Owner of the daemon.

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

Command Command that started the daemon.






Menu Commands


Configuration > Daemon 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.

107 NBU_DAEMON

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_DATABASE_CONTAINERIcon

Parameters


Type

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



%PSL pconfig("REPLACE", "/Runtime/NBU/<node-id>/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 an eventand annotate the last data point.



availability



108NBU_DATABASE_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

InfoBox

Name Description

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

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

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






109 NBU_DATABASE_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Menu Commands


Reports > DatabaseBackup Information

Reports information about the last catalog database backup.

Configuration > Databases

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 Veritas NetBackup installation directory (for example /usr/openv onHP-UX).

110NBU_DATABASE_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_DATABASEIcon

Parameters


Type

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 parameter changesto warning or alarm state, therecovery 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


111 NBU_DATABASE

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


InfoBox

Name Description

Name Name of the Veritas NetBackup catalog database.

Description Description of the Veritas NetBackup catalog database.

Path Full file path of the catalog database.

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






Menu Commands


Configuration > Database

Sets the database instance to be enabled or disabled for monitoring by the NBUKM.

112NBU_DATABASE

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_DEVICE_CONTAINERIcon

Parameters


Type

NBUDriveCollectorExecTime



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

seconds Warning > presetvalue orobservedmaximum(default)

CollectionStatus

NBUDriveDetails Set by NBUDriveCollector. Displaysall data returned to the standardout from commands executed by thedata collector.

n/a n/a n/a

113 NBU_DEVICE_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

InfoBox

Name Description






Menu Commands


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:

114NBU_DEVICE_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_DEVICEIcon

Parameters


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.



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



115 NBU_DEVICE

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

InfoBox

Name Description

Name Name of the standalone drive.

Description Description of the drive.

Path Device path of the drive.

Type Media type used in the drive.

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

Serial Number Serial number of the drive.

Drive Index Unique index assigned to the drive.

Control Control mode for the drive.

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

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

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

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






116NBU_DEVICE

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Menu Commands


Administration > OnlineDrive

Allows the selected drive to be brought online.

Administration > OfflineDrive

Allows the selected drive to be brought offline.

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:

117 NBU_DEVICE

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_DPOOLIcon

Parameters


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

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.




Availability

NBUDPoolVolumeCount*

Set by NBUStorageCollector.Displays the number of volumes inthe disk pool.

count None Statistics


118NBU_DPOOL

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

InfoBox

Name Description

Name Name of the disk pool.

Description Description of the disk pool.

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

Storage Server Type Type of the storage server.

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

Raw Size Raw disk size of the disk pool.

Usable Size Usable disk size of the disk pool.

High Watermark High watermark for the volumes in disk pool.

Low Watermark Low watermark for the volumes in disk pool.






119 NBU_DPOOL

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Menu Commands


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/Down Status

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.

120NBU_DPOOL

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_DVOLUMEIcon

Parameters


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

NBUDVolumeSpaceUsed*

Set by NBUStorageCollector. Displays thedisk space occupied by the backup datain this disk volume.

Gigabytes(GB)

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.


None Availability

121 NBU_DVOLUME

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


Type

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.



Availability

NBUDVolumeWriteStreamCount*

Set by NBUStorageCollector. Displays thenumber of current write steams for thedisk volume




InfoBox

Name Description

Name Name of the disk volume.

Description Description of the disk volume.

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

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

Disk Type Type of the disk.

Disk Media ID Media ID of the disk.

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

Total Capacity Total disk capacity of the disk volume.

Free Space Free disk space in the volume.

Used Percent Percentage of used disk space.

Number of ReadMounts

Number of read mounts of the disk volume.

Number of WriteMounts

Number of write mounts of the disk volume.

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

Collector LastStart

Date & time when the last data collection cycle started.


122NBU_DVOLUME

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Name Description

Collector NextStart

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


Menu Commands


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.

123 NBU_DVOLUME

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_JOB_CONTAINERIcon

Parameters


Type

NBUJobActiveBackupCount*

Set by NBUJobCollector. Displaysthe number of active backup jobscurrently discovered andmonitored.


NBUJobActiveBackupReduction*

Set by NBUJobCollector. Displaysthe reduction in number of activebackup jobs since the lastcollection cycle.


NBUJobActiveCount* Set by NBUJobCollector. Displaysthe number of active jobs currentlydiscovered and monitored.


NBUJobActiveNonBackupCount*

Set by NBUJobCollector. Displaysthe number of active non-backupjobs currently discovered andmonitored.


NBUJobCollectorExecTime

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

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

Seconds Warning > presetvalue orobservedmaximum(default)

CollectionStatus

NBUJobDetails Set by NBUJobCollector. Displaysall data returned to the standardout from commands executed by thedata collector.

n/a n/a n/a

NBUJobQueuedBackupCount*

Set by NBUJobCollector. Displaysthe number of backup jobs in"Queued" state.Units: count


124NBU_JOB_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


Type

NBUJobQueuedBackupReduction *

Set by NBUJobCollector. Displaysthe reduction in number of queuedbackup jobs since the lastcollection cycle.




InfoBox

Name Description






Menu Commands


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:

125 NBU_JOB_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


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:

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 job alerts(warnings or alarms) when it detects new errors.

126NBU_JOB

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_JOBIcon

Parameters

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


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.


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

127 NBU_JOB

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


Type

NBUJobStatus Set by NBUJobCollector. Monitorsthe status of the job. This status isdetermined by the job statusmapping rule defined in the KMcommand Configuration>JobsStatus.




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.


None Statistics



InfoBox

Name Description

Job ID Identifier assigned to the job by Veritas NetBackup.

Type Type of the job.

Schedule Name of the schedule used by the job.

Schedule Type Type of the schedule used by the job.

Subtype Subtype of the schedule used by the job.

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

Completion Status Completion status of the job.

Exit Status Exit status code of the job.

Policy Name Name of the policy used by the job.

Policy Type Type of the policy used by the job.

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

128NBU_JOB

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Name Description

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

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

Schedule Start Schedule start time.

Schedule End Schedule end time.

Start Date & time when the job was initiated.

End Date & time when the job completed.

Duration Duration of the job.

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

Files Number of files that have been written for 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.

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

Attempt Number of attempts of the job.

Operation Last operation performed by the job.

Job PID Process ID of the job.

Priority Priority of the job.

Owner Owner of the job.

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

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

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

Last Backup Duration Duration of the last similar successful backup.

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

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






Menu Commands


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

129 NBU_JOB

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_LDEVICEIcon

Parameters


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.




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 last backupactivity.


None Statistics


130NBU_LDEVICE

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


InfoBox

Name Description

Name Name of the robotic drive.

Description Description of the drive.

Path Device path of the drive.

Type Media type used in the drive.

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

Serial Number Serial number of the drive.

Drive Index Unique index assigned to the drive.

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.

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

Control Control mode for the drive.

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

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

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

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






131 NBU_LDEVICE

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Menu Commands


Administration > OnlineDrive

Allows the selected robotic drive to be brought online.

Administration > OfflineDrive

Allows the selected robotic drive to be taken offline.

Configuration > RoboticDrive

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

Configuration > RoboticDrive Status

Accesses the individual configuration for determining the drive status for 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.)

132NBU_LDEVICE

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_LIBRARY_CONTAINERIcon

Parameters


Type

NBULibraryCollectorExecTime



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


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






133 NBU_LIBRARY_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Menu Commands


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:

134NBU_LIBRARY_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_LIBRARYIcon

Parameters


Type

NBULibraryMediaAssignedCount

Set by NBULibraryCollector.Displays the number of assignedmedia loaded in this roboticlibrary. (Assigned media are tapemedia assigned to a non-scratchvolume pool.)


NBULibraryMediaAvailableCount

Set by NBULibraryCollector.Displays the number of mediaavailable to use in this roboticlibrary. This includes unassignedand scratch media.


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.


count Warning: 2or lessAlarm: 0

Statistics

NBULibraryMediaCount

Set by NBULibraryCollector.Displays the total number of medialoaded in this robotic library.


135 NBU_LIBRARY

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


Type

NBULibraryMediaScratchCount

Set by NBULibraryCollector.Displays the number of scratchmedia loaded in this roboticlibrary. (Scratch media are tapemedia assigned to the scratchvolume pool.)


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


NBULibraryMediaUnassignedPercent*

Set by NBULibraryCollector.Monitors the percentage ofunassigned media against the totalnumber of media loaded in thisrobotic library.


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.




Availability

136NBU_LIBRARY

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


Type

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.


None Statistics

NBULibraryUpDriveCount

Set by NBULibraryCollector.Displays the number up / onlinestate drives in this robotic library.





InfoBox

Name Description

Name Name of the robotic library.

Description Description of the robotic library.

Path Path of the robotic library.

Robot Number Unique number assigned to the robotic library.

Type Media type of the robotic library.

Device Host Name of the remote host where the robotic library is connected.

Robot Control Host Name of the host that provides the robotic control for a robot.

Serial Number Serial number of the robotic library.

Status Status of the robotic library.






137 NBU_LIBRARY

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Menu Commands


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 by theNBU 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.

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.

138NBU_LIBRARY

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_LOG_CONTAINERIcon

Parameters


Type

NBULogCollectorExecTime



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


CollectionStatus

NBULogDetails Set by NBUDatabaseCollector.Summarizes the databaseinformation as reported bycommands executed by the datacollector.

n/a n/a n/a

InfoBox

Name Description






Menu Commands

139 NBU_LOG_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


Reports > Messages List Reports all Veritas 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 Veritas NetBackup installation directory (for example /usr/openvon HP-UX), unless the path is fully qualified as for the system log on Solaris andHP-UX.

Configuration > LogsFilter

Accesses the global configuration of the filter for expressions used for detectingerror 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.

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.

140NBU_LOG

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_LOGIcon

Parameters


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, depending onthe configuration in the KMcommand Configuration > Log(s)Alert Acknowledgement. Manualacknowledgement is availableunder the KM sub-menuAcknowledgement.

n/a None n/a

NBULogFSSpaceUsedPercent*

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


Percentage(%)

Warning:between 95and 98Alarm : 98 and over

Statistics

141 NBU_LOG

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


Type

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.

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

count Warning:more thanor equal to1

Statistics

142NBU_LOG

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


Type

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, depending onthe configuration set through theKM command Configuration>Log(s)Alert Acknowledgement. Manualacknowledgement is availableunder the KM sub-menuAcknowledgement.

n/a None n/a



InfoBox

Name Description

Name Name of the Veritas NetBackup log file.

Description Description of the Veritas NetBackup log file.

Path Full file path of the log file.

Log File ModificationTime

Date & time when the log file was last modified.

Log File Size File size of the log file.

Total FS Space Total space used by the file system.

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

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

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






143 NBU_LOG

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Menu Commands


Acknowledgement > Warnings

Allows acknowledgement of warning messages detected on the selected log fileinstance.This dialog allows selective acknowledgement of "suspicious" error messagesdetected in the log file and sent to the text parameter 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 the selectedlog 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.

144NBU_LOG

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_MAINIcon

Parameters

No parameters.

InfoBox

No parameters.

Menu Commands


Configuration > NetBackup Nodes

Allows to monitor several NetBackup master and media servers, and NetBackupappliances with one PATROL agent

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 Veritas NetBackup applicationwithout any PATROL Console connection.

Configuration > ForceClassic ConfigurationMode

Forces the KM to "Classic Mode" and allows to configure NetBackup KM fromPATROL Consoles.

Configuration > About Shows the version and general information about PRODUCT SHORT NAME%>

145 NBU_MAIN

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_MEDIASERVER_CONTAINERIcon

Parameters


Type

NBUMediaServerCollectorExecTime



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


CollectionStatus

NBUMediaServerDetails Set by NBUMediaServerCollector.Displays all data returned to thestandard out from commandsexecuted by the data collector.

n/a n/a n/a

InfoBox

Name Description






Menu Commands


Configuration > MediaServers

Accesses the dialog for specifying which media servers are to be monitored bythe NetBackup KM. By default, all media servers are monitored.

146NBU_MEDIASERVER_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Configuration > MediaServers Status

Accesses the configuration for determining the status for all monitoredinstances.By default, the following NBUMediaServerState to NBUMediaServerStatusmapping rule is used:

147 NBU_MEDIASERVER_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_MEDIASERVERIcon

Parameters


Type

NBUMediaServerState Set by NBUMediaServerCollector.Displays the state of the mediaserver as reported in the commandexecuted by the data collector.

4 = NotReachableBy Master;8 = NotActive ForTape OrDisk Jobs ; 12 = ActiveFor DiskJobs; 13 =AdministrativePause ; 14 = ActiveFor TapeAnd DiskJobs ; -1 =Unknown

None Availability

NBUMediaServerStatus Set by NBUMediaServerCollector.Monitors the status of the mediaserver. This status is determined bythe media server mapping ruledefined through the KM command Configuration > Media Server(s)Status. If this status parameterchanges to warning or alarm state,the recovery action will trigger anevent and annotate the last datapoint.



Availability

NBUMediaServerSummary

This text parameter displays thesummary of processed datacollected from the command.

n/a n/a n/a

InfoBox

148NBU_MEDIASERVER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Name Description

Name Name of the media server.

Type Type of server. Possible values are Master or Media.

Status Status of the media server.






149 NBU_MEDIASERVER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Menu Commands


Configuration > MediaServer

Accesses the dialog for specifying which media servers are to be monitored bythe NetBackup KM. By default, all media servers are monitored.

Configuration > MediaServers Status

Accesses the configuration for determining the status for all monitoredinstances. By default, the following NBUMediaServerState toNBUMediaServerStatus mapping rule is used:

150NBU_MEDIASERVER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_MOUNT_CONTAINERIcon

Parameters


Type

NBURequestCollectorExecTime



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


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

Name Description






Menu Commands

151 NBU_MOUNT_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


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 Veritas NetBackup command.

Configuration > MountRequests

Accesses the dialog for specifying which mount requests are to be monitored bythe 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 Veritas NetBackup for the date/time of a mountrequest is set to "MO/DD/YY HH:MM:SS". The date/time is then converted by theNBU KM using the system time zone on the PATROL Agent (system time zone isindicated by an empty field).

152NBU_MOUNT_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_MOUNTIcon

Parameters

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


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.




Availability

NBURequestSummary Set by NBURequestCollector.Summarizes the pending requestinformation as reported bycommands executed by the datacollector.

n/a n/a n/a



153 NBU_MOUNT

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

InfoBox

Name Description

Request ID Full name assigned for the pending request.

Description Description of the pending request.

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

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

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

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

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

Density Density of the requested media.

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

Barcode Barcode of the requested media.

Volume Group Volume group of the requested media.

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

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.

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.






Menu Commands


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

Administration > Deny Denies the selected pending request.

Administration > Resubmit

Resubmits the selected pending request.

154NBU_MOUNT

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_PCLIENTIcon

Parameters


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.


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.


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.


NBUPClientIncrBackupFileCount

Set by NBUPolicyCollector. Displaysthe number of files backed up in thelast successful incremental backupfor this policy client.


155 NBU_PCLIENT

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


Type

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



InfoBox

Name Description

Name Host name of the Veritas NetBackup policy client.

Description Description of the Veritas NetBackup policy client.

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

Hardware Hardware platform of the policy client.

Operating System Operating system of the policy client.

Priority Priority of the policy client.

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

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

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

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

Last Full Backup Start Date & time when the last successful full backup started 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 Incr Backup Start Date & time when the last successful incremental backup started for the policyclient.

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.



156NBU_PCLIENT

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Name Description




Menu Commands


Configuration > PolicyClient

Sets the policy client instance to be enabled or disabled for monitoring by theNBU KM.

157 NBU_PCLIENT

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_POLICY_CONTAINERIcon

Parameters


Type

NBUPolicyCollectorExecTime



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


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






158NBU_POLICY_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Menu Commands


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

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

159 NBU_POLICY_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_POLICYIcon

Parameters


Type

NBUPolicyBackupElapsed*

Set by NBUPolicyCollector. Displaysthe elapsed time since the lastbackup for this policy, regardlessof completion status of the backup.This last backup is determined fromthe monitored jobs as configured inthe 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.


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.


160NBU_POLICY

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


Type


NBUPolicyFullBackupFileCount

Set by NBUPolicyCollector. Displaysthe number of files backed up in thelast successful full backup for thispolicy.


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.


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.



NBUPolicyIncrBackupFileCount

Set by NBUPolicyCollector. Displaysthe number of files backed up in thelast successful incremental backupfor this policy.


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 = NotStarted

None Availability

161 NBU_POLICY

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


Type

4 =Inactive-1 =Unknown

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.




Availability

NBUPolicySuccBackupElapsed*

Set by NBUPolicyCollector. Displaysthe elapsed time since the lastsuccessful backup for this policy.This last backup is determined fromthe monitored jobs as configured inthe KM command Configuration>Jobs from the Jobsicon.



NBUPolicySummary Set by NBUPolicyCollector.Summarizes the policy informationas reported by commands executedby the data collector.

n/a None n/a



InfoBox

Name Description

Name Name of the Veritas NetBackup policy.

Description Description of the Veritas NetBackup policy.

Type Type of the policy.

Active Status of the policy (yes or no).

162NBU_POLICY

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Name Description

Priority Priority of the policy.

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

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

Residence Label of the storage unit used by the policy.

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

Volume Pool Volume pool of the policy.

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

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

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

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

Last Full Backup Start Date & time when the last successful full backup started 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 Incr Backup Start Date & time when the last successful incremental 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.

Next Backup Date & time of the next scheduled backup.

Next Backup ScheduleName

Name of the next backup schedule.



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



163 NBU_POLICY

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Menu Commands


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 policy statusmapping rule configured at the global/container level.

Configuration > PolicyClients

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

164NBU_POLICY

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_POOL_CONTAINERIcon

Parameters


Type

NBUPoolCollectorExecTime



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


CollectionStatus

NBUPoolDetails Set by NBUPoolCollector. Displaysall data returned to the standardout from commands executed bythe data collector.

n/a n/a n/a

165 NBU_POOL_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

InfoBox

Name Description






Menu Commands


Reports > AvailableMedia

Reports all available media across all volume pools.

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 Veritas NetBackup application).

166NBU_POOL_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_POOLIcon

Parameters

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


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.


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.


NBUMediaFrozenCount

Set by NBUPoolCollector. Displaysthe number of frozen media in thisvolume pool. Frozen is a possiblestatus for a tape media.


NBUMediaFullCount Set by NBUPoolCollector. Displaysthe number of full media in thisvolume pool. Full is a possiblestatus for a tape media.


NBUMediaFullPercent*

Set by NBUPoolCollector. Monitorsthe percentage of full media againstthe total number of media in thisvolume pool.

Percentage(%)


Statistics

167 NBU_POOL

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


Type


NBUMediaLoadedCount

Set by NBUPoolCollector. Displaysthe number of media in this volumepool, currently loaded to a roboticlibrary.


NBUMediaLoadedEmptyCount

Set by NBUPoolCollector. Displaysthe number of empty media in thisvolume pool, currently loaded to arobotic library.


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.


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.


NBUMediaUnassignedCount

Set by NBUPoolCollector. Displaysthe number of media in unassignedstate in this volume pool.


NBUMediaUnassignedPercent*

Set by NBUPoolCollector. Monitorsthe percentage of unassigned mediaagainst the total number of mediain 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.


168NBU_POOL

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


Type

NBUPoolSpaceAvailable*

Set by NBUPoolCollector. Monitorsthe available media space for thebackup data to use amongst theassigned media in this volumepool.


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(%)


Statistics

NBUPoolSummary Set by NBUPoolCollector.Summarizes the volume poolinformation as reported bycommands executed by the datacollector.

n/a n/a n/a



169 NBU_POOL

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

InfoBox

Name Description

Name Name of the volume pool.

Description Description of the pool.

Host Name Name of the host that will be permitted to request and use volumes in this pool.

User User ID of the person or application who is permitted to use volumes in thispool.

Group Name of the operating system user group allowed to use volumes in this pool.






Menu Commands


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.

170NBU_POOL

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_SERVERIcon

Parameters


Type

ExtraFilesList Pushes the NetBackup KM libraryfiles to the PATROL Agent during the"Commit" operation.

n/a None n/a

NBUClientCollector Collects Veritas NetBackup clientrelated information. It sets allconsumer parameters in the NBU_CLIENT_CONTAINER andNBU_CLIENT application classes. Bydefault, this collector is executedonly 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.


n/a None n/a

NBUDaemonCollector Collects Veritas NetBackup daemonrelated information. It sets allconsumer parameters in the NBU_DAEMON_CONTAINER andNBU_DAEMON application classes.


n/a None n/a

NBUDatabaseCollector Collects Veritas NetBackup catalogdatabase related information. Itsets all consumer parameters inthe NBU_DATABASE_CONTAINERand NBU_DATABASE applicationclasses. By default, this collector isexecuted only on the master server.


n/a None n/a

171 NBU_SERVER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


Type

NBUDriveCollector Collects Veritas NetBackupstandalone drive relatedinformation. It sets all consumerparameters in the NBU_DEVICE_CONTAINER andNBU_DEVICE application classes.


n/a None n/a

NBUJobCollector Collects Veritas NetBackup backup/restore activity related information.It sets all consumer parameters inthe NBU_JOB_CONTAINER andNBU_JOB application classes. Bydefault, this collector is executedonly on the master server.


n/a None n/a

NBULibraryCollector Collects Veritas NetBackup roboticlibrary and robotic drive relatedinformation. It sets all consumerparameters in the NBU_LIBRARY_CONTAINER,NBU_LIBRARY, and NBU_LDEVICEapplication classes.


n/a None n/a

NBULogCollector Collects Veritas NetBackup log filerelated information. It sets allconsumer parameters in the NBU_LOG_CONTAINER andNBU_LOG application classes.


n/a None n/a

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.




CollectionStatus

172NBU_SERVER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


Type

NBUMediaServerCollector

Collects information about mediaservers. It sets all consumerparameters for all possible mediaservers in the NBU_MEDIASERVER_CONTAINER andNBU_MEDIASERVER applicationclasses, including master serversas instances of NBU_MEDIASERVER.By default, this collector isexecuted only on the master server.


n/a None n/a

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 theVeritas NetBackup application onthis managed system. It is set bythe NBU_SERVER application classdiscovery.If the node is unreachable or if anyof the Veritas NetBackupapplication daemons is notrunning, this parameter will be setto Failure state. The list of criticalVeritas NetBackup daemons can becustomized using the KM command Configuration>Node Status from theVeritas NetBackup icon. If there areany suspicious commands due toan error from the master/mediaserver, this parameter will be set toSuspicious state.




Availability

173 NBU_SERVER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


Type

NBUPolicyCollector Collects Veritas NetBackup policyand 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.


n/a n/a n/a

NBUPoolCollector Collects Veritas NetBackup volumepool related information. It sets allconsumer parameters in NBU_POOL_CONTAINER andNBU_POOL application classes.By default, this collector isexecuted only on the master server.


n/a n/a n/a

NBURequestCollector Collects Veritas NetBackup pendingrequest related information. It setsall consumer parameters in the NBU_MOUNT_CONTAINER andNBU_MOUNT application classes.By default, this collector isexecuted only on the master server.


n/a n/a n/a

NBUStorageCollector Collects Veritas NetBackup storagepool related information. It sets allconsumer parameters in the 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

174NBU_SERVER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


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.

Master Server(s) Names of the discovered Master Servers.

Media Server(s) Names of the discovered Media Servers.

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

Node Type Type of node (Master Server or Media Server).

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

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

Operating System Operating system description as reported by PATROL Agent.

Installation Path Veritas NetBackup software installation path.

Binary Path Veritas NetBackup software binary paths used by NBU KM.

Library Path Veritas NetBackup software library paths used by NBU KM.

Monitoring Mode Monitoring mode of the Knowledge Module.

Monitoring Node Node currently monitoring Veritas NetBackup.

Menu Commands


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

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.

175 NBU_SERVER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


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 Veritas 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 > Monitoring Mode

Accesses the Failover Mode Configuration dialog, which is used for enabling ordisabling KM failover, when monitoring clustered Veritas 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 Veritas 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 this menu

Binary Paths are the application and operating system binary path, which is used forsetting PATH environment variable. The KM discovers and set this automatically. Thismenu can be used, if the discovered paths are incorrect.

Library Paths are the application and operating system library path, which is used forsetting the following environment variables:

LD_LIBRARY_PATH (on Solaris)

SHLIB_PATH (on HP-UX)

LIBPATH (on AIX)

The KM discovers and set this automatically. This menu can be used, if the discovered pathsare incorrect.

Log Directory Path is the application log path discovered by the KM, where NetBackupmaintains the daily messages logs.

Remote Temp Directory Path (remote nodes only) is used for creating KM temporary fileson the remote node.

Configuration > NodeType

Accesses the Node Type dialog, which displays and sets the type of the VeritasNetBackup 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.

Configuration > NodeStatus

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

176NBU_SERVER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


The NBU KM checks for the existence of these daemons to determine the statusof the node (parameter NBUNodeStatus). By default, the following daemons aresought:

Configuration > InstanceLimits

Accesses the Instance Limits Configuration dialog to view and modify themaximum number of NBU KM application instances allowed for eachapplication class.

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

177 NBU_SERVER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_STORAGE_CONTAINERIcon

Parameters


Type

NBUStorageCollectorExecTime



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


CollectionStatus

NBUStorageDetails Set by NBUStorageCollector.Displays all data returned to thestandard out from commandsexecuted by the data collector.

n/a n/a n/a



InfoBox

Name Description






178NBU_STORAGE_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Menu Commands


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:


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.


Accesses the global configuration for determining the up/down status formonitored disk volume instances.

By default, the following NBUDVolumeUpDownState toNBUDVolumeUpDownStatus mapping rule is used:

179 NBU_STORAGE_CONTAINER

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_STORAGEIcon

Parameters

Storage monitoring is disabled in passive multi-node mode


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.


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.




Availability

InfoBox

Name Description

Storage Server Name of the host where the storage is attached to.

Storage Server Type Type of the storage server.

Description Description of the storage.

Storage Type Type of storage.

Up/Down State Up/down status of the storage.

180NBU_STORAGE

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Name Description






Menu Commands


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.


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.


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.

181 NBU_STORAGE

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Managing Baselines and KeyPerformance IndicatorsTo detect abnormalities on the monitored environment, BMC TrueSight Operations Managementcalculates baselines per attribute based on values collected over a specified period of time todetermine a normal operating range. When the collected values for these parameters are out ofrange, an alert is triggered. Some attributes are identified by default as Key PerformanceIndicators (identified with the icon) and automatically included in the base lining calculation.

Managing baselines

The baseline is the expected normal operating range for an attribute of a monitor. There are twobaselines: Baseline High and Baseline Low. Baseline High represents the point at which 95% ofthe weighted average of the historical values fall below this value for the selected time period; Baseline Low represents the point at which 90% of the weighted average of historical values forthe selected time period fall above this line.

Baselines are generated for KPI attributes that have an active abnormality thresholds.

Managing Key Performance Indicators

Starting from v9.5 of BPPM, attributes that have not been initially designated in the KM as KeyPerformance Indicators (KPIs) cannot be flagged as KPIs from BPPM/TrueSight. Although enablingbaseline is possible through the Options > Administration > Intelligent Event Thresholds featureavailable in the Infrastructure Management Server operator console, BMC does not recommenddoing it.

For more information, refer to the BMC TrueSight Operations Management documentation available f romdocs.bmc.com.

https://docs.bmc.com/docs/dashboard.action

Additional Information

183 Troubleshooting

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

TroubleshootingThe table below will help you diagnose any problem you may encounter when installing orrunning Veritas 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 Veritas 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/knowledge folder.

Veritas NetBackup KM for PATROL files have not been installed correctly under the PATROL installationdirectory on the PATROL Console.

VeritasNetBackupicon does notappear after loading

Check that the KM is loaded using NBU_LOAD.kml and that NBU_MAIN is loaded.

Check that there is no KM version mismatch between the PATROL Console and the PATROL Agent.Check the messages in the PATROL Console SOW to verify this.

Check whether the PATROL Agent tuning variable,/AgentSetup/AgentTuning/pslInstructionMax hasbeen increased as suggested in section Changes to BMC PATROL. Check the messages in the PATROLConsole SOW.

Check whether the PATROL Agent user has necessary privileges added in the Agent’s Access ControlList (/AgentSetup/accessControlList) in order to read and write to the Agent Configuration Database.

Parameter NBULoginStatus is in suspicious (warning)status

This parameter will show a “suspicious” state if any command executed by NetBackup KM fails.

Check the annotation point on the first state change data point of this parameter to look for any failingcommands. If an annotation point cannot be found, or if it is not up-to-date, check the KM StatusReport, which can be viewed by selecting the menu KM Status from the server icon. These errors areproduced from the Veritas NetBackup commands executed by the NetBackup KM.

Check that the operating system user configured in the menu Configuration>Login can execute allNetBackup 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 PATROL Agent,possibly after an improper upgrade of the KM. Check the messages in the PATROL Console SOW toverify this.

Check that the NetBackup KM login details are still valid. Has the password changed on the system?Look for any error messages on the SOW, and check for additional information in the last annotationpoint for parameter NBULoginStatus.

All/some KM application instances donot appear

Check that the KM instance limits have not been exceeded. Look for any error messages on the SOW,and increase the instance limits for affected objects using the menu Configuration>Instance Limits.

Check whether the server icon is in offline state. None of the data collectors will be executed until theserver is enable and online.

If the KM is configured for multi-node mode monitoring, some components are not monitored on thepassive cluster node.

184Troubleshooting

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


Behavior ofthe 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 is notcomplete. Make sure both the PATROL Console and the PATROL Agent are uninstalled and installedcorrectly 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 in the KM. Theseintervals are defined for a standard environment with minimal resource impact. These intervals can becustomized from the PATROL Developer Console or PCM to suit your environment. Refer to the PATROL

Console User Guide for more details.

Poorperformance of the Veritas NetBackup master/mediaserver after installingthe KM

This happens if the NetBackup KM is installed on a heavily used system. Depending on the complexity ofyour Symantec NetBackup environment, the NetBackup KM may consume more resources to interrogatethe application and process the data. In such a complex environment, the NetBackup KM may requiresome fine tuning to optimize the available resources. Consider the following options:

Disable monitoring of unnecessary application instances. This can be achieved by using theappropriate Configuration Menu. Refer to the section Filtering Elements to Monitor.

Increase the scheduling interval (polling cycle) for data collectors.

Deactivate monitoring non-critical components by setting the Instance Limits to 0 (Zero).

Deactivate unnecessary data collectors during selected time intervals, where there are no SymantecNetBackup activity. For example, if the job monitoring can be disabled between 9 am and 4 pmeveryday, except weekends, then disable job data collector (NBUJobCollector) during this period,using following PSL through PATROL Console:

%PSL pconfig("REPLACE","/Runtime/NBU/<node-id>/NBUJobCollectorMode",

"0|32400|57600|0|0|||||||||||0|0");

Here the pconfig variable is named as: <collector name>Mode. Replace <node-id> with the appropriatenode ID of the NetBackup server. The value contains following details, delimited by pipe (|):enabled (1)/disabled (0) data collection, default start/end times in number of seconds since midnight, start/endtimes for non-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. Replace <node-id> with the appropriate node ID of theNetBackup server and restart the PATROL Agent:

%PSL pconfig("REPLACE", "/Runtime/NBU/<node-id>/NBU_JOB/

jobCollectText", 0);

As part of collection, the collector compares each job against previous similar backup to calculate theprogress data. In addition the last backup info is shared under NBU_POLICY parameters(NBUPolicy*Backup*) to monitor the success at the policy level. This functionality can also be disabledto speed up the collector, using the PSL below. Replace <node-id> with the appropriate node ID of theNetBackup server and restart the PATROL Agent:

%PSL pconfig("REPLACE", "/Runtime/NBU/<node-id>/NBU_JOB/

jobCollectLastBackupStats", 0);

185 Troubleshooting

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


Defining a "no command execution window" for all collectors will pause running commands at peaktimes or during NetBackup maintenance windows. This can be set using the PSL below. Replace <node-id> with the appropriate node ID of the NetBackup server and restart the PATROL Agent:

%PSL pconfig("REPLACE", "/Runtime/NBU/<node-id>/noExecuteWindow",

"23:59:00|120");

The value of this permanent configuration variable is in format “<start time in HH:MM:SS 24-hour clock>|<duration in seconds>”. The above “23:59:00|120” sets all collectors to sleep between 23:59:00 and00:01:00 (2 minutes) every day before executing commands. Also this noExecutewindow supportsmultiple time windows:

%PSL pconfig("REPLACE", "/Runtime/NBU/<node-id>/noExecuteWindow",

["23:59:00|120","11:59:00|120"]);

Replace <node-id> with the appropriate node ID.

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> Instance Limits.

Also refer to Infinite Loop Errors for a possible PATROL internal scheduling delay which may impact theperformance of the KM.

Old active jobsare not removedfrom the console

By default, all active jobs are monitored, and they are exempted from ageing. It is possible to change thisbehavior by Including Active Jobs in the menu Configuration>Jobs from Jobs container.

Infinite LoopErrors(Errormessages on 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) tostop running PSL functions in an infinite loop. When a PSL function reaches this maximum threshold, itreports this error, and puts the execution of this function to the back of the process queue. This will notonly delay the data collector, it will also impact the performance of the system.

To resolve this situation, the maximum number of instructions should be increased to an optimum value.This depends on the complexity of your environment. It is required that the default value of 500,000should be increased to at least 5,000,000 on a standard Veritas NetBackup environment to enable theNetBackup KM data collectors to execute without impacting your system.

If this still does not resolve the problem, you can disable this functionality by setting the value of thetuning 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 turnthe debug on by setting appropriate PATROL Agent configuration variable with a timestamp value. Thistimestamp value determines when the debug should be turned off. For example, to turn on the debug for60 minutes from now, run the following PSL through PATROL Console:

%PSL pconfig("REPLACE","/Runtime/NBU/<component>Debug",

time()+3600);

Where <Component> is either server for debugging the server discovery or name of the collectorcomponent in lower case followed by “Collector”, like daemonCollector for debugging daemon collector.

Oldacknowledged jobs are stillkept in the pconfig

By default the KM stores all acknowledged jobs. Use the following PSL through PATROL Console to keeponly the last <Number> of jobs on <node-id):

%PSL pconfig("REPLACE",

"/Runtime/NBU/<node-id>/NBU_JOB/jobAcknowledgementCapacity",

<Number>);

186Troubleshooting

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01


database.Replace <node-id> with the appropriate node ID of the NetBackup server.

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/<node-id>/labelByJobID",

<Format Number>);

Where:

<node-id> is the appropriate node ID of the NetBackup server

<Format Number> is either 1, 2, or 3 as described above. Use the menu Force Full Collection from theJobs container instance to recreate the job instances.

187 Troubleshooting

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

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 ofservers and components monitored by the KM, your CPU and memory usage will increase.

When monitoring a standard local installation of Veritas NetBackup using NetBackup KM, thePATROL Agent will consume between 5MBytes and 10MBytes of additional system memory. Anenterprise installation of Veritas NetBackup Master Server with multiple Media Servers, Clients,Storage Servers and Storage Units can consume more memory (as per other KMs used by thePATROL Agent). The memory usage of NetBackup KM can be reduced by:

• disabling monitoring unnecessary component instances (by using the configuration menu)

• disabling unwanted components (by setting their instance limits to 0)

• disabling unwanted collectors (by using the PATROL Configuration Manager)

• increasing the collector scheduling interval (by using the PATROL Configuration Manager)

• decreasing the instance limits to limit the number of instances created by the collectors

The data collectors in NetBackup KM uses Veritas NetBackup command line interface to obtainVeritas 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 Veritas NetBackup systems.

Network Traffic

When monitoring a NetBackup server through a local PATROL Agent, the NetBackup KMgenerates minimal network traffic. Most of the data is kept on the managed node. The amount ofnetwork traffic that it generates depends on the number of PATROL Consoles that are connectedto the PATROL Agent and the frequency of data collection.

When monitoring remote NetBackup servers, some network traffic will be observed as ittransfers the commands result over the network. The traffic depends on the amount of datapolled during each command execution. When commands are expected to return large output,the KM is designed to use file transfers through SFTP (on UNIX/Linux) and Windows file shares(on Windows).

188

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Index

- A -Abnormalities 181

Access

Executable Files 17

Files 17

Library Files 17

Paths 17

Permissions 17Acknowledge

Alarm 94

Alerts 94

Job Alerts 94

Log Alerts 94

Mount Request 64

Warning 94Acknowledgement

Configure 86

Job 86

Log 86Administer

Veritas NetBackup 62Administration

Robotic Drives 64

Standalone Drives 64Agent

PATROL 53AIX 17

Alarm

Acknowledge 94Alarm Filter State Rules 74

Alert Acknowledgement 86

Configure 86

Job 86

Log 86Alerts

Acknowledge 94Application Class

NBU_CLIENT 100

NBU_CLIENT_CONTAINER 98

NBU_DAEMON 104

NBU_DAEMON_CONTAINER 102

NBU_DATABASE 110

NBU_DATABASE_CONTAINER 107

NBU_DEVICE 114, 129

NBU_DEVICE_CONTAINER 112

NBU_DPOOL 117

NBU_DVOLUME 120

NBU_JOB 126

NBU_JOB_CONTAINER 123

NBU_LIBRARY 134

NBU_LIBRARY_CONTAINER 132

NBU_LOG 140

NBU_LOG_CONTAINER 138

NBU_MAIN 144

NBU_MEDIASERVER 147

NBU_MEDIASERVER_CONTAINER 145

NBU_MOUNT 152

NBU_MOUNT_CONTAINER 150

NBU_PCLIENT 154

NBU_POLICY 159

NBU_POLICY_CONTAINER 157

NBU_POOL 166

NBU_POOL_CONTAINER 164

NBU_SERVER 170

NBU_STORAGE 179

NBU_STORAGE_CONTAINER 177Available Media

Reports 164

- B -Baselines

Generation 181

Manage 181

Requirements 181

TrueSight 181Block

Monitoring 71BMC

BMC Portal 60

BMC Software PATROL Agent 14

BMC Software PATROL Console 14

Requirements 14

TrueSight 14BMC PATROL

Changes 14

pslInstructionMax 14

189

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

- C -CA

Mode 88Changes 8

Check

Instance Limits 56Classic

Mode 88Classic Mode

Force 88Clients

Delete 68

Disable 68

Enable 68

Status Configuration 74Cluster

Configure 66Clustering Application 66

Commands

Reload 90Configuration

About 144

Force Classic Configuration Mode 144

NetBackup Nodes 144

Preloading 144Configure

Alert Acknowledgement 86

Cluster 66

Jobs Exit Status Filter 83

KM User Account 53

Log Error Filter 80

Log Scan Limit 82

Monitoring Period 71

Multi-Node Monitoring Mode 66

NetBackup Nodes 52

Node Status 76

Node Type 66

Nodes 52

Paths 65

PATROL Agent 48

Policy Backup Restriction 85Console Administration 88

Customize

Monitored Mount Requests 78

Mount Request Date/Time Format 78

Mount Request Status 78

Mount Requests 78

- D -Daemons

Delete 68

Disable 68

Enable 68

Status Configuration 74Data Collection for Jobs

Force 89Data Collectors

Force 89Databases

Delete 68

Disable 68

Enable 68Debug

Disable 91

Enable 91

End 91

Files 91

Path 91Delete

Clients 68

Daemons 68

Databases 68

Logs 68

Policies 68

Policy Clients 68

Robotic Drives 68

Robotic Libraries 68

Standalone Drives 68

Storages 68

Volume Pools 68Disable

Clients 68

Daemons 68

Databases 68

Debug 91

Logs 68

Monitoring 52

Policies 68

Policy Clients 68

Robotic Drives 68



Storages 68

190

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Disable

Volume Pools 68Discoveries

Force 89Discovery

Verify 56Disk Space

Requirements 23

- E -Enable

Clients 68

Daemons 68

Databases 68

Debug 91

Logs 68

Monitoring 52

Policies 68

Policy Clients 68

Robotic Drives 68



Storages 68

Volume Pools 68

- F -Failover Group Name 66

Files 27

ins_ALL_<version>.tar 26

ins_WINDOWS_<version>.exe 26

Setup 27

setup.exe 30

setup.sh 30

uninstall.exe 41

uninstall.sh 41Filtering Options

Clients 68

Daemons 68

Databases 68

Logs 68

Policies 68

Policy Clients 68

Robotic Drives 68



Storages 68

Volume Pools 68Force

All Data Collectors 89

All Discoveries 89

Classic Mode 88

Full Data Collection for Jobs 89

Selected Data Collectors 89FQDN 52

- G -Generate

Baselines 181

- H -Hostname 52

HP-UX 17

- I -Improvement 8

InfoBox

Active 159

Application 100

Application Name 170

Application Version 170

Attempt 126

Available FS Space 140

Barcode 152

Binary Path 170

Client 126, 152

Collector Last End 98, 100, 102, 104, 107,110, 112, 114, 117, 120, 123, 126, 129, 132,134, 138, 140, 145, 147, 150, 152, 154, 157,159, 164, 166, 177, 179

Collector Last Start 98, 100, 102, 104, 107,110, 112, 114, 117, 120, 123, 126, 129, 132,134, 138, 140, 145, 147, 150, 152, 154, 157,159, 164, 166, 177, 179

Collector Name 98, 100, 102, 104, 107,110, 112, 114, 117, 120, 123, 126, 129, 132,134, 138, 140, 145, 147, 150, 152, 154, 157,159, 164, 166, 177, 179

Collector Next Start 98, 100, 102, 104, 107,110, 112, 114, 117, 120, 123, 126, 129, 132,134, 138, 140, 145, 147, 150, 152, 154, 157,159, 164, 166, 177, 179

191

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

InfoBox

Collector Status 98, 100, 102, 104, 107,110, 112, 114, 117, 120, 123, 126, 129, 132,134, 138, 140, 145, 147, 150, 152, 154, 157,159, 164, 166, 177, 179

Command 104

Completion Status 126

Control 114, 129

Copyright 144

Density 152

Description 100, 104, 110, 114, 117, 120,129, 140, 152, 154, 159, 166, 179

Device Host 114, 129

Disk Media ID 120

Disk Pool Name 120

Disk Type 120

Drive Index 114, 129

Duration 126

End 126

Exit Status 126

External Media ID 152

Files 126

Free Space 120

FS Percent Used 140

Group 166

Hardware 100, 154

High Watermark 117

Host Name 166, 170

Installation Path 100, 170

Job ID 126, 152

Job PID 126

Job Type 152

Keyword 159

Last Backup 110

Last Backup Duration 126

Last Backup End 126, 154, 159

Last Backup Files 126

Last Backup Job ID 110, 126, 154, 159

Last Backup Mode 110

Last Backup Size 126

Last Backup Start 126, 154, 159

Last Backup Status 154, 159

Last Full Backup End 154, 159

Last Full Backup Job ID 154, 159

Last Full Backup Start 154, 159

Last Incr Backup End 159

Last Incr Backup End Time 154

Last Incr Backup Job ID 154, 159

Last Incr Backup Start 154, 159

Last Purge 110, 140

Library Path 170

Log File Modification Time 140

Log File Size 140

Low Watermark 117

Master Server(s) 170

Max Jobs/Policy 159

Media ID 114, 129

Media Server 126, 152

Media Server(s) 170

Mode 152

Monitoring Mode 170

Monitoring Node 170

Multiple Data Stream 159

Name 100, 104, 110, 114, 117, 120, 129,140, 147, 154, 159, 166

Node Name(s) 170

Node Type 170

Number of Read Mounts 120

Number of Write Mounts 120

Operating System 100, 154, 170

Operation 126

Owner 104, 126

Path 110, 114, 129, 140

PATROL Agent version 144

Percent Completed 126

PID 104

Platform 170

Policy Name 126, 152, 154

Policy Type 126

PPID 104

Priority 126, 154, 159

Product Name 144

Product Release Date 144

Product Version 144

Raw Size 117

Recorded Media ID 152

Request ID 114, 129, 152

Request Time 152

Residence 159

Robot Drive Number 129

Robot Number 129

Robot Type 129

Schedule 126

Schedule End 126

Schedule Start 126

Schedule Type 126

Serial Number 114, 129

Size 126

192

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

InfoBox

Start 126

Status 100, 104, 114, 126, 129, 147, 159

Storage Server 117, 120, 179

Storage Server Type 117, 179

Storage Type 179

Storage Unit 126, 152

Subtype 126

Support 144

Time Remaining 126

Total Capacity 120

Total FS Space 140

Type 114, 126, 129, 147, 159

Up/Down State 117, 120, 179

Usable Size 117

Used Percent 120

User 114, 129, 152, 166

Version 100

Volume Group 152

Volume Pool 159

Website 144Install / Un-install 29, 41

BMC Software Installation Utility 26

Log 30

Packages 27

Procedure 30

Setup Files 27Instance Limits

Check 56Integration

BMC TrueSight Operations Management 60Introduction 29

IP Address 52

Issues

Fixed 8

- J -Job Alerts

Acknowledge 94Jobs

Configure 71


Status Configuration 74Jobs Exit Status Filter

Configure 83

- K -Key Performance Indicators

Manage 181

TrueSight 181KM

Configure 53

Initial Setup 58

Load 47, 48, 60

Preload 48

Preloaded 49, 50

Unload 49, 50

User Account 53KPI

Manage 181

TrueSight 181

- L -Linux 17

Load

KM 47, 48, 60

PATROL Central 48Log Alerts

Acknowledge 94Log Error Filter

Configure 80Log Scan Limit

Configure 82Logs

Delete 68

Disable 68

Enable 68

- M -Maintenance 71

Manage

Baselines 181

KPI 181

TrueSight 181Managed Node

Status Configuration 74Master Server

Configure 66Master/Media Server

193

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Master/Media Server

Start 62

Stop 63Media Server

Configure 66Menu Commands

Acknowledgement 123, 126, 140

Administration 114, 129, 150, 152, 170

Alarms 123, 140

Alert 126

All 123, 140

Assign 152

Assign All 150

Client 100

Client Status 100

Clients 98

Clients Status 98

Configuration 98, 100, 102, 104, 107, 110,112, 114, 117, 120, 123, 134, 138, 140, 145,147, 150, 154, 157, 159, 164, 166, 177, 179

Daemon 104

Daemon List 102

Daemon Status 104

Daemons 102

Daemons Status 102

Database 110

Database Backup Information 107

Databases 107

Debug 170

Deny 152

Deny All 150

Disk Pool 117

Disk Pool Up/Down Status 117

Disk Pools 179

Disk Pools Up/Down Status 177, 179

Disk Volume 120

Disk Volume Up/Down Status 120

Disk Volumes 117

Disk Volumes Up/Down Status 117, 177,179

Drive Cleaning Statistics 112, 132

Force Discovery 170

Force Full Collection 123

Instance Limits 170

Jobs 123

Jobs Alert Acknowledgement 123

Jobs Erroneous Exit Status 123

Jobs Status 123

KM Status 170

Log 140

Log Alert Acknowledgement 140

Log Filter 140

Log Scan Limit 140

Login 170

Logs 138

Logs Alert Acknowledgement 138

Logs Filter 138

Logs Scan Limit 138

Media List 166

Media Server 147

Media Servers 145

Media Servers Status 145, 147

Messages List 138

Monitoring Mode 170

Mount Request Date/Time Format 150

Mount Requests 150

Mount Requests Status 150

Node Status 170

Node Type 170

Offline Drive 114, 129

Online Drive 114, 129

Paths 170

Pending Requests 150

Policies 157

Policies Backup Restriction 157

Policies Status 157

Policy 159

Policy Backup Restriction 159

Policy Client 154

Policy Clients 157, 159

Policy Schedule 159

Policy Status 159

Refresh Parameters 170

Refresh Process Cache 170

Reload Commands 170

Reports 102, 107, 112, 132, 134, 138, 150,159, 166

Resubmit 152

Resubmit All 150

Robotic Drive 129

Robotic Drive Status 129

Robotic Drives 134

Robotic Drives Status 132, 134


Robotic Libraries Status 132

Robotic Library 134

Robotic Library Contents 134

Robotic Library Status 134

194

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Menu Commands

Standalone Drives 112, 114

Standalone Drives Status 112, 114

Start Master Server 170

Start Media Server 170

Stop Master Server 170

Stop Media Server 170

Storage 179

Storage Up/Down Status 179

Storages 177

Storages Up/Down Status 177

Volume Pool 166

Volume Pools 164

Warnings 123, 140Monitored Mount Requests

Customize 78Monitoring

Block 71

Blocked 71

Disable 52

Enable 52

Stop 71

Stopped 71Monitoring Period

Configure 71

Jobs 71

Mount Requests 71Mount Request

Acknowledge 64Mount Request Date/Time Format

Customize 78Mount Request Status

Customize 78Mount Requests

Configure 71

Customize 78


Status Configuration 74Multi-Node Monitoring Mode

Configure 66

- N -NBU_CLIENT

Application Class 100NBU_CLIENT_CONTAINER

Application Class 98NBU_DAEMON

Application Class 104NBU_DAEMON_CONTAINER

Application Class 102NBU_DATABASE

Application Class 110NBU_DATABASE_CONTAINER

Application Class 107NBU_DEVICE

Application Class 114, 129NBU_DEVICE_CONTAINER

Application Class 112NBU_DPOOL

Application Class 117NBU_DVOLUME

Application Class 120NBU_JOB

Application Class 126NBU_JOB_CONTAINER

Application Class 123NBU_LIBRARY

Application Class 134NBU_LIBRARY_CONTAINER

Application Class 132NBU_LOG

Application Class 140NBU_LOG_CONTAINER

Application Class 138NBU_MEDIASERVER

Application Class 147NBU_MEDIASERVER_CONTAINER

Application Class 145NBU_MOUNT

Application Class 152NBU_MOUNT_CONTAINER

Application Class 150NBU_PCLIENT

Application Class 154NBU_POLICY

Application Class 159NBU_POLICY_CONTAINER

Application Class 157NBU_POOL

Application Class 166NBU_POOL_CONTAINER

Application Class 164NBU_SERVER

Application Class 170NBU_STORAGE

Application Class 179

195

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

NBU_STORAGE_CONTAINER

Application Class 177New features 8

Node Status

Configure 76Node Type

Configure 66

Master Server 66

Media Server 66Nodes

Configure 52

FQDN 52

Hostname 52

IP Address 52

- O -Operating Systems

Linux 26, 27, 30, 41

Unix 26, 27, 41

Windows 26, 27, 30, 41Options

Common services 30

Console Systems role 30

Managed System 30

View Log 30Oracle Solaris Cluster 66

Overview 10

- P -Parameter

NBULoginStatus 53Parameters

BURequestCollectorExecTime 150

ExtraFilesList 170

NBUClientCollector 170

NBUClientCollectorExecTime 98

NBUClientDetails 98

NBUClientState 100

NBUClientStatus 100

NBUClientSummary 100

NBUCreateDistribution 170

NBUDaemonCollector 170

NBUDaemonCollectorExecTime 102

NBUDaemonCPUDuration 104

NBUDaemonCPUUtilization 104

NBUDaemonDetails 102

NBUDaemonMemorySize 104

NBUDaemonProcessCount 104

NBUDaemonState 104

NBUDaemonStatus 104

NBUDaemonSummary 104

NBUDatabaseBackupElapsed 107, 110

NBUDatabaseCollector 170

NBUDatabaseCollectorExecTime 107

NBUDatabaseDetails 107

NBUDatabaseFSSpaceUsedPercent 110

NBUDatabaseSpaceAvailable 110

NBUDatabaseSpaceGrowthRate 110

NBUDatabaseSpaceUsed 110

NBUDatabaseSpaceUsedPercent 110

NBUDatabaseStatus 107

NBUDatabaseSummary 110

NBUDPoolSummary 117

NBUDPoolUpDownState 117

NBUDPoolUpDownStatus 117

NBUDPoolVolumeCount 117

NBUDriveCollector 170

NBUDriveCollectorExecTime 112

NBUDriveDetails 112

NBUDriveState 114

NBUDriveStatus 114

NBUDriveSummary 114

NBUDriveThroughput 114

NBUDVolumeReadStreamCount 120

NBUDVolumeSpaceAvailable 120

NBUDVolumeSpaceGrowthRate 120

NBUDVolumeSpaceUsed 120

NBUDVolumeSpaceUsedPercent 120

NBUDVolumeSummary 120

NBUDVolumeUpDownState 120

NBUDVolumeUpDownStatus 120

NBUDVolumeWriteStreamCount 120

NBUFileExcludeList 154

NBUFileIncludeList 154

NBUJobActiveBackupCount 123

NBUJobActiveBackupReduction 123

NBUJobActiveCount 123

NBUJobActiveNonBackupCount 123

NBUJobCollector 170

NBUJobCollectorExecTime 123

NBUJobDetails 123

NBUJobDuration 126

NBUJobFileCount 126

NBUJobQueuedBackupCount 123

NBUJobQueuedBackupReduction 123

196

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Parameters

NBUJobSize 126

NBUJobState 126

NBUJobStatus 126

NBUJobSummary 126

NBUJobText 126

NBUJobThroughput 126

NBULibraryCollector 170

NBULibraryCollectorExecTime 132

NBULibraryDetails 132

NBULibraryMediaAssignedCount 134

NBULibraryMediaAvailableCount 134

NBULibraryMediaAvailablePercent 134

NBULibraryMediaCleaningLeft 134

NBULibraryMediaCount 134

NBULibraryMediaScratchCount 134

NBULibraryMediaScratchPercent 134

NBULibraryMediaUnassignedCount 134

NBULibraryMediaUnassignedPercent 134

NBULibraryState 134

NBULibraryStatus 134

NBULibrarySummary 134

NBULibraryThroughput 134

NBULibraryUpDriveCount 134

NBULogAlarmCount 140

NBULogAlarmText 140

NBULogCollector 170

NBULogCollectorExecTime 138

NBULogDetails 138

NBULogFSSpaceUsedPercent 140

NBULoginStatus 170

NBULogSpaceAvailable 140

NBULogSpaceGrowthRate 140

NBULogSpaceUsed 140

NBULogSpaceUsedPercent 140

NBULogSummary 140

NBULogText 140

NBULogWarningCount 140

NBULogWarningText 140

NBUMediaActiveCount 166

NBUMediaActivePercent 166

NBUMediaCount 166

NBUMediaFrozenCount 166

NBUMediaFullCount 166

NBUMediaFullPercent 166

NBUMediaLoadedCount 166

NBUMediaLoadedEmptyCount 166

NBUMediaLoadedEmptyPercent 166

NBUMediaReadOnlyCount 166

NBUMediaScratchCount 166

NBUMediaServerCollectorExecTime 145

NBUMediaServerDetails 145

NBUMediaServerState 147

NBUMediaServerStatus 147

NBUMediaServerSummary 147

NBUMediaSuspendedCount 166

NBUMediaUnassignedCount 166

NBUMediaUnassignedPercent 166

NBUMediaUnknownCount 166

NBUMediServerCollector 170

NBUMonitoringMode 170

NBUNodeStatus 170

NBUPClientBackupSummary 154

NBUPClientBackupThroughput 154

NBUPClientFullBackupDuration 154

NBUPClientFullBackupFileCount 154

NBUPClientFullBackupSize 154

NBUPClientIncrBackupDuration 154

NBUPClientIncrBackupFileCount 154

NBUPClientIncrBackupSize 154

NBUPClientSummary 154

NBUPolicyBackupElapsed 159

NBUPolicyBackupSummary 159

NBUPolicyBackupThroughput 159

NBUPolicyCollector 170

NBUPolicyCollectorExecTime 157

NBUPolicyDetails 157

NBUPolicyFullBackupDuration 159

NBUPolicyFullBackupElapsed 159

NBUPolicyFullBackupFileCount 159

NBUPolicyFullBackupSize 159

NBUPolicyIncrBackupDuration 159

NBUPolicyIncrBackupElapsed 159

NBUPolicyIncrBackupFileCoun 159

NBUPolicyIncrBackupSize 159

NBUPolicyState 159

NBUPolicyStatus 159

NBUPolicySuccBackupElapsed 159

NBUPolicySummary 159

NBUPoolCollector 170

NBUPoolCollectorExecTime 164

NBUPoolDetails 164

NBUPoolSpaceAvailable 166

NBUPoolSpaceGrowthRate 166

NBUPoolSpaceUsed 166

NBUPoolSpaceUsedPercent 166

NBUPoolSummary 166

NBURDriveState 129

197

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

Parameters

NBURDriveStatus 129

NBURDriveSummary 129

NBURDriveThroughput 129

NBURequestCollector 170

NBURequestDetails 150

NBURequestElapsed 152

NBURequestState 152

NBURequestStatus 152

NBURequestSummary 152

NBUStorageCollector 170

NBUStorageCollectorExecTime 177

NBUStorageDetails 177

NBUStorageSummary 179

NBUStorageUpDownState 179

NBUStorageUpDownStatus 179

Refresh 89Paths

Binary 65

Configure 65

Debug Directory 65

Home Directory 65

Library 65

Netbackup Installation 65

NetBackup Log Directory 65

Temp Directory 65PATROL

Agent 53

PATROL Agent 49

PATROL Agent system 23

PATROL Central Console 49, 50

PATROL Central Console Server system 23

PATROL Central Web Server system 23

PATROL Console 49, 50

PATROL Console system 23PATROL Agent

Configure 48

Restart 58PATROL Console 47

Restart 58Permissions

Access 17Platforms

Unix 53Policies

Delete 68

Disable 68

Enable 68Policy Backup Restriction

Configure 85Policy Clients

Delete 68

Disable 68

Enable 68Preload

KM 48Preloaded

KM 49, 50Prepare

Debug Files 91

- R -Refresh

Parameters 89Release Notes 8

Reload

Commands 90remote PATROL Agent Checking 66

Reports

Available Media 164Requirements

Additional 14

BMC ProactiveNet Performance ManagementPortal 14

BMC Software PATROL Agent 14

BMC Software PATROL Console 14

Disk Space 23

Security 17

Software 14

Symantec NetBackup™ 14

System 13Restart

PATROL Agent 58

PATROL Console 58Robotic Drives

Administration 64

Delete 68

Disable 68

Enable 68

Status Configuration 74Robotic Libraries

Delete 68

Disable 68

Enable 68

Status Configuration 74

198

Ver

itas

Net

Bac

kup

KM

fo

r P

ATR

OL

Ver

sion

3.1

.01

- S -Security

Requirements 17Setup

Check 58

Initial 58

KM 58Solaris 17

Standalone Drives

Administration 64

Delete 68

Disable 68

Enable 68

Status Configuration 74Start

Master/Media Server 62Status Configuration

Clients 74

Daemons 74

Jobs 74

Managed Node 74

Mount Requests 74

Robotic Drives 74


Standalone Drives 74Stop

Master/Media Server 63Storages

Delete 68

Disable 68

Enable 68Sudo 53

User 17System

HP-UX 13

IBM AIX 13

Microsoft Windows 13

Oracle Solaris 13

Red Hat Linux 13

Requirements 13

- T -Troubleshooting 183

TrueSight

Abnormalities 181

Baselines 181

Key Performance Indicators 181

KPI 181

- U -Unix 53

Unload

KM 49, 50

- V -Verify

Application Discovery 56Veritas Cluster File System 66

Veritas Cluster Server 66

Veritas NetBackup

Administer 62Volume Pools

Delete 68

Disable 68

Enable 68

- W -Warning

Acknowledge 94Warning 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 TrueSight environment. Sentry Software alsodevelops adapters for BMC Atrium Orchestrator that enables IT administrators toautomate the execution of common requests and tasks that occur in the daily course ofIT operations. Combined with BMC’s servers and network automation tools, theadapters allow IT administrators to implement provisioning and decommissioningworkflows that cover all layers of their IT infrastructure. Finally, Sentry Software designsconnectors that bring storage capacity metrics into BMC TrueSight Capacity Optimizationto ensure IT administrators that their storage infrastructure is properly sized for theircurrent and future needs.

Like us on Facebook:facebook.com/sentrysoftware

Follow us on Twitter:

twitter.com/sentrysoftware

LEARN MORE

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

© BMC Software, Inc. All rights reserved.

ABOUT MARKETZONE DIRECT PRODUCTS

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

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

www.bmc.com.

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

BUSINESS RUNS ON I.T .

I.T . RUNS ON BMC SOFT WARE

http://facebook.com/sentrysoftware

http://twitter.com/sentrysoftware

http://twitter.com/sentrysoftware

http://facebook.com/sentrysoftware

Veritas NetBackup KM for PATROL Version 3.1

Documents

Transcript of Veritas NetBackup KM for PATROL Version 3.1