QNX High Availability Framework consists of the following main components:
The QNX Neutrino microkernel provides system-wide stability by offering full memory protection to all processes. And there's very little code running in kernel mode that could cause the microkernel itself to fail. All individual processes, whether applications or OS services — including device drivers — can be started and stopped dynamically, without jeopardizing system uptime.
For more on the suitability of the QNX Neutrino RTOS for HA, see the next chapter in this guide.
As a self-monitoring manager, a HAM is resilient to internal failures. If, for whatever reason, the HAM itself is stopped abnormally, it can immediately and completely reconstruct its own state by handing over to a mirror process called the Guardian.
For details on the HAM, see the chapter Using the High Availability Manager in this guide.
You use the API to interact with a HAM in order to begin monitoring processes and to set up the various conditions (e.g. the death of a server) that will trigger certain recovery actions.
For descriptions of the functions in the HAM API, see the HAM API Reference chapter in this guide.
For descriptions of the client library functions, see the Client Recovery Library Reference chapter in this guide.
For details, see the Examples appendix in this guide.