Add images to the Disaster recovery page #2619
Open
+905
−14
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
modules/ROOT/pages/clustering/multi-region-deployment/disaster-recovery.adoc
Outdated
Show resolved
Hide resolved
modules/ROOT/pages/clustering/multi-region-deployment/disaster-recovery.adoc
Outdated
Show resolved
Hide resolved
modules/ROOT/pages/clustering/multi-region-deployment/disaster-recovery.adoc
Outdated
Show resolved
Hide resolved
modules/ROOT/pages/clustering/multi-region-deployment/disaster-recovery.adoc
Show resolved
Hide resolved
NataliaIvakina
force-pushed
the
dev-images-disaster-recovery-1
branch
from
0a2fd7a to
6598d6c
Compare
|
This PR includes documentation updates Updated pages: |
NataliaIvakina
commented
Oct 3, 2025
|
|
||
| |Database A | ||
| |All allocations are lost. | ||
| |The database needs to be recreated from a backup. |
There was a problem hiding this comment.
@AnnaSjerling, could you add a bit more details about the recovery strategy in each case?
| If you recreate databases using xref:database-administration/standard-databases/recreate-database.adoc#undefined-servers[undefined servers] or xref:database-administration/standard-databases/recreate-database.adoc#undefined-servers-backup[undefined servers with fallback backup], the store might not be recreated as up-to-date as possible in certain edge cases where the `system` database has been restored. | ||
| ===== | ||
| + | ||
| image::servers-cordoned-databases-moved.svg[width="400", title="Recreate databases", role=popup] |
There was a problem hiding this comment.
I think, we need to explain why databases A, B, and C were recreated in this step. Could you help me with that?
| This will move all database allocations from this server to an available server in the cluster. | ||
| + | ||
| image::servers-deallocated.svg[width="400", title="Deallocate databases from unavailable servers", role=popup] | ||
| + |
There was a problem hiding this comment.
To add a line explaining why the database D was moved or recreated in this step.
| ==== | ||
| image::fully-recovered-cluster.svg[width="400", title="Fully recovered cluster", role="popup"] | ||
|
|
||
|
|
There was a problem hiding this comment.
I was thinking that we could add some kind of conclusion here.
something like:
All databases, affected by the current disaster, were recreated and allocated to new servers.
The restored `system` database is in a primary mode.
What else should we say here? WDYT?
NataliaIvakina
commented
Oct 3, 2025
| + | ||
| If servers were added in the <<make-the-system-database-write-available, Make the `system` database write-available>> step of this guide, additional servers might not be needed here. | ||
| It is important that the new servers are unconstrained, or deallocating servers might be blocked even though enough servers were added. | ||
| If servers were added in the <<make-the-system-database-write-available, Make the `system` database write-available>> step of this guide (like it is done in the current disaster recovery example), additional servers might not be needed here. |
There was a problem hiding this comment.
Suggested change
| If servers were added in the <<make-the-system-database-write-available, Make the `system` database write-available>> step of this guide (like it is done in the current disaster recovery example), additional servers might not be needed here. | |
| If servers were added in the <<make-the-system-database-write-available, Make the `system` database write-available>> step of this guide (like it has been done in the current disaster recovery example), additional servers might not be needed here. |
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.
No description provided.