Merge branch 'dev' into imgrefresh-batch2

Author: lidiazuin

modules/ROOT/content-nav.adoc

@@ -68,8 +68,6 @@
 *** xref:kubernetes/operations/scaling.adoc[]
 *** xref:kubernetes/operations/image-pull-secret.adoc[]
 *** xref:kubernetes/operations/assign-neo4j-pods.adoc[]
-** Deploy a multi-data center Neo4j cluster
-*** xref:kubernetes/multi-dc-cluster/aks.adoc[]
 ** xref:kubernetes/troubleshooting.adoc[]
 
 * xref:configuration/index.adoc[]

modules/ROOT/images/multi-dc-cc-aks.png

@@ -1,7 +1,7 @@
 [role=enterprise-edition]
 [[aggregate-backup]]
 = Aggregate a database backup chain
-:description: This section describes how to aggregate a backup chain into a single backup.
+:description: This section describes how to aggregate a backup chain into a single backup and recover a full backup.
 
 [[aggregate-backup-command]]
 == Command
@@ -17,6 +17,8 @@ The benefits of aggregating a backup chain are notably:
 As part of the aggregation, transactions contained in the differential backups are applied to the store contained in the full backup artifact.
 This operation is called _recovery_ and can be costly.
 * Reduces the risk of losing chain’s links.
+* Some commands, like consistency check, cannot run against a backup chain or a full backup that is not recovered.
+Aggregating produces an artifact they can work against.
 
 
 [role=label--changed-2025.01]
@@ -205,3 +207,40 @@ bin/neo4j-admin backup aggregate --from-path=azb://myStorageAccount/myContainer/
 ----
 ======
 =====
+
+
+[[aggregate-unrecovered-full-backup]]
+=== Aggregating an unrecovered full backup
+
+To check if a full backup is in a recovered state, run the `neo4j-admin backup inspect` command:
+
+[source,shell]
+----
+bin/neo4j-admin backup inspect /mnt/backups/neo4j-2025-09-10T08-14-56.backup
+----
+
+The output will include the `RECOVERED` column.
+If it shows `false`, the backup is not yet recovered:
+
+[output]
+----
+|                                                 FILE | DATABASE |                          DATABASE ID |          TIME (UTC) | FULL | COMPRESSED | LOWEST TX | HIGHEST TX | STORE ID HASH | RECOVERED |
+| file:///mnt/backups/neo4j-2025-09-10T08-14-56.backup |    neo4j | 4e98fab8-6ae6-46cc-84c0-61ee8a8db60a | 2025-09-10T08:14:56 | true |       true |         1 |          3 |    -116350002 |     false |
+----
+
+If your full backup is not recovered, aggregating it will perform recovery.
+Run the following command:
+
+[source,shell]
+----
+bin/neo4j-admin backup aggregate --from-path=/mnt/backups/neo4j-2025-09-10T08-14-56.backup --keep-old-backup=true
+----
+
+This command will:
+
+* Generate a new, recovered backup alongside the existing one.
+* Preserve the original backup file (due to `--keep-old-backup=true`).
+
+After aggregation, you can run consistency checker against the recovered backup and/or restore it.
+
+

modules/ROOT/pages/backup-restore/aggregate.adoc

@@ -1,8 +1,9 @@
 :description: Describes the Neo4j consistency checker.
+:page-aliases: tools/neo4j-admin/consistency-checker.adoc
 [[consistency-checker]]
 = Check database consistency
 
-You can use the `neo4j-admin database check` command to check the consistency of a database, a dump, or a full backup.
+You can use the `neo4j-admin database check` command to check the consistency of a database, a dump, or a full recovered backup.
 The `neo4j-admin` tool is located in the _/bin_ directory.
 
 == Syntax
@@ -201,8 +202,10 @@ Consistency check
 
 [NOTE]
 ====
-Note that consistency check is not supported for differential backups.
-The backup chain must be aggregated into a full backup artifact before running consistency check.
+Note that consistency check is not supported for differential backups or unrecovered full backups.
+The backup chain must be aggregated into a full recovered backup artifact before running consistency check.
+
+See xref:backup-restore/aggregate.adoc[] for more details.
 ====
 
 Run with the `--from-path` option to check the consistency of a backup or a dump:

modules/ROOT/pages/backup-restore/consistency-checker.adoc

@@ -1,4 +1,5 @@
 :description: How to remove cluster state data from a Neo4j server using `neo4j-admin server unbind`.
+:page-aliases: tools/neo4j-admin/unbind.adoc
 [role=enterprise-edition]
 [[neo4j-admin-unbind]]
 = Unbind a server

modules/ROOT/pages/clustering/unbind.adoc

@@ -1,6 +1,7 @@
 [[neo4j-admin-migrate-configuration]]
 = Migrate configurations
 :description: This chapter describes the `neo4j-admin server migrate-configuration` command.
+:page-aliases: tools/neo4j-admin/migrate-configuration.adoc
 
 You can use the `migrate-configuration` command to migrate a legacy Neo4j configuration file to the current format.
 The new version will be written in a target configuration directory.

modules/ROOT/pages/configuration/migrate-configuration.adoc

@@ -1,4 +1,5 @@
 :description: This chapter describes the `memory-recommendation` command of Neo4j Admin.
+:page-aliases: tools/neo4j-admin/neo4j-admin-memrec.adoc
 [[neo4j-admin-memrec]]
 = Get initial memory recommendations
 

modules/ROOT/pages/configuration/neo4j-admin-memrec.adoc

@@ -1,7 +1,7 @@
 [[neo4j-admin-validate-config]]
 = Validate configurations
-:page-role: new-5.5
 :description: How to validate configurations using Neo4j Admin.
+:page-aliases: tools/neo4j-admin/validate-config.adoc
 
 
 The `neo4j-admin server validate-config` command validates the Neo4j and Log4j configurations.

modules/ROOT/pages/configuration/validate-config.adoc

@@ -1,4 +1,5 @@
 :description: Describes Neo4j Cypher Shell command-line interface (CLI) and how to use it.
+:page-aliases: tools/cypher-shell.adoc
 [[cypher-shell]]
 = Cypher Shell
 

modules/ROOT/pages/cypher-shell.adoc

@@ -1,4 +1,5 @@
 :description: This chapter describes the `neo4j-admin database migrate` command.
+:page-aliases: tools/neo4j-admin/migrate-database.adoc
 [[neo4j-admin-migrate]]
 = Migrate a database