This section describes how to prepare for upgrading your Neo4j deployment.
It covers the following topics:
Upgrading your Neo4j deployment ensures that you are provided with the latest improvements in performance, security, and bug fixes.
The following are methods of keeping your Neo4j deployment up-to-date:
The process of upgrading an existing Neo4j deployment (single or clustered) to a newer Neo4j version, when such process does not require changes to the configuration or to the applications that use Neo4j.
What needs to be upgraded
systemdatabase schema, which restructures the contents of that database. This is done automatically on standalone server and in static cluster upgrades (where you temporarily set each server as standalone), but need to be run manually on rolling upgrades after the other two upgrades (product and stores) have been done.
The process of upgrading an existing Neo4j deployment (single or clustered) to a newer Neo4j version, when such process requires a review of the configuration(s) and the applications that use Neo4j.
What needs to be upgraded and migrated
systemdatabase schema - same as in upgrade.
For more information, see Neo4j Migration Guide.
The following upgrade paths are supported:
The following upgrade checklist provides a high-level overview of the tasks you have to perform:
If you are upgrading a Causal Cluster, do the tasks for each member of the cluster.
It is recommended to perform and verify the following backups, to avoid losing data in case of a failure.
neo4j-admin dumpand store it in a safe location.
Even though a Neo4j upgrade does not require changes to the configuration, you still have to prepare the new neo4j.conf file to be used by the new deployment.
Based on the findings in this chapter, allocate a staging test environment for the upgrade and do a test upgrade. The test upgrade will give you valuable information about the time required for the production upgrade. Follow the steps as per your deployment type. For more information, see Section 10.2, “Upgrade a single instance” or Section 10.3, “Upgrade a Causal Cluster”.
The neo4j.log file contains information on how many steps the upgrade will involve and how far it has progressed. It is a good idea to monitor this log.