Go to documentation repository
Page History
...
Distributed architecture can operate in the failover mode. If the connection with one of distributed system Servers fails, then this mode enables transferring the configuration created under the Server to a Standby Server. A Standby Server temporarily becomes a Video video server and records archive in accordance with the settings of the Computer object that corresponds to a Standby Server (see Selecting the disks for video archive storage section). When the connection is restored, the configuration is restored on the main Server.
| Info | ||
|---|---|---|
| ||
Video image update on Client Video Surveillance Monitors can take several seconds after configuration transfer as so , as the update is performed sequentially once in every 3 seconds. Video is displayed as usual after the update. If more than 64 cameras are added on the monitor, the update does not occur while the System Settings dialog box is open. The update period can be decreased by the monitor_refresh_delay registry key – see Registry Keys Reference Guide. |
| Info | ||
|---|---|---|
| ||
When moving configuration to the Backup Server and getting it back to the Main 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 JScript language section of Programming Guide (JScript). |
The configuration transfer time after losing communication connection with the main Server depends on many factors including but not limited to the following:
- Computer capacity.
- Data storage system speed.
- The value of the FastIndex key in the registry (see Registry keys reference guide). It is recommended that to set the key be set value to 1.
- The system objects tree objects tree (the more subsystems and modules there are, the slower the configuration transfer).
| Info | ||
|---|---|---|
| ||
The following migration time is confirmed in both directions (i.e. from the Main Server to the Standby standby Server and vice versa):
The archive size tested was more than 5TB and the Servers hardware as follows: |
...
If the main Server + standby Server flowchart 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 section). In this case , the archive is always available no matter what which Server operates with cameras.
...
If the N main Servers + standby server flowchart operation scheme is in use (see the figures below), it is impossible to create a unified archive. In this case , the main Servers perform recording on different logical drives (sections, partitions), local or network. If these drives are specified for archive recording are specified on a the standby Server, then the archives from different main Servers will mix.
The AxxonPlayer.exe utility can be used to access the archive created by a 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 Server archives can be synchronized through the Backup archive module (see Configuring archive synchronization of main and backup Servers).
...
The N main Servers + standby server flowchart when archive is recorded to one NAS:
If configuration from several main Servers is transferred to one a single standby Server, then provide enough processor resourcesyou should foresee a situation where all main Servers fail and ensure that standby Server has sufficient CPU, RAM and LAN on a standby Server in case when all main Servers become disabledresources.
Two Servers being standby for each other
Any Server can act both as a primary main and as a standby at the same time given that the performance of the Server platform allows it. Therefore, a Failover system can be organized with two video servers that are standby in relation to each other.
As in the cases described above, if both Servers write record the archive to the network storage, access to the archive is available when the configuration is transferred. If the Servers write record a local archive or use different network storages, the AxxonPlayer.exe utility (see The Axxon Player utility for viewing and converting the video archive) or synchronization through the Backup archive module (see Configuring archive synchronization of main and backup Servers) can be used to access the archive created by a the standby Server on NAS or on local drive.
Limitations of the Failover mode
The Failover mode is configured using the Failover service objects created under on the basis of the Computer objects corresponding to backup servers in the Hardware tab of the System settings dialog box.
...
If the quantity of cameras is bound to specific Servers in the license security key, then the license becomes invalid when cameras are moved to the backup Server. In this case the system gives 50 days to days to restore the faulty failed Server in order to move the cameras back and the license to become valid again. Otherwise, Axxon PSIM will unload on the backup Server because the hardware limit is exceeded (see Features Specifics of the Axxon PSIM software operation when the object limit is exceeded section). Time The time (in days) remaining for restoring the main Server is shown displayed on the settings panel of the Failover service object:
When you log off Axxon PSIM™, If Axxon PSIM is normally unloaded on the main Server, the configuration is not transferred from main Server to a standby serverto the standby Server.
In case of manual shutdown of the main Server, the configuration is also not transferred to the standby Server.
The number of failovers failover services running on a backup Server each computer simultaneously can be limited. For this the The Manager of Failover failover services object is used for this. It is created under on the basis of the Computer object ( that is not a the Client ) (see Role-assignment in distributed system section).
If the number of dead servers failed Servers exceeds the specified limit specified for , the backup Server, configuration from the new dead servers failed Servers will be transferred to the corresponding backup Server as previously dead servers restorethe previously failed Servers become operational.
Overview
Content Tools