8.4.4.1 Redundancy Commands

While the general aspects of the redundancy are statically configured in the 'backend.properties' file, the backend provides a /api/v1/redundancy API call to control if the primary or the backup machine of a redundant pair shall be used. There are two commands which may be sent with this API call.

command description
RESET tells the backend to switch back to primary M&C. If the backend is already connected to the primary M&C, or if no redundancy is configured for this M&C, the 'RESET' command has no effect. If the backend cannot connect to the primary M&C for some time, it tries to switch over to the backup machine.
FORCE forces a switch over to the backup M&C - even if the communication with the primary one works fine. Has no effect if no redundancy is configured or if the backend is already connected to the backup machine.