Infrastructure

Database Replication

Database replication in VICIdial is the process of automatically copying the MySQL database from a primary (master) server to one or more secondary (slave) servers in real time. Replication provides data redundancy (protecting against data loss if the primary server fails), read scaling (distributing database queries across multiple servers), and disaster recovery capability for VICIdial clusters.

How It Works in VICIdial

VICIdial’s database stores all operational data: lead records, agent activity logs, campaign configurations, recordings metadata, dispositions, call detail records, and real-time agent states. In a replicated configuration, the primary MySQL server handles all write operations (inserts, updates, deletes), and these changes are replicated to secondary servers through MySQL’s binary log replication.

Two primary replication topologies are used in VICIdial deployments. Master-slave replication sends all writes to a single primary server and replicates to read-only slaves — VICIdial’s reporting queries can be directed to slaves, reducing load on the primary. Galera Cluster provides multi-master replication where any server can accept writes, with synchronous replication ensuring data consistency across all nodes.

VICIdial’s AST_DB_dead_server_check.pl process monitors replication health and can trigger alerts when replication lag exceeds thresholds. The hopper process, real-time monitoring, and agent screens all depend on database performance, making replication health critical.

Why It Matters

The MySQL database is the single most critical component in a VICIdial deployment. All call center operations — dialing, agent routing, lead management, and reporting — depend on database availability and performance. A database failure without replication means total system downtime and potential data loss.

For VICIdial deployments handling more than 100 agents or requiring high availability, database replication should be considered mandatory. Master-slave replication provides basic redundancy and read scaling. Galera Cluster provides automatic failover with no data loss. See the VICIdial cluster guide for database replication architecture and configuration guidance.

Related Terms

VICIdial Cluster View definition → Load Balancing View definition → Hopper View definition →

Related Articles

VICIdial Optimization

VICIdial New Features: Everything You Need to Know

· 22 min read
Technical Guides

VICIdial Cloud Deployment: AWS, GCP & DigitalOcean

· 18 min read
Compliance

VICIdial DNC List Management: Federal, State & Internal

· 22 min read

Part of the VICIdial Performance Optimization Guide

Need Help With Your VICIdial Setup?

Get a free performance audit from our team of VICIdial experts. We'll identify quick wins and long-term improvements.

Get Your Free Audit →