Data Sync

When you make a change in Configuration Manager, the system automatically generates configuration files and applies them. In an all-in-one deployment this happens instantly on the same server. In a cluster, changes must be synchronized to all servers.

How It Works

1. You save a change in Configuration Manager
2. The change is recorded with a version number
3. Configuration files are regenerated
4. Commands are queued (e.g., reload PBX dialplan, refresh Kamailio routing)
5. The sync agent (cacher) picks up the commands and executes them

In cluster mode, file synchronization (via lsyncd) replicates configuration files to Worker nodes before commands execute. Each server runs its own sync agent that processes only its own commands.

Monitoring Sync Status

Use Data Sync (under Tools > Data Sync) to check:

• Whether the sync agent is running on each server
• Current sync version per server vs. the latest configuration version
• Any pending or failed commands

The Change Log shows all configuration changes with version numbers, useful for correlating issues with specific changes.

Troubleshooting

Common sync issues:

• Sync agent not running — check with systemctl status cacher on the affected server
• Server version behind — the server may have missed commands; check cacher logs
• File sync delay (cluster only) — check lsyncd status on the Manager node