Scheduling
The installer sets up a daily cron job at 02:00 automatically. To customize:
# Root install
sudo nano /etc/cron.d/calmbackup
# User install
crontab -e
# View logs
journalctl -t calmbackupMake cron’s environment explicit
Cron may run as a different user or with a different PATH from your interactive shell. Use the installed binary path and an explicit configuration path when needed. Check database-tool access, directory permissions and available local space.
Choose a schedule from your recovery needs
Ask how much changed data you can afford to recreate, then account for the duration and load of a complete backup. Avoid overlapping runs against the same source.
When a run is missing
Check that the host was online, cron executed, and the process could reach the database and upload destination. Compare local logs with the cloud backup history. A local encrypted file alone does not establish that an off-machine upload completed.
Understand failed and missed backups →