Transfer egroupware docker containers to a new box, best practice?

[AlexS]

Hello Together,
I have an old server box running the egroupware related docker containers:

• egroupware
• egroupware-db
• egroupware-nginx
• collabora-key
• rocketchat
• mongo
• push
• watchtower

Now I have prepared a new server and I was wondering how I can transfer these containers and their data to the new box.
I found some ways here https://bobcares.com/blog/move-docker-container-to-another-host however I am not sure what is the best solution for the egroupware containers.
Thanks for your input and support and best regards
Alex

[StefanU]

Hi Alex.

these containers and their data to the new box.

You install EGroupware first. So all the containers will be installed as well.
The EGroupware data is stored in the DB on the host and in /var/lib/egroupware (backups, VFS data, …). Now you can do a migration like before 19.1. Take a look here:

🇬🇧 My installation of EGroupware 19.1 on Debian 10

and here:

EGroupware/egroupware

So:
Make a current backup, copy the files and restore the backup.

---

push

Oh, ist that your developer box?

Only with the Rocketchat DB (Mongo) I am unsure. There @RalfBecker would have to say something.
There would still have to be some documentation. The backup too…
There is a /var/lib/egroupware/default/rocketchat/dump . For Backup?

Stefan

[AlexS]

Hello Stefan,
thanks for your reply, I will go this way then…! I somehow was hoping for an all in one solution, transferring the entire containers and volumes, without the need to do manual backup -restore for the databases and the files… . In terms of a quick way to clone a life system this would be also very nice…
I now also searched for a clean answer for the rocketchat backup - restore but I could not find one so far. There we also have the mongo db on one side and the uploaded files on the other side… please correct me if I am wrong.
BR
Alex

[J_Roeleveld]

To ensure I would be able to backup the Rocketchat data as well, I modified the “docker-compose.yml” file to have the “mongo” volume point to an actual location on my server. As I have all the different volumes and docker-compose files on a different partition, I only need to backup the database and partition.

[RalfBecker]

That works fine on a linux machine, you need to be careful with that approach on a Mac or Windows.

Longterm plan is to create a cron-job backing up MongoDB like you can do it with MariaDB/MySQL.

Obviously you can use mongodump yourself to backup and restore MongoDB:

https://docs.mongodb.com/manual/tutorial/backup-and-restore-tools/

(Don’t get scared by the talk about clusters and how they need to be backed up, you are not using a cluster, so mongodump and -restore is fine for you.)

Ralf