Update disaster recovery guide to reflect error message change (#709) (#711)

AlexicaWright · jackwaudby · web-flow · commit f3e80d42931e · 2023-04-19T15:49:29.000+02:00
Recently in 5.7 we updated the error message when attempting to
deallocate a server hosting a database with only 1 primary. This PR
updates the disaster recovery guide to reflect this.

---------

Co-authored-by: Jack Waudby &lt;33488812+jackwaudby@users.noreply.github.com&gt;
diff --git a/modules/ROOT/pages/clustering/disaster-recovery.adoc b/modules/ROOT/pages/clustering/disaster-recovery.adoc
@@ -117,7 +117,7 @@ If *all* servers show health `AVAILABLE` and status `ENABLED` continue to xref:c
 . On each `UNAVAILABLE` server, run `CALL dbms.cluster.cordonServer("unavailable-server-id")`.
 . On each `CORDONED` server, run `DEALLOCATE DATABASES FROM SERVER cordoned-server-id`.
 . On each server that failed to deallocate with one of the following messages:
-.. `Could not deallocate server [server]. Can't move databases in single mode [database]`
+.. `Could not deallocate server [server]. Can't move databases with only one primary [database].`
 +
 or
 +

Original file line number	Diff line number	Diff line change
@@ -117,7 +117,7 @@ If all servers show health `AVAILABLE` and status `ENABLED` continue to xref:c
`117`	`117`	. On each `UNAVAILABLE` server, run `CALL dbms.cluster.cordonServer("unavailable-server-id")`.
`118`	`118`	. On each `CORDONED` server, run `DEALLOCATE DATABASES FROM SERVER cordoned-server-id`.
`119`	`119`	`. On each server that failed to deallocate with one of the following messages:`
`120`		-.. `Could not deallocate server [server]. Can't move databases in single mode [database]`
	`120`	+.. `Could not deallocate server [server]. Can't move databases with only one primary [database].`
`121`	`121`	`+`
`122`	`122`	`or`
`123`	`123`	`+`