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
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
The text was updated successfully, but these errors were encountered:
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
Uh oh!
There was an error while loading. Please reload this page.
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
The text was updated successfully, but these errors were encountered: