From 3344a01a00055ad72c297f518a85fcf785ac55a6 Mon Sep 17 00:00:00 2001 From: Ralf Becker Date: Wed, 14 Aug 2019 15:31:08 +0200 Subject: [PATCH] Created Update recommendations and troubleshooting (markdown) --- Update-recommendations-and-troubleshooting.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 Update-recommendations-and-troubleshooting.md diff --git a/Update-recommendations-and-troubleshooting.md b/Update-recommendations-and-troubleshooting.md new file mode 100644 index 0000000..d024eda --- /dev/null +++ b/Update-recommendations-and-troubleshooting.md @@ -0,0 +1,17 @@ +![](http://www.egroupware.org/wp-content/themes/egroupware/images/logo.svg) + +> **If something goes wrong with the update, it is in almost all cases related to the Apache or Nginx configuration on the host, and NOT Docker and the running containers!** + +If you are not familiar with your Apache/Nginx configuration (including https), or need to ensure only a minimal downtime, the recommendation will be always to do the **painless new installation** on a new host and then an **migration of your database and files** to the new host! Same is true if your old hosts version is no longer supported by from it distribution. + +# How to migrate your data from an existing 17.1 or older installation +1. do a new installation as described for the distribution of the new host +2. enable https using Let's Encrypt following the exzellent instructs from eg. [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-ubuntu-18-04) +3. make a database backup inside EGroupware using ***Administration >> Database backup and restore*** +4. rsync the files and backups from the old installation to the new server, run on the new server the following commands: +``` +rsync -av --delete root@:/var/lib/egroupware/default/ /var/lib/egroupware/default/ +chown -R 33:33 /var/lib/egroupware/default +``` +5. log into the new EGroupware using the generated ***sysop*** user and go to ***Administration >> Database backup and restore*** and restore the last backup you rsynced to the new server +6. you can repeat steps 3. to 5. multiple times, until you are ready to use the new system productively \ No newline at end of file