Update databases.adoc

Author: NataliaIvakina

modules/ROOT/pages/clustering/databases.adoc

@@ -227,47 +227,55 @@ neo4j@neo4j> DRYRUN REALLOCATE DATABASES;
 
 [role=label--new-5.24]
 [[recreate-databases]]
-== Recreate databases
+== Recreate a database
 
-Neo4j 5.24 introduces the xref:reference/procedures.adoc#procedure_dbms_cluster_recreateDatabase[`dbms.cluster.recreateDatabase()`] procedure, which allows you to restore a database:
+Neo4j 5.24 introduces the xref:reference/procedures.adoc#procedure_dbms_cluster_recreateDatabase[`dbms.cluster.recreateDatabase()`] procedure, which allows you:
 
-* to a specified backup, while keeping all the associated privileges for the database.
+* To change the database store to a specified backup, while keeping all the associated privileges for the database.
 
-* to a write mode again after it has been lost (for example, due to a disaster).
+* To make your database write-available again after it has been lost (for example, due to a disaster).
 // See xref:clustering/disaster-recovery.adoc[] for more information.
 
 [CAUTION]
 ====
 The recreate procedure works only for real user databases and not for composite databases, or the `system` database.
 
-Keep in mind the recreate procedure results in downtime while the stores get updated.
+Remember that the recreate procedure results in downtime while the stores get updated.
 The time is unbounded and may depend on different factors -- for example, the size of the store, network speed, etc.
-
-The database recreation process is designed to select the latest seed from the defined seeding servers.
-Specifying only a subset of the previous cluster servers as seeders carries a risk of data loss.
 ====
 
-The database in question can be in an `online` or `offline` state when it is recreated, but a successful operation starts the database regardless of the previous state.
+The database in question can be in an `online` or `offline` state when it is recreated, but a successful operation starts the database regardless of its previous state.
 
 If CDC is enabled for the database, it will still be enabled after recreating the database, however the chain will be broken.
-See link:https://neo4j.com/docs/cdc/current/[CDC documentation] for more details.
+See link:https://neo4j.com/docs/cdc/current/backup-restore/[CDC documentation -> Restore backups and snapshots] for more details.
 
 Before recreating a database, any eventual quarantined states need to be addressed.
 For more information, see xref:database-administration/standard-databases/errors.adoc#quarantine[Standard databases -> Error handling].
 
-You need xref:authentication-authorization/dbms-administration.adoc#access-control-dbms-administration-database-management[the `CREATE DATABASE` and `DROP DATABASE` privileges] to run the recreate procedure. 
-
-[[recreate-seeding-options]]
-=== Seeding options and configurations
+You need xref:authentication-authorization/dbms-administration.adoc#access-control-dbms-administration-database-management[the `CREATE DATABASE` and `DROP DATABASE` privileges] to run the recreate procedure.
 
-The store to be used during the recreation of a database can be defined in three different ways.
-One method uses a backup, while the two others use available allocations in the cluster.
+To check if the recreation is successful, use the `SHOW DATABASES` command and verify that all allocations have been started.
 
 Additionally, you have the option to modify <<alter-topology-recreate, the topology>> during the recreation process.
 However, note that the store format, access, and enrichment cannot be altered during recreation.
 
+[[recreate-seeding-options]]
+=== Seeding options
+
+The store to be used during the recreation of a database can be defined in different ways.
+One method uses a backup, while others use available allocations in the cluster.
+
+You can use either <<uri-seed, `seedURI`>> or <<seed-servers, `seedingServers`>> to specify the source from which the database should be recreated.
+
+* If you define neither, an error is thrown.
+
+* If you define both of them, then `seedingServers` must be an empty list.
+
+* If `seedingServers` is not empty and `seedURI` is also defined, an error will occur.
+See <<undefined-servers-backup, Undefined servers with fallback backup>> for more details.
+
 [[uri-seed]]
-==== `seedURI`
+==== Use backup as a seed
 
 If you provide a URI to a backup or a dump, the stores on all allocations will be replaced by the backup or the dump at the given URI.
 The new allocations can be put on any `ENABLED` server in the cluster.
@@ -277,13 +285,19 @@ To avoid possible data loss, ensure you back up the current store before replaci
 
 [source, shell]
 ----
-CALL dbms.cluster.recreateDatabase("neo4j", {seedURI: "myBackup"});
+CALL dbms.cluster.recreateDatabase("neo4j", {seedURI: "s3:/myBucket/myBackup.backup"});
 ----
 
 [[seed-servers]]
-==== `seedingServers`
+==== Use available allocations as seed
+
+The database recreation process is designed to select the latest seed from the seeding servers.
+Specifying only a subset of the previous cluster servers as seeders carries a risk of data loss.
+
+[[specified-servers]]
+===== Specified servers
 
-Specify a set of available servers.
+You can specify a set of available servers.
 The stores on all allocations will be synchronized to the most up-to-date store from the defined servers.
 The number of defined servers cannot exceed the number of total allocations in the desired topology. 
 
@@ -293,7 +307,7 @@ CALL dbms.cluster.recreateDatabase("neo4j", {seedingServers: ["serverId1", "serv
 ----
 
 [[undefined-servers]]
-==== Undefined servers
+===== Undefined servers
 
 If you provide an empty list of seeding servers and do not specify a `seedURI`, Neo4j automatically selects all available allocations of the database as seeders.
 The store will be replaced by the most up-to-date seeder available in the cluster.
@@ -312,7 +326,7 @@ This means the store is replaced by the most up-to-date seeder if available; oth
 
 [source, shell]
 ----
-CALL dbms.cluster.recreateDatabase("neo4j", {seedingServers: [], seedURI: "myBackup"});
+CALL dbms.cluster.recreateDatabase("neo4j", {seedingServers: [], seedURI: "s3:/myBucket/myBackup.backup"});
 ----
 
 [[alter-topology-recreate]]