Replies: 1 comment
-
|
Looks like this is a Craft CMS discussion link. If the issue there is related to MySQL/database corruption or broken DB tables, I’d usually try the normal recovery path first. Check the MySQL/MariaDB logs, verify the database service is healthy, and if InnoDB is damaged try recovery mode (innodb_force_recovery) just to get the database up long enough to export data. If the database files are damaged beyond normal repair, then a third-party recovery tool like Stellar Repair for MySQL can be an option. It can help recover corrupted MySQL/MariaDB databases, extract tables from damaged files, and save recovered data into a new database instead of working directly on the original files. For a Craft CMS install, I would also make a copy of the whole DB/data directory first, because the goal is to recover the content tables safely rather than risk making the corruption worse. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I was trying to create production ready Docker setup of Craft as per https://craftcms.com/knowledge-base/docker-in-production
I am using MySQL because that seems the most recommended database as per https://craftcms.com/knowledge-base/craft-database-options-and-best-practices
I have problem with MySQL backup and restore, from both CLI and dashboard.
Errors from CLI:
Backup:
Restore:
Similar issues:
#17143
#18155
Could you please update the guide with production ready Dockerised Craft compatible with MySQL?
Looks like the problem is that the so-called "mysql-client" in Alpine is actually "mariadb-client".
I must say its annoying how Linux distros pretend MariaDB is MySQL and let people fight with the incompatibilities.
Relevant upstream issue: https://gitlab.alpinelinux.org/alpine/aports/-/issues/17798
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions