Installation: Upgrading to a New Version
On a live system, a minor version upgrade process typically takes around 30 seconds.
Upgrading a RavenDB instance to a new version is very simple. To do so:
Download a distribution package from here.
Shut RavenDB Server down.
- for a service (or daemon) - shutdown before upgrading.
- for a console application - execute a 'shutdown' command in the RavenDB CLI.
Remove old RavenDB binaries
- Avoid deleting your actual data, contained in folders like
- Avoid overwriting your configuration files, e.g. settings.json.
- Avoid deleting your certificate file (ending with
- For additional information see the certificate page.
- These steps are strictly necessary when updating to version 5.1.
To update to lower versions, overriding the old binaries may be sufficient - although removing them is recommended.
Copy the new binaries.
Restart the server.
High Availability & Cluster
For zero downtime during a version upgrade, please upgrade a single cluster node at
a time and wait until it becomes a fully fledged node (either Member, Leader, or Watcher).
The state of the node can be checked in Cluster View.
Upgrading Data Files
While upgrade RavenDB, no special action is needed to migrate the stored data.
However, sometimes our adjustments require changing the file format ("schema version").
If RavenDB finds during startup that the stored database uses an old format, it
will automatically perform this kind of migration.
Migrating data files is only one type of migration.
If you try to downgrade to an older RavenDB version after making any changes in data files
format, RavenDB will fail to start with a detailed error message.
Data can also be migrated, across all RavenDB versions, using
or External replication.
Major version upgrade
4.x does not support automatic upgrading from previous major versions of the product (e.g.
Please read the migration article for additional data and client migration strategies.
If you have a license for a RavenDB version older than
6.x, upgrading to version
6.0 will require you
to upgrade your license key.
- Read here how to upgrade
and replace your existing license key.
- Read here about migrating from one RavenDB version to another.