Troubleshooting Backup & Restore

If you encountered errors, they possibly can be corrected.


🥸 Your issue is not listed…?

Please consult the Zammad Community for technical assistance.

Exit Codes

Our backup & restore scripts come with exit codes to help you finding a solution. However, we do not guarantee a complete error handling.

Beside the exit codes, there are also error messages returned to standard out.

Exit code list


Description / Situation


The script finished successfully (or the error is not handled).


This is a general error. Most often used for script aborts due to incorrect information provided or information missing.


There was an error with database handling. This usually either happens if your database server does not meet script requirements, login data being invalid or „broken‟ database dumps.


There were issues with file / folder permissions.


Here’s some classics you may encounter.

password authentication failed or peer authentication failed

This indicates that the password of your Zammad DB user is either different from your database.yml or the wrong database server may be contacted.

„But my Zammad instance is running, how can it be wrong?‟

Zammad may fall back to socket connection which is why you didn’t notice.

What to do …

Ensure that the provided user credentials are correct. You can also consider to use the Database Helper: (re)set password script, you can find in the backup directory.

Ident authentication failed for user

This indicates your database server does require ident authentication. That authentication method is not supported by our scripts.

What to do …

Check pg_hba.conf of your PostgreSQL-Server and adjust it if needed.

Usually authentication can be allowed like so:

host    all             all               md5
host    all             all             ::1/128                 md5

Please consult the offical PostgreSQL documentation for this, as this is out of our documentation scope.

WARNING: You don't seem to have any attachments in the file system!

This indicate you’ve set FULL_FS_DUMP to no but your instance currently does not save attachments to file system.

This warning will be shown once before creating an empty directory to allow the backup process to continue successfully.

If you believe that this is an error, please see Storage Settings. In case the issue posts, please consult the Zammad Community.