Emphasize in docs that in clustering environments, when using incremental import the updated database must be reseeded (neo4j#2093)

Co-authored-by: NataliaIvakina <[email protected]>

Author: renetapopova

modules/ROOT/pages/tools/neo4j-admin/neo4j-admin-import.adoc

@@ -619,6 +619,17 @@ Incremental import into an existing database.
 
 === Usage and limitations
 
+[WARNING]
+====
+The importer works well on standalone servers.
+
+In clustering environments with multiple copies of the database, the updated database must be used as a source to reseed the rest of the database copies.
+You can use the procedure xref:procedures.adoc#procedure_dbms_cluster_recreateDatabase[`dbms.cluster.recreateDatabase()`].
+For details, see xref:clustering/databases.adoc#recreate-databases[Recreate databases].
+
+Starting the clustered database after an incremental import without reseeding or performing the incremental import on a single server while the database remains online on other clustered members may result in unpredictable consequences, including data inconsistency between cluster members.
+====
+
 The incremental import command can be used to add:
 
 * New nodes with labels and properties.
@@ -638,12 +649,6 @@ The incremental import command cannot be used to:
 * Update or delete labels in nodes.
 * Delete existing nodes and relationships.
 
-[NOTE]
-====
-The importer works well on standalone servers.
-In clustering environments with multiple copies of the database, the updated database must be reseeded.
-====
-
 === Parameters
 
 .`neo4j-admin database import incremental` parameters