Restoring into fresh docker-compose installation

Technical assistance
1

Infos:

  • Used Zammad version: 6.5
  • Used Zammad installation type: (docker-compose)
  • Operating system: Ubuntu 24
  • Browser + version: Firefox 140.1

I took a backup of files+data from a 6.5 bare metal installation (from which we want to migrate), and tried to restore it into a fresh docker-compose installation, again 6.5.

To prepare I copied the config.dist file to config, and configured the database.yml file with proper credentials. The restore command was “zammad_restore.sh 20250901173027”, as both file and data backup files had this timestamp.

There were a few database errors during the restore. At the end the message was that “Zammad restored successfully”. During the restore I had the backup and postgresql services running.

I then did a “down” followed by an “up”, and tried the webpage. Before the restore it showed “set up a new system”, and after the restore it shows the same.

The logs for the postgresql service show:

zammad-postgresql_1 |
zammad-postgresql_1 | PostgreSQL Database directory appears to contain a database; Skipping initialization
zammad-postgresql_1 |
zammad-postgresql_1 | 2025-09-02 11:27:01.100 UTC [1] LOG: starting PostgreSQL 17.5 on x86_64-pc-linux-musl, compiled by gcc (Alpine 14.2.0) 14.2.0, 64-bit
zammad-postgresql_1 | 2025-09-02 11:27:01.100 UTC [1] LOG: listening on IPv4 address “0.0.0.0”, port 5432
zammad-postgresql_1 | 2025-09-02 11:27:01.100 UTC [1] LOG: listening on IPv6 address “::”, port 5432
zammad-postgresql_1 | 2025-09-02 11:27:01.136 UTC [1] LOG: listening on Unix socket “/var/run/postgresql/.s.PGSQL.5432”
zammad-postgresql_1 | 2025-09-02 11:27:01.174 UTC [28] LOG: database system was shut down at 2025-09-02 11:26:50 UTC
zammad-postgresql_1 | 2025-09-02 11:27:01.313 UTC [1] LOG: database system is ready to accept connections
zammad-postgresql_1 | 2025-09-02 11:27:01.987 UTC [32] LOG: incomplete startup packet
zammad-postgresql_1 | 2025-09-02 11:32:01.296 UTC [26] LOG: checkpoint starting: time
zammad-postgresql_1 | 2025-09-02 11:32:03.223 UTC [26] LOG: checkpoint complete: wrote 19 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=1.914 s, sync=0.003 s, total=1.928 s; sync files=37, longest=0.001 s, average=0.001 s; distance=3132 kB, estimate=3132 kB; lsn=A/74948C90, redo lsn=A/74948C00

Please advise on what to do next, or point me to a better restore method.

2

i write the doc for 6.3.X to 6.5.0
i had do the restore ;
maybe you can refer to this docs：

3

I’m trying to do the same as initially posted, i. e. copied my database and files archives into a newly created restore directory of the backup volume as described in Backup & Restore (Docker) — Zammad System Documentation documentation After starting again the entire stack, I expected the database and files storage to be updated with the new archives and afterwards the restore folder to be renamed. But nothing happens at all. How can I troubleshoot this or precisely get the restore folder processed as expected?

Thanks
Andreas

4

That is because you’re looking at a pre release documentation page.
This functionality comes with Zammad 7.0 and is not available in Zammad 6.5, the current stable, as of now.

So you will have to wait for the release if you really wanna use that functionality.

The page also warns you about this fact

image
image991×164 9.44 KB

5

Ah ok. Thought it would be already available at least as some kind of beta functionality in 6.5 Basically I want to switch from package based to containerized installation to reduce host OS dependencies and simplify maintenance. Is release 7 expected to come during the year or even during the next months?

Thanks
Andreas

6

It’s on the way, generally no ETAs are communicated though.