EE Push

Backups & Rollback

EE Push creates automatic database backups before every deployment, giving you a safety net to rollback if something goes wrong.

Automatic Backups

Before each deployment, EE Push runs mysqldump to create a complete database backup. The backup file is stored on the server and its path is recorded in the deployment log.

Default backup location:

system/user/cache/ee_push_backups/deploy_42_20260212_143022.sql

You can change the backup directory in Settings > Backup Path.

Skipping Backups

You can skip the backup when starting a deployment by checking Skip Backup. This is not recommended for production deployments. If you skip the backup, rollback will not be available for that deployment.

Backup Retention

Configure how long backups are kept in Settings > Backup Retention. The default is 30 days. Old backups are cleaned up automatically.

Rolling Back

If a deployment causes problems, you can rollback to the pre-deployment state:

  1. Go to Deployment Logs
  2. Find the deployment you want to rollback
  3. Click View Log
  4. Click the Rollback button
  5. Confirm the rollback

What Rollback Does

  • Restores the database from the backup SQL file using mysql import
  • Marks the deployment status as rolled_back
  • Appends rollback details to the deployment log

What Rollback Does Not Do

  • It does not revert file changes (Git commits are not reversed)
  • It does not restore uploaded files or media
  • It does not affect server configuration
For a complete rollback including code, you would need to manually deploy the previous Git commit after restoring the database.

Rollback Eligibility

A deployment can be rolled back if:

  • Its status is success or failed
  • A database backup file exists and is accessible
  • It has not already been rolled back

The Rollback button only appears on the log detail page when all conditions are met.

Backup Requirements

  • mysqldump must be available on the server (typically installed with MySQL/MariaDB)
  • The PHP process must have permission to write to the backup directory
  • Sufficient disk space for the database dump