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

backupccl: check mismatched cluster regions on backup and restore #11278

Closed
Tracked by #10937
jseldess opened this issue Sep 8, 2021 · 2 comments · Fixed by #11966
Closed
Tracked by #10937

backupccl: check mismatched cluster regions on backup and restore #11278

jseldess opened this issue Sep 8, 2021 · 2 comments · Fixed by #11966

Comments

@jseldess
Copy link
Contributor

jseldess commented Sep 8, 2021

PR: cockroachdb/cockroach#64758

From release notes:

Previously, if a restore cluster mismatched the regions in backup cluster, the data would be restored as if the zone configuration did not exist. CockroachDB now checks the regions before restore, making users aware of mismatched regions between backup and restore clusters. If there is a mismatched region, users can either update cluster localities or restore with the --skip-localities-check option to continue. [#64758][#64758] {% comment %}doc{% endcomment %}

@jseldess jseldess added this to the 21.2 milestone Sep 8, 2021
@mikeCRL mikeCRL added the A-io label Sep 22, 2021
@kathancox
Copy link
Contributor

Relates to #10937

@livlobo
Copy link

livlobo commented Oct 8, 2021

@kathancox - for testing this feature - it was helpful for me to read this in addition to the description in the PR.
https://www.cockroachlabs.com/docs/v21.1/multiregion-overview.html

For additional context, you can refer to my test results here, if you'd like.

I'm not sure how we want to note this open issue: cockroachdb/cockroach#71349

Let me know if you need any additional info for the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants