You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I try to restore mysql backups it fails almost everytime - i followed every guide on the pmm site but it doesn't work. This error only happens after editing the database.
I read about a bug that didn't received the state of mysqld this caused the error warning even after a successful restore - maybe this is an similar error? Maybe the MySQL server started to slow which causes this issue? Because the restore was successful - everything was restored correctly. (The hardware of the mysql server isn't the best - because its not used in production, just for testing at the moment.)
I also saw an youtube video which showed a "log" button in the restore list, is this not available for mysql restores? where can I find the output from xtrabackup when restoring backups via pmm?
I also would like to restore it directly with xxtrabackup which command is used by pmm to restore the backup? I looked in the source code but it is too large...
The restores in the red rectangle are from a clean installed mysql server without any changes, the yellow rectangles contains the restores after import the employees. (This also happens with any other changes too not only with the employees test database)
Expected Results
Backups should be able to restore correctly without strange errors.
Actual Results
The Dashboard says that the restore was not successful (error, not more informations are available) but when I look into the /var/lib/mysql folder all files where restored correctly. The MySQL server also started without any issues.
Version
2.39
Steps to reproduce
Install pmm with Docker
Install the latest xtrabackup, pmm-client and mysql on ubuntu
Create a backup, I use min.io as a S3 server
Try to restore the backup - this should work because the MySQL server is untouched
Import a test database I used employees (really popular test database)
now create a new backup and try to restore it - probably it will work for the first time but after this the restores will fail almost every time
Relevant logs
I dont have relevant logs, pmm-managed log doenst contain anything about it, mysql is also running without any errors.
Code of Conduct
I agree to follow Percona Community Code of Conduct
The text was updated successfully, but these errors were encountered:
Description
When I try to restore mysql backups it fails almost everytime - i followed every guide on the pmm site but it doesn't work. This error only happens after editing the database.
I read about a bug that didn't received the state of mysqld this caused the error warning even after a successful restore - maybe this is an similar error? Maybe the MySQL server started to slow which causes this issue? Because the restore was successful - everything was restored correctly. (The hardware of the mysql server isn't the best - because its not used in production, just for testing at the moment.)
I also saw an youtube video which showed a "log" button in the restore list, is this not available for mysql restores? where can I find the output from xtrabackup when restoring backups via pmm?
I also would like to restore it directly with xxtrabackup which command is used by pmm to restore the backup? I looked in the source code but it is too large...
The restores in the red rectangle are from a clean installed mysql server without any changes, the yellow rectangles contains the restores after import the employees. (This also happens with any other changes too not only with the employees test database)
Expected Results
Backups should be able to restore correctly without strange errors.
Actual Results
The Dashboard says that the restore was not successful (error, not more informations are available) but when I look into the /var/lib/mysql folder all files where restored correctly. The MySQL server also started without any issues.
Version
2.39
Steps to reproduce
Relevant logs
Code of Conduct
The text was updated successfully, but these errors were encountered: