Is there any solution to backup Zammad files and DB to remote server (FTP, Cloud services like Dropbox etc…)
Zammad comes with basic backup scripts that you’re welcome to adjust as needed.
Technically as soon as you’ve created these backup files you can push them into any direction you’d want.
From our end there’s no magical scripts that will do that for you. 
Mounting e.g. shares before running the script and unmounting after it run however is no big deal in my opinion.
More information on the backup process in general can be found here:
https://docs.zammad.org/en/latest/appendix/backup-and-restore.html
1 Like
I have found curlftpfs and try to use it. It seems is ok, but when I try to do backup on mounted folder I have some errors. What this mean and what with backup files will be in the future?
Zammad backup started - Thu Jun 11 13:54:31 EEST 2020!
creating file backup…
ln: failed to create symbolic link ‘/mnt/zammad_backup/latest_zammad_files.tar.gz’: Function not implemented
creating postgresql backup…
mv: failed to preserve ownership for ‘/mnt/zammad_backup/20200611135431_zammad_db.psql.gz’: Operation not permitted
mv: preserving permissions for ‘/mnt/zammad_backup/20200611135431_zammad_db.psql.gz’: Operation not permitted
ln: failed to create symbolic link ‘/mnt/zammad_backup/latest_zammad_db.psql.gz’: Function not implemented
Zammad backuped successfully - Thu Jun 11 13:55:10 EEST 2020!
You seem to have a folder permissions issue. Or folder does not exist.
ls -la /mnt
Run the command and upload the output here.
root@helpdesk:/mnt/zammad_backup# ls -la /mnt
total 8
drwxr-xr-x 3 root root 4096 Jun 11 13:30 .
drwxr-xr-x 24 root root 4096 Jun 11 06:18 …
drwxr-xr-x 1 root root 1024 Jan 1 1970 zammad_backup
root@helpdesk:/mnt/zammad_backup# ls -la /mnt/zammad_backup/
total 733452
-rw-r–r-- 1 root root 5200767 Jun 11 14:31 20200611133044_zammad_db.psql.gz
-rw-r–r-- 1 root root 119968845 Jun 11 14:31 20200611133044_zammad_files.tar.gz
-rw-r–r-- 1 root root 5200753 Jun 11 14:55 20200611135431_zammad_db.psql.gz
-rw-r–r-- 1 root root 119968845 Jun 11 14:55 20200611135431_zammad_files.tar.gz
-rw-r–r-- 1 root root 5200762 Jun 11 15:14 20200611141416_zammad_db.psql.gz
-rw-r–r-- 1 root root 119968845 Jun 11 15:14 20200611141416_zammad_files.tar.gz
-rw-r–r-- 1 root root 5202868 Jun 11 15:18 20200611141819_zammad_db.psql.gz
-rw-r–r-- 1 root root 119968845 Jun 11 15:18 20200611141819_zammad_files.tar.gz
-rw-r–r-- 1 root root 5203041 Jun 11 15:27 20200611142647_zammad_db.psql.gz
-rw-r–r-- 1 root root 119968814 Jun 11 15:27 20200611142647_zammad_files.tar.gz
-rw-r–r-- 1 root root 5202940 Jun 11 15:51 20200611145125_zammad_db.psql.gz
-rw-r–r-- 1 root root 119968806 Jun 11 15:51 20200611145125_zammad_files.tar.gz
Actually the main issue is the above.
By default the move command does preserve the file permissiosn (so user and permission flags).
On most remote systems those users are not available and thus can’t be set or the operation simply is not allowed.
This will help you:
1 Like
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.