Upgrade checklist for 4.x patch release
This chapter describes how to prepare to upgrade the Neo4j DBMS to a newer
PATCHrelease within the same
Follow the checklist to prepare for upgrading your Neo4j deployment:
Complete all prerequisites for the upgrade.
Back up your current deployment to avoid losing data in case of failure.
Neo4j does not support downgrades. If the upgrade is not successful, you have to do a full rollback, including restoring a pre-upgrade backup.
Download the new version of Neo4j.
Perform the upgrade.
If you are upgrading a Causal Cluster, complete the checklist for each cluster member.
Depending on your particular deployment and environment, it is important to design an appropriate backup and restore strategy. For more information about what to consider when deciding on your backup and restore strategy, what needs to be backed up, and the different backup modes and options, see the Operations Manual → Backup and restore planning page of your version.
Prepare a neo4j.conf file to be used by the new installation if you have any custom values configured in your old neo4j.conf file. Look for:
Any non-default settings.
Any custom values of the settings
(In cluster installations) Cluster-specific configuration settings, which might be different for the different cluster members.
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 Neo4j version and deployment type.
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. For more information, see Operations Manual → Log files.
Was this page helpful?