HP Data Protector A.06.
Legal and notice information © Copyright 2004, 2008 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Contents About this guide ................................................................... 9 Intended audience ............................................................................................... 9 Documentation set ............................................................................................... 9 Guides ........................................................................................................ 9 Online help ..........................................................
SNMP Emanate Agent (required) ............................................................ 27 Additional software for Windows managed nodes (Data Protector Cell Server) ...................................................................................................... 28 SNMP service (required) ........................................................................ 28 Disk-space requirements ............................................................................... 29 Memory (RAM) requirements ....
Databases ................................................................................................ Media pool status ....................................................................................... Media pool size ......................................................................................... Monitor status of long running backup sessions ............................................... Check important configuration files ..............................................................
Number of Files Backed Up trend .................................................................. 92 6 Troubleshooting ............................................................... 95 HP Data Protector events not arriving on the HPOM message browser ...................... HP Data Protector services not visible in the HPOM Console ................................... Auto-deployment of policies failing on HPOM 8.00 ...............................................
Figures 1 Operations Manager–Data Protector Integration architecture ................. 23 2 Data Protector GUI Reporting Context ............................................... 37 3 Configuring the SNMP service on Windows ........................................ 38 4 The Data Protector service tree .......................................................... 53 5 Windows users ...............................................................................
Tables 1 Document conventions ...................................................................... 17 2 HP Data Protector availability ............................................................ 26 3 Cell service tree nodes ..................................................................... 54 4 Data Protector Operations Manager operators and their roles ...............
About this guide This guide provides information about how to monitor and manage the health and performance of the Data Protector environment with HP Operations Manager for Windows. Intended audience This guide is intended for users of HP Operations Manager for Windows, with knowledge of: • HP Data Protector concepts • HP Operations Manager for Windows concepts Documentation set Other documents and online Help provide related information.
This guide describes Data Protector concepts and provides background information on how Data Protector works. It is intended to be used with the task-oriented online Help. • HP Data Protector installation and licensing guide This guide describes how to install the Data Protector software, taking into account the operating system and architecture of your environment. This guide also gives details on how to upgrade Data Protector, as well as how to obtain the proper licenses for your environment.
This guide describes how to install, configure, and use the integration of Data Protector with HP Service Information Portal. It is intended for backup administrators. It discusses how to use the applications for Data Protector service management. • HP Data Protector integration guide for HP Reporter This guide describes how to install, configure, and use the integration of Data Protector with HP Reporter. It is intended for backup administrators.
describes how to configure and use Data Protector to perform backup and restore using the Microsoft Volume Shadow Copy Service. • HP Data Protector MPE/iX System user guide This guide describes how to configure MPE/iX clients and how to back up and restore MPE/iX data. • HP Data Protector Media Operations user guide This guide provides information for network administrators responsible for maintaining and backing up systems on the tracking and management of offline storage media.
Documentation map Abbreviations Abbreviations in the documentation map that follows are explained below. The guide titles are all preceded by the words “HP Data Protector.
Abbreviation guide MO UG Media Operations user guide MPE/iX MPE/iX system user guide PA Product announcements, software notes, and references Trouble Troubleshooting guide ZDB Admin ZDB administrator's guide ZDB Concpt ZDB concepts guide ZDB IG ZDB integration guide Map The following table shows where to find information of different kinds. Shaded squares are a good place to look first.
Integrations Look in these guides for details of the following integrations: Integration Guide HP Operations Manager for UNIX/for Windows IG-OMU, IG-OMW HP Performance Manager IG-PM/PA HP Performance Agent IG-PM/PA HP Reporter IG-R HP Service Information Portal IG-SIP HP StorageWorks Disk Array XP all ZDB HP StorageWorks Enterprise Virtual Array (EVA) all ZDB Integration guide for HP Operations Manager for Windows 15
Integration Guide HP StorageWorks Virtual Array (VA) all ZDB IBM DB2 UDB IG-IBM Informix IG-IBM Lotus Notes/Domino IG-IBM MaxDB IG-O/S Media Operations MO User MPE/iX System MPE/iX Microsoft Exchange Servers IG-MS, ZDB IG Microsoft Exchange Single Mailbox IG-MS Microsoft SQL Servers IG-MS, ZDB IG Microsoft Volume Shadow Copy Service (VSS) IG-MS, ZDB IG NDMP Server IG-Var Network Node Manager (NNM) IG-Var Oracle IG-O/S Oracle ZDB ZDB IG SAP DB IG-O/S SAP R/3 IG-O/S, ZDB
Document conventions and symbols Table 1 Document conventions Convention Element Blue text: Table 1 on page 17 Cross-reference links and e-mail addresses Blue, underlined text: http://www.hp.
NOTE: Provides additional information. TIP: Provides helpful hints and shortcuts. General Information General information about Data Protector can be found at http://www.hp.com/go/ dataprotector HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
HP websites For additional information, see the following HP websites: • • • • http://www.hp.com http://www.hp.com/go/storage http://www.hp.com/support/manuals http://www.hp.com/support/downloads Documentation feedback HP welcomes your feedback. To make comments and suggestions about product documentation, please send a message to DP.docfeedback@hp.com. All submissions become the property of HP.
About this guide
1 Introduction In this chapter This chapter provides an overview of the HP Data Protector Integration, its key features and its architecture. For descriptions of HP Data Protector and HP Operations Manager, see the HP Data Protector concepts guide and the HP Operations Manager concepts guide.
• You can run Data Protector functionality from the Operations Manager tool group window. • Data Protector Integration messages sent to the Operations Manager Server includes instructions that help you correct the problem. The main benefits of the integration are: • Centralized problem management using Operations Manager agents at Data Protector managed nodes. Using a central management server avoids duplicated administrative effort.
Figure 1 Operations Manager–Data Protector Integration architecture The Operations Manager policies monitor: • Data Protector vital Cell Manager processes • Data Protector log files • Data Protector events through SNMP traps They are configured on the Operations Manager Agent on a Data Protector Cell Manager. The Agent sends messages to the Operations Manager Server for display in the message browser only if appropriate conditions match.
Introduction
2 Installing the Data Protector Integration This chapter describes: • Prerequisites for installing the Data Protector integration. • Installing the Data Protector Integration on the Operations Manager Server system. • Installing Data Protector Integration components on Operations Manager managed node (Data Protector Cell Manager) system. • Uninstalling Data Protector Integration components from Operations Manager managed node (Data Protector Cell Manager) systems.
Data Protector supported versions The Data Protector Integration is designed to work with the following HP Data Protector versions: Table 2 HP Data Protector availability Data Protector Version HP Operations Manager for Windows 7.5/8.0/8.1 plus patches, if available 5.1, 5.5, 6.0, 6.
NOTE: The Data Protector Integration supports Operations Manager installed in an MS Cluster environment. However, the integration does not support Data Protector Cell Managers (managed nodes) in a cluster environment. Managed node systems (Data Protector Cell Server) A number of agents and the Data Protector Integration are required for the complete management of Data Protector environments.
Operations Manager Server. This is called Distributed Event Interception, since the SNMP traps are intercepted on the managed node and filtered and forwarded to the Operations Manager Server by the Operations Agent. The advantages, especially for large enterprise environments with a high number of Data Protector Cell Managers, are: • The solution scales better. Additional Data Protector Cell Managers do not put additional load on the management server because SNMP traps are processed on the managed node.
Disk-space requirements The following table lists disk space requirements for both the installation of the Data Protector Integration and the Data Protector Integration’s run-time files on the Operations Manager Server and the OM managed node. Machine Operations Manager Version Operating System Total Operations Manager Server 7.5/8.0/8.1 Windows 15 MB Operations Manager Managed Node 7.5/8.0/8.
OMW 7.5: system_drive\Program Files\HP OpenView OMW 8.
• obspi2.conf The following directories are created on a Data Protector Cell Manager running on Windows after the Data Protector Policies and Monitors have been deployed to it.
• spi_datapro_input.xml • spi_datapro_install.xml • spi_datapro_reg.xml • spi_datapro_runSHSCollector.cmd • spi_datapro_task.xml NOTE: You should delete these instrumentation files manually deleted from the Windows/UNIX cell manager nodes after the policies are un-installed from the nodes. The management server will not remove them automatically. Installation verification To verify the installation: 1. Open the Add/Remove Programs window: Start -> Settings -> Control Panel -> Add/Remove Programs 2.
NOTE: The ellipses highlight DP integration components.
1. Run the Add DP Cell tool to create the necessary folders and nodes under the DP ALL CELLS and DP ALL MGRS node groups. The Edit Parameters window is displayed: 2. When prompted, enter the name of the node group that you are creating under DP ALL CELLS. In the example in window above, the node name of the Cell Manager, nt8447, is also used for the name of the node folder created under DP ALL CELLS.
View -> Policy inventory Agent configuration NOTE: In order to receive the File Library SNMP events from Data Protector 5.
SNMP configuration on UNIX To enable the Operations Manager Agent on UNIX nodes to receive SNMP traps from Data Protector: 1. Execute one of the following commands to set the SNMP mode: • If an ovtrapd process is running, add: ovconfchg -ns eaagt -set SNMP_SESSION_MODE TRY_BOTH • If no ovtrapd process is running, add: ovconfchg -ns eaagt -set SNMP_SESSION_MODE NO_TRAPD 2. Configure the SNMP Emanate Agent to send SNMP traps to the local Operations Manager Agent by adding the following lines to the snmpd.
3. Configure Data Protector to send SNMP traps to the DP Cell Manager: a. Using the Data Protector GUI Reporting context, set up all Notification events to use: • SNMP as delivery method • Cell Manager system as the destination Figure 2 Data Protector GUI Reporting Context b. Add the Cell Manager hostname as trap destination to the OVdests file in /etc/opt/omni/snmp (Data Protector 5.1) /etc/opt/omni/server/snmp (Data Protector 5.5 and above). c.
3. Configure the SNMP Service on a Windows system to send traps to the Operations Manager Server. The community name should be public (the default community name that Data Protector SNMP traps use). The trap destination must be the IP address or the hostname of the Operations Manager Server and the rights of the community must be READ CREATE. To use a custom community name other than public, set the value in the Registry.
4. Configure Data Protector to send SNMP traps to the Operations Manager Server system: a. Using the Data Protector GUI Reporting context, set up all notification events to use: • SNMP as delivery method • Operations Manager Server system as the destination See Figure 2 on page 37. b. Add the Operations Manager Server hostname as trap destination to the OVdests file in Data Protector Root/Config/server/SNMP. c.
NOTE: To check whether SNMP is been configured or not , on the OMW server GUI, right-click on the node Select View -> Hosting service list. SNMP traps should be displayed in the list. Data Protector user configuration NOTE: DP SPI tools and applications do not support non-root agent nodes. UNIX nodes: Check the local root user is in Data Protector’s admin user group. Windows nodes: Add the local HP ITO account user to Data Protector’s admin user group.
Program identification UNIX managed nodes: All Data Protector Integration programs and configuration files contain an identification string that can be displayed using the UNIX command “what(1):”. The output is of the form: HP Data Protector Integration into Operation Manager Unix A.06.10 (build_date) Windows managed nodes: All Data Protector Integration programs and configuration files contain an identification string: 1. Right-click the ob_spi_backup.exe file. 2. Select Properties from the popup menu.
Uninstalling from managed nodes Undeploying all Data Protector policies from managed nodes 1. Select Policy management\Policy groups\SPI for DataProtector, right-click and select All Tasks -> Uninstall from ... from the pop-up menu. The Uninstall policies from ... window is displayed. 2. Mark the DP ALL MGRS node entry. 3. Click on force policy removal and remove all versions (in the case of OMW 8.0). 4. Click OK.
1. Select Tools \ SPI for DataProtector \ DP_tools -> Del DP Cell. The DPSPIDelDPCell window is displayed: 2. Enter the DP cell manager name and select its OS type. 3. Click OK. 4. Remove the cell manager entry from DP ALL CELLS. Right-click on Node, select Configure->Nodes. The Configure Managed Nodes window is displayed: Under DP ALL CELLS, right-click on the DP Cell Manager Node name and select Delete. A Confirmation window pops up. Click OK.
NOTE: Before proceeding to the next step, make sure all the DP Cell Manager Managed nodes are removed from the Operations Manager Server. Removing the Data Protector integration To remove the Data Protector Integration from the Operations Manager Server: 1. From the Control Panel, select Add/Remove Programs. The Add/Remove Programs window is displayed: 2. In the Add/Remove Programs window, scroll down until you find the HP Operations Smart Plug-in for HP Data Protector entry. 3.
3 Performance measurement with the HP Performance Agent NOTE: See the HP Data Protector PM/PA integration guide for details regarding the integration of Performance Manager and Performance Agent with Data Protector.
Performance measurement with the HP Performance Agent
4 Using the Data Protector Integration In this chapter The sections in this chapter show which new components are added to Operations Manager during the installation of the Data Protector Integration and describe how to use them to best effect: • • • • • • • • Data Protector SPI policies, page 47 Message groups, page 48 Node groups, page 50 Tools groups, page 51 Data Protector service tree, page 53 Users and user roles, page 55 Monitored objects, page 62 Monitored log files, page 70 Data Protector SPI pol
The SPI for DataProtector policy group contains: • DP-SPI NT Policies • DP-SPI UX Policies Both are assigned by default to the DP UX MGRS node group for automatic deployment to any node added to this node group. Run the Add DP Cell tool and the appropriate policy group is automatically deployed to the newly added Data Protector Cell Manager. Message groups Message Groups are used to categorize messages in the Operations Manager message browser.
DP_Backup Backup session messages DP_Restore Restore session messages DP_Mount Mount request messages DP_Misc All other important Data Protector related messages DP_SPI Messages from the Data Protector Integration DP_Interactive Detailed messages normally only displayed in the Data Protector GUI. This message group is disabled as default. Enable the group for the greatest level of detail about Data Protector operation.
Node groups Node groups are logical groups of systems or devices assigned together with message groups to an operator to manage. Each node group is represented by an icon in the Nodes tab/context in the OM window. Open a node group to view all systems within it. A system may belong to more than one node group. The Data Protector Integration provides the four Node Groups, DP ALL CELLS, DP ALL MGRS, DP NT MGRS and DP UX MGRS: The Add Data Protector Cell action adds a node below the DP ALL MGRS node group.
administrator uses the Add Data Protector Cell application to create a new node, the node is automatically placed in the node group corresponding to its operating system. Tools groups Installation of the Data Protector Integration adds two new tools groups to the Operations Manager Tools folder. Each different Operations Manager user role has an appropriate set of Data Protector Integration applications.
Using tools and reports Tools usually execute on the management server or managed nodes. The Add DP Cell tool runs on the system where the console for the OM Management Server resides. The user name and password may be stored with the tool properties or you may have to enter them when you run the tool. When you select a tool to be run and the target type for the tool is Selected Node, a window opens prompting you for nodes on which to execute the application associated with the tool in the Details tab.
Data Protector service tree Data Protector is represented as a service tree with each cell an icon. The tree is updated by SNMP traps sent by the notification feature in Data Protector and by messages from Data Protector Integration monitors. Figure 4 illustrates the HP_Data Protector service tree consisting of a sub-tree for the Cell Manager:nt8446 Data Protector Cell Manager.
The following service tree nodes are available for each cell: Table 3 Cell service tree nodes Node Description backup group. Contains Running, Waiting, Aborted, Failed, Completed, Completed with Failures, and Completed with Errors. Backup Sessions Data Protector sends SNMP traps to trigger the update of these items. Running Updated by Start of Session SNMP trap issued by Data Protector notification.
Node Description Ended Updated by Session Completed, Completed with Errors, or Completed with Failures SNMP trap. Database Updated by DB* SNMP traps issued by Data Protector notification and by messages resulting from database log file monitoring. Device Events Updated by Device Error-, Mount Request-, Mail Slots-, and Full- SNMP traps issued by Data Protector notification.
A Data Protector user group defines access rights for its members. A member of a user group is identified by the group’s operating system user. This user, used to log in to the system, has access rights and Data Protector GUI context determined by the user group. When a user from the group starts the Data Protector GUI from Tools, the layout of the Data Protector GUI and permissions for the user are determined by the operating system user.
Operations Manager user roles Operations Manager uses User Roles to describe the configuration of abstract users. They are useful in large, dynamic environments with many Operations Manager users and allow the rapid setting up of Operations Manager users with default configuration. An Operations Manager user may have multiple user profiles assigned and so can hold multiple roles.
DP Backup Admin Restricted to a Data Protector Cell. Tool Groups: • DP_Backup_Admin • DP_Reports Can access messages in the Operations Manager Message Browser, if the Operations Manager message policy for detailed messages DP_Detailed is enabled. DP Backup Operator Restricted to a Data Protector Cell. Tool Groups: DP_Backup_Oper Message Groups: • DP_Backup • DP_Misc • DP_Mount These are backup session messages and mount requests of backup sessions messages.
DP Cell Administrator Restricted to clients of Data Protector Cells. Tool Groups: • DP_Reports • DP_Tools Message Groups: • DP_Misc • DP_SPI DP Report Administrator Restricted to a Data Protector Cell. Tool Groups: DP_Reporting Messages: None. Data Protector Operations Manager operators The Data Protector Operations Manager operators use Operations Manager to maintain, manage, monitor, and control multiple Data Protector cells from a single console.
Role Backup Operator Restore Operator 60 DP Privileges Description Switch session ownership You can specify the owner of the backup specification under which backup is started. By default, this is the user who started the backup. Scheduled backups are started as root on a UNIX Cell Manager and under the Cell Manager account on a Windows system. Start a backup (if not scheduled), monitor the status of backup sessions, and respond to mount requests by providing media to devices.
Role Device & Media Administrator Media Operator DP Privileges Description Restore to other clients You can restore an object to a system other than that from which the object was backed up. Restore from other users You can restore objects belonging to another user. UNIX specific user right. Restore as root You can restore objects with the rights of the root UNIX user. Note: This is a powerful right that can affect the security of your system. Required to restore on NetWare clients.
Role DP Privileges Cell Administrator Instals and update Data Protector client systems, add, delete, or modify Data Protector users and groups, and administer the Data Protector database. Report Administrator Description Client configuration You can install and update client systems. User configuration You can add, delete and modify users or user groups. Note: This is a powerful right.
Threshold: Number of processes <3 Polling interval: 10 minutes Message structure: Message Group DP_Misc Applications Data Protector Node name_cell_manager Severity Critical Service Name Services.Data Protector.cell name Object Windows: DP_CheckProc_NT UNIX: DP_CheckProc_UX Operator Action in case of problem Start services Message Text when problem solved Auto-acknowledge this message and the preceding problem message Databases Checks amount and percentage of used available space.
Applications Data Protector Node name_database_server Severity Critical Service Name Services.Data Protector.cell name .Database Object Windows: DP_CheckDB_NT UNIX: DP_CheckDB_UX Automatic Action in case of problem Status of database Operator Action in case of problem Purge or extend the database Message Text when problem solved Auto-acknowledge this message and the preceding problem message NOTE: The usage of this monitor program is as follows: Windows: ob_spi_db.
Applications Data Protector Node name_cell_manager Severity Critical or Warning Service Name Services.Data Protector.
Operator Action in case of problem Status of the Media Pool Message Text when problem solved Auto-acknowledge this message and the preceding problem message Monitor status of long running backup sessions Checks if there are backup up sessions that have been running for longer than: • 12 hours (Critical) • 8 hours (Warning) Polling interval: 60 minutes Message structure: Message Group DP_Backup Applications Data Protector Node name_database_server Severity Critical or Warning Service Name Servic
UNIX nodes: OB_CheckFile_UX starts ob_spi_file.sh Windows systems Checks if the following files exist in subdirectories of the Data Protector configuration directory (default: system_drive\Program Files\OmniBack\Config\): For Data Protector 5.1 and earlier: • cell\cell_info • cell\cell_server • cell\installation_servers • users\userlist • users\classspec • users\webaccess • snmp\OVdests • snmp\OVfilter • options\global • options\trace For Data Protector 5.
UNIX systems Checks if the following files exist: For Data Protector 5.1 and earlier: • /etc/opt/omni/cell/cell_info • /etc/opt/omni/cell/installation_servers • /etc/opt/omni/users/UserList • /etc/opt/omni/users/ClassSpec • /etc/opt/omni/users/WebAccess • /etc/opt/omni/snmp/OVdests • /etc/opt/omni/snmp/OVfilter • /etc/opt/omni/options/global • /etc/opt/omni/options/trace • /etc/opt/omni/cell/cell_server For Data Protector 5.
Windows: OvAgentDir\bin\instrumentation UNIX: /var/opt/OV/bin/instrumentation Examples of the default obspi.conf files are given below: Windows: [OB_CheckFile_NT] \Config\client\cell_info \Config\client\installation_servers \Config\server\users\userlist \Config\server\users\classspec \Config\server\users\webaccess \Config\server\SNMP\OVdests \Config\server\SNMP\OVfilter \Config\server\Options\global \Config\server\Options\trace \Config\client\cell_server [OB_CheckProc_NT] rds.exe crs.exe mmd.
Use the Operations Manager Policy Editor on the Operations Manager Server to adjust how often each monitor is started. If you change any Operations Manager policy, it must be redistributed to the assigned systems before it becomes active. Monitored log files You can use Operations Manager to monitor applications by observing their log files. You can suppress log file entries or forward them to Operations Manager as messages.
Automatic Action Get status of Cell Manager processes Examples 2001-6-13 7:46:40 -STOP HP Data Protector services successfully stopped. 2001-6-13 7:46:47 -START HP Data Protector services successfully started. inet.log Provides security information. Messages document requests to the inet process from non-authorized systems. The data/time format depends on the value of the language environment variable. Examples 06/14/01 09:42:30 INET.12236.0 ["inet/allow_deny.c /main/7":524] A.04.
purge.log Contains purge session messages. Purge sessions are used to clean up the database. The data/time format depends on the value of the language environment variable. Examples 06/17/01 15:42:15 ASM.1999 5.0 Purge session started. 06/17/01 15:42:15 ASM.1999 5.0 Filename purge session started. 06/17/01 15:42:16 ASM.1999 6.0 Purge session finished. 06/17/01 15:42:16 ASM.1999 5.0 Filename purge session ended. ["sm/asm/asm_purge.c /main/16":435] A.04.00 b364 ["sm/asm/asm_purge.c /main/16":445] A.04.
readascii.log Messages generated when the database is read from a file using readascii. writeascii.log Messages generated when the database is written to a file with writeascii. lic.log Unexpected licensing events. sm.log Detailed errors during backup or restore sessions, such as errors while parsing the backup specification. No message catalog is used. The time/date format depends on the language environment variable.
Using the Data Protector Integration
5 ReporterLite integration In this chapter This chapter covers integration with ReporterLite and creating Data Protector reports: • • • • • ReporterLite overview, page 75 ReporterLite integration with Data Protector architecture, page 76 Installing the Reporter Lite integration, page 77 Using the Reporter Lite integration with Data Protector, page 78 Preconfigured reports, page 81 ReporterLite overview NOTE: The ReporterLite integration is available only with Operations Manager for Windows 7.
• Ability to view session trend reports and gain insight on the overall health of Data Protector cell servers over a selected time. • Ability to view trend reports on the data backup, backup duration and number of files backed up. • Reporting Error Status and Session Health details over a selected time. • Easy for administrators to predict the volume of data to be backed up in the future, as the trend reports shows the amount of data growth.
• DBSM The following is a high-level representation of the integration: Figure 6 ReporterLite integration with Data Protector architecture 1. The Add Cell utility is used to register a Data Protector management server with this module. 2. The Gatherer (DPGather), supplied as a part of this package, collects the required data from Data Protector and adds it to the database. 3. The Reporter Engine of ReporterLite generates reports using the database and the templates.
INSTALL_DIR\newconfig\Packages Contains XML and SRP files used to create database tables and views, and to add report definitions INSTALL_DIR\data\reports\DP Contains report templates and ReadMe.txt Verifying installation To verify the installation: 1. Open the Add/Remove Programs window: Start -> Settings -> Control Panel -> Add/Remove Programs 2. Check HP Operations Smart Plug-In for HP Data Protector appears as an installed product.
Figure 7 Add Cell window Use this to register as many Data Protector Cell Managers as required. Troubleshooting Error message Not able to load Reporter Database!! Description The application cannot access the Reporter database. Action Ensure that the reporter database is accessible. Error message Not able to Resolve the host name!! This cell information is not updated. Description The application cannot resolve the host name. Action Ensure the host system exists and is accessible.
Action Ensure the database table DPCELLS is present. If the tables do not exists, create/recreate them using the following commands: newdb -xml INSTALL_DIR\newconfig\ Packages\DPCELLS.xml and newdb -xml INSTALL_DIR\newconfig\ Packages\DPTREND.xml Error message Cell Manager already exists in the Reporter database!! Error Code: 23000 Description A Data Protector Cell Manager is already registered with ReporterLite, and you cannot use this application to update the information.
http://OVO_SERVER:PortNumber/HPOV_Reports/ Family_Data_Protector_Service_Level_Reports.htm Where PortNumber is the port on which the web server is running. Click on the appropriate link to view the desired report. Preconfigured reports Session Trend report This graph shows the success and failure of backup sessions over time. The default period is 30 days. The date range is configurable by administrators. The graph shows trends for all sessions and for the individual Cell Manager.
Backup Duration Trend report This graph shows the duration of backup sessions in hours over time. The default period is 30 days (configurable by administrators).
Amount of Data Written Trend report This graph shows how much data is written to backup media over time. The default period is 30 days (configurable by administrators). The graph shows trends for all sessions and for the individual Cell Manager.
The amount of data written is in gigabytes. To calculate the number of files backed up with the amount of data written in one graph, the On Demand report template is used. See “On Demand report—number of files, data written and date” on page 88. Number of Files Backed Up Trend by All Backup Groups report This graph shows the trend of the number of files (in 1000s) backed up by all Backup Groups over time. The default period is 30 days (configurable by administrators).
Backup Session Health Overview report This graph shows the ratio of successes to failures for backup sessions of each Data Protector Management system. Failures include session aborts, session errors and session failures. One graph is produced for each of the sessions run during the past month, week and day.
Operational Error Status report This graph shows the number of operational errors that occurred on Data Protector Cell Managers. Error status include Session Aborted, Session Error, Session Failed, Mount Errors, Mount Request (not enough free media).
Skipped Files report This lists files not backed up during the backup session.
On Demand report—number of files, data written and date You can generate custom reports and standard reports. For standard reports the Data Protector template file is used with the following graph names: • Sessions Trend • GB Written Over Number of Files backed-up The following is an example of a graph of GB Written Over Number of Files backed-up.
Media Pool Usage trend This graph shows the trend of media pool usage information for all Data Protector Cell Managers.
Successful Backup trend This shows the percentage of successful backups for each Backup Group by all Data Protector Cell Managers.
Backup Volume Usage trend This graph shows the amount of data backed up for each Backup Group used by all Data Protector Cell Managers.
Number of Files Backed Up trend This shows the numbers of files backed up for each Backup Group by all Data Protector Cell Managers.
Integration guide for HP Operations Manager for Windows 93
ReporterLite integration
6 Troubleshooting Following are the issues in the HP Data Protector Integration: • • • • HP Data Protector events not arriving on the HPOM message browser HP Data Protector services not visible in the HPOM Console Auto-deployment of policies failing on HPOM 8.00 Auto-deployment of policies failing on OVOW 7.5 HP Data Protector events not arriving on the HPOM message browser Symptom: No HP Data Protector events arriving in the HPOM message browser.
9. Make sure the dpspi instrumentation binaries are deployed at the Data Protector CM at the OM_AGENT_INSTRUMENTATION_DIR. HP Data Protector services not visible in the HPOM Console Symptom: HP Data Protector services are not visible in the HPOM Console. Action: Ensure that the Service Discovery policies in the policy groups from Policy Management > Policy Groups > SPI for DataProtector > DPSPI NT POLICIES > DP_Service_Discovery is deployed on the HP Data Protector CM node.
Index D A Add Data Protector Cell application, 33 additional software for Windows nodes, 28 agent configuration, 35 PA versions supported by Operations Manager, 27 versions supported by Operations Manager, 27 Amount of Data Written Trend report, 83 architecture, 22 audience, 9 B Backup Duration Trend report, 82 Backup Session Health Overview report, 85 Backup Usage Trend report, 91 C cell manager prerequisites, 27 permanently running processes, 62 configuration files, monitoring, 66 configuration, agent,
G L groups message, 48 node, 50 tool, 51 log files Data Protector database, 71 default, 70 monitoring, 70 not monitored, 72 long running backup sessions, monitoring, 66 H hardware prerequisites Operations Manager Server, 26 help obtaining, 18 HP technical support, 18 I identifying Data Protector Integration identifying programs, 41 inet.
Operations Manager additional software for Windows nodes, 27 supported agent versions, 27 Operations Manager managed nodes SNMP configuration on UNIX, 36 Data Protector user configuration, 40 SNMP configuration on Windows, 37 Operations Manager Server installing, 26 supported versions, 26 hardware prerequisites, 26 installing Data Protector Integration, 29 patches, 26 software prerequisites, 26 Operations Manager user roles, 57 operators, Data Protector Operations Manager, 59 P patches Operations Manager S
software prerequisites Operations Manager Server, 26 Subscriber's Choice, HP, 18 Successful Backup Trend report, 90 T technical support HP, 18 service locator website, 19 tool groups, 51 U uninstalling DP integration, 41 from managed nodes, 42 from OM server, 42 uninstalling ReporterLite, 78 user Data Protector Integration, 56 groups, Data Protector, 55 operating system, 55 user roles Data Protector Operations Manager, 57 Operations Manager, 57 users and use roles, 55 V verifying management server instal
