Go to documentation repository
Page History
...
Info | ||
---|---|---|
| ||
When moving configuration to the backup Server and getting it back to the main Server the Failover service object generates START and STOP events. These events can be used in scripts for flexible system configuration. For examples, see Examples of scripts in the JScript language section of Programming Guide (JScript) The Script object. Programming using the JScript language. |
The configuration transfer time after losing connection with the main Server depends on many factors including but not limited to the following:
...
If the main Server + standby Server operation scheme is in use (see the figure below), it is possible to configure both main and standby Servers for recording on the same network resource or several resources (see Using network disks). In this case, the archive is always available no matter which Server operates with cameras.
...
The AxxonPlayer.exe utility can be used to access the archive created by the standby Server on NAS or local drive (see The Axxon Player utility for viewing and converting the video archive). Alternatively, the main and the backup Server archives can be synchronized through the Backup archive module (see Configuring archive synchronization of main and backup Servers).
...
The number of failover services running on each computer simultaneously can be limited. The Manager of failover services object is used for this. It is created on the basis of the Computer object that is not the Client (see Role-assignment in distributed system).
If the number of failed Servers exceeds the specified limit, the configuration from the new failed Servers will be transferred to the corresponding backup Server as the previously failed Servers become operational.