Skip to main content
The Backup History page lists every backup run across all your jobs, most recent first.

​
What’s shown

​
Investigating a failure

Click on a failed run to see its full error message. Common causes include:
  • The database doesn’t exist, or the name was typed incorrectly
  • The database credentials are no longer valid
  • The agent lost its connection partway through the backup
  • The storage destination rejected the upload, for example due to invalid credentials
See Backup Failures for help resolving specific errors.

​
Retention

savemydb doesn’t currently delete old backup history entries automatically. If you’ve configured your own S3 or Dropbox storage, you can set retention rules directly with your storage provider to manage how long backup files themselves are kept.