Stream Backup
Automatically move listeners to a backup server if your main stream fails
What Is Stream Backup?
Duplicate infrastructure in a different location that takes over automatically
The Problem
Single point of failure: One server means if ANYTHING goes wrong at that location, your stream dies.
The Solution
Zero single point of failure: Primary fails → DNS redirects → Backup takes over → Listeners never notice.
Who needs this: DAB stations (license compliance requires uptime), professional networks, stations with revenue dependencies, or anyone who absolutely cannot afford downtime.
Why Stations Choose Stream Backup
Critical protection for stations where downtime has real consequences
Target 99.99% Uptime
Engineered for maximum reliability. Primary datacenter fails? Backup takes over within 30 seconds. Listeners experience brief buffering at worst.
We run this infrastructure for DAB stations where regulatory compliance demands continuous operation. Your station gets that same level of engineering.
Separate Datacenters
Different buildings, different cities, different network providers. True geographic redundancy.
Constant Health Monitoring
DNS checks every 30 seconds. Detects failures instantly and redirects traffic automatically.
DAB License Compliance
Meet regulatory uptime requirements. Sleep at night knowing you're compliant.
Who Needs Stream Backup?
DAB Stations
License compliance requires continuous operation. Ofcom doesn't accept "datacenter was down" as an excuse.
Backup stream ensures regulatory compliance
Revenue-Dependent Stations
Live advertising, sponsorship commitments, or revenue tied to listener count. Downtime = lost money.
Backup protects your revenue stream
Professional Networks
Multi-station operations or white-label providers who serve clients. Your reliability is your reputation.
Backup protects your professional reputation
Syndicated Show Producers
Provide "self-healing" service to client stations. Your stream stays up even if your datacenter goes down. Professional reliability.
Backup ensures your show reaches all stations
How Automatic Failover Works
DNS health checks detect server failures and redirect traffic automatically
Normal Operation: Your studio broadcasts to BOTH servers simultaneously (they stay in sync). DNS points listeners to Server 1 (primary). Server 2 is on standby.
Both servers receive your audio. Only the primary is serving listeners. DNS health checks monitor Server 1 every 30 seconds.
Key Point: Stream Backup protects against OUR infrastructure failing. AutoDJ protects against YOUR source failing. Combined, you have complete redundancy at every level.
Complete Professional Solution
Stream Backup works seamlessly with our other premium services while maintaining full redundancy
Cloud Silence Detection
Add-on ServiceDetects audio silence (equipment failure, cable unplugged) and automatically triggers AutoDJ failover on BOTH servers simultaneously.
Maintains Redundancy: Silence detection runs on both Server 1 and Server 2. If primary server fails, backup server's silence detection continues protecting you.
- Detects silence within seconds
- Triggers AutoDJ on both servers
- Works during DNS failover
Cloud Audio Processing
Add-on ServiceProfessional audio compression, limiting, and loudness normalization applied server-side on BOTH servers before distribution.
Maintains Redundancy: Processing configured identically on both servers. Your audio quality stays consistent regardless of which server is active.
- Broadcast-grade processing
- Identical config on both servers
- No client-side processing needed
Stream Backup + Optional Add-ons
All services work together while maintaining complete redundancy
Professional Insight: Every service is configured identically on both servers. Failover is transparent - listeners can't tell which server they're using.
Dual Source + Dual Server
Enterprise-grade: Lose one encoder AND one server - still on-air
This is a setup option for your Stream Backup service - no additional products needed. You choose how to configure your redundancy.
All Systems Normal: Encoder 1 broadcasts to Server 1 /primary and Server 2 /primary. Encoder 2 broadcasts to Server 1 /secondary and Server 2 /secondary as fallback.
Server 1 serves listeners using /primary mountpoint. If Encoder 1 fails, Server 1 switches to /secondary (Encoder 2). Complete redundancy at source level.
How I'd run my own station: Dual encoders on separate internet connections. Dual servers in different datacenters. Total redundancy at every level. This is professional broadcast engineering.
Technical Implementation
How we achieve true redundancy
Dual Server Setup
DNS Failover System
Optional: Dual Source Setup
Your Choice - No Extra CostWant even more redundancy? Run two encoders (separate internet connections, different power sources) broadcasting to both servers simultaneously using Icecast mountpoint fallback.
One encoder → both servers. DNS failover protects against server/datacenter failure.
Two encoders → both servers. Protects against encoder AND server failure simultaneously.
Fully compatible with Stream Machine: The dual source setup shown in the Advanced Redundancy diagram works with your existing backup service. Configure Icecast mountpoints (/primary and /secondary) on both servers - no additional cost, just setup preference.
Plain English: You broadcast to both servers (they stay in sync). DNS health checks monitor the primary. If primary fails, DNS automatically points listeners to the backup. Failover is transparent - listeners experience a brief buffering pause at worst, not complete silence.
Add Stream Backup Protection
Enterprise redundancy for your existing stream hosting
Backup Transmitter Feed
What's Included:
- Ensure continuous broadcasting even when the unexpected happens. The Backup Transmitter Feed provides a fully redundant secondary streaming account designed for ultimate reliability
- Your backup feed operates on a completely separate server, in a different data centre, using distinct bandwidth providers from our primary setup. Diverse Infrastructure
- If your main stream faces disruption—whether from service failure, maintenance, or malicious attacks—the Backup Transmitter Feed instantly activates your secondary feed. Intelligent, Automatic Switching
- The system automatically reverts to your primary stream once it becomes available again. Seamless Restoration
- This entire failover and recovery process is fully automated, keeping you live without you needing to lift a finger. Zero Intervention Required
Requires active stream hosting account. Contact us if you need a custom configuration.
Common Questions
How fast is the failover?
DNS checks run every 30 seconds. When a failure is detected, DNS redirects within 30 seconds. Most listeners experience a brief buffering pause (similar to poor mobile signal), then playback resumes. Total interruption: typically under 2 minutes.
Do I need to change my stream URL?
No. You use a single DNS hostname (e.g., stream.yourstation.com). We manage the DNS failover behind the scenes. TuneIn, your website, and apps all use the same URL - they don't need to know about the backup.
How do I broadcast to both servers?
Your encoder (BUTT, Mixxx, etc.) connects to both servers simultaneously. MediaCP on both servers stays in sync. We provide setup instructions and assistance - it's typically just adding a second connection in your encoder.
What if backup server also fails?
Statistically extremely unlikely (different datacenters, providers, power sources). But if it happens, DNS would redirect back to primary when it recovers. For triple redundancy, contact us - we can architect custom solutions.
Protect Your Broadcast
Add Stream Backup to your existing hosting plan
Or contact our engineers to discuss custom redundancy solutions
Broadcasting Glossary • New to technical terms? Our glossary explains encoders, datacenters, DNS, mountpoints, and more.
