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 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 N main Servers + standby server 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 on the standby Server, then the archives from different main Servers will mix.
The AxxonPlayer.exe AxxonPSIM player utility can be used to access the archive created by the standby Server on NAS or local drive (see Axxon Player documentation The AxxonPSIM 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).
...
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 AxxonPSIM player utility (see Axxon Player documentation The AxxonPSIM 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 the standby Server on NAS or on local drive.
Overview
Content Tools