Reports & alerts

Less guessing. A clearer backup history.

Understand what completed, choose how success emails arrive, and know what to investigate when a backup is missing or fails.

Start free trial
White report sheets emerging from an envelope with amber accents

Ask AI about CalmBackup

See what it does, who it’s for, and whether it fits your needs.

Opens with product context and a link to this page.

View or copy the prompt

Daily overview or immediate updates

Choose the success emails you need.

CalmBackup offers two success-notification preferences: an email after each confirmed backup or a daily digest that groups successful backups. New accounts default to the digest preference.

These messages report backup activity. They do not certify that a full application restore exercise has taken place. Use the recovery guide to establish that separate routine.

01

Immediate

Useful while setting up a new source or investigating a schedule. Receive confirmation as individual backups complete.

02

Daily digest

Useful once the routine is established. Review successful activity together rather than receiving an email for every run.

Manage notification preferences

02 / Reports & alerts

Read a status with its context.

A timestamp without the right source is not useful reassurance. Use meaningful source names and labels so you can distinguish production, staging and separate applications.

SignalWhat it tells youWhat to check next
Confirmed backupThe API accepted the client’s upload confirmation metadata.Confirm the expected source, time and backup size.
Backup failedA backup operation reported an error.Read the error and check credentials, database tools, storage and network access.
Backup missedExpected backup activity was not observed by the missed-backup detector.Check that cron ran and the host was online.
Restore failedA client restore reported an error.Check the selected archive, encryption key, destination and database tools.

03 / Reports & alerts

Investigate the process, not just the email.

The backup workflow from database export to encrypted storage
  1. 01

    Check the source machine

    Confirm it is online, has free disk space and can reach the database and the upload destination.

  2. 02

    Check the scheduled command

    Review the user running cron, the binary path and the configuration file it loads. A working interactive shell does not guarantee the same environment in cron.

  3. 03

    Review the log and latest backup

    Compare the error with the latest confirmed backup. Re-run the backup only after identifying whether the previous attempt finished or needs attention.

  4. 04

    Confirm recovery separately

    When the backup flow is healthy again, make sure your recovery exercise and key copy are still current.

Review scheduling and logs
An amber backup snapshot ready to recover

A calmer place to start

Your next backup.
Your first recovery rehearsal.

Connect a source, keep your encryption key safe, and try a restore. Make the whole routine familiar before you need it.

Start your 14-day trial

Plans from $5/month. See pricing