Skip to content
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

Incremental backup: support native MySQL GTID values as valid positions. #13415

Closed
shlomi-noach opened this issue Jun 29, 2023 · 0 comments · Fixed by #13474
Closed

Incremental backup: support native MySQL GTID values as valid positions. #13415

shlomi-noach opened this issue Jun 29, 2023 · 0 comments · Fixed by #13474
Assignees
Labels
Component: Backup and Restore Type: Enhancement Logical improvement (somewhere between a bug and feature)

Comments

@shlomi-noach
Copy link
Contributor

shlomi-noach commented Jun 29, 2023

The flag --incremental_from_pos supports the following types of entries:

  • A MySQL56 GTID position format
  • the magic hint auto

Examples:

$ vtctlclient -- Backup --incremental_from_pos "MySQL56/16b1039f-22b6-11ed-b765-0a43f95f28a3:1-615" zone1-0000000102
$ vtctlclient -- Backup --incremental_from_pos "auto" zone1-0000000102

Since incremental backup & restore are designed to only work with MySQL GTIDs, it would be nice, as convenience, to allow a native MySQL GTID set, without the MySQL56/ prefix, as follows:

$ vtctlclient -- Backup --incremental_from_pos "16b1039f-22b6-11ed-b765-0a43f95f28a3:1-615" zone1-0000000102

RFC: #11227

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Backup and Restore Type: Enhancement Logical improvement (somewhere between a bug and feature)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant