Microsoft System Center Operations Manager 2007 Management Pack Guide for Veritas NetBackup™

Copyright © 2008 Symantec Corporation. All rights reserved.

Symantec, the Symantec Logo, and NetBackup Operations Manager are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

Portions of this software are derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm. Copyright 1991-92, RSA Data Security, Inc. Created 1991. All rights reserved.

The product described in this document is distributed under licenses restricting its use,copying, distribution, and decompilation/reverse engineering. No part of this documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THIS DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID, SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be “commercial computer software” and “commercial computer software documentation” as defined in FAR Sections 12.212 and DFARS Section 227.7202.

Symantec Corporation20330 Stevens Creek Blvd.Cupertino, CA 95014www.symantec.com

Printed in the United States of America.

Third-party legal notices

Third-party software may be recommended, distributed, embedded, or bundled with this Symantec product. Such third-party software is licensed separately by its copyright holder. All third-party copyrights that are associated with this product are listed in the accompanying release notes.Windows is a registered trademark of Microsoft Corporation.

Licensing and registration

Veritas NetBackup is a licensed product. See the NetBackup Installation Guide for license installation instructions.

Technical support

For technical assistance, visit http://entsupport.symantec.com and select phone or email support. Use the Knowledge Base search feature to access resources such as TechNotes, product alerts, software downloads, hardware compatibility lists, and our customer email notification service

4

Contents

Chapter 1 Introducing Microsoft System Center Operations Manager Management Pack for Veritas NetBackup

Chapter 2 Integrating NOM and SCOM 2007Prerequisites for NOM and SCOM integration ................................................10Installing and configuring SNMP and WMI SNMP provider ........................10Compiling MicrosoftOperationsManager.mib file and the NOM MIB files into

WMI format ..................................................................................................11Deploying the SCOM Management Pack for NetBackup ...............................12Configuring NetBackup Operations Manager .................................................16Viewing NetBackup alerts in SCOM 2007 ........................................................17

Chapter 3 NetBackup AlertsAlert Severity Mapping between NOM and SCOM .........................................19Alert Conditions in NOM 6.5 and 6.5.x .............................................................20Alert Conditions in NOM 6.0 and 6.0 MPx .......................................................22

6 Contents

Introducing Microsoft System Center Operations Manager Management Pack for Veritas NetBackup

Microsoft System Center Operations Manager Management Pack for Veritas NetBackup lets you monitor and manage NetBackup alerts using Microsoft System Center Operations Manager 2007 (SCOM). By detecting and alerting you on critical conditions, this Management Pack helps prevent possible service outages.

For information about NetBackup alerts, see “Alert Conditions in NOM 6.5 and 6.5.x” on page 20 and “Alert Conditions in NOM 6.0 and 6.0 MPx” on page 22.

This document discusses how you can deploy and configure the SCOM Management Pack for NetBackup into your existing SCOM 2007 environment. Currently, NetBackup Operations Manager (NOM), a management solution shipped with NetBackup, can generate and monitor NetBackup alerts. By deploying the SCOM Management Pack for NetBackup and integrating NOM and SCOM, SCOM can receive the SNMP trap alerts that have been configured in NOM. As a result, SCOM can be used for the centralized management of NetBackup alerts.

Note: The term SCOM in this document refers specifically to SCOM 2007.

1Chapter

8 Introducing Microsoft System Center Operations Manager Management Pack for Veritas NetBackup

Note: The term NetBackup alerts used in this document means alerts about NetBackup. It does not mean that these alerts are generated by NetBackup.

Integrating NOM and SCOM 2007

This chapter describes how you can integrate NOM and SCOM to be able to receive NetBackup alerts using SCOM 2007.

Table 2-1 on page 9 describes the sequence of steps to be followed for integrating NOM and SCOM.

Table 2-1 Sequence of steps for integrating NOM and SCOM

Step Description See this Topic

1 Check the list of prerequisites for NOM and SCOM integration.

“Prerequisites for NOM and SCOM integration” on page 10.

2 Install SNMP and WMI SNMP provider on the SCOM server.

“Installing and configuring SNMP and WMI SNMP provider” on page 10.

3 Compile MicrosoftOperationsMana

ger.mib file and the three NOM MIB files into WMI format.

“Compiling MicrosoftOperationsManager.mib file and the NOM MIB files into WMI format” on page 11.

4 Deploy the SCOM Management Pack for NetBackup.

“Deploying the SCOM Management Pack for NetBackup” on page 12.

5 Configure NetBackup Operations Manager.

“Configuring NetBackup Operations Manager” on page 16.

6 View NetBackup alerts in SCOM 2007.

“Viewing NetBackup alerts in SCOM 2007” on page 17.

Chapter 2

10 Integrating NOM and SCOM 2007Prerequisites for NOM and SCOM integration

Prerequisites for NOM and SCOM integrationThe prerequisites for NOM and SCOM integration include the following:

■ SCOM 2007 must be installed on the host machine where SNMP traps are received. In addition, SCOM 2007 Service Pack 1 (final RTM version) must be installed.

■ The managed NetBackup servers must be on NetBackup 6.0 or above.

■ SCOM 2007 agent must be installed on the NOM server and configured to be managed by the SCOM server.

■ SNMP Service must be installed on the host machine where SCOM server is running. The service can be installed from a Windows installation CD.

■ SNMP Service must be installed on the host machine where NOM server is running. The service can be installed from a Windows installation CD.

■ SCOM Management Pack for NetBackup must be downloaded and deployed on the SCOM server.

■ SCOM server must have the rights to access WMI database or SCOM 2007 agent when NOM server is running.

Installing and configuring SNMP and WMI SNMP provider

Use the following steps to install and configure the SNMP service and the WMI SNMP provider on the SCOM server and the NOM server:

1 Ensure that the SNMP service is installed and running on the SCOM server. To install the SNMP provider, perform the following steps:

a From the Control Panel, select Add or Remove Programs.

b In the Add/Remove dialog box, select Add/Remove Windows components from the left pane.

c Select Management and Monitoring Tools, and then click Details.

d Select Simple Network Management Protocol and WMI SNMP Provider, and click OK.

e Follow the steps in the wizard to complete the installation.

2 Configure the SNMP service on the SCOM server so that the SCOM server is able to receive SNMP traps.

To configure the SNMP service, perform the following steps:

a Right click the My Computer icon, and then click Manage.

11Integrating NOM and SCOM 2007Compiling MicrosoftOperationsManager.mib file and the NOM MIB files into WMI format

b In the Computer Management console tree, expand the Services and Applications node, and then click Services.

c In the details pane, right-click SNMP Service, and then click Properties.

d In the Properties dialog box, on the General tab, set the Startup type to Automatic.

e In the Properties dialog box, on the Traps tab, add public as the Community name. Also add localhost as the trap destination.

f In the Properties dialog box, on the Security tab, add the Community Name public with rights READ CREATE to Accepted Community names.

g In the Properties dialog box, on the Security tab, select Accept SNMP packet from any host.

3 Configure the SNMP service on the NOM server.

To configure the SNMP service, perform the following steps:

a Right click the My Computer icon, and then click Manage.

b In the Computer Management console tree, expand the Services and Applications node, and then click Services.

c In the details pane, right-click SNMP Service, and then click Properties.

d In the Properties dialog box, on the Security tab, select Accept SNMP packets from these hosts.

e In the Properties dialog box, on the Security tab, click Add (located at the bottom of the dialog box) to add the IP address of the SCOM server.

Compiling MicrosoftOperationsManager.mib file and the NOM MIB files into WMI format

In order to capture and display NOM generated SNMP traps with WMI, you must first compile the MicrosoftOperationsManager.mib file using the SNMP information module compiler(smi2smir) utility.

Note: MicrosoftOperationsManager.mib is available in the Tools directory of the MOM 2005 SDK.

After this, the NOM MIB’s need to be compiled into Windows Management Instrumentation (WMI) format so that SCOM can read them. The MIB files can be compiled using the smi2smir utility. This utility loads the MIB information into WMI and is located in C:\WINDOWS\system32\wbem\snmp directory.

12 Integrating NOM and SCOM 2007Deploying the SCOM Management Pack for NetBackup

Note: Three MIB files namely VERITAS-REG.mib, VERITAS-TC.mib, and VRTS-cca.mib have been shipped with the SCOM Management Pack for NetBackup.

To compile MicrosoftOperationsManager.mib file

1 Set the value of the PATH variable by using the following command:SET PATH=C:\WINDOWS\system32\wbem\snmp;%PATH%

2 Copy the MIB file to a folder on the SCOM agent and compile the MIB file using the /sa and /t options.smi2smir.exe /sa /t MicrosoftOperationsManager.mib

To compile the NOM MIB files into WMI format

1 Navigate to the directory where the MIB’s have been extracted.

2 Set the value of the PATH variable by using the following command:SET PATH=C:\WINDOWS\system32\wbem\snmp;%PATH%

3 Use the smi2smir.exe utility to compile the three MIB files for NOM. The compiler runs in the command-line mode, using one MIB file as input. Use the following command to compile the files:smi2smir.exe /sa /t <MIB FILE>

4 The compiled modules can be verified using the following command:smi2smir.exe /l

This command lists all the compiled modules in the WMI. On running this command, the following modules (or more) must be displayed:Smi2smir: modules in the SMIR:"MISSION_CRITICAL_MIB""VERITAS_REG""RFC1213_MIB"

Deploying the SCOM Management Pack for NetBackup

Before you can use SCOM 2007 to receive and display NetBackup alerts, you must first download and deploy the SCOM Management Pack for NetBackup.

The following procedures describe how to discover network devices on the SCOM server and deploy the SCOM Management Pack for NetBackup.

After following these procedures, the SCOM server is configured as an SNMP trap receiver.

13Integrating NOM and SCOM 2007Deploying the SCOM Management Pack for NetBackup

Note: You must be logged on as a member of the SCOM Administrators group to perform these procedures.

To discover network devices on the SCOM server

1 Launch the SCOM Operations Console. Select Start > Programs > System Center Operations Manager 2007 > Operations Console.

2 In the Operations Console, click the Administration button.

3 In the Administration pane, expand Administration and then expand Device Management.

4 Right-click on Network Devices and then click Discovery Wizard. The Discovery wizard helps you to identify SNMP-enabled devices on the SCOM server.

5 In the Computer and Device Management Wizard, on the Introduction page, click Next.

The Introduction page does not appear if the Computer and Device Management Wizard has been run before and Don't show this page again was selected.

14 Integrating NOM and SCOM 2007Deploying the SCOM Management Pack for NetBackup

6 On the Auto or Advanced? page, do the following:

a Select Advanced discovery.

b In the Computer & Device Types list, select Network Devices.

c Click Next.

7 On the Discovery Method page, enter the IP address of the NOM server in both Start and End fields, and then click Discover. The Discovery Progress page is displayed.

15Integrating NOM and SCOM 2007Deploying the SCOM Management Pack for NetBackup

8 On the Select Objects to Manage page, select the IP address obtained as discovery result (IP address of the SCOM server), and then click Next.

9 On the Summary page, click Finish.

To deploy SCOM Management Pack on the SCOM server

1 Launch the SCOM 2007 Operations Console.

16 Integrating NOM and SCOM 2007Configuring NetBackup Operations Manager

2 In the Operations Console, click the Administration button.

3 Right-click the Management Packs node and then click Import Management Pack(s).

4 In the Select Management Pack(s) to import dialog box, browse to the directory where the SCOM Management Pack is saved. Select NetBackup.Operations.Manager.xml and click Open.

Note: NetBackup.Operations.Manager.xml is shipped with the SCOM Management Pack for NetBackup.

5 In the Import Management Packs dialog box, which displays the Management Pack that you selected, click the Import button.

6 After the import process is complete, and the dialog box displays an icon next to each Management Pack indicating success or failure of the importation, click the Close button.

7 You must restart the SCOM server after importing this Management Pack.

Note: SCOM 2007 will not be able to monitor NetBackup alerts if you do not restart your SCOM server after importing the Management Pack.

Configuring NetBackup Operations ManagerYou must configure NOM to send SNMP traps to the desired SCOM agent. A SCOM Administrator can thus monitor and manage all NetBackup alerts that are configured in NOM to be sent to the SCOM server as SNMP traps.

To configure NetBackup Operations Manager

1 Log on to the NOM console as an Administrator.

2 Select Settings > Recipients > SNMP.

3 In the Tasks pane, click Create Recipients. Enter the details to create an SNMP trap recipient and click OK.

4 Select Managing > Alert Policies > Details.

5 In the Tasks pane, click New Alert Policy. Enter the details to create an alert policy that generates an SNMP trap.

6 Select an alert condition for this policy. For many alert conditions, you may need to enter threshold parameters and other required or optional parameters.

7 Enter a name and description for the alert policy. The name must be unique.

17Integrating NOM and SCOM 2007Viewing NetBackup alerts in SCOM 2007

8 Specify any email recipients if required. Click Save and Next to continue further.

9 Select a Recipient for Trap notifications and click Finish.

The alert policy is created. When the selection criteria for this policy are met, an SNMP trap is generated for the recipient, which can be received and displayed in the SCOM Operations Console on clicking the Monitoring button.

Note: See the NOM online help for more information on configuring NOM. You can access the context-sensitive help while using NOM, by clicking Help on the title bar.

Viewing NetBackup alerts in SCOM 2007Netbackup alerts can be viewed from the Monitoring pane in the Operations Console of SCOM 2007.

Use the following procedure to view NetBackup alerts in SCOM 2007.

To view NetBackup alerts in SCOM 2007

1 Launch the SCOM Operations console.

Select Start > Programs > System Center Operations Manager 2007 >

Operations Console.

2 In the Operations Console, click on Monitoring button.

3 In the Monitoring pane, expand NetBackup Views, and click Alerts View.

Figure 2-1 shows the Alerts View.

18 Integrating NOM and SCOM 2007Viewing NetBackup alerts in SCOM 2007

Figure 2-1 NetBackup alerts in SCOM 2007

NetBackup alerts

NetBackup Alerts

This chapter lists the NetBackup alerts that you can view using SCOM. By integrating NOM and SCOM as per the instructions in Chapter 2, “Integrating NOM and SCOM 2007”, SCOM can receive the SNMP trap alerts that have been configured in NOM. The alerts that you receive using SCOM depend on whether you have installed NOM 6.0 and 6.0 MPx or NOM 6.5 and 6.5.x.

If you have NOM 6.5 or 6.5.x, see Table 3-2 on page 20 to view the list of available alerts. In case you have NOM 6.0 or 6.0 MPx, see Table 3-3 on page 22 to view the list of available alerts.

Alert Severity Mapping between NOM and SCOMTo get alerts in NOM, you can create an alert policy based on a set of pre-defined alert conditions. While creating an alert policy, you need to select the alert condition and specify the alert severity. Based on the alert severity, the alert is displayed in the selected alert category in NOM.

Note: See NetBackup Operations Manager Guide or the NOM online help for more details on creating an alert policy.

The following alert severities are present in NOM:

■ Critical

■ Major

■ Informational

■ Warning

Chapter 3

20 NetBackup AlertsAlert Conditions in NOM 6.5 and 6.5.x

Table 3-1 on page 20 lists the alert severity in NOM and the corresponding alert severity depicted in SCOM.

Alert Conditions in NOM 6.5 and 6.5.xTable 3-2 on page 20 lists the alert conditions available in NOM 6.5 and 6.5.x (server context only).

Table 3-1 Alert Severity Mapping between NOM and SCOM

Alert Severity in NOM Alert Severity in SCOM

Critical Critical

Major Error

Informational Information

Warning Warning

Table 3-2 Alert Conditions in NOM 6.5 and 6.5.x

Serial Number Alert Condition

1. Catalog Backup Disabled

2. Catalog not Backed up

3. Catalog Space low

4. Disk Volume Down

5. Disk Volume Full

6. Drive is Down

7. Exceeded Max Media Mounts

8. Frozen Media

9. High Down Drives

10. High Frozen Media

11. High Job Failure Rate

12. High Suspended Media

13. Hung Job

14. Job Finalized

15. Job Policy Change

21NetBackup AlertsAlert Conditions in NOM 6.5 and 6.5.x

Note: In addition to the alert conditions, NOM 6.5/6.5.x contains an internal pre-defined alert policy called the License Capacity Alert. It is an informational alert policy and cannot be modified. SNMP recipients for this policy can be configured. This policy appears only in the server context and occurs if your storage service capacity has exceeded the license capacity. The alert is not generated for the capacity-based licenses for OpenStorage Disk option, PureDisk Storage option, and Virtual Tape option.All capacity values for this alert are calculated based on the definition that 1 terabyte=1024 GB.

16. Lost Contact with Media Server

17. Low Available Media

18. Low Disk Volume Capacity

19. Master Server Unreachable

20. Media Required for Restore

21. Mount Request

22. No Cleaning Tape

23. Service stopped

24. Suspended Media

25. Zero Cleaning Left

Table 3-2 Alert Conditions in NOM 6.5 and 6.5.x

Serial Number Alert Condition

22 NetBackup AlertsAlert Conditions in NOM 6.0 and 6.0 MPx

Alert Conditions in NOM 6.0 and 6.0 MPxTable 3-3 on page 22 lists the alert conditions available in NOM 6.0 and 6.0 MPx.

Table 3-3 Alert Conditions in NOM 6.0 and 6.0 MPx

Serial Number Alert condition

1. Catalog Backup Disabled

2. Catalog not Backed Up

3. Catalog Space low

4. Drive is Down

5. High Down Drives

6. High Frozen Media

7. High Job Failure Rate

8. High Suspended Media

9. Hung Job

10. Job Finalized

11. Lost Contact with Media Server

12. Low Available Media

13. Master Server Unreachable

14. Mount Request

15. No Cleaning Tape

16. Service stopped

17. Zero Cleaning left