You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -154,11 +157,20 @@ It is recommended to use `SHOW USERS`, `SHOW ROLES`, and `SHOW ROLE $role PRIVIL
154
157
|The size of the page cache to use for the backup process.
155
158
|
156
159
160
+
|--parallel-download[=true\|false]
161
+
|label:new[Introduced in 2025.11] Download backup data from multiple Neo4j instances in parallel.
162
+
|false
163
+
157
164
|--parallel-recovery[=true\|false]
158
165
| Allow multiple threads to apply pulled transactions to a backup in parallel. For some databases and workloads, this may reduce backup times significantly.
159
166
Note: this is an EXPERIMENTAL option. Consult Neo4j support before use.
160
167
|false
161
168
169
+
|--recovery[=true\|false]
170
+
|label:new[Introduced in 2025.11] Perform recovery as part of the full backup. Skipping recovery might result in faster backups,
171
+
but recovery will have to be done during restore time.
172
+
|true
173
+
162
174
|--prefer-diff-as-parent
163
175
|label:new[Introduced in 2025.04] When performing a differential backup, prefer the latest non-empty differential backup as the parent instead of the latest backup.
164
176
|false
@@ -380,6 +392,15 @@ The server selection occurs in the following order:
380
392
* The DBMS first selects all servers hosting the database in secondary mode.
381
393
* If it is not possible to back up from one of the secondaries, the DBMS attempts to take a backup from the primary followers before finally trying the database primary writer.
382
394
395
+
[role=label--new-2025.11]
396
+
==== Using `--parallel-download`
397
+
398
+
Starting from 2025.11, the `--parallel-download` option is available.
399
+
When enabled, the backup process will pull data from multiple instances which have been either defined in the
400
+
--from or determined from --remote-address-resolution.
401
+
402
+
Note that this will speed up the backup process if there are enough throughput provisioned in both the
403
+
backup process and the instances from which data is being pulled from.
0 commit comments