Zammad Backup Failure - DB ADAPTER not found when using PostgreSQL

Infos:

Used Zammad version: 3.3
Used Zammad installation source: 6.0
Operating system: CentOS 7.7.1908
Browser + version: Not important

Expected behavior:
I expect the backup of my Zammad installation to be completed correctly and comprehensively.

Actual behavior:
The backup of Zammad fails with the following error message: “DB ADAPTER not found,” even though the backup is already saved in the file backup, using SQLite. However, I am using PostgreSQL as the database.

Steps to reproduce the behavior:

Execute ./zammad_backup.sh on my system.

Prosa:

I am currently using Zammad version 3.3.x with PostgreSQL 9.2 on CentOS 7.7. I am planning to migrate to a new setup with Ubuntu 20.04, PostgreSQL 12.15, and Zammad 6.0.

To ensure a smooth transition, I decided to create a backup of my existing Zammad installation. However, when I run the ./zammad_backup.sh script, I encounter an unexpected issue. The backup process fails with an error message stating “DB ADAPTER not found.” This is puzzling to me because the backup is already stored in the file backup using SQLite, whereas I am using PostgreSQL as my database.

I followed the migration tutorial provided by Zammad, available at the following link: Migrate Zammad to new host — Zammad documentation

I would greatly appreciate any assistance or insights into resolving this backup issue and ensuring a successful migration to the new setup. Thank you in advance for your support.

Sorry but Zammad 3.3 is so old that I’m not going to bother and debug that old backup script. It has changed a lot since than.

Most likely the easiest workaround for this situation is to simply get contrib/backup/ from the current stable from GitHub - zammad/zammad: Zammad is a web based open source helpdesk/customer support system .

It should support the old codebase without issues. The plus on that regard is that the documentation also applies. Please consider upgrading more frequently in the future.

This topic was automatically closed 360 days after the last reply. New replies are no longer allowed.