Contents. Notification types - events that trigger notifications

Transcription

1 Data Protector allows you to send notifications from the Cell Manager when specific events occur. For example, when a backup, object copy, object consolidation, or object verification session is completed, you can send an with the status of the session. You can set up a notification so that it triggers a report. You can configure notifications using the Data Protector GUI or any Web browser with Java support. Input parameters let you customize notifications. Some input parameters allow multiple selections. All other input parameters depend on the type of the notification. Depending on the send method, the recipient can be any of the following: a system an address an SNMP trap a script a file a configured report group the Data Protector Event Log By default, notifications are configured with default values and are sent to the Data Protector Event Log. To send additional notification using some other sending method and/or other input parameters values, the configuration values must be changed. To access the Data Protector notification functionality. You either have to be added in the admin user group or granted the Reporting and notifications user rights. Contents 1 Notification types - events that trigger notifications 2 Notifications Send Methods 3 Configure notifications 4 Related task Notification types - events that trigger notifications There are two main types of notifications. Notifications that are triggered when an event occurs Notifications that are scheduled and started by the Data Protector checking and maintenance mechanism Notifications that are triggered when an event occurs Alarm Expired Certificates Check UNIX Media Agent Csa Start Session Failed Device Error End of Session IDB Corrupted File Library Disk Usage Mail Slots Full Mount Request Session Error

2 Start of Session Too Many Sessions Notifications that are scheduled and started by the Data Protector checking and maintenance mechanism Health Check Failed IDB Backup Needed IDB Limits IDB Reorganization Needed IDB Space Low License Warning License Will Expire Not Enough Free Media Unexpected Events User Check Failed Alarm What triggers the notification: Alarm Data Protector Internal critical conditions, such as Automated Media Copy upgrade, Upgrade Core Part End, Upgrade Detail Part End, Purge End, abort of session, Disk Agents upgrade during UCP, and so on. Warning Alarm: Alarm_message

3 Expired certificates What triggers the notification: ExpiredCertificates The certificate stored on Cell Manager certificate directory is expired or not yet valid. The Cell Manager certificate directory stores all client certificates for Secure Control Communication. Warning Certificate certificate_name expired or not yet valid.

4 Csa start session failed What triggers the notification: CsaStartSessionFailed The backup session that ends with the error message: Could not start a new backup session. Major CsaStartSession failed for datalist datalist_name.

5 Device error DeviceError What triggers the notification: An error on the device Device (default: <Any>). Critical Error on device Device occurred.

6 End of session What triggers the notification: Messages displayed: EndofSession A backup, copy, consolidation, or object verification session specified in the session specification Session Specification (default: <Any>) that ends with the message Session Status (default: Completed with errors). Warning Backup session session_id of session specification backup_specification, backup specification group group completed with overall status session_overall_status; session_type session session_id of session specification session_spec, completed with overall status session_status.

7 File library disk usage FileLibraryDiskUsage What triggers the notification: A lack of free disk space for the file library Name of the File Library (default: All). Warning The File Library Device is low in disk space in the File Library Path directory.

8 Health check failed What triggers the notification: HealthCheckFailed A non-zero value returned by the omnihealthcheck command. The command returns zero if the following is true: The Data Protector services (CRS, MMD, hpdp-idb, hpdp-idb-cp, hpdp-as, KMS, omnitrig, and omniinet) are active. The Data Protector Media Management Database (MMDB) is consistent. At least one backup of the IDB exists. By default, Data Protector starts the Health Check (which runs the omnihealthcheck command) once a day. Critical Health check message: healthcheck_command failed.

9 IDB backup needed IDBBackupNeeded What triggers the notification: Too many successive incremental IDB backups or insufficiently frequent full IDB backup. Warning There are n successive incremental IDB backups. The last backup of the Data Protector Internal Database was done on MM/DD/YY hh:mm:ss.

10 IDB corrupted IDBCorrupted What triggers the notification: Corruption of a part of the IDB. Critical Corruption in the IDB_part part of the Data Protector Internal Database has been detected (error_message). Values for error messages are: Verification of datafile(s) failed. KeyStore is corrupted. Media and Media in position tables are not consistent. Database is not in consistent state. Database schema is not consistent.

11 IDB limits IDBLimits What triggers the notification: Reaching the limit of any of the MMDB or CDB parts. Major The IDB_part part of the Data Protector Internal Database has reached its limit.

12 IDB reorganization needed IDBReorganizationNeeded What triggers the notification: One or more IDB entities need to be reorganized due to fragmentation or wasted space. Warning Bloat on table name_of_table detected. Fragmentation of table name_of_table on column uuid detected. Fragmentation of index name_of_index detected.

13 IDB space low What triggers the notification: IDBSpaceLow One of the following events: The maximum free disk size is below the IDB Disk Free Threshold [MB] (default: 300 MB) value. The difference between the maximum and current size of all DC directories falls below the DCBF Size Limit Threshold [MB] (default: 500 MB) value. The maximum free disk size is below the WAL Disk Free Threshold [MB] (default: 300 MB) value. By default, Data Protector checks the IDB Space Low condition once a day. Major Data Protector Internal Database is running out of space.

14 License warning LicenseWarning What triggers the notification: A need for purchased licenses. Warning n licenses need to be purchased for category name of the license. Run omnicc - check_licenses -detail for more info.

15 License will expire What triggers the notification: LicenseWillExpire The forthcoming expiration date of the Data Protector license. The license will expire in number of days specified in License expires in days (default: 10). Warning The first license will expire in License expires in days days.

16 Mail slots full MailSlotsFull What triggers the notification: Full mail slots of the device Device (default: <Any>). Warning All mail slots of library Device are full. Remove them immediately.

17 Mount request MountRequest What triggers the notification: A mount request for the device Device (default: <Any>). Warning Mount request on device Device.

18 Not enough free media What triggers the notification: NotEnoughFreeMedia A lack of free media in the Media Pool. Notice, that if a Media Pool is configured to use a Free Pool, the Number of Free Media from the Free Pool is also considered. Warning Media pool Media Pool contains only number_of_mediafree media.

19 Session error What triggers the notification: Messages displayed: SessionError A backup, copy, consolidation, or object verification session with a message of the level Single Message Level (default: Major) or higher, displayed in the Monitor window. Major Backup session session_id of session specification backup_specification, backup specification group group has errors: number_of_errors. session_type session session_id of session specification session_spec has errors: number_of_errors.

20 Start of session What triggers the notification: Messages displayed: StartofSession A start of a backup, copy, consolidation, or object verification session specified in the session specification Session Specification (default: <Any>). Normal Backup session session_id started for session specification backup_specification backup specification group group. session_type session session_id started for session specification session_spec.

21 Too many sessions TooManySessions What triggers the notification: Start of a session when 1000 sessions are already running concurrently. Warning Session cannot start because the maximum number of concurrently running sessions has been reached.

22 Unexpected events What triggers the notification: UnexpectedEvents An unusually high number of new events in the Data Protector Event Log since the last time the check was made. The number exceeds Number of events (default: 20). By default, Data Protector checks the condition once a day. Warning Data Protector Event Log increased for number_of events_in_last_day unexpected events in the last day.

23 Check UNIX media agent What triggers the notification: UnixMediaAgentWarning The mrgcfg -check_ma command triggers this notification when client devices are using rewind device files instead of no-rewind device files. Warning Media Agents, clients devices may have been configured using rewind device files instead of no-rewind device files. This may lead to problems in SAN environments.

24 User check failed What triggers the notification: UserCheckFailed A non-zero value returned by the user-created script/command with the name Command Path located in the default Data Protector administrative commands directory. By default, Data Protector starts the User Check (which runs the script) once a day (default: None). Major User check failed with exit code error_code:error_description.

25 Notifications Send Methods You can choose among various send methods when configuring a notification. By default, all notifications are configured to be sent to the Data Protector Event Log. To send a notification using another sending method, also, you must configure an additional notification. The available notification send methods are: Broadcast message send method send method (SMTP) send method External send method Log to file send method Data Protector Event Log send method SNMP send method Use report group send method Broadcast Message send method The broadcast message send method allows you to send a broadcast message with the output of the notification to specified systems after a specified event occurs. Broadcast messages can be sent to Windows systems only by specifying the target system. Broadcast messages are limited to 1000 characters, so a short format is preferred. send method You can send an with the output of a notification to specified recipients. Make sure you provide the full address of the recipient. Important Due to security features of Microsoft Outlook, using the send method may cause the CRS service to stop responding. Therefore, the recommended method for sending notifications is SMTP. On Windows systems To send an notification from a Windows system, you need to have a mail profile. You can either use an existing mail profile or create a new one, named OmniBack. To use an existing mail profile, add the following line to the Data Protectoromnirc file: OB2_MAPIPROFILE=existing_MAPI_profile_name On UNIX systems The subsystem has to be configured and running on a UNIX system. Due to the operating system limitations, international characters in localized notifications can be displayed incorrectly on UNIX systems, if they are passed between systems using a different locale. (SMTP) send method You can send an with the output of a notification to specified recipients. Make sure you provide the full address of the recipient. This is the recommended send method. By default, the address of the SMTP server used for sending the notifications is set to the Cell Manager IP address. To change the address, edit the SMTPServer global option. The SMTP server must be accessible from the Cell Manager system, but

26 does not need to be part of the Data Protector cell. External send method The external script send method allows you to process the output of the notification in your own script. The script receives the output as standard input (STDIN). The recommended format for script processing is the tab format. The script, which is located on the Cell Manager system, must reside in the default Data Protector administrative commands directory. Provide only the name of the script, no path. Note that only.bat,.exe, and.cmd are supported extensions for external scripts on Windows systems. To run a script with an unsupported extension (for example,.vbs), create a batch file that starts the script. Then configure Data Protector to run the batch file as an external script, which then starts the script with the unsupported extension. You can also use this delivery method to perform a scheduled eject of the specified media. Log to file send method The log to file send method lets you post a file with the output of the notification when a specified event occurs. The file is posted to the Cell Manager system. You have to specify the name of the file to which you want to post the notification. The file will be overwritten if it exists. Data Protector Event Log send method By default, all notifications are sent to the Data Protector Event Log. The Data Protector Event Log is accessible only for Data Protector users in the admin user group and to Data Protector users that are granted the Reporting and notifications user rights. You can view or delete all events in the Data Protector Event Log. SNMP send method SNMP send method allows you to send an SNMP trap with the output of the notification when a specified event occurs. The SNMP trap can be further processed by applications using SNMP traps. On Windows systems On a Windows Cell Manager, SNMP traps are sent to the systems configured in the Windows SNMP traps configuration. You need to configure Windows SNMP traps to use the SNMP send method on Windows systems. On UNIX systems On a UNIX Cell Manager, SNMP traps are sent to the systems configured in the notification. Use report group send method Use report group send method allows you to run a report group when a specified event occurs. Configure notifications To configure a notification you need to provide a name for the notification, a type of notification, message level, send method, and recipient. All other input parameters depend on the type of the notification. You either have to be added in the admin user group or granted the Reporting and notifications user rights. Complete the following steps: 1. In the Context List, select Reporting. 2. Right-click Notifications and click Add Notification to open the wizard.

27 3. The wizard options depend on the notification you selected. For example, all options available for the IDB Space Low notification are not available for the IDB Limits notification. Click Next as many times as needed to reach the last page of the wizard. 4. Click Finish to exit the wizard. The notification will be sent using the specified send method when the specified event occurs. Tip To trigger a report group by a notification, configure a report group and then configure the notification to use the Use Report Group send method. Related task Troubleshoot Reports and Notifications