Go to documentation repository
Page History
...
| Info | ||
|---|---|---|
| ||
The following migration time is confirmed in both directions (i.e. from the Main Server to the standby Server and vice versa):
The archive size tested was more than 5TB and the Servers hardware as follows: |
In the case of a normal shutdown of Axxon PSIM on the main Server, the configuration is not transferred to the backup Server.
In case of manual shutdown of the main Server, the configuration is also not transferred to the backup Server.
Examples of Failover system organization
...
The AxxonPlayer.exe utility can be used to access the archive created by the standby Server on NAS or local drive (see Axxon Player documentation). 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 N main Servers + standby server flowchart when archive is recorded to one NAS:
If configuration from several main Servers is transferred to a single standby Server, you should foresee a situation where all main Servers fail and ensure that standby Server has sufficient CPU, RAM and LAN resources.
...
Any Server can act both as a 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 record the archive to the network storage, access to the archive is available when the configuration is transferred. If the Servers record a local archive or use different network storages, the AxxonPlayer.exe utility (see Axxon Player documentation) 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 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 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 security key, then the license becomes invalid when cameras are moved to the backup Server. In this case the system gives 50 days to restore the 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 Specifics of the Axxon PSIM operation when the object limit is exceeded). The time (in days) remaining for restoring the main Server is displayed on the settings panel of the Failover service object:
If Axxon PSIM is normally unloaded on the main Server, the configuration is not transferred to 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 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.
Overview
Content Tools