Update "Disaster recovery for WAN-federated datacenters" #22834
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
danielehc
added
the
type/docs
danielehc
added
pr/no-changelog
boruszak
reviewed
Sep 26, 2025
website/content/docs/manage/disaster-recovery/disaster-preparation.mdx
Outdated
Show resolved
Hide resolved
website/content/docs/manage/disaster-recovery/disaster-preparation.mdx
Outdated
Show resolved
Hide resolved
website/content/docs/manage/disaster-recovery/disaster-preparation.mdx
Outdated
Show resolved
Hide resolved
website/content/docs/manage/disaster-recovery/disaster-preparation.mdx
Outdated
Show resolved
Hide resolved
website/content/docs/manage/disaster-recovery/restore-primary.mdx
Outdated
Show resolved
Hide resolved
website/content/docs/manage/disaster-recovery/restore-primary.mdx
Outdated
Show resolved
Hide resolved
|
|
||
| ## Restore and validate federation | ||
|
|
||
| If you have a federated environment, after the primary datacenter restore it is possible that the IP addresses of the Consul server agents changed. |
There was a problem hiding this comment.
Suggested change
| If you have a federated environment, after the primary datacenter restore it is possible that the IP addresses of the Consul server agents changed. | |
| If you have a federated environment, it is possible that the IP addresses of the Consul server agents changed when the primary datacenter was restored. |
|
|
||
| If you have a federated environment, after the primary datacenter restore it is possible that the IP addresses of the Consul server agents changed. | ||
|
|
||
| Depending on the configuration of your secondary datacenters' server agents, you might need to re-establish federation by updating the server configuration. |
There was a problem hiding this comment.
Suggested change
| Depending on the configuration of your secondary datacenters' server agents, you might need to re-establish federation by updating the server configuration. | |
| Depending on how you configured the server agents in your secondary datacenter, you may need to re-establish federation by updating the secondary datacenter configurations as well. |
|
|
||
| Depending on the configuration of your secondary datacenters' server agents, you might need to re-establish federation by updating the server configuration. | ||
|
|
||
| Refer to [Loss of federation due to primary datacenter restore.](/consul/docs/manage/disaster-recovery/restore-federated#loss-of-federation-due-to-primary-datacenter-restore) for more information on this. |
There was a problem hiding this comment.
Suggested change
| Refer to [Loss of federation due to primary datacenter restore.](/consul/docs/manage/disaster-recovery/restore-federated#loss-of-federation-due-to-primary-datacenter-restore) for more information on this. | |
| For more information, refer to [Loss of federation due to primary datacenter restore](/consul/docs/manage/disaster-recovery/restore-federated#loss-of-federation-due-to-primary-datacenter-restore). |
Co-authored-by: Jeff Boruszak <[email protected]>
Co-authored-by: Jeff Boruszak <[email protected]>
Co-authored-by: Jeff Boruszak <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Update "Disaster recovery for WAN-federated datacenters" https://hashicorp.atlassian.net/browse/CE-921
This started as a simple update of the content of a single page but, it became a full restructure of the whole
manage/disaster-recoverycontent trying to rationalize the content and remove duplicated steps or concepts.Preview
https://consul-git-CE-921-hashicorp.vercel.app/consul/docs/manage/disaster-recovery
Conflicts
This content supersedes the one in #22756 that, in my opinion should be closed.