With the ability to download a database Dump form Aura you have another tool along with Backup/Restore to manage your data and use it with flexibility in Aura and on premise.
In this case we want to download a database Dump form an existing Aura instance and load to another (or it could be the same) instance.
This way you can decide to roll back your database to a previous state (note that a dump is a snapshot, and not a full backup) or decide you need to do some development and test on a duplicate of your current database etc...
1 - Download a database Dump (also called an Export)
Click the database name in the Aura console and open up the SNAPSHOTS tab and download the dump file.
2 - Download the Export (a.k.a Dump file) locally to your machine.
Download time is dependent on the dump file size (compressed datastore size) and of course your connection speed.
Note that the file will ultimately be saved as graph.db.dump locally (you can rename it but keep the file extension)
3 - Upload the local dump file back to Aura .
To upload a dump file you will need push-to-cloud but as you may be using different versions of neo4j, you need to use the right binaries.
a - Dump file from a Neo4j v3.5.x (or v3.6.x in Aura)
You will need a Neo4j installation. the easiest option is to use the neo4j Desktop to achieve this as the push-to-cloud jar file is present by default.
Nevertheless if you need it again you can find it here: https://dist.neo4j.org/neo4j-push-to-cloud-3.jar
b - Dump file from a Neo4j v4.x (or Aura 4)
Please download the push-to-jar binaries from here: https://dist.neo4j.org/neo4j-push-to-cloud-4.jar and place them in <NEO4J_HOME>/lib
To verify if push to cloud is present run
<NEO4J_HOME>/bin/neo4j-admin help push-to-cloud
4 - Run the push-to-cloud command
Now that everything is ready we can run the command to upload the dump.
We will need the Aura database URI (neo4j+s//<your_dbid>.databases.neo4j.io) as can be seen in the Aura console and your password (this is the password to the database - not your Aura Console credentials). If you are intending on creating a new database, you need to do so now before you can run the command.
The minimal set you will need to provide is (this means you will need to provide further info in interactive mode, like the username and password and confirmation you want to overwrite the content)
push-to-cloud --bolt-uri neo4j+s://<dbid>.databases.neo4j.io --dump /path/to/dumpfile/graph.db
Example:
Note: in this example we have included the password on the command line but you can set it via environment variables (NEO4J_USERNAME, NEO4J_PASSWORD) or use the interactive mode for better security
user@hostname:installation-3.5.18$ bin/neo4j-admin push-to-cloud \
--bolt-uri=neo4j+s://ac43ded9.databases.neo4j.io \
--dump=/home/username/Downloads/graph.db.dump \
--username=neo4j \
--password='U1JQFOX5_wgdwptm41PkHLekUBtDZ0y_7QX51RQuncU' \
--overwrite=true
Upload
.................... 10%
.................... 20%
.................... 30%
.................... 40%
.................... 50%
.................... 60%
.................... 70%
.................... 80%
.................... 90%
.................... 100%
We have received your export and it is currently being loaded into your Aura instance.
You can wait here, or abort this command and head over to the console to be notified of when your database is running.
Import progress (estimated)
.................... 10%
.................... 20%
.................... 30%
.................... 40%
.................... 50%
.................... 60%
.................... 70%
.................... 80%
.................... 90%
.................... 100%
Your data was successfully pushed to Aura and is now running.
It is safe to delete the dump file now: /home/username/Downloads/graph.db.dump
5 - Monitor status and availability of your database in the Aura console
While the dump file is uploading the database is still marked as Running.
Then the database will display Loading
And when it is complete you will see Running status again
Additional notes
If you use the --database switch the command assumes this is for the local database instance and will search in the matching dump location
For full options of the push-to-cloud command see the help:
user@hostname:$ bin/neo4j-admin help push-to-cloud
usage: neo4j-admin push-to-cloud [--database=<name>]
[--dump=</path/to/my-neo4j-database-dump-file>]
[--dump-to=</path/to/dump-file-to-be-created>]
--bolt-uri=<bolt+routing://mydatabaseid.databases.neo4j.io>
[--verbose=<true/false>] [--username=<neo4j>]
[--password=<mYs3cr3tPa$$w0rd>]
[--overwrite=<true/false>]
environment variables:
NEO4J_CONF Path to directory which contains neo4j.conf.
NEO4J_DEBUG Set to anything to enable debug output.
NEO4J_HOME Neo4j home directory.
HEAP_SIZE Set JVM maximum heap size during command execution.
Takes a number and a unit, for example 512m.
Push your local database to a Neo4j Aura instance. The database must be shutdown
in order to take a dump to upload. The target location is your Neo4j Aura Bolt
URI. You will be asked your Neo4j Cloud username and password during the
push-to-cloud operation.
options:
--database=<name>
Name of database. [default:graph.db]
--dump=</path/to/my-neo4j-database-dump-file>
Path to an existing database dump for upload. This arugment cannot be used
together with --database. [default:null]
--dump-to=</path/to/dump-file-to-be-created>
Target path for dump file. Used in combination with the --database
argument. [default:null]
--bolt-uri=<bolt+routing://mydatabaseid.databases.neo4j.io>
Bolt URI of target database
--verbose=<true/false>
Enable verbose output. [default:null]
--username=<neo4j>
Optional: Username of the target database to push this database to. Prompt
will ask for username if not provided. Alternatively NEO4J_USERNAME
environment variable can be used. [default:null]
--password=<mYs3cr3tPa$$w0rd>
Optional: Password of the target database to push this database to. Prompt
will ask for password if not provided. Alternatively NEO4J_PASSWORD
environment variable can be used. [default:null]
--overwrite=<true/false>
Optional: Overwrite the data in the target database. [default:false]
user@hostname:
Comments
0 comments
Please sign in to leave a comment.