Primary-backup configuration example
- Last UpdatedApr 24, 2025
- 2 minute read
This example illustrates a distributed project’s configuration where each system controls its own set of field devices. The primary system, PRI, can view backup system activity and also receive alarms and events that occur on the backup system, BAC1.
The figure below displays the dynamics between a primary, backup, and their remotes while in Primary-backup mode.

The primary system, PRI, can view BAC1 system activity, as well as receive its alarms and events. BAC1 is not able to view any PRI data. PRI also has the ability to modify or add records to BAC1 for routine maintenance. However, PRI cannot control the backup system activity unless BAC1 gives control to the primary system.
This example requires the following configuration:
Requirements for primary-backup mode configuration
|
Table |
Description |
|---|---|
|
oas_system |
These records are required to define the PRI and BAC1 systems. |
|
doas_dataset |
In the example above, two doas_dataset records are required, one for each system. Specific privileges are assigned uniformly amongst all records in a given mode and system. |
|
doas_mode |
In the example above, two doas_mode records are required:
|
|
doas_privilege |
Six doas_privilege records are required for the example above. Three for each mode. For the INDEPENDENT_CONTROL mode:
|