Skip to content

Split backup mysql user in seperate file #1120

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.

Sign up for GitHub

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

Jump to bottom
Open
svaroqui opened this issue Apr 17, 2025 · 2 comments
Open

Split backup mysql user in seperate file #1120

svaroqui opened this issue Apr 17, 2025 · 2 comments
Assignees
@caffeinated92
Labels
backup maintenance staging

Comments

@svaroqui
Copy link
Collaborator

svaroqui commented Apr 17, 2025 •
edited
Loading

  • Mysqldump --insert-ignore --system=user mysql users
  • Myloader restore mysql table only with insert ignore of csv.gzip file and rename user table gzip files before restoring backup restore file after restore
@svaroqui svaroqui added staging and removed staging labels Apr 17, 2025
@caffeinated92
Copy link
Collaborator

Correct syntax: Mysqldump --insert-ignore --system=user

@svaroqui
Copy link
Collaborator Author

svaroqui commented May 2, 2025 •
edited
Loading

I would rather improve on this with embedding mariadb >=11 .6 using https://mariadb.com/resources/blog/enhancements-to-mariadb-logical-dump-and-import-tools-in-release-series-11-5-11-6/ this would give:

  • Consistency with mydumper getting a file per table
  • Speedup using concurrent restore via mariadb-import
  • Capability to have consistent backup with system tables and only restore system table on demand

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@caffeinated92 caffeinated92

Labels
backup maintenance staging
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@svaroqui @caffeinated92