Select from many delivery methods used to deliver reports (such as e-mail, SNMP, broadcast (available on Windows only), write to file, and send to external command)

You can combine most of these different formats, delivery methods, schedules, and triggers.

Some examples are shown below:

Reporting and notification examples

Every morning at 7:00, a report about all backup, copy, and consolidation sessions in the last 24 hours is created and sent by e-mail in the ASCII format to the backup administrator's mailbox. Additionally, the same report is written to a file on your Web server in the HTML format so that others can also access this information.

In event of a device failure or a mount request, a broadcast message is immediately sent to the backup administrator's Windows workstation, and an external command is triggered, which activates the backup administrator's pager.

At the end of a backup session, every end user whose system has been backed up receives an e-mail in ASCII format that contains a backup status report.

Event logging and notification

The Data Protector Event Log is a central repository of all Data Protector-related notifications. The Data Protector built-in notification engine sends alerts or activates the Data Protector reporting mechanism based on the log entries. The event log is the information source for SLA-compliance reports in Data Protector or in HP software management applications. In addition to reports, log entries feed HP software management applications via the Data Protector SPI (SMART Plug-In) so that they can trigger preventive or corrective actions (for details, see the example under 3.1).

Since the Data Protector built-in notification engine can send alerts via SNMP, virtually any application that can receive SNMP traps can integrate with Data Protector. Integration with Operations Manager and Reporter is an example of SNMP trap-based implementation.

The Event Log is accessible only for Data Protector users in the Admin group and for Data Protector users that are granted the Reporting and notifications user rights. You can view or delete all events in the Event Log.

212

Service management