Other income report tables<\/strong> \u2013 keep for X days.<\/li>\n<\/ul>\n\n\n\nYou can also enable automatic cleanup of:<\/p>\n\n\n\n
\nAccounts<\/strong> \u2013 delete accounts that have been inactive\/expired for X days.<\/li>\n\n\n\nGateways<\/strong> \u2013 delete gateways belonging to deleted accounts.<\/li>\n\n\n\nPhones<\/strong> \u2013 delete phones belonging to deleted accounts.<\/li>\n<\/ul>\n\n\n\nHow Auto\u2011Cleanup Works<\/h3>\n\n\n\n Once enabled, a background process runs daily (typically at low\u2011traffic hours) and:<\/p>\n\n\n\n
\nIdentifies tables older than the configured retention period.<\/li>\n\n\n\n Drops those entire tables (fastest method).<\/li>\n\n\n\n Logs the action in system logs for audit.<\/li>\n\n\n\n If configured, deletes orphaned accounts\/gateways\/phones.<\/li>\n<\/ol>\n\n\n\n\u26a0\ufe0f Important:<\/strong> Auto\u2011cleanup deletes entire tables<\/strong>, not individual rows. This is extremely fast and efficient but means you cannot keep partial months \u2013 it’s all or nothing per table.<\/p>\n\n\n\nRecommended Retention Periods – VOS3000 Data Maintenance<\/h2>\n\n\n\n Based on typical VoIP operations, here are sensible starting points:<\/p>\n\n\n\nData Type<\/th> Retention Period<\/th> Reason<\/th><\/tr> CDRs<\/td> 90 days<\/td> Enough for customer disputes and traffic analysis; older data can be archived externally.<\/td><\/tr> System logs<\/td> 30 days<\/td> Security audits rarely need older logs; export if longer retention required.<\/td><\/tr> History alarms<\/td> 60 days<\/td> Alarm patterns over two months help identify recurring issues.<\/td><\/tr> Payment records<\/td> 365 days (or longer for compliance)<\/td> Financial records may need 1\u20117 years depending on local laws \u2013 adjust accordingly.<\/td><\/tr> Data reports<\/td> 30 days<\/td> Reports can be regenerated from CDRs if needed.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nBackup Strategy Before Cleanup – VOS3000 Data Maintenance<\/h2>\n\n\n\n Before enabling auto\u2011cleanup or running manual deletes, ensure you have reliable backups:<\/p>\n\n\n\n
\nDaily mysqldump<\/strong> of the entire VOS3000 database (compressed).<\/li>\n\n\n\nBinary logs<\/strong> for point\u2011in\u2011time recovery (if you need to restore to a specific moment).<\/li>\n\n\n\nOff\u2011site storage<\/strong> \u2013 keep backups on a different server or cloud storage.<\/li>\n<\/ul>\n\n\n\nTest your backups regularly by restoring to a test environment.<\/p>\n\n\n\n
Monitoring Disk Space<\/h2>\n\n\n\n Even with auto\u2011cleanup, monitor disk usage:<\/p>\n\n\n\n
\nUse System Management > Server Monitor<\/strong> to see disk usage trends.<\/li>\n\n\n\nSet up Disk Alarm<\/strong> under Alarm Management to notify you when disk usage exceeds thresholds (e.g., 80%, 90%).<\/li>\n\n\n\nCheck MySQL data directory size periodically: du -sh \/var\/lib\/mysql<\/code><\/li>\n<\/ul>\n\n\n\nAdvanced: Archiving Old CDRs<\/h2>\n\n\n\n If you need to keep CDRs longer than auto\u2011cleanup allows, consider archiving:<\/p>\n\n\n\n
\nExport old CDR tables to CSV or SQL files.<\/li>\n\n\n\n Compress and store them in a secure location.<\/li>\n\n\n\n Delete the tables from the live database (either manually or via auto\u2011cleanup).<\/li>\n\n\n\n If you need to query archived data, import into a separate reporting database or use command\u2011line tools.<\/li>\n<\/ol>\n\n\n\nVOS3000 does not include built\u2011in archival tools, but you can script this using mysqldump<\/code> and cron<\/code>.<\/p>\n\n\n\nFrequently Asked Questions (VOS3000 Data Maintenance)<\/h2>\n\n\n\nWill auto\u2011cleanup delete accounts that still have active phones?<\/h3>\n\n\n\n No. Auto\u2011cleanup only deletes accounts that have been expired and have no associated active phones, gateways, or bind numbers. It checks dependencies before deleting.<\/p>\n\n\n\n
Can I recover data after auto\u2011cleanup deletes it?<\/h3>\n\n\n\n Not from the live system. You must restore from backups if you need deleted data. This is why testing your backup restoration process is critical before enabling auto\u2011cleanup.<\/p>\n\n\n\n
Does deleting CDR tables affect current calls?<\/h3>\n\n\n\n No. VOS3000 writes CDRs to a temporary table and moves them to the daily table after the call ends. Deleting old tables has no impact on ongoing calls.<\/p>\n\n\n\n
Why are my CDR tables not being deleted even though auto\u2011cleanup is enabled?<\/h3>\n\n\n\n Check that the retention period is set correctly and that the cleanup process is running (system logs will show cleanup actions). Also ensure that the tables are indeed older than the retention period \u2013 auto\u2011cleanup runs daily, so tables become eligible only after the configured number of days have passed since their creation.<\/p>\n\n\n\n
Can I keep payment records forever while auto\u2011deleting CDRs?<\/h3>\n\n\n\n Yes. Each data type has independent retention settings. Set payment records to a high value (e.g., 3650 days) and CDRs to a lower value (e.g., 90 days).<\/p>\n\n\n\n
Conclusion<\/h2>\n\n\n\n Proper VOS3000 data maintenance<\/strong> ensures your softswitch runs smoothly, queries stay fast, and disk space never becomes a crisis. Whether you prefer manual control or fully automated cleanup, VOS3000 provides the tools you need. Start with conservative retention periods, monitor the results, and adjust as you gain confidence.<\/p>\n\n\n\nNeed help setting up data maintenance or recovering from a disk space emergency? Contact us on WhatsApp: +8801911119966<\/strong><\/p>\n\n\n\n