Failover feature provides maximum possible uptime for the Userful server. Failover requires two Userful servers to be located on the same subnet; if that is the case, then if the Primary server fails, the Secondary server takes over the network receiver devices of the Primary i.e. failed server.
This page outlines the best practices and steps to take when preparing for and executing failover procedures using network receiver devices.
Before configuring failover group, following requirements and caveats must be met:
1. Primary-Secondary Relationship
- Although all members in the failover group are equivalent; we still suggest that user should indicate one server as the Primary and the other as the Secondary
- Primary is the server with assigned display(s) that is configured and added first when a failover group is created.
- Secondary is the server without any assigned display(s) but only with the onboard display running.
2. Same Hardware Specifications
- Both Userful servers should have similar hardware specifications.
3. Same Working Environment
- Both Userful servers should have an identical version of all the software packages (especially the "userful-control-center" package).
4. Same Media Content
- Any local content must be added manually to both servers and CMS subscription may be required for both servers.
The first step in setting failover group is to Enable Failover on the Primary server.
- Open Control Center > Settings > Failover Group Settings.
- Select Enable Failover.
- Allow Control Center to restart.
Define Failover Group
The next step is to define the failover group, i.e. the failover relation among two servers.
Follow the below mentioned steps to define failover group:
- Open Control Center of the Primary server.
- Go to Settings > Failover Group Settings.
- Enter the Group Name and click Create Group to create a new group.
Any server can join the Failover group as a Secondary server irrespective of the (i.e., valid or expired) status of the Maintenance and Support contract.
Select the Failback Setting to be "Automatic" or "Manual" depending on the use case.
"Failback" occurs once the Primary server comes back online where the failed over displays from the Secondary server will be re-assigned back to the Primary server. This failback can happen automatically or manually as mentioned above.
Assigning a Backup Server
- Log in to your backup server and follow the below steps:
- Open Control Center.
- Go to Settings > Failover Group Settings
- Select Enable Failover and allow Control Center to restart.
- Go back to Failover Group Settings.
- Add your backup server to the group you created earlier by selecting Join an existing group and selecting the desired group from the drop-down.
- Click Join Group button.
Please note that joining an existing failover group will copy and overwrite current display mapping with the display mapping from the failover group's shared database.
Testing the Failover Process
- Ensure that the "Primary" server and "Secondary" server are both online under the same subnet
- Shutdown or unplug the network cable from the "Primary" server
- Within few seconds, the displays that were assigned to the Primary (failed) server will come back online; but these displays are now running on the "Secondary" server as failover displays.
Please note that the failover displays have orange display icon with the display ID
- Reboot or plug the network cable back to the Primary server.
- Within few seconds, all failover displays will unassign from the "Secondary" server and restored back to the "Primary" server automatically or manually depending on the Failback Setting selected.