Mailcow-dockerized: backup all for new serever

Created on 25 Mar 2018  路  4Comments  路  Source: mailcow/mailcow-dockerized

how to quick backup mailcow and transfer to new server? where run only 2 commands: `sudo curl -sSL https://get.docker.com/ | CHANNEL=stable sh
sudo systemctl enable docker.service
sudo systemctl start docker.service

sudo curl -L https://github.com/docker/compose/releases/download/1.20.1/docker-compose-uname -s-uname -m -o /usr/local/bin/docker-compose
sudo chmod +x /usr/local/bin/docker-compose
`

Most helpful comment

In addition to the above reply.
Check your old servers SQL password.

Restoring Mailcow SQL on a new server results in SQL connection failed.
As generate_config.sh generates a new random SQL password for mailcow.conf.
Which conflicts with the backup.

All 4 comments

You could create a backup with this, move it to the new server with e.g. rsync and restore it
Or directly move the whole volumes/data to the new server

In addition to the above reply.
Check your old servers SQL password.

Restoring Mailcow SQL on a new server results in SQL connection failed.
As generate_config.sh generates a new random SQL password for mailcow.conf.
Which conflicts with the backup.

P.s.
Pay attention when restoring data from Rspam from the old to the new server.
I systematic got 502 errors by Nginx, when trying to visit the Rspam GUI after recovery.

I did not investigate further because skipping the data solves the problem.
Its maybe because I stopped using ClamAV. I don't know.

Rspam is working great out of the box so not having Rspam's learning curve is no problem for me.

I believe this issue was solved already. I'm closing this now.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

a3li picture a3li  路  3Comments

GalacticLion7 picture GalacticLion7  路  3Comments

zkryakgul picture zkryakgul  路  3Comments

RogerSik picture RogerSik  路  3Comments

mritzmann picture mritzmann  路  3Comments