Suppose you are planning to take a backup of your existing database and upload that into Neo4j Aura. In that case, 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 a specific database/backup has been corrupted, you can perform a consistency check.

This can be achieved by running a Consistency Check in your database or backup.

neo4j-home> bin/neo4j-admin database check <database-name> 

 To run the consistency check using your dump or backup file, use:

neo4j-home> bin/neo4j-admin database check <database-name> --from-path=full_backup_path

To run the consistency check on an Aura backup file, you first need to aggregate the backup running:

neo4j-home> bin/neo4j-admin database aggregate-backup --from-path=full_backup_path

If the tool comes back with no error, then the database is consistent. Otherwise, an error is returned and a report is written. 

For more information on how to fix inconsistencies with your database, please refer to: How do I resolve Consistency Check errors 

 

Note that with Aura, you can't check the consistency of your database on your own, and here we 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.

Instead, Aura, as part of the automatic backup process, at our end, runs a consistency check which validates that the backup copy is valid and ensures the data can be restored.

At times, errors may be encountered; in those situations, customer support may contact you so that you can perform the corrective action. This includes dropping and recreating your index store, which can be done by following these articles:

Indexes - Capture / Drop / Recreate existing.