Once the problem on the Main Server is fixed it is ready to be brought back into operation again. Before doing so, it is good practice to first bring the Standby Server back to “Standby” state. This can be achieved by means of stopping its core services. Once back in “Standby” state, again all clients connected to the Standby Server will lose connection. Now, on the Main Server, the operator must import the latest database backups from the Standby Server. Server-specific information such as e.g. equipment agent IP addresses will be exchanged during import. Then they will start the base and core services so that Main Server becomes running again and clients can connect back to the Main Server.

Of course, one can also bring back the Main Server to “Running” state without before bringing the Standby Server back to “Standby” state (leaving it in “Running” state). In this case all FOXMAN-UN clients connected to the Main or the Standby Server will observe a “Main Server and Standby Server running both at the same time” alarm in the FOXMAN-UN alarm list.

However, having both servers in “Running” state shall be handled with care. This might increase the network load and the CPU load on the individual network elements (processing requests from two FOXMAN-UN at the same time). Far worse, some services created on one FOXMAN-UN will not be reflected to the other one (because its configuration data is only stored in the local FOXMAN-UN database).