Restoring EGW after an HDD failure

[fzpulce]

Hi all,
I thing I need help.
I’m trying to recover a EGW installation after an HDD fault.
Unfortunately I have only a mysqldump because internal groupware backup files are lost.
I’m trying to recover so

1. reinstalled a Debian 10 (same version as previous system) then,
2. installed mariadb-server with same root password as in previous system
3. restored all MariaDB db from my raw backup
4. installed groupware-epl via apt
5. upgraded to egroupware-docker

after reboot I got error 502 bad gateway.

Is there a way to recover my data ?
can you please help ?

[StefanU]

Hi fzpulce.

because internal groupware backup files are lost.

And thus also your files from the VFS.

What was your EGroupware version?

after reboot I got error 502 bad gateway.

There are several contributions to this here in the forum. Please take a look at them first.
I mean, the problem could be access to the database (not running, password, …)

reinstalled a Debian 10 (same version as previous system) then,
installed mariadb-server with same root password as in previous system
restored all MariaDB db from my raw backup
installed groupware-epl via apt
upgraded to egroupware-docker

EGroupware brings everything with the installation. Even in the 19.1 docker installation the database is located on the host. Take a look:

🇬🇧 Docker (in EGroupware 19.1)?

🇬🇧 My installation of EGroupware 19.1 on Debian 10

Our commercial support is of course also a possibility. If this is for a company and you need to go fast, you should consider this.

Stefan

[fzpulce]

Hi StefanU,
thank you for your reply.
If I understand correctly, all my data should still be in my local database (MariaDB 10.3) because groupware docker still make use of external database server.
I just have to recover calendar data and address book data from one groupware user.

Can you suggest a way to do it ?

P.S. I’m on Egroupware 19.1.20200211

[StefanU]

If I understand correctly, all my data should still be in my local database (MariaDB 10.3) because groupware docker still make use of external database server.

Yes. The DB is NOT in an Docker-Container:

Also the directories for files an backups are located on the host. That you have to backup (in future). Same as in 17.1.

Can you suggest a way to do it ?

First: Virtualize your Debian/EGroupware-Installation (Proxmox etc.)
Second: Install as in My installation of EGroupware 19.1 on Debian 10
Third: If EGw runs, try (after a Backup of the System) to restore your dump

I can’t tell you if and how the database dump works. Just try it…

Stefan