Merge branch 'dev' into kubernetes-diagram

Author: lidiazuin

modules/ROOT/pages/authentication-authorization/built-in-roles.adoc

@@ -827,7 +827,7 @@ These include the rights to perform the following classes of tasks:
 
 * Manage xref:authentication-authorization/database-administration.adoc[database privileges] to control the rights to perform actions on specific databases:
 ** Manage access to a database and the right to start and stop a database.
-** Manage link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/search-performance-indexes/overview/[indexes] and link:{neo4j-docs-base-uri}/cypher-manual/current/constraints/[constraints].
+** Manage link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/[indexes] and link:{neo4j-docs-base-uri}/cypher-manual/current/constraints/[constraints].
 ** Allow the creation of labels, relationship types, or property names.
 ** Manage transactions.
 * Manage xref:authentication-authorization/dbms-administration.adoc[DBMS privileges] to control the rights to perform actions on the entire system:

modules/ROOT/pages/authentication-authorization/dbms-administration.adoc

@@ -97,7 +97,7 @@ This includes the following tasks and their relevant privileges:
 * Manage xref:authentication-authorization/privileges-reads.adoc[read] and xref:authentication-authorization/privileges-writes.adoc[write] sub-graph privileges.
 * Manage <<access-control-dbms-administration-impersonation, impersonation privileges>>.
 * Manage <<access-control-dbms-administration-execute, procedure security>>.
-* Manage <<access-control-dbms-administration-load-privileges, load data security>>.
+* Manage xref:authentication-authorization/load-privileges.adoc[load data security].
 
 To enable a user to perform these tasks, you can grant them the `admin` role, but it is also possible to make a custom role with a subset of these privileges.
 All privileges are also assignable using Cypher commands.

modules/ROOT/pages/authentication-authorization/limitations.adoc

@@ -26,10 +26,10 @@ Further to that, Neo4j's role-based access control has some limitations and impl
 == Security and indexes
 
 Neo4j lets you create and use indexes to speed up Cypher queries.
-See the link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/search-performance-indexes/[Cypher Manual -> Indexes] for more details on the different types of indexes available in Neo4j.
+See the link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/[Cypher Manual -> Indexes] for more details on the different types of indexes available in Neo4j.
 
 However, Neo4j’s security model still controls what results you see, regardless of whether or not you use indexes.
-For example, when you use link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/search-performance-indexes/overview/[search-performance indexes] (non–full-text) indexes, queries return the same results they would without any index.
+For example, when you use link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/search-performance-indexes/[search-performance indexes] (non–full-text) indexes, queries return the same results they would without any index.
 This means that, if the security model causes fewer results to be returned due to restricted read access in xref:authentication-authorization/manage-privileges.adoc[graph and sub-graph access control],
 the index will also return the same fewer results.
 

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

@@ -38,7 +38,7 @@ If you have zero tolerance for downtime and data loss, you might want to conside
 ** use SSL/TLS for the backup network communication (online only).
 ** keep your databases as archive files (online or offline).
 * How many backups you want to keep.
-* Where the backups will be stored — drive or remote server, cloud storage, different data center, different location, etc.
+* Where the backups will be stored — drive or remote server, cloud storage, different data center, different location, etc.
 +
 [TIP]
 ====
@@ -51,15 +51,14 @@ This ensures that if for some reason your Neo4j DBMS crashes, you will be able t
 == Backup and restore options
 
 Neo4j supports backing up and restoring both online and offline databases.
-It uses xref:neo4j-admin-neo4j-cli.adoc[Neo4j Admin tool] commands, which can be run from a live, as well as from an offline Neo4j DBMS.
+It uses xref:neo4j-admin-neo4j-cli.adoc[Neo4j Admin tool] commands that can be executed on a Neo4j DBMS, whether it is running or offline.
 All `neo4j-admin` commands must be invoked as the `neo4j` user to ensure the appropriate file permissions.
 
-* `neo4j-admin database backup/restore` (Enterprise only) -– used for performing online backup (xref:backup-restore/modes.adoc#full-backup[full] and xref:backup-restore/modes.adoc#differential-backup[differential]) and restore operations.
-The database to be backed up must be in **online** mode.
-The command produces an immutable artifact, which has an inspectable API to aid management and operability.
-This command is suitable for production environments, where you cannot afford downtime.
-+
-The command can also be invoked over the network if access is enabled using `server.backup.listen_address`.
+* `neo4j-admin database backup/restore` label:enterprise[Enterprise Edition] – used for performing online backup (xref:backup-restore/modes.adoc#full-backup[full] and xref:backup-restore/modes.adoc#differential-backup[differential]) and restore operations.
+** The database to be backed up must be in **online** mode.
+** The command produces an immutable artifact, which has an inspectable API to aid management and operability.
+** This command is suitable for production environments, where you cannot afford downtime.
+** The command can also be invoked over the network if access is enabled using `server.backup.listen_address`.
 +
 [NOTE]
 ====
@@ -73,9 +72,9 @@ For more information, refer to the xref:backup-restore/online-backup.adoc#backup
 When using `neo4j-admin database backup` in a cluster, it is recommended to back up from an external instance as opposed to reuse instances that form part of the cluster.
 ====
 * `neo4j-admin database dump/load` –- used for performing offline dump and load operations.
-The database to be dumped must be in **offline** mode.
-The dump command can only be invoked from the server command line and is suitable for environments where downtime is not a factor.
-The command produces an archive file that follows the format _<databasename><timestamp>.dump_.
+** The database to be dumped must be in **offline** mode.
+** The dump command can only be invoked from the server command line and is suitable for environments where downtime is not a factor.
+** The command produces an archive file that follows the format _<databasename><timestamp>.dump_.
 * `neo4j-admin database copy` –- used for copying an offline database or backup.
 This command can be used for cleaning up database inconsistencies and reclaiming unused space.
 
@@ -84,23 +83,9 @@ This command can be used for cleaning up database inconsistencies and reclaiming
 File system copy-and-paste of databases is not supported and may result in unwanted behavior, such as corrupt stores.
 ====
 
-=== Considerations for backing up and restoring databases in a cluster
-
-Backing up a database in a clustered environment is not essentially different from a standalone backup, apart from the fact that you must know which server in a cluster to connect to.
-Use `SHOW DATABASE <database>` to learn which servers are hosting the database you want to back up.
-See xref:clustering/monitoring/show-databases-monitoring.adoc#show-databases-monitoring-listing-single[Listing a single database] for more information.
-
-However, _restoring_ a database in a cluster is different since it is not known in advance how a database is going to be allocated to the servers in a cluster.
-This method relies on the seed already existing on one of the servers.
-The recommended way to restore a database in a cluster is to xref::database-administration/standard-databases/seed-from-uri.adoc[seed from URI].
+The following table summarizes the commands' capabilities and usage.
 
-[NOTE]
-====
-The Neo4j Admin commands `backup`, `restore`, `dump`, `load`, `copy`, and `check-consistency` are not supported for use on xref:database-administration/composite-databases/concepts.adoc[Composite databases].
-They must be run directly on the databases that are associated with that Composite database.
-====
-
-.The following table describes the commands' capabilities and usage.
+.`neo4j-admin` commands for backing up and restoring databases
 [cols="<,^,^,^",frame="topbot",options="header"]
 |===
 | Capability/ Usage
@@ -184,18 +169,45 @@ They must be run directly on the databases that are associated with that Composi
 | {check-mark}
 |===
 
+
+[NOTE]
+====
+The Neo4j Admin commands `backup`, `restore`, `dump`, `load`, `copy`, and `check-consistency` are not supported for use on xref:database-administration/composite-databases/concepts.adoc[Composite databases].
+They must be run directly on the databases that are associated with that Composite database.
+====
+
+
+== Considerations for backing up and restoring databases in a cluster
+
+Backing up a database in a clustered environment is not essentially different from a standalone backup, apart from the fact that you must know which server in a cluster to connect to.
+Use `SHOW DATABASE <database>` to learn which servers are hosting the database you want to back up.
+See xref:clustering/monitoring/show-databases-monitoring.adoc#show-databases-monitoring-listing-single[Listing a single database] for more information.
+
+Restoring from the command line involves putting a copy of the database on disk on each server that will need it.
+That can be awkward to achieve.
+The recommended way to restore a database in a cluster is to xref::database-administration/standard-databases/seed-from-uri.adoc[seed from URI].
+
+[IMPORTANT]
+====
+By default, a database backup includes only the database contents.
+If you choose to include metadata, the backup also stores the role-based access control (RBAC) settings associated with the database.
+
+When restoring, you have the flexibility to define the target topology (how many primaries and secondaries are desired for the database), which may differ from the topology at backup time.
+The database will then be allocated across the available servers according to that topology. 
+====
+
 [[backup-planning-databases]]
-== Databases to backup
+== Databases to back up
 
 A Neo4j DBMS can host multiple databases.
-Both Neo4j Community and Enterprise Editions have a default user database, called `neo4j`, and a `system` database, which contains configurations, e.g., operational states of databases, security configuration, schema definitions, login credentials, and roles.
-In the Enterprise Edition, you can also create additional user databases.
+Both Neo4j Community and Enterprise Editions have a default user database named `neo4j` and a `system` database.
+The `system` database contains configurations, e.g., operational states of databases, security configuration, schema definitions, login credentials, and roles.
+
+In the Enterprise Edition, you can also create multiple user databases.
 Each of these databases is backed up independently of one another.
 
-[NOTE]
-====
 It is very important to store a recent backup of your databases, including the `system` database, in a safe location.
-====
+
 
 [[backup-planning-additional]]
 == Additional files to back up
@@ -215,4 +227,4 @@ If you have a cluster, you should back up these files for each cluster member.
 
 For any backup, it is important that you store your data separately from the production system, where there are no common dependencies, and preferably off-site.
 If you are running Neo4j in the cloud, you may use a different availability zone or even a separate cloud provider.
-Since backups are kept for a long time, the longevity of archival storage should be considered as part of backup planning.
+Since backups are kept for a long time, the longevity of archival storage should be considered as part of backup planning.

modules/ROOT/pages/changes-deprecations-removals.adoc

@@ -408,7 +408,7 @@ Replaced by xref:procedures.adoc#procedure_dbms_unquarantineDatabase[`dbms.unqua
 | label:deprecated[Deprecated in 5.26] +
 label:removed[Removed in Cypher 25] +
 Replaced by the Cypher command `CREATE VECTOR INDEX`.
-For more information, see the link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/semantic-indexes/vector-indexes/#create-vector-index/[Cypher Manual → Create a vector index].
+For more information, see the link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/semantic-indexes/vector-indexes/#create-vector-index[Cypher Manual → Create a vector index].
 
 
 | xref:procedures.adoc#procedure_dbms_cluster_uncordonServer[`dbms.cluster.uncordonServer()`]

modules/ROOT/pages/clustering/servers.adoc

@@ -120,7 +120,7 @@ Once dropped, a server cannot rejoin a cluster.
 
 [NOTE]
 ====
-The same physical hardware can rejoin the cluster, provided the Neo4j installation has been "reset" (either re-installing, or running `neo4j-admin unbind`), causing it to receive a new generated server ID on next startup.
+The same physical hardware can rejoin the cluster, provided the Neo4j installation has been "reset" (either re-installing, or running `neo4j-admin server unbind`), causing it to receive a new generated server ID on next startup.
 ====
 
 == Listing servers

modules/ROOT/pages/configuration/neo4j-conf.adoc

@@ -6,7 +6,7 @@ The _neo4j.conf_ file is the main source of configuration settings in Neo4j and
 The location of the _neo4j.conf_ file in the different configurations of Neo4j is listed in xref:configuration/file-locations.adoc[Default file locations].
 
 Most of the configuration settings in the _neo4j.conf_ file apply directly to Neo4j itself, but there are also other settings related to the Java Runtime (the JVM) on which Neo4j runs.
-For more information, see the xref:configuration/neo4j-conf.adoc#neo4j-conf-JVM[JVM specific configuration settings].
+For more information, see the <<neo4j-conf-JVM, JVM specific configuration settings>>.
 Many of the configuration settings are also used by `neo4j` launcher scripts.
 
 

modules/ROOT/pages/database-administration/standard-databases/create-databases.adoc

@@ -137,7 +137,7 @@ Replaced by `existingDataSeedServer`.
 | URI to a backup or a dump from an existing database.
 |
 Defines an identical seed from an external source which will be used to seed all servers.
-For more information, see xref::database-administration/standard-databases/seed-from-uri.adoc[Seed from a URI].
+For more information, see xref:database-administration/standard-databases/seed-from-uri.adoc[Create a database from a URI].
 
 | `seedConfig`
 | Comma-separated list of configuration values.
@@ -198,14 +198,14 @@ Defines a seed from an external source, which will be used to seed all servers.
 | `seedConfig`
 | Comma-separated list of configuration values.
 |
-For more information see xref::clustering/databases.adoc#cluster-seed-uri[Seed from URI].
+For more information see xref:database-administration/standard-databases/seed-from-uri.adoc[Create a database from a URI].
 
-| `txLogEnrichment`
+| `txLogEnrichment`§
 | `FULL` \| `DIFF` \| `OFF`
 |
 Defines the level of enrichment applied to transaction logs for Change Data Capture (CDC) purposes.
 
-For details about enrichment mode, see link:{neo4j-docs-base-uri}/cdc/current/get-started/self-managed/#set-enrichment-mode/[Change Data Capture Manual -> Enable CDC on self-managed instances -> Set the enrichment mode].
+For details about enrichment mode, see link:{neo4j-docs-base-uri}/cdc/current/get-started/self-managed/#tweak-mode[Change Data Capture Manual -> Enable CDC on self-managed instances -> Toggle CDC mode].
 
 | `storeFormat`
 | `aligned` \| `standard` \| `high_limit` \| `block`

modules/ROOT/pages/introduction.adoc

@@ -160,7 +160,7 @@ a| APOC 450+ link:https://neo4j.com/docs/apoc/5/[Core Procedures and Functions]
 
 3+^s| Indexes and constraints
 
-| link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/search-performance-indexes/overview/[Fast writes via native label indexes]
+| link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/[Fast writes via native label indexes]
 | {check-mark}
 | {check-mark}
 

modules/ROOT/pages/kubernetes/operations/backup-restore.adoc

@@ -1053,7 +1053,7 @@ To restore the `system` database, follow the steps described in xref:kubernetes/
 To migrate from persistent volume-based backups to cloud-native backups, you need to follow these steps:
 
 . Perform a final traditional backup to ensure you have the latest data.
-For more information, see <<kubernetes-neo4j-backup-on-prem, Prepare to back up a database(s) to on-premises storage>> and <<kubernetes-neo4j-backup, Back up your databases>>.
+For more information, see <<kubernetes-neo4j-backup-on-prem, Prepare to back up a database(s) to on-premises storage>> and <<#_back_up_your_databases, Back up your databases>>.
 . Upload existing backups to the cloud storage bucket if needed.
 You can use cloud provider CLI tools to transfer your backup files:
 ** For AWS S3: `aws s3 cp /path/to/backups s3://your-bucket/backups --recursive`
@@ -1062,5 +1062,5 @@ You can use cloud provider CLI tools to transfer your backup files:
 . Update the _backup-values.yaml_ file to configure the cloud provider, bucket name, and credentials.
 See <<kubernetes-neo4j-backup-cloud, Prepare to back up a database(s) to a cloud provider (AWS, GCP, and Azure) bucket>> for details.
 . Install the _neo4j-admin_ Helm chart with the updated _backup-values.yaml_ file to back up your databases to the cloud provider bucket.
-See <<_back_up_your_databases, Back up your databases>> for details.
+See <<#_back_up_your_databases, Back up your databases>> for details.