WIP

Author: AnnaSjerling

modules/ROOT/pages/clustering/disaster-recovery.adoc

@@ -178,8 +178,11 @@ Furthermore, it might require the topology for a database to be altered to make
 =====
 
 . Run `SHOW DATABASES`. If a database show `currentStatus`= `offline` this database has been stopped.
-. For each stopped database that has at least one allocation on any of the `CORDONED` servers, start them by running `START DATABASE stopped-db WAIT`.
+. For each stopped database, start them by running `START DATABASE stopped-db WAIT`.
+// Is it a problem that it might not have started yet here? Should I write a line about making sure it is started before checking the write availability?
+// Cannot use wait here, because we will hang on lost members that are stopped. Should poll for started state on all non-lost members, but there are some situation where we will not be able to start. So how long should they wait here?
 This is necessary since stopped databases cannot be moved from one server to another.
+// And since status check doesn't work otherwise.
 +
 [NOTE]
 =====
@@ -193,6 +196,7 @@ If any of the primary allocations for a database report `replicationSuccessful`
 Go to xref:clustering/databases.adoc#recreate-databases[Recreate databases] for more information about recreate options.
 If any allocation has `currentStatus` = `QUARANTINED`, recreate them from backup using xref:clustering/databases.adoc#uri-seed[Backup as seed] or define seeding servers in the recreate procedure using xref:clustering/databases.adoc#specified-servers[Specified seeders] so that problematic allocations are excluded.
 Remember to make sure there are recent backups for the databases before recreating them, see xref:backup-restore/online-backup.adoc[Online backup] for more information.
+// What if a quarantined database had the desire to be stopped? Check quarantine before stopped?
 +
 [NOTE]
 =====