database
8 posts.
How to migrate from OSDial to VICIdial
OSDial is a VICIdial fork with a near-identical database schema. Moving to a current VICIdial install is mostly a schema-diff exercise, not a re-platform. Here is the practical path.
Read postRunning the VICIdial database on its own server
Splitting MySQL onto a dedicated database server frees the telephony box for Asterisk and opens the door to replication. Here is when and how to do it.
Read postMoving VICIdial to new server hardware
Migrating VICIdial to a new box is five jobs: dump the database, sync recordings, cut over the IP and DNS, rebuild the config, and re-register your trunks.
Read postA backup strategy for a VICIdial server
A real VICIdial backup covers three things: the database, the recordings, and the config. Here is what to dump, how often, and where to keep it.
Read postRunning a VICIdial database schema upgrade
When VICIdial code expects new columns, you run the upgrade SQL script to bring the schema forward. Here is what the ALTER scripts do and how to run them safely.
Read postSetting up MySQL/MariaDB for VICIdial
What VICIdial needs from its database: the asterisk database, the cron and DB users, MyISAM tables, basic tuning, and keeping the DB on the right box.
Read postDiagnosing slow reports and why they can stall the whole system
Slow reports do more than test your patience — they can stall the whole dialer. The Admin Report Log Viewer shows each report's run time so you can find the offender.
Read postDatabase and Asterisk reload issues: a safe order of operations
Restarting the database or Asterisk under load drops calls. Here is the safe order: make the admin change, let the keepalive apply it, then reload only if needed.
Read post