A Virtual Business Service allows high availability decisions to be localized at the cluster level, while it propagates the events up the dependency chain. It is not mandatory for Veritas Operations Manager to be online for the fault to be propagated and the configured behavior to be executed. The high availability of a Virtual Business Service is guaranteed even if Veritas Operations Manager Management Server is temporarily down.
The following events can occur in response to a failure of the database application.
See Sample Virtual Business Service configuration.
Each tier has its own high availability mechanism, such as Veritas Cluster Server or ApplicationHA.
Inter-cluster fault propagation allows for the high availability events to be propagated up. For example, the Virtual Business Service notifies the middle tier about the fault and any subsequent recovery that occurs in the database tier.
You can configure how the middle tier must respond to the fault in the lower tier and so on. Depending on the business need, the middle tier might be configured to stop, restart, or stay online. The event might be propagated upwards based on the fault policy configured.
Table: Virtual Business Services fault policy behavior lists how a parent behaves in response to a fault or recovery on its child for various dependency types.
Table: Virtual Business Services fault policy behavior
Table: Virtual Business Services fault propagation behavior list how a parent propagates a fault to its parents in response to a fault or recovery on its child for different dependency types.
Table: Virtual Business Services fault propagation behavior
See Enabling fault management for a Virtual Business Service.
See Disabling fault management for a Virtual Business Service.