Merge branch 'dev' into 2024-12-seed-restore-until

Author: NataliaIvakina

antora.yml

@@ -1,13 +1,14 @@
 name: operations-manual
 title: Operations Manual
-version: '5'
+version: '2025.01'
+current: true
 start_page: ROOT:index.adoc
 nav:
 - modules/ROOT/content-nav.adoc
 asciidoc:
   attributes:
-    neo4j-version: '5'
-    neo4j-version-minor: '5.26'
-    neo4j-version-exact: '5.26.0'
-    neo4j-buildnumber: '5.26'
+    neo4j-version: '2025.01'
+    neo4j-version-minor: '2025.01'
+    neo4j-version-exact: '2025.01.0'
+    neo4j-buildnumber: '2025.01'
     neo4j-debian-package-version: '1:5.22.0@'

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

@@ -180,7 +180,7 @@ Use `REVOKE` if you want to remove a privilege.
 
 Common errors, such as misspellings or attempts to revoke privileges that have not been granted or denied, will lead to notifications.
 Some of these notifications may be replaced with errors in a future major version of Neo4j.
-See link:{neo4j-docs-base-uri}/status-codes/{page-version}/notifications/all-notifications[Status Codes -> Notification codes] for details on notifications.
+See link:{neo4j-docs-base-uri}/status-codes/{page-version}/notifications/all-notifications[Status Codes for Errors & Notifications -> Server notifications] for details on notifications.
 
 The hierarchy between the different database privileges is shown in the image below.
 

modules/ROOT/pages/authentication-authorization/ldap-integration.adoc

@@ -197,7 +197,7 @@ dbms.security.ldap.authorization.system_username=cn=search-account,cn=Users,dc=e
 +
 [source, properties]
 ----
-dbms.security.ldap.authorization.system_password=mypassword
+dbms.security.ldap.authorization.system_password=your_password
 ----
 
 .. Configure which attribute to search for by adding the following lines to the _neo4j.conf_ file (replacing `myattribute` with the actual attribute name):
@@ -490,7 +490,7 @@ ldapsearch -v -H ldap://myactivedirectory.example.com:389 -x -D cn=john,cn=Users
 ----
 # ldapsearch -v -H ldap://<dbms.security.ldap.host> -x -D <dbms.security.ldap.authorization.system_username> -w <dbms.security.ldap.authorization.system_password> -b <dbms.security.ldap.authorization.user_search_base> "<dbms.security.ldap.authorization.user_search_filter>" <dbms.security.ldap.authorization.group_membership_attributes>
 
-ldapsearch -v -H ldap://myactivedirectory.example.com:389 -x -D cn=search-account,cn=Users,dc=example,dc=com -w mypassword -b cn=Users,dc=example,dc=com "(&(objectClass=*)(cn=john))" memberOf
+ldapsearch -v -H ldap://myactivedirectory.example.com:389 -x -D cn=search-account,cn=Users,dc=example,dc=com -w your_password -b cn=Users,dc=example,dc=com "(&(objectClass=*)(cn=john))" memberOf
 ----
 
 . Verify that the value of the returned membership attribute is a group that is mapped to a role in `dbms.security.ldap.authorization.group_to_role_mapping`.

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

@@ -107,6 +107,11 @@ The `<backup-path>` parameter can also inspect backups stored in AWS S3 buckets
 |
 |===
 
+[NOTE]
+====
+The `--latest-backup` and `--latest-chain` options cannot be used together.
+====
+
 
 [[aggregate-backup-example]]
 == Examples

modules/ROOT/pages/clustering/databases.adoc

@@ -268,8 +268,8 @@ Neo4j 5.24 introduces the xref:procedures.adoc#procedure_dbms_cluster_recreateDa
 * To change the database store to a specified backup, while keeping all the associated privileges for the database.
 
 * 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.
-
+See xref:clustering/disaster-recovery.adoc[Disaster recovery] for more information.
+ 
 [CAUTION]
 ====
 The recreate procedure works only for real user databases and not for composite databases, or the `system` database.
@@ -506,7 +506,7 @@ To determine the cause of the problem, it is recommended to look at the `debug.l
 
 The `FileSeedProvider`  supports:
 
-** `file:` 
+** `file:`
 
 [[url-connection-seed-provider]]
 ==== URLConnectionSeedProvider
@@ -522,8 +522,8 @@ The `URLConnectionSeedProvider` supports the following:
 
 The `CloudSeedProvider` supports:
 
-** `s3:` 
-** `gs:` 
+** `s3:`
+** `gs:`
 ** `azb:`
 
 The `CloudSeedProvider` supports using xref:backup-restore/modes.adoc#differential-backup[differential backups] as seeds.
@@ -538,7 +538,7 @@ include::partial$/aws-s3-overrides.adoc[]
 
 include::partial$/aws-s3-credentials.adoc[]
 
-. Create database from `myBackup.backup`. 
+. Create database from `myBackup.backup`.
 +
 [source,shell, role="nocopy"]
 ----
@@ -551,7 +551,7 @@ CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 's3:/myBucket/myBack
 
 include::partial$/gcs-credentials.adoc[]
 
-. Create database from `myBackup.backup`. 
+. Create database from `myBackup.backup`.
 +
 [source,shell]
 ----
@@ -563,7 +563,7 @@ CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 'gs:/myBucket/myBack
 
 include::partial$/azb-credentials.adoc[]
 
-. Create database from `myBackup.backup`. 
+. Create database from `myBackup.backup`.
 +
 [source,shell]
 ----
@@ -578,6 +578,8 @@ The `CloudSeedProvider` supports seeding up to a specific date or transaction ID
 
 To seed up to a specific date, you need to pass the differential backup, which contains the data up to that date.
 
+** `s3:` label:deprecated[Deprecated in 5.26]
+
 [source,shell]
 ----
 CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 's3:/myBucket/myBackup.backup', seedRestoreUntil: datetime("2019-06-01T18:40:32.142+0100") }
@@ -605,7 +607,8 @@ This will seed the database with transactions up to, but not including transacti
 | URI example
 
 | `file:`
-| `FileSeedProvider`
+| `FileSeedProvider` +
+`URLConnectionSeedProvider` label:deprecated[Deprecated in 5.26]
 | `file:/tmp/backup1.backup`
 
 | `ftp:`
@@ -621,7 +624,8 @@ This will seed the database with transactions up to, but not including transacti
 | `\https://myhttp.com/backups/backup1.backup`
 
 | `s3:`
-| `CloudSeedProvider`
+| `S3SeedProvider` label:deprecated[Deprecated in 5.26], +
+`CloudSeedProvider`
 | `s3://mybucket/backups/backup1.backup`
 
 | `gs:`