problem with new install elabftw and copy directories and files of an old install

[RICFE]

I encountered a bug upon starting the DEBIAN 11 virtual machine with LVM, which no longer boots.
I managed to recover the directories /var/elabftw, /var/lib/docker, and the file docker-compose.yml with elabFTW version 4.9.0.

I performed a new installation based on this docker-compose.yml file,
but my question is, what can I and should I copy from the recovered directories to the new installation?
Which file contains all my admin and sysadmin configurations ?
And I do verify the rights on directories and files with 999

do you have a spoon installation procedure ?

Thank you in advance.
Best Regards,
Richard

[NicolasCARPi]

Hello Richard,

There are two things to restore. The uploaded files, and your database. Let's start with the easy part: the uploaded files.

Simply copy them from /var/elabftw/web and make sure permissions are correct with:

chown -R 101:101 /var/elabftw/web

For the database, it is best to use a backup created with mysqldump, but I suspect you have none, correct?

In that case, you can copy the mysql files present in /var/elabftw/mysql. Ideally, do a copy that keeps the same permissions. If you cannot, simply make sure that the permissions and ownership of files and directories match what you have in your fresh installation. The userid/group id of the mysql user in the mysql container is indeed 999:999.

[NicolasCARPi]

this means that the php can't find the mysql service, maybe the container name is wrong, it depends on what you have in DB_HOST. You should restore from the mysqldump. See https://doc.elabftw.net/backup.html#how-to-restore-a-backup

[RICFE]

hello Nicolas,

finally, I recovered the saved file by the following command

mysqldump -u root --password= --all-databases > /opt/Backup-dump-mysql_elabftw/all-databases-$(date +%Y-%m-%d_%H:%M).sql

how can I recover this data from the .sql file to import directly into my elabFTW database ?

I thank you in advance.

Best regards.
Richard

[NicolasCARPi]

how can I recover this data from the .sql file to import directly into my elabFTW database ?

see the link just above your message

[RICFE]

Hello Nicolas,

THANKS VERY MUCH !
Good thing I had this mysqldump !

the restoration procedure from your web page worked very well.

Best regards.
Richard

[NicolasCARPi]

Great! Make sure to document everything and regularly test your backup/restoration procedure ;)

[RICFE]

Hello Nicolas,

yes I am documenting my backup and restore procedure.

Afterwards I updated from 4.9.0 to 5.0.1 !

However, experimenters in my laboratory tell me that they no longer have access to an experiment between January 31 and February 22. It's really surprising because normally I backed up with a mysqldump and all the basics!

To check, i'm going to test 2 things :
1. restore the databases and elabftw again, without doing it directly after updating to version 5.0.1
2. and retrieve the docker images from mysql and elabftw using a docker export and put them on another virtual machine
In order to check if there really is this data loss !

I know that colleagues work like this; they make 1 post on an experience for each manipulation and on which several colleagues connect and over several weeks or months.
Could there be a bug ? Or they don't use it as they should !

Best regards.
Richard

[NicolasCARPi]

It might be related to their scope setting or the change regarding cross team experiments.

See #4812 and #4908

It is unlikely that your dump "missed" some entries, but very likely that the visibility/permissions are not adequate.