Skip to content

Database users and grants to be backup in separated files and restore with insert-ignore as default #1108

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

Open
svaroqui opened this issue Apr 15, 2025 · 0 comments

Comments

@svaroqui
Copy link
Collaborator

svaroqui commented Apr 15, 2025

  • This would enable child multi channel (source) clusters to be recover from parent cluster backups and taking care of the case where repman monitoring and replication user/password are different between the 2 clusters

  • This would enable to auto provision a child cluster and initialize with data from it's parent cluster

  • This could be used for initialize staging cluster

  • Api grants should take care that cross cluster data exchange is possible may be an additional grant to enable this is needed today this is checked via same user only

  • Child cluster is also the preferred way to trigger migration from very old releases or between different flavor or infrastructure

  • The restore should be considering default to binlog on restored leader so that staging replicas can auto catch proposed option bootstrap-from-parent-cluster-disable-binlog

@svaroqui svaroqui changed the title Database User info to be backup in separated files and restore with insert-ignore as default Database users and grants to be backup in separated files and restore with insert-ignore as default Apr 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants