Page History

...

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

5.  If you need to maintain local footage archives on primary Servers, activate the corresponding switch (2).

   Note
   title Attention!
   The local video footag will be created as a 10 GB file located in the C:/temp_arch folder. If the node is migrated from a primary Server to a backup one, video data will be recorded to this file and replicated to the main Archive (video footage) on the backup Server (see paragraph 10).

   
   

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, de-activate the Self-diagnostics parameter (4).

8. Click the Logging button to set the logging options (45, see Setting up basic configuration).
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 footage archives operation:
    1. On the backup node, create an archive for replication (see Creating archives).
    2. On the primary nodes, configure the replication from the primary Servers' archives to the backup node's archive. The replication period should be set to Always (see Configuring data replication). You have to set the replication time period to Always regardless of the value of the Forced Replication parameter (see paragraph 6).
       

...

• add / remove Servers;
• add / delete nodes;

• activate / de-activate the self-diagnostics service;

• change logging parameters;
• completely remove the configuration.

...