VICIdial Database Maintenance

Originally published at vicistack.com . Follow us for more call center engineering content. Last updated: March 2026 | Reading time: ~26 minutes Your VICIdial server is going to crash. Not might. Will. The only question is whether it crashes at 2 AM on a Saturday when nobody cares, or at 10:30 AM on a Monday when 80 agents are mid-call and your operations manager is standing behind you asking why the phones died. The difference between those two scenarios is database maintenance. VICIdial generates an absurd amount of data — call logs, agent events, recording metadata, hopper entries, disposition history, carrier logs — and if you don't actively manage that data, your MySQL tables will grow until they corrupt, your disk will fill until the OS stops writing, and your queries will slow until the real-time report takes 45 seconds to load. I've rebuilt VICIdial databases from crashed systems more times than I want to admit. Every single one was preventable with a maintenance schedule that