-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Snapshot of MariaDB Add-on likely corrupt #1575
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Does this still happen? |
It happened to me yesterday |
One option would be to quickly stop MariaDB before the backup or restore. I used that trick when a restore did not work due to corrupt data. |
Stopping/Starting MariaDB before/after backup is more of a workaround, and does cause an outage. The |
@stewartsmith Have you an example of implementation of this ? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Unstale. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Still not solved. |
Still open. At Moment Mariadb-Addon Snapshots / Backup is unusable. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
It doesn't look like anything has changed. The backup tarballs still contain a copy of the MariaDB data directory, and unless there's extra XtraBackup steps being performed behind the scenes, then this is still basically just a corrupt copy of the database as part of the "backup" |
There is, it was implemented in #2063 |
The problem
When creating a Snapshot to download from the HA Web UI, the MariaDB portion is just a copy of the data directory. Seeing as this is not done with
mysqldump
or 'xtrabackup`, it means that writes may be ongoing as the files are copied, which render the copy corrupt.i.e. by default, the 'snapshot' cannot be consistent for the MariaDB database.
Environment
Applies to all environments.
Problem-relevant configuration
Traceback/Error logs
Additional information
The correct behaviour should be that when you create a Snapshot of the MariaDB database, it either uses
mysqldump
orxtrabackup
to create a consistent copy of the data. Anyone currently successfully using the snapshot to restore a MariaDB database is getting a non-corrupt database purely by accident.The text was updated successfully, but these errors were encountered: