How to Setup Neo4j Backup Wrapper Script
For operators of Neo4j looking to implement regular hot backups of a Neo4j database using automated job scheduling, applying this
neo4j-admin backup will make your job easier. Simply read this guide, customize according to your environment, and
set your job scheduler to run the
backupDatabase.sh wrapper script.
This backup script will work with Neo4j version
contact Neo4j Customer Support for information on how to implement the backup script.
First, download the script link: here.
To setup the backup wrapper script on Linux systems, follow these steps:
Review and modify the script User and Mail variables as required.
The default log location is
$NEO4J_HOME/logs/backupDatabase_$timestamp.log. The location and timestamped naming convention can be modified as required in the script under the
chmod 750 $NEO4J_HOME/bin/backupDatabase.shto set execute permissions on the script
Show options by running
-d Backup destination directory to save files to (Mandatory) -b Backup name : Default graph.db-backup (Optional) -f Set From Host : Default localhost (Optional) -c Run Consistency Check [false] : Default true (Optional) -m Set HEAP_SIZE : Default 2G (Optional) -p Set pache cache : Default 4G (Optional) -h Print help message
$ ./backupDatabase.sh `-d /<full_path_to_backup_dir>/backup`
NOTE 1: Neo4j will automatically determine whether to run a full or incremental backup, by default the script is designed to run incremental backups to the mandatory backup location provided by the
-d flag. To perform an incremental backup you need to specify the same location of your previous backup.
If a full backup is desired, the script can be modified to comment out the following line in the script as shown:
#bname=graph.db-backup #POSSIBLY CHANGE ME, USED FOR INCREMENTAL BACKUPS
And uncomment the following line in the script as shown:
bname=graph.db-backup-$timestamp #POSSIBLY CHANGE ME, USED FOR FULL BACKUPS
This will force the backup to use a new timestamped naming convention for the backup; if this is run daily, then a full backup will occur each day into the respective timestamped directory.
NOTE 2: The default setting for
--check-consistency is set to false, so this will not run against the active online database.
The consistency check will be run offline by default against the backup once it is completed.
The consistency check can be omitted from being run offline by specifying the
-c false flag.
NOTE 3: The script will verify whether the Neo4j database is online before proceeding and will exit if the database is not running.
NOTE 4: The default setting for
--fallback-to-full is set to true. If an incremental backup fails, the script will move the old backup to <name>.err.<N> and fallback to a full backup instead.
$ ./backupDatabase.sh -d /<full_path_to_backup_dir>/backup `-f 192.168.0.10:6362`
NOTE 1: The default for the
-f setting is
localhost:6362. You can specify an alternate remote host IP or IP:Port.
$ ./backupDatabase.sh -d /<full_path_to_backup_dir>/backup `-b graph.db-TEST`
NOTE 1: Neo4j will automatically determine whether to run a full or incremental backup, by default the script is designed to run incremental backup. If the graph.db-TEST directory in this example does NOT exist, then a full backup will occur.
$ ./backupDatabase.sh -d /<full_path_to_backup_dir>/backup `-p 15G`
NOTE 1: The default pagecache setting is 4G
$ ./backupDatabase.sh -d /<full_path_to_backup_dir>/backup `-m 8G -p 15G`
NOTE 1: The default HEAP size setting is 2G and the default pagecache setting is 4G
Was this page helpful?