Skip to main content

Automatic Failover

When your master server fails, Tergum automatically redirects traffic to the slave.

Failover Process

  1. Detection: Master heartbeats stop (60-90 seconds)
  2. Verification: Confirm slave is healthy
  3. DNS Update: Cloudflare DNS pointed to tunnel
  4. Notification: Email sent to configured addresses

What Changes During Failover

  • DNS record updated to Cloudflare Tunnel endpoint
  • Traffic flows through tunnel to slave server
  • Master can be offline for recovery

After Failover

Your options:

  1. Fix master and fail back: Restore master, sync data, update DNS
  2. Promote slave permanently: Continue using slave as new master

Manual Failover

Trigger failover manually from dashboard:

  1. Go to domain settings
  2. Click "Trigger Failover"
  3. Confirm action

Useful for testing or planned maintenance.