# Less guessing. A clearer backup history.

> Understand confirmed, failed and missed backups. Explore success emails, daily digests and the checks to make when a scheduled backup needs attention.

Canonical page: https://www.calmbackup.com/reports

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

[Start free trial](https://app.calmbackup.com/register)

## 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.

### Immediate

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

### Daily digest

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

[Manage notification preferences](https://app.calmbackup.com/settings/notifications)

## 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.

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

## Investigate the process, not just the email.

1.  ### Check the source machine
    
    Confirm it is online, has free disk space and can reach the database and the upload destination.
    
2.  ### 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.  ### 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.  ### 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](https://www.calmbackup.com/docs/scheduling)
