The MxHub offers a failover recording to provide redundancy of the recording server.
If the “Main Recording Server” fails or has problems, the Failover Recording Server steps in for it and takes over the tasks of the “Main Recording Server” as long as it is not functional.
The system checks the availability every 0.5 seconds.
How to configure a failover system you can see in this article
If you do not use a domain setup with an Active Directory server (AD), but a workgroup setup, follow these steps:
- Log into Windows using an account that is part of the local Administrators group and has full permissions on the Windows system.
Note: In a distributed MxHub setup make sure to use the same account with the same password on all computers in the system.
Main PC: Username: hub (Local Administrator) PW: 12345678
Failover PC: Username: hub (Local Administrator) PW: 12345678
1. Add the Windows User to the Administration Role in Management Client
→ ManagementClient → Security → Roles
Click on Add and choose Windows User
Fill in your created windows user and click on Check Names
Windows User “hub” is now a part of the Administrator Role
2. Download the Recording Server from the Administration Page
3. Install the Recoding Server on an other Windows Machine
Note:: You must create the same Windows user on the 2nd PC as on the main computer…
Select the prefered language for the installer
Enter the Adress of the ManagementServer
Select a location where the recordings and database should be located
Click on Browse and search for your windows user (hub)
Enter the password of this windows user
Select your installationlocation
After some minutes the installation should be finished
4. Install the latest Device Driver
To have full support of the latest cameras, the latest device driver package should be installed afterwards.
=> After a successfull installation you can see the following 2 symbols.
5. Check if the Failover Server is registered in the ManagementClient
→ ManagementClient → Failover Servers
Important Note: A Recording Server is capable of running without limitations in environments such as these, however a Failover Recording Server will be unable to provide the Management Server with status information due to a reliance on Windows authentication as of version 2020 R3. We hope to be able to remove this limitation soon. With that said, it is still possible for a Failover Recording Server to detect the failure of a Recording Server, assume the appropriate configuration, and take over recording responsibility, provide live and recorded playback to clients, and deliver recordings to the original Recording Server when it becomes available again. But the Failover Recording Server will always show “Connection is broken” with a yellow caution symbol in the Management Client and you will not be able to trigger the “failover started” and “failover stopped” events in the Rules engine.
6. Activate the Faoliver Server in ManagementClient
→ ManagementClient → Recording Servers → “Choose your Recording Server” → Failover
Click on “Primary failover server group” → Add new
Select your Failover Server in the list of available servers and click on Add
Click on Advanced failover settings…
Now you can decide what the failover server should take over in case of a failure
Now the Failover Server is finished and ready
→ Stop the Recording Server on the Main Machine
→ Check if the Recording Server on your Failover System is started and ready
→ Start the Recording Server on the Main Machine
→ Check if the Recording Server on your Failover System ist stopped
→ Check the Recordings while the Main Recording Server is offline and when the connection is OK again