Page History

...

1. Hover the mouse cursor over the  button and click the N+1 button.
   
2. Click the button and add a backup Server.
   
3. Click the button and add primary Servers.
4. If you need to maintain a local event database on Servers, activate the corresponding switch (1).
   

5.  If you want to replicate the local archive when the master node is on the backup Server, activate the corresponding switch (2).

   Note
   title Attention!
   The local archive must be created on the master node (see Creating a local archive).

   
   

6.  If you need to replicate local archives to the backup Server on permanent basis, activate the corresponding switch (3). Otherwise, the replication will be performed only when the corresponding node is migrated to the backup Server.

7. By default, the self-diagnostics service is running on all nodes (see Self-diagnostics service). To stop it, deactivate the Self diagnostics parameter (4).

8. Click the Logging button to set the logging parameters (5):
   1. Select the logging level (see Configuring the logging levels Log Management Utility).
   2. Set the log archive parameters (see Configuring the Server log storage and archiving options (see Log Management Utility).
9. Click the APPLY button.
   The configuration is now created, and the nodes are now automatically started. "Failover" string will be automatically added to the name of the backup node.
   
10. Merge all nodes into a single Axxon-domain (see Connecting to a Node and Configuring of an Axxon domain).
11. Configure the archives operation:
    1. On the backup node, create an archive for replication (see Creating archives).
    2. On the master nodes, configure the replication from the master Servers' archives to the backup node's archive (see Configuring data replication). The replication period should be set to Always regardless of the value of the Force archive replication parameter (see item 6).
       

...