Defining a parameter recovery action

Parameter automated recovery actions include pro-active and automatic correction of a given problem. Automated recovery attempts to prevent situations that adversely affect availability or application throughput.

Recovery action guidelines

Use the following guidelines in developing recovery actions:

General guidelines

General guidelines for these template recovery actions are as follows:

• Design for broad applicability.
• Use well-documented procedures and scripts.
• Provide thorough user documentation, including:
  • decision-tree information
  • troubleshooting information
• Provide a verification/audit trail of ALL recovery attempts.
• Automated recovery actions should be disabled by default.
• Before performing any action, the recovery action script should test for the global variable to determine that automated recovery is enabled for the parameter. See Creating a parameter for more information.

This does not mean that automated recovery actions should not be provided. Rather, users can implement those recovery strategies that are consistent with their internal policies.

 Using tasks versus commands

You can define a recovery action as either a command or a task. 

When you run a recovery action as a task:

• A task icon appears in the PATROL Console to indicate that the recovery action executed. If every recovery action spawns a task window, you might get a task output window overload.
• The task output window provides recovery status and a starting point for investigating and auditing the problem's resolution.

External notification

Notification is an administrative function. For information about how to configure notifications, see the BMC PATROL Knowledge Module for Event Management Online documentation.