Infos:
- Used Zammad version: 3.4.x (updated)
- Used Zammad installation source: apt (source, package, …)
- Operating system: Debian 8.11
- Browser + version: Not Problemspecific
Expected behavior:
- Make a correct and complete backup of my zammad installation.
Actual behavior:
- Backup of Zammad fails showing: DB ADAPTER not found. if its sqlite backup is already saved in the filebackup
However Postgresql is used…
Steps to reproduce the behavior:
- execute ./zammad_backup.sh on my system
Prosa
I want to move my Zammad installation from a Proxmox VM to another Proxmox CT (not problem specific). To get a clean installation I would like to create a backup and restore it later on.
I have made other transfer without a problem. However on this machine it does not backup the database.
root@zammad:/opt/zammad/contrib/backup# cat config
#!/usr/bin/env bashzammad backup script config
BACKUP_DIR=‘/var/tmp/XXX_zammad_backup’
HOLD_DAYS=‘10’
DEBUG=‘no’
root@zammad:/opt/zammad/contrib/backup# ./zammad_backup.shZammad backup started - Thu 10 Sep 12:15:30 CEST 2020!
creating file backup…
DB ADAPTER not found. if its sqlite backup is already saved in the filebackupZammad backuped successfully - Thu 10 Sep 12:16:45 CEST 2020!
Database config
root@zammad:/opt/zammad/contrib/backup# cat /opt/zammad/config/database.yml
production:
adapter: postgresql
database: zammad_production
pool: 50
timeout: 5000
encoding: utf8
username: zammad
password: YYY
host: 127.0.0.1development:
adapter: postgresql
database: zammad_production
pool: 50
timeout: 5000
encoding: utf8
username: zammad
password: YYY
host: 127.0.0.1Warning: The database defined as “test” will be erased and
re-generated from your development database when you run “rake”.
Do not set this db to the same as development or production.
test:
adapter: postgresql
database: zammad_production
pool: 50
timeout: 5000
encoding: utf8
username: zammad
password: YYY
host: 127.0.0.1root@zammad:/opt/zammad/contrib/backup#
Any hints what I’m doing wrong?