bmc proactivenet - symantec netbackup storage monitoring · using bmc proactivenet performance...

User Documentation August 2012

BMC ProactiveNet PerformanceManagement - SymantecNetBackup Storage MonitoringVersion 2.8.00

Table of Contents 2

Version 2.8.00

BMC ProactiveNet Performance Management - Symantec NetBackup Storage Monitoring

Table of Contents...........................................................................................................................5Release Notes for v2.8.01

...........................................................................................................................5Support Information

...........................................................................................................................5Legal Notices

...........................................................................................................................6Key Concepts

...........................................................................................................................6User Goals and Features

...........................................................................................................................6Business Value

...........................................................................................................................7Requirements

..................................................................................................................7Software Requirements

..................................................................................................................8System Requirements

..................................................................................................................8Security Requirements

...........................................................................................................................12Planning

...........................................................................................................................12Adding Central Monitoring Administration Tags

...........................................................................................................................13Installing

...........................................................................................................................13Preparing for Installation

...........................................................................................................................14Creating a Component Installation Package

...........................................................................................................................16Editing a Component Installation Package

...........................................................................................................................16Downloading and Installing an Installation Package

...........................................................................................................................17Configuring After Installation

...........................................................................................................................18Configuring General Settings

..................................................................................................................18Managing Policies

...........................................................................................................................19Configuring Monitor Settings

..................................................................................................................22Configuring Symantec NetBackup KM

..............................................................................................................22Configuring the User Account

..............................................................................................................24Enabling the Debug Mode

..............................................................................................................28Configuring the Maximum Number of Instances

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

..............................................................................................................35Configuring the NetBackup Server Discovery Overrides (Optional)

..................................................................................................................38Filtering Elements to Monitor

..................................................................................................................40Configuring Jobs

..................................................................................................................42Configuring Mount Requests

..................................................................................................................44Configuring NetBackup Policies

...........................................................................................................................45Configuring Thresholds

Table of Contents 3

Version 2.8.00


...........................................................................................................................48Using BMC ProactiveNet Performance Management -Symantec NetBackup Storage Monitoring

..................................................................................................................48Navigating the BMC ProactiveNet Operations Console

..................................................................................................................51Adding attributes to the graph

..................................................................................................................52Viewing and manipulating attribute graphs

..................................................................................................................52Viewing monitors for a device

..................................................................................................................53Changing thresholds

..................................................................................................................53Managing Baselines and Key Performance Indicators

...........................................................................................................................55Reference Guide

...........................................................................................................................56NetBackup Client

...........................................................................................................................56NetBackup Daemon

...........................................................................................................................57NetBackup Database

...........................................................................................................................57NetBackup Disk Pool

...........................................................................................................................58NetBackup Disk Storage

...........................................................................................................................59NetBackup Disk Volume

...........................................................................................................................60NetBackup Job

...........................................................................................................................60NetBackup Jobs

...........................................................................................................................61NetBackup Log

...........................................................................................................................61NetBackup Mount Request

...........................................................................................................................62NetBackup Policy

...........................................................................................................................63NetBackup Policy Client

...........................................................................................................................64NetBackup Robotic Drive

...........................................................................................................................65NetBackup Robotic Library

...........................................................................................................................66NetBackup Standalone Drive

...........................................................................................................................66NetBackup Volume Pool

...........................................................................................................................68Symantec NetBackup KM

BMC ProactiveNet Performance Management Symantec NetBackup Storage Monitoring

5Release Notes for v2.8.01

Version 2.8.00


Release Notes for v2.8.01

Fixed IssuesWhen configured through the BPPM Console Administration with custom configurations of certainclasses (i.e. NBU_CLIENT, NBU_POLICY, NBU_JOB, etc.), the KM would not properly switch to aforced classic mode.

Erroneous exit status values set through the BPPM Console Administration were not properlyprocessed.

Support Information

This section contains information about how to contact Customer Support and the levels of supportoffered for this and other releases.

If you have problems with or questions about a BMC product, or for the latest support policies, see theCustomer Support website at http://www.bmc.com/support. You can also access product documentsand search the Knowledge Base for help with an issue at http://www.SentrySoftware.com. If you do nothave access to the web and you are in the United States or Canada, contact Customer Support at 800537 1813. Outside the United States or Canada, contact your local BMC office or agent.

Legal Notices

© Copyright 2011 BMC Software, Inc.

BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., areregistered with the U.S. Patent and Trademark Office, and may be registered or pending registration inother countries. All other BMC trademarks, service marks, and logos may be registered or pendingregistration in the U.S. or in other countries. All other trademarks or registered trademarks are theproperty of their respective owners.

Linux is the registered trademark of Linus Torvalds.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may betrademarks of their respective owners.

UNIX is the registered trademark of The Open Group in the US and other countries.

The information included in this documentation is the proprietary and confidential information of BMCSoftware, Inc., its affiliates, or licensors. Your use of this information is subject to the terms andconditions of the applicable End User License agreement for the product and to the proprietary andrestricted rights notices included in the product documentation.

http://www.bmc.com/support

http://www.sentrysoftware.com

6Legal Notices

Version 2.8.00


BMC Software Inc.2101 City West Blv d, Houston TX 77042-2827, USA713 918 8800Custom er Support: 800 537 1813 (United States and Canada) or contact y our local support center

Key Concepts

The pages in this section provide a high-level overview of the product.

User Goals and Features

Business Value

Supported Platforms

Note that for convenience and brev ity , reference to BMC ProactiveNet Performance Management - SymantecNetBackup Storage Monitoring, may also be made as NetBackup KM.

User Goals and FeaturesNetBackup KM enables you to monitor the following in your environment:

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

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

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

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

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

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

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

Business ValueThe NetBackup KM provides current and historical information through a centralized console so you caneasily view and manage your entire environment. The product collects and brings critical performancedata and useful metrics into the BMC ProactiveNet Performance Management environment and enablesAdministrators to be warned whenever a problem occurs in their environment.

The NetBackup KM:

7Key Concepts

Version 2.8.00


ensures maximum backup application availability and maximum data protection

detects backup and restore errors

helps prevent backup system failures

detects disk or tapes space shortages

helps identify bottlenecks and optimize the backup policies.

RequirementsBefore installing the NetBackup KM, verify the:

software requirements

system requirements

security requirements.

Software RequirementsThe NetBackup KM supports the following platforms:

Veritas NetBackup 4.5



Symantec NetBackup 6.0


Symantec NetBackup 7


NetBackup KM v2.8.01 may support other versions of Symantec NetBackup but only the above versions have been

tested by Sentry Software.

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

Purpose Software Version

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

Sudo (superuser do) 1.6.7 or later

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

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

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

Any

When running NBU KM on Linux managed nodes

Korn shell binary (/bin/ksh) Any

When running NBU KM on Microsoft Windows x64 managed nodes

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

Any

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

8Key Concepts

Version 2.8.00


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

System RequirementsBMC ProactiveNet Performance Management - Symantec NetBackup Storage Monitoring supports thefollowing operating systems:

Operating System Version

Oracle SolarisTM 8, 9, 10

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

IBM® AIXTM 5.1, 5.2, 5.3, 6.1

Red Hat® Linux® 7.2

Microsoft® Windows® 2003, 2008, 2008 R2

Security Requirements

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

The following user accounts can be used:

On Unix platforms:

a root user

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

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

On Windows platforms:

an administrator user

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

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

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

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

9Key Concepts

Version 2.8.00


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

Access Permissions

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

Executable and Library Files accessed by the NetBackup KM User

Unix Microsoft Windows

INSTALL_PATH/netbackup INSTALL_PATH\NetBackup

INSTALL_PATH/netbackup/bin INSTALL_PATH\NetBackup\bin

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

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

INSTALL_PATH/volmgr/bin INSTALL_PATH\Volmgr\bin

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

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

/usr/openwin/lib INSTALL_PATH\NetBackup\lib

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

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

vxdctl (in Veritas Cluster File System)

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

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

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

i=0; sudoers="";

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

{

ctl=get(var);

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

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

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

10Key Concepts

Version 2.8.00


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

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

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

{

met="";

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

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

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

else

{

scmd=cmd;

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

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

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

}

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

}

}

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

Paths and Files Accessed by PATROL Agent User

Unix Microsoft Windows

INSTALL_PATH/netbackup/db INSTALL_PATH\NetBackup\db

INSTALL_PATH/volmgr/database INSTALL_PATH\Volmgr\database

INSTALL_PATH/var INSTALL_PATH\NetBackup\var

INSTALL_PATH/netbackup/db/error/ daily_messages.log

INSTALL_PATH\NetBackup\db\error\log_date

/var/adm/messages (on Solaris)

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

/var/log/messages (on Linux)

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

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

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

11Key Concepts

Version 2.8.00


Sudo User for Operating System Access

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

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

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

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

On SolarisUser_Alias NBUKMUSERS = user1, user2, user3

Defaults:NBUKMUSERS !lecture,!authenticate,\

env_keep+="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 and PATROL_HOME with therelevant paths.

On HP-UXUser_Alias NBUKMUSERS = user1, user2, user3


env_keep+="SHLIB_PATH INSTALL_PATH KM_HOME \

KM_TEMP",env_reset






12Key Concepts

Version 2.8.00





On AIX & LinuxUser_Alias NBUKMUSERS = user1, user2, user3


env_keep+="LIBPATH INSTALL_PATH KM_HOME \

KM_TEMP",env_reset









Planning

Adding Central Monitoring Administration TagsAdding Central Monitoring Administration tags should be taken into consideration before installation.

A policy specifies a set of actions to be taken when a specific condition on the BMC PATROL Agent isfulfilled. A policy enables you to perform the following actions:

Apply specific configuration to one or more BMC PATROL Agents

Configure thresholds and set baselines on BMC ProactiveNet Child Servers

Each policy is assigned a BMC ProactiveNet Central Monitoring Administration tag and each BMC PATROLAgent can have one or more tags assigned to it. When you assign a tag to a BMC PATROL Agent theassociated policy is applied to the PATROL Agent. You can assign the tag value of a policy to a PATROLAgent in the following ways:

You can add a PATROL Agent and set the tag as part of the configuration process that you performfrom Central Monitoring Administration. For details, see Managing downloads in Central MonitoringAdministration.

If the PATROL Agent has already been installed, use PATROL Configuration Manager to set thefollowing ruleset that provides the tags:/AgentSetup/Identification/Tags/TAG/tagName =tagDescription

For example if the tag which has to be applied is oracleTag, the ruleset is as follows/AgentSetup/Identification/Tags/TAG/oracleTag= “ORACLE MONITORING”

13Planning

Version 2.8.00


In BMC ProactiveNet version 9.0, the tag description is ignored, and only the tag name is used to evaluate the policy .

Installing

The creation of the NetBackup KM installation package is performed directly from BMC ProactiveNetCentral Monitoring Administration. An installation package for a component such as SymantecNetBackup can be downloaded and installed on several servers. The component installation package canbe edited and saved under a new name.

With Central Monitoring Administration, administrators select monitor installation components, such asthe BMC PATROL Agent and monitoring solutions, from a repository to create an installation package.The components can then be installed together using the installation package. Administrators can reusethe installation packages, or deploy the packages to multiple computers.

Preparing for InstallationThe BMC ProactiveNet Central Monitoring Repository is a requirement on the BMC ProactiveNet CentralServer where Central Monitoring Administration is enabled. The Central Monitoring Repository includesthe current versions of BMC components that you can use with BMC ProactiveNet.

After creating a component installation package, administrators can save the package to the MonitoringInstallation Packages list for future use, or download the package on the current host without saving thepackage. For saved packages, administrators can download and install the package on any host, or edita package.

For supported 64-bit Linux versions, you must install the Linux runtime package, glibc.i686, version 2.3.4 or later.W ithout the Linux runtime package, BMC ProactiveNet component installations might fail.

For further details regarding the BMC ProactiveNet Central Monitoring Administration, please refer to the BMCdocumentation.

14Installing

Version 2.8.00


Creating a Component Installation PackageIf you want to import the entire repository, first download Central Monitoring Repository files from theBMC Electronic Product Distribution (EPD) facility, or copy the files from your installation kit, to the BMCProactiveNet Central Server file system.

To import a single or custom solution1. In the navigation pane of Central Monitoring Administration, click the Repository drawer and

select Manage Repository.

2. Click Import.

3. In the Import a New Solution dialog box, select Single solution or Custom solution.

4. Browse to a source file in one of the following formats: zip, tar, or tar.gz.The solution must be located on the local computer from which you are running the CentralMonitoring Administration web-based console.

5. (Custom solution, only) provide the following details:

Custom solutions name: The name of the custom solution, as it will be displayed in CentralMonitoring Administration.

Custom solution version: The version number for the custom solution. Values in the first twoversion boxes are required.

6. Click Import.

The selected archive file is imported to the repository and extracted. You can close the window duringthe import process.

15Installing

Version 2.8.00


To create a component installation package1. In the navigation pane of Central Monitoring Administration, click the Repository drawer and

select Monitoring Repository.

2. Click Add .

3. Select the operating system for which you want to create a package, and then select a platform onwhich you want to install the package.The list of components in the repository that are supported on the specified operating system andplatform is displayed.

4. From the Available components list, select components that you want to include in the package.

5. From the Version list, select the version of the component that you want to include in the package.You can select a specific version or you can select latest, which automatically updates the packagewith the latest versions of the components when new versions of those components are added tothe Central Monitoring Repository. By default, the appropriate BMC PATROL Agent for the operating system and platform that youchose is included in the Selected components list.

6. Click the right arrow button to move the selected components into the Selected Components list,and then click Next.The installation wizards for the products that you selected are displayed. They'll vary depending onthe products or components that you selected to include in the package. Go through the wizards tocomplete the installation.

7. The Installation Package Details is displayed. Verify that the operating system and platform arecorrect for the type of package that you want to create. Also verify that the components that youwant to include are listed in the Included Components list. Provide the following information:

Name: Enter a unique name for the package.

(Optional) Description: Enter a description of the package.The description is displayed in the Monitoring Installation Packages list on the MonitoringRepository window.

Format: Select a file compression format for the package.

8. Perform one or both of the following actions:

To save the package for future installation on the current host or other hosts, click SaveInstallation Package. The package is available in the Monitoring Installation Packages list.

To download the package immediately, click Download.

If you click Download and do not click Save Installation Package, the package is not saved in the MonitoringInstallation Packages list for later use or editing.

9. When you are finished, click Close.

16Installing

Version 2.8.00


Editing a Component Installation PackageYou can edit any part of an existing component installation package except the operating system andplatform.

1. In the navigation pane of Central Monitoring Administration, click the Repository drawer andselect Monitoring Repository.

2. (Optional) To filter the list of packages, select an operating system from the Filter by OperatingSystem list.

3. Select the row for a package and click Edit .

4. From the Available components list, add or remove components, and click Next.

5. Perform one or more of the following actions, depending on your requirements:

Edit the installation details of existing components.

Add installation details for new components.

Click Finish Update to skip to the Installation Package Details window.

If you add a component to the package, you must complete the configuration process. The Finish Update buttonshows an explanatory tooltip and does not skip to the Installation Package Details window.

6. In the Installation Package Details window, modify the following information as needed:

Name: To save your changes to the same package, do not change the name. To save thepackage under a unique name, change the name.

(Optional) Description: Enter a description of the package.The description is displayed in the Monitoring Installation Packages list on the MonitoringRepository window.

Format: Select a file compression format for the installation package.

7. Perform one or both of the following actions:

To save the package for future installation on the current host or other hosts, click SaveInstallation Package.The package is available through the Monitoring Installation Packages list.

To download the installation package immediately, click Download.

If you click Download and do not click Save Installation Package, the changes are not saved in the MonitoringInstallation Packages list for later use or editing.

8. When you are finished, click Close.

Downloading and Installing an InstallationPackageYou can download an installation package and install the components on one or more hosts. Theinstallation runs silently with the information entered during package creation.

RecommendationIf you defined the BMC ProactiveNet Integration Service variable for PATROL Agents in theinstallation package, ensure the agents are started in phases. Do not start newly deployed agents all

17Installing

Version 2.8.00


at once. Start and configure monitoring for the agents in planned phases to reduce the performanceimpact on the Integration Service nodes and on the BMC ProactiveNet Server associated with theautomatic workflow process.

To download and install an installation package1. From the computer on which you want to install the package, log on to BMC ProactiveNet

Central Monitoring Administration.

2. (Optional) To filter the list of installation packages, select an operating system from the Filter byOperating System list.

3. Click the link for the installation package that you want to download.

4. Through the browser's download dialog box, save the installation package.

5. Extract the installation package as appropriate for your operating system. The package is extractedto the bmc_products directory on the current host.

6. From the bmc_products directory, run the installation utility for your operating system:

(UNIX or Linux) RunSilentInstall.sh

(Microsoft Windows) RunSilentInstall.exe

The package is installed on the current host. If the package includes a BMC PATROL Agent, the agentsends a configuration request by passing its tags to BMC ProactiveNet Central Monitoring Administration,via the Integration Service. Central Monitoring Administration evaluates policies that match the tags,determines the final configuration to be applied, and sends the configuration information back to theagent. Monitoring is based on the configuration information received by the agent.

If no policy matches the tags associated with the agent, the agent does not receive configurationinformation. The agent does not begin monitoring until a matching policy is created.

For further information regarding the Repository management, please refer to the BMC ProactiveNet CentralMonitoring Administration documentation.

Configuring After Installation

You configure monitoring of NetBackup KM when you create a policy. A policy is a template containingthe configuration of a PATROL Agent. A policy can be assigned to one or more PATROL Agents using aunique tag (Central Monitoring Administration tag), and a PATROL Agent can be assigned one or morepolicies with different priorities.

If you have not already added the Central Monitoring Administration tag to your PATROL Agents duringthe solution installation, then you must manually assign the tag after you have configured the policy. Fordetails, see Adding Central Monitoring Administration Tags.

18Configuring After Installation

Version 2.8.00


Configuring General SettingsThrough the General tab of the Add Policy dialog, you can create a new policy. A policy specifies a setof actions to be taken when a specific condition on the PATROL Agent is fulfilled. First and foremost,actions include monitor configuration. Once a monitor is configured, policies can also specify thresholdcreation and the setting of baselines. A policy can also include intelligent server-side thresholds so thatIT administrators can immediately be alerted on potential problems.

Field Instructions

Name Enter a policy name. Policy names must be unique. In an environment with tenants, policy names must be unique for a single tenant

Tenant(For environments withtenants)

Select a tenant name. See Policies and tenants for details.

Global indicates a policy applicable to all tenants.

Provider indicates a policy applicable to the cloud service provider

Enable policy Select this option to enable the policy, or clear the option to disable the policy. The option isselected by default. If you clear the option, the policy and its associations remain intact, butthe policy configuration is not applied until the policy is enabled again.

Precedence Enter a number from 0 to 999.

Description (Optional) Enter a policy description.

Tag Enter a Central Monitoring Administration tag.Policies are applied to BMC PATROL Agents with matching tags.Tags are case sensitive and cannot contain spaces or any of the following characters: /, \,{, }, <, >, ‘, “, &.

Policy precedence

When more than one policy is applied to a BMC PATROL Agent and BMC ProactiveNet Child Server,configuration is a union of every attribute defined the policies. If a conflict arises (that is, two policiesconfigure the same attributes), it is resolved in one of the following ways:

Policies with the same tag: If conflicting policies have the same tag, the precedence valuedetermines the order the policies are applied. The policy with the lower number value forprecedence is the policy from which the final configuration is applied.

Policies with different tags: If conflicting policies have different tags, then the policies areapplied according to the order they are listed on the BMC PATROL Agent. The policy listed last onthe agent is the policy from which the final configuration is applied.

Managing PoliciesThis topic provides general instructions for the following policy management tasks: editing, deleting,enabling and disabling.

Before you begin

Enable Central Monitoring Administration and log on to Central Monitoring Administration. Refer to theBMC documentation and more especially to the section Enabling and configuring Central Monitoring


Version 2.8.00


Administration for details.

Policies with only threshold configuration or server side configuration are applicable only after a policy with monitorconfiguration is applied.

To edit a monitoring policy1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a

policy view.

2. Select a policy and click Edit .

3. Edit the Configuring general settings of the policy.

4. Edit information on one or more of the following tabs:

Configuring monitor settings.

Configuring threshold settings.

5. Click Update.

To delete a monitoring policy

Deleting a policy deletes all monitor instances and most settings configured through the policy.Devices remain in the User Groups to which they have been added.

1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select apolicy view.

2. Select one or more policies and click Delete .

3. Click Yes to confirm deletion.

To enable or disable a monitoring policy

Enable or disable policies for maintenance and troubleshooting. When a policy is disabled, the policy andits associations remain intact, but the policy configuration is not applied until the policy is enabled again.


2. Select one or more policies and click Enable or Disable.

Configuring Monitor SettingsWhen you create or edit a policy, you can add and configure monitor types. The Add Monitor Typesdialog box presents configuration fields for compatible BMC PATROL monitoring solutions that arelocated in the Central Monitoring Repository. For a list of monitoring solutions that you can configurethrough Central Monitoring Administration, see Monitoring solutions configurable through CentralMonitoring Administration.

For configuration details for a specific monitor type, see the monitor documentation. To configurecustom monitoring solutions through Central Monitoring Administration, ensure the solution is structuredcorrectly; for details, see Building a PATROL Knowledge Module Developers Guide from BMC Support


Version 2.8.00


website.

To configure the Monitor Type settings using the AddMonitor Types dialog box

To add a monitor type:


2. Click Add to display the Add Policy dialog box.

3. Configure the policy general settings.

4. Click the Monitor Configuration tab.


Version 2.8.00


5. Click Add

A dding Monitor Ty pes

6. From the Solution menu, select Symantec NetBackup.

7. From the Version menu, select the required version.

8. From the Monitor Type menu, select the required monitor:

Monitor Type Description

NetBackup Client To set filtering options that indicate the clients to monitor.

NetBackup Daemon To set filtering options that indicate the daemons to monitor.

NetBackup Disk Pool To set filtering options that indicate the disk pools to monitor.

NetBackup Disk Storage To set filtering options that indicate the disk storage to monitor.

NetBackup Disk Volume To set filtering options that indicate the disks volume to monitor.

NetBackup Job To indicate:

how long the jobs in OK, Suspicious, and Failure status will be monitored.

the status the jobs will have when the monitoring period is over.

NetBackup Mount Request To indicate:


Version 2.8.00


how long the mount requests will be monitored.

the date/time format used in NetBackup mount request messages.

NetBackup Policy To set:

filtering options that indicate the policies to monitor

backup restrictions.

NetBackup Policy Client To set filtering options that indicate the policy clients to monitor.

NetBackup Robotic Drive To set filtering options that indicate the robotic drives to monitor.

NetBackup Robotic Library To set filtering options that indicate the robotic libraries to monitor.

NetBackup Standalone Drive To set filtering options that indicate the standalone drives to monitor.

NetBackup Volume Pool To set filtering options that indicate the volume pools to monitor.

Symantec NetBackup KM To set the general settings of Symantec NetBackup KM (credentials, debug mode,instances, multi-node mode, etc.)

Configuring Symantec NetBackup KMBefore using NetBackup KM, you'll have to configure its general settings. This section will learn you howto:

Configure the user account

Enable the debug mode

Configure the maximum number of instances

Configure the multi-node monitoring mode

Configure the NetBackup Server Discovery Overrides (Optional)

Configuring the User Account

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

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


Version 2.8.00


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

an administrator user

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

To configure the user account1. Add or edit a monitor type

2. From the Monitor Type menu, select Symantec NetBackup KM


Version 2.8.00


3. In the Hostname field, enter:

localhost to apply these settings to all PATROL Agents installed on NetBackup Master and Mediaservers

a hostname or IP address to apply these settings to a specific server

3. Set the NetBackup Credentials:

To use the default PATROL Agent Account, check the Use Agent Default Account box

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

(Unix Only) If the user account has sudo privileges, check the Use Sudo box and indicate thesudo binary file path (by default: usr/local/bin/sudo)

5. Click the Advanced button if you need to configure:

the debug mode

the maximum number of instances

the multi-node monitoring mode

the NetBackup Server discovery overrides (Optional).

6. Click Add to List.

Enabling the Debug Mode

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

To enable the debug mode1. Edit a Symantec NetBackup KM monitor type:

In the navigation pane of Central Monitoring Administration, click the Policies drawer and selecta policy view

Select a policy and click Edit

In the Monitor Configuration tab, select a policy and click Edit


Version 2.8.00


Editing the NetBackup Monitoring Settings


Version 2.8.00


2. From the List - NetBackup Monitoring Settings, select the host or localhost

3. Click the Advanced button

A dv anced Settings


Version 2.8.00


4. Click the Debug button

Configuring the Debug Mode

5. Select all the elements for which you want to obtain debug information

6. In the Options section, indicate:

when the system must stop logging debug information. The required format is: YYYY/MM/DD HH:MM:SS

where the debug file will be stored. The default path is: <PATROL_HOME>/lib/NBU/debug

7. Click Close on all pop-ups

8. Click Modify Selection in the main window and click Update.

When the debug end time is reached, a tar/zip file is automatically created under <PATROL_HOME>/lib/NBU/ and can be sent to the BMC Support for help. It is also recommended to check the NBU.log file,stored in <PATROL_HOME>/log, for any error.


Version 2.8.00


Configuring the Maximum Number of Instances

The NetBackup KM automatically sets the number of instances that will be displayed in the Console foreach monitored elements. This configuration, set to offer maximum performance, can however bemodified to better suit your environment.

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

To configure the maximum number of instances1. Edit a Symantec NetBackup KM monitor type:




Editing the NetBackup Monitoring Settings


Version 2.8.00




A dv anced Settings


Version 2.8.00


4. Click the Instance Max button

5. For each monitored element, indicate the number of instances to be displayed

6. Enter 0 in the relevant field to disable the monitoring of a specific element




Version 2.8.00


Configuring the Multi-Node Monitoring Mode

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

To configure the multi-node monitoring mode1. Edit a Symantec NetBackup KM monitor type:




Editing the Sy m antec NetBackup KM Monitor Ty pe


Version 2.8.00




A dv anced Settings


Version 2.8.00


4. Select Enable Multi-node Monitoring Mode and click the Multi-node M... button

Configuring Multi-node Mode

5. Configure the Multi-node Mode:

Select the appropriate Cluster Application.

Indicate the Failover Group Name. Leave this field blank if you previously selected VeritasCluster File System. Then the NetBackup KM will monitor the entire cluster from the active mastersystem, which is identified by “vxdctl -c mode” command. This method requires vxconfigd inenable mode with its clustered state active.

In the Monitoring Node Names field, name all the nodes where the solution is installed. The listmust be delimited by commas.

6. (Optional) Allow the solution to check the monitoring mode of the remote PATROL Agents. If the Remote PATROL Agent Checking is disabled, the solution will monitor actively through activemaster system or on the node where failover group is online and will not check the monitoringstatus of the other nodes through PATROL Agent:

Check the Enable Remote PATROL Agent Checking box.

Click the Remote Agent button


Version 2.8.00


Configuring the Rem ote A gent

In the Monitoring Node Name field, indicate the cluster node used for multi-node mode failover

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

In the Number of Attempts field, indicate how many times the solution will try to communicatewith the remote PATROL Agent before failing over

Enter the timeout between attempts

Click Add to List

Resume the procedure for all the nodes previously listed in step 5



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


Version 2.8.00


If a managed node is unable to determine the system which should be in A ctive Multi-node Mode, it will change toTemporary Single-node Mode. It will reset as soon as it detects a system in A ctive Multi-node Mode. If multiplemanaged nodes in a cluster runs in Single-node Mode or Temporary Single-node Mode, duplicate events may betriggered from shared components (clients, policies, jobs, requests, robotic libraries, drives, volume pools andstorages).

Configuring the NetBackup Server Discovery Overrides (Optional)

The solution automatically discovers the NetBackup installation path, the NetBackup temporary directorypath, the node type, and the node status daemons. This information can however be overridden.

To configure NetBackup server discovery overrides1. Edit a Symantec NetBackup KM monitor type:





Version 2.8.00


Editing the Sy m antec NetBackup KM Monitor Ty pe


Version 2.8.00




A dv anced Settings

4. In the NetBackup Server Discovery Overrides section, indicate:

the NetBackup installation path

the NetBackup log path

the temporary directory path

the node type

the node status daemons




Version 2.8.00


Filtering Elements to Monitor

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

Filtering options are available for the following monitor types: NetBackup Client, NetBackup Daemon,NetBackup Disk Pool, NetBackup Disk Storage, NetBackup Disk Volume, NetBackup Policy, NetBackupPolicy Client, NetBackup Robotic Drive, NetBackup Robotic Library, NetBackup Standalone Drive, andNetBackup Volume Pools.

To filter elements to monitor1. Add or edit a monitor type

Filtering Elem ents to Monitor

2. Select the Monitor Type for which you wish to apply filters.




Version 2.8.00



4. Indicate which elements will be monitored:

Click the Filtering button

In the Keep Only... section, indicate the element to be monitored and click Add to List

In the Exclude... section, indicate the element not to be monitored and click Add To List

Resume procedure to keep and/or exclude as many elements as required

Click Close

5. If needed, manually add elements to be monitored:

Click the Manual Add button

Indicate the element to be monitored and click Add to List

Resume procedure to add as many elements as required

Click Close

6. Click Add to List.

7. Click Add.

8. Finally, Update the policy.


Version 2.8.00


Configuring Jobs

By default, the NetBackup KM monitors all scheduled jobs that completed successfully for 24 hours andany other scheduled job for 72 hours. This monitoring duration can however be modified to better suityour requirements.

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

To configure jobs1. Add or edit a monitor type and select NetBackup Job as a Monitor Type.

Configuring NetBackup Jobs


Version 2.8.00





3. In the Monitoring Duration section:

Indicate how many hours the jobs in OK, Suspicious, and Failure status will be monitored

Select Keep Monitoring Active Jobs Indefinitely if you prefer to endlessly monitor active jobs

4. In the Erroneous Exit Status Codes field, indicate the exit status codes that will set the job stateto Error. By default, all non-zero exit status codes (except 150 - terminated by administrator) setthe job state to Failed. Codes entered must be delimited by commas.

5. Click Add to List

6. Click Add.

7. Finally, Update the policy.


Version 2.8.00


Configuring Mount Requests

By default, the NetBackup KM monitors all mount requests for 24 hours. This monitoring duration canhowever be modified to better suit your requirements.

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

To configure mount requests:

1. Add or edit a monitor type and select NetBackup Mount Request as a Monitor Type.

Configuring Mount Requests





Version 2.8.00


3. In the Mount Request Configuration section, indicate how many hours the mount requests willbe monitored

4. If the date/time format returned by Symantec NetBackup commands is different from your localsystem time zone, you will have to configure it in the Date/Time Format Configuration section:

Indicate the Expected Format. Refer to the table below to know the valid formats:

Format Description

Default Date/Time Format Leave blank.

EPOCH Set EPOCH, if the the time format is the number of secondsthat have elapsed since 00:00:00 GMT January 1, 1970

Year Formats

YY Two digit figureExample: 12 for the year 2012

YYYY Four digit figureExample: 2012

Month Formats

MO Two digit figureExample: 02 for February

MONTH Month full name Example: February

MON Three character nameExample: Feb

Date Formats

DD Two digit figureExample: 05

Day Formats

DAYFULL Day full name Example: Friday

DAY Three character nameExample: Fr

Hour Formats

HH Two digit figure

Minute Formats

MM Two digit figure

Second Formats

SS Two digit figure

Time Formats

[blank] Time is in 24-hour format

PM Time is in 12-hour format; am/pm is displayedExample: 10:15:00pm

P.M Time is in 12-hour format; a.m/p.m is displayedExample: 10:15:00p.m

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


Version 2.8.00


5. Click Add to List

6. Click Add.

Configuring NetBackup PoliciesBy default, the NetBackup KM monitors all policies configured on the master server, except the standardtemplate policies. Filters can however be applied to better suit your requirements. Additionnally, arestriction window can be configured for policy backups.

To configure policies1. Add or edit a monitor type and select NetBackup Policy as a Monitor Type.

Configuring Policies





Version 2.8.00


2. Set the filtering options. Refer to Filtering Elements to Monitor for more details.

3. If you want a warning to be triggered when a backup is started during a specific period of time,configure a backup restriction window:

Check the Enable Backup Restriction Window box

Indicate the Restriction Start and End Time. The format required is HH:MM:SS and therestriction window must at least last 5 minutes.

4. Click Add to list.

5. Click Add.

Configuring ThresholdsWhen you are creating or editing a policy, you can add and configure monitor thresholds. The AddThresholds dialog box presents threshold configuration fields for BMC ProactiveNet monitors that areconfigured through Central Monitoring Administration.

For details about baselines and Key Performance Indicators (KPI), see BMC ProactiveNet CentralMonitoring Administration or BMC ProactiveNet documentation or refer to the Managing Baselines andKey Performance Indicators section. For details about the monitored attributes, refer to the specificmonitor type in the Reference Guide section.

Before you begin

Ensure that monitor configuration is complete before thresholds are applied. Thresholds cannot beapplied to monitors that are not configured through Central Monitoring Administration. If you have notdone so already, define general policy details.

To add and configure monitor thresholds1. Open the Add Policy dialog box. Click for steps:

In the navigation pane of Central Monitoring Administration, click the Policies drawer and select apolicy view.

Click Add , or select an existing policy and click Edit .


Version 2.8.00


2. Select the Threshold Configuration tab and click Add .

A dding a Threshold

3. In the Add Thresholds dialog box, select an item from each of the following lists: Solution,Version, and Monitor Type. Configuration fields are displayed.

4. In the Scope list, the Instance option is automatically selected. Type an Instance Name string orregular expression to apply threshold configuration to instances with matching patterns. Select Match Device Name to include the associated device and use the entire<deviceName>\<instanceName> string for pattern matching. Instance thresholds are applied to thematched monitor instance names or instance names patterns.You can use the following regular expression patterns for the instance name: ?, +, *, ( ), |, [ ], { },

,̂ $, .If the instance name contains one of the pattern characters (except for *), use a backslash ( \ )before the pattern character. For example, to enter the instance name Storage1 (1), enterStorage1 $1$.

5. From the Attribute list, select a monitor attribute.

In the A ttribute list, some attributes are designated as key performance indicators (KPIs). Depending on themonitored env ironment and version, the list of KPIs might appear differently in the BMC ProactiveNet OperationsConsole.

6. From the Type of Threshold list, select the threshold type.

7. Select and enter values for the threshold parameters.

8. To continue configuration, perform one or more of the following actions in the Add Thresholdsdialog box, and then select a different monitor type, version, or solution:

To add the configuration details for the threshold to the Threshold Configuration tab, click theAdd button at the bottom of the window.

To return the settings in the current window to default values, click the Reset button at thebottom of the window. The values on the current window are reset. Be sure to click the Addbutton to save the configuration on the Threshold Configuration tab.


Version 2.8.00


9. When you finish configuration, click Close. The configuration details are displayed in the table onthe Threshold Configuration tab.

10. When you finish configuring thresholds, click Save at the bottom of the Add Policy dialog box, orUpdate at the bottom of the Edit Policy dialog box.

After you save or update the policy, new threshold configurations are pushed to BMC PATROL Agentswith matching Central Monitoring Configuration tags.

To edit a threshold configuration1. On the Threshold Configuration tab, select a threshold definition, and click Edit.

2. Edit the configuration values and click Update.

3. When you finish editing the threshold configuration, click Close.

4. To save changes to the policy, click Update at the bottom of the Edit Policy dialog box.

After you update the policy, updated threshold configurations are pushed to BMC PATROL Agents withmatching Central Monitoring Configuration tags.

To delete a threshold configuration1. On the Threshold Configuration tab, select attributes, monitor types, versions, or

solutions.

2. Click Delete.

3. After you delete one or more threshold configurations, click Close.

4. To save changes to the policy, click Update at the bottom of the Edit Policy dialog box.

After you update the policy, deleted threshold configurations are removed from BMC PATROL Agentswith matching Central Monitoring Configuration tags.

Recommended Thresholds

Thresholds define acceptable high and/or low values for the data collected. Thresholds can be createdas part of a policy that can be applied to multiple monitors types on multiple BMC PATROL Agents. The Reference Guide provides a list of monitor types with their respective attributes and, when meaningful,a recommended threshold.


Version 2.8.00


Using BMC ProactiveNet PerformanceManagement - Symantec NetBackup StorageMonitoringThis section provides a brief overview of how to navigate and use the product in the BMC ProactiveNetOperations Console.

Navigating the BMC ProactiveNet Operations Console

Adding attributes to the graph

Viewing and manipulating attribute graphs

Viewing monitors for a device

Changing Thresholds

For more detailed information, see BMC ProactiveNet User Guide in the PDF product guides.

Navigating the BMC ProactiveNet Operations ConsoleThe BMC ProactiveNet Operations Console is a Web-based application that provides options to navigatethrough BMC ProactiveNet and view all of the information collected and computed by the BMCProactiveNet Server related to events, views, and graphs.

Navigation tree

The navigation tree shows an at-a-glance synopsis of events and views. Event and component foldersare displayed hierarchically and are divided into the following categories, or nodes.

Object Definition

Global node The Global node contains the following default collectors:All Event Collectors—displays the entire event collector hierarchyAll Abnormalities—displays all the abnormality eventsAll Services—displays all the servicesAll Groups—displays all the groupsAll Devices—displays all the devicesBased on permissions, users can create event and component folders under this node to organize theevent view.

My Foldernode

Based on permissions, users can create event and component folders under this node to organize theevent view.

To further organize your display, beneath these top-level folders you can add event and componentfolders, including folders for Component Instances (CIs) associated with a service model. Your ability toadd event and component folders depends on your permissions.

The severity icons for a collector dynamically change depending on the severity level of the events forthat collector.


Version 2.8.00


For example, if there is a Critical event on one of the devices, the green icon changes to a red icon,indicating a Critical event. The icons enable you to see the status of devices on your systemimmediately.

For complete details, see the BMC ProactiveNet Getting Started Guide on the BMC Support website.

Navigation drawers

The navigation pane in the Operations Console contains a series of drawers that enable you to navigatethrough BMC ProactiveNet functions and views. You can select which drawers to display in thenavigation pane.

The following table describes the available drawers in the navigation pane and describes their functions.

Drawer Description

Main Provides access to event lists and displays event information and status.

Other cells Lists available remote cells connected to the BMC ProactiveNet Server and monitored by BMCProactiveNet.

Reports Enables you to generate and manage reports based on data collected by BMC ProactiveNet.Note: You must have permission to view this drawer.

Views & graphs Provides options for the management of views and graphs in the Operations Console

Bookmarks Enables you to view, rename, and delete bookmarks of objects and their related views that youcreate in the navigation tree.

Find CI Provides a search mechanism so that you can search for Component Instances that meet thespecified search criteria.Note: You must have permission to view this drawer.

Event and component folders

Event and component folders enable you to organize cells and collectors to make event displaysmeaningful for operators. For example, you might create an event folder for collectors that gatherdatabase warning events and allow only operators who are database administrators access to thatevent folder. You can drag components from one existing folder to another within the top-level folders inthe navigation tree. You also can drag and drop CIs from the Tile or Graph view to an existing folder inthe All Services folder.

Event folders

An event folder is a grouping of collectors that shows the relationship of events or abnormalities throughthe hierarchy of the navigation tree. Administrators define event folders and associate them with one ormore collectors. Each level of the collector is shown as a node under the event folder. An event list isassociated with the lowest level nodes of an event folder. The parent level of an event folder representsall of the events or abnormalities associated with the collectors.


Version 2.8.00


Event collectors

Event collectors gather events for display in an event list to provide operators with meaningful groups ofevents or abnormalities and to show relationship through the hierarchy of the nodes in the navigationtree. To access the event list for a collector, operators click the collector node in the navigation tree.Event collectors are dynamic or static. Nodes for dynamic collectors appear or disappear from thenavigation tree based on whether or not events are present that meet the criteria for those collectors.Nodes for static collectors remain in the navigation tree regardless of whether events are present ornot.

Component folders

A component folder is a grouping of groups, services, or devices from several different event lists(collectors) that shows the relationship of groups, services, or devices through the hierarchy of thenavigation tree. Administrators define component folders and associate them with one or more groups,services, or devices. Each level of the component folder is shown as a node under the parentcomponent folder. An event list is associated with the lowest level nodes of a component folder. Theparent level of a component folder represents all of the events associated with the groups, services, ordevices. Component folders are static or dynamic. You populate static component folders by selectingfrom a list of objects. You populate dynamic component folders by creating a query. Static foldersalways contain only the objects that you manually select. Dynamic folders contain the objects that matchthe query, so the contents of these folders can change without further editing.

Operations Console views

The following table shows the different views that are available, depending on what object you select inthe navigation tree. Each view is accessed by clicking the associated Console view icon. If a view is notavailable for the object that is selected in the navigation tree, the icon for that view is not displayed inthe toolbar.

View Description

Event The Event view displays all events in an event list. This is the default view for all objects. Use the Eventview to check the details of events and to address events that highlight incorrect state. Probable CauseAnalysis can help you to identify the cause of the event. An event could be assigned to other users, whocan acknowledge and take ownership of the event, fix the problem, and close the event. You can alsoaddress the incorrect condition by invoking remote actions, detailed diagnostics, and local actions. TheGraph view helps check the impacting service and you can cross-launch to Impact Model Designer, ServiceLevel Manager and Product Catalog in BMC Remedy IT Service Management (BMC Remedy ITSM).You can display an Event view for:

Event collectors

Abnormalities

Services

Groups

Devices

Monitors


Version 2.8.00


View Description

Title The Canvas view enables you to you create a graphical representation of the components that are beingmonitored in your environment. The components are represented by objects that you can place on abackground image. The objects can be graphics, such as images or connectors, or metrics informationrepresented in a tile.You can create and display a Canvas view for:

Event collectors

services

Groups

Devices

Tree/Graph

The Tree/Graph view displays information for a selected object as a tree that represents the hierarchy ofthe object. The Tree view is available for groups and services. You can use the Tree view to get a real-time,interactive visualization of the event status and other details of the selected group or service. In the Grouphyperbolic tree, the entire group hierarchy and devices are visible on a hyperbolic pane that is mapped to acircular display region. Service tree is applicable only for the selected service.If a service is selected in the navigation tree, this view displays a graphical representation of theconfiguration items in the service model and shows how those configuration items relate to each other. Usethe Graph view to monitor events for published service models that represent your business services.You can display a Tree/Graph view for:

Services

Groups

Grid Grid view displays information for the selected object in a tabular format. you can view the event status andother details of the selected object through hyperlinks to graphs, views, etc. You can display a Grid viewfor:

Abnormalities

Groups

Devices

For more detailed information, BMC ProactiveNet Getting Started Guide on the BMC Support website.

Adding attributes to the graphFollowing configuration, only one attribute is enabled for the graph of each monitor. You might want toadd additional attributes to the monitor graph.

1. In the BMC ProactiveNet Operations console, select the Navigation drawer.

2. Select Global > Devices.

3. Select the Grid view.All the monitored devices are displayed in table format.

4. Select a device from the displayed table.

5. Select a monitor.

6. Click Tools >Show Graph

7. Select the Attributes & Indicators tab.

8. Select one or more attributes.Up to 12 attributes of a monitor can be displayed on a single graph. Though only two units ofmeasurement can be used.


Version 2.8.00


Viewing and manipulating attribute graphs

The graph provides a visual display of the attributes of a monitor. Up to 12 attributes of a monitor canbe displayed on a single graph.

1. In the BMC ProactiveNet Operations console, select the Navigation drawer.


3. Select the Grid view. All the monitored devices are displayed in table format.

4. Select a device from the table.


6. Click Tools > Show Graph

If Collect Data is not enabled then no data is available.

The Graph Display window opens, displaying a graph displaying the values of the selected attributes forthis monitor.You can use the options available on this tab to manipulate the graph. For complete details, refer toBMC ProactiveNet User Guide on the BMC Support website.

Viewing monitors for a deviceThis section provides a brief overview of how to view the monitors for a selected device. For completedetails, refer to BMC ProactiveNet User Guide on the BMC Support website.

To view the Monitor types for a device1. In the BMC ProactiveNet Operations console, select the Navigation drawer.



4. Select a device from the table. A hierarchical tree listing the monitors for that device is displayed.You can click the + and - to expand and collapse nodes of the hierarchical tree.


Version 2.8.00


The following information is displayed:

Information Description

Monitor Name Device name or process name, a device might appear more than once if it is monitored byseveral PATROL Agents

Monitor Type Name of the monitor type.This will correspond to the element displayed in the Monitor Name column, specifying thetype of device or process monitored

Source Agent ProactiveNet server where the PATROL Agent and integration service are running

Open Number of open alerts, a green globe is displayed if no alerts are open

Closed Number of closed alerts

Enabled Enabled if data is being collected

Changing thresholdsYou can adjust the thresholds for the attributes of a monitor type either globally or for a specific deviceinstance. In the BMC ProactiveNet Operations console, select the Navigation drawer.



3. Select a device from the table.


5. Select Tools > Thresholds. A menu containing the available thresholds is displayed.

Global thresholds are applied to all monitor instances of the selected monitor type. Instance thresholds are applied tothe selected monitor instance.

6. Edit the Threshold settings

7. Click Apply.

Managing Baselines and Key Performance Indicators

In order to facilitate the detection of abnormalities on your monitored environment, BMC ProactiveNetcalculates baselines per attributes based on values collected over a specified period of time todetermine a normal operating range. When the collected values for these attributes are out of range, analert is triggered.

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

Managing baselines

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


Version 2.8.00


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

Requirements for baseline generation

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

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

Managing Key Performance Indicators

The KPI attribute of an attribute can be activated or deactivated manually through the BMC ProactiveNetAdministration Console. In this KM, some attributes have been designated as important indicators ofperformance (KPIs). We do not recommend that these default settings are modified.

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

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

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

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

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

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

deselect the KPI check box to remove the corresponding attribute from the KPIs for that monitortype

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

Attributes considered as KPIs are respectively identified by the following icon: .

55Reference Guide

Version 2.8.00


Reference Guide

Introduction

This chapter provides statistical information about resources, operating status, and performancesmanaged by the NetBackup KM. It contains tables describing the attributes used in the KM, grouped byMonitor Types, and provides a brief description of each attribute and its default settings.

Monitor Types

NetBackup Client

NetBackup Daemon

NetBackup Database

NetBackup Disk Pool

NetBackup Disk Storage

NetBackup Disk Volume

NetBackup Job

NetBackup Log

NetBackup Mount Request

NetBackup Policy

NetBackup Policy Client

NetBackup Robotic Drive

NetBackup Robotic Library

NetBackup Standalone Drive

NetBackup Volume Pool

Symantec NetBackup KM

Baselines and Key Performance Indicators

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

In this guide, attributes flagged as KPIs are respectively identified by the following icon: .

56Reference Guide

Version 2.8.00


NetBackup Client

Attributes

Name Description Units RecommendedAlert Conditions

BMC ProactiveNetAttribute Type

State Displays the state of theclient as reported in thecommand executed by thedata collector.

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

None Availability

Status Monitors the status of theclient.

0 = Ok1 = Suspicious 2 = Failure

Warning = 1Alarm = 2

Availability

NetBackup Daemon

Attributes



CPU Duration Displays the CPU secondsconsumed by the daemon.

seconds None Statistics

CPU Utilization Displays the percentageof CPU used by thedaemon.

% None Statistics

Memory Size Displays the core imagesize of the daemon in thevirtual memory.

KB None Statistics

Process Count Displays the number ofdaemon processes/threads found.

processes None Statistics

State Displays the state of thedaemon as reported in thecommand executed by thedata collector.

0 = Running1 = Sleeping2 = Waiting3 = Queued4 =Intermediate5 =Terminated 6 = Stopped/Disabled ;7 = Growing 8 =Nonexistent/NotResponding 9 = NotRunning-1 = Unknown

None Availability

57Reference Guide

Version 2.8.00


Status Monitors the status of thedaemon.



Availability

For detailed information about KP I, see Managing Baselines and Key Performance Indicators.

NetBackup Database

Attributes


BMCProactiveNetAttribute Type

Backup Elapsed Displays the elapsed timesince the last successfuldatabase backup.

hours None Statistics

File System Space

Used Percent

Monitors the percentage ofspace used by the filesystem where thedatabase resides.

% Warning between 95and 98Alarm: 98 and over

Statistics

Space Available Monitors the amount ofassigned space remainingavailable for use by thecatalog database.

MB Warning: between 2 and5Alarm when < 2

Availability

Space Growth Rate Displays the growth rate ofthe space used by thecatalog database.

MB/s None Statistics

Space Used Displays the amount ofassigned space used bythe catalog database.

MB None Statistics

Space Used Percent Monitors the percentage ofassigned space used bythe catalog database.

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

Statistics


NetBackup Disk Pool

Attributes



Up Down State Displays the up/down stateof the disk pool.

0 = Down1 = Up-1 = Unknown

None Availability

Up Down Status Monitors the up/downstatus of the disk pool.

0 = Ok 1 = Suspicious 2 = Failure


Availability

Volume Count Displays the number ofvolumes in the disk pool.

count None Statistics

58Reference Guide

Version 2.8.00


For detailed information KP I, see Managing Baselines and Key Performance Indicators.

NetBackup Disk Storage

Attributes



Up Down State Displays the up/down stateof the storage.

0 = Down 1 = Up -1 = Unknown

None Availability

Up Down Status Monitors the up/downstatus of the storage.

0 = Ok 1 =Suspicious 2 = Failure


Availability

59Reference Guide

Version 2.8.00


NetBackup Disk Volume

Attributes



Read Stream Count Displays the number ofcurrent read steams forthe disk volume.


Space Available Monitors the available diskvolume space for thebackup data to use.

GB Warning between 0 and1Alarm: between -1 and0

Availability

Space Growth Rate Displays the growth rate ofthe disk space used by thebackup data in this diskvolume.

GB/s None Statistics

Space Used Displays the disk spaceoccupied by the backupdata in this disk volume.

% None Statistics

Space Used Percent Monitors the percentage ofoccupied disk space againstthe capacity of this diskvolume.

% Warning between 95and 98Alarm: 98 and over

Statistics

Up Down State Displays the up/down stateof the disk volume.

0 = Down 1 = Up -1 = Unknown

None Availability

Up Down Status Monitors the up/downstatus of the disk volume.

0 = Ok 1 = Suspicious2 = Failure


Availability

Write Stream Count Displays the number ofcurrent write steams forthe disk volume


For detailed information KP I, see Managing Baselines and Key

60Reference Guide

Version 2.8.00


NetBackup Job

Attributes



Duration Displays the duration ofthe job from the start.


File Count Displays the number offiles backed up for thisjob.


Size Displays the amount ofdata backed up for thejob.

MB None Statistics

State Displays the state of thejob. This is determinedusing the job completionstate, job exit statuscode, last job operation,and the erroneous exitstatus filter.

0 =Completed 1 = Queued 2 = Mounting 3 = InProgress 4 = InProgress/Error 5 = Requeued 6 = Error 7 = Aborted8 =Suspended 9 =Incomplete 10 = Failed -1 = Unknown

None Availability

Status Monitors the status of thejob.



Availability

Throughput Displays the throughput ofthis job.



NetBackup Jobs

Attributes



61Reference Guide

Version 2.8.00


Active Backup Count Displays the number ofactive backup jobscurrently discovered andmonitored.


Active Count Displays the number ofactive jobs currentlydiscovered and monitored.


Active Non-Backup

Count

Displays the number ofactive non-backup jobscurrently discovered andmonitored.



NetBackup Log

Attributes



Alarm Message Count Monitors the number ofalarm messages.

count Alarm: more than orequal 1

Statistics

Filesystem Space Used

Percent

Monitors the percentage ofspace used by the filesystem (where the log fileresides).

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

Statistics

Space Available Monitors the availablespace for the log file to use(this is also the availablespace on the file system).

MB Warning: between 2 and5Alarm: 2 or less

Availability

File Space GrowthRate

Displays the growth rate ofthe amount of space usedby the log file.

KB/s None Statistics

File Space Used Displays the amount ofspace used by the log file.

KB None Statistics

Space Used Percent Monitors the percentage ofcapacity used by the logfile.


Statistics

Warning MessageCount

Monitors the numberwarning messages.

count Warning: more than orequal to 1

Statistics


NetBackup Mount Request

Attributes



62Reference Guide

Version 2.8.00


Elapsed Displays the elapsed timesince the mount requestwas issued.

minutes None Statistics

State Displays the state of themount request as reportedin the command executedby the data collector.

0 = Completed1 = Pending-1 = Unknown

None Availability

Status Monitors the status of themount request.



Availability


NetBackup Policy

Attributes



Backup Elapsed Displays the elapsed timesince the last backup forthis policy, regardless ofcompletion status of thebackup.


Backup Throughput Displays the throughput ofthe last backup for thispolicy.


Full Backup Duration Displays the duration ofthe last successful fullbackup for this policy.


Full Backup Elapsed Displays the elapsed timesince the last successfulfull backup for this policy.


Full Backup File Count Displays the number offiles backed up in the lastsuccessful full backup forthis policy.


Full Backup Size Displays the size of the lastsuccessful full backup forthis policy.

GB None Statistics

Incremental Backup

Duration

Displays the duration ofthe last successfulincremental backup for thispolicy.


Incremental Backup

Elapsed

Displays the elapsed timesince the last successfulincremental backup for thispolicy.


Incremental Backup

File Count

Displays the number offiles backed up in the lastsuccessful incrementalbackup for this policy.


63Reference Guide

Version 2.8.00


Incremental Backup

Size

Displays the size of the lastsuccessful incrementalbackup for this policy.

GB None Statistics

State Displays the state of thepolicy.

0 = Idle1 = Running 2 = Running inRestrictedWindow -1 = Unknown

None Availability

Status Monitors the status of thepolicy.

0 = Ok1 =Suspicious 2 = Failure


Availability

Successful Backup

Elapsed

Displays the elapsed timesince the last successfulbackup for this policy.



NetBackup Policy Client

Attributes



Backup Throughput Displays the throughput ofthe last backup for thispolicy client.


Last Full Backup

Duration

Displays the duration ofthe last successful fullbackup for this policyclient.


Last Full Backup File

Count

Displays the number offiles backed up in the lastsuccessful full backup forthis policy client.


Last Incremental

Backup Size

Displays the size of thelast successful full backupfor this policy client.

MB None Statistics

Last Incremental

Backup Duration

Displays the duration ofthe last successfulincremental backup for thispolicy client.


Last Incremental

Backup File Count

Displays the number offiles backed up in the lastsuccessful incrementalbackup for this policyclient.


Last Incremental

Backup Size

Displays the size of thelast successful incrementalbackup for this policyclient.

MB None Statistics


64Reference Guide

Version 2.8.00


NetBackup Robotic Drive

Attributes



State Displays the state of therobotic drive. This isdetermined from therobotic drive controlinformation.

0 = Idle 1 = Mounted2 = In Use 3 = Pending 4 = Down -1 = Unknown

None Availability

Status Monitors the status of therobotic drive.



Availability

Drive Throughput Displays the throughputof the robotic drive duringthe last backup activity.



65Reference Guide

Version 2.8.00


NetBackup Robotic Library

Attributes



Media Assigned Count Displays the number ofassigned media loaded inthis robotic library.

Assigned media are tapemedia assigned to a non-scratch volume pool.


Media Available Count Displays the number ofmedia available to use inthis robotic library. Thisincludes unassigned andscratch media.


Media Available

Percent

Monitors the percentageof available media againstthe total number of medialoaded in this roboticlibrary.

% Warning: between 2and 5Alarm: 2 or less

Statistics

Media Cleaning Left Monitors the number ofcleaning left on thecleaning media available inthis robotic library.

count Warning: 2 or lessAlarm: 0

Statistics

Media Count Displays the total numberof media loaded in thisrobotic library.


Media Scratch Count Displays the number ofscratch media loaded inthis robotic library.(Scratch media are tapemedia assigned to thescratch volume pool.)


Media Scratch Percent Monitors the percentageof scratch media againstthe total number of medialoaded in this roboticlibrary.

% None Statistics

Media Unassigned

Count

Displays the number ofunassigned media loadedin this robotic library.(Unassigned media aretape media not assigned toa volume pool.)


Media Unassigned

Percent

Monitors the percentageof unassigned mediaagainst the total numberof media loaded in thisrobotic library.

% None Statistics

66Reference Guide

Version 2.8.00


State Displays whether theinquiry for the roboticlibrary is valid or invalid. Itwill not perform anyremote robotic library testcommand on the mediaserver.

0 = Online1 = Remote 2 = Offline3 = Invalid-1 = Unknown

None Availability

Status Monitors the status of therobotic library.

0 = Ok 1 = Suspicious 2 = Failure


Availability

Throughput Displays the totalthroughput of each roboticlibrary drive during the lastbackup activities within thelast hour.


Up Drive Count Displays the number ofup / online state drives inthis robotic library.


For detailed information about KP I, see Managing Baselines and Key

NetBackup Standalone Drive

Attributes



State Displays the state of thestandalone drive. This isdetermined from thestandalone drive controlinformation.

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

None Availability

Status Monitors the status of thestandalone drive.

0 = Ok1 = Suspicious2 = Failure


Availability

Throughput Displays the throughput ofthe standalone driveduring the last backupactivity.



NetBackup Volume Pool

Attributes



67Reference Guide

Version 2.8.00


Media Active Count Displays the number ofactive media in this volumepool. (Active media areavailable tape media with astatus of Active, wheredata has been written butthe media is not yet full.)


Media Active Percent Monitors the percentage ofactive media against thetotal number of media inthis volume pool.

% Warning between 2 and5Alarm when < 2

Statistics

Media Count Displays the total numberof media in this volumepool.


Media Empty Count Displays the number of fullmedia in this volume pool.(Empty media are availabletape media with a statusActive and no data storedon them.)


Media Frozen Count Displays the number offrozen media in this volumepool. Frozen is a possiblestatus for a tape media.


Media Full Count Displays the number of fullmedia in this volume pool.Full is a possible status fora tape media.


Media Full Percent Monitors the percentage offull media against the totalnumber of media in thisvolume pool.


Statistics

Media Loaded Count Displays the number ofmedia in this volume pool,currently loaded to arobotic library.


Media ReadOnly Count

Displays the number ofmedia in this volume pool,currently read-only. Amedia turns read-onlywhen it has reached themaximum allowed mounts.


Media Scratch Count Displays the number ofscratch media in thisvolume pool. Theparameter is visible and setonly for scratch volumepools.

count Warning when < 2Alarm = 0

Statistics

Media Suspended

Count

Displays the number ofsuspended media in thisvolume pool. Suspended isa possible status for a tapemedia.


Media Unassigned

Count

Displays the number ofmedia in unassigned statein this volume pool.


68Reference Guide

Version 2.8.00


Media Unassigned

Percent

Monitors the percentage ofunassigned media againstthe total number of mediain this volume pool.If this parameter changesto warning or alarm state,the recovery action willtrigger an event.

% None Statistics

Media Unknown Count

Displays the number ofmedia in unknown state inthis volume pool.


Space Available Monitors the availablemedia space for thebackup data to useamongst the assignedmedia in this volume pool.

GB None Availability

Space Growth Rate Displays the growth rate ofthe total media space usedby the backup data in thisvolume pool.


Space Used Displays the total mediaspace occupied by thebackup data in this volumepool.

GB None Statistics

Space Used Percent Monitors the percentage oftotal occupied media spaceagainst the total mediacapacity of this volumepool (not including anyscratch media).


Statistics


Symantec NetBackup KM

Attributes



Login Status Monitors the status of theNetBackup KM login details(username/password) forthe operating system. Ifno valid username/password is detected forthe operating system, thisparameter will be set toFailure state. If there areany suspicious commandexits, this parameter willbe set to Suspicious state.



Collection Status

69Reference Guide

Version 2.8.00


Monitoring Mode Monitors failover mode ofthe NetBackup KM. Bydefault NetBackup KMruns in Permanent Single-node Mode. Refer toConfiguring the Multi-NodeMonitoring Mode for moredetails.

0 = PermanentSingle-nodeMode1 = TemporarySingle-nodeMode 2 = ActiveMulti-nodeMode3 = PassiveMulti-nodeMode-1 = Unknown

None Collection Status

Node Status Monitors error messagesfor the SymantecNetBackup application onthis managed system. Ifany of the SymantecNetBackup applicationdaemons is not running,this parameter will be setto Failure state. If thereare any suspiciouscommand exits due to anerror from the master/media server, thisparameter will be set toSuspicious state.



Availability

Index 70

Version 2.8.00


Index

- A -Abnormalities 53

Access

Executable Files 8

Files 8

Library Files 8

Paths 8

Permissions 8AIX 8

Application Class

NBU_SERVER 68Attribute 51, 52

Attributes

Active Backup Count 60

Active Count 60

Active Non-Backup Count 60

Alarm Message Count 61

Backup Elapsed 57, 62

Backup Throughput 62, 63

CPU Duration 56

CPU Utilization 56

Drive Throughput 64

Duration 60

Elapsed 61

File Count 60

File Space Growth Rate 61

File Space Used 61

File System Space Used Percent 57

Filesystem Space Used Percent 61

Full Backup Duration 62

Full Backup Elapsed 62

Full Backup File Count 62

Full Backup Size 62

Incremental Backup Duration 62

Incremental Backup Elapsed 62

Incremental Backup File Count 62

Incremental Backup Size 62

Last Full Backup Duration 63

Last Full Backup File Count 63

Last Incremental Backup Duration 63

Last Incremental Backup File Count 63

Last Incremental Backup Size 63

Media Active Count 66

Media Active Percent 66

Media Assigned Count 65

Media Available Count 65

Media Available Percent 65

Media Cleaning Left 65

Media Count 65, 66

Media Empty Count 66

Media Frozen Count 66

Media Full Count 66

Media Full Percent 66

Media Loaded Count 66

Media ReadOnly Count 66

Media Scratch Count 65, 66

Media Scratch Percent 65

Media Suspended Count 66

Media Unassigned Count 65, 66

Media Unassigned Percent 65, 66

Media Unknown Count 66

Memory Size 56

Process Count 56

Read Stream Count 59

Size 60

Space Available 57, 59, 61, 66

Space Growth Rate 57, 59, 66

Space Used 57, 59, 66

Space Used Percent 57, 59, 61, 66

State 56, 60, 61, 62, 64, 65, 66

Status 56, 60, 61, 62, 64, 65, 66

Successful Backup Elapsed 62

Throughput 60, 65, 66

Up Down State 57, 58, 59

Up Down Status 57, 58, 59

Up Drive Count 65

Volume Count 57

Warning Message Count 61

Write Stream Count 59

- B -Backup

Restriction 44Baseline 55

Baselines

BMC ProactiveNet Performance Management 53

Generation 53

Manage 53

Index 71

Version 2.8.00


Baselines

Requirements 53BMC 5

BMC Proactive Performance Management

Use 48BMC ProactiveNet Performance Management

Abnormalities 53

Baselines 53

Key Performance Indicators 53

KPI 53BMC Software 5

Business Value 6

- C -Client

Maximum Instances 28Clients

Debug 24Cluster Application 31

Component

folders 48Component Installation package

creating 14

downloading 16

editing 16Configure

Date format 42

Hostname 40

Jobs 40

Maximum Instances 28

Monitor Type 19

Monitoring Duration 40

Mount Request 42

Multi-node monitoring mode 31

Overrides 35

Time format 42Configuring

thresholds 45

- D -Daemon

Maximum Instances 28Daemons

Debug 24Database


Databases

Debug 24Date

Configure 42

Format 42Debug

Clients 24

Daemons 24

Databases 24

Debug 24

Directory Path 24

Disk Storages 24

Enable 24

End 24

Jobs 24

Logs 24

Mount Requests 24

Policies 24

Pools 24

Robotic Libraries/Drives 24

Server 24

Volume Pools 24

Volumes 24Disk Pool

Maximum Instances 28Disk Storage

Maximum Instances 28Disk Storages

Debug 24Disk Volume

Maximum Instances 28Downloading 16

Duration

Duration 42

Monitoring 42

- E -Enable

Backup Restriction 44Erroneous Exit Status 40

Event

collectors 48

folders 48

- F -Failover Group Name 31

Index 72

Version 2.8.00


Features 6

Filtering Options

NetBackup Client 38

NetBackup Daemon 38

NetBackup Disk Pool 38

NetBackup Disk Storage 38

NetBackup Disk Volume 38

NetBackup Policy 38

NetBackup Policy Client 38

NetBackup Robotic Drive 38

NetBackup Robotic Library 38

NetBackup Standalone Drive 38

NetBackup Volume Pools 38Filters

NetBackup Client 38

NetBackup Daemon 38

NetBackup Disk Pool 38

NetBackup Disk Storage 38

NetBackup Disk Volume 38

NetBackup Policy 38

NetBackup Policy Client 38

NetBackup Robotic Drive 38

NetBackup Robotic Library 38

NetBackup Standalone Drive 38

NetBackup Volume Pools 38

- G -General Settings

configuring 18Generate

Baselines 53Goals 6

Graphs 51, 52

- H -HP-UX 8

- I -InfoBox

Application Name 68

Application Version 68

Binary Path 68

Copyright 68

Host Name 68

Installation Path 68

Library Path 68

Master Server(s) 68

Media Server(s) 68

Monitoring Mode 68

Monitoring Node 68

Node Name(s) 68

Node Type 68

Operating System 68

PATROL Agent Version 68

Platform 68

Product Name 68

Product Release Date 68

Product Version 68

Support 68

Web Site 68Information

Closed 52

Enabled 52

Open 52

Source Agent 52Installation 13

configuring 17Installing 13

Preparation 13Instances

Client 28

Configure 28

Daemon 28

Database 28

Disk Pool 28

Disk Storage 28

Disk Volume 28

Job 28

Log 28

Maximum 28

Mount Request 28

Policy 28

Policy Client 28

Robotic Drive 28

Robotic Library 28

Standalone Drive 28

Volume Pool 28

- J -Job


Index 73

Version 2.8.00


Jobs

Active 40

Configure 40

Debug 24

Monitoring 40

- K -Key Concepts 6



Manage 53KPI 55


Manage 53

- L -Legal Notices 5

Linux 8

Log

Maximum Instances 28Logs

Debug 24

- M -Manage

Baselines 53


KPI 53Menu Commands

About 68

Administration 68

Debug 68

Force Discovery 68

Instance Limits 68

KM Status 68

Login 68

Monitoring Mode 68

Node Status 68

Node Type 68

Paths 68

Preloading 68

Refresh Parameters 68

Refresh Process Cache 68

Reload Commands 68

Start Master Server 68

Start Media Server 68

Stop Master Server 68

Stop Media Server 68Monitor

name 52

type 52Monitor Types

Configure 19

NetBackup Client 19, 55, 56

NetBackup Daemon 19, 55, 56

NetBackup Database 55, 57

NetBackup Disk Pool 19, 55, 57

NetBackup Disk Storage 19, 55, 58

NetBackup Disk Volume 19, 55, 59

NetBackup Job 19, 55, 60

NetBackup Jobs 60

NetBackup Log 55, 61

NetBackup Mount Request 19, 55, 61

NetBackup Policy 19, 55, 62

NetBackup Policy Client 19, 55, 63

NetBackup Robotic Drive 19, 55, 64

NetBackup Robotic Library 19, 55, 65

NetBackup Standalone Drive 19, 55, 66

NetBackup Volume Pool 19, 55, 66

Symantec NetBackup KM 19, 22, 55Monitoring

Configure 42

Duration 42Monitoring Duration

Jobs 40Monitoring Node Names 31

Mount Request

Configure 42


Monitoring Duration 42Mount Requests

Debug 24Multi-node monitoring mode

Configure 31

- N -Navigation

drawers 48

tree 48NBU_SERVER

Index 74

Version 2.8.00


NBU_SERVER

Application Class 68NetBackup

Policies 44NetBackup Policies

Configure 44NetBackup Server Discovery

Overrides 35

- O -Operations Console views

Event 48

Grid 48

Title 48

Tree/Graph 48Overrides

Configure 35

NetBackup Server Discovery 35

- P -Package 14, 16

Parameters

ExtraFilesList 68

NBUClientCollector 68

NBUCreateDistribution 68

NBUDaemonCollector 68

NBUDatabaseCollector 68

NBUDriveCollector 68

NBUJobCollector 68

NBULibraryCollector 68

NBULogCollector 68

NBULoginStatus 68

NBUMonitoringMode 68

NBUNodeStatus 68

NBUPolicyCollector 68

NBUPoolCollector 68

NBURemoveTempFiles 68

NBURequestCollector 68

NBUStorageCollector 68

NBUUpdateAgent 68Path

Debug 24PATROL Configuration Manager 12

Permissions

Access 8Platforms

Supported 7

Symantec NetBackup 7Policies

Configure 44

Debug 24

Manage 18

NetBackup 44Policy

Maximum Instances 28Policy Client

Maximum Instances 28Pools

Debug 24Precedence 18

- R -Reference Guide 55

Remote PATROL Agent Checking 31

Requirements 7

Security 8

System 8Restriction

Backup 44

End Time 44

Start Time 44

Window 44Robotic Drive

Maximum Instances 28Robotic Libraries/Drives

Debug 24Robotic Library


- S -Security

Requirements 8Server

Debug 24Solaris 8

Standalone Drive

Maximum Instances 28Sudo 22

User 8Support 5

Supported

Platforms 7

Index 75

Version 2.8.00


Supported

Symantec NetBackup 7Symantec NetBackup KM

Configure 22

Monitor Type 22System

HP-UX 8

IBM AIX 8

Microsoft Windows 8

Oracle Solaris 8

Red Hat Linux 8

Requirements 8

- T -Tag 18

Tags 12

Tenant 18

Thresholds

adding 45

configuring 45

editing 45

modifications 53

recommended 45Time

Configure 42

Format 42

- U -UNIX 22

Use

BMC Proactive Performance Management 48

User Account

Configure 22

patrol 22

Privileges 22

Sudo 22

- V -Volume Pool

Maximum Instances 28Volume Pools

Debug 24Volumes

Debug 24

- W -Windows 22

About BMC® SoftwareBMC Software, Inc. NYSE:BMC, is a leading provider of enterprise managementsolutions that empower companies to manage their IT infrastructure from abusiness perspective. Delivering Business Service Management, BMC Softwaresolutions span enterprise systems, applications, databases, and servicemanagement. Founded in 1980, BMC Software has offices worldwide and fiscal2004 revenues of more than $1.4 billion. For more information about BMC

Software, visit www.bmc.com.

About Sentry Software™Sentry Software, a strategic Technology Alliance Partner of BMC Software,provides key monitoring solutions specifically designed to expand thecapabilities of BMC Performance Manager, thus enabling up to 100% coverage ofany infrastructure. Sentry Software specializes in single solutions for multi-platform monitoring of hardware, custom applications or any IT component, andblackout windows. Sentry Software products are deployed in 45 countries acrossthe globe and lead the list of BMC Software’s third-party product sales. For more

information about Sentry Software, please visit www.sentrysoftware.net.

bmc proactivenet - symantec netbackup storage monitoring · using bmc proactivenet performance...

Documents