Upgrade a standalone server with an RPM package manager

This example shows how to upgrade a Neo4j standalone server to any 2025-2026 version using an RPM package manager.

If you are moving from 5.26 LTS to any 2025-2026 version, it is recommended to read the following pages before continuing:

For critical systems, it is recommended to:

Backup your server(s), including databases, configurations, licenses, encryption keys, and custom plugins to avoid losing data in case of failure. For details, see the Operations Manual Backup and Restore or Docker → Dump and load a Neo4j database (offline) .
Perform the upgrade in a test environment.

Upgrade steps

Stop the neo4j service by running:
```
sudo systemctl stop neo4j
```
Upgrade your Neo4j deployment by running:
```
sudo yum update neo4j-enterprise
```
If you are upgrading Community Edition, replace neo4j-enterprise with neo4j.
Start the Neo4j service by running:
```
sudo systemctl start neo4j
```

Monitor the logs

When Neo4j restarts, it can be useful to monitor the logs for any errors or warnings caused by the upgrade. You can find information about the upgrade in the neo4j.log file.

Further information

The Neo4j RPM yum repository is configured as described in Operations Manual → Red Hat, CentOS, Fedora, and Amazon Linux (.rpm).
For more information about the supported package and service managers, see Operations Manual → Linux installation.