Skip to content

Commit 33a7825

Browse files
authored
Add info on skipping consistency check in 4.x (neo4j#932) (neo4j#964)
Cherry-picked from neo4j#932
1 parent 4477998 commit 33a7825

File tree

2 files changed

+2
-1
lines changed

2 files changed

+2
-1
lines changed

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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -178,6 +178,7 @@ Therefore, it is highly recommended to perform the backup and consistency check
178178
+
179179
Alternatively, you can decouple the backup operation from the consistency check (using the `neo4j-admin backup` option `--check-consistency=false`) and schedule that part of the workflow to happen at a later point in time, on a dedicated machine.
180180
Consistency checking a backup is vital for safeguarding and ensuring the quality of the data, and should not be underestimated.
181+
For more information, see xref:tools/consistency-checker.adoc[Consistency checker].
181182
+
182183
[TIP]
183184
====

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -229,4 +229,4 @@ If you have a cluster, you should back up these files for each cluster member.
229229

230230
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.
231231
If you are running Neo4j in the cloud, you may use a different availability zone or even a separate cloud provider.
232-
Since backups are kept for a long time, the longevity of archival storage should be considered as part of backup planning.
232+
Since backups are kept for a long time, the longevity of archival storage should be considered as part of backup planning.

0 commit comments

Comments
 (0)