What is Consistency Checker? How can I fix/avoid inconsistencies in my data?

If you are planning to take a backup of your existing database and upload that into Neo4j Aura, we recommend you check the consistency of the backup before uploading it into Aura to avoid errors.

A database’s consistency could be compromised if a software or hardware failure has occurred that affects the Neo4j database. To check if specific database/backup has been corrupted, you can perform a consistency check.

This can be achieved by utilizing thecheck-consistency=trueoption with thebackupcommand 

neo4j-home> bin/neo4j-admin backup --backup-dir=/home/backups --name=graph.db --check-consistency=true

If the tool comes back with no error, then the database is consistent. Otherwise, an error is returned and a report is written. See the Neo4j Operations Manual for more options.

It is also possible to check the consistency of an offline dump. For more details please check

Four ways to check the consistency of a graph

For more information on how to fix inconsistencies with your database, please refer below articles:

How do I resolve consistency check errors

How do I resolve inconsistency problems on an instance of a cluster

It is worth noting that with Aura you don't have the ability to check the consistency of your database on your own and this article goal is to explain how you can validate the consistency of your existing database or dump beforehand so that you don't get any errors during Import to Aura. With Aura, as part of the automatic backup process, at our end, we run a consistency check which validates that the backup copy is valid and ensure the data can be restored. At times errors may be encountered, in those situations, Aura support will raise a proactive ticket with you so that you can perform the corrective action. This includes dropping and recreating your index store which can be done by following this knowledge base article available here.