Redundancy with Shinobi Failover Servers

Shinobi Core servers can experience unexpected downtime. A failover server mitigates this risk by automatically assuming operations when the primary server goes offline. During downtime, the failover captures recordings and events, then synchronizes this data back to the restored Core server.

What is this feature?

This feature provides backup redundancy for Shinobi Core servers. When a main server becomes unavailable, all cameras and user accounts automatically transfer to the failover server. Once the primary server returns online, recorded footage and events sync back automatically. Multiple failover servers can be deployed for enhanced reliability.

• Critical requirement : both servers need activation with separate license keys.
• Status note : as of the article date, this functionality exists only in the feature-failover branch, with planned merges to dev (early May 2026) and master (early June 2026).

How does it work?

The configuration involves four straightforward steps.

• Deploy two Shinobi servers — one primary with active cameras, one designated for failover duty.
• Enable failover mode via configuration settings.
• Generate a connection key on the failover server.
• Link the primary server to the failover using the connection key.

Configuration note : cloud uploaders are disabled on failover startup by default but can be enabled through configuration settings.

Configuring the Failover Setup

For the Failover Server

• Access the Superuser panel, navigate to Configuration, and toggle isFailover to active.
• For cloud upload continuation, enable failoverAllowCloudUploaders.
• Configure the video storage directory path — this doesn't mirror from the Core server.
• After saving and restarting Shinobi, access the Failover Keys tab to create an authentication key for the Core server's use. No restart is needed after key generation.

For the Core Server

• Log into its Superuser panel and access Failover Servers.
• Input the failover server's web address and previously created key, formatted as : ws://[IP]:[PORT]/failover
• Save settings — connection should establish immediately. Test functionality by taking the Core offline.

ws://10.1.103.100:8080/failover

Pro Tip: Central Management

Connecting both servers to a Central Management Portal enables monitoring from a unified interface. An account named [email protected] automatically appears — preserve this account as it's required for monitoring functionality. You can switch between accounts to check each server's status anytime.

• Setup resource : Central Management documentation