BMC ProactiveNet Performance Management EMC NetWorker Monitoring

Transcription

1 BMC ProactiveNet Performance Management EMC NetWorker Monitoring User Documentation January 2013

2 Table of Contents User Goals and Features...5 Business Value...5 Requirements...5 System Requirements...6 Software Requirements...6 Security Requirements...7 Adding Central Monitoring...10 Administration Tags Preparing for Installation Creating a Component Installation Package...14 Editing a Component Installation Package Downloading and Installing...15 an Installation Package...16 Configuring General Settings Managing Policies Configuring Monitor Settings...20 Configuring EMC NetWorker KM...20 Configuring the User Account Enabling the Debug Mode Configuring the Maximum Number of Instances Configuring the Multi-Node...30 Monitoring Mode Configuring the NetWorker...35 Server Discovery Overrides (Optional)...38 Filtering Elements to Monitor...38 Configuring Pending Requests Configuring Groups...41 Configuring Save Groups...43 Configuring Thresholds Using BMC ProactiveNet Performance Management...46 Navigating the BMC ProactiveNet Operations Console...50 Adding attributes to the graph Viewing and manipulating...50 attribute graphs...51 Viewing monitors for a device Changing thresholds Managing Baselines and Key Performance Indicators Table of Contents 2

3 EMC NetWorker KM...54 NetWorker Client...55 NetWorker Daemon...55 NetWorker Database...56 NetWorker Databases...57 NetWorker Group...57 NetWorker Group Client...58 NetWorker Jukebox...59 NetWorker Jukebox Device...60 NetWorker Log NetWorker Pending Request NetWorker Save Client...62 NetWorker Save Group...63 NetWorker Save Groups NetWorker Standalone Device NetWorker Volume Pool Table of Contents

4 This section contains information about how to contact Customer Support and the levels of support offered for this and other releases. If you have problems with or questions about a BMC product, or for the latest support policies, see the Customer Support website at You can also access product documents and search the Knowledge Base for help with an issue at If you do not have access to the web and you are in the United States or Canada, contact Customer Support at Outside the United States or Canada, contact your local BMC office or agent. Copyright 2011 BMC Software, Inc. BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property 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 be trademarks 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 BMC Software, Inc., its affiliates, or licensors. Your use of this information is subject to the terms and conditions of the applicable End User License agreement for the product and to the proprietary and restricted rights notices included in the product documentation. BMC Softw are Inc CityW est Blvd, Houston TX , USA Customer Support: (United States and Canada) or contact your local support center The pages in this section provide a high-level overview of the product. User Goals and Features Business Value Requirements Note that for convenience and brevity, reference to BMC ProactiveNet Performance Management - EMC NetW orker Monitoring, may also be made as EMC NetW orker KM. 4

5 User Goals and Features EMC NetWorker KM enables you to monitor the following in your environment: Server availability: status of all the processes. Log files: monitoring of the daemon.log and messages files, size, etc. Pending Media Events: monitoring of the media mount requests Bootstrap Messages: bootstrap settings verification, recommendations, etc. Client Indexes: number of entries, utilization as a percentage and index size. Devices: status of mounted volumes and history of volume mounts. Save Groups and Save Sets: status, progress, size and duration Business Value provides current and historical information through a centralized console so you can easily view and manage your entire EMC NetWorker environment. The product collects and brings critical performance data and useful metrics into the BMC ProactiveNet Performance Management environment and enables Backup and Storage Administrators to be warned whenever a problem occurs in their EMC NetWorker environment. The : Detects backup and restore errors Monitors Storage/Library availability Detects abnormalities around backups and performances Helps to analyze trends on storage capacity Helps to identify bottlenecks and optimize the backup system performance. Requirements Before installing the EMC NetWorker KM, verify the: software requirements system requirements security requirements. User Goals and Features 5

6 System Requirements Operating System Operating System Version Oracle SolarisTM 8, 9, 10 HP-UX 11.00, 11.11, 11iv2, 11iv3 IBM AIXTM 5.1, 5.2, 5.3, 6.1 Red Hat Linux 7.2 Microsoft Windows 2003, 2008, 2008 R2 If the operating system is upgraded (or dow ngraded) at a later date, you w ill need to reload commands for the EMC NetW orker KM. Software Requirements Software Version EMC NetWorker 6.1.x, 6.2, 7.0, 7.1.x, 7.2.x, 7.3.x, 7.4.x, 7.5.x, 7.6.x BMC PATROL Agent , 3.5.x, 3.6.x, 3.7.x, 3.8.x, 3.9.x, 9.x BMC PATROL Console 3.4.x, 3.5.x, 7.x BMC Portal 2.3.x, 2.4.x, 2.5.x, 2.6.x, 2.7.x, 2.8.x BMC ProactiveNet Performance Manager 8.x, 8.5.x, 8.6.x, 9.x If you're running the EMC NetWorker KM with sudo user account, or on AIX, LINUX, or Microsoft Windows x64 managed nodes, please verify these additional software requirements: Purpose Software Version When running EMC NetWorker KM with sudo user account on Solaris, HP-UX, AIX or Linux managed nodes Sudo (superuser do) or later When running EMC NetWorker KM on Linux managed nodes Korn shell binary (/bin/ksh) Any When running EMC NetWorker KM on Microsoft Windows x64 managed nodes Reg.exe patch KB ( Any The Microsoft Windows x64 Reg.exe patch, KB is required to allow access to 64-bit registry keys from PATROL Agent. Access the above patch site from the managed node to obtain the correct patch for that platform. Requirements 6

7 Security Requirements A user account with administrative privileges must be configured in BMC PATROL to read and execute EMC NetWorker application programs and access file systems. Depending on the operating systems used, several options will be available. The following user accounts can be used: On Unix platforms: a root user a non-root user, such as patrol, that has sudo privileges on EMC NetWorker to execute application programs and access file systems a non-root account, such as patrol, configured in the EMC NetWorker application to administer the EMC NetWorker application. On Windows platforms: an administrator user a non-administrator account, such as patrol, configured in the EMC NetWorker application to administer the EMC NetWorker application. The user login details are configured in the KM. The password is stored in the PATROL Agent in a DES encrypted format. The encrypted password can be viewed by any user who has access to the PATROL Agent configuration variables (pconfig). This user could then execute PSL statements using the encrypted password through the PATROL Console. This can be prevented by setting up an appropriate Access Control List (ACL) for users. Please refer to the PATROL Agent Reference Manual for details on how to set up an ACL. Access Permissions The EMC NetWorker KM user needs read & execute permission to executable and library files under the paths listed below. The EMC NetWorker installation path INSTALL_PATH is normally /nsr or / opt/networker (on Unix) or C:\Program Files\nsr (on MS Windows). Unix Microsoft Windows INSTALL_PATH/bin INSTALL_PATH\bin INSTALL_PATH/lib /usr/bin /usr/sbin /usr/sbin/nsr /usr/lib/nsr /etc/lgtouscsi If the KM is enabled to failover in a clustered environment, the login user needs execute permissions Requirements 7

8 to the following cluster commands: /opt/vrtsvcs/bin/hagrp (in Veritas Cluster Server) vxdctl (in Veritas Cluster File System) /usr/cluster/bin/clrg (in Oracle Solaris Cluster) C:\Windows\sysnative\cluster (in Microsoft Cluster) The EMC NetWorker KM includes some scripts which should be executable by the PATROL Agent user and the NetWorker KM user. These scripts are stored under KM_HOME path, normally PATROL_HOME/lib/NSR. To list all OS commands used by the EMC NetWorker KM, execute the following PSL code from the PATROL Console, using PSL Task menu, after installing and loading the KM. i=0; sudoers=""; foreach var (grep("^/runtime/nsr/commandcontrols/",pconfig("list"))) { ctl=get(var); opt=ntharg(grep("option",ctl),"2-"," ="); nsa=ntharg(grep("nosudoattempt",ctl),"2-"," ="); sua=ntharg(grep("singleuserattempt",ctl),"2-"," ="); typ=ntharg(grep("commandtype",ctl),"2-"," ="); cmd=nthargf(grep("commandtext",ctl),"2-","=","="); if((typ == "") (typ == "OS")) { met=""; if(opt == "NoLogin") { met = "(run as patrol user)"; } elsif(nsa == "YES") { met = "(run as configured user without sudo)"; } elsif(sua == "YES") { met = "(run as supplied user - used in menu)"; } else { scmd=cmd; s=index(scmd,"%sudo"); if(s) { scmd=replace(substr(scmd,s,length(scmd)),"%sudo",""); } sudoers=union(sudoers,ntharg(ntharg(scmd,1," "),"1-"," "," ")); } printf("(%2d) %-30s %-40s: %s\n",i++,ntharg(var,"5","/"),met,cmd); } } printf("\n\ncommands used with sudo:\n%s",sort(sudoers)); The PATROL Agent user (normally patrol) needs read & execute permission to following paths and files: Unix Microsoft Windows INSTALL_PATH/res INSTALL_PATH\res INSTALL_PATH/index INSTALL_PATH\index INSTALL_PATH/mm INSTALL_PATH\mm INSTALL_PATH/logs/daemon.log INSTALL_PATH\logs\daemon.log INSTALL_PATH/logs/messages INSTALL_PATH\logs\messages INSTALL_PATH/logs/summary INSTALL_PATH\logs\summary INSTALL_PATH/lic/logs/lgtomd.log INSTALL_PATH\logs\savegrp.log /var/adm/messages (on Solaris) Requirements 8

9 /var/adm/syslog/syslog.log (on HP-UX) To access files under above paths the relevant user needs read & execute permission to all parent directories. If a monitored log file cannot be read by the PATROL Agent user, it will be copied to KM_TEMP path using the configured KM login account, and processed by the PATROL Agent user. On completion, the copied log file will be removed. This may increase the file system usage under KM_TEMP temporarily during this activity. On Windows platforms the EMC NetWorker installation is identified by checking the Windows Registry. Depending on whether you are using a 32/64-bit OS and/or 32/64-bit Application, the Registry entries are stored in different locations: HKEY_LOCAL_MACHINE\SOFTWARE\Legato\NetWorker\ and HKEY_LOCAL_MACHINE\SOFTWARE \Wow6432Node\Legato\NetWorker\. Sudo User for Operating System Access If a non-root user with sudo privileges is preferred as the EMC NetWorker KM user, configure the account as a sudoer through the visudo utility using code appropriate for your platform as detailed below. This user should be able to execute NetWorker commands and OS commands. The code below also applies to all non-root users who may execute EMC NetWorker KM administration and report menu commands using their sudo privileges. The EMC NetWorker KM accepts any non-root user with the following sudo configuration in the sudoers file. Please replace user1, user2, user3 with appropriate KM user name. The EMC NetWorker installation path INSTALL_PATH, referenced below is normally /nsr or /opt/networker and PATROL_HOME is the path where the PATROL Agent is installed (including the target, like /opt/bmc/patrol3/solaris29sun4/). On Solaris: User_Alias NSRKMUSERS = user1, user2, user3 Defaults:NSRKMUSERS!lecture,!authenticate,\ env_keep+="ld_library_path INSTALL_PATH KM_HOME \ KM_TEMP",env_reset NSRKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\ /usr/sbin/nsr/*,/etc/lgtouscsi/*\ INSTALL_PATH/bin/*,\ PATROL_HOME/lib/NSR/*,PATROL_HOME/bin/* user1, user2, user3 must be replaced w ith username(s) used by the KM; INSTALL_PATH and PATROL_HOME w ith the relevant paths. On HP-UX: User_Alias NSRKMUSERS = user1, user2, user3 Defaults:NSRKMUSERS!lecture,!authenticate,\ env_keep+="shlib_path INSTALL_PATH KM_HOME \ KM_TEMP",env_reset NSRKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\ Requirements 9

10 /usr/sbin/nsr/*,/etc/lgtouscsi/*\ INSTALL_PATH/bin/*,\ PATROL_HOME/lib/NSR/*,PATROL_HOME/bin/* user1, user2, user3 must be replaced w ith username(s) used by the KM; INSTALL_PATH and PATROL_HOME w ith the relevant paths. On AIX: User_Alias NSRKMUSERS = user1, user2, user3 Defaults:NSRKMUSERS!lecture,!authenticate,\ env_keep+="libpath INSTALL_PATH KM_HOME \ KM_TEMP",env_reset NSRKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\ /usr/sbin/nsr/*,/etc/lgtouscsi/*\ INSTALL_PATH/bin/*,\ PATROL_HOME/lib/NSR/*,PATROL_HOME/bin/* user1, user2, user3 must be replaced w ith username(s) used by the KM; INSTALL_PATH and PATROL_HOME w ith the relevant paths. This non-root sudo user configured in the KM will be able to execute root equivalent commands by opening a shell window. To prevent this, ensure this user is only used within the KM and not made public for general use. Entering the non-root sudo user with Use Sudo option selected in to the KM login configuration dialog, before updating the sudoers file, will generate sudo errors. Also if the sudo user is configured differently, the KM may run sudo commands using incorrect sudo settings, which will expose the sudo user password. Adding Central Monitoring Administration Tags Adding 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 is fulfilled. 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 PATROL Agent can have one or more tags assigned to it. When you assign a tag to a BMC PATROL Agent the associated policy is applied to the PATROL Agent. You can assign the tag value of a policy to a PATROL Agent in the following ways: Requirements 10

11 You can add a PATROL Agent and set the tag as part of the configuration process that you perform from Central Monitoring Administration. For details, see Managing downloads in Central Monitoring Administration. If the PATROL Agent has already been installed, use PATROL Configuration Manager to set the following 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 In BMC ProactiveNet version 9.0, the tag description is ignored, and only the tag name is used to evaluate the policy. The creation of the EMC NetWorker KM installation package is performed directly from BMC ProactiveNet Central Monitoring Administration. An installation package for a component can be downloaded and installed on several servers. The component installation package can be edited and saved under a new name. With Central Monitoring Administration, administrators select monitor installation components, such as the 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 reuse the installation packages, or deploy the packages to multiple computers. Preparing for Installation The BMC ProactiveNet Central Monitoring Repository is a requirement on the BMC ProactiveNet Central Server where Central Monitoring Administration is enabled. The Central Monitoring Repository includes the 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 Monitoring Installation Packages list for future use, or download the package on the current host without saving the package. For saved packages, administrators can download and install the package on any host, or edit a package. For supported 64-bit Linux versions, you must install the Linux runtime package, glibc.i686, version 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 BMC documentation. Adding Central Monitoring Administration Tags 11

12 Creating a Component Installation Package If you want to import the entire repository, first download Central Monitoring Repository files from the BMC Electronic Product Distribution (EPD) facility, or copy the files from your installation kit, to the BMC ProactiveNet Central Server file system. To import a single or custom solution 1. 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 Central Monitoring 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 Central Monitoring Administration. Custom solution version: The version number for the custom solution. Values in the first two version boxes are required. 6. Click Import. The selected archive file is imported to the repository and extracted. You can close the window during the import process. Creating a Component Installation Package 12

13 To create a component installation package 1. 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 on which you want to install the package. The list of components in the repository that are supported on the specified operating system and platform 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 package with the latest versions of the components when new versions of those components are added to the Central Monitoring Repository. By default, the appropriate BMC PATROL Agent for the operating system and platform that you chose 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 on the products or components that you selected to include in the package. Go through the wizards to complete the installation. 7. The Installation Package Details is displayed. Verify that the operating system and platform are correct for the type of package that you want to create. Also verify that the components that you want 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 Monitoring Repository 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 Save Installation Package. The package is available in the Monitoring Installation Packages list. To download the package immediately, click Download. If you click Dow nload and do not click Save Installation Package, the package is not saved in the Monitoring Installation Packages list for later use or editing. 9. When you are finished, click Close. Creating a Component Installation Package 13

14 Editing a Component Installation Package You can edit any part of an existing component installation package except the operating system and platform. 1. In the navigation pane of Central Monitoring Administration, click the Repository drawer and select Monitoring Repository. 2. (Optional) To filter the list of packages, select an operating system from the Filter by Operating System 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 button show s an explanatory tooltip and does not skip to the Installation Package Details w indow. 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 the package 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 Monitoring Repository 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 Save Installation Package. The package is available through the Monitoring Installation Packages list. To download the installation package immediately, click Download. If you click Dow nload and do not click Save Installation Package, the changes are not saved in the Monitoring Installation Packages list for later use or editing. 8. When you are finished, click Close. Editing a Component Installation Package 14

15 Downloading and Installing an Installation Package You can download an installation package and install the components on one or more hosts. The installation runs silently with the information entered during package creation. Recommendation If you defined the BMC ProactiveNet Integration Service variable for PATROL Agents in the installation package, ensure the agents are started in phases. Do not start newly deployed agents all at once. Start and configure monitoring for the agents in planned phases to reduce the performance impact on the Integration Service nodes and on the BMC ProactiveNet Server associated with the automatic workflow process. To download and install an installation package 1. 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 by Operating 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 extracted to 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 agent sends 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 the agent. 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 configuration information. 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 Central Monitoring Administration documentation. Downloading and Installing an Installation Package 15

16 You configure monitoring of EMC NetWorker KM when you create a policy. A policy is a template containing the configuration of a PATROL Agent. A policy can be assigned to one or more PATROL Agents using a unique tag (Central Monitoring Administration tag), and a PATROL Agent can be assigned one or more policies with different priorities. If you have not already added the Central Monitoring Administration tag to your PATROL Agents during the solution installation, then you must manually assign the tag after you have configured the policy. For details, see Adding Central Monitoring Administration Tags. Configuring General Settings Through the General tab of the Add Policy dialog, you can create a new policy. A policy specifies a set of 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 threshold creation and the setting of baselines. A policy can also include intelligent server-side thresholds so that IT 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 with tenants) Select a tenant name. See Policies and tenants for details. Global indicates a policy applicable to all tenants. Enable policy Select this option to enable the policy, or clear the option to disable the policy. The option is selected by default. If you clear the option, the policy and its associations remain intact, but the 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: /, \, {, }, <, >,,, &. Provider indicates a policy applicable to the cloud service provider 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 by the policies. If a conflict arises (that is, two policies configure 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 value determines the order the policies are applied. The policy with the lower number value for precedence is the policy from which the final configuration is applied. Policies with different tags: If conflicting policies have different tags, then the policies are applied according to the order they are listed on the BMC PATROL Agent. The policy listed last on the agent is the policy from which the final configuration is applied. 16

17 Managing Policies This 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 the BMC documentation and more especially to the section Enabling and configuring Central Monitoring Administration for details. Policies w ith only threshold configuration or server side configuration are applicable only after a policy w ith monitor configuration is applied. To edit a monitoring policy 1. 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 a policy 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 and its associations remain intact, but the policy configuration is not applied until the policy is enabled again. 1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view. 2. Select one or more policies and click Enable or Disable. Configuring General Settings 17

18 Configuring Monitor Settings When you create or edit a policy, you can add and configure monitor types. The Add Monitor Types dialog box presents configuration fields for compatible BMC PATROL monitoring solutions that are located in the Central Monitoring Repository. For a list of monitoring solutions that you can configure through Central Monitoring Administration, see the Monitoring solutions configurable through Central Monitoring Administration chapter in the BPPM online documentation. For configuration details for a specific monitor type, see the monitor documentation. To configure custom monitoring solutions through Central Monitoring Administration, ensure the solution is structured correctly; for details, see the Building a PATROL Know ledge Module Developers Guide on BMC Support website. To configure the Monitor Type settings using the Add Monitor Types dialog box To add a monitor type: 1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view. 2. Click Add to display the Add Policy dialog box. 3. Configure the policy general settings. 4. Click the Monitor Configuration tab. Configuring Monitor Settings 18

19 5. Click Add A dding Monitor Types 6. From the Solution menu, select EMC NetWorker. 7. From the Version menu, select the required version. 8. From the Monitor Type menu, select the required monitor: Monitor Type Description EMC NetWorker KM To set the general settings of EMC NetWorker KM (credentials, debug mode, instances, multi-node mode, etc.) NetWorker Client Enables access to the filtering options to select the client elements that will be monitored. NetWorker Daemon Enables access to the filtering options to select the daemon elements that will be monitored. NetWorker Group To: Configuring Monitor Settings 19

20 enable access to the filtering options to select the group elements that will be monitored. set backup restrictions. NetWorker Group Client Enables access to the filtering options to select the group client elements that will be monitored. NetWorker Jukebox Enables access to the filtering options to select the jukebox elements that will be monitored. NetWorker Jukebox Devices Enables access to the filtering options to select the jukebox devices elements that will be monitored. NetWorker Pending Request To indicate: how long the pending requests will be monitored. the date/time format used in NetWorker pending request messages. NetWorker Save Group To indicate: how long the save groups in OK, Suspicious, and Failure status will be monitored which saved clients will be monitored (, Failed only, Succeeded Only, All) NetWorker Standalone Devices Enables access to the filtering options to select the standalone devices elements that will be monitored. NetWorker Volume Pools Enables access to the filtering options to select the volume pools elements that will be monitored. Configuring EMC NetWorker KM Before using EMC NetWorker KM, you'll have to configure its general settings. This section will learn you how to: configure the user account enable the debug mode configure the maximum number of instances configure the multi-node monitoring mode configure the NetWorker server discovery overrides (Optional). Configuring the User Account A user account with administrative privileges must be configured in BMC ProactiveNet to read and execute EMC NetWorker application programs and file systems. Depending on the operating systems used, several options will be available. On Unix platforms, you can use the following user accounts: Configuring Monitor Settings 20

21 a root user a non-root user, such as patrol, that has sudo privileges on EMC NetWorker to execute application programs and access file systems a non-root account, such as patrol, configured in the EMC NetWorker application to administer the EMC NetWorker application. On Windows platforms, you can use the following user accounts: an administrator user a non-administrator account, such as patrol, configured in the EMC NetWorker application to administer the EMC NetWorker application. To configure the user account 1. Add or edit a monitor type 2. From the Monitor Type menu, select EMC NetWorker KM Configuring Monitor Settings 21

22 3. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on the EMC NetWorker servers a hostname or IP address to apply these settings to a specific server 4. Set the NetWorker 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 the sudo 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 NetWorker Server discovery overrides (Optional). 6. Click Add to List. 7. Click Update. Enabling the Debug Mode When you encounter an issue and wish to report it to Sentry Software, you will be asked to enable the Debug Mode and provide the debug output to the Sentry Software support team. To enable the debug mode 1. Edit a EMC NetWorker KM monitor type: In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view Select a policy and click Edit In the Monitor Configuration tab, select EMC NetWorker KM monitor type and click Edit Configuring Monitor Settings 22

23 Editing the EMC NetW orker Monitoring Settings Configuring Monitor Settings 23

24 2. From the List - NetWorker Monitoring Settings, select the host or localhost 3. Click the Advanced button A dvanced Settings Configuring Monitor Settings 24

25 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/NSR/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/nsr/ and can be sent to the BMC Support for help. It is also recommended to check the NSR.log file, stored in <PATROL_HOME>/log, for any error. Configuring Monitor Settings 25

26 Configuring the Maximum Number of Instances By default, there is no limitation set for the available instances in BMC ProactiveNet Performance Management - EMC NetWorker Monitoring. To offer maximum performance, it is however recommended to set the maximum number of instances that will be displayed in the Console for each monitored elements. To configure the maximum number of instances: 1. Edit a EMC NetWorker KM monitor type: In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view Select a policy and click Edit In the Monitor Configuration tab, select an EMC NetWorker KM monitor type and click Edit Configuring Monitor Settings 26

27 Editing the EMC NetW orker Monitoring Settings Configuring Monitor Settings 27

28 2. From the List - NetWorker Monitoring Settings, select the host or localhost 3. Click the Advanced button A dvanced Settings Configuring Monitor Settings 28

29 4. Click the Instance Max button For each monitored element, indicate the maximum number of instances to be displayed Enter 0 in the relevant field to disable the monitoring of a specific element Click Close on all pop-ups Click Modify Selection in the main window and click Update. Configuring Monitor Settings 29

30 Configuring the Multi-Node Monitoring Mode If the EMC NetWorker environment is installed in a cluster using Veritas Cluster Server, Veritas Cluster File System, Oracle Solaris Cluster, or Microsoft Cluster, EMC NetWorker KM must be installed on all the cluster nodes to enable continuous monitoring and avoid single point of failure. To avoid duplicate alerts from multiple nodes, it is recommended to configure the solution to operate in multinode monitoring mode. To configure the multi-node monitoring mode 1. Edit a EMC NetWorker KM monitor type: In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view Select a policy and click Edit In the Monitor Configuration tab, select EMC NetWorker KM monitor type and click Edit Configuring Monitor Settings 30

31 Editing the EMC NetW orker KM Monitor Type Configuring Monitor Settings 31

32 2. From the List - NetWorker Monitoring Settings, select the host or localhost 3. Click the Advanced button A dvanced Settings Configuring Monitor Settings 32

33 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 Veritas Cluster File System. Then the EMC NetWorker KM will monitor the entire cluster from the active master system, which is identified by vxdctl -c mode command. This method requires vxconfigd in enable mode with its clustered state active. In the Monitoring Node Names field, name all the nodes where the solution is installed. The list must 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 active EMC NetWorker Server system or on the node where failover group is online and will not check the monitoring status of the other nodes through PATROL Agent: Check the Enable Remote PATROL Agent Checking box. Click the Remote Agent button Configuring Monitor Settings 33

34 Configuring the Remote 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 communicate with 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 7. Click Close on all pop-ups 8. Click Modify Selection in the main window and click Update. EMC NetWorker will then be monitored through the active or online node. The other nodes, which are standing by for a failover, will be in passive multi-node mode and only the local EMC NetWorker components will be monitored. If a managed node is unable to determine the system w hich should be in Active Multi-node Mode, it w ill change to Temporary Single-node Mode. Configuring Monitor Settings 34

35 Configuring the NetWorker Server Discovery Overrides (Optional) The solution automatically discovers the installation, binary, and library paths. This information can however be overridden. To configure NetWorker server discovery overrides 1. Edit an EMC NetWorker KM monitor type: In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view Select a policy and click Edit In the Monitor Configuration tab, select an EMC NetWorker KM monitor type and click Edit Configuring Monitor Settings 35

36 Editing the EMC NetW orker KM Monitor Type Configuring Monitor Settings 36

37 2. From the List - NetWorker Monitoring Settings, select the host or localhost 3. Click the Advanced button A dvanced Settings 4. In the NetWorker Server Discovery Overrides section, indicate: the NetWorker installation path the temporary directory path the node type the node status daemons 5. Click Close on all pop-ups 6. Click Modify Selection in the main window and click Update. Configuring Monitor Settings 37

38 Filtering Elements to Monitor By default, the solution monitors all the elements discovered, which may represent an important workload to the agents and the BPPM servers. Because the monitoring of some elements may be irrelevant 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: NetWorker Client, NetWorker Daemon, NetWorker Group, NetWorker Group Client, NetWorker Jukebox, NetWorker Jukebox Device, NetWorker Standalone Device, and NetWorker Volume Pool. To filter elements to monitor 1. Add or edit a monitor type 2. Select the Monitor Type for which you wish to apply filters. 3. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on EMC NetWorker Servers a hostname or IP address to apply these settings to a specific server 4. Indicate which elements will be monitored: Click the Filtering button In the Keep Only... section, indicate the regular expression for the element to be monitored and click Add to List In the Exclude... section, indicate the regular expression for 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. Configuring Pending Requests By default, the EMC NetWorker KM monitors all mount requests for 24 hours. This monitoring duration can however be modified to better suit your requirements. Increasing the monitoring duration may affect the performance of the application. To configure mount requests: Configuring Monitor Settings 38

39 1. Add or edit a monitor type and select NetWorker Pending Request as a Monitor Type. Configuring Pending Requests 2. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on EMC NetWorker servers a hostname or IP address to apply these settings to a specific server 3. In the Pending Request Configuration section, indicate how many hours the pending requests will be monitored 4. If the date/time format returned by EMC NetWorker commands is different from your local system 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 time format is the number of seconds that have elapsed since 00:00:00 GMT January 1, 1970 Year Formats YY Configuring Monitor Settings Two digit figure Example: 12 for the year

40 YYYY Four digit figure Example: 2012 Month Formats MO Two digit figure Example: 02 for February MONTH Month full name Example: February MON Three character name Example: Feb Date Formats DD Two digit figure Example: 05 Day Formats DAYFULL Day full name Example: Friday DAY Three character name Example: 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 displayed Example: 10:15:00pm P.M Time is in 12-hour format; a.m/p.m is displayed Example: 10:15:00p.m Indicate a PSL-compatible Time Zone String (e.g.: NZDT, NZST, EDT, EST, GMT-1200, etc.) 5. Click Add to List 6. Click Add. Configuring Monitor Settings 40

41 Configuring Groups To Configure Groups: 1. Add or edit a monitor type and select NetWorker Group as a Monitor Type. Configuring Groups 2. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on EMC NetWorker servers a hostname or IP address to apply these settings to a specific server Configuring Monitor Settings 41

42 3. Set the filtering options. Refer to Filtering Elements to Monitor for more details. 4. 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 the restriction window must at least last 5 minutes. 5. Click Add to list. 6. Click Add. Configuring Monitor Settings 42

43 Configuring Save Groups By default, the EMC NetWorker KM monitors all save groups that completed successfully for 24 hours and any other save groups for 72 hours. This monitoring duration can however be modified to better suit your requirements. Increasing the monitoring duration may affect the performance of the application. To configure save groups 1. Add or edit a monitor type and select NetWorker Save Group as a Monitor Type. Configuring Save Groups 2. In the Hostname field, enter: localhost to apply these settings to all PATROL Agents installed on the EMC NetWorker servers Configuring Monitor Settings 43

44 a hostname or IP address to apply these settings to a specific server In the Monitoring Duration section: Indicate how many hours the save groups in OK, Suspicious, and Failure status will be monitored Select Keep Monitoring Active Jobs Indefinitely if you prefer to endlessly monitor active save groups In the Monitored Save Clients dialog box, select the desired level of monitoring: : to disable the save clients monitoring feature Failed Only (default): to only monitor failed save clients Succeed Only: to only monitor successful save clients All: to monitor all the save clients. Click Add to list. Click Add. Configuring Thresholds When you are creating or editing a policy, you can add and configure monitor thresholds. The Add Thresholds dialog box presents threshold configuration fields for BMC ProactiveNet monitors that are configured through Central Monitoring Administration. For details about baselines and Key Performance Indicators (KPI), see BMC ProactiveNet Central Monitoring Administration or BMC ProactiveNet documentation or refer to the Managing Baselines and Key Performance Indicators section. For details about the monitored attributes, refer to the specific monitor type in the Reference Guide section. Before you begin Ensure that monitor configuration is complete before thresholds are applied. Thresholds cannot be applied to monitors that are not configured through Central Monitoring Administration. If you have not done so already, define general policy details. To add and configure monitor thresholds 1. Open the Add Policy dialog box. Click for steps: In the navigation pane of Central Monitoring Administration, click the Policies drawer and select a policy view. Click Add, or select an existing policy and click Edit. Configuring Monitor Settings 44

45 2. Select the Threshold Configuration tab and click Add. 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 or regular 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 the matched 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), enter Storage1 \(1\). 5. From the Attribute list, select a monitor attribute. In the Attribute list, some attributes are designated as key performance indicators (KPIs). Depending on the monitored environment and version, the list of KPIs might appear differently in the BMC ProactiveNet Operations Console. 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 Thresholds dialog 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 the Add button at the bottom of the window. To return the settings in the current window to default values, click the Reset button at the bottom of the window. The values on the current window are reset. Be sure to click the Add button to save the configuration on the Threshold Configuration tab. 9. When you finish configuration, click Close. The configuration details are displayed in the table on the Threshold Configuration tab. 10. When you finish configuring thresholds, click Save at the bottom of the Add Policy dialog box, or Update at the bottom of the Edit Policy dialog box. After you save or update the policy, new threshold configurations are pushed to BMC PATROL Agents with matching Central Monitoring Configuration tags. To edit a threshold configuration On the Threshold Configuration tab, select a threshold definition, and click Edit. Edit the configuration values and click Update. When you finish editing the threshold configuration, click Close. 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 with matching Central Monitoring Configuration tags. Configuring Thresholds 45

46 To delete a threshold configuration 1. 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 Agents with matching Central Monitoring Configuration tags. Recommended Thresholds Thresholds define acceptable high and/or low values for the data collected. Thresholds can be created as 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. Using BMC ProactiveNet Performance Management This section provides a brief overview of how to navigate and use the product in the BMC ProactiveNet Operations 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 Console The BMC ProactiveNet Operations Console is a Web-based application that provides options to navigate through BMC ProactiveNet and view all of the information collected and computed by the BMC ProactiveNet 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 folders are displayed hierarchically and are divided into the following categories, or nodes. Configuring Thresholds 46

47 Object Definition Global node The Global node contains the following default collectors: All Event Collectors displays the entire event collector hierarchy All Abnormalities displays all the abnormality events All Services displays all the services All Groups displays all the groups All Devices displays all the devices Based on permissions, users can create event and component folders under this node to organize the event view. My Folder node Based on permissions, users can create event and component folders under this node to organize the event view. To further organize your display, beneath these top-level folders you can add event and component folders, including folders for Component Instances (CIs) associated with a service model. Your ability to add event and component folders depends on your permissions. The severity icons for a collector dynamically change depending on the severity level of the events for that collector. 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 system immediately. 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 navigate through BMC ProactiveNet functions and views. You can select which drawers to display in the navigation 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 BMC ProactiveNet. 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 you create in the navigation tree. Find CI Provides a search mechanism so that you can search for Component Instances that meet the specified search criteria. Note: You must have permission to view this drawer. Using BMC ProactiveNet Performance Management 47

48 Event and component folders Event and component folders enable you to organize cells and collectors to make event displays meaningful for operators. For example, you might create an event folder for collectors that gather database warning events and allow only operators who are database administrators access to that event folder. You can drag components from one existing folder to another within the top-level folders in the navigation tree. You also can drag and drop CIs from the Tile or Graph view to an existing folder in the All Services folder. Event folders An event folder is a grouping of collectors that shows the relationship of events or abnormalities through the hierarchy of the navigation tree. Administrators define event folders and associate them with one or more collectors. Each level of the collector is shown as a node under the event folder. An event list is associated with the lowest level nodes of an event folder. The parent level of an event folder represents all of the events or abnormalities associated with the collectors. Event collectors Event collectors gather events for display in an event list to provide operators with meaningful groups of events or abnormalities and to show relationship through the hierarchy of the nodes in the navigation tree. 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 the navigation 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 or not. 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 the navigation 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 parent component folder. An event list is associated with the lowest level nodes of a component folder. The parent level of a component folder represents all of the events associated with the groups, services, or devices. Component folders are static or dynamic. You populate static component folders by selecting from a list of objects. You populate dynamic component folders by creating a query. Static folders always contain only the objects that you manually select. Dynamic folders contain the objects that match the 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 in the navigation tree. Each view is accessed by clicking the associated Console view icon. If a view is not available for the object that is selected in the navigation tree, the icon for that view is not displayed in the toolbar. Using BMC ProactiveNet Performance Management 48

49 View Description Event The Event view displays all events in an event list. This is the default view for all objects. Use the Event view to check the details of events and to address events that highlight incorrect state. Probable Cause Analysis can help you to identify the cause of the event. An event could be assigned to other users, who can acknowledge and take ownership of the event, fix the problem, and close the event. You can also address the incorrect condition by invoking remote actions, detailed diagnostics, and local actions. The Graph view helps check the impacting service and you can cross-launch to Impact Model Designer, Service Level 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 Title The Canvas view enables you to create a graphical representation of the components that are being monitored in your environment. The components are represented by objects that you can place on a background image. The objects can be graphics, such as images or connectors, or metrics information represented 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 of the 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 Group hyperbolic tree, the entire group hierarchy and devices are visible on a hyperbolic pane that is mapped to a circular 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 the configuration items in the service model and shows how those configuration items relate to each other. Use the 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 and other details of the selected object through hyperlinks to graphs, views, etc. You can display a Grid view for: Abnormalities Groups Devices For more detailed information, BMC ProactiveNet Getting Started Guide on the BMC Support website. Using BMC ProactiveNet Performance Management 49

50 Adding attributes to the graph Following configuration, only one attribute is enabled for the graph of each monitor. You might want to add 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 of measurement can be used. Viewing and manipulating attribute graphs The graph provides a visual display of the attributes of a monitor. Up to 12 attributes of a monitor can be displayed on a single graph In the BMC ProactiveNet Operations console, select the Navigation drawer. Select Global > Devices. Select the Grid view. All the monitored devices are displayed in table format. Select a device from the table. Select a monitor. 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 for this monitor. You can use the options available on this tab to manipulate the graph. For complete details, refer to BMC ProactiveNet User Guide on the BMC Support website. Using BMC ProactiveNet Performance Management 50

51 Viewing monitors for a device This section provides a brief overview of how to view the monitors for a selected device. For complete details, refer to BMC ProactiveNet User Guide on the BMC Support website. To view the Monitor types for a device In the BMC ProactiveNet Operations console, select the Navigation drawer. Select Global > Devices. Select the Grid view. All the monitored devices are displayed in table format. 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. 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 by several PATROL Agents Monitor Type Name of the monitor type. This will correspond to the element displayed in the Monitor Name column, specifying the type 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 thresholds You can adjust the thresholds for the attributes of a monitor type either globally or for a specific device instance. In the BMC ProactiveNet Operations console, select the Navigation drawer Select Select Select Select Select Global > Devices. the Grid view. All the monitored devices are displayed in table format. a device from the table. a monitor. 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 to the selected monitor instance. 6. Edit the Threshold settings 7. Click Apply. Using BMC ProactiveNet Performance Management 51

52 Managing Baselines and Key Performance Indicators In order to facilitate the detection of abnormalities on your monitored environment, BMC ProactiveNet calculates baselines per attributes based on values collected over a specified period of time to determine a normal operating range. When the collected values for these attributes are out of range, an alert is triggered. Some attributes are identified by default as Key Performance Indicators and therefore automatically included in the base lining calculation. Managing baselines The baseline is the expected normal operating range for a metric or attribute of a monitor. The baseline is calculated by collecting the values for a monitor s attributes and metrics over a specified time period and establishing a low baseline value (consisting of the 10th percentile of all the values for a given time period) and a high baseline value (consisting of the 90th percentile of all the values for a given time period), taking a weighted average of these values over time. A higher weight is given to the latest 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 threshold exists and is not suppressed. Additionally, if the Key Performance Indicator (KPI) mode is active, only those attributes that have an active abnormality threshold and are also KPI attributes will have baselines generated for them. Absolute thresholds (w ith "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 ProactiveNet Administration Console. In this KM, some attributes have been designated as important indicators of performance (KPIs). We do not recommend that these default settings are modified. However, advanced users may activate or deactivate KPIs from the BMC ProactiveNet Administration Console. Using BMC ProactiveNet Performance Management 52

53 To add or remove Key Performance Indicator (KPI) attributes for a monitor type 1. In the Administration Console, from the menu bar, choose Tools > KPI Administration. The KPI Administration dialog box is displayed. 2. From the Monitor Type list, choose the monitor type for which you want to add or remove KPI attributes. A list of attributes for the selected monitor type is displayed. 3. In the KPI column for the attributes that you want to add or remove as Key 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 monitor type For complete and detailed information on this procedure, please refer to the BMC ProactiveNet documentation available from BMC W eb site. Attributes considered as KPIs are respectively identified by the following icon:. Introduction This chapter provides statistical information about resources, operating status, and performances managed by the EMC NetWorker KM. It contains tables describing the attributes used in the KM, grouped by Monitor Types, and provides a brief description of each attribute and its default settings. Monitor Types EMC NetWorker KM NetWorker Client NetWorker Daemon NetWorker Database NetWorker Databases NetWorker Group NetWorker Group Client NetWorker Jukebox NetWorker Jukebox Device NetWorker Log NetWorker Pending Request NetWorker Save Client NetWorker Save Group NetWorker Save Groups NetWorker Standalone Device NetWorker Volume Pool Baselines and Key Performance Indicators Some attributes are identified by default as Key Performance Indicators (KPIs) and therefore Using BMC ProactiveNet Performance Management 53

54 automatically 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:. EMC NetWorker KM Attributes Name Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type Administrator Change Monitors any change in NetWorker administrator configuration between discovery cycles. 0 = No Change 1 = Changed -1 = Unknown Warning = 1 Availability Login Status Monitors the status of the NSR KM login details (username/password) for the operating system. 0 = Ok 1 = Suspicious 2 = Failure Warning = 1 Alarm = 2 Collection Status Monitor RAP Collects the status of the NetWorker RAP (Resource Allocation Protocol) monitor configuration. 0 = Enabled 1 = Disabled -1 = Unknown Availability Monitoring Mode Monitors the failover mode of EMC NetWorker KM for PATROL. 0 = Permanent Single-node Mode 1 = Temporary Single-node Mode 2 = Active Multi-node Mode 3 = Passive Multi-node Mode -1 = Unknown Collection Status Node Status Monitors error messages for the EMC NetWorker application on this managed system. 0 = Ok 1 = Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability 54

55 NetWorker Client Attributes Name Description Units Recommended Alert BMC Conditions ProactiveNet Attribute Type Index Record Count Displays the number of records found in the index database for this client. count Index Space Used Percent Displays the percentage of index space used by the client. % Index Space Used Displays the index space used by this client. KB State Displays the state of the client as reported in the command executed by the data collector. 0 = Running 1 = Not Running 2 = Client Down -1 = Unknown Availability Status Monitors the status of the client. 0 = Ok 1 = Suspicious 2 = Failure Warning = 1 Alarm =2 Availability For detailed information about KPI, see Managing Baselines and Key Performance Indicators. NetWorker Daemon Attributes Name Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type CPU Duration Displays the CPU seconds consumed by the daemon. seconds CPU Utilization Displays the percentage of CPU used by the daemon. % Memory Size Displays the core image size of the daemon in the virtual memory. KB Process Count Displays the number of daemon processes/threads found. processes State Displays the state of the daemon as reported in the command executed by the data collector. 0 = Running 1 = Sleeping 2 = Waiting 3 = Queued Availability EMC NetWorker KM 55

56 4= Intermediate 5= Terminated 6 = Stopped/ Disabled 7 = Growing 8= xistent/ Not Responding 9 = Not Running -1 = Unknown Status Monitors the status of the daemon. For detailed information about 0 = Ok 1 = Suspicious 2 = Failure Availability KPI, see Managing Baselines and Key Performance Indicators. NetWorker Database Attributes Name Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type Filesystem Space Used Percent Monitors the percentage of space used by the file system where the database resides. % Alarm if out of [0-100] range Warning: Alarm: Space Available Monitors the amount of assigned space remaining available for use by the index database. MB Warning: 2-5 Alarm 2 Availability Space Growth Rate Displays the growth rate of the space used by the index database. MB/s Space Used Percent Monitors the percentage of assigned space used by the index database. % Alarm if out of [0-100] range Warning: Alarm: Space Used Displays the amount of assigned space used by the index database. MB For detailed information about NetWorker Daemon KPI, see Managing Baselines and Key Performance Indicators. 56

57 NetWorker Databases Attributes Name Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type Backup Elapsed Displays the elapsed time since the last successful database backup. hours Retention Displays the number of days data will be retained by the database. days n/a For detailed information about KPI, see Managing Baselines and Key Performance Indicators. NetWorker Group Attributes Name Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type Backup Elapsed Displays the elapsed time since the last backup for this group, regardless of the backup completion status. hours Backup Throughput Displays the last backup throughput for this group. GB/s Full Backup Duration Displays the duration of the last successful full backup for this group. seconds Full Backup Elapsed Displays the time elapsed since the last successful full backup for this group. hours Full Backup File Count Displays the number of files backed up in the last successful full backup for this group. count Full Backup Size Displays the size of the last successful full backup for this group. GB Incremental Backup Duration Displays the duration of the last successful incremental backup for this group. seconds NetWorker Databases 57

58 Incremental Backup Elapsed Displays the elapsed time since the last successful incremental backup for this group. hours Incremental Backup File Count Displays the number of files backed up in the last successful incremental backup for this group. count Incremental Backup Size Displays the size of the last successful incremental backup for this group. GB State Displays the state of the group. 0 = Idle 1 = Running 2 = Running in Restricted Window 3 = Cloning -1 = Unknown Availability Status Monitors the status of the group. 0 = Ok 1 = Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability Successful Backup Elapsed Displays the time elapsed since the last successful backup for this group. hours For detailed information about KPI, see Managing Baselines and Key Performance Indicators. NetWorker Group Client Attributes Name Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type Backup Throughput Displays the last backup throughput for this group client. MB/s Last Full Backup Duration Displays the duration of the last successful full backup for this group client. seconds Last Full Backup File Count Displays the number of files backed up in the last successful full backup for this group client. count Last Full Backup Size Displays the size of the last successful full backup for this group client. MB Last Incremental Backup Duration Displays the duration of the last successful incremental backup for this group client. seconds NetWorker Group 58

59 Last Incremental Backup File Count Displays the number of files backed up in the last successful incremental backup for this group client. count Last Incremental Backup Size Displays the size of the last successful incremental backup for this group client. MB For detailed information about KPI, see Managing Baselines and Key Performance Indicators. NetWorker Jukebox Attributes Name Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type Auto Media Management State Displays the state of the jukebox auto media management configuration. 0 = Yes 1 = No -1 = Unknown Availability Auto Media Management Status Monitors the status of the jukebox auto media management configuration. 0 = Ok 1 = Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability Cleaning Left Count Displays the number of uses left on the cleaning tape loaded in this jukebox. count Warning = - 1 State Displays the jukebox state, which is derived from the jukebox resource. It will not perform any remote jukebox test command on the storage node. 0 = Running 1 = Event Found 2 = Service Mode 3 = No Enabled Jukebox Devices 4 = Error -1 = Unknown Availability Status Monitors the status of the jukebox. 0 = Ok 1 = Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability Throughput Displays the total throughput of each jukebox device during the last backup save groups. MB/s Up Drive Count Displays the number up / online state drives in this robotic library. count NetWorker Group Client 59

60 Volume Assigned Count Displays the number of assigned volume loaded in this jukebox. (Assigned volumes are registered tape volumes assigned to a volume pool.) count Volume Count Displays the total number of volumes loaded in this jukebox. count Volume Empty Count Displays the number of empty volumes loaded in this jukebox. (Empty volume are tape volumes with 0% used space.) count Volume Empty Percent Monitors the percentage of empty volumes against the total number of volumes loaded in this jukebox. % Alarm if out of [0-100] range Warning: 2-5 Alarm: 0-2 For detailed information about KPI, see Managing Baselines and Key Performance Indicators. NetWorker Jukebox Device Attributes Name Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type Session Count Displays the number of sessions configured for the jukebox device. sessions Session Maximum Displays the maximum number of sessions configured for the jukebox device. sessions Session Target Displays the number of target sessions configured for the jukebox device. sessions State Displays the state of the jukebox device. This is determined from the jukebox device control information. 0 = Idle 1 = Mounted 2 = Verify Label 3 = Label 4 = Eject 5 = Read 6 = Setting Up for Writing 7 = Write 8 = Cleaning Required 9 = Service Mode 10 = Error 11 = Disabled 12 = Failure -1 = Unknown Availability NetWorker Jukebox 60

61 Status Monitors the status of the jukebox device. 0 = Ok 1= Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability Throughput Displays the throughput of the jukebox device during the last save group. MB/s For detailed information about KPI, see Managing Baselines and Key Performance Indicators. NetWorker Log Attributes Name Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type Alarm Message Count Monitors the number of alarm messages. count Alarm if out of [0-100] range Alarm when 1 File Space Growth Rate Displays the growth rate of the amount of space used by the log file. KB/s File Space Used Displays the amount of space used by the log file. KB/s Filesystem Space Used Percent Monitors the percentage of space used by the file system (where the log file resides). % Alarm if out of [0-100] range Warning = Alarm = Rendered Monitors whether raw log files are rendered in runtime. 0 = Yes 1 = No -1 = Unknown Warning if out of [0-1] range Warning = 1 Availability Note: This parameter is only available for NetW orker raw log files. Space Available Monitors the available space to be used for the log file. It also corresponds to the space available on the file system. MB Warning = 2-5 Alarm 2 Availability Space Used Percent Monitors the percentage of capacity used by the log file. % Alarm if out of [0-100] range Warning = Alarm = Warning Message Count Monitors the number of warning messages. count Alarm if out of [0-100] range Warning: For detailed information about NetWorker Jukebox Device KPI, see Managing Baselines and Key Performance Indicators. 61

62 NetWorker Pending Request Attributes Name Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type Elapsed Displays the elapsed time since the pending request was issued. minutes State Displays the state of the pending request as reported in the command executed by the data collector. 0 = Completed 1 = Pending -1 = Unknown Availability Status Monitors the status of the pending request. 0 = Ok 1 = Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability For detailed information about KPI, see Managing Baselines and Key Performance Indicators. NetWorker Save Client Attributes Name Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type State Displays the state of the save client. 0= Succeeded 1 = Failed -1 = Unknown Availability Status Monitors the status of the save client. 0 = Ok 1= Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability For detailed information about NetWorker Pending Request KPI, see Managing Baselines and Key Performance Indicators. 62

63 NetWorker Save Group Attributes Name Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type Duration Displays the duration of the save group from the start. seconds File Count Displays the number of files backed up for this save group. count Save Set Count Displays the total number of save sets in this save group. count Save Set Failed Count Displays the number of count failed save sets in this save group. Save Set Pending Count Displays the number of pending save sets in this save group. count Save Set Succeeded Count Displays the number of succeeded save sets in this save group. count Size Displays the amount of data backed up for the save group. MB State Displays the state of the save group. This is determined using the save group completion state and the number of pending, succeeded & failed save sets. 0 = Completed 1 = In Progress 2= Completed/ Errors 3 = In Progress/ Errors 4 = Aborted 5 = Failed -1 = Unknown Availability Status Monitors the status of the save group. 0 = Ok 1 = Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability Throughput Displays the throughput of this save group. MB/s For detailed information about NetWorker Save Client KPI, see Managing Baselines and Key Performance Indicators. 63

64 NetWorker Save Groups Attributes Name Description Units Recommended Alert Conditions BMC ProactiveNet Attribute Type Active Backup Count Displays the number of active backup jobs currently discovered and monitored. count Active Count Displays the number of active jobs currently discovered and monitored. count Active Non-Backup Count Displays the number of active jobs currently discovered and monitored. count Manual Saves Displays whether the manual saves are enabled or disabled. 0 = Enabled 1 = Disabled -1 = Unknown Availability For detailed information about KPI, see Managing Baselines and Key Performance Indicators. NetWorker Standalone Device Attributes Name Description Session Count Recommended Alert Conditions BMC ProactiveNet Attribute Type Displays the number of sessions sessions configured for the device. Session Maximum Displays the maximum number of sessions configured for the device. sessions Session Target Displays the number of target sessions configured for the device. sessions State Displays the state of the standalone device. 0 = Idle 1 = Mounted 2 = Verify Label 3 = Label 4 = Eject 5 = Read 6 = Setting Up for Writing 7 = Write 8 = Cleaning Required Availability NetWorker Save Groups Units 64

65 9 = Service Mode 10 = Error 11 = Disabled 12 = Failure -1 = Unknown Status Monitors the status of the standalone device. Throughput Displays the throughput of the standalone device during the last save group. For detailed information about 0 = Ok 1 = Suspicious 2 = Failure Warning = 1 Alarm = 2 Availability KPI, see Managing Baselines and Key Performance Indicators. NetWorker Volume Pool Attributes Name Description Units Recommended Alert BMC ProactiveNet Conditions Attribute Type Space Available Monitors the available volume space for the backup data to use in this volume pool. If this parameter changes to warning or alarm state, the recovery action will trigger an event. GB Availability Space Growth Rate Displays the growth rate of the total volume space used by the backup data in this volume pool. GB/s Space Used Displays the total volume space occupied by the backup data in this volume pool. GB Space Used Percent Monitors the percentage of total occupied volume space against the total volume capacity of this volume pool (not including any scratch volume). % Alarm if out of [0-100] range Warning: Alarm: Volume Active Count Displays the number of active volumes in this volume pool. (Active volumes are available tape volumes where data can be written without any intervention.) count NetWorker Standalone Device 65

66 Volume Active Percent Monitors the percentage of active volumes against the total number of volumes in this volume pool % Alarm if out of [0-100] range Warning: 2-5 Alarm: 0-2 Volume Available Count Displays the number of volumes assigned to this volume pool. count Volume Available Percent Monitors the percentage of available volumes against the total number of volumes in this volume pool. % Alarm if out of [0-100] range Warning: 2-5 Alarm: 0-2 Volume Count Displays the total number of volumes in this volume pool. count Volume Empty Count Displays the number of empty volumes in this volume pool. (Empty volumes are available tape volumes with no data stored on them.) count Volume Full Count Displays the number of full volumes in this volume pool. ("Full" is a possible status for a tape volume.) count Volume Full Percent Monitors the percentage % of full volumes against the total number of volumes in this volume pool. Alarm if out of [0-100] range Warning: Alarm: Volume Manual Recycle Count Displays the number of volumes in this volume pool, which require manual recycling. ("Manually-recyclable" volume is a possible volume state set on tape volumes.) count Volume Read Only Count Displays the number of read only volumes in this volume pool. ("Read Only" is a possible volume flag set on tape volumes.) count For detailed information about NetWorker Volume Pool KPI, see Managing Baselines and Key Performance Indicators. 66

67 Index -A Abnormalities Access 52 Permissions 7 User 7 Add Monitor Types 18 Attribute 50 Attributes Active Backup Count 64 Active Count 64 Active Non-Backup Count 64 Administrator Change 54 Alarm Message Count 61 Auto Media Management State 59 Auto Media Management Status 59 Backup Elapsed 57 Backup Throughput 57, 58 Cleaning Left Count 59 CPU Duration 55 CPU Utilization 55 Duration 63 Elapsed 62 File Count 63 File Space Growth Rate 61 File Space Used 61 Filesystem Space Used Percent 56, 61 Full Backup Duration 57 Full Backup Elapsed 57 Full Backup File Count 57 Full Backup Size 57 Incremental Backup Duration 57 Incremental Backup Elapsed 57 Incremental Backup File Count 57 Incremental Backup Size 57 Index Record Count 55 Index Space Used 55 Index Space Used Percent 55 Last Full Backup Duration 58 Last Full Backup File Count 58 Last Full Backup Size 58 Last Incremental Backup Duration 58 Last Incremental Backup File Count 58 Index Last Incremental Backup Size 58 Login Status 54 Manual Saves 64 Memory Size 55 Monitor RAP 54 Monitoring Mode 54 Node Status 54 Process Count 55 Rendered 61 Retention 57 Save Set Count 63 Save Set Failed Count 63 Save Set Pending Count 63 Save Set Succeeded Count 63 Session Count 60, 64 Session Maximum 60, 64 Session Target 60, 64 Size 63 Space Available 56, 61, 65 Space Growth Rate 56, 65 Space Used 56, 65 Space Used Percent 56, 61, 65 State 55, 57, 59, 60, 62, 63, 64 Status 55, 57, 59, 60, 62, 63, 64 Successful Backup Elapsed 57 Throughput 59, 60, 63, 64 Up Drive Count 59 Volume Active Count 65 Volume Active Percent 65 Volume Assigned Count 59 Volume Available Count 65 Volume Available Percent 65 Volume Count 59, 65 Volume Empty Count 59, 65 Volume Empty Percent 59 Volume Full Count 65 Volume Full Percent 65 Volume Manual Recycle Count 65 Volume Read Only Count 65 Warning Message Count 61 Automated Drives Debug 22 Automated Libraries Debug 22 -BBaseline 67 53

68 Baselines BMC ProactiveNet Performance Management 52 Generation 52 Manage 52 Requirements 52 BMC PATROL Changes 6 BMC ProactiveNet Performance Management Abnormalities 52 Baselines 52 Key Performance Indicators 52 KPI 52 Business Value 5 Domains 22 End Time 22 Jobs 22 Logs 22 Mount Requests 22 Processes 22 Server 22 Storage Pools 22 Domains Debug 22 Downloading 15 Duration Duration 38 Monitoring 38 -C- -E- Clients Debug 22 Cluster Application Component Event collectors 46 folders F- folders 46 Component Installation package creating 12 downloading 15 editing 14 Configure Groups 41 Maximum Instances 26 Multi-node monitoring mode Overrides 35 Pending equest 38 Configuring monitor settings 18 -DDaemons Debug Databases TSM Automated Drive 38 TSM Automated Library 38 TSM Client 38 TSM Daemon 38 TSM Domain 38 TSM Domain Client Node 38 TSM Manual Drive 38 TSM Storage Pool Debug 22 Debug Automated Drives 22 Automated Libraries 22 Clients 22 Daemons 22 Databases 22 Directory Path 22 Index 30 Failover Group Name 30 Features 5 Filtering Options TSM Automated Drive 38 TSM Automated Library 38 TSM Client 38 TSM Daemon 38 TSM Domain 38 TSM Domain Client Node 38 TSM Manual Drive 38 TSM Storage Pool 38 Filters -GGenerate 68

69 Generate Baselines Goals 5 Graphs 50 Groups Configure -L- 52 Logs Debug 41 -M- -I- Manage Baselines 52 Key Performance Indicators KPI 52 Monitor name 51 type 51 Monitor Settings Information Closed 51 Enabled 51 Open 51 Source Agent 51 Installation 11 configuring 16 Installing Preparation 11 Instances Client 26 Daemon 26 Database 26 Group 26 Group Client 26 Jukebox 26 Jukebox Device 26 Log 26 Pending Request 26 Save Group 26 Standalone Device 26 Volume Pool 26 Jobs 22 EMC NetWorker KM 53 NetWorker Client 53 NetWorker Daemon 53 NetWorker Database 53 NetWorker Databases 53 NetWorker Group 53 NetWorker Group Client 53 NetWorker Jukebox 53 NetWorker Jukebox Device 53 NetWorker Log 53 NetWorker Pending Request 53 NetWorker Save Client 53 NetWorker Save Group 53 -KKey Concepts 4 Key Performance Indicators 53 BMC ProactiveNet Performance Management 52 Manage 52 KPI 53 BMC ProactiveNet Performance Management 52 Manage 52 Index 52 configuring 18 Monitor Type EMC NetWorker KM 54 NetWorker Client 55 NetWorker Daemon 55 NetWorker Database 56 NetWorker Databases 57 NetWorker Group 57 NetWorker Group Client 58 NetWorker Jukebox 59 NetWorker Jukebox Device 60 NetWorker Log 61 NetWorker Pending Request 62 NetWorker Save Client 62 NetWorker Save Group 63 NetWorker Save Groups 64 NetWorker Standalone Device 64 NetWorker Volume Pool 65 Monitor Types -JDebug 22 69

70 Monitor Types NetWorker Save Groups 53 NetWorker Volume Pool 53 Monitoring Configure 38 Duration 38 Monitoring Node Names 30 Mount Request Configure 38 Monitoring Duration 38 Mount Requests Software 6 System 6 -SSecurity Requirements Server Debug Software Debug 22 Sudo 7, 20 System Requirements -Ndrawers 46 tree 46 Operations Console views Changes 6 TSM Server Discovery Overrides 35 -UUNIX 20 User Account 35 Configure 20 patrol 20 Privileges 20 Sudo 20 -PPackage 12, 14, 15 PATROL Configuration Manager Policies Debug 10 -W - 17 Windows 22 -RReference Guide 53 Remote PATROL Agent Checking Requirements Security 7 Index 6 Tags 10 Thresholds modifications 51 Tivoli Storage Manager -O- Manage Processes 6 -T- Navigation Event 46 Grid 46 Title 46 Tree/Graph 46 Overrides Configure 35 TSM Server Discovery 22 Requirements Storage Pools Debug 22 Multi-node monitoring mode Configure

71 About BMC Software BMC Software, Inc. NYSE:BMC, is a leading provider of enterprise management solutions that empower companies to manage their IT infrastructure from a business perspective. Delivering Business Service Management, BMC Software solutions span enterprise systems, applications, databases, and service management. Founded in 1980, BMC Software has offices worldwide and fiscal 2004 revenues of more than $1.4 billion. For more information about BMC Software, visit About Sentry Software Sentry Software, a strategic Technology Alliance Partner of BMC Software, provides key monitoring solutions specifically designed to expand the capabilities of BMC Performance Manager, thus enabling up to 100% coverage of any infrastructure. Sentry Software specializes in single solutions for multi-platform monitoring of hardware, custom applications or any IT component, and blackout windows. Sentry Software products are deployed in 45 countries across the globe and lead the list of BMC Software s third-party product sales. For more information about Sentry Software, please visit