Data-retention and housekeeping settings that control automatic cleanup and redaction of old call data.
Automatic cleanup (housekeeping)
Mividas Core stores a large amount of logs, synchronization and call-statistics data over time. To keep your database from growing without limit, Mividas Housekeeper can automatically delete this data once it reaches a certain age. This page controls whether that happens and how long each type of data is kept.
How the retention interval works:
- For each data category, you enter an interval – the length of time the data is kept. Anything older than the interval is removed the next time cleanup runs; newer data is always kept.
- Enter the interval as
DD HH:MM:SS(days, hours, minutes, seconds). Example:30 00:00:00keeps 30 days of data. - Leave the interval empty to disable cleanup for that category – that data is then never deleted automatically.
- Cleanup only runs when Enable automatic cleanup is switched on.
Important – Enabling automatic cleanup, or changing a schedule from e.g. 30 days to 10 days, will not create free space on the hard drive. The used up space will remain the same, but the space that was used can be re-used. For information on how to free up space from /var/logs, see FAQ below.
Cleanup settings
| Option | Description |
|---|---|
| Enable automatic cleanup | Master on/off switch for all housekeeping. When switched off, no data is ever removed, regardless of the intervals below. When on, Mividas checks roughly every 15 minutes whether any category is due for cleaning. |
| Save meeting room names when redacting call participants | When enabled (default), the meeting room name is kept while personal participant details (names and addresses) are removed. When disabled, the meeting room name is also removed. |
| Ts last run | Shows the date and time the automatic cleanup last ran. |
Cleanup schedules
| Interval | Type key | Description |
|---|---|---|
| acano_cdr Default: 30 00:00:00 | CMS CDR log. | Call Detail Records received from Cisco Meeting Server. |
| acano_cdr_spam Default: 10 00:00:00 | CMS CDR spambox log | Unmatched or discarded CMS CDR events (the “spam box”). |
| audit_log Default: empty | Audit log | Audit trail and policy log entries. |
| changed_meeting Default: 60 00:00:00 | Meeting changes | Superseded versions of meetings that were later changed. |
| email_log Default: 30 00:00:00 | Email log | Record of emails sent by the system. |
| endpoint_cisco_event Default: 30 00:00:00 | Cisco HTTP events | HTTP feedback events received from Cisco endpoints. |
| endpoint_cisco_provision Default: 30 00:00:00 | Cisco provisioning log | Log of provisioning actions sent to Cisco endpoints. |
| endpoint_data_file Default: 30 00:00:00 | Historical system information | Older snapshots of endpoint configuration and status changes. |
| endpoint_tasks Default: empty | Provisioning actions | History of completed or canceled endpoint provisioning tasks. |
| error_log Default: 30 00:00:00 | Error log | Recorded system error messages. |
| meeting Default: empty | Ended meetings | Information about meetings that have already finished. |
| pexip_eventsink Default: 30 00:00:00 | Pexip Event Sink | Event data pushed from Pexip via the event sink. |
| pexip_history Default: 30 00:00:00 | Pexip History API | Call history retrieved from the Pexip History API. |
| pexip_policy_log Default: 30 00:00:00 | Pexip Policy | Pexip external policy request log. |
| policy_auth_log Default: empty | Policy authentication log | Expired policy authorization records. |
| policy_auth_log_redaction Default: empty | Policy authentication log cleaning of overrides | Removes stored setting overrides from policy authentication records (anonymization, not deletion). |
| sensor_data 1 Default: empty | Sensor data | Room sensor readings such as people count, temperature and air quality. |
| statistics_full_delete 1 Default: empty | Full deletion of call statistics | Permanently deletes all call statistics data older than the interval. Use with care. |
| statistics_invalid_calls 1 Default: 60 00:00:00 | Invalid calls | Calls that have no valid participants. |
| statistics_invalid_legs 1 Default: 60 00:00:00 | Invalid call participants | Participant records that do not count towards statistics (for example, calls under 60 seconds, or chat/presentation/distribution legs). |
| statistics_redaction 1 Default: empty | Redaction of participant information | Anonymizes participant records by removing names and addresses. The data is retained for statistical purposes, but personal details are anonymized. |
| synced_mcu_data Default: 60 00:00:00 | Previously synced MCU information | Cached provider objects (for example, meeting rooms, URIs, and users) that are no longer active on the provider. |
| trace_log Default: 1 00:00:00 | Trace log | Detailed diagnostic trace data (verbose; kept only briefly). |
| vcs_calls Default: 30 00:00:00 | VCS/Expressway call history | Call history collected from Cisco VCS/Expressway. |
- Enabling/changing these will affect data presented in the product, e.g., sensor data or call statistics.
FAQ
Here are some frequently asked questions (FAQs) to help you find the answers you’re looking for.
To clean up the /var/log directory when it’s full, you can follow these steps using SSH or the Mividas Installer console:
Check and Identify Large Files
Identify the largest folders in /var/log:
sudo du -xh /var/log | sort -h | tail -n40List files by size within the /var/log and /var/log/docker/ directories to locate the largest log files:
ls -shSr /var/log/
ls -shSr /var/log/docker/Delete Unnecessary Log Files
Delete specific old log files one at a time:
sudo rm /var/log/<file_name>Bulk delete compressed log files:
sudo rm -f /var/log/*.log.[1-4].gzRun Hard Drive Cleanup from the Mividas Installer Console
Access Hard drive cleanup options in the Mividas Installer console:
- Debug logs/raw call data: Remove old debug logs and raw call data.
- Old versions: Remove old versions of components or software.
Clean Up Docker Resources
Remove unused Docker images if they’re no longer needed:
sudo docker image prune -fNote: Only perform Docker cleanup when all Mividas components are active and running. If components are missing or inactive, this can lead to further cleanup or redeployment needs, particularly for offline systems.
Remove all unused Docker resources (images, containers, networks):
sudo docker system prune -fClean up any Docker resources that are not currently in use:
sudo docker system prune -afBy following these steps, you can manage storage in /var/log effectively without compromising system stability.